Positioning reference signal (PRS) timing offset

Abstract

Techniques for wireless communication are disclosed. In an aspect, a radio access network (RAN) node transmits a positioning reference signal (PRS) offset configuration to a location server, the PRS offset configuration indicating one or more parameters specifying at least a timing offset for one or more PRS resources transmitted by the RAN node, wherein the timing offset is relative to a PRS time offset point within a frame, subframe, or slot of the RAN node, wherein the PRS time offset point is configured to at least one user equipment (UE) to indicate a transmission time of the one or more PRS resources relative to a start of the frame, subframe, or slot; and transmitting the one or more PRS resources to the at least one UE according to at least the timing offset.

Description

BACKGROUND OF THE DISCLOSURE 1. FIELD OF THE TECHNOLOGY

[0001] Aspects of the present disclosure generally relate to wireless communication.

[0002] 2. Description of Related Technologies

[0003] Wireless communication systems have evolved through many generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including transitional 2.5G and 2.75G networks), third generation (3G) high-speed data, Internet-capable wireless services, and fourth generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). Currently, there are many different types of wireless communication systems in use, including cellular systems and Personal Communication Service (PCS) systems. Examples of known cellular systems include 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.

[0004] The fifth generation (5G) wireless standard, known as New Radio (NR), enables higher data transfer speeds, a greater number of connections, better coverage, and other improvements. According to the Next Generation Mobile Networks 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, along with the use of higher frequency bands, advancements in PRS processes and technologies, and high-density deployments of 5G enable high-precision positioning based on 5G. SUMMARY OF THE INVENTION

[0005] The following presents a simplified summary of one or more aspects related to the present disclosure. Accordingly, the following summary is not to be considered an exhaustive overview of all contemplated aspects, nor is it to be considered identifying key or critical elements of all contemplated aspects or delineating the scope associated with any particular aspect. Thus, the sole purpose of the following summary is to present certain concepts related to one or more aspects of the mechanisms disclosed herein in a simplified form prior to the detailed description that follows.

[0006] In one aspect, a method of wireless communication performed by a radio access network (RAN) node includes: sending a positioning reference signal (PRS) offset configuration to a location server, the PRS offset configuration indicating at least one or more parameters specifying a timing offset, a frequency offset, or both of one or more PRS resources transmitted by the RAN node, wherein the timing offset is relative to a PRS time offset point within a frame, subframe, or time slot of the RAN node, wherein the PRS time offset point is configured to at least one user equipment (UE) to indicate a transmission time of the one or more PRS resources relative to a start of the frame, subframe, or time slot, wherein the frequency offset is relative to a PRS frequency offset point within a frequency range of the RAN node, and wherein the PRS frequency offset point is configured to the at least one UE to indicate a transmission frequency of the one or more PRS resources relative to the frequency range of the RAN node; and transmitting the one or more PRS resources to the at least one UE based at least on the timing offset, the frequency offset, or both.

[0007] In one aspect, a radio access network (RAN) node includes: 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: send, via the at least one transceiver, a positioning reference signal (PRS) offset configuration to a location server, the PRS offset configuration indicating at least one or more parameters specifying a timing offset, a frequency offset, or both of one or more PRS resources transmitted by the RAN node, wherein the timing offset is relative to a PRS time offset point within a frame, subframe, or time slot of the RAN node, wherein the PRS time offset point is configured to at least one user equipment (UE) to indicate a transmission time of the one or more PRS resources relative to a start of the frame, subframe, or time slot, wherein the frequency offset is relative to a PRS frequency offset point within a frequency range of the RAN node, and wherein the PRS frequency offset point is configured to the at least one UE to indicate a transmission frequency of the one or more PRS resources relative to the frequency range of the RAN node; and transmit, via the at least one transceiver, the one or more PRS resources to the at least one UE based at least on the timing offset, the frequency offset, or both.

[0008] In one aspect, a radio access network (RAN) node includes: means for sending a positioning reference signal (PRS) offset configuration to a location server, the PRS offset configuration indicating at least one or more parameters specifying a timing offset, a frequency offset, or both, of one or more PRS resources transmitted by the RAN node, wherein the timing offset is relative to a PRS time offset point within a frame, subframe, or time slot of the RAN node, wherein the PRS time offset point is configured to at least one user equipment (UE) to indicate a transmission time of the one or more PRS resources relative to the start of the frame, subframe, or time slot, wherein the frequency offset is relative to a PRS frequency offset point within a frequency range of the RAN node, and wherein the PRS frequency offset point is configured to the at least one UE to indicate a transmission frequency of the one or more PRS resources relative to the frequency range of the RAN node; and means for transmitting the one or more PRS resources to the at least one UE at least based on the timing offset, the frequency offset, or both.

[0009] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a radio access network (RAN) node, cause the RAN node to: send a positioning reference signal (PRS) offset configuration to a location server, the PRS offset configuration indicating at least one or more parameters specifying a timing offset, a frequency offset, or both, of one or more PRS resources transmitted by the RAN node, wherein the timing offset is relative to a PRS time offset point within a frame, subframe, or time slot of the RAN node, wherein the PRS time offset point is configured to at least one user equipment (UE) to indicate a transmission time of the one or more PRS resources relative to the start of the frame, subframe, or time slot, wherein the frequency offset is relative to a PRS frequency offset point within a frequency range of the RAN node, and wherein the PRS frequency offset point is configured to the at least one UE to indicate a transmission frequency of the one or more PRS resources relative to the frequency range of the RAN node; and transmit the one or more PRS resources to the at least one UE at least based on the timing offset, the frequency offset, or both.

[0010] Based on the drawings and the detailed description, other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The drawings are presented to assist in describing various aspects of the present disclosure, and the drawings are provided for illustration only and not to limit the aspects.

[0012] Figure 1 An example wireless communication system in accordance with aspects of the present disclosure is illustrated.

[0013] Figure 2A , Figure 2B and Figure 2C illustrate example wireless network architectures in accordance with aspects of the present disclosure.

[0014] Figure 3A , Figure 3B and Figure 3C are simplified block diagrams of several example aspects of components that can be employed in a user equipment (UE), a base station, and a network entity, respectively, and are configured to support communications as taught herein.

[0015] Figure 4 illustrate examples of various positioning methods supported in New Radio (NR) in accordance with aspects of the present disclosure.

[0016] Figure 5 is a diagram illustrating an example frame structure in accordance with aspects of the present disclosure.

[0017] Figure 6 is a diagram of an example PRS configuration for PRS transmission for a given base station in accordance with aspects of the present disclosure.

[0018] Figure 7A is a diagram illustrating an example non-terrestrial network (NTN) scenario based on a transparent payload in accordance with aspects of the present disclosure.

[0019] Figure 7B is a diagram illustrating an example non-terrestrial network (NTN) scenario based on a regenerated payload in accordance with aspects of the present disclosure.

[0020] Figure 8 illustrates an example Long Term Evolution (LTE) Positioning Protocol (LPP) reference source for positioning.

[0021] Figure 9 is a diagram illustrating an example architecture suitable for positioning a UE using NR access in accordance with aspects of the present disclosure.

[0022] Figure 10 is a diagram illustrating other aspects of reference signal time difference (RSTD) measurements between a reference transmission point (TP) and an adjacent transmission point (TP) in accordance with aspects of the present disclosure.

[0023] Figure 11 illustrates an example method of wireless communication in accordance with aspects of the present disclosure. DETAILED DESCRIPTION

[0024] Aspects of the present disclosure are provided in the following description of various examples provided for illustrative purposes and the associated drawings. Alternative aspects can 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.

[0025] The terms "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 superior or better than other aspects. Similarly, 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.

[0026] Those skilled in the art will appreciate that any of a variety of different technologies and methods can be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the following description can be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof, in part depending on the particular application, in part depending on the desired design, in part depending on the corresponding technology, and so on.

[0027] Furthermore, many aspects are described in terms of a sequence of actions to be performed by, for example, elements of a computing device. It will be recognized that the various actions described herein can be performed by specific circuitry (e.g., an application specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of both. Additionally, the sequence of actions described herein can be regarded as fully embodied in any form of non-transitory computer-readable storage medium having stored therein a corresponding set of computer instructions that, when executed, cause or direct the associated processor of the device to perform the functionality described herein. Accordingly, the various aspects of the present disclosure can be embodied in many different forms, all of which have been contemplated within the scope of the claimed subject matter. Additionally, for each of the aspects described herein, the corresponding form of any such aspect can be described herein as, for example, "logic configured to perform the described actions".

[0028] As used herein, unless otherwise specified, the terms "user equipment" (UE) and "base station" are not intended to be specific or otherwise limited to any particular radio access technology (RAT). In general, a UE can be any wireless communication device used by a user to communicate via a wireless communication network (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a consumer asset tracking device, a wearable device (e.g., a smartwatch, glasses, an 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.). The UE can be mobile or can be stationary (e.g., at certain times) and can communicate with a radio access network (RAN). As used herein, the term "UE" can be interchangeably referred to as "access terminal" or "AT", "client device", "wireless device", "subscriber equipment", "subscriber terminal", "subscriber station", "user terminal" or "UT", "mobile device", "mobile terminal", "mobile station", or variants thereof. In general, the UE can communicate with a core network via the RAN, and through the core network, the UE can connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for the UE to connect to the core network and / or the Internet are possible, such as via a wired access network, a wireless local area network (WLAN) network (e.g., based on Institute of Electrical and Electronics Engineers (IEEE) 802.11 specifications, etc.).

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

[0030] The term "base station" can refer to a single physical transmit receive point (TRP) or multiple physical TRPs that may or may not be co-located. For example, in the case where the term "base station" refers to a single physical TRP, the physical TRP can be the antenna of the base station corresponding to the cell (or a number of cell sectors) of the base station. In the case where the term "base station" refers to multiple co-located physical TRPs, the physical TRP can be an antenna array of the base station (e.g., as in a multiple input multiple output (MIMO) system or when beamforming is employed at the base station). In the case where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP can be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRP can be the serving base station that receives measurement reports from the UE and an adjacent base station whose reference radio frequency (RF) signal the UE is measuring. Since, as used herein, a TRP is the point by which a base station transmits and receives wireless signals, a reference to transmission from or reception at a base station should be understood to refer to a particular TRP of the base station.

[0031] In some specific implementations that support UE positioning, a base station may not support wireless access for the UE (e.g., may not support data, voice, and / or signaling connections for the UE), but instead may send reference signals to be measured by the UE and / or may receive and measure signals sent by the UE. Such a base station can be referred to as a positioning beacon (e.g., in the case of sending signals to the UE) and / or as a position measurement unit (e.g., in the case of receiving and measuring signals from the UE).

[0032] An "RF signal" includes an electromagnetic wave of a given frequency that transmits information through the space between a transmitter and a receiver. As used herein, a transmitter may send a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through a multipath channel, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and the receiver can be referred to as a "multipath" RF signal. As used herein, when it is clear from the context that the term "signal" refers to a wireless signal or an RF signal, the RF signal can also be referred to as a "wireless signal" or simply as a "signal".

[0033] Figure 1An example wireless communication system 100 in accordance with aspects of the present disclosure is illustrated. The wireless communication system 100 (which may also be 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 macro cell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macro cell 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 femto cells, pico cells, micro cells, etc.

[0034] The base stations 102 may together form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) via a backhaul link 122, and interface with one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) via the core network 170. The location server 172 may be part of the core network 170 or may be external to the core network 170. The location server 172 may be integrated with the base stations 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 via the base station 102 currently serving the UE 104. The UE 104 may also communicate with the location server 172 via another path, such as via an application server (not shown), via another network, such as via a wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below), etc. For signaling purposes, the communication between the UE 104 and the location server 172 may be represented as an indirect connection (e.g., via the core network 170, etc.) or a direct connection (e.g., as shown via a direct connection 128), where intermediate nodes (if any) are omitted from the signaling diagram for clarity.

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

[0036] Base station 102 can communicate wirelessly with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographical coverage area 110. In one aspect, one or more cells can be supported by the base stations 102 in each geographical coverage area 110. A "cell" is a logical communication entity used to communicate with a base station (e.g., on a certain frequency resource, which is referred to as carrier frequency, component carrier, carrier, frequency band, etc.), and can be associated with an identifier used to distinguish cells operating via the same or different carrier frequencies (e.g., physical cell identifier (PCI), enhanced cell identifier (ECI), virtual cell identifier (VCI), cell global identifier (CGI), etc.). In some cases, different cells can be configured according to different protocol types that can provide access for different types of UEs (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types). Since a cell is supported by a specific base station, the term "cell" can, depending on the context, refer to either or both of the logical communication entity and the base station that supports it. In addition, since the TRP is typically the physical transmission point of a cell, the terms "cell" and "TRP" can be used interchangeably. In some cases, the term "cell" can also refer to the geographical coverage area of a base station (e.g., a sector), as long as the carrier frequency can be detected and used for communication within a certain part of the geographical coverage area 110.

[0037] Although the geographical coverage areas 110 of adjacent macro cell base stations 102 can partially overlap (e.g., in a handover area), some areas in the geographical coverage area 110 can substantially overlap with a larger geographical coverage area 110. For example, a small cell base station 102' (marked as "SC" for "small cell") can have a geographical coverage area 110' that substantially overlaps with the geographical coverage area 110 of one or more macro cell base stations 102. A network including both small cell base stations and macro cell base stations can be referred to as a heterogeneous network. The heterogeneous network can also include a home eNB (HeNB), which can provide services to a restricted group called a closed subscriber group (CSG).

[0038] The communication link 120 between base station 102 and UE 104 can include an uplink (also referred to as reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also referred to as forward link) transmission from base station 102 to UE 104. The communication link 120 can use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 can pass through one or more carrier frequencies. The allocation of carriers can be asymmetric for the downlink and uplink (e.g., more or fewer carriers can be allocated to the downlink compared to the uplink).

[0039] The wireless communication system 100 may also include a WLAN access point (AP) 150 that communicates with a wireless local area network (WLAN) station (STA) 152 via a communication link 154 in an unlicensed spectrum (e.g., 5 GHz). When communicating in the unlicensed spectrum, the WLAN STA 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 the channel is available.

[0040] The small cell base station 102' may operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell base station 102' may employ LTE or NR technologies and use the same 5 GHz unlicensed spectrum as that used by the WLAN AP 150. The small cell base station 102' that employs LTE / 5G in the unlicensed spectrum may enhance the coverage of the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum may be referred to as NR-U. LTE in the unlicensed spectrum may be referred to as LTE-U, Licensed-Assisted Access (LAA), or MulteFire.

[0041] The wireless communication system 100 may also include a millimeter wave (mmW) base station 180 that may operate at mmW frequencies and / or near-mmW frequencies to communicate with a UE 182. The Extremely High Frequency (EHF) is a part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. The radio waves in this band may be referred to as millimeter waves. Near-mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The Super High Frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using the mmW / near-mmW radio frequency bands have high path loss and relatively short distances. The mmW base station 180 and the UE 182 may utilize beamforming (transmission and / or reception) on the mmW communication link 184 to compensate for the extremely high path loss and short distances. Additionally, it should be understood that in an alternative configuration, one or more of the base stations 102 may also use mmW or near-mmW and beamforming for transmission. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.

[0042] Transmit beamforming is a technique for focusing RF signals in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal omnidirectionally, i.e., in all directions. With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thus providing a faster (in terms of data rate) and stronger RF signal to the receiving device. To change the directivity of the RF signal during transmission, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters that broadcast the RF signal. For example, the network node can use an array of antennas (referred to as a "phased array" or "antenna array") that creates an RF beam that can be "manipulated" to point in different directions without actually moving the antennas. Specifically, the RF currents from the transmitters are fed to the individual antennas with the correct phase relationships such that the radio waves from the individual antennas add together to increase radiation in the desired direction while canceling to suppress radiation in the undesired directions.

[0043] Transmit beams can be quasi - co - located, which means that they appear to have the same parameters to a receiver (e.g., a UE), regardless of whether the transmit antennas of the network node are physically co - located. In NR, there are four types of quasi - co - location (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters of a second reference RF signal on a second beam can be derived based on information about a source reference RF signal on a source beam. Thus, if the source reference RF signal is of QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is of 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 of 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 of QCL type D, the receiver can use the source reference RF signal to estimate the spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0044] In receive beamforming, the receiver uses receive beams to amplify the RF signals detected on a given channel. For example, the receiver may increase the gain setting of the antenna array in a specific direction and / or adjust the phase setting of the antenna array in a specific direction to amplify the RF signals received from that direction (e.g., increase its gain level). Thus, when the receiver is described as beamforming in a certain direction, this means that the beam gain in that direction is high relative to the beam gains in other directions, or the beam gain in that direction is the highest compared to the beam gains of all other receive beams available to the receiver in that direction. This results in a stronger received signal strength for the RF signals received from that direction (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.).

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

[0046] Note that depending on the entity forming the "downlink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to send a reference signal to a UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam for receiving downlink reference signals. Similarly, depending on the entity forming the "uplink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, it is an uplink receive beam, and if the UE is forming an uplink beam, it is an uplink transmit beam.

[0047] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, in various documents and articles, FR1 is typically (interchangeably) referred to as the "sub-6 GHz" band. Regarding FR2, a similar naming issue sometimes occurs, which is typically (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band.

[0048] The frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Recent 5G NR research has identified operating bands for these mid-band frequencies as frequency range designations FR3 (7.125 GHz to 24.25 GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher bands are currently being explored 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 bands falls within the EHF band.

[0049] Taking the above aspects into account, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" etc. is used herein, it can generally represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" etc. is used herein, it can generally represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0050] 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 a carrier operating on the primary frequency (e.g., FR1) utilized by the UE 104 / 182 and the cell, where the UE 104 / 182 performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection reestablishment procedure in the cell. The primary carrier carries all common and UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2), which can be configured and used to provide additional radio resources once an RRC connection is established between the UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier can contain only necessary signaling information and signals. For example, since the primary uplink carrier and the primary downlink carrier are typically UE-specific, those UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell can have different downlink primary carriers. The same holds for the primary uplink carrier. The network can change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to the carrier frequency / component carrier on which a certain base station communicates, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. can be used interchangeably.

[0051] For example, still referring to Figure 1 , one of the frequencies utilized by the macro cell base station 102 can be the anchor carrier (or "PCell"), and the other frequencies utilized by the macro cell base station 102 and / or the mmW base station 180 can be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers enables the UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, compared to the data rate obtained with a single 20 MHz carrier, two 20 MHz aggregated carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40 MHz).

[0052] The wireless communication system 100 may further include a UE 164, which may communicate with the macro cell base station 102 via a communication link 120 and / or communicate with the mmW base station 180 via an mmW communication link 184. For example, the macro cell base station 102 may support a PCell and one or more SCell for the UE 164, and the mmW base station 180 may support one or more SCell for the UE 164.

[0053] In some cases, the UE 164 and the UE 182 are capable of performing sidelink communication. A UE with sidelink capabilities (SL-UE) may communicate with the base station 102 via the Uu interface (i.e., the air interface between the UE and the base station) through the communication link 120. The SL-UEs (e.g., UE 164, UE 182) may also communicate directly with each other via the PC5 interface (i.e., the air interface between UEs with sidelink capabilities) through the wireless sidelink 160. The wireless sidelink (or simply referred to as "sidelink") is an adaptation of the core cellular network (e.g., LTE, NR) standard, which allows direct communication between two or more UEs without communicating through the base station. Sidelink communication can be unicast or multicast and can be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, etc.), emergency rescue applications, etc. One or more SL-UEs in a group of SL-UEs that utilize sidelink communication may be located within the geographical coverage area 110 of the base station 102. Other SL-UEs in such a group may be outside the geographical coverage area 110 of the base station 102 or may not be able to receive transmissions from the base station 102 for other reasons. In some cases, each group of SL-UEs that communicate via sidelink communication may utilize a one-to-many (1:M) system, where each SL-UE transmits to each other SL-UE 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 the SL-UEs without involving the base station 102.

[0054] In one aspect, the sidelink 160 may operate on a wireless communication medium of interest, which may be shared with other vehicles and / or infrastructure access points and other wireless communications between other RATs. The "medium" may include one or more time, frequency, and / or spatial communication resources associated with wireless communication between one or more transmitter / receiver pairs (e.g., covering one or more channels across one or more carriers). In one aspect, the medium of interest may correspond to at least a portion of an unlicensed band shared between various RATs. Although different licensed bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) in the United States), these systems (specifically those employing small cell access points) have recently extended their operation into unlicensed 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 technologies commonly referred to as "Wi-Fi"). Example systems of this type include different variants of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, etc.

[0055] Note that while Figure 1 only two of these UEs are illustrated as SL-UEs (i.e., UE 164 and 182), any of the illustrated UEs may be an SL-UE. Additionally, although only UE 182 is described as being capable of beamforming, any of the illustrated UEs (including UE 164) are capable of beamforming. In cases where the SL-UEs are capable of beamforming, they may beamform towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UE 104), towards base stations (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 the sidelink 160.

[0056] In Figure 1 the example of, the illustrated UEs (for simplicity, in Figure 1Any one of the UEs 104 shown as a single UE in the figure can receive a signal 124 from one or more space vehicles (SVs) 112 in Earth orbit (e.g., satellites). In one aspect, the SV 112 can be part of a satellite positioning system that the UE 104 can use as an independent source of position information. A satellite positioning system typically includes a transmitter system (e.g., the SV 112) that is positioned such that a receiver (e.g., the UE 104) can determine its position on or above the Earth at least in part based on positioning signals received from the transmitter (e.g., the signal 124). Such transmitters typically send signals marked with a repeating pseudo-random noise (PN) code with a set number of chips. Although typically located in the SV 112, the transmitter can sometimes be located on a ground-based control station, a base station 102, and / or another UE 104. The UE 104 can include one or more dedicated receivers that are specifically designed to receive the signal 124 in order to derive geographical location information from the SV 112.

[0057] In a satellite positioning system, the use of the signal 124 can be enhanced by various satellite-based augmentation systems (SBAS) that can be associated with or otherwise enable the use of one or more global and / or regional navigation satellite systems. For example, an SBAS can include augmentation systems that provide integrity information, differential corrections, etc., such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi-functional Satellite Augmentation System (MSAS), GPS- Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation System (GAGAN), etc. Thus, as used herein, a satellite positioning system can include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0058] In one aspect, the SV 112 can additionally or alternatively be part of one or more non-terrestrial networks (NTN). In an NTN, the SV 112 is connected to an earth station (also known as a ground station, NTN gateway, or gateway) that is in turn connected to elements in a 5G network, such as an enhanced base station 102 (without a ground antenna) or a network node in the 5GC. This element in turn provides access to other elements in the 5G network and ultimately provides access to entities external to the 5G network, such as Internet web servers and other user equipment. In this way, instead of or in addition to communication signals from the ground base station 102, the UE 104 can receive communication signals (e.g., the signal 124) from the SV 112.

[0059] The wireless communication system 100 may also include one or more UEs (such as UE 190), which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "sidelinks"). In Figure 1 the example of, UE 190 has a D2D P2P link 192 with a UE in UE 104 connected to one of the base stations in base station 102 (for example, UE190 can indirectly obtain cellular connectivity through this D2D P2P link), and has a D2D P2P link 194 with WLAN STA 152 connected to WLAN AP150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through this D2D P2P link). In one example, the D2D P2P links 192 and 194 can be supported by any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), and so on.

[0060] Figure 2A Illustrates an example wireless network structure 200. For example, 5GC 210 (also known as Next Generation Core (NGC)) can be functionally regarded as a control plane (C-plane) function 214 (such as UE registration, authentication, network access, gateway selection, etc.) and a user plane (U-plane) function 212 (such as UE gateway function, access to data networks, IP routing, etc.), which cooperate to form a core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C) 215 connect gNB 222 to 5GC 210, and specifically connect to the user plane function 212 and the control plane function 214 respectively. In an additional configuration, ng-eNB 224 can also be connected to 5GC 210 via NG-C 215 to the control plane function 214 and NG-U 213 to the user plane function 212. In addition, ng-eNB224 can communicate directly with gNB 222 via a backhaul connection 223. In some configurations, the Next Generation RAN (NG-RAN) 220 can have one or more gNB 222, while other configurations include one or more of both ng-eNB 224 and gNB 222. Any one (or both) of gNB222 or ng-eNB 224 can communicate with one or more UEs 204 (such as any of the UEs described herein).

[0061] Another optional aspect may include a location server 230 that may communicate with the 5GC 210 to provide location assistance for the UE 204. The location server 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively may each correspond to a single server. The location server 230 may be configured to support one or more location services for the UE 204 that may be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). Additionally, 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).

[0062] Figure 2B Another example wireless network structure 240 is illustrated. The 5GC 260 (which may correspond to Figure 2AThe 5GC 210) can be functionally regarded as the control plane function provided by the Access and Mobility Management Function (AMF) 264, and the user plane function provided by the User Plane Function (UPF) 262, which cooperate to form the core network (i.e., 5GC 260). The functions of the AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any one of the UEs described herein) and the Session Management Function (SMF) 266, transparent proxy service for routing SM messages, access authentication and access authorization, transmission of Short Message Service (SMS) messages between the UE 204 and the Short Message Service Function (SMSF) (not shown), and Security Anchor Functionality (SEAF). The AMF 264 also interacts with the Authentication Server Function (AUSF) (not shown) and the UE 204, and receives the intermediate key established as a result of the UE 204 authentication process. In the case of authentication based on a UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), the AMF 264 retrieves the security material from the AUSF. The functions of the AMF 264 also include Security Context Management (SCM). The SCM receives the key from the SEAF, which uses this key to derive the access network-specific key. The functionality of the AMF 264 also includes location service management for regulatory services, transmission of location service messages between the UE 204 and the Location Management Function (LMF) 270 (which acts as the location server 230), transmission of location service messages between the NG-RAN 220 and the LMF 270, allocation of Evolved Packet System (EPS) bearer identifiers for EPS interoperability, and UE 204 mobility event notification. In addition, the AMF 264 also supports functionality for non-3GPP (Third Generation Partnership Project) access networks.

[0063] 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 the interconnection to a data network (not shown), providing 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) handling of the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (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 transmitting and forwarding one or more "end markers" to the source RAN node. The UPF 262 may also support the passing of location service messages between the UE 204 and a location server (such as the SLP 272) on the user plane.

[0064] The functions of the SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, traffic steering configuration at the UPF 262 for routing traffic to the correct destination, partial control of policy enforcement and QoS, and downlink data notification. The interface through which the SMF 266 communicates with the AMF 264 is referred to as the N11 interface.

[0065] Another optional aspect may include the LMF 270, which may communicate with the 5GC 260 to provide location assistance for 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 distributed across multiple physical servers, etc.), or alternatively may each correspond to a single server. The LMF 270 may be configured to support one or more location services for the UE 204, which may be connected to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not illustrated). The SLP 272 may support functions similar to those of the LMF 270, but the LMF 270 may communicate with the AMF 264, the NG-RAN 220, and the UE 204 on the control plane (e.g., using interfaces and protocols designed to convey signaling messages rather than voice or data), and the SLP 272 may communicate with the UE 204 and an external client (e.g., a third-party server 274) on the user plane (e.g., using protocols designed to carry voice and / or data, such as the Transmission Control Protocol (TCP) and / or IP).

[0066] Another optional aspect may include a third-party server 274 that may communicate 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) of the UE 204. Thus, in some cases, the third-party server 274 may be referred to as a location service (LCS) client or an external client. The third-party server 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively may each correspond to a single server.

[0067] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and the AMF 264, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220, respectively. The interface between the gNB 222 and / or the ng-eNB 224 and the AMF 264 is referred to as the "N2" interface, while the interface between the gNB 222 and / or the ng-eNB 224 and the UPF 262 is referred to as the "N3" interface. The gNBs 222 and / or the ng-eNBs 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 gNBs 222 and / or the ng-eNBs 224 may communicate with one or more UEs 204 via a radio interface referred to as the "Uu" interface.

[0068] The functionality of gNB 222 can be divided between a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DU) 228, and one or more gNB radio units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically allocated to the gNB-DU 228, including delivering user data, mobility control, radio access network sharing, positioning, session management, and so on. More specifically, the gNB-CU 226 generally 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 generally hosts the radio link control (RLC) and media 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 more 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-DU 228s is referred to as the "F1" interface. The physical (PHY) layer functionality of the gNB 222 is generally hosted by one or more independent gNB-RU 229s, 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 layer, SDAP layer, and PDCP layer, communicates with the gNB-DU 228 via the RLC layer and MAC layer, and communicates with the gNB-RU 229 via the PHY layer.

[0069] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, RAN nodes, core network nodes, network elements, or network equipment (such as base stations or one or more units (or one or more components) that perform base station functionality) can 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, etc.) can be implemented as an aggregated base station (also referred to as a stand-alone base station or a monolithic base station) or a disaggregated base station.

[0070] A centralized base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A split base station may be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or 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).

[0071] The base station type operation or network design may consider the aggregation characteristics of the base station functionality. For example, a split base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration as advocated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). The splitting may include distributing functions across two or more units at various physical locations, as well as virtually distributing the functions of at least one unit, which may achieve flexibility in network design. The various units of a split base station or a split RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0072] Figure 2C An example split base station architecture 250 in accordance with aspects of the present disclosure is illustrated. The split base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CU 226), which may 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 split base station units, such as a near real-time (near 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 a respective UE 204 via one or more radio frequency (RF) access links. In some embodiments, the UE 204 may be served simultaneously by multiple RUs 287.

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

[0074] In some aspects, the CU 280 may host one or more higher 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 utilize an interface that is configured to convey 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 specific implementations, the CU 280 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bi-directionally with the CU-CP units via an interface (such as an E1 interface). As needed, the CU 280 may be implemented to communicate with the DU 285 for network control and signaling.

[0075] The DU 285 may correspond to a logical unit that includes 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 the radio link control (RLC) layer, the media access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation, etc.) at least partially depending on a functional split (such as the functional split defined by the 3rd Generation Partnership Project (3GPP)). In some aspects, the DU 285 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 285 or with control functions hosted by the CU 280.

[0076] The lower layer functionality may be implemented by one or more RUs 287. In some deployments, the RUs 287 controlled by the DU 285 may correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both at least partially based on a functional split (such as a lower layer functional split). In such an architecture, the RUs 287 may be implemented to handle over-the-air (OTA) communication with one or more UEs 204. In some embodiments, the real-time and non-real-time aspects of the control plane and user plane communication with the RUs 287 may be controlled by the corresponding DU 285. In some scenarios, this configuration may enable the implementation of the DU 285 and the CU 280 in a cloud-based RAN architecture (such as a vRAN architecture).

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

[0078] The non-RT RIC 257 can be configured to include logical functions that can enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and update, or policy-based guidance of applications / features in the near RT RIC 259. The non-RT RIC 257 can be coupled to or communicate with the near RT RIC 259 (such as via the A1 interface). The near RT RIC 259 can be configured to include logical functions that can enable near-real-time control and optimization of RAN elements and resources through an interface (such as via the E2 interface) via data collection and actions, and this interface connects one or more CUs 280, one or more DUs 285, or both, and the O-eNB to the near RT RIC 259.

[0079] In some specific implementations, to generate the AI / ML models to be deployed in the near-RT RIC 259, the non-RT RIC 257 may receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 259 and can be received from non-network data sources or from network functions at the SMO framework 255 or the non-RT RIC 257. In some examples, the non-RT RIC 257 or the near-RT RIC 259 may be configured to tune the RAN behavior or performance. For example, the non-RT RIC 257 may monitor long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions via the SMO framework 255 (such as reconfiguration via O1) or via creating RAN management policies (such as A1 policies).

[0080] Figure 3A , Figure 3B and Figure 3C illustrates several example components (represented by corresponding boxes) that may be incorporated into 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 the location server 230 and the LMF 270, or alternatively may be independent of Figure 2A and Figure 2B the depicted NG-RAN 220 and / or 5GC 210 / 260 infrastructure, such as a private network), to support operations as described herein. It should be understood that these components may be implemented in different specific implementations in different types of devices (e.g., in an ASIC, in a system-on-chip (SoC), etc.). The illustrated components may also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Moreover, a given device may include one or more of these 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.

[0081] UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively. These wireless wide area network (WWAN) transceivers provide components (e.g., components for transmission, components for reception, components for measurement, components for tuning, components for blocking transmission, etc.) for communication via one or more wireless communication networks (not shown), such as an NR network, an LTE network, a GSM network, etc. WWAN transceivers 310 and 350 can each be respectively connected to one or more antennas 316 and 356 for communicating with other network nodes (such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc.) via at least one specified RAT (e.g., NR, LTE, GSM, etc.) on an interested wireless communication medium (e.g., a set of time / frequency resources in a specific spectrum). WWAN transceivers 310 and 350 can be configured in different ways to respectively transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to the specified RAT, and conversely, to respectively receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, WWAN transceivers 310 and 350 respectively include: one or more transmitters 314 and 354 for respectively transmitting and encoding signals 318 and 358, and one or more receivers 312 and 352 for respectively receiving and decoding signals 318 and 358.

[0082] At least in some cases, UE 302 and base station 304 each also include one or more short-range wireless transceivers 320 and 360, respectively. Short-range wireless transceivers 320 and 360 can be respectively connected to one or more antennas 326 and 366, and provide for communication via at least one specified RAT (e.g., WiFi, LTE-D, Components (e.g., components for transmission, reception, measurement, tuning, transmission blocking, etc.) that communicate with other network nodes (such as other UEs, access points, base stations, etc.) using PC5, dedicated short-range communication (DSRC), wireless access for vehicle environments (WAVE), near-field communication (NFC), ultra-wideband (UWB), etc. The short-range wireless transceivers 320 and 360 can be configured in different ways to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.) according to the specified RAT, and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, the short-range wireless transceivers 320 and 360 respectively include: one or more transmitters 324 and 364 for transmitting and encoding signals 328 and 368, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368. As a specific example, the short-range wireless transceivers 320 and 360 can be WiFi transceivers, transceivers, and / or transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

[0083] At least in some cases, the UE 302 and the base station 304 also include satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 can be respectively connected to one or more antennas 336 and 376, and can provide components for receiving and / or measuring satellite positioning / communication signals 338 and 378. In the case where the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning / communication signals 338 and 378 can be Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. In the case where the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 can be communication signals (e.g., carrying control and / or user data) originating from a 5G network. The satellite signal receivers 330 and 370 can include any suitable hardware and / or software for receiving and processing the satellite positioning / communication signals 338 and 378. The satellite signal receivers 330 and 370 can request appropriate information and operations from other systems, and at least in some cases, perform calculations using measurements obtained by any suitable satellite positioning system algorithm to respectively determine the positions of the UE 302 and the base station 304.

[0084] Base station 304 and network entity 306 each include one or more network transceivers 380 and 390, respectively, which provide components (e.g., components for transmission, components for reception, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, base station 304 may employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. As another example, network entity 306 may employ one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or communicate with other network entities 306 via one or more wired or wireless core network interfaces.

[0085] The transceiver may be configured to communicate via a wired or wireless link. The transceiver (whether a wired transceiver or a wireless transceiver) includes a transmitter circuit (e.g., transmitters 314, 324, 354, 364) and a receiver circuit (e.g., receivers 312, 322, 352, 362). In some specific implementations, the transceiver may be an integrated device (e.g., the transmitter circuit and the receiver circuit are implemented in a single device), in some specific implementations may include a separate transmitter circuit and a separate receiver circuit, or may be implemented in other ways in other specific implementations. The transmitter circuit and the receiver circuit of a wired transceiver (e.g., network transceivers 380 and 390 in some specific implementations) may be coupled to one or more wired network interface ports. The wireless transmitter circuit (e.g., transmitters 314, 324, 354, 364) may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the corresponding device (e.g., UE 302, base station 304) to perform transmission "beamforming" as described herein. Similarly, the wireless receiver circuit (e.g., receivers 312, 322, 352, 362) may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming as described herein. In one aspect, the transmitter circuit and the receiver circuit may share the same plurality of antennas (e.g., antennas 316, 326, 356, 366), such that the corresponding device can only receive or only transmit at a given time, rather than receive and transmit both at the same time. The wireless transceiver (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a network listening module (NLM) for performing various measurements, etc.

[0086] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360 in some embodiments, and network transceivers 380 and 390), and wired transceivers (e.g., network transceivers 380 and 390 in some embodiments) may generally be characterized as "transceiver", "at least one transceiver", or "one or more transceivers". Thus, it may be inferred whether a particular transceiver is a wired transceiver or a wireless transceiver based on the type of communication being performed. For example, fronthaul communication between network devices or servers typically involves signaling via a wired transceiver, while wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) will typically involve signaling via a wireless transceiver.

[0087] UE 302, base station 304, and network entity 306 also include other components that may be used in conjunction with the operations disclosed herein. UE 302, base station 304, and network entity 306 each include one or more processors 332, 384, and 394 for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 332, 384, and 394 may provide components for processing, such as components for determining, for calculating, for receiving, for transmitting, for indicating, etc. In one aspect, processors 332, 384, and 394 may 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 circuits, or various combinations thereof.

[0088] UE 302, base station 304, and network entity 306 respectively include memory circuits that implement memories 340, 386, and 396 (e.g., each including a memory device), and the memory circuits are used to maintain information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Thus, memories 340, 386, and 396 can provide components for storage, components for retrieval, components for maintenance, etc. In some cases, UE 302, base station 304, and network entity 306 may respectively include NTN components 342, 388, and 398. NTN components 342, 388, and 398 can be hardware circuits that are respectively part of or coupled to processors 332, 384, and 394, and these hardware circuits, when executed, cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, NTN components 342, 388, and 398 can be external to processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, NTN components 342, 388, and 398 can be memory modules respectively stored in memories 340, 386, and 396, and these memory modules, when executed by processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. Figure 3A Illustrates the possible locations of NTN component 342, which can be part of, for example, one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or can be an independent component. Figure 3B Illustrates the possible locations of NTN component 388, which can be part of, for example, one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or can be an independent component. Figure 3C Illustrates the possible locations of NTN component 398, which can be part of, for example, one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or can be an independent component.

[0089] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide components for sensing or detecting movement and / or orientation information unrelated to movement data derived from signals received from one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. By way of example, sensors 344 may include accelerometers (e.g., microelectromechanical systems (MEMS) devices), gyroscopes, geomagnetic sensors (e.g., compasses), altimeters (e.g., barometric altimeters), and / or any other type of movement detection sensor. Additionally, sensors 344 may include multiple different types of devices and combine their outputs to provide movement information. For example, sensors 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate positioning in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

[0090] Additionally, UE 302 includes a user interface 346 that provides components for providing indications to a user (e.g., audible and / or visual indications) and / or for receiving user input (e.g., when the user actuates a sensing device such as a keypad, touch screen, microphone, etc.). Although not shown, base station 304 and network entity 306 may also include a user interface.

[0091] Referring in more detail to one or more processors 384, in the downlink, IP packets from network entity 306 may be provided to processor 384. One or more processors 384 may implement functionality for the RRC layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, and medium access control (MAC) layer. One or more processors 384 may provide: RRC layer functionality associated with the broadcast of system information (e.g., master information block (MIB), system information block (SIB)), 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 the transfer of 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 the mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

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

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

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

[0095] Similar to the functionality described in connection with downlink transmission performed by base station 304, 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 the transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with the mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

[0096] Channel estimates derived by a channel estimator from reference signals or feedback transmitted by base station 304 can be used by transmitter 314 to select appropriate decoding and modulation schemes and facilitate spatial processing. The spatial streams generated by transmitter 314 can be provided to different antennas 316. Transmitter 314 can modulate RF carriers with the respective spatial streams for transmission.

[0097] Uplink transmission is processed at base station 304 in a manner similar to that described in connection with the receiver functionality at UE 302. Receiver 352 receives signals via its respective antennas 356. Receiver 352 recovers the information modulated onto the RF carriers and provides the information to one or more processors 384.

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

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

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

[0101] Figure 3A , Figure 3B and Figure 3C The components of can be implemented in various ways. In some specific implementations, Figure 3A , Figure 3B and Figure 3CThe components 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). Here, each circuit may use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide the functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by the processor and memory components of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by the processor and memory components of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Moreover, some or all of the functionality represented by blocks 390 to 398 may be implemented by the processor and memory components of network entity 306 (e.g., by executing 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", "performed by the base station", "performed by the network entity", etc. However, as will be understood, such operations, actions, and / or functions may actually be performed by specific components or combinations of components of 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, NTN components 342, 388, and 398, etc.

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

[0103] NR supports a variety of 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. Figure 4Examples of various positioning methods in accordance with aspects of the present disclosure are illustrated. In the OTDOA or DL-TDOA positioning procedure illustrated in scenario 410, the UE measures the difference in the time of arrival (ToA) of reference signals (e.g., positioning reference signals (PRS)) received from paired base stations (referred to as reference signal time difference (RSTD) or time difference of arrival (TDOA) measurements), and reports these differences to a positioning entity. More specifically, the UE receives in the assistance data the identifiers (IDs) of a reference base station (e.g., serving base station) and a plurality of non-reference base stations. The UE then measures the RSTD between the reference base station and each non-reference base station. Based on the known locations of the involved base stations and the RSTD measurements, a positioning entity (e.g., the UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the location of the UE.

[0104] For DL-AoD positioning illustrated in scenario 420, the positioning entity uses measurement reports from the UE of the received signal strength measurements of a plurality of downlink transmission beams to determine the angle between the UE and the transmitting base station. The positioning entity can then estimate the location of the UE based on the determined angle and the known location of the transmitting base station.

[0105] 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 uplink reference signals (e.g., sounding reference signals (SRS)) transmitted by the UE to a plurality of base stations. Specifically, the UE transmits one or more uplink reference signals, which are measured by a reference base station and a plurality of non-reference base stations. Each base station then reports to a positioning entity (e.g., a location server) that knows the locations and relative timings of the involved base stations the reception time of the reference signal (referred to as relative time of arrival (RTOA)). Based on the received-to-received (Rx-Rx) time difference between the reported RTOA of the reference base station and the reported RTOA of each non-reference base station, the known locations of the base stations, and their known timing offsets, the positioning entity can use TDOA to estimate the location of the UE.

[0106] 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 reception beams. The positioning entity uses the signal strength measurements and the angles of the reception beams to determine the angle between the UE and the base station. Based on the determined angle and the known location of the base station, the positioning entity can then estimate the location of the UE.

[0107] Downlink- and uplink-based positioning methods include: enhanced cell ID (E-CID) positioning and multi-round-trip time (RTT) positioning (also known as "multi-cell RTT" and "multi-RTT"). In the RTT procedure, a first entity (e.g., a base station or a UE) sends a first RTT-related signal (e.g., a PRS or an SRS) to a second entity (e.g., a UE or a base station), and the second entity sends a second RTT-related signal (e.g., an SRS or a PRS) back to the first entity. Each entity measures the time difference between the arrival time (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. This time difference is referred to as the received-transmitted (Rx-Tx) time difference. The Rx-Tx time difference measurement can be made or adjusted to include only the time difference between the received signal and the nearest time slot boundary of the transmitted signal. Then, the two entities can transmit their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round-trip propagation time (i.e., the RTT) between the two entities based on these two Rx-Tx time difference measurements (e.g., calculated as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity can transmit its Rx-Tx time difference measurement to the other entity, and then the other entity calculates the RTT. The distance between the two entities can be determined based on the RTT and a known signal speed (e.g., the speed of light). For multi-RTT positioning illustrated in scenario 430, a first entity (e.g., a UE or a base station) performs the RTT positioning procedure with multiple second entities (e.g., multiple base stations or UEs) so that the position of the first entity can be determined (e.g., using multilateration) based on the distances to the second entities and the known positions of the second entities. The RTT and multi-RTT methods can be combined with other positioning techniques (such as UL-AoA and DL-AoD) to improve position accuracy, as illustrated in scenario 440.

[0108] 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 identifiers, estimated timing, and signal strength of the detected neighboring base stations. Then, the position of the UE is estimated based on this information and the known positions of the base stations.

[0109] 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 a cell / TRP of the base station) from which the reference signal is measured, reference signal configuration parameters (e.g., including the number of consecutive time slots including the PRS, the periodicity of the consecutive time slots including the PRS, the silence sequence, the frequency hopping sequence, the reference signal identifier, the reference signal bandwidth, etc.) and / or other parameters applicable to a specific positioning method. Alternatively, the assistance data may directly originate from the base station itself (e.g., in periodically broadcast overhead messages, etc.). In some cases, the UE itself may be able to detect adjacent network nodes without using assistance data.

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

[0111] A location estimate may be referred to by other names, such as positioning estimate, location, positioning, positioning lock, lock, etc. A location estimate may be geodetic and include coordinates (e.g., latitude, longitude, and possibly altitude), or it may be civic and include a street address, a postal address, or some other verbal description of the location. A location estimate may be further defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possibly altitude). A positioning estimate may include an expected error or uncertainty (e.g., by including the area or volume within which the location is expected to be included with a certain specified or default confidence).

[0112] Various frame structures may be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). Figure 5 FIG. 500 is a diagram illustrating an example frame structure in accordance with 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.

[0113] 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 divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often referred to as frequency tones, frequency bins, etc. Each subcarrier can be modulated with data. Generally speaking, modulation symbols are transmitted using OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kilohertz (kHz), and the minimum resource allocation (resource block) can be 12 subcarriers (or 180 kHz). Thus, for system bandwidths of 1.25 megahertz (MHz), 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, the nominal Fast Fourier Transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048 respectively. The system bandwidth can also be divided into multiple subbands. For example, a subband can cover 1.08 MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, there can be 1, 2, 4, 8, or 16 subbands respectively.

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

[0115] In Figure 5 the example of, a parameter set of 15 kHz is used. Thus, in the time domain, a 10 ms frame is divided into 10 equal-sized subframes, each subframe being 1 ms, and each subframe includes one time slot. In Figure 5 it, time is represented horizontally (on the X-axis), where time increases from left to right, while frequency is represented vertically (on the Y-axis), where frequency increases (or decreases) from bottom to top.

[0116] A resource grid can be used to represent a time slot, and each time slot includes one or more time-concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE can correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In Figure 5In the parameter set of , for the normal cyclic prefix, an RB can contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 resource elements (REs). For the extended cyclic prefix, an RB can contain 12 consecutive subcarriers in the frequency domain and six 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.

[0117] Some REs can carry reference (pilot) signals (RSs). These reference signals can include positioning reference signals (PRSs), tracking reference signals (TRSs), phase tracking reference signals (PTRSs), cell-specific reference signals (CRSs), channel state information reference signals (CSI-RSs), demodulation reference signals (DMRSs), primary synchronization signals (PSSs), secondary synchronization signals (SSSs), synchronization signal blocks (SSBs), sounding reference signals (SRSs), etc., depending on whether the illustrated frame structure is used for uplink communication or downlink communication. Figure 5 An example location of an RE carrying a reference signal (marked as "R") is illustrated.

[0118] The set of resource elements (REs) used for the transmission of PRS is referred to as a "PRS resource". The set of resource elements can span multiple physical resource blocks (PRBs) in the frequency domain and 'N' (such as one or more) consecutive symbols within a time slot in the time domain. In a given OFDM symbol in the time domain, the PRS resource occupies consecutive PRBs in the frequency domain.

[0119] The transmission of the PRS resource within a given PRB has a specific comb size (also referred to as "comb density"). The comb size 'N' represents the subcarrier spacing (or frequency / tone spacing) within each symbol of the PRS resource configuration. Specifically, for a comb size 'N', the PRS is transmitted in every Nth subcarrier of a symbol of the PRB. For example, for a comb-4, for each symbol of the PRS resource configuration, the REs corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) are used to transmit the PRS of the PRS resource. Currently, for DL-PRS, comb sizes of comb-2, comb-4, comb-6, and comb-12 are supported. Figure 5 An example PRS resource configuration for a comb-4 (which spans four symbols) is illustrated. That is, the location of the shaded REs (marked as "R") indicates the comb-4 PRS resource configuration.

[0120] Currently, DL-PRS resources use a full-frequency-domain interleaved pattern that can span 2, 4, 6, or 12 consecutive symbols within a time slot. DL-PRS resources can be configured in any downlink or flexible (FL) symbol configured by the higher layer in a time slot. For all REs of a given DL-PRS resource, there may be a constant energy per resource element (EPRE). The following are the per-symbol frequency offsets for comb sizes 2, 4, 6, and 12 on 2, 4, 6, and 12 symbols. 2-symbol comb - 2: {0, 1}; 4-symbol comb - 2: {0, 1, 0, 1}; 6-symbol comb - 2: {0, 1, 0, 1, 0, 1}; 12-symbol comb - 2: {0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1}; 4-symbol comb - 4: {0, 2, 1, 3} (as in the example of Figure 5 ); 12-symbol comb - 4: {0, 2, 1, 3, 0, 2, 1, 3, 0, 2, 1, 3}; 6-symbol comb - 6: {0, 3, 1, 4, 2, 5}; 12-symbol comb - 6: {0, 3, 1, 4, 2, 5, 0, 3, 1, 4, 2, 5}; and 12-symbol comb - 12: {0, 6, 3, 9, 1, 7, 4, 10, 2, 8, 5, 11}.

[0121] 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, the PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and is associated with a specific TRP (identified by the TRP ID). In addition, the PRS resources in a PRS resource set have the same periodicity, common silent mode configuration, and the same repetition factor (such as "PRS-ResourceRepetitionFactor") across time slots. 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 can have a length selected from: 2^μ * {4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240} time slots, where μ = 0, 1, 2, 3. The repetition factor can have a length selected from {1, 2, 4, 6, 8, 16, 32} time slots.

[0122] The PRS resource ID in the PRS resource pool is associated with a single beam (or beam ID) transmitted from a single TRP (where one TRP can transmit one or more beams). That is, each PRS resource in the PRS resource pool can be transmitted on different beams, and thus, the "PRS resource" (or simply "resource") can also be referred to as a "beam". Note that this does not imply anything about whether the UE knows the TRP and beam on which the PRS is transmitted.

[0123] A "PRS instance" or "PRS occasion" is an instance of a periodically repeating time window (such as a group of one or more consecutive time slots) in which the PRS is expected to be transmitted. A PRS occasion can also be referred to as a "PRS positioning occasion", "PRS positioning instance", "positioning occasion", "positioning instance", "positioning repetition", or simply "occasion", "instance", or "repetition".

[0124] A "positioning frequency layer" (also simply referred to as a "frequency layer") is a set of one or more PRS resource pools with the same values for certain parameters across one or more TRPs. Specifically, the set of PRS resource pools has the same subcarrier spacing and cyclic prefix (CP) type (meaning that all parameter sets supported for the physical downlink shared channel (PDSCH) are also supported for the PRS), the same point A, the same value for the 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") and is an identifier / code for a pair of physical radio channels specified for transmission and reception. The downlink PRS bandwidth can have a granularity of four PRBs, and the minimum value is 24 PRBs while the maximum value is 272 PRBs. Currently, up to four frequency layers have been defined, and up to two PRS resource pools can be configured per TRP per frequency layer.

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

[0126] Note that the terms "positioning reference signal" and "PRS" generally refer to specific reference signals for positioning in NR and LTE systems. However, as used herein, the terms "positioning reference signal" and "PRS" may also refer to any type of reference signal that can be used for positioning, such as but not limited to: PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc. as defined in LTE and NR. In addition, the terms "positioning reference signal" and "PRS" can refer to a downlink positioning reference signal, an uplink positioning reference signal, or a sidelink positioning reference signal, unless otherwise indicated by the context. If further differentiation of the type of PRS is needed, the downlink positioning reference signal can be referred to as "DL-PRS", the uplink positioning reference signal (e.g., SRS for positioning, i.e., PTRS) can be referred to as "UL-PRS", and the sidelink positioning reference signal can be referred to as "SL-PRS". In addition, for signals that can be transmitted in the downlink, uplink, and / or sidelink (e.g., DMRS), these signals can be prefixed with "DL", "UL", or "SL" to distinguish the direction. For example, "UL-DMRS" can be different from "DL-DMRS".

[0127] Figure 6 is a diagram of an example PRS configuration 600 for PRS transmission for a given base station in accordance with aspects of the present disclosure. In Figure 6 it, time is represented horizontally and increases from left to right. Each long rectangle represents a time slot, and each short (shaded) rectangle represents an OFDM symbol. In Figure 6 the example of, the PRS resource set 610 (labeled "PRS resource set 1") includes two PRS resources: a first PRS resource 612 (labeled "PRS resource 1") and a second PRS resource 614 (labeled "PRS resource 2"). The base station transmits PRS on the PRS resources 612 and 614 in the PRS resource set 610.

[0128] The PRS resource set 610 has an occasion length (N_PRS) of two time slots and a periodicity (T_PRS) of, for example, 160 time slots or 160 milliseconds (ms) (for a 15 kHz subcarrier spacing). Thus, both PRS resources 612 and 614 are two consecutive time slots in length and repeat every T_PRS time slots starting from the time slot of the first symbol in which the corresponding PRS resource appears. In Figure 6 the example of, the PRS resource 612 has a symbol length (N_symb) of two symbols, and the PRS resource 614 has a symbol length (N_symb) of four symbols. The PRS resources 612 and 614 can be transmitted on separate beams of the same base station.

[0129] Each instance of the PRS resource set 610 (illustrated as instances 620a, 620b, and 620c) includes a timing of length '2' (i.e., N_PRS = 2) for each PRS resource 612, 614 in the PRS resource set. The PRS resources 612 and 614 repeat every T_PRS time slots until the silence sequence period T_REP. Therefore, a bitmap of length T_REP will be required to indicate which timings of the instances 620a, 620b, and 620c of the PRS resource set 610 are silent (i.e., not transmitted).

[0130] In one aspect, there may be additional constraints on the PRS configuration 600. For example, for all PRS resources (e.g., PRS resources 612, 614) in a PRS resource set (e.g., PRS resource set 610), the base station may configure the following parameters to be the same: (a) timing length (N_PRS), (b) number of symbols (N_symb), (c) comb type, and / or (d) bandwidth. Additionally, for all PRS resources in all PRS resource sets, the subcarrier spacing and cyclic prefix may be configured to be the same for one base station or for all base stations. Whether it is for one base station or for all base stations may depend on the UE's ability to support the first and / or second options.

[0131] A non-terrestrial network (NTN) refers to a network or a segment of a network that uses RF resources on board a satellite (or a drone system (UAS) platform). Figure 7A and 7B depicts a typical scenario of an NTN providing access to a UE. Specifically, Figure 7A is a diagram 700 illustrating an example NTN scenario based on a transparent payload according to aspects of the present disclosure. The transparent payload utilizes radio frequency filtering as well as frequency conversion and amplification. Thus, the waveform signal repeated by the payload remains unchanged. Figure 7B is a diagram 750 illustrating an example NTN scenario based on a regenerative payload according to aspects of the present disclosure. The regenerative payload utilizes radio frequency filtering, frequency conversion and amplification, and in addition, demodulation / decoding, switching, and / or routing, and encoding / modulation. This effectively amounts to having all or part of the base station functions (e.g., gNB) on board a satellite (or UAS platform).

[0132] Reference Figure 7A and Figure 7B, NTN is typically characterized by the following elements: (1) one or several satellite gateways (sat-gateways) connecting NTN to a common data network, (2) geostationary earth orbit (GEO) satellites fed by one or several satellite gateways deployed across satellite target coverage (e.g., regional or even continental coverage), (3) non-GEO satellites continuously served by one or several satellite gateways at a time (to ensure service and feeder link continuity between satellite gateways for continuous service, with sufficient time duration to continue mobility anchoring and handover), (4) a feeder link or radio link between the satellite gateway and the satellite (or UAS platform), (5) a service link or radio link between the UE and the satellite (or UAS platform), (6) (optionally) an inter-satellite link (ISL) in the case of a satellite constellation (requiring a regenerative payload on-board the satellite).

[0133] The satellite (or UAS platform) can implement transparent or regenerative (using on-board processing) payloads. The satellite (or UAS platform) can generate several beams over a given service area defined by its field of view. The coverage area of the beam typically has an elliptical shape. The field of view of the satellite (or UAS platform) depends on the on-board antenna pattern and the minimum elevation angle. The beam coverage area can move over the earth as the satellite (or UAS platform) moves in its orbit. Alternatively, the beam coverage area can be earth-fixed, in which case some beam pointing mechanisms (mechanical or electronic steering features) can compensate for the satellite (or UAS platform) movement. Note that the concept of "satellite beam" is different from the concept of "beam" in NR FR2.

[0134] When the UE is served by a satellite (or UAS platform) within the target service area, the network operator may be forced to cross-check the UE location reported by the UE in order to meet the regulatory requirements for UE location for network verification (e.g., lawful interception, emergency calls, public warning systems, etc.). More specifically, when the UE is connected to NTN, the UE reports its location to the network. This location is determined by components external to the cellular modem (e.g., Global Navigation Satellite System (GNSS)), and therefore, the provided location is not trustworthy and needs to be verified by the network. The network operator should be able to check the UE-reported location information by, for example, estimating the UE's location on the network side and specifying whether a mechanism is needed to meet the regulatory requirements. Currently, in order to determine the UE location for network verification, a UE with NTN capabilities can report its GNSS location (since a UE with NTN capabilities is required to have GNSS), and the network (e.g., a location server) verifies or refines the UE's GNSS report through NTN positioning techniques.

[0135] In LTE, and at least in some cases (NR), positioning measurements are reported via higher layer signaling, specifically LTE Positioning Protocol (LPP) signaling and / or RRC. LPP is used point-to-point between a location server (e.g., location server 230, LMF 270, SLP 272) and a UE (e.g., any of the UEs described herein) to locate the UE using location-related measurements obtained from one or more reference sources. Figure 8 FIG. 800 is a diagram that illustrates example LPP reference sources for positioning. In Figure 8 the example, a target device, specifically UE 804 (e.g., any of the UEs described herein) participates in an LPP session with a location server 830 (labeled as "E-SMLC / SLP" in Figure 8 a specific example). UE 804 is also receiving / measuring wireless positioning signals from a first reference source, specifically one or more base stations 802 (which may correspond to any of the base stations described herein and are labeled as "eNode B" in Figure 8 a specific example) and a second reference source, specifically one or more SPS satellites 820 (which may correspond to Figure 1 SV 112 in

[0136] An LPP session is used between the location server 830 and the UE 804 to obtain location-related measurements or a location estimate, or to transfer assistance data. A single LPP session is used to support a single location request (e.g., for a single Mobile Terminated Location Request (MT-LR), Mobile Originated Location Request (MO-LR), or Network Initiated Location Request (NI-LR)). 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, where each LPP transaction performs a single operation (e.g., capability exchange, assistance data transfer, or location information transfer). LPP transactions are referred to as LPP procedures. The initiator of an LPP session initiates the first LPP transaction, but subsequent transactions may be initiated by either endpoint. LPP transactions within a session may occur serially or in parallel. LPP transactions are indicated at the LPP protocol level by a transaction identifier to associate messages (e.g., requests and responses) with each other. Messages within a transaction are linked by a common transaction identifier.

[0137] The LPP positioning method and associated signaling content are defined in the 3GPP LPP standard (3GPP Technical Specification (TS) 36.355, which is publicly available and incorporated herein by reference in its entirety). LPP signaling can be used to request and report measurements related to the following positioning methods: Observed Time Difference of Arrival (OTDOA), Downlink Time Difference of Arrival (DL-TDOA), Assisted Global Navigation Satellite System (A-GNSS), LTE Enhanced Cell ID (E-CID), NR E-CID, sensors, Terrestrial Beacon System (TBS), WLAN, Bluetooth, Downlink Angle of Departure (DL-AoD), Uplink Angle of Arrival (UL-AoA), and Multiple Round Trip Time (RTT). Currently, LPP measurement reports can contain the following measurements: (1) one or more Time of Arrival (ToA), Time Difference of Arrival (TDOA), Reference Signal Time Difference (RSTD), or Received Transmit (Rx-Tx) measurements, (2) one or more AoA and / or AoD measurements (currently only used for the base station to report UL-AoA and DL-AoD to the location server 830), (3) one or more multipath measurements (per-path ToA, Reference Signal Received Power (RSRP), AoA / AoD), (4) one or more motion states (e.g., walking, driving, etc.) and trajectories (currently only used for UE 804), and (5) one or more report quality indicators. In the present disclosure, positioning measurements (such as the example measurements just listed, and regardless of the positioning technology) can be collectively referred to as Positioning State Information (PSI).

[0138] UE 804 and / or the location server 830 can derive location information from one or more reference sources (illustrated as SPS satellites 820 and base station 802 in the Figure 8 example). Each reference source can be used to calculate an independent estimate of the location of UE 804 using the associated positioning technology. In the Figure 8 example, UE 804 is measuring the characteristics of the positioning signal received from base station 802 (e.g., ToA, RSRP, RSTD, etc.) to calculate or assist the location server 830 in calculating an estimate of the location of UE 804 using one or more cellular network-based positioning methods (e.g., multiple RTT, OTDOA, DL-TDOA, DL-AoD, E-CID, etc.). Similarly, UE 804 is measuring the characteristics of the GNSS signal received from SPS satellites 820 (e.g., ToA) to triangulate its location in two or three dimensions based on the number of SPS satellites 820 measured. In some cases, UE804 or the location server 830 can combine the location solutions derived from each of the different positioning technologies to improve the accuracy of the final location estimate.

[0139] As noted above, the UE 804 uses LPP to report location-related measurements obtained from different reference sources (e.g., base station 802, Bluetooth beacon, SPS satellite 820, WLAN access point, motion sensor, etc.). As an example, for GNSS-based positioning, the UE 804 uses the LPP information element (IE) "A-GNSS-ProvideLocationInformation" to provide location measurements (e.g., pseudorange, location estimate, velocity, etc.) along with time information to the location server 830. It can also be used to provide GNSS positioning-specific error causes. The "A-GNSS-ProvideLocationInformation" IE includes IEs such as "GNSS-SignalMeasurementInformation", "GNSS-LocationInformation", "GNSS-MeasurementList", and "GNSS-Error". When the UE 804 provides the location derived using GNSS or a combination of GNSS and other measurements and (optionally) velocity information to the location server 830, the UE includes the "GNSS-LocationInformation" IE. The UE 804 uses the "GNSS-SignalMeasurementInformation" IE to provide GNSS signal measurement information to the location server 830 and provide GNSS network time association (if requested by the location server 830). This information includes measurements of code phase, Doppler, C / No, and (optionally) accumulated carrier phase (also known as accumulated delta range (ADR)), which implements the UE-assisted GNSS method where the location is computed in the location server 830. The UE 804 uses the "GNSS-MeasurementList" IE to provide measurements of code phase, Doppler, C / No, and (optionally) accumulated carrier phase (or ADR).

[0140] As another example, for motion sensor-based positioning, the currently supported positioning methods use a barometric pressure sensor and motion sensors, as described in 3GPP TS 36.305 (which is publicly available and incorporated herein by reference in its entirety). The UE 804 uses the LPP IE "Sensor-ProvideLocationInformation" to provide location information for sensor-based methods to the location server 830. It can also be used to provide sensor-specific error reasons. The UE 804 uses the "Sensor-MeasurementInformation" IE to provide sensor measurements (e.g., barometric pressure readings) to the location server 830. The UE 804 uses "Sensor-MotionInformation" to provide motion information to the location server 830. The motion information may include a series of ordered points. This information can be obtained by the UE 804 using one or more motion sensors (e.g., accelerometer, barometer, magnetometer, etc.).

[0141] As yet another example, for Bluetooth-based positioning, the UE 804 uses the "BT-ProvideLocationInformation" IE to provide measurements of one or more Bluetooth beacons to the location server 830. This IE can also be used to provide Bluetooth positioning-specific error reasons.

[0142] Figure 9 FIG. 900 is a diagram illustrating an example architecture suitable for positioning a UE using NR access in accordance with aspects of the present disclosure. Referring Figure 9 , the AMF 264 receives a request for a certain location service associated with a specific target UE 204 from another entity (e.g., Gateway Mobile Location Center (GMLC) or UE 204), or the AMF 264 itself decides to initiate a certain location service on behalf of the specific target UE 204 (e.g., for an IP Multimedia Subsystem (IMS) emergency call from the UE).

[0143] The AMF 264 then transmits the location service request to the LMF 270. The LMF 270 processes the location service request, which may include delivering assistance data to the target UE 204 to assist in UE-based and / or UE-assisted positioning, and / or may include positioning of the target UE 204. The LMF 270 then returns the result of the location service to the AMF 264 (e.g., a location estimate of the UE 204). In the case where the location service is requested by an entity other than the AMF 264 (e.g., GMLC or UE 204), the AMF 264 returns the location service result to that entity.

[0144] An NG-RAN node (e.g., gNB 222 or ng-eNB 224) may control several TRPs (such as remote radio heads) or DL-PRS transmission points (TPs) only for supporting PRS-based TBS.

[0145] The LMF 270 may have a dedicated signaling connection to an evolved serving mobile location center (E-SMLC), which may enable the LMF 270 to access information from the evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN) (e.g., using downlink measurements obtained by the target UE 204 from signals of eNBs and / or only PRS TPs in the E-UTRAN to support observed time difference of arrival (OTDOA) for the evolved UMTS terrestrial radio access (E-UTRA) positioning method). Details of the signaling interaction between the LMF and the E-SMLC are outside the scope of this disclosure.

[0146] The LMF 270 may have a dedicated signaling connection to the SLP 272. The SLP 272 is a SUPL entity responsible for positioning on the user plane. Further details of the signaling interaction between the LMF 270 and the SLP 272 are outside the scope of this disclosure.

[0147] Figure 10 FIG. 1000 is a diagram illustrating other aspects of the RSTD measurement between a reference transmission point (TP) and an adjacent transmission point (TP) in accordance with aspects of the present disclosure. In Figure 10 the example, time is represented horizontally and each block represents a subframe (or time slot). The target UE may assume that the start of the subframe (or time slot) of the downlink reference signal (e.g., PRS) for a non-reference (or adjacent) transmission point is received within a search window of size [-nr-DL-PRS-ExpectedRSTD-Uncertainty×R; nr-DL-PRS-ExpectedRSTD-Uncertainty×R] centered at TREF+Nms+nr-DL-PRS-ExpectedRSTD×4×Ts. The parameters "nr-DL-PRS-ExpectedRSTD-Uncertainty" and "nr-DL-PRS-ExpectedRSTD" may be provided to the UE via the LPP assistance data transfer procedure. The parameter T REFIt is the reception time at the UE's antenna connector of the start of a subframe (or time slot) of a downlink reference signal (e.g., PRS) for a reference transmission point indicated in the auxiliary data. The parameter N is calculated based on the parameters "nr-DL-PRS-SFN0-Offset", "d1-PRS-Periodicity-and-ResourceSetSlotOffset", and "d1-PRS-ResourceSlotOffset". These parameters can also be provided to the UE via the LPP auxiliary data transfer procedure. If all PRS resources are in FR2, the resolution R is Ts, otherwise it is 4×Ts, where Ts = 1 / (15000*2048) seconds. Currently, the maximum expected RSTD is 3841×4×Ts = 0.5 ms. In addition, for FR1, the search window (i.e., 2×nr-DL-PRS-ExpectedRSTD-Uncertainty×R) has a maximum value of 246×4×Ts = 32 μs.

[0148] Regarding PRS sequence generation, the UE assumes that the reference signal sequence r(m) is defined as follows:

[0149]

[0150] In the above formula, c(n) is a pseudo-random sequence of a Gold sequence of length 31. This sequence is initialized by c init which is a function of the PRS sequence identifier and the number of time slots. The PRS sequence identifier is given by the parameter "dl-PRS-SequenceID-r16" and can have an integer value ranging from 0 to 4095.

[0151] The NTN-connected UE is expected to have an accurate position estimate based on GNSS measurements. If the UE has acquired satellite ephemeris data (e.g., satellite trajectory information), the UE can calculate the downlink frame / subframe boundary timing without reading the PRS from that satellite TRP. More specifically, the TRP transmits a PRS with a known offset to the start of the frame / subframe / slot to the TRP (e.g., "nr-DL-PRS-SFN0-Offset", "d1-PRS-ResourceS1otOffset"). This PRS offset can be configured to the UE in the positioning assistance data from the location server or in the system information broadcast by the TRP (e.g., one or more SIBs). Then, the reception time of the PRS at the UE can be used to determine the downlink frame / subframe / slot boundary timing for that TRP (i.e., the start of the frame / subframe / slot for that TRP) by subtracting the offset from that reception time. Since the UE knows its own position (from GNSS), the position of the satellite TRP (from ephemeris data), and the PRS offset (from assistance data), the UE can calculate the expected reception time of the PRS from that satellite and thus calculate what the frame / subframe boundary timing of the satellite should be. This can be UE-specific implementation. However, for network position verification, the goal is to force the UE to read / measure the PRS for downlink timing estimation to ensure that the UE does not spoof its position.

[0152] Accordingly, the present disclosure introduces a timing and / or frequency offset to the PRS transmission (PRS resource) to force the UE to measure the PRS for downlink timing estimation for network-verified position. As a first option, a satellite-based RAN node (e.g., as Figure 7A and Figure 7B illustrated) applies a timing and / or frequency offset to the PRS it transmits and notifies the LMF of the offset. As a second option, the LMF can request the satellite-based RAN node to apply a time and / or frequency offset to the PRS of that RAN node.

[0153] For simplicity, the following description refers to the timing offset rather than both the time offset and the frequency offset. However, as will be understood, the following description equally applies to the frequency offset.

[0154] The timing offset for PRS transmission is simply the shift of the PRS transmission time relative to the offset point where the PRS is configured to be transmitted (e.g., "nr-DL-PRS-SFN0-Offset", "d1-PRS-ResourceSlotOffset"). The shift can be positive (i.e., transmit the PRS later in the frame / subframe / slot) or negative (i.e., transmit the PRS earlier in the frame / subframe / slot). The offset point where the PRS is configured to be transmitted can be configured by a location server, network operator, original equipment manufacturer (OEM), etc. to the NG-RAN node.

[0155] Referring to the first option above, where the RAN node decides to apply a timing offset, in this option, the RAN node notifies the LMF of the details of the timing offset (i.e., the timing offset configuration) so that the LMF can remove the amount of the timing offset from the positioning measurements obtained by the UE using time-offset PRS (e.g., RSTD, UE Rx-Tx time difference, etc.). For example, the following parameters can be signaled by the RAN node to the LMF: (1) the PRS timing offset, (2) one or more groups of PRS resources to which a fixed timing offset is applied, and / or (3) how the PRS timing offset varies from one group of PRS resources to another group of PRS resources.

[0156] This information can be signaled in a variety of ways. For example, the RAN node can signal all possible timing offset values as a list. Then, for a given time instance, it applies the first timing offset value to N consecutive PRS resources, the second timing offset value to the next N consecutive PRS resources, and so on. When the list of timing offsets is exhausted, the RAN node can cycle back to the first value of the list. However, as will be understood, this is merely an example, and the selection of the timing offset is not limited to this one example.

[0157] The RAN node can also indicate the start and end times for applying the PRS transmission timing offset. For example, the RAN node can convey to the LMF the timing offset configuration (as discussed above) that is to be applied to all PRS resources from a given start time until a certain end time or for a certain duration. For example, the end point of this duration can be specified based on the number of repetitions of the PRS resources or absolute time. Outside the indicated time period, the LMF assumes legacy operation (i.e., no PRS timing offset).

[0158] Referring to the second option, where the LMF requests the RAN node to apply a timing offset. In this option, this can be as simple a request as asking the RAN node to apply the timing offset to the PRS transmission. In response, the RAN node may convey the PRS timing offset configuration to the LMF. Alternatively, the LMF may request the RAN node to apply certain parameters for the PRS timing offset configuration. For example, the LMF may request the duration for applying the PRS timing offset. Alternatively, the LMF may recommend values for all of the values in the PRS timing offset configuration. In this case, the RAN node may respond with an acknowledgement indicating which of the requested PRS timing offset parameters the RAN node applies and the values of the parameters that the RAN node does not apply the requested values to.

[0159] Once the RAN node and the LMF are synchronized on the PRS timing offset configuration, the LMF configures the PRS measurement window (PRS search window) for the UE based on the PRS timing offset configuration. That is, the LMF adjusts the PRS measurement window to account for the PRS timing offset. The PRS measurement window may be configured to the UE in the LPP provide assistance data message. The assistance data may include the duration for which the PRS measurement window configuration is valid. This may or may not correspond to the duration for which the PRS timing offset is applied to the PRS transmission. The duration may be specified as a start time and an end time specified according to frames, subframes, time slots, or absolute time. Alternatively, the duration may be specified as a start time and a duration specified according to frames, subframes, time slots, or absolute time.

[0160] Outside of this duration, the UE assumes legacy operation. The PRS measurement window may be defined according to groups of PRS resources or PRS resource repetitions. Under legacy operation, the UE may accumulate (e.g., average) measurements over multiple PRS resource repetitions over a period of time picked by the UE. However, if a PRS timing offset is configured, the UE should not accumulate PRS measurements outside of the configured PRS measurement window because the timing offset may not be applied to those PRS resource repetitions, or different timing offsets may be applied to those PRS resource repetitions. Therefore, when a PRS measurement window within which to obtain positioning measurements for one or more PRS resources is configured, it is expected that the UE only performs positioning measurements of PRS resources within the PRS measurement window. The UE should not accumulate PRS measurements obtained during the configured PRS measurement window with PRS measurements obtained outside of the configured PRS measurement window.

[0161] Figure 11 An example method 1100 of wireless communication in accordance with aspects of the present disclosure is illustrated. In one aspect, method 1100 may be performed by a RAN node (e.g., a satellite-based TRP).

[0162] At 1110, the RAN node sends a PRS offset configuration to the location server, the PRS offset configuration indicating at least one or more parameters specifying a timing offset, a frequency offset, or both, of one or more PRS resources to be sent by the RAN node, where the timing offset is relative to a PRS time offset point within a frame, subframe, or time slot of the RAN node, where the PRS time offset point is configured to at least one UE (e.g., in positioning assistance data) to indicate a transmission time of one or more PRS resources relative to the start of a frame, subframe, or time slot, where the frequency offset is relative to a PRS frequency offset point within the frequency range of the RAN node, and where the PRS frequency offset point is configured to at least one UE to indicate a transmission frequency of one or more PRS resources relative to the frequency range of the RAN node. In one aspect, operation 1110 may be performed by one or more WWAN transceivers 350, one or more network transceivers 380, one or more processors 384, memory 386, and / or positioning component 388, any one or all of which may be considered components for performing the operation.

[0163] At 1120, the RAN node sends one or more PRS resources to at least one UE based at least on the timing offset, the frequency offset, or both. In one aspect, operation 1120 may be performed by one or more WWAN transceivers 350, one or more network transceivers 380, one or more processors 384, memory 386, and / or positioning component 388, any one or all of which may be considered components for performing the operation.

[0164] As will be appreciated, a technical advantage of method 1100 is improved security of the network-verified location of at least one UE.

[0165] In the foregoing detailed description, it can be seen that different features are grouped together in the various examples. This manner of disclosure should not be construed as an intention that the example clauses have more features than those expressly recited in each clause. On the contrary, various aspects of the present disclosure may include less than all of the features of the individual example clauses disclosed. Accordingly, the following clauses are hereby considered incorporated into the description, where each clause by itself may serve as a separate example. Although each dependent clause may refer in the clause to a particular combination with one of the other clauses, the aspects of that dependent clause are not limited to the particular combination. It should be understood that other example clauses may also include combinations of aspects of dependent clauses with the subject matter of any other dependent clause or independent clause or combinations of any feature with other dependent clauses and independent clauses. The various aspects disclosed herein expressly include such combinations, unless expressly stated or readily inferable that a particular combination is not intended to be used (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). Additionally, it is contemplated that aspects of the clauses may be included in any other independent clause, even if the clause does not directly depend on the independent clause.

[0166] Specific example embodiments are described in the following numbered clauses:

[0167] Clause 1. A method of wireless communication performed by a radio access network (RAN) node, the method comprising: sending a positioning reference signal (PRS) offset configuration to a location server, the PRS offset configuration indicating at least one or more parameters specifying a timing offset, a frequency offset, or both of one or more PRS resources transmitted by the RAN node, wherein the timing offset is relative to a PRS time offset point within a frame, subframe, or time slot of the RAN node, wherein the PRS time offset point is configured to at least one user equipment (UE) to indicate a transmission time of the one or more PRS resources relative to a start of the frame, subframe, or time slot, wherein the frequency offset is relative to a PRS frequency offset point within a frequency range of the RAN node, and wherein the PRS frequency offset point is configured to the at least one UE to indicate a transmission frequency of the one or more PRS resources relative to the frequency range of the RAN node; and transmitting the one or more PRS resources to the at least one UE based at least on the timing offset, the frequency offset, or both.

[0168] Clause 2. The method according to clause 1, the method further comprising: receiving, from the location server, a request to apply the timing offset, the frequency offset, or both to the one or more PRS resources, wherein the PRS offset configuration is sent to the location server in response to the request.

[0169] Clause 3. The method according to Clause 2, wherein the request includes at least one of the one or more parameters.

[0170] Clause 4. The method according to any one of Clauses 1 to 3, wherein the one or more parameters include: the timing offset, the frequency offset or the amounts of both, and the duration of time during which the timing offset, the frequency offset or both are applied.

[0171] Clause 5. The method according to Clause 4, wherein the one or more parameters further include: a plurality of groups of PRS resources to which the timing offset, the frequency offset or both are applied, and an indication of how the timing offset, the frequency offset or both change from one group of PRS resources to another group of PRS resources among the plurality of groups of PRS resources.

[0172] Clause 6. The method according to Clause 5, wherein the indication of how the timing offset, the frequency offset or both change from one group of PRS resources to another group of PRS resources includes: a list of the timing offset, the frequency offset or both, and an indication of which timing offset, frequency offset or both in the list of the timing offset, the frequency offset or both is applied to which group of PRS resources among the plurality of groups of PRS resources.

[0173] Clause 7. The method according to any one of Clauses 4 to 6, wherein the duration of time is indicated as: a start time and a duration, or the start time and an end time.

[0174] Clause 8. The method according to Clause 7, wherein the start time, the duration and the end time are indicated as the number of frames, the number of sub - frames, the number of time slots, an absolute time or the number of PRS resource repetitions.

[0175] Clause 9. The method according to any one of Clauses 1 to 8, the method further includes: transmitting one or more second PRS resources at least according to a second timing offset different from the timing offset, a second frequency offset different from the frequency offset or both.

[0176] Clause 10. The method according to any one of Clauses 1 to 9, the method further includes: sending an indication of the start time and the duration of the transmission of the one or more PRS resources to the location server according to the timing offset, the frequency offset or both.

[0177] Clause 11. The method according to Clause 10, wherein the duration is indicated as the number of frames, the number of sub - frames, the number of time slots, an absolute time or the number of PRS resource repetitions.

[0178] Clause 12. The method according to any one of Clauses 1 to 11, wherein the RAN node comprises a satellite-based transmit-receive point (TRP).

[0179] Clause 13. A radio access network (RAN) node, the radio access network (RAN) node comprising: a memory; at least one transceiver; and at least one processor, the at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: send, via the at least one transceiver, a positioning reference signal (PRS) offset configuration to a location server, the PRS offset configuration indicating at least one or more parameters specifying a timing offset, a frequency offset, or both, of one or more PRS resources transmitted by the RAN node, wherein the timing offset is relative to a PRS time offset point within a frame, subframe, or time slot of the RAN node, wherein the PRS time offset point is configured to at least one user equipment (UE) to indicate a transmission time of the one or more PRS resources relative to a start of the frame, subframe, or time slot, wherein the frequency offset is relative to a PRS frequency offset point within a frequency range of the RAN node, and wherein the PRS frequency offset point is configured to the at least one UE to indicate a transmission frequency of the one or more PRS resources relative to the frequency range of the RAN node; and send, via the at least one transceiver, the one or more PRS resources to the at least one UE at least according to the timing offset, the frequency offset, or both.

[0180] Clause 14. The RAN node according to Clause 13, wherein the at least one processor is further configured to: receive, via the at least one transceiver, a request from the location server to apply the timing offset, the frequency offset, or both, to the one or more PRS resources, wherein the PRS offset configuration is sent to the location server in response to the request.

[0181] Clause 15. The RAN node according to Clause 14, wherein the request comprises at least one of the one or more parameters.

[0182] Clause 16. The RAN node according to any one of Clauses 13 to 15, wherein the one or more parameters comprise: an amount of the timing offset, the frequency offset, or both, and a duration of time during which the timing offset, the frequency offset, or both are applied.

[0183] Clause 17. The RAN node according to Clause 16, wherein the one or more parameters further include: multiple groups of PRS resources to which a timing offset, a frequency offset, or both are applied, and an indication of how the timing offset, the frequency offset, or both change from one group of PRS resources to another group of PRS resources among the multiple groups of PRS resources.

[0184] Clause 18. The RAN node according to Clause 17, wherein the indication of how the timing offset, the frequency offset, or both change from one group of PRS resources to another group of PRS resources includes: a list of the timing offset, the frequency offset, or both, and an indication of which timing offset, frequency offset, or both in the list is applied to which group of PRS resources among the multiple groups of PRS resources.

[0185] Clause 19. The RAN node according to any one of Clauses 16 to 18, wherein the duration of time is indicated as: a start time and a duration, or the start time and an end time.

[0186] Clause 20. The RAN node according to Clause 19, wherein the start time, the duration, and the end time are indicated as the number of frames, the number of sub - frames, the number of time slots, an absolute time, or the number of PRS resource repetitions.

[0187] Clause 21. The RAN node according to any one of Clauses 13 to 20, wherein the at least one processor is further configured to: transmit one or more second PRS resources via the at least one transceiver at least according to a second timing offset different from the timing offset, a second frequency offset different from the frequency offset, or both.

[0188] Clause 22. The RAN node according to any one of Clauses 13 to 21, wherein the at least one processor is further configured to: send an indication of the start time and the duration of the transmission of the one or more PRS resources to the location server via the at least one transceiver according to the timing offset, the frequency offset, or both.

[0189] Clause 23. The RAN node according to Clause 22, wherein the duration is indicated as the number of frames, the number of sub - frames, the number of time slots, an absolute time, or the number of PRS resource repetitions.

[0190] Clause 24. The RAN node according to any one of Clauses 13 to 23, wherein the RAN node includes a satellite - based transmit - receive point (TRP).

[0191] Clause 25. A radio access network (RAN) node, the radio access network (RAN) node comprising: means for sending a positioning reference signal (PRS) offset configuration to a location server, the PRS offset configuration indicating one or more parameters specifying at least a timing offset, a frequency offset, or both, of one or more PRS resources transmitted by the RAN node, wherein the timing offset is relative to a PRS time offset point within a frame, sub-frame, or time slot of the RAN node, wherein the PRS time offset point is configured to at least one user equipment (UE) to indicate a transmission time of the one or more PRS resources relative to a start of the frame, sub-frame, or time slot, wherein the frequency offset is relative to a PRS frequency offset point within a frequency range of the RAN node, and wherein the PRS frequency offset point is configured to the at least one UE to indicate a transmission frequency of the one or more PRS resources relative to the frequency range of the RAN node; and means for sending the one or more PRS resources to the at least one UE at least according to the timing offset, the frequency offset, or both.

[0192] Clause 26. The RAN node according to clause 25, the RAN node further comprising: means for receiving, from the location server, a request for applying the timing offset, the frequency offset, or both, to the one or more PRS resources, wherein the PRS offset configuration is sent to the location server in response to the request.

[0193] Clause 27. The RAN node according to clause 26, wherein the request comprises at least one parameter of the one or more parameters.

[0194] Clause 28. The RAN node according to any one of clauses 25 to 27, wherein the one or more parameters comprise: an amount of the timing offset, the frequency offset, or both, and a duration of time during which the timing offset, the frequency offset, or both are applied.

[0195] Clause 29. The RAN node according to clause 28, wherein the one or more parameters further comprise: a plurality of groups of PRS resources to which the timing offset, the frequency offset, or both are applied, and an indication of how the timing offset, the frequency offset, or both change from one group of PRS resources to another group of PRS resources among the plurality of groups of PRS resources.

[0196] Clause 30. The RAN node according to Clause 29, wherein the indication of how the timing offset, the frequency offset, or both change from one group of PRS resources to another group of PRS resources includes: a list of the timing offset, the frequency offset, or both, and an indication of which timing offset, frequency offset, or both in the list of the timing offset, the frequency offset, or both is applied to which group of PRS resources among the multiple groups of PRS resources.

[0197] Clause 31. The RAN node according to any one of Clauses 28 to 30, wherein the duration of time is indicated as: a start time and a duration, or the start time and an end time.

[0198] Clause 32. The RAN node according to Clause 31, wherein the start time, the duration, and the end time are indicated as the number of frames, the number of subframes, the number of time slots, an absolute time, or the number of PRS resource repetitions.

[0199] Clause 33. The RAN node according to any one of Clauses 25 to 32, the RAN node further includes: means for transmitting one or more second PRS resources at least according to a second timing offset different from the timing offset, a second frequency offset different from the frequency offset, or both.

[0200] Clause 34. The RAN node according to any one of Clauses 25 to 33, the RAN node further includes: means for sending an indication of the start time and the duration of the transmission of the one or more PRS resources to the location server according to the timing offset, the frequency offset, or both.

[0201] Clause 35. The RAN node according to Clause 34, wherein the duration is indicated as the number of frames, the number of subframes, the number of time slots, an absolute time, or the number of PRS resource repetitions.

[0202] Clause 36. The RAN node according to any one of Clauses 25 to 35, wherein the RAN node includes a satellite-based transmit-receive point (TRP).

[0203] Clause 37. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a radio access network (RAN) node, cause the RAN node to: send a positioning reference signal (PRS) offset configuration to a location server, the PRS offset configuration indicating one or more parameters specifying at least a timing offset, a frequency offset, or both, of one or more PRS resources transmitted by the RAN node, wherein the timing offset is relative to a PRS time offset point within a frame, subframe, or time slot of the RAN node, wherein the PRS time offset point is configured for at least one user equipment (UE) to indicate a transmission time of the one or more PRS resources relative to a start of the frame, subframe, or time slot, wherein the frequency offset is relative to a PRS frequency offset point within a frequency range of the RAN node, and wherein the PRS frequency offset point is configured for the at least one UE to indicate a transmission frequency of the one or more PRS resources relative to the frequency range of the RAN node; and transmit the one or more PRS resources to the at least one UE based at least on the timing offset, the frequency offset, or both.

[0204] Clause 38. The non-transitory computer-readable medium according to clause 37, the non-transitory computer-readable medium further comprising: computer-executable instructions that, when executed by the RAN node, cause the RAN node to: receive, from the location server, a request to apply the timing offset, the frequency offset, or both, to the one or more PRS resources, wherein the PRS offset configuration is sent to the location server in response to the request.

[0205] Clause 39. The non-transitory computer-readable medium according to clause 38, wherein the request includes at least one parameter of the one or more parameters.

[0206] Clause 40. The non-transitory computer-readable medium according to any one of clauses 37 to 39, wherein the one or more parameters include: an amount of the timing offset, the frequency offset, or both, and a duration of time during which the timing offset, the frequency offset, or both are applied.

[0207] Clause 41. The non-transitory computer-readable medium according to clause 40, wherein the one or more parameters further include: a plurality of groups of PRS resources to which the timing offset, the frequency offset, or both are applied, and an indication of how the timing offset, the frequency offset, or both change from one group of PRS resources to another group of PRS resources among the plurality of groups of PRS resources.

[0208] Clause 42. The non-transitory computer-readable medium according to Clause 41, wherein the indication of how the timing offset, the frequency offset, or both change from one group of PRS resources to another group of PRS resources includes: a list of the timing offset, the frequency offset, or both, and an indication of which timing offset, frequency offset, or both in the list is applied to which group of PRS resources among the multiple groups of PRS resources.

[0209] Clause 43. The non-transitory computer-readable medium according to any one of Clauses 40 to 42, wherein the duration of time is indicated as: a start time and a duration, or the start time and an end time.

[0210] Clause 44. The non-transitory computer-readable medium according to Clause 43, wherein the start time, the duration, and the end time are indicated as the number of frames, the number of sub-frames, the number of time slots, an absolute time, or the number of repetitions of PRS resources.

[0211] Clause 45. The non-transitory computer-readable medium according to any one of Clauses 37 to 44, the non-transitory computer-readable medium further comprising: computer-executable instructions that, when executed by the RAN node, cause the RAN node to transmit one or more second PRS resources at least according to a second timing offset different from the timing offset, a second frequency offset different from the frequency offset, or both.

[0212] Clause 46. The non-transitory computer-readable medium according to any one of Clauses 37 to 45, the non-transitory computer-readable medium further comprising: computer-executable instructions that, when executed by the RAN node, cause the RAN node to send an indication of the start time and the duration of the transmission of the one or more PRS resources to the location server according to the timing offset, the frequency offset, or both.

[0213] Clause 47. The non-transitory computer-readable medium according to Clause 46, wherein the duration is indicated as the number of frames, the number of sub-frames, the number of time slots, an absolute time, or the number of repetitions of PRS resources.

[0214] Clause 48. The non-transitory computer-readable medium according to any one of Clauses 37 to 47, wherein the RAN node includes a satellite-based transmit-receive point (TRP).

[0215] Those skilled in the art should understand that information and signals can be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may have been mentioned throughout the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0216] In addition, those skilled in the art should understand that the various illustrative logical blocks, modules, circuits, and algorithmic 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, the 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 upon the particular application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in different ways for each particular application, but such specific implementation decisions should not be construed as causing a departure from the scope of the present disclosure.

[0217] The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein can be implemented or executed with 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 in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as 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.

[0218] The methods, sequences, and / or algorithms described in connection with the aspects disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of both. 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, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, 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., a UE). In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

[0219] In one or more example aspects, the functions 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. The computer-readable medium includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. The storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may include 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 the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used herein, disk and disc include: compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0220] Although the foregoing disclosure shows illustrative aspects of the present disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the present disclosure as defined by the appended claims. Additionally, the functions, steps, and / or acts of the method claims according to aspects of the present disclosure described herein need not be performed in any particular order. Further, although elements of the present disclosure may be described or claimed in the singular, the plural is also contemplated unless expressly stated to be limited to the singular.

Claims

1. A method of wireless communication performed by a radio access network (RAN) node, the method comprising: Sending a positioning reference signal (PRS) offset configuration to a location server, the PRS offset configuration indicating at least one or more parameters specifying a timing offset, a frequency offset, or both of one or more PRS resources transmitted by the RAN node, wherein the timing offset is relative to a PRS time offset point within a frame, sub-frame, or time slot of the RAN node, wherein the PRS time offset point is configured to at least one user equipment (UE) to indicate a transmission time of the one or more PRS resources relative to a start of the frame, sub-frame, or time slot, wherein the frequency offset is relative to a PRS frequency offset point within a frequency range of the RAN node, and wherein the PRS frequency offset point is configured to the at least one UE to indicate a transmission frequency of the one or more PRS resources relative to the frequency range of the RAN node; And Sending the one or more PRS resources to the at least one UE at least according to the timing offset, the frequency offset, or both.

2. The method according to claim 1, the method further comprising: Receiving, from the location server, a request to apply the timing offset, the frequency offset, or both to the one or more PRS resources, wherein the PRS offset configuration is sent to the location server in response to the request.

3. The method according to claim 2, wherein the request includes at least one parameter of the one or more parameters.

4. The method according to claim 1, wherein the one or more parameters include: An amount of the timing offset, the frequency offset, or both, and A duration of time during which the timing offset, the frequency offset, or both are applied.

5. The method according to claim 4, wherein the one or more parameters further include: Multiple groups of PRS resources to which the timing offset, the frequency offset, or both are applied, and an indication of how the timing offset, the frequency offset, or both change from a PRS resource of one group of the multiple groups of PRS resources to a PRS resource of another group.

6. The method according to claim 5, wherein the indication of how the timing offset, the frequency offset, or both change from a PRS resource of one group to a PRS resource of another group includes: A list of the timing offset, the frequency offset, or both, and An indication of which timing offset, frequency offset, or both in the list are applied to which group of PRS resources of the multiple groups of PRS resources.

7. The method according to claim 4, wherein the duration of time is indicated as: A start time and a duration, or The start time and an end time.

8. The method according to claim 7, wherein the start time, the duration, and the end time are indicated as a number of frames, a number of sub-frames, a number of time slots, an absolute time, or a number of PRS resource repetitions.

9. The method according to claim 1, the method further comprising: Transmitting one or more second PRS resources based at least on a second timing offset different from the timing offset, a second frequency offset different from the frequency offset, or both.

10. The method according to claim 1, the method further comprising: Sending an indication of a start time and a duration of the transmission of the one or more PRS resources to the location server based on the timing offset, the frequency offset, or both.

11. The method according to claim 10, wherein the duration is indicated as a number of frames, a number of subframes, a number of time slots, an absolute time, or a number of PRS resource repetitions.

12. The method according to claim 1, wherein the RAN node comprises a satellite-based transmit-receive point (TRP).

13. A radio access network (RAN) node, the radio access network (RAN) node 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: Send a positioning reference signal (PRS) offset configuration to a location server via the at least one transceiver, the PRS offset configuration indicating at least one or more parameters specifying a timing offset, a frequency offset, or both of one or more PRS resources transmitted by the RAN node, wherein the timing offset is relative to a PRS time offset point within a frame, subframe, or time slot of the RAN node, wherein the PRS time offset point is configured to at least one user equipment (UE) to indicate a transmission time of the one or more PRS resources relative to a start of the frame, subframe, or time slot, wherein the frequency offset is relative to a PRS frequency offset point within a frequency range of the RAN node, and wherein the PRS frequency offset point is configured to the at least one UE to indicate a transmission frequency of the one or more PRS resources relative to the frequency range of the RAN node; And Transmitting the one or more PRS resources to the at least one UE via the at least one transceiver based at least on the timing offset, the frequency offset, or both.

14. The RAN node according to claim 13, wherein the at least one processor is further configured to: Receive, via the at least one transceiver, a request from the location server for applying the timing offset, the frequency offset, or both to the one or more PRS resources, Wherein the PRS offset configuration is sent to the location server in response to the request.

15. The RAN node according to claim 14, wherein the request comprises at least one of the one or more parameters.

16. The RAN node according to claim 13, wherein the one or more parameters comprise: An amount of the timing offset, the frequency offset, or both, and A duration of time during which the timing offset, the frequency offset, or both are applied.

17. The RAN node according to claim 16, wherein the one or more parameters further include: Multiple groups of PRS resources to which a timing offset, a frequency offset, or both are applied, and an indication of how the timing offset, the frequency offset, or both change from one group of PRS resources to another group of PRS resources among the multiple groups of PRS resources.

18. The RAN node according to claim 17, wherein the indication of how the timing offset, the frequency offset, or both change from one group of PRS resources to another group of PRS resources includes: A list of the timing offset, the frequency offset, or both, and An indication of which timing offset, frequency offset, or both in the list are applied to which group of PRS resources among the multiple groups of PRS resources.

19. The RAN node according to claim 16, wherein the duration of time is indicated as: A start time and a duration, or The start time and an end time.

20. The RAN node according to claim 19, wherein the start time, the duration, and the end time are indicated as the number of frames, the number of sub - frames, the number of time slots, an absolute time, or the number of PRS resource repetitions.

21. The RAN node according to claim 13, wherein the at least one processor is further configured to: Transmit one or more second PRS resources via the at least one transceiver according to at least a second timing offset different from the timing offset, a second frequency offset different from the frequency offset, or both.

22. The RAN node according to claim 13, wherein the at least one processor is further configured to: Send, via the at least one transceiver, an indication of the start time and the duration of the transmission of the one or more PRS resources to the location server according to the timing offset, the frequency offset, or both.

23. The RAN node according to claim 22, wherein the duration is indicated as the number of frames, the number of sub - frames, the number of time slots, an absolute time, or the number of PRS resource repetitions.

24. The RAN node according to claim 13, wherein the RAN node includes a satellite - based transmit - receive point (TRP).

25. A radio access network (RAN) node, the radio access network (RAN) node comprising: A component for sending a positioning reference signal (PRS) offset configuration to a location server, the PRS offset configuration indicating one or more parameters specifying at least a timing offset, a frequency offset, or both of one or more PRS resources transmitted by the RAN node, wherein the timing offset is relative to a PRS time offset point within a frame, sub-frame, or time slot of the RAN node, wherein the PRS time offset point is configured to at least one user equipment (UE) to indicate a transmission time of the one or more PRS resources relative to a start of the frame, sub-frame, or time slot, wherein the frequency offset is relative to a PRS frequency offset point within a frequency range of the RAN node, and wherein the PRS frequency offset point is configured to the at least one UE to indicate a transmission frequency of the one or more PRS resources relative to the frequency range of the RAN node; and A component for transmitting the one or more PRS resources to the at least one UE at least according to the timing offset, the frequency offset, or both.

26. The RAN node according to claim 25, the RAN node further comprising: A component for receiving, from the location server, a request for applying the timing offset, the frequency offset, or both to the one or more PRS resources, wherein the PRS offset configuration is sent to the location server in response to the request.

27. The RAN node according to claim 26, wherein the request includes at least one parameter of the one or more parameters.

28. The RAN node according to claim 25, wherein the one or more parameters include: an amount of the timing offset, the frequency offset, or both, and a duration of time during which the timing offset, the frequency offset, or both are applied.

29. The RAN node according to claim 28, wherein the one or more parameters further include: a plurality of groups of PRS resources to which the timing offset, the frequency offset, or both are applied, and an indication of how the timing offset, the frequency offset, or both change from one group of PRS resources to another group of PRS resources among the plurality of groups of PRS resources.

30. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a radio access network (RAN) node, cause the RAN node to: Send a positioning reference signal (PRS) offset configuration to a location server, the PRS offset configuration indicating at least one or more parameters specifying a timing offset, a frequency offset, or both, of one or more PRS resources transmitted by the RAN node, wherein the timing offset is relative to a PRS time offset point within a frame, subframe, or time slot of the RAN node, wherein the PRS time offset point is configured to at least one user equipment (UE) to indicate a transmission time of the one or more PRS resources relative to a start of the frame, subframe, or time slot, wherein the frequency offset is relative to a PRS frequency offset point within a frequency range of the RAN node, and wherein the PRS frequency offset point is configured to the at least one UE to indicate a transmission frequency of the one or more PRS resources relative to the frequency range of the RAN node; and Transmit the one or more PRS resources to the at least one UE based at least on the timing offset, the frequency offset, or both.

Images