2-part Positioning Reference Signal (PRS)

Abstract

Techniques for wireless communications are disclosed. In one aspect, a user equipment (UE) receives configuration information for a two-part positioning reference signal (PRS) transmitted by a transmission point, the two-part PRS including a first part PRS and a second part PRS separated by a time gap, attempts to detect the first part PRS based on the configuration information, and obtains positioning measurements for the second part PRS based on the detection of the first part PRS and the configuration information.

Description

[Technical Field]

[0001] 1. Field of Disclosure Aspects of the present disclosure relate generally to wireless communications, and more particularly to reference signal structures for positioning.

[0002] 2. Description of Related Technology Wireless communication systems have evolved through various generations, including first-generation (1G) analog wireless telephone service, second-generation (2G) digital wireless telephone service (including interim 2.5G and 2.75G networks), third-generation (3G) high-speed data, Internet-enabled wireless service, and fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular systems and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog advanced mobile phone system (AMPS) and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile communications (GSM), etc.

[0003] The fifth-generation (5G) wireless standard, called New Radio (NR), enables higher data rates, more connections, and better coverage, among other improvements. According to the Next Generation Mobile Network Alliance, the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technical enhancements compared to previous standards. These enhancements, as well as the use of higher frequency bands, advances in PRS processes and technology, and dense deployments for 5G, enable highly accurate 5G-based positioning. Summary of the Invention

[0004]

[0004] The following presents a simplified summary of one or more aspects disclosed herein. As such, the following summary should not be considered an extensive overview of all contemplated aspects, nor should it be considered as identifying key or critical elements of all contemplated aspects or as delimiting the scope of any particular aspect. Thus, the sole purpose of the following summary is to present certain concepts of one or more aspects of the mechanisms disclosed herein in a simplified form prior to the detailed description presented below.

[0005]

[0005] In one aspect, a method of wireless communication performed by user equipment (UE) includes receiving configuration information for a two-part positioning reference signal (PRS) transmitted by a transmission point, the two-part PRS including a first part PRS and a second part PRS separated by a time gap, attempting to detect the first part PRS based on the configuration information, and obtaining positioning measurements of the second part PRS based on the detection of the first part PRS and the configuration information.

[0006]

[0006] In one aspect, a user equipment (UE) comprises a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, configuration information for a two-part positioning reference signal (PRS) transmitted by a transmission point, the two-part PRS including a first part PRS and a second part PRS separated by a time gap; attempt to detect the first part PRS based on the configuration information; and obtain positioning measurements of the second part PRS based on the detection of the first part PRS and the configuration information.

[0007] In one aspect, a user equipment (UE) comprises: means for receiving configuration information for a two-part positioning reference signal (PRS) transmitted by a transmission point, the PRS including a first part PRS and a second part PRS separated by a time gap; means for attempting to detect the first part PRS based on the configuration information; and means for obtaining positioning measurements for the second part PRS based on the detection of the first part PRS and the configuration information.

[0008]

[0008] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to receive configuration information for a two-part positioning reference signal (PRS) transmitted by a transmission point, the two-part PRS including a first part PRS and a second part PRS separated by a time gap, attempt to detect the first part PRS based on the configuration information, and obtain positioning measurements of the second part PRS based on the detection of the first part PRS and the configuration information.

[0009]

[0009] Other objects and advantages associated with the embodiments disclosed herein will become apparent to those skilled in the art based on the accompanying drawings and detailed description. [Brief explanation of the drawings]

[0010]

[0010] The accompanying drawings are presented to aid in the explanation of various aspects of the present disclosure and are provided only to illustrate the aspects, not to limit the aspects. [Figure 1]

[0011] FIG. 1 illustrates an exemplary wireless communication system according to aspects of the present disclosure. [Figure 2A]

[0012] 1 illustrates an exemplary wireless network structure according to an aspect of the present disclosure. [Figure 2B] 1 illustrates an exemplary wireless network structure according to an aspect of the present disclosure. [Figure 2C] 1 illustrates an exemplary wireless network structure according to an aspect of the present disclosure. [Figure 3A]

[0013] 1 is a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE) and configured to support communication as taught herein; [Figure 3B] 1 is a simplified block diagram of several sample aspects of components that may be employed in a base station and configured to support communication as taught herein; [Figure 3C] 1 is a simplified block diagram of several sample aspects of components that may be employed in a network entity and configured to support communications as taught herein; [Figure 4]

[0014] 1 illustrates examples of various positioning methods supported in New Radio (NR), according to aspects of the present disclosure. [Figure 5]

[0015] 1 illustrates an example Long Term Evolution (LTE) positioning protocol (LPP) capability transfer procedure, assistance data transfer procedure, and location information transfer procedure between a target device and a location server, according to an aspect of the present disclosure. [Figure 6]

[0016] FIG. 2 illustrates an exemplary frame structure according to aspects of the present disclosure. [Figure 7]

[0017] FIG. 1 illustrates an example downlink positioning reference signal (DL-PRS) configuration for two transmission-reception points (TRPs) operating within the same positioning frequency layer, according to an embodiment of the present disclosure. [Figure 8]

[0018] FIG. 1 illustrates an example of a space vehicle generating multiple transmit beams toward multiple geographic regions. [Figure 9]

[0019] FIG. 10 illustrates further aspects of reference signal time difference (RSTD) measurement between a reference transmission point (TP) and a neighboring transmission point (TP), according to aspects of the present disclosure. [Figure 10]

[0020] FIG. 10 illustrates example latencies for different positions of non-terrestrial network (NTN) transmission points relative to a UE's location, according to an aspect of the present disclosure. [Figure 11]

[0021] FIG. 1 illustrates an aspect of a two-part positioning reference signal (PRS) according to an aspect of the present disclosure. [Figure 12]

[0022] FIG. 10 illustrates aspects of RSTD measurements between a reference transmission point (TP) and a neighboring transmission point (TP), according to aspects of the present disclosure. [Figure 13]

[0023] FIG. 10 illustrates example PRS configuration parameters that may be provided to a UE during an LPP-assisted data transfer procedure, according to an aspect of the disclosure. [Figure 14]

[0024] FIG. 10 illustrates example PRS configuration parameters for supporting a two-part PRS, according to an aspect of the disclosure. [Figure 15]

[0025] FIG. 10 illustrates the same PRS resource identifier within a PRS resource set of a positioning frequency layer defining both part A and part B of a two-part PRS, according to an aspect of the disclosure. [Figure 16]

[0026] FIG. 10 illustrates example PRS configuration parameters that may be defined for a PRS resource identifier that defines both part A and part B of a two-part PRS, according to an aspect of the disclosure. [Figure 17]

[0027] FIG. 10 illustrates different PRS resource identifiers in different PRS resource sets of the same positioning frequency layer defining part A and part B of a two-part PRS, according to an aspect of the disclosure. [Figure 18]

[0028] FIG. 10 illustrates example parameters that may be added to assistance data for a TRP to enable a two-part PRS across different PRS resource sets of the same positioning frequency layer, according to an aspect of the disclosure. [Figure 19]

[0029] 1 illustrates an exemplary method of wireless communication according to an aspect of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0011]

[0030] Aspects of the present disclosure are provided in the following description and related drawings, directed to various examples provided for illustrative purposes. Alternative aspects may be devised without departing from the scope of the present disclosure. Additionally, well-known elements of the present disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the present disclosure.

[0012]

[0031] The words "exemplary" and / or "example" are used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" and / or "example" is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term "aspects of the present disclosure" does not require that all aspects of the present disclosure include the discussed feature, advantage or mode of operation.

[0013]

[0032] Those skilled in the art will understand that the information and signals described below may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the following description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the particular application, desired design, corresponding technology, etc.

[0014]

[0033] Further, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be appreciated that various actions described herein can be performed by specific circuitry (e.g., application specific integrated circuits (ASICs)), by program instructions executed by one or more processors, or a combination of both. In addition, the sequence(s) of actions described herein may be considered to be embodied entirely in any form of non-transitory computer-readable medium storing a corresponding set of computer instructions, which, when executed, cause or instruct the associated processor(s) of a device to perform the functionality described herein. Accordingly, various aspects of the present disclosure may be embodied in several different forms, all of which are contemplated to be within the scope of the claimed subject matter. Additionally, for each aspect described herein, the corresponding form of any such aspect may be described herein as, for example, “logic configured to” perform the described actions.

[0015]

[0034] The terms “user equipment” (UE) and “base station” as used herein are not intended to be specific to or limited to any particular radio access technology (RAT) unless otherwise specified. Generally, a UE can be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a consumer location device, a wearable (e.g., a smart watch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. A UE may be mobile or may be stationary (e.g., at a given time) and may communicate with a radio access network (RAN). As used herein, the term "UE" may be referred to interchangeably as an "access terminal" or "AT," "client device," "wireless device," "subscriber device," "subscriber terminal," "subscriber station," "user terminal" or "UT," "mobile device," "mobile terminal," "mobile station," or variations thereof. Generally, a UE may communicate with a core network via a RAN, through which the UE may be connected to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for a UE, such as via a wired access network, a wireless local area network (WLAN) network (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.), etc.

[0016]

[0035] A base station may operate according to one of several RATs with which it communicates with UEs depending on the network in which it is deployed and may alternatively be referred to as an access point (AP), network node, Node B, evolved Node B (eNB), next generation eNB (ng-eNB), New Radio (NR) Node B (also referred to as gNB or gNode B), etc. A base station may be used primarily to support wireless access by UEs, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, a base station may provide only edge node signaling functionality, while in other systems, a base station may provide additional control and / or network management functions. The communication link over which a UE can send signals to a base station is called an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). A communication link through which a base station can send signals to a UE is called a downlink (DL) channel or a forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term traffic channel (TCH) can refer to either an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0017]

[0036] The term "base station" can refer to a single physical transmission / reception point (TRP) or multiple physical TRPs, which may or may not be collocated. For example, when the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to the base station's cell (or several cell sectors). When the term "base station" refers to multiple collocated physical TRPs, the physical TRP may be an array of antennas of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or when the base station employs beamforming). When the term "base station" refers to multiple non-collocated physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, non-co-located physical TRPs may be the serving base station that receives measurement reports from the UE and neighboring base stations whose reference radio frequency (RF) signals the UE is measuring. Because a TRP is a point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station should be understood as referring to a particular TRP of the base station.

[0018]

[0037] In some implementations that support UE positioning, a base station may not support wireless access by the UE (e.g., may not support data, voice, and / or signaling connections for the UE), but instead may transmit reference signals to the UE to be measured by the UE and / or may receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., if it transmits signals to the UE) and / or a location measurement unit (e.g., if it receives and measures signals from the UE).

[0019]

[0038] An "RF signal" includes electromagnetic waves of a given frequency that propagate information through space between a transmitter and a receiver. 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 RF signals through multipath channels, the receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same RF signal transmitted over different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal" when it is clear from the context that the term "signal" refers to a wireless signal or an RF signal.

[0020]

[0039] 1 illustrates an exemplary wireless communication system 100 according to an aspect of the present disclosure. The wireless communication system 100 (sometimes referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled “BS”) and various UEs 104. The base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macrocell base stations may include eNBs and / or ng-eNBs where the wireless communication system 100 corresponds to an LTE network, or gNBs where the wireless communication system 100 corresponds to an NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0021]

[0040] The base stations 102 may collectively form a RAN and may interface with a core network 170 (e.g., evolved packet core (EPC) or 5G core (5G core, 5GC)) through backhaul links 122 and to one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) through the core network 170. The location server(s) 172 may be part of the core network 170 or may be external to the core network 170. The location server(s) 172 may be integrated with the base station 102. The UE 104 may communicate with the location server 172 directly or indirectly. For example, the UE 104 may communicate with the location server 172 through the base station 102 currently serving the UE 104. The UE 104 may also communicate with the location server 172 through another path, such as through an application server (not shown), through another network, such as through a wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below), etc. For signaling purposes, communication between the UE 104 and the location server 172 may be represented as an indirect connection (e.g., through the core network 170), or a direct connection (e.g., as shown via direct connection 128), with intervening nodes (if any) omitted from the signaling diagrams for clarity.

[0022]

[0041] In addition to other functions, the base stations 102 may perform functions related to one or more of the following: forwarding user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, non-access stratum (NAS) message delivery, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracing, RAN information management (RIM), paging, positioning, and alert message delivery. The base stations 102 may communicate with each other directly or indirectly (e.g., through EPC / 5GC) via backhaul links 134, which may be wired or wireless.

[0023]

[0042] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In one aspect, one or more cells may be supported by the base stations 102 in each geographic coverage area 110. A “cell” is a logical communication entity used for communication with a base station (e.g., over some frequency resources referred to as a carrier frequency, component carrier, carrier, band, etc.) and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) to distinguish between cells operating over the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access to different types of UEs. Because a cell is supported by a particular base station, the term "cell" may refer to either or both of the logical communication entity and its supporting base station, depending on the context. Additionally, because a TRP is typically the physical transmission point of a cell, the terms "cell" and "TRP" may be used interchangeably. In some cases, the term "cell" may also refer to the geographic coverage area (e.g., sector) of a base station, as long as the carrier frequency can be detected and used for communication within some portion of the geographic coverage area 110.

[0024]

[0043] The geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in handover regions), and some of the geographic coverage areas 110 may be significantly overlapped by larger geographic coverage areas 110. For example, a small cell base station 102' (labeled "SC" for "small cell") may have a geographic coverage area 110' that significantly overlaps with the geographic coverage area 110 of one or more macrocell base stations 102. A network including both small cell and macrocell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs), which may serve closed groups known as closed subscriber groups (CSGs).

[0025]

[0044] The communication link 120 between the base station 102 and the UE 104 may include uplink (also called reverse link) transmissions from the UE 104 to the base station 102, and / or downlink (DL) (also called forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be over one or more carrier frequencies. Carrier allocation may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be allocated for the downlink than for the uplink).

[0026]

[0045] The wireless communication system 100 may further include a wireless local area network (WLAN) access point (WLAN) 150 communicating in an unlicensed frequency spectrum (e.g., 5 gigahertz (GHz)) with wireless local area network (WLAN) stations (STAs) 152 via communication link 154. When communicating in the unlicensed frequency spectrum, the WLAN STAs 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure before communicating to determine whether a channel is available.

[0027]

[0046] The small cell base station 102' may operate in a licensed and / or unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102' may employ LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum used by the WLAN AP 150. A small cell base station 102' employing LTE / 5G in an unlicensed frequency spectrum may extend coverage to and / or increase the capacity of an access network. NR in an unlicensed spectrum may be referred to as NR-U. LTE in an unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MultiFire.

[0028]

[0047] The wireless communication system 100 may further include an mmW base station 180 that may operate at millimeter wave (mmW) and / or sub-mmW frequencies in communication with the UE 182. Extremely high frequency (EHF) is a portion of RF in the electromagnetic spectrum. EHF ranges from 30 GHz to 300 GHz and has wavelengths from 1 millimeter to 10 millimeters. Radio waves within this band may be referred to as millimeter waves. Sub-mmW may fall down to frequencies of 3 GHz with wavelengths of 100 millimeters. The super high frequency (SHF) band ranges from 3 GHz to 30 GHz and is also referred to as centimeter waves. Communications using the mmW / sub-mmW radio frequency bands have high path loss and relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and / or receive) over the mmW communication link 184 to compensate for the extremely high path loss and short range. Furthermore, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or quasi-mmW and beamforming. Accordingly, it will be appreciated that the above illustrations are merely examples and should not be construed as limiting various aspects disclosed herein.

[0029]

[0048] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., UE) is located (relative to the transmitting network node) and emits a stronger downlink RF signal in that specific direction, thereby providing a faster and more powerful RF signal (in terms of data rate) to the receiving device(s). To change the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, the network node may use an array of antennas (also called a "phased array" or "antenna array") that creates beams of RF waves that can be "steered" to point in different directions without actually moving the antennas. Specifically, RF currents from the transmitters are supplied to the individual antennas with the appropriate phase relationship so that radio waves from the separate antennas are combined to cancel and suppress radiation in undesired directions while increasing radiation in desired directions.

[0030]

[0049] A transmit beam may be quasi-colocated, meaning that the transmit beam appears to a receiver (e.g., a UE) to have the same parameters regardless of whether the network node's own transmit antenna is physically colocated. In NR, there are four types of quasi-colocation (QCL) relationships. Specifically, a given type of QCL relationship means that some parameters for a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam. Thus, if the source reference RF signal is QCL Type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, mean delay, and delay spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type D, the receiver can use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0031]

[0050] In receive beamforming, a receiver uses receive beams to amplify RF signals detected on a given channel. For example, the receiver can increase the gain setting and / or adjust the phase setting of an antenna array in a particular direction to amplify (e.g., increase its gain level) RF signals received from that direction. Thus, when a receiver is said to beamform in a certain direction, it means that the beam gain in that direction is higher than the beam gains along other directions, or that the beam gain in that direction is the highest compared to the beam gains in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.) of RF signals received from that direction.

[0032]

[0051] The transmit beam and the receive beam may be spatially related. Spatial relationship means that parameters for a second beam (e.g., a transmit beam or a receive beam) for a second reference signal may be derived from information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal. For example, a UE may use a particular receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE can then form a transmit beam for sending an uplink reference signal (e.g., a sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.

[0033]

[0052] Note that a "downlink" beam can be either a transmit beam or a receive beam, depending on the entity that forms it. For example, if a base station forms a downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. However, if the UE forms a downlink beam, it is a receive beam to receive a downlink reference signal. Similarly, an "uplink" beam can be either a transmit beam or a receive beam, depending on the entity that forms it. For example, if a base station forms an uplink beam, it is an uplink receive beam, and if the UE forms an uplink beam, it is an uplink transmit beam.

[0034]

[0053] The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that, although a portion of FR1 is above 6 GHz, FR1 is often referred to (interchangeably) as the “sub-6 GHz” band in various documents and papers. Similar nomenclature issues may arise with respect to FR2, which is often referred to (interchangeably) as the “millimeter wave” band in documents and papers, even though it is different from the Extremely High Frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunications Union (ITU) as the “millimeter wave” band.

[0035]

[0054] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands within FR3 may inherit the characteristics of FR1 and / or FR2, thus effectively extending the features of FR1 and / or FR2 to the mid-band frequencies. Furthermore, higher frequency bands are currently being considered to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands is within the EHF band.

[0036]

[0055] With the above aspects in mind, it should be understood that, unless specifically stated otherwise, terms such as "sub-6 GHz," as used herein, may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Furthermore, it should be understood that, unless specifically stated otherwise, terms such as "mmWave," as used herein, may broadly refer to frequencies that may include mid-band frequencies, may be within the ranges of FR2, FR4, FR4-a, or FR4-1, and / or FR5, or may be within the EHF band.

[0037]

[0056] In a multi-carrier system such as 5G, one of the carrier frequencies is referred to as the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell," and the remaining carrier frequencies are referred to as "secondary carriers" or "secondary serving cells" or "SCells." In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by the UE 104 / 182 and the cell on which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common control channels and UE-specific control channels and may (but is not always) be a carrier among licensed frequencies. The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once an RRC connection is established between the UE 104 and the anchor carrier and may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier among unlicensed frequencies. Since both the primary uplink carrier and the primary downlink carrier are typically UE-specific, the secondary carrier shall contain only the necessary signaling information and signals; e.g., there shall be no UE-specific signaling information and signals in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same applies to the uplink primary carrier. The network may change the primary carrier of any UE 104 / 182 at any time. This may be done, for example, to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier over which several base stations are communicating, terms such as "cell," "serving cell," "component carrier," and "carrier frequency" may be used interchangeably.

[0038]

[0057] For example, with continued reference to FIG. 1, one of the frequencies utilized by the macrocell base station 102 may be an anchor carrier (or "PCell"), and other frequencies utilized by the macrocell base station 102 and / or the mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two 20 MHz carriers aggregated in a multi-carrier system would theoretically provide a two-fold increase in data rate (i.e., 40 MHz) compared to the data rate achieved by a single 20 MHz carrier.

[0039]

[0058] Wireless communications system 100 may further include UE 164, which may communicate with macrocell base station 102 via communications link 120 and / or with mmW base station 180 via mmW communications link 184. For example, macrocell base station 102 may support a PCell and one or more SCells for UE 164, and mmW base station 180 may support one or more SCells for UE 164.

[0040]

[0059] In some cases, the UE 164 and the UE 182 may be capable of sidelink communication. Sidelink-capable UEs (SL-UEs) can communicate with the base station 102 via a communication link 120 that uses the Uu interface (i.e., the air interface between the UE and the base station). SL-UEs (e.g., the UE 164, the UE 182) may also communicate directly with each other via a wireless sidelink 160 that uses the PC5 interface (i.e., the air interface between sidelink-capable UEs). Wireless sidelink (or simply "sidelink") is an adaptation of the core cellular (e.g., LTE, NR) standard that enables direct communication between two or more UEs without the communication having to go through a base station. Sidelink communications may be unicast or multicast and may be used for device-to-device (D2D) medium sharing, vehicle-to-vehicle (V2V) communications, vehicle-to-everything (V2X) communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more of a group of SL-UEs utilizing sidelink communications may be within the geographic coverage area 110 of the base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of the base station 102 or may in some cases be unable to receive transmissions from the base station 102. In some cases, a group of SL-UEs communicating via sidelink communications may utilize a one-to-many (1:M) system in which each SL-UE transmits to all other SL-UEs in the group. In some cases, the base station 102 facilitates the scheduling of resources for sidelink communication. In other cases, sidelink communication is performed between SL-UEs without the involvement of the base station 102.

[0041]

[0060] In one aspect, the sidelink 160 may operate over a target wireless communications medium, which may be shared with other vehicular and / or infrastructure access points, as well as other wireless communications between other RATs. The “medium” may consist of one or more time, frequency, and / or spatial communications resources (e.g., encompassing one or more channels across one or more carriers) associated with wireless communications between one or more transmitter / receiver pairs. In one aspect, the target medium may correspond to at least a portion of an unlicensed frequency band shared among various RATs. While different licensed frequency bands have been reserved for some communications systems (e.g., by government agencies such as the Federal Communications Commission (FCC) in the United States), these systems, particularly those employing small cell access points, have recently extended operation to unlicensed frequency bands, such as the Unlicensed National Information Infrastructure (U-NII) bands used by Wireless Local Area Network (WLAN) technologies, most notably the IEEE 802.11x WLAN technology commonly referred to as “Wi-Fi.” Exemplary systems of this type include CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and various variations thereof.

[0042]

[0061] 1 illustrates only two of the UEs as SL-UEs (i.e., UEs 164 and 182), it should be noted that any of the illustrated UEs may be SL-UEs. Additionally, while only UE 182 has been described as being beamforming capable, any of the illustrated UEs, including UE 164, may be beamforming capable. If SL-UEs are beamforming capable, they may beamform toward each other (i.e., toward other SL-UEs), toward other UEs (e.g., UE 104), toward a base station (e.g., base station 102, 180, small cell 102′, access point 150), etc. Thus, in some cases, UE 164 and UE 182 may utilize beamforming over sidelink 160.

[0043]

[0062] In the example of FIG. 1, any of the illustrated UEs (shown in FIG. 1 as UEs 114 and 116 for simplicity) may receive signals 124 from one or more Earth-orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SVs 112 may be part of a satellite positioning system that the UEs 114 and / or 116 (or any other UE) can use as an independent source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SVs 112) positioned to enable receivers (e.g., UEs 114 and / or 116) to determine their location on or above the Earth based, at least in part, on positioning signals (e.g., signals 124) received from the transmitters. Such transmitters typically transmit signals marked with a repeating pseudo-random noise (PN) code of a set number of chips. Although typically located within the SV 112, the transmitter may sometimes be located on a ground-based control station, a base station 102, and / or another UE 104. The UE (e.g., UE 114 and / or 116) may include one or more dedicated receivers specifically designed to receive signals 124 from the SV 112 to derive geolocation information.

[0044]

[0063] In a satellite positioning system, the use of signals 124 may be augmented by various satellite-based augmentation systems (SBAS) that may be associated with or enabled for use with one or more global and / or regional navigation satellite systems. For example, the SBAS may include augmentation system(s) that provide integrity information, error correction, etc., such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi-functional Satellite Augmentation System (MSAS), the Global Positioning System (GPS) Aided Geo-Augmented Navigation, or the GPS and Geo Augmented Navigation system (GAGAN). Thus, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0045]

[0064] In one aspect, the SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, the SV 112 is connected to an earth station (ES) 118 (also referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in a 5G network (e.g., core network 170). This element then provides access to other elements in the 5G network and ultimately to entities outside the 5G network, such as Internet web servers and other user devices. In this manner, the UE 114 and / or 116 may receive communication signals (e.g., signal 124) from the SV 112 instead of, or in addition to, communication signals from the terrestrial base station 102. The wireless link between the UE (e.g., UE 114, 116) and the SV 112 is referred to as a “service link” (e.g., service link 124). The wireless link between the SV 112 and the ground station 118 is called a "feeder link" (eg, feeder link 126).

[0046]

[0065] NTNs may also be used to enhance 5G service reliability by providing service continuity for machine-to-machine (M2M) devices and / or IoT devices, or for passengers on moving platforms (e.g., passenger vehicles such as airplanes, ships, high-speed trains, buses, etc.), or by ensuring service availability anywhere, especially for critical communications. NTNs can also enable 5G network scalability by providing efficient multicast / broadcast resources for data delivery towards the network edge or even to the UEs (e.g., UEs 114 and / or 116).

[0047]

[0066] 1, the SV 112 is in communication with a UE 114 (representing a UE in an area not served by a terrestrial 5G network) outside the coverage area of ​​the base station 102, and with a UE 116 (representing a UE not fully served by a terrestrial 5G network) inside the coverage area of ​​the base station 102. Thus, the SV 112 may act as a serving base station to the UE 114 and as a primary or secondary cell to the UE 116 depending on the services provided to the UE 116 by the base station 102.

[0048]

[0067] It should be noted that although FIG. 1 only shows a single SV 112 and a single ground station 118, it should be appreciated that this is by way of example only and that there may be any number of SVs 112 connected to any number of ground stations 118.

[0049]

[0068] The wireless communication system 100 may further include one or more UEs, such as a UE 190, that indirectly connect to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “sidelinks”). In the example of FIG. 1, the UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which the UE 190 may indirectly obtain cellular connectivity), and a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (through which the UE 190 may indirectly obtain WLAN-based Internet connectivity). In one example, the D2D P2P links 192 and 194 may be supported using any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, etc.

[0050]

[0069] 2A illustrates an exemplary wireless network structure 200. For example, a 5GC 210 (also referred to as a Next Generation Core (NGC)) may be functionally considered as control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212 (e.g., UE gateway functions, data network access, IP routing, etc.) that operate cooperatively to form a core network. A user plane interface (NG-U) 213 and a control plane interface (NG-C) 215 connect a gNB 222 to the 5GC 210, specifically to the user plane function 212 and the control plane function 214, respectively. In an additional configuration, the ng-eNB 224 may also be connected to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. Additionally, the ng-eNB 224 may communicate directly with the gNB 222 via a backhaul connection 223. In some configurations, the Next Generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of both the ng-eNB 224 and the gNB 222. Either the gNB 222 or the ng-eNB 224 (or both) may communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0051]

[0070] Another optional aspect may include a location server 230, which may be in communication with the 5GC 210 to provide location assistance to the UE(s) 204. The location servers 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The location servers 230 may be configured to support one or more location services for UEs 204 that can connect to the location server 230 via the core network, the 5GC 210, and / or the Internet (not shown). Furthermore, the location server 230 may be integrated into a component of the core network, or alternatively, may be external to the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0052]

[0071] 2B illustrates another exemplary wireless network structure 240. A 5GC 260 (which may correspond to 5GC 210 in FIG. 2A ) may be considered functionally as control plane functions provided by an access and mobility management function (AMF) 264 and user plane functions provided by a user plane function (UPF) 262, which operate cooperatively to form a core network (i.e., 5GC 260). The functions of the AMF 264 include registration management, connection management, reachability management, mobility management, lawful intercept, transport for session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and a session management function (SMF) 266, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the UE 204 and a short message service function (SMSF) (not shown), and a security anchor functionality (SEAF). The AMF 264 also communicates with an authentication server function (AUSF) (not shown) and the UE 204 to receive intermediate keys established as a result of the UE 204 authentication process. In the case of UMTS (universal mobile telecommunications system) subscriber identity module (USIM)-based authentication, the AMF 264 retrieves security material from the AUSF. The AMF 264's functions also include security context management (SCM), which receives keys from the SEAF that the SCM uses to derive access network specific keys.The functionality of the AMF 264 also includes location service management for regulatory services, transport for location service messages between the UE 204 and the Location Management Function (LMF) 270 (acting as the location server 230), transport for location service messages between the NG-RAN 220 and the LMF 270, Evolved Packet System (EPS) bearer identifier allocation for interworking with EPS, and UE 204 mobility event notification. In addition, the AMF 264 also supports functions for non-3GPP (Third Generation Partnership Project) access networks.

[0053]

[0072] The functions of the UPF 262 include acting as an anchor point for intra-RAT / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) processing for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic validation (service data flow (SDF) to QoS flow mapping), transport-level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more "end markers" to the source RAN node. The UPF 262 may also support the transfer of location service messages over the user plane between the UE 204 and a location server such as the SLP 272.

[0054]

[0073] The functions of the SMF 266 include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering in the UPF 262 to route traffic to the appropriate destination, control of policy enforcement and parts of QoS, and downlink data notification. The interface through which the SMF 266 communicates with the AMF 264 is called the N11 interface.

[0055]

[0074] Another optional aspect may include an LMF 270, which may be in communication with the 5GC 260, to provide location assistance to the UE 204. The LMF 270 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The LMF 270 may be configured to support one or more location services for UEs 204 that may connect to the LMF 270 via a core network, the 5GC 260, and / or via the Internet (not shown). The SLP 272 may support similar functions as the LMF 270, while the LMF 270 may communicate with the AMF 264, the NG-RAN 220, and the UE 204 via the control plane (e.g., using interfaces and protocols intended to convey signaling messages rather than voice or data), and the SLP 272 may communicate with the UE 204 and external clients (e.g., third-party servers 274) via the user plane (e.g., using protocols intended to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP).

[0056]

[0075] Yet another optional aspect may include a third party server 274, which may be in communication with the LMF 270, the SLP 272, the 5GC 260 (e.g., via the AMF 264 and / or the UPF 262), the NG-RAN 220, and / or the UE 204 to obtain location information (e.g., a location estimate) for the UE 204. Thus, in some cases, the third party server 274 may be referred to as a location services (LCS) client or an external client. The third party servers 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternatively, each may correspond to a single server.

[0057]

[0076] A user plane interface 263 and a control plane interface 265 connect the 5GC 260, and in particular the UPF 262 and AMF 264, to one or more gNBs 222 and / or ng-eNBs 224, respectively, in the NG-RAN 220. The interface between the gNB(s) 222 and / or ng-eNB(s) 224 and the AMF 264 is referred to as the “N2” interface, and the interface between the gNB(s) 222 and / or ng-eNB(s) 224 and the UPF 262 is referred to as the “N3” interface. The gNB(s) 222 and / or ng-eNB(s) 224 of the NG-RAN 220 may communicate directly with each other via a backhaul connection 223, referred to as the “Xn-C” interface. One or more of the gNB222 and / or ng-eNB224 may communicate with one or more UE204 via a wireless interface referred to as the "Uu" interface.

[0058]

[0077] The functionality of the gNB 222 may be divided between a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DUs) 228, and one or more gNB radio units (gNB-RUs) 229. The gNB-CU 226 is a logical node that includes base station functions such as user data forwarding, mobility control, radio access network sharing, positioning, and session management, except for those functions exclusively allocated to the gNB-DU(s) 228. More specifically, the gNB-CU 226 typically hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that typically hosts the Radio Link Control (RLC) and Medium Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or multiple cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and one or more gNB-DUs 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of the gNB 222 is generally hosted by one or more standalone gNB-RUs 229, which perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU 228 and the gNB-RU 229 is referred to as the "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC, SDAP, and PDCP layers, with the gNB-DU 228 via the RLC and MAC layers, and with the gNB-RU 229 via the PHY layer.

[0059]

[0078] The deployment of a communication system, such as a 5G NR system, may be configured in multiple ways using various components or components. In a 5G NR system or network, a network node, network entity, mobility element of a network, RAN node, core network node, network element, or network equipment, such as a base station or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), transmit / receive point (TRP), or cell) may be implemented as an aggregated base station (also known as a standalone base station or monolithic base station) or a disaggregated base station.

[0060]

[0079] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A non-aggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (e.g., one or more centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU or alternatively may be geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0061]

[0080] The operation of a base station type or network design may take into account the aggregation characteristics of base station functionality. For example, a disaggregated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration supported by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units in different physical locations, as well as virtually distributing functionality for at least one unit, which may allow flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0062]

[0081] 2C illustrates an exemplary disaggregated base station architecture 250 according to an aspect of the present disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CU 226) that can communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link or indirectly with the core network 267 through one or more disaggregated base station units (e.g., a Near-Real Time (RT) RAN Intelligent Controller (RIC) 259 via an E2 link, or a non-real-time (non-RT) RIC 257 associated with a Service Management and Orchestration (SMO) framework 255, or both). The CU 280 may communicate with one or more distributed units (DUs) 285 (e.g., gNB-DU 228) via respective midhaul links, such as an F1 interface. The DU 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RU 229) via respective fronthaul links. The RU 287 may communicate with each UE 204 via one or more radio frequency (RF) access links. In some implementations, a UE 204 may be served by multiple RUs 287 simultaneously.

[0063]

[0082] Each of the units, i.e., CU 280, DU 285, RU 287, and quasi-RT RIC 259, non-RT RIC 257, and SMO framework 255, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more of the other units via a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to one or more of the other units via a wired transmission medium. Furthermore, the units may include a wireless interface, which may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive, transmit, or receive signals via a wireless transmission medium to one or more of the other units.

[0064]

[0083] In some aspects, the CU 280 can host one or more upper layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by the CU 280. The CU 280 may be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 280 may be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP units, when implemented in an O-RAN configuration, may communicate bidirectionally with the CU-CP units via an interface, such as an E1 interface. The CU 280 may be implemented to communicate with the DU 285 as needed for network control and signaling.

[0065]

[0084] The DU 285 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 287. In some aspects, the DU 285 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.), at least in part according to a functional division such as that defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DU 285 may further host one or more lower PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 285 or with control functions hosted by the CU 280.

[0066]

[0085] Lower layer functionality may be implemented by one or more RUs 287. In some deployments, the RUs 287 controlled by the DUs 285 may correspond to logical nodes hosting RF processing functions, lower PHY layer functions (such as performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional division, such as a lower layer functional division. In such an architecture, the RU(s) 287 may be implemented to handle over-the-air (OTA) communications with one or more UEs 204. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU(s) 287 may be controlled by the corresponding DUs 285. In some scenarios, this configuration may enable the DU(s) 285 and CU 280 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0067]

[0086] The SMO framework 255 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 255 may be configured to support deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (e.g., an O1 interface). For virtualized network elements, the SMO framework 255 may be configured to interact with a cloud computing platform (e.g., an open cloud (O-cloud) 269) via a cloud computing platform interface (e.g., an O2 interface) to perform network element lifecycle management (e.g., instantiate virtualized network elements). Such virtualized network elements may include, but are not limited to, the CU 280, the DU 285, the RU 287, and the quasi-RT RIC 259. In some implementations, the SMO framework 255 may communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 261, via the O1 interface. Additionally, in some implementations, the SMO framework 255 can communicate directly with one or more RUs 287 via an O1 interface. The SMO framework 255 may also include a non-RT RIC 257 configured to support the functionality of the SMO framework 255.

[0068]

[0087] The non-RT RIC 257 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the quasi-RT RIC 259. The non-RT RIC 257 may be coupled to or in communication with the quasi-RT RIC 259 (e.g., via an A1 interface). The quasi-RT RIC 259 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources by data collection and action via interfaces (e.g., via an E2 interface) that connect one or more CUs 280, one or more DUs 285, or both, and the O-eNB to the quasi-RT RIC 259.

[0069]

[0088] In some implementations, the non-RT RIC 257 may receive parameters or external enrichment information from an external server to generate the AI / ML models deployed to the quasi-RT RIC 259. Such information may be utilized by the quasi-RT RIC 259 or may be received from a non-network data source or from a network function in the SMO framework 255 or the non-RT RIC 257. In some examples, the non-RT RIC 257 or the quasi-RT RIC 259 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 257 may employ AI / ML models to monitor long-term trends and patterns in performance and implement corrective actions through the SMO framework 255 (e.g., reconfiguration via O1) or through the creation of RAN management policies (e.g., A1 policies).

[0070]

[0089] 3A, 3B, and 3C illustrate several example components (represented by corresponding blocks) that may be incorporated within a UE 302 (which may correspond to any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including a location server 230 and an LMF 270, or alternatively, may be independent of the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in FIGS. 2A and 2B, such as a private network) to support the operations described herein. It will be understood that these components may be implemented in different types of devices in different implementations (e.g., within an ASIC, within a system-on-chip (SoC), etc.). The illustrated components may also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to the illustrated components to provide similar functionality. Also, a given device may include one or more of the components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0071]

[0090] The UE 302 and the base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, providing means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) over one or more wireless communications networks (not shown), such as an NR network, an LTE network, a GSM network, etc. The WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes, such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc., over at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communications medium of interest (e.g., some set of time / frequency resources in a particular frequency spectrum). The WWAN transceivers 310 and 350 may be variously configured to transmit and encode signals 318 and 358, respectively (e.g., messages, instructions, information, etc.), and conversely, to receive and decode signals 318 and 358, respectively (e.g., messages, instructions, information, pilots, etc.) in accordance with a designated RAT. Specifically, the WWAN transceivers 310 and 350 include one or more transmitters 314 and 354, respectively, to transmit and encode signals 318 and 358, respectively, and include one or more receivers 312 and 352, respectively, to receive and decode signals 318 and 358, respectively.

[0072]

[0091] The UE 302 and base station 304 also each, at least in some cases, include one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, and may provide means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth, Zigbee, Z-Wave, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), ultra-wideband (UWB), etc.) over a target wireless communication medium. The short-range wireless transceivers 320 and 360 may be variously configured to transmit and encode signals 328 and 368, respectively (e.g., messages, instructions, information, etc.), and conversely, to receive and decode signals 328 and 368, respectively (e.g., messages, instructions, information, pilots, etc.) in accordance with a designated RAT. Specifically, the short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, to transmit and encode signals 328 and 368, respectively, and include one or more receivers 322 and 362, respectively, to receive and decode signals 328 and 368, respectively. As specific examples, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Bluetooth® transceivers, Zigbee® and / or Z-Wave® transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

[0073]

[0092] UE 302 and base station 304 also, in at least some cases, include satellite signal receivers 330 and 370. Satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide a means for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. If satellite signal receivers 330 and 370 are satellite positioning system receivers, satellite positioning / communication signals 338 and 378 may be Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, Beidou signals, Navigation Satellite System of India (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. If satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. Satellite signal receivers 330 and 370 may comprise any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request information and actions from other systems as appropriate and, at least in some cases, perform calculations using acquired measurements with any suitable satellite positioning system algorithms to determine the locations of UE 302 and base station 304, respectively.

[0074]

[0093] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, that provide a means for communicating (e.g., a means for transmitting, a means for receiving, etc.) with other network entities (e.g., other base stations 304, other network entities 306). For example, a base station 304 may employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 over one or more wired or wireless backhaul links. As another example, a network entity 306 may employ one or more network transceivers 390 to communicate with one or more base stations 304 over one or more wired or wireless backhaul links or with other network entities 306 over one or more wired or wireless core network interfaces.

[0075]

[0094] A transceiver may be configured to communicate over a wired link or a wireless link. The transceiver (whether a wired transceiver or a wireless transceiver) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., embodying the transmitter and receiver circuitry within a single device), in some implementations, may comprise separate transmitter and receiver circuitry, or in other implementations may be embodied in other ways. The transmitter and receiver circuitry of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. The wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array that enables the respective device (e.g., UE 302, base station 304) to perform transmit “beamforming,” as described herein. Similarly, the wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array that enables the respective device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter and receiver circuitry may share multiple identical antennas (e.g., antennas 316, 326, 356, 366), such that the respective device can only receive or transmit at a given time, but not both at the same time. The wireless transceivers (eg, WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a network listen module (NLM) or the like for performing various measurements.

[0076]

[0095] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360, and network transceivers 380 and 390, in some implementations) and wired transceivers (e.g., network transceivers 380 and 390, in some implementations) may be generally characterized as a “transceiver,” “at least one transceiver,” or “one or more transceivers.” Thus, whether a particular transceiver is a wired transceiver or a wireless transceiver can be inferred from the type of communication being performed. For example, backhaul communications between network devices or servers generally involve signaling via wired transceivers, while wireless communications between a UE (e.g., UE 302) and a base station (e.g., base station 304) generally involve signaling via wireless transceivers.

[0077]

[0096] The UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with operations as disclosed herein. The UE 302, base station 304, and network entity 306 each include one or more processors 332, 384, and 394, e.g., to provide functionality related to wireless communications and to provide other processing functionality. Accordingly, the processors 332, 384, and 394 can comprise processing means, such as determining means, calculating means, receiving means, transmitting means, and directing means. In one aspect, the processors 332, 384, and 394 can include, for example, one or more general-purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuitry, or various combinations thereof.

[0078]

[0097] The UE 302, the base station 304, and the network entity 306 include memory circuitry implementing memories 340, 386, and 396, respectively (e.g., each including a memory device) for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, etc.). Thus, the memories 340, 386, and 396 can provide means for storing, means for retrieving, means for maintaining, etc. In some cases, the UE 302, the base station 304, and the network entity 306 may include positioning components 342, 388, and 398, respectively. The positioning components 342, 388, and 398 may be hardware circuits that are part of or coupled to the processors 332, 384, and 394, respectively, that, when executed, cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. In other aspects, the positioning components 342, 388, and 398 may be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning components 342, 388, and 398 may be memory modules stored in the memories 340, 386, and 396, respectively, that, when executed by the processors 332, 384, and 394 (or modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. Figure 3A illustrates possible locations of the positioning component 342, which may be, for example, part of the one or more WWAN transceivers 310, the memory 340, the one or more processors 332, or any combination thereof, or may be a standalone component. FIG. 3B shows possible locations of a positioning component 388, which may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a stand-alone component.FIG. 3C shows possible locations of a positioning component 398, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a stand-alone component.

[0079]

[0098] The UE 302 may include one or more sensors 344 coupled to the one or more processors 332 to provide a means of sensing or detecting movement and / or orientation information that is independent of motion data derived from signals received by the one or more WWAN transceivers 310, the one or more short-range wireless transceivers 320, and / or the satellite signal receiver 330. By way of example, the sensor(s) 344 may include an accelerometer (e.g., a micro-electrical mechanical systems (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of motion detection sensor. Furthermore, the sensor(s) 344 may include multiple different types of devices, and their outputs may be combined to provide motion information. For example, the sensor(s) 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate position in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

[0080]

[0099] Additionally, the UE 302 includes a user interface 346 that provides a means for providing instructions to a user (e.g., audio and / or visual displays) and / or receiving user input (e.g., upon user actuation of a sensing device such as a keypad, touch screen, microphone, etc.). Although not shown, the base station 304 and the network entity 306 may also include user interfaces.

[0081]

[0100] Referring more particularly to the one or more processors 384, on the downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for an RRC layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. The one or more processors 384 may provide RRC layer functionality associated with broadcasting system information (e.g., master information blocks (MIBs), system information blocks (SIBs)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with forwarding upper layer PDUs, error correction via automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0082]

[0101] The transmitter 354 and receiver 352 may implement Layer-1 (L1) functionality associated with various signal processing functions. Layer-1, including the physical (PHY) layer, may include error detection on transport channels, forward error correction (FEC) coding / decoding of transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to orthogonal frequency division multiplexing (OFDM) subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine coding and modulation schemes and for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with the individual spatial streams for transmission.

[0083]

[0102] At the UE 302, the receiver 312 receives signals through its respective antenna(s) 316. The receiver 312 recovers information modulated onto RF carriers and provides the information to one or more processors 332. The transmitter 314 and receiver 312 implement Layer 1 functionality associated with various signal processing functions. The receiver 312 may perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they may be combined into a single OFDM symbol stream by the receiver 312. The receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency-domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 304. These soft decisions may be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the base station 304. The data and control signals are then provided to one or more processors 332 that implement Layer 3 (L3) and Layer 2 (L2) functionality.

[0084]

[0103] In the downlink, one or more processors 332 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header recovery, and control signal processing to recover IP packets from the core network. The one or more processors 332 are also responsible for error detection.

[0085]

[0104] Similar to the functionality described in connection with downlink transmissions by the base station 304, the one or more processors 332 provide RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with forwarding upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto transport blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

[0086]

[0105] Channel estimates derived by the channel estimator from a reference signal or feedback transmitted by the base station 304 may be used by the transmitter 314 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antenna(s) 316. The transmitter 314 may modulate an RF carrier with the individual spatial streams for transmission.

[0087]

[0106] Uplink transmissions are processed at the base station 304 in a manner similar to that described with respect to the receiver function at the UE 302. The receiver 352 receives signals via its respective antenna(s) 356. The receiver 352 recovers information modulated onto an RF carrier and provides the information to one or more processors 384.

[0088]

[0107] In the uplink, one or more processors 384 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the UE 302. The IP packets from the one or more processors 384 may be provided to the core network. The one or more processors 384 are also responsible for error detection.

[0089]

[0108] For convenience, the UE 302, base station 304, and / or network entity 306 are illustrated in FIGS. 3A, 3B, and 3C as including various components that may be configured in accordance with various examples described herein. However, it will be understood that the illustrated components may have different functionality in different designs. In particular, various components in FIGS. 3A-3C are optional in alternative configurations, and various aspects include configurations that may vary due to design choice, cost, device use, or other considerations. For example, in FIG. 3A, a particular implementation of the UE 302 may omit the WWAN transceiver(s) 310 (e.g., a wearable device or tablet computer or PC or laptop may have Wi-Fi and / or Bluetooth capabilities without cellular capabilities), or may omit the short-range wireless transceiver(s) 320 (e.g., cellular only, etc.), or may omit the satellite signal receiver 330, or may omit the sensor(s) 344, etc. 3B, a particular implementation of base station 304 may omit WWAN transceiver(s) 350 (e.g., a Wi-Fi “hotspot” access point without cellular capability), or may omit short-range wireless transceiver(s) 360 (e.g., cellular only), or may omit satellite signal receiver 370, etc. For the sake of brevity, examples of various alternative configurations are not provided herein, but should be readily apparent to those skilled in the art.

[0090]

[0109] The various components of the UE 302, the base station 304, and the network entity 306 may be communicatively coupled to one another via data buses 334, 382, ​​and 392, respectively. In one aspect, the data buses 334, 382, ​​and 392 may form or be part of communication interfaces of the UE 302, the base station 304, and the network entity 306, respectively. For example, when different logical entities are embodied within the same device (e.g., gNB and location server functionality incorporated within the same base station 304), the data buses 334, 382, ​​and 392 may provide communication therebetween.

[0091]

[0110] The components of Figures 3A, 3B, and 3C may be implemented in various ways. In some implementations, the components of Figures 3A, 3B, and 3C may be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors), where each circuit may use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide its functionality. For example, some or all of the functionality represented by blocks 310-346 may be implemented by the processor and memory component(s) of the UE 302 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). Similarly, some or all of the functionality represented by blocks 350-388 may be implemented by the processor and memory component(s) of the base station 304 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). Additionally, some or all of the functionality represented by blocks 390-398 may be implemented by the processor and memory component(s) of the network entity 306 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). For simplicity, various operations, actions, and / or functions are described herein as being performed "by the UE," "by the base station," "by the network entity," etc. However, it will be understood that such operations, actions, and / or functions may actually be performed by particular components or combinations of components of the UE 302, base station 304, network entity 306, etc., such as processors 332, 384, 394, transceivers 310, 320, 350, and 360, memories 340, 386, and 396, positioning components 342, 388, and 398, etc.

[0092]

[0111] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be separate from the network operator or operation of the cellular network infrastructure (e.g., the NG RAN 220 and / or the 5GC 210 / 260). For example, the network entity 306 may be a component of a private network that may be configured to communicate with the UE 302 via the base station 304 or independently of the base station 304 (e.g., via a non-cellular communication link such as WiFi).

[0093]

[0112] NR supports several cellular network-based positioning techniques, including downlink-based positioning methods, uplink-based positioning methods, and downlink-and-uplink-based positioning methods. Downlink-based positioning methods include observed time difference of arrival (OTDOA) in LTE, downlink time difference of arrival (DL-TDOA) in NR, and downlink angle-of-departure (DL-AoD) in NR. FIG. 4 illustrates examples of various positioning methods according to aspects of the present disclosure. In an OTDOA or DL-TDOA positioning procedure illustrated by scenario 410, a UE measures the relative downlink timing differences, referred to as reference signal time difference (RSTD) measurements or time difference of arrival (TDOA) measurements, between pairs of transmission points (e.g., terrestrial base stations, spacecraft, beacon transmitters, etc.), and reports them to a positioning entity. More specifically, the UE receives a reference transmission point (e.g., a serving base station) as well as identifiers (IDs) of multiple non-reference, or neighboring, transmission points in the assistance data. The UE then measures the RSTD between the reference transmission point and each of the non-reference transmission points. The UE may determine the RSTD as the difference between the start of the subframe (or slot) from the non-reference transmission point and the start of the subframe (or slot) from the reference transmission point that is closest in time to the subframe received from the reference transmission point. More specifically, the RSTD for non-serving transmission point "j" relative to reference transmission point "i" may be given as T_SubframeRx,j - T_SubframeRx,i.where T_SubframeRx,j is the time when the UE receives the start of one subframe from transmission point j, and T_SubframeRx,i is the time when the UE receives the corresponding start of one subframe from transmission point i that is closest in time to the subframe received from transmission point j. The UE may determine the start of a subframe (or slot) based on measurements of one or more downlink reference signals (e.g., PRS, TRS, CRS, CSI-RS, etc.) transmitted by each transmission point. For FR1, the reference point for RSTD measurements is the UE's antenna connector. For FR2, the reference point for RSTD measurements is the UE's antenna. Based on the known locations of the involved transmission points and the RSTD measurements, a positioning entity (e.g., the UE in the case of UE-based positioning, or a location server in the case of UE-assisted positioning) can estimate the UE's location.

[0094]

[0113] For DL-AoD positioning, as illustrated by scenario 420, the positioning entity uses measurement reports from the UE of received signal strength measurements of multiple downlink transmit beams to determine the angle(s) between the UE and the transmitting base station(s). The positioning entity can then estimate the location of the UE based on the determined angle(s) and the known location(s) of the transmitting base station(s).

[0095]

[0114] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle-of-arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but is based on an uplink reference signal (e.g., a sounding reference signal (SRS)) transmitted by the UE to multiple base stations. Specifically, the UE transmits one or more uplink reference signals that are measured by a reference base station and multiple non-reference base stations. Each base station then reports the reception time (called the relative time of arrival (RTOA)) of the reference signal(s) to a positioning entity (e.g., a location server), which knows the locations and relative timing of the participating base stations. Based on the reception-to-reception (Rx-Rx) time difference between the reported RTOA of the reference base station and that of each non-reference base station, the known locations of the base stations, and their known timing offsets, the positioning entity can estimate the UE's location using TDOA.

[0096]

[0115] For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink receive beams. The positioning entity uses the signal strength measurements and the angle(s) of the receive beam(s) to determine the angle(s) between the UE and the base station(s). Based on the determined angle(s) and the known location(s) of the base station(s), the positioning entity can then estimate the location of the UE.

[0097]

[0116] Downlink and uplink-based positioning methods include enhanced cell-ID (E-CID) positioning and multiple round-trip-time (RTT) positioning (also referred to as "multi-cell RTT" and "multi-RTT"). In an RTT procedure, a first entity (e.g., a base station or a UE) transmits a first RTT-related signal (e.g., a PRS or SRS) to a second entity (e.g., a UE or a base station), and the second entity transmits a second RTT-related signal (e.g., an SRS or PRS) back to the first entity. Each entity measures the time difference between the time of arrival (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. This time difference is called the reception-to-transmission (Rx-Tx) time difference. The Rx-Tx time difference measurement may be performed or adjusted to include only the time difference between the nearest slot boundaries for the received and transmitted signals. Both entities may then send their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round-trip propagation time (i.e., RTT) between the two entities from the two Rx-Tx time difference measurements (e.g., as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity may send its Rx-Tx time difference measurement to the other entity, which then calculates the RTT. The distance between the two entities may be determined from the RTT and a known signal speed (e.g., the speed of light). In the case of multi-RTT positioning illustrated by scenario 430, a first entity (e.g., a UE or base station) conducts RTT positioning procedures with multiple second entities (e.g., multiple base stations or UEs) to allow the location of the first entity to be determined based on the distance to the second entities and the known locations of the second entities (e.g., using multilateration). As illustrated by scenario 440, RTT and multi-RTT methods can be combined with other positioning techniques such as UL-AoA and DL-AoD to improve location accuracy.

[0098]

[0117] The E-CID positioning method is based on radio resource management (RRM) measurements. In E-CID, the UE reports the serving cell ID, timing advance (TA), and the identities, estimated timing, and signal strength of detected neighboring base stations. The UE's location is then estimated based on this information and the known location of the base station(s).

[0099]

[0118] To assist in positioning operations, a location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data to the UE. For example, the assistance data may include an identifier of the base station (or base station's cell / TRP) whose reference signal should be measured, reference signal configuration parameters (e.g., the number of consecutive slots containing the PRS, the periodicity of the consecutive slots containing the PRS, a muting sequence, a frequency hopping sequence, a reference signal identifier, a reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, the assistance data may be obtained directly from the base station itself (e.g., in a periodically broadcast overhead message, etc.). In some cases, the UE may be able to detect neighboring network nodes itself without using the assistance data.

[0100]

[0119] In the case of OTDOA or DL-TDOA positioning procedures, the assistance data may further include an expected RSTD value and an uncertainty, or search window, associated with the expected RSTD before and after the expected RSTD. In some cases, the value range for the expected RSTD may be + / - 500 microseconds (μs), or 0.5 milliseconds (ms). In some cases, when any of the resources used for the positioning measurements are in FR1, the value range for the expected RSTD uncertainty may be + / - 32 μs. In other cases, when all of the resources used for the positioning measurement(s) are in FR2, the value range for the expected RSTD uncertainty may be + / - 8 μs.

[0101]

[0120] A location estimate may be referred to by other names, such as a position estimate, location, position, position fix, or fix. A location estimate may be geodetic and include coordinates (e.g., latitude, longitude, and possibly altitude), or urban and include a street address, postal address, or some other linguistic description of the location. A location estimate may also be defined relative to some other known location, or may be defined absolutely (e.g., using latitude, longitude, and possibly altitude). A location estimate may include an expected error or uncertainty (e.g., by including an area or volume within which the location is expected to lie with some specified or default level of confidence).

[0102]

[0121] The Long Term Evolution (LTE) Positioning Protocol (LPP) is used point-to-point between a location server (e.g., LMF 270) and a target device (e.g., UE) to position the target device using location-related measurements obtained by one or more reference sources (physical entities or parts of physical entities that provide signals that can be measured by the target device to obtain its location). An LPP session is used between the location server and the target device to obtain location-related measurements or location estimates or to transfer assistance data. Currently, a single LPP session is used to support a single location request, and multiple LPP sessions may be used between the same endpoints to support multiple different location requests. Each LPP session includes one or more LPP transactions (or procedures), and each LPP transaction performs a single operation (capability exchange, assistance data transfer, or location information transfer). Each LPP transaction includes the exchange of one or more LPP messages between the location server and the target device.

[0103]

[0122] An LPP session generally includes at least a capability transfer or instruction procedure, an assistance data transfer or distribution procedure, and a location information transfer or distribution procedure. Figure 5 illustrates exemplary LPP capability transfer procedure 510, LPP assistance data transfer procedure 530, and LPP location information transfer procedure 550 between a target device (labeled "target") and a location server (labeled "server") according to aspects of the present disclosure.

[0104]

[0123] The purpose of the LPP Capability Transfer procedure 510 is to enable the transfer of capabilities from a target device (e.g., UE 204) to a location server (e.g., LMF 270). Capabilities in this context refer to positioning capabilities and protocol capabilities related to LPP and the positioning methods supported by LPP. In the LPP Capability Transfer procedure 510, the location server (e.g., LMF 270) indicates the types of capabilities required from the target device (e.g., UE 204) in an LPP Capability Request message. The target device responds with an LPP Capability Provide message. The capabilities included in the LPP Capability Provide message must correspond to any capability types specified in the LPP Capability Request message. Specifically, for each positioning method for which a capability request is included in the LPP Capability Request message, if the target device supports this positioning method, the target device includes its capabilities for that supported positioning method in the LPP Capability Provide message. In the case of the LPP Capability Indication procedure, the target device provides unrequested capabilities (i.e., for which it has not received an LPP Capability Request message) to the location server in the LPP Capability Provide message.

[0105]

[0124] The purpose of the LPP Assistance Data Forwarding procedure 530 is to allow a target device to request assistance data from a location server to assist positioning and for the location server to forward the assistance data to the target device in the absence of a request. In the LPP Assistance Data Forwarding procedure 530, the target device sends an LPP Assistance Data Request message to the location server. The location server responds to the target device with an LPP Provide Assistance Data message containing the assistance data. The forwarded assistance data must match or be a subset of the assistance data requested in the LPP Assistance Data Request. The location server may also provide any unsolicited information that the server deems useful to the target device. The location server may also send one or more additional LPP Provide Assistance Data messages containing further assistance data to the target device. In the LPP Assistance Data Delivery procedure, the location server provides unsolicited assistance data necessary for positioning. Assistance data may be provided periodically or aperiodically.

[0106]

[0125] The purpose of the LPP Location Information Transfer procedure 550 is to allow a location server to request location measurement data and / or a location estimate from a target device, and for the target device to forward the location measurement data and / or a location estimate to the location server in the absence of a request. In the LPP Location Information Transfer procedure 550, the location server sends an LPP Location Information Request message to the target device to request location information, indicating the type of location information required and, in some cases, the associated QoS. The target device responds to the location server with an LPP Provide Location Information message to forward the location information. The forwarded location information must match or be a subset of the location information requested by the LPP Location Information Request, unless the location server explicitly allows additional location information. More specifically, if the requested information is compatible with the capabilities and configuration of the target device, the target device includes the requested information in the LPP Provide Location Information message. Otherwise, if the target device does not support one or more of the requested positioning methods, the target device continues to process the message as if it contained information only for supported positioning methods and handles the signaling content of unsupported positioning methods with LPP error detection. If requested by the LPP Lactation Information Request message, the target device sends additional LPP Provide Location Information messages to the location server to transfer additional location information. The LPP Location Information Delivery procedure supports the delivery of positioning estimates based on unsolicited services.

[0107]

[0126] Various frame structures may be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). Figure 6 is a diagram 600 illustrating example frame structures according to aspects of the present disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.

[0108]

[0127] LTE, and in some cases NR, utilizes orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option of using OFDM on the uplink. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. Generally, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, or the total number of subcarriers (K) may depend on the system bandwidth. For example, the subcarrier spacing may be 15 kilohertz (kHz), and the minimum resource allocation (resource block) may be 12 subcarriers (i.e., 180 kHz). Thus, the nominal fast Fourier transform (FFT) size may be equal to 128, 256, 512, 1024, or 2048 for a system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0109]

[0128] LTE supports a single numerology (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR may support multiple numerologies (μ), e.g., subcarrier spacings of 15 kHz (μ=0), 30 kHz (μ=1), 60 kHz (μ=2), 120 kHz (μ=3), and 240 kHz (μ=4) or greater may be available. At each subcarrier spacing, there are 14 symbols per slot. For a 15 kHz SCS (μ=0), there is one slot per subframe, 10 slots per frame, a slot duration of 1 ms, a symbol duration of 66.7 microseconds (μs), and a maximum nominal system bandwidth (in MHz) of 50 with an FFT size of 4K. For a 30 kHz SCS (μ=1), there are two slots per subframe, 20 slots per frame, a slot duration of 0.5 ms, a symbol duration of 33.3 μs, and a maximum nominal system bandwidth (in MHz) of 100 for a 4K FFT size. For a 60 kHz SCS (μ=2), there are four slots per subframe, 40 slots per frame, a slot duration of 0.25 ms, a symbol duration of 16.7 μs, and a maximum nominal system bandwidth (in MHz) of 200 for a 4K FFT size. For a 120 kHz SCS (μ=3), there are eight slots per subframe, 80 slots per frame, a slot duration of 0.125 ms, a symbol duration of 8.33 μs, and a maximum nominal system bandwidth (in MHz) of 400 for a 4K FFT size. For a 240 kHz SCS (μ=4), there are 16 slots per subframe, 160 slots per frame, slot duration is 0.0625 ms, symbol duration is 4.17 μs, and the maximum nominal system bandwidth (in MHz) with an FFT size of 4K is 800.

[0110]

[0129] In the example of Figure 6, a 15 kHz numerology is used. Thus, in the time domain, a 10 ms frame is divided into 10 equally sized subframes of 1 ms each, with each subframe containing one time slot. In Figure 6, time is represented horizontally (X-axis), with time increasing from left to right, and frequency is represented vertically (Y-axis), with frequency increasing (or decreasing) from bottom to top.

[0111]

[0130] A resource grid may be used to represent a time slot, and each time slot includes one or more time-parallel resource blocks (RBs) (also called physical RBs, PRBs) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In the numerology of FIG. 6, for a normal cyclic prefix, an RB may include 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB may include 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0112]

[0131] Some of the REs may carry reference (pilot) signals (RS). The reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSBs), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communications. Figure 6 shows example locations of REs carrying reference signals (labeled "R").

[0113]

[0132] A set of resource elements (REs) used to transmit a PRS is called a "PRS resource." A set of resource elements can span multiple PRBs in the frequency domain and "N" consecutive symbol(s) within a slot (e.g., one or more) in the time domain. In a given OFDM symbol in the time domain, a PRS resource occupies consecutive PRBs in the frequency domain.

[0114]

[0133] The transmission of PRS resources within a given PRB has a particular comb size (also called "comb density"). The comb size "N" represents the subcarrier spacing (or frequency / tone spacing) within each symbol of the PRS resource configuration. Specifically, for comb size "N," a PRS is transmitted in every N subcarriers of the PRB symbol. For example, for comb 4, REs corresponding to every four subcarriers (e.g., subcarriers 0, 4, 8) are used to transmit the PRS in the PRS resource for each symbol of the PRS resource configuration. Currently, comb sizes of comb 2, comb 4, comb 6, and comb 12 are supported for DL-PRS. Figure 6 shows an example PRS resource configuration for comb 4 (spanning four symbols). That is, the location of the shaded REs (labeled "R") indicates the comb 4 PRS resource configuration.

[0115]

[0134] Currently, DL-PRS resources can span 2, 4, 6, or 12 consecutive symbols within a slot with a staggered pattern across the frequency domain. DL-PRS resources can be configured within any higher layer configured downlink or flexible (FL) symbols of a slot. There can be a constant energy per resource element (EPRE) for all REs of a given DL-PRS resource. Below are the symbol-to-symbol frequency offsets for comb sizes 2, 4, 6, and 12 across 2, 4, 6, and 12 symbols: 2-symbol comb2: {0,1}, 4-symbol comb2: {0,1,0,1}, 6-symbol comb2: {0,1,0,1,0,1}, 12-symbol comb2: {0,1,0,1,0,1,0,1,0,1,0,1} (for the example in Figure 6), 4-symbol comb4: {0,2,1,3}, 12-symbol comb4: {0,2,1,3,0,2,1,3,0,2,1,3}, 6-symbol comb6: {0,3,1,4,2,5}, 12-symbol comb6: {0,3,1,4,2,5,0,3,1,4,2,5}, and 12-symbol comb12: {0,6,3,9,1,7,4,10,2,8,5,11}.

[0116]

[0135] A "PRS resource set" is a set of PRS resources used to transmit PRS signals, where each PRS resource has a PRS resource ID. In addition, PRS resources within 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 TRP ID). In addition, PRS resources within a PRS resource set have the same periodicity across slots, a common muting pattern configuration, and the same repetition factor (e.g., "PRS-ResourceRepetitionFactor"). Periodicity is the time from the first repetition of the first PRS resource of the first PRS instance to the same first repetition of the same first PRS resource of the next PRS instance. The periodicity is μ = 0, 1, 2, 3, where μ is the number of PRS resources in a PRS resource set that are equal to or less than 2^μ. * The repetition factor may have a length selected from {1, 2, 4, 6, 8, 16, 32} slots.

[0117]

[0136] A PRS resource ID in a PRS resource set is associated with a single beam (or beam ID) transmitted from a single TRP (where a TRP may transmit one or multiple beams). That is, each PRS resource in a PRS resource set may be transmitted on a different beam, and thus a "PRS resource" or simply a "resource" may also be referred to as a "beam." Note that this does not have any implications regarding whether the TRP and beam on which the PRS is transmitted are known to the UE.

[0118]

[0137] A "PRS instance" or "PRS occasion" is one instance of a periodically repeating time window (e.g., a group of one or more contiguous slots) during which a PRS is expected to be transmitted. A PRS occasion may also be referred to as a "PRS positioning occasion," "PRS positioning instance," "positioning occasion," "positioning instance," "positioning repetition," or simply an "occasion," "instance," or "repetition."

[0119]

[0138] A "positioning frequency layer" (also simply referred to as "frequency layer") is a collection of one or more PRS resource sets across one or more TRPs that have the same values ​​for certain parameters. In particular, a collection of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning that all numerologies supported for the physical downlink shared channel (PDSCH) are also supported for PRS), the same Point A, the same value of downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The Point A parameter takes the value of the parameter "ARFCN-ValueNR" (where "ARFCN" stands for "absolute radio-frequency channel number"), which is an identifier / code that specifies a pair of physical radio channels used for transmission and reception. The downlink PRS bandwidth may have a granularity of 4 PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs. Currently, up to four frequency layers are defined, and up to two PRS resource sets per TRP can be configured per frequency layer.

[0120]

[0139] The concept of a frequency layer is somewhat similar to that of a component carrier and bandwidth parts (BWPs), but differs in that a component carrier and BWP are used by one base station (or a macrocell base station and a small cell base station) to transmit a data channel, while a frequency layer is used by several (usually three or more) base stations to transmit PRS. A UE may indicate the number of frequency layers it can support when it transmits its positioning capabilities to the network, such as during an LTE Positioning Protocol (LPP) session. For example, the UE may indicate whether it can support one positioning frequency layer or four positioning frequency layers.

[0121]

[0140] It should be noted that the terms “positioning reference signal” and “PRS” generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms “positioning reference signal” and “PRS” can also refer to any type of reference signal that can be used for positioning, such as, but not limited to, PRS defined in LTE and NR, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc. Furthermore, the terms “positioning reference signal” and “PRS” can refer to downlink, uplink, or sidelink positioning reference signals, unless otherwise suggested by the context. When necessary to further distinguish between types of PRS, downlink positioning reference signals may be referred to as “DL-PRS,” uplink positioning reference signals (e.g., SRS for positioning, PTRS) may be referred to as “UL-PRS,” and sidelink positioning reference signals may be referred to as “SL-PRS.” Additionally, for signals that may be transmitted in the downlink, uplink, and / or sidelink (e.g., DMRS), "DL," "UL," or "SL" may be prepended to the signal to distinguish the direction. For example, "UL-DMRS" is different from "DL-DMRS."

[0122]

[0141] FIG. 7 is a diagram 700 illustrating example PRS configurations for two TRPs (labeled “TRP1” and “TRP2”) operating within the same positioning frequency layer (labeled “Positioning Frequency Layer 1”) in accordance with aspects of the present disclosure. For a positioning session, a UE may be provided with assistance data indicating the illustrated PRS configurations. In the example of FIG. 7, a first TRP (“TRP1”) is associated with (e.g., transmits) two PRS resource sets labeled “PRS Resource Set 1” and “PRS Resource Set 2,” and a second TRP (“TRP2”) is associated with one PRS resource set labeled “PRS Resource Set 3.” Each PRS resource set includes at least two PRS resources. Specifically, the first PRS resource set ("PRS resource set 1") includes PRS resources labeled "PRS resource 1" and "PRS resource 2," the second PRS resource set ("PRS resource set 2") includes PRS resources labeled "PRS resource 3" and "PRS resource 4," and the third PRS resource set ("PRS resource set 3") includes PRS resources labeled "PRS resource 5" and "PRS resource 6."

[0123]

[0142] The concept of a "beam" in NTN (e.g., for transmitting PRS) differs from the concept of a "beam" in NR FR2. FIG. 8 is a diagram 800 illustrating an example of a space vehicle 112 generating multiple transmit beams (labeled "B1," "B2," "B3," "B4," "B5," and "B6") toward multiple geographic regions (labeled "Region A," "Region B," and "Region C"). As shown in FIG. 8, a satellite or airborne vehicle, such as space vehicle 112, typically generates several beams (e.g., B1-B6) toward a given geographic area (e.g., Regions A, B, and C), and the footprints of these beams are typically elliptical in shape. The beam footprint may move on the Earth as the satellite or airborne vehicle moves in its orbit. Alternatively, the beam footprint may be Earth-fixed. In that case, a beam-pointing mechanism (mechanical or electronic steering) may be used to compensate for the motion of the satellite or airborne vehicle.

[0124]

[0143] Network operators may be mandated to cross-check the UE location reported by the UE to meet regulatory requirements regarding network-verified UE location (e.g., lawful interception, emergency calls, public warning systems, etc.). That is, network operators should be able to check the UE's reported location information and specify whether mechanisms are necessary to meet regulatory requirements, for example, by estimating the UE's location on the network side. Currently, to determine network-verified UE location, an NTN-enabled UE may report its GNSS location (because NTN-enabled UEs are required to have GNSS), and the network (e.g., a location server) verifies or refines the UE's GNSS report through NTN positioning techniques.

[0125]

[0144] 9 is a diagram 900 illustrating a further aspect of RSTD measurements between a reference transmission point (TP) and a neighboring transmission point (TP) according to an aspect of the disclosure. In the example of FIG. 9, time is represented horizontally, with each block representing a subframe (or slot). The target UE determines whether the start of a subframe (or slot) for a downlink reference signal (e.g., PRS) of a non-reference (or neighboring) transmission point occurs between T REF +N ms+nr-DL-PRS-ExpectedRSTD×4×Ts within a search window of size [-nr-DL-PRS-ExpectedRSTD-Uncertainty×R;nr-DL-PRS-ExpectedRSTD-Uncertainty×R] centered at . The parameters "nr-DL-PRS-ExpectedRSTD-Uncertainty" and "nr-DL-PRS-ExpectedRSTD" may be provided to the UE via the LPP assisted data transfer procedure 530. The parameter T REF is the reception time at the UE antenna connector of the beginning of the subframe (or slot) for the downlink reference signal (e.g., PRS) of the reference transmission point indicated in the assistance data. The parameter N is calculated based on the parameters "nr-DL-PRS-SFN0-Offset", "dl-PRS-Periodicity-and-ResourceSetSlotOffset", and "dl-PRS-ResourceSlotOffset". These parameters may also be provided to the UE via the LPP assistance data forwarding procedure 530. The resolution R is either Ts if all PRS resources are within FR2, or 4×Ts otherwise, where Ts=1 / (15000 * 2048) seconds. Currently, the maximum expected RSTD is 3841 × 4 × Ts = 0.5 ms. Furthermore, the search window (i.e., 2 × nr-DL-PRS-ExpectedRSTD-Uncertainty × R) has a maximum value of 246 × 4 × Ts = 32 μs for FR1.

[0126]

[0145] A problem with NR-based NTN positioning techniques, such as TDOA-based techniques, is the longer propagation delay (latency) between the NTN transmission point (e.g., SV112) and the UE. As mentioned above, the reporting range for RSTD measurements is [-0.5 ms, 0.5 ms]. That is, the RSTD measurement needs to be less than or equal to 1 ms (e.g., the duration of a subframe). However, in NTN scenarios, the RSTD measurement may be much larger than 1 ms due to the propagation delay between different NTN transmission points. Existing RSTD frameworks do not accommodate large values ​​such as RSTD, predicted RSTD, and RSTD uncertainty. FIG. 10 is a diagram 1000 illustrating example latencies for different positions of NTN transmission points (e.g., satellites) relative to the UE's location, according to an aspect of the present disclosure.

[0127]

[0146] Another problem with DL-TDOA techniques for NTN positioning is that the network may not have a precise a priori location estimate of the target UE. In terrestrial networks, the LMF (e.g., LMF270) can obtain at least the cell-level location of the UE by obtaining serving cell information through the ECID procedure. The uncertainty in the a priori location estimate is then directly converted into the value of the parameter "nr-DL-PRS-ExpectedRSTD-Uncertainty." Currently, the value of "nr-DL-PRS-ExpectedRSTD-Uncertainty" does not exceed 32 μs, or approximately 10 kilometers (km), for FR1. However, in NTN, the beam size is much larger than this. For example, depending on the orbit of the space vehicle, the beam diameter can range from 20 km to 250 km. Therefore, for NTN beams, the expected RSTD uncertainty can span multiple subframes.

[0128]

[0147] A PRS is a wideband reference signal. However, it may not be desirable for a UE to search for a wideband reference signal for a long duration (e.g., across multiple subframes), as may be necessary for TDOA-based NTN positioning. This is because processing a wideband reference signal requires a large buffer size and additional receiver complexity. Therefore, the present disclosure provides a two-part PRS. The first part (referred to herein as "Part A") of the PRS of the present disclosure may be narrowband, and the second part (referred to herein as "Part B") may be wideband. At a high level, a UE may first search for (i.e., attempt to detect and measure) the Part A PRS during a PRS search window. If the UE detects the Part A PRS, the UE then searches for the Part B PRS to determine a more accurate time-of-arrival estimate.

[0129]

[0148] FIG. 11 is a diagram 1100 illustrating an aspect of a two-part PRS according to an aspect of the disclosure. As shown in FIG. 11, narrowband PRS part A is transmitted, followed by wideband PRS part B. Wideband PRS part B may be transmitted after narrowband PRS part A by some amount of time gap. A location server (e.g., LMF 270) may signal configuration information (e.g., parameters) for PRS part A and PRS part B to the UE in the LPP assisted data transfer procedure 530. PRS part A configuration parameters may include time and frequency domain assignments, sequences, and time gaps. PRS part B configuration information (e.g., parameters) may similarly include time and frequency domain assignments, sequences, and time gaps (if not provided in the PRS part A configuration). Furthermore, PRS part A and PRS part B must be quasi-colocated. That is, PRS portion B must have the same spatial, Doppler, delay spread, and / or average delay QCL characteristics as PRS portion A.

[0130]

[0149] The UE may search (attempt to detect / measure) PRS portion A in all slots and / or subframes within the PRS search window. FIG. 12 is a diagram 1200 illustrating an aspect of RSTD measurements between a reference transmission point (TP) and a neighboring transmission point (TP) according to aspects of the present disclosure. In the example of FIG. 12, time is represented horizontally, with each block representing a subframe (or slot). As described above with reference to FIG. 9, the target UE may determine that the start of a subframe (or slot) for a downlink reference signal (e.g., PRS) of a neighboring transmission point occurs between T REF +N ms+nr-DL-PRS-ExpectedRSTD×4×Ts within a search window of size [-nr-DL-PRS-ExpectedRSTD-Uncertainty×R;nr-DL-PRS-ExpectedRSTD-Uncertainty×R] centered at . The parameters "nr-DL-PRS-ExpectedRSTD-Uncertainty" and "nr-DL-PRS-ExpectedRSTD" may be provided to the UE via the LPP assisted data transfer procedure 530. The parameter T REF , N, R, and Ts are the same as described above with reference to Figure 9. However, in contrast to Figure 9, the RSTD uncertainty may span multiple subframes, as shown in the example of Figure 12.

[0131]

[0150] FIG. 13 is a diagram 1300 illustrating example PRS configuration parameters (i.e., configuration information) that may be provided to a UE during an LPP assistance data transfer procedure 530, according to an aspect of the present disclosure. Specifically, FIG. 13 illustrates different fields and information elements (IEs) included within the "NR-DL-PRS-AssistanceData" information element (IE) as currently defined. The IE "NR-DL-PRS-AssistanceDataPerFreq" combines the per-TRP configuration (provided by the IE "NR-DL-PRS-AssistanceDataPerTRP") and the per-positioning frequency layer configuration (provided by the IE "NR-DL-PRS-PositioningFrequencyLayer"). The "dl-PRS-ResourceBandwidth" field within the "NR-DL-PRS-PositioningFrequencyLayer" IE specifies the number of PRBs allocated for DL-PRS resources (allocated DL-PRS bandwidth), in multiples of four PRBs. Currently, all DL-PRS resources in a DL-PRS resource set have the same bandwidth. Similarly, all DL-PRS resource sets belonging to the same positioning frequency layer (PFL) have the same DL-PRS bandwidth and starting PRB. An integer value of "1" corresponds to 24 PRBs, a value of "2" corresponds to 28 PRBs, a value of "3" corresponds to 32 PRBs, and so on.

[0132]

[0151] Currently, LPP does not support configuring a two-part PRS (e.g., PRS part A and PRS part B) as disclosed herein. This disclosure provides positioning frequency layer parameters that allow multiple parameter sets (e.g., point A, bandwidth, etc.) per TRP per frequency layer. The positioning frequency layer parameters may be different versions of the currently defined "NR-DL-PRS-PositioningFrequencyLayer" IE, as shown in Figure 14. In this case, configuring at least one PRS resource per TRP per positioning frequency layer for positioning may be sufficient.

[0133]

[0152] 14 is a diagram 1400 illustrating example PRS configuration parameters for supporting a two-part PRS, according to an aspect of the present disclosure. The illustrated PRS configuration parameters may be provided to the UE during the LPP assisted data transfer procedure 530. As shown in FIG. 14, the "NR-DL-PRS-PositioningFrequencyLayer" IE includes a PRS part A bandwidth parameter (e.g., "dl-PRS-PartA-ResourceBandwidth"), a PRS part A start PRB parameter (e.g., "dl-PRS-PartA-StartPRB"), a PRS part A point A parameter (e.g., "dl-PRS-PartA-PointA"), and a PRS part A comb size parameter (e.g., "dl-PRS-PartA-CombSizeN"). Similarly, the "NR-DL-PRS-PositioningFrequencyLayer" IE includes a PRS part B bandwidth parameter (e.g., "dl-PRS-PartB-ResourceBandwidth"), a PRS part B start PRB parameter (e.g., "dl-PRS-PartB-StartPRB"), a PRS part B point A parameter (e.g., "dl-PRS-PartB-PointA"), and a PRS part B comb size parameter (e.g., "dl-PRS-PartB-CombSizeN").

[0134]

[0153] There are different options for configuring PRS resources within the positioning frequency layer that allow for multiple PRS configurations (e.g., as shown in FIG. 14). As a first option, a two-part PRS may be defined by a single PRS resource identifier (ID). FIG. 15 is a diagram 1500 illustrating the same PRS resource ID (labeled "PRS Resource ID 1") within a PRS resource set (labeled "PRS Resource Set 1") in the positioning frequency layer (labeled "PFL 1") that defines both Part A and Part B of a two-part PRS, in accordance with aspects of the present disclosure.

[0135]

[0154] 16 is a diagram 1600 illustrating example PRS configuration parameters that may be defined for a PRS resource ID that defines both part A and part B of a two-part PRS, according to an aspect of the disclosure. These parameters may be defined within the "NR-DL-PRS-Info" IE (shown in FIGS. 13 and 14). As shown in FIG. 16, for the same PRS resource ID (e.g., "nr-DL-PRS-ResourceID"), PRS Part A and Part B may have different sequence IDs (e.g., "dl-PRS-PartA-SequenceID" and "dl-PRS-PartB-SequenceID"), different comb sizes and resource element offsets (e.g., "dl-PRS-PartA-CombSizeN-AndReOffset" and "dl-PRS-PartB-CombSizeN-AndReOffset"), different slot offsets (e.g., "dl-PRS-PartA-ResourceSlotOffset" and "dl-PRS-PartB-ResourceSlotOffset"), and different symbol offsets (e.g., "dl-PRS-PartA-ResourceSymbolOffset" and "dl-PRS-PartB-ResourceSymbolOffset"). The PRS resource configuration may further include a time gap between PRS Part A and Part B (e.g., "dl-PRS-PartA-PartB-TimeGap") as a multiple of slots, subframes, milliseconds, or the like. Also as shown, PRS Part A and Part B have the same QCL information (e.g., "dl-PRS-QCL-Info").

[0136]

[0155] As a second option for configuring PRS resources within a positioning frequency layer that allows for multiple PRS configurations (e.g., as shown in FIG. 14), the narrowband PRS (i.e., PRS portion A) and the wideband PRS (i.e., PRS portion B) may be allocated to two separate PRS resource sets. Within each resource set, at least one PRS resource per TRP is configured per positioning frequency layer. This option maintains the constraint that all PRS resources per PRS resource set have the same parameters. FIG. 17 is a diagram 1700 illustrating different PRS resource IDs (labeled "PRS Resource ID 1" and "PRS Resource ID 2") within different PRS resource sets (labeled "PRS Resource Set 1" and "PRS Resource Set 2") of the same positioning frequency layer (labeled "PFL 1") that define parts A and B of a two-part PRS, in accordance with an aspect of the present disclosure.

[0137]

[0156] In this option, the location server needs to ensure that the PRS resources of the two PRS resource sets have the same QCL relationship and repetition and muting patterns. The standard must allow two (or more) PRS resources to be quasi-colocated with respect to all QCL characteristics, or the PRS resources must be transmitted on the same antenna port. Currently, there is no such association. In this case, the signaling overhead can be reduced by linking the two PRS resources of different PRS resource sets, as described further below.

[0138]

[0157] Because the Part A and Part B PRS resources are in different PRS resource sets, the location server needs to link the Part A and Part B PRS resources from the two PRS resource sets (e.g., PRS resource set 1 and PRS resource set 2 in FIG. 17) and configure a time gap. This can be done by introducing a linkage parameter at the TRP level (e.g., in the “NR-DL-PRS-AssistanceDataPerTRP” IE shown in FIG. 14). FIG. 18 is a diagram 1800 illustrating example parameters that may be added to assistance data for a TRP (e.g., the “NR-DL-PRS-AssistanceDataPerTRP” IE) to enable two-part PRS across different PRS resource sets of the same positioning frequency layer, according to aspects of the present disclosure. As shown in FIG. 18, a separate PRS resource ID (for either Part A or Part B) can be added in the assistance data per transmission / reception point (TRP) along with a time gap (e.g., “dl-PRS-PartA-PartB-TimeGap”). In the example of Figure 18, the "NR-DL-PRS-AssistanceDataPerTRP" IE includes a PRS resource ID for part A (e.g., "dl-PRS-PartA-ID"). This links the PRS ID for part A to the PRS ID for part B, which may be given by the parameter "dl-PRS-ID" in the example of Figure 18. However, as will be appreciated, the parameter "dl-PRS-ID" may also be for PRS part A and the additional PRS ID may be for PRS part B.

[0139]

[0158] Furthermore, if an additional PRS ID (e.g., "dl-PRS-PartA-ID") is present, the UE may assume that Part A and Part B PRS resources have the same QCL relationship, repetition, and muting pattern. In this case, at least for one PRS resource, these configurations do not need to be signaled redundantly. That is, these parameters may appear in only one "nr-DL-PRS-Info" IE.

[0140]

[0159] It will be appreciated that while the above describes the use of a two-part PRS for RSTD measurements, the two-part PRS may be used for any other type of positioning measurements, such as ToA, RSRP, AoA, Rx-Tx time difference, etc. Additionally, while the above generally describes the two-part PRS as being transmitted by a space vehicle, it will be appreciated that any type of transmission point may transmit the two-part PRS.

[0141]

[0160] 19 illustrates an example method 1900 of wireless communication according to an aspect of the present disclosure. In one aspect, the method 1900 may be performed by a UE (e.g., any of the UEs described herein).

[0142]

[0161] At 1910, the UE receives configuration information for a two-part PRS transmitted by a transmission point (e.g., SV112), the two-part PRS including a first part PRS (e.g., PRS portion A) and a second part PRS (e.g., PRS portion B) separated by a time gap. In one aspect, operation 1910 may be performed by one or more WWAN transceivers 310, one or more processors 332, memories 340, and / or positioning components 342, any or all of which may be considered a means for performing this operation.

[0143]

[0162] At 1920, the UE attempts to detect the first partial PRS based on the configuration information. In one aspect, operation 1920 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered a means for performing this operation.

[0144]

[0163] At 1930, the UE obtains positioning measurements for the second partial PRS based on the detection and configuration information for the first partial PRS. In one aspect, operation 1930 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered a means for performing this operation.

[0145]

[0164] As can be appreciated, a technical advantage of method 1900 is that it reduces the complexity at the UE side required to search for and measure a second-part PRS (e.g., a wideband PRS). More specifically, because the uncertainty window can be larger, the UE needs to perform a blind search for the wideband PRS over multiple slots (generally over a longer duration). This increases the UE's complexity (e.g., power consumption, processing power) because the UE receiver is operating at a larger bandwidth for a longer period of time. In addition, the UE needs to buffer more time-domain samples, which uses more L1 memory. Using a two-part PRS mitigates these issues while maintaining positioning accuracy.

[0146]

[0165] In the above detailed description, it can be seen that various features are grouped together in each example. This manner of disclosure should not be understood as an intention that the exemplary clauses have more features than are expressly stated in each clause. Rather, various aspects of the present disclosure may include fewer than all features of each disclosed exemplary clause. Accordingly, the following clauses should be considered incorporated into the description, and each clause may stand alone as a separate example. Although each dependent clause may refer to a specific combination with one of the other clauses within that clause, the aspect(s) of that dependent clause are not limited to that specific combination. It will be understood that other exemplary clauses may also include combinations of the aspect(s) of the dependent clause with the subject matter of any other dependent clause or independent clause, or any combination of features with other dependent clauses and independent clauses. The various aspects disclosed herein expressly include specific combinations (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor) unless such combinations are expressly expressed or can be readily inferred. It is further contemplated that aspects of a clause may be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

[0147]

[0166] Example implementations are described in the following numbered clauses.

[0148]

[0167] Clause 1. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving configuration information for a two-part positioning reference signal (PRS) transmitted by a transmission point, the two-part PRS including a first part PRS and a second part PRS separated by a time gap; attempting to detect the first part PRS based on the configuration information; and obtaining positioning measurements of the second part PRS based on the detection of the first part PRS and the configuration information.

[0149]

[0168] Clause 2. The method of clause 1, wherein attempting to detect the first partial PRS based on the configuration information includes attempting to detect the first partial PRS during a PRS search window defined by an expected reference signal time difference (RSTD) parameter and an expected RSTD uncertainty parameter indicated in the configuration information.

[0150]

[0169] Clause 3. The method of clause 2, wherein the PRS search window spans multiple slots or subframes.

[0151]

[0170] Clause 4. The method of any one of clauses 1 to 3, wherein the first partial PRS and the second partial PRS have the same quasi-collocation (QCL) relationship.

[0152]

[0171] Clause 5. The method of any one of clauses 1 to 4, wherein the configuration information includes one or more parameters defining a positioning frequency layer on which both the first partial PRS and the second partial PRS are transmitted.

[0153]

[0172] Clause 6. The method of clause 5, wherein the one or more parameters defining the positioning frequency layer include a first bandwidth for the first partial PRS and a second bandwidth for the second partial PRS, a first starting physical resource block (PRB) for the first partial PRS and a second starting PRB for the second partial PRS, a first point A for the first partial PRS and a second point A for the second partial PRS, a first comb size for the first partial PRS and a second comb size for the second partial PRS, or any combination thereof.

[0154]

[0173] Clause 7. The method of clause 5 or 6, wherein the configuration information includes one or more parameters defining PRS resources in the positioning frequency layer for the two-part PRS, and the one or more parameters defining the PRS resources include a first sequence identifier (ID) for the first partial PRS and a second sequence ID for the second partial PRS, a first comb size and resource element offset for the first partial PRS and a second comb size and resource element offset for the second partial PRS, a first resource slot offset for the first partial PRS and a second resource slot offset for the second partial PRS, or any combination thereof.

[0155]

[0174] Clause 8. The method of any one of clauses 5 to 7, wherein the configuration information includes one or more parameters defining a first PRS resource set in a positioning frequency layer for a first partial PRS and a second PRS resource set in a positioning frequency layer for a second partial PRS, wherein the first PRS resource in the first PRS resource set is configured as the first partial PRS and the second PRS resource in the second PRS resource set is configured as the second partial PRS.

[0156]

[0175] Clause 9. The method of clause 8, wherein the first PRS resource and the second PRS resource have the same quasi-co-location (QCL) relationship, the first PRS resource and the second PRS resource have the same antenna port, or any combination thereof.

[0157]

[0176] Clause 10. The method of clause 8 or 9, wherein the configuration information includes one or more parameters linking the first PRS resource and the second PRS resource.

[0158]

[0177] Clause 11. The method of clause 10, wherein the one or more parameters linking the first PRS resource and the second PRS resource include a first identifier of the first PRS resource within a set of parameters per transmission / reception point (TRP) in the configuration information, a second identifier of the second PRS resource within a set of parameters per TRP in the configuration information, or any combination thereof.

[0159]

[0178] Clause 12. The method of clause 10 or 11, wherein the configuration information includes a QCL relationship for only the first PRS resource or the second PRS resource, a repetition pattern for only the first PRS resource or the second PRS resource, a muting pattern for only the first PRS resource or the second PRS resource, or any combination thereof.

[0160]

[0179] Clause 13. The method of any one of clauses 1 to 12, wherein the configuration information includes a parameter indicating a time gap.

[0161]

[0180] Clause 14. The method of clause 13, wherein the parameter indicating the time gap has a value of a number of slots, subframes, or milliseconds.

[0162]

[0181] Clause 15. The method of any one of clauses 1 to 14, wherein the first part PRS comprises a narrowband PRS and the second part PRS comprises a wideband PRS.

[0163]

[0182] Clause 16. The method of any one of clauses 1 to 15, wherein the configuration information includes one or more Long Term Evolution (LTE) Positioning Protocol (LPP) information elements.

[0164]

[0183] Clause 17. The method of any one of clauses 1 to 16, wherein the positioning measurements include RSTD measurements, receive-to-transmit (Rx-Tx) time difference measurements, time of arrival (ToA) measurements, or reference signal received power (RSRP) measurements.

[0165]

[0184] Clause 18. A user equipment (UE), comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: receive, via the at least one transceiver, configuration information for a two-part positioning reference signal (PRS) transmitted by a transmission point, the two-part PRS including a first part PRS and a second part PRS separated by a time gap; attempt to detect the first part PRS based on the configuration information; and obtain positioning measurements for the second part PRS based on the detection of the first part PRS and the configuration information.

[0166]

[0185] Clause 19. The UE of Clause 18, wherein the at least one processor being configured to attempt to detect the first partial PRS based on the configuration information includes the at least one processor being configured to attempt to detect the first partial PRS during a PRS search window defined by an expected reference signal time difference (RSTD) parameter and an expected RSTD uncertainty parameter indicated in the configuration information.

[0167]

[0186] Clause 20. The UE of clause 19, wherein the PRS search window spans multiple slots or subframes.

[0168]

[0187] Clause 21. The UE of any one of clauses 18 to 20, wherein the first partial PRS and the second partial PRS have the same quasi-collocation (QCL) relationship.

[0169]

[0188] Clause 22. A UE as described in any one of clauses 18 to 21, wherein the configuration information includes one or more parameters defining a positioning frequency layer on which both the first partial PRS and the second partial PRS are transmitted.

[0170]

[0189] Clause 23. The UE of Clause 22, wherein the one or more parameters defining the positioning frequency layer include a first bandwidth for the first partial PRS and a second bandwidth for the second partial PRS, a first starting physical resource block (PRB) for the first partial PRS and a second starting PRB for the second partial PRS, a first point A for the first partial PRS and a second point A for the second partial PRS, a first comb size for the first partial PRS and a second comb size for the second partial PRS, or any combination thereof.

[0171]

[0190] Clause 24. The UE of Clause 22 or 23, wherein the configuration information includes one or more parameters defining PRS resources in the positioning frequency layer for the two-part PRS, and the one or more parameters defining the PRS resources include a first sequence identifier (ID) for the first partial PRS and a second sequence ID for the second partial PRS, a first comb size and resource element offset for the first partial PRS and a second comb size and resource element offset for the second partial PRS, a first resource slot offset for the first partial PRS and a second resource slot offset for the second partial PRS, or any combination thereof.

[0172]

[0191] Clause 25. A UE as described in any one of clauses 22 to 24, wherein the configuration information includes one or more parameters defining a first PRS resource set in a positioning frequency layer for a first partial PRS and a second PRS resource set in a positioning frequency layer for a second partial PRS, wherein the first PRS resource in the first PRS resource set is configured as the first partial PRS and the second PRS resource in the second PRS resource set is configured as the second partial PRS.

[0173]

[0192] Clause 26. The UE of clause 25, wherein the first PRS resource and the second PRS resource have the same quasi-co-location (QCL) relationship, the first PRS resource and the second PRS resource have the same antenna port, or any combination thereof.

[0174]

[0193] Clause 27. The UE of clause 25 or 26, wherein the configuration information includes one or more parameters linking the first PRS resource and the second PRS resource.

[0175]

[0194] Clause 28. The UE of Clause 27, wherein the one or more parameters linking the first PRS resource and the second PRS resource include a first identifier of the first PRS resource within a set of parameters per transmission / reception point (TRP) in the configuration information, a second identifier of the second PRS resource within a set of parameters per TRP in the configuration information, or any combination thereof.

[0176]

[0195] Clause 29. The UE of clause 27 or 28, wherein the configuration information includes a QCL relationship for only the first PRS resource or the second PRS resource, a recurrence pattern for only the first PRS resource or the second PRS resource, a muting pattern for only the first PRS resource or the second PRS resource, or any combination thereof.

[0177]

[0196] Clause 30. The UE of any one of clauses 18 to 29, wherein the configuration information includes a parameter indicating a time gap.

[0178]

[0197] Clause 31. The UE of clause 30, wherein the parameter indicating the time gap has a value of a number of slots, subframes, or milliseconds.

[0179]

[0198] Clause 32. The UE of any one of clauses 18 to 31, wherein the first portion PRS includes a narrowband PRS and the second portion PRS includes a wideband PRS.

[0180]

[0199] Clause 33. The UE of any one of clauses 18 to 32, wherein the configuration information includes one or more Long Term Evolution (LTE) Positioning Protocol (LPP) information elements.

[0181]

[0200] Clause 34. The UE of any one of clauses 18 to 33, wherein the positioning measurements include an RSTD measurement, a receive-to-transmit (Rx-Tx) time difference measurement, a time of arrival (ToA) measurement, or a reference signal received power (RSRP) measurement.

[0182]

[0201] Clause 35. A user equipment (UE), comprising: means for receiving configuration information for a two-part positioning reference signal (PRS) transmitted by a transmission point, the two-part PRS including a first part PRS and a second part PRS separated by a time gap; means for attempting to detect the first part PRS based on the configuration information; and means for obtaining positioning measurements of the second part PRS based on the detection of the first part PRS and the configuration information.

[0183]

[0202] Clause 36. The UE of clause 35, wherein the means for attempting to detect the first partial PRS based on the configuration information includes means for attempting to detect the first partial PRS during a PRS search window defined by an expected reference signal time difference (RSTD) parameter and an expected RSTD uncertainty parameter indicated in the configuration information.

[0184]

[0203] Clause 37. The UE of clause 36, wherein the PRS search window spans multiple slots or subframes.

[0185]

[0204] Clause 38. The UE of any one of clauses 35 to 37, wherein the first partial PRS and the second partial PRS have the same quasi-collocation (QCL) relationship.

[0186]

[0205] Clause 39. The UE of any one of clauses 35 to 38, wherein the configuration information includes one or more parameters defining a positioning frequency layer on which both the first partial PRS and the second partial PRS are transmitted.

[0187]

[0206] Clause 40. The UE of Clause 39, wherein the one or more parameters defining the positioning frequency layer include a first bandwidth for the first partial PRS and a second bandwidth for the second partial PRS, a first starting physical resource block (PRB) for the first partial PRS and a second starting PRB for the second partial PRS, a first point A for the first partial PRS and a second point A for the second partial PRS, a first comb size for the first partial PRS and a second comb size for the second partial PRS, or any combination thereof.

[0188]

[0207] Clause 41. The UE of Clause 39 or 40, wherein the configuration information includes one or more parameters defining PRS resources in the positioning frequency layer for the two-part PRS, and the one or more parameters defining the PRS resources include a first sequence identifier (ID) for the first part PRS and a second sequence ID for the second part PRS, a first comb size and resource element offset for the first part PRS and a second comb size and resource element offset for the second part PRS, a first resource slot offset for the first part PRS and a second resource slot offset for the second part PRS, or any combination thereof.

[0189]

[0208] Clause 42. A UE as described in any one of clauses 39 to 41, wherein the configuration information includes one or more parameters defining a first PRS resource set in a positioning frequency layer for a first partial PRS and a second PRS resource set in a positioning frequency layer for a second partial PRS, wherein the first PRS resource in the first PRS resource set is configured as the first partial PRS and the second PRS resource in the second PRS resource set is configured as the second partial PRS.

[0190]

[0209] Clause 43. The UE of clause 42, wherein the first PRS resource and the second PRS resource have the same quasi-co-location (QCL) relationship, the first PRS resource and the second PRS resource have the same antenna port, or any combination thereof.

[0191]

[0210] Clause 44. The UE of clause 42 or 43, wherein the configuration information includes one or more parameters linking the first PRS resource and the second PRS resource.

[0192]

[0211] Clause 45. The UE of Clause 44, wherein the one or more parameters linking the first PRS resource and the second PRS resource include a first identifier of the first PRS resource within a set of parameters per transmission / reception point (TRP) in the configuration information, a second identifier of the second PRS resource within a set of parameters per TRP in the configuration information, or any combination thereof.

[0193]

[0212] Clause 46. The UE of clause 44 or 45, wherein the configuration information includes a QCL relationship for only the first PRS resource or the second PRS resource, a recurrence pattern for only the first PRS resource or the second PRS resource, a muting pattern for only the first PRS resource or the second PRS resource, or any combination thereof.

[0194]

[0213] Clause 47. The UE of any one of clauses 35 to 46, wherein the configuration information includes a parameter indicating a time gap.

[0195]

[0214] Clause 48. The UE of clause 47, wherein the parameter indicating the time gap has a value of a number of slots, subframes, or milliseconds.

[0196]

[0215] Clause 49. The UE of any one of clauses 35 to 48, wherein the first portion PRS comprises a narrowband PRS and the second portion PRS comprises a wideband PRS.

[0197]

[0216] Clause 50. The UE of any one of clauses 35 to 49, wherein the configuration information includes one or more Long Term Evolution (LTE) Positioning Protocol (LPP) information elements.

[0198]

[0217] Clause 51. The UE of any one of clauses 35 to 50, wherein the positioning measurements include an RSTD measurement, a receive-to-transmit (Rx-Tx) time difference measurement, a time of arrival (ToA) measurement, or a reference signal received power (RSRP) measurement.

[0199]

[0218] Clause 52. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to receive configuration information for a two-part positioning reference signal (PRS) transmitted by a transmission point, the two-part PRS including a first part PRS and a second part PRS separated by a time gap, attempt to detect the first part PRS based on the configuration information, and obtain positioning measurements for the second part PRS based on the detection of the first part PRS and the configuration information.

[0200]

[0219] Clause 53. A non-transitory computer-readable medium as described in Clause 52, comprising computer-executable instructions that, when executed by a UE, cause the UE to attempt to detect a first partial PRS based on configuration information, and that, when executed by the UE, cause the UE to attempt to detect a first partial PRS during a PRS search window defined by an expected reference signal time difference (RSTD) parameter and an expected RSTD uncertainty parameter indicated in the configuration information.

[0201]

[0220] Clause 54. The non-transitory computer-readable medium of clause 53, wherein the PRS search window spans multiple slots or subframes.

[0202]

[0221] Clause 55. The non-transitory computer-readable medium of any one of clauses 52 to 54, wherein the first partial PRS and the second partial PRS have the same quasi-collocation (QCL) relationship.

[0203]

[0222] Clause 56. A non-transitory computer-readable medium according to any one of clauses 52 to 55, wherein the configuration information includes one or more parameters defining a positioning frequency layer on which both the first partial PRS and the second partial PRS are transmitted.

[0204]

[0223] Clause 57. The non-transitory computer-readable medium of Clause 56, wherein the one or more parameters defining the positioning frequency layer include a first bandwidth for the first partial PRS and a second bandwidth for the second partial PRS, a first starting physical resource block (PRB) for the first partial PRS and a second starting PRB for the second partial PRS, a first point A for the first partial PRS and a second point A for the second partial PRS, a first comb size for the first partial PRS and a second comb size for the second partial PRS, or any combination thereof.

[0205]

[0224] Clause 58. The non-transitory computer-readable medium of Clause 56 or 57, wherein the configuration information includes one or more parameters defining PRS resources in the positioning frequency layer for the two-part PRS, and the one or more parameters defining the PRS resources include a first sequence identifier (ID) for the first partial PRS and a second sequence ID for the second partial PRS, a first comb size and resource element offset for the first partial PRS and a second comb size and resource element offset for the second partial PRS, a first resource slot offset for the first partial PRS and a second resource slot offset for the second partial PRS, or any combination thereof.

[0206]

[0225] Clause 59. A non-transitory computer-readable medium as described in any one of clauses 56 to 58, wherein the configuration information includes one or more parameters defining a first PRS resource set in a positioning frequency layer for a first partial PRS and a second PRS resource set in a positioning frequency layer for a second partial PRS, wherein the first PRS resource in the first PRS resource set is configured as the first partial PRS and the second PRS resource in the second PRS resource set is configured as the second partial PRS.

[0207]

[0226] Clause 60. The non-transitory computer-readable medium of Clause 59, wherein the first PRS resource and the second PRS resource have the same quasi-co-location (QCL) relationship, the first PRS resource and the second PRS resource have the same antenna port, or any combination thereof.

[0208]

[0227] Clause 61. The non-transitory computer-readable medium of clause 59 or 60, wherein the configuration information includes one or more parameters that link the first PRS resource and the second PRS resource.

[0209]

[0228] Clause 62. The non-transitory computer-readable medium of Clause 61, wherein the one or more parameters linking the first PRS resource and the second PRS resource include a first identifier of the first PRS resource within a set of parameters per transmitting / receiving point (TRP) in the configuration information, a second identifier of the second PRS resource within a set of parameters per TRP in the configuration information, or any combination thereof.

[0210]

[0229] Clause 63. The non-transitory computer-readable medium of clause 61 or 62, wherein the configuration information includes a QCL relationship for only the first PRS resource or the second PRS resource, a repetition pattern for only the first PRS resource or the second PRS resource, a muting pattern for only the first PRS resource or the second PRS resource, or any combination thereof.

[0211]

[0230] Clause 64. The non-transitory computer-readable medium of any one of clauses 52 to 63, wherein the configuration information includes a parameter indicating a time gap.

[0212]

[0231] Clause 65. The non-transitory computer-readable medium of clause 64, wherein the parameter indicating the time gap has a value of a number of slots, subframes, or milliseconds.

[0213]

[0232] Clause 66. The non-transitory computer-readable medium of any one of clauses 52-65, wherein the first portion PRS comprises a narrowband PRS and the second portion PRS comprises a wideband PRS.

[0214]

[0233] Clause 67. The non-transitory computer-readable medium of any one of clauses 52 to 66, wherein the configuration information includes one or more Long Term Evolution (LTE) Positioning Protocol (LPP) information elements.

[0215]

[0234] Clause 68. The non-transitory computer-readable medium of any one of clauses 52 to 67, wherein the positioning measurements include RSTD measurements, receive-to-transmit (Rx-Tx) time difference measurements, time of arrival (ToA) measurements, or reference signal received power (RSRP) measurements.

[0216]

[0235] Those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0217]

[0236] Furthermore, those skilled in the art will understand that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0218]

[0237] The various example logic blocks, modules, and circuits described in connection with aspects disclosed herein may be implemented or performed using a general-purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0219]

[0238] The methods, sequences, and / or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). Alternatively, the processor and the storage medium may reside as discrete components in the user terminal.

[0220]

[0239] In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code. Computer-readable media includes both computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Storage media may be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of medium. As used herein, disk and disc include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically and discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0221]

[0240] While the above disclosure illustrates exemplary aspects of the present disclosure, it should be noted that various changes and modifications can be made herein without departing from the scope of the present disclosure, which is defined by the appended claims. The functions, steps, and / or actions of the method claims in accordance with the aspects of the present disclosure described herein need not be performed in any particular order. Furthermore, although elements of the present disclosure may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.

Claims

1. A method of wireless communication performed by user equipment (UE), Receiving configuration information for a two-part positioning reference signal (PRS) transmitted by a transmission point, wherein the two-part PRS includes a first-part PRS and a second-part PRS separated by a time gap, the configuration information includes one or more parameters defining a positioning frequency layer on which both the first-part PRS and the second-part PRS are transmitted, and the one or more parameters defining the positioning frequency layer include a first bandwidth for the first-part PRS and a second wider bandwidth for the second-part PRS. An attempt is made to detect the first partial PRS based on the aforementioned configuration information, The detection of the first partial PRS and the acquisition of positioning measurements of the second partial PRS based on the configuration information, Methods that include...

2. An attempt is made to detect the first partial PRS based on the aforementioned configuration information. This includes attempting to detect the first partial PRS during a PRS search window defined by the expected reference signal time difference (RSTD) parameter and the expected RSTD uncertainty parameter shown in the configuration information, and optionally, The method according to claim 1, wherein the PRS search window spans multiple slots or subframes.

3. The method according to claim 1, wherein the first partial PRS and the second partial PRS have the same quasi-collocation (QCL) relationship.

4. The one or more parameters that define the positioning frequency layer are, A first start physical resource block (PRB) for the first partial PRS and a second start PRB for the second partial PRS, The first point A for the first part PRS and the second point A for the second part PRS, A first comb size for the first part PRS and a second comb size for the second part PRS, or Any combination of those, The method according to claim 1, including the method described in claim 1.

5. The configuration information includes one or more parameters that define the PRS resources in the positioning frequency layer for the two-part PRS, The one or more parameters that define the PRS resource are, A first sequence identifier (ID) for the first partial PRS and a second sequence ID for the second partial PRS, A first comb size and resource element offset for the first partial PRS and a second comb size and resource element offset for the second partial PRS, A first resource slot offset for the first partial PRS and a second resource slot offset for the second partial PRS, or Any combination of those, The method according to claim 1, including the method described in claim 1.

6. The configuration information includes one or more parameters that define a first PRS resource set in the positioning frequency layer for the first partial PRS and a second PRS resource set in the positioning frequency layer for the second partial PRS, The first PRS resource within the first PRS resource set is configured as the first partial PRS, The method according to claim 1, wherein the second PRS resource in the second PRS resource set is configured as the second partial PRS.

7. The first PRS resource and the second PRS resource have the same quasi-collocation (QCL) relationship. The first PRS resource and the second PRS resource have the same antenna port, or The method according to claim 6, which is any combination thereof.

8. The configuration information includes one or more parameters that link the first PRS resource and the second PRS resource, optionally, The one or more parameters linking the first PRS resource and the second PRS resource are: The first identifier of the first PRS resource in the set of parameters for each transmit / receive point (TRP) in the configuration information, or The second identifier of the second PRS resource in the set of parameters for each TRP in the configuration information, or Any combination of those, including and / or, The above configuration information, QCL relationship for the first PRS resource or the second PRS resource only, A repeating pattern for the first PRS resource or the second PRS resource only, A muting pattern for the first PRS resource or the second PRS resource only, or Any combination of those, The method according to claim 6, including the method described in claim 6.

9. The method according to claim 1, wherein the configuration information includes a parameter indicating the time gap, and optionally the parameter indicating the time gap has a value of a plurality of slots, subframes, or milliseconds.

10. The first partial PRS includes a narrowband PRS, The method according to claim 1, wherein the second partial PRS includes a broadband PRS.

11. The method according to claim 1, wherein the configuration information includes one or more Long-Term Evolution (LTE) Positioning Protocol (LPP) information elements.

12. The method according to claim 1, wherein the positioning measurement includes an RSTD measurement, a (Rx-Tx) time difference measurement from reception to transmission, a time to arrival (ToA) measurement, or a reference signal received power (RSRP) measurement.

13. User equipment (UE), Memory and At least one transceiver, A processor that is communicatively coupled to the memory and the at least one transceiver, The transceiver receives configuration information for a two-part positioning reference signal (PRS) transmitted by a transmitting point, wherein the two-part PRS includes a first-part PRS and a second-part PRS separated by a time gap, and the configuration information includes one or more parameters defining a positioning frequency layer on which both the first-part PRS and the second-part PRS are transmitted, and the one or more parameters defining the positioning frequency layer include a first bandwidth for the first-part PRS and a second wider bandwidth for the second-part PRS. An attempt is made to detect the first partial PRS based on the aforementioned configuration information. The detection of the first partial PRS and the acquisition of positioning measurements of the second partial PRS based on the configuration information are performed. A system comprising at least one processor configured as follows: UE equipped with

14. The UE according to claim 13, further configured to perform the method described in any one of claims 2 to 12.

15. A non-temporary computer-readable medium for storing computer-executable instructions, wherein when the computer-executable instructions are executed by a user device (UE), the UE causes the UE to execute the method according to any one of claims 1 to 12.

Images