Core and radio access network signaling for overlap configuration recommendation and selection of sounding reference signals (SRS) for positioning

Abstract

Techniques for communication are disclosed. In an aspect, a location server sends, to a base station serving a user equipment (UE), a request for one or more transmit frequency hopping characteristics of an uplink positioning reference signal (UL-PRS) to be transmitted by the UE during a positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter of a frequency domain hop of the UL-PRS, and receiving, from the base station, a response indicating acceptance of the one or more transmit frequency hopping characteristics or a modified value of the one or more transmit frequency hopping characteristics.

Description

Background Art 1. Technical Field

[0002] Aspects of the present disclosure generally relate to wireless communications.

[0003] 2. Description of Related Technologies

[0004] Wireless communication systems have evolved over 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, many different types of wireless communication systems are in use, including cellular systems and Personal Communications Service (PCS) systems. Examples of known cellular systems include the cellular analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile Communications (GSM), and the like.

[0005] The fifth-generation (5G) wireless standard, known as New Radio (NR), enables higher data transfer speeds, a greater number of connections, and better coverage, among 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 Positioning Reference Signals (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, advances in PRS procedures and technologies, and high-density deployments of 5G, enable highly accurate positioning based on 5G. Summary of the Invention

[0006] The following presents a simplified summary of one or more aspects disclosed herein. Therefore, the following summary should neither be considered an exhaustive overview of all contemplated aspects nor be considered to identify key or critical elements related to all contemplated aspects or to delineate the scope associated with any particular aspect. Therefore, 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 presented below.

[0007] In one aspect, a method of communication performed by a location server includes: sending a request to a base station serving a user equipment (UE) for one or more transmit frequency hopping characteristics of an uplink positioning reference signal (UL-PRS) to be sent by the UE during a positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the UL-PRS; and receiving a response from the base station indicating acceptance of the one or more transmit frequency hopping characteristics or a modified value of the one or more transmit frequency hopping characteristics.

[0008] In one aspect, a method of wireless communication performed by a user equipment (UE) includes: receiving a request from one or more UEs for one or more transmit frequency hopping characteristics of a sidelink positioning reference signal (SL-PRS) to be sent by the UE during a sidelink positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the SL-PRS; and sending the SL-PRS to the one or more UEs, the SL-PRS being configured according to the one or more transmit frequency hopping characteristics or a modified value of the one or more transmit frequency hopping characteristics.

[0009] In one aspect, a location server includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: send, via the at least one transceiver, to a base station serving a user equipment (UE) a request for one or more transmit frequency hopping characteristics of an uplink positioning reference signal (UL-PRS) to be sent by the UE during a positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the UL-PRS; and receive, via the at least one transceiver, a response from the base station indicating acceptance of the one or more transmit frequency hopping characteristics or a modified value of the one or more transmit frequency hopping characteristics.

[0010] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, from one or more UEs via the at least one transceiver, a request for one or more transmit frequency hopping characteristics of a sidelink positioning reference signal (SL-PRS) to be sent by the UE during a sidelink positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the SL-PRS; and send, to the one or more UEs via the at least one transceiver, the SL-PRS being configured according to the one or more transmit frequency hopping characteristics or a modified value of the one or more transmit frequency hopping characteristics.

[0011] In one aspect, a location server includes: a component for sending a request to a base station serving a user equipment (UE) for one or more transmit frequency hopping characteristics of an uplink positioning reference signal (UL-PRS) to be sent by the UE during a positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the UL-PRS; and a component for receiving a response from the base station indicating acceptance of the one or more transmit frequency hopping characteristics or a modified value of the one or more transmit frequency hopping characteristics.

[0012] In one aspect, a user equipment (UE) includes: a component for receiving a request for one or more transmit frequency hopping characteristics of a sidelink positioning reference signal (SL-PRS) to be sent by the UE during a sidelink positioning session from one or more UEs, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the SL-PRS; and a component for sending the SL-PRS to the one or more UEs, the SL-PRS being configured according to the one or more transmit frequency hopping characteristics or a modified value of the one or more transmit frequency hopping characteristics.

[0013] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a location server, cause the location server to: send a request to a base station serving a user equipment (UE) for one or more transmit frequency hopping characteristics of an uplink positioning reference signal (UL-PRS) to be sent by the UE during a positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the UL-PRS; and receive a response from the base station indicating acceptance of the one or more transmit frequency hopping characteristics or a modified value of the one or more transmit frequency hopping characteristics.

[0014] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive, from one or more UEs, a request for one or more transmit frequency hopping characteristics of a sidelink positioning reference signal (SL-PRS) to be sent by the UE during a sidelink positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the SL-PRS; and send, to the one or more UEs, the SL-PRS configured according to the one or more transmit frequency hopping characteristics or a modified value of the one or more transmit frequency hopping characteristics.

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

[0016] The accompanying drawings are presented to aid in describing various aspects of the present disclosure and are provided solely for illustration and not limitation of the various aspects.

[0017] Figure 1 An example wireless communication system according to aspects of the present disclosure is illustrated.

[0018] Figure 2A 、 Figure 2B and Figure 2C Example wireless network structures according to aspects of the present disclosure are illustrated.

[0019] Figure 3A 、 Figure 3B and Figure 3C is a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.

[0020] Figure 4 Examples of various positioning methods supported in New Radio (NR) according to aspects of the present disclosure are illustrated.

[0021] Figure 5A and Figure 5B Various interesting scenarios for sidelink-only positioning or joint Uu and sidelink positioning according to aspects of the present disclosure are illustrated.

[0022] Figure 6 is a diagram illustrating an example frame structure according to aspects of the present disclosure.

[0023] Figure 7 is a diagram illustrating an example of overlapping bandwidth between hops according to aspects of the present disclosure.

[0024] Figure 8 is a diagram illustrating an example of a switching gap between hops according to aspects of the present disclosure.

[0025] Figure 9 is a diagram illustrating an example frequency hopping pattern of a sounding reference signal (SRS) for positioning according to aspects of the present disclosure.

[0026] Figure 10 is a diagram illustrating an example positioning information exchange process according to aspects of the present disclosure.

[0027] Figure 11A and Figure 11B A table showing fields of a "Requested SRS Transmission Characteristics" information element (IE) according to aspects of the present disclosure is illustrated.

[0028] Figure 12 An example “NR-Multi-RTT-TargetDeviceErrorCauses” IE in accordance with aspects of the present disclosure is illustrated.

[0029] Figure 13 and Figure 14 Example communication methods according to aspects of the present disclosure are illustrated. DETAILED DESCRIPTION

[0030] Various aspects of the present disclosure are provided below in the description and related drawings of various examples provided for illustrative purposes. Alternative aspects may be designed 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 to avoid making the relevant details of the present disclosure difficult to understand.

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

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

[0033] In addition, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be appreciated that the various actions described herein may be performed by specific circuits (e.g., application specific integrated circuits (ASICs)), by program instructions executed by one or more processors, or by a combination of the two. Additionally, the sequences of actions described herein may be viewed as being fully embodied within any form of non-transitory computer-readable storage medium having stored therein a corresponding set of computer instructions that, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Accordingly, various aspects of the present disclosure may be embodied in a variety of different forms, all of which are contemplated to be within the scope of the claimed subject matter. In addition, for each of the various aspects described herein, the corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions."

[0034] Various aspects generally relate to transmit frequency hopping performed by a UE. Some aspects more specifically relate to specifying transmit frequency hopping characteristics of positioning reference signals transmitted by the UE, such as a sounding reference signal (SRS) for positioning and a sidelink positioning reference signal (SL-PRS). In some examples, for SRS for positioning, a location server requests a specific frequency domain overlap configuration for SRS frequency hopping from a serving base station. The serving base station may respond with a recommended overlap configuration, and the location server may transmit the configuration to one or more other base stations that are expected to measure SRS. In some examples, the base station may report whether the requested frequency domain overlap is acceptable or whether a different frequency domain overlap is preferred.

[0035] In some examples, for SL-PRS, one or more receiver-side link UEs may request a specific SL-PRS frequency hopping overlap configuration from a transmitter-side link UE. In some examples, if the transmitter UE receives recommendations for SL-PRS overlap configurations from multiple UEs, the transmitter UE may select a single overlap for transmission of the SL-PRS.

[0036] Certain aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by requesting specific transmit frequency hopping characteristics for positioning reference signals sent by a UE, the described techniques can be used to enable a location server to share the transmit frequency hopping characteristics with other base stations that intend to measure positioning reference signals, thereby improving the accuracy of their measurements. In some examples, by requesting specific transmit frequency hopping characteristics for positioning reference signals sent by a UE, the described techniques can be used to enable a receiver-side link UE to specify the transmit frequency hopping characteristics that it can measure.

[0037] 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 over a wireless communication network (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a consumer asset location device, a wearable device (e.g., a smart watch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.). A 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 an "access terminal" or "AT", "client device", "wireless device", "subscriber device", "subscriber terminal", "subscriber station", "user terminal" or "UT", "mobile device", "mobile terminal", "mobile station" or variations thereof. In general, a 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 connecting to the core network and / or the Internet are also possible for the UE, such as through a wired access network, a wireless local area network (WLAN) network (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.), etc.

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

[0039] The term "base station" may refer to a single physical transmit receive point (TRP) or multiple physical TRPs that may or may not be co-located. For example, where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to the cell (or several cell sectors) of the base station. Where the term "base station" refers to multiple co-located physical TRPs, the physical TRP may be an antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a 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 may be a serving base station that receives measurement reports from a UE and a neighboring base station whose reference radio frequency (RF) signal the UE is measuring. Because, as used herein, a TRP is a point at which a base station transmits and receives wireless signals, references to transmitting from a base station or receiving at a base station should be understood to refer to a specific TRP of a base station.

[0040] In some implementations of supporting UE positioning, a base station may not support wireless access by the UE (e.g., may not support data, voice, and / or signaling connections for the UE), but may instead transmit a reference signal to the UE to be measured by the UE and / or may receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., when transmitting a signal to the UE) and / or as a position measurement unit (e.g., when receiving and measuring a signal from the UE).

[0041] An "RF signal" comprises 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 transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply as a "signal" where the context clearly indicates that the term "signal" refers to either a wireless signal or an RF signal.

[0042] Figure 1An example wireless communication system 100 according to various 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 macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macrocell base stations may include eNBs and / or ng-eNBs (where the wireless communication system 100 corresponds to an LTE network), or gNBs (where the wireless communication system 100 corresponds to an NR network), or a combination of the two, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0043] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) via backhaul links 122. The base stations 102 may also 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 servers 172 may be part of the core network 170 or external to the core network 170. The location servers 172 may be integrated with the base stations 102. The UE 104 may communicate with the location servers 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, communication between UE 104 and location server 172 may be represented as an indirect connection (e.g., through core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with intermediate nodes (if any) omitted from the signaling diagram for clarity.

[0044] Among other functions, the base stations 102 may perform functions related to one or more of the following: delivering 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., through EPC / 5GC) over a backhaul link 134, which may be wired or wireless.

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

[0046] Although the geographic coverage areas 110 of adjacent macrocell base stations 102 may partially overlap (e.g., in a handover area), some areas of the geographic coverage areas 110 may substantially overlap with the larger geographic coverage area 110. For example, a small cell base station 102' (labeled "SC" for "small cell") may have a geographic coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a Home eNB (HeNB), which may provide service to a restricted group called a Closed Subscriber Group (CSG).

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

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

[0049] The small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell base station 102' can adopt LTE or NR technology and use the same 5 GHz unlicensed spectrum used by the WLAN AP 150. The small cell base station 102' using LTE / 5G in the unlicensed spectrum can improve the coverage of the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum can be referred to as NR-U. LTE in the unlicensed spectrum can be referred to as LTE-U, License Assisted Access (LAA), or MulteFire.

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

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

[0052] The transmit beams can be quasi-co-located, meaning that they appear to the receiver (e.g., UE) to have the same parameters, regardless of whether the network node's own transmit antennas 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 about the second reference RF signal on the second beam can be derived based on information about the source reference RF signal on the source beam. Thus, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type D, the receiver may use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.

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

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

[0055] Note that depending on the entity forming the "downlink" beam, the beam can be either a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to transmit a reference signal to the 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 either a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, the uplink beam is an uplink receive beam, while if the UE is forming an uplink beam, the uplink beam is an uplink transmit beam.

[0056] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, 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 portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with reference to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0057] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0058] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used herein, the term "sub-6 GHz" or the like may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that if used herein, the term "millimeter wave" or the like may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or may be within the EHF band.

[0059] 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) used by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common 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) that 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 may contain only necessary signaling information and signals. For example, since the primary uplink carrier and the primary downlink carrier are generally 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 is true for the uplink primary 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 a carrier frequency / component carrier through which a base station communicates, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. can be used interchangeably.

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

[0061] The wireless communication system 100 may also include a UE 164 that may communicate with the macrocell base station 102 via a communication link 120 and / or with the mmW base station 180 via a mmW communication link 184. For example, the macrocell base station 102 may support a PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0062] In some cases, UE 164 and UE 182 are capable of sidelink communication. Sidelink-capable UEs (SL-UEs) can communicate with base station 102 via communication link 120 using a Uu interface (i.e., the air interface between the UE and the base station). SL-UEs (e.g., UE 164, UE 182) can also communicate directly with each other via a wireless sidelink 160 using a PC5 interface (i.e., the air interface between sidelink-capable UEs). A wireless sidelink (or simply "sidelink") is an adaptation of a core cellular network (e.g., LTE, NR) standard that allows direct communication between two or more UEs without going through a 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 utilizing sidelink communication may be located within the geographic coverage area 110 of the base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of the base station 102 or unable to receive transmissions from the base station 102 for other reasons. In some cases, each group of SL-UEs communicating 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 the sidelink communication. In other cases, the sidelink communication is performed between the SL-UEs without involving the base station 102.

[0063] 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. A "medium" may include one or more time, frequency, and / or spatial communication resources associated with wireless communications between one or more transmitter / receiver pairs (e.g., encompassing 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 frequency band shared between various RATs. While different licensed frequency 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 (particularly those employing small cell access points) have recently expanded operations into unlicensed frequency bands such as the Unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technologies (most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include different variations of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and the like.

[0064] Note that although Figure 1 Only two of these UEs are illustrated as SL-UEs (i.e., UE 164 and UE 182), but any of the illustrated UEs may be SL-UEs. Furthermore, while only UE 182 is described as capable of beamforming, any of the illustrated UEs (including UE 164) may be capable of beamforming. Where SL-UEs are capable of beamforming, they may beamform toward each other (i.e., toward other SL-UEs), toward other UEs (e.g., UE 104), toward a base station (e.g., base station 102, base station 180, small cell 102′, access point 150), and so forth. Thus, in some cases, UE 164 and UE 182 may utilize beamforming via sidelink 160.

[0065] exist Figure 1 In the example of FIG, the UE illustrated (for simplicity, Figure 1Any UE (shown as a single UE 104 in FIG) can receive a signal 124 from one or more Earth-orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SVs 112 can be part of a satellite positioning system that the UEs 104 can use as an independent source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SVs 112) positioned to enable a receiver (e.g., a UE 104) to determine its position on or above the Earth based, at least in part, on positioning signals (e.g., signals 124) received from the transmitters. Such transmitters typically transmit a signal with a repeating pseudorandom noise (PN) code marked with a set number of chips. While typically located in the SVs 112, the transmitters can sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. The UEs 104 can include one or more dedicated receivers specifically designed to receive the signal 124 in order to derive geographic location information from the SVs 112.

[0066] In a satellite positioning system, the use of signal 124 may be enhanced by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential corrections, and the like, such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multifunctional Satellite Augmentation System (MSAS), the Global Positioning System (GPS)-Assisted Geo-Augmented Navigation, or the GPS and Geo-Augmented Navigation System (GAGAN), among others. Thus, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0067] In one aspect, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, SV 112 connects to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn connects to elements in the 5G network, such as a modified base station 102 (without a ground antenna) or a network node in a 5GC. This element, in turn, provides access to other elements in the 5G network and ultimately provides access to entities outside the 5G network, such as Internet web servers and other user devices. Thus, instead of or in addition to communication signals from terrestrial base station 102, UE 104 can receive communication signals (e.g., signal 124) from SV 112.

[0068] The wireless communication system 100 may also include one or more UEs, such as UE 190, that are indirectly connected to one or more communication networks via one or more device-to-device (D2D) or peer-to-peer (P2P) links (referred to as “side links”). Figure 1 In the example of FIG1 , UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through the D2D P2P link), and has a D2D P2P link 194 with WLAN STA 152 connected to WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through the D2D P2P link). In one example, 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), wait.

[0069] Figure 2A An example wireless network architecture 200 is illustrated. For example, 5GC 210 (also known as the Next Generation Core (NGC)) can be functionally considered to include control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.), which operate in conjunction to form the core network. A user plane interface (NG-U) 213 and a control plane interface (NG-C) 215 connect gNBs 222 to 5GC 210, and specifically to user plane functions 212 and control plane functions 214, respectively. In additional configurations, ng-eNBs 224 can also connect to 5GC 210 via NG-C 215 to control plane functions 214 and NG-U 213 to user plane functions 212. Furthermore, ng-eNBs 224 can communicate directly with gNBs 222 via backhaul connections 223. In some configurations, the next generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of ng-eNBs 224 and gNBs 222. Either gNB 222 or ng-eNB 224 (or both) may communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0070] Another optional aspect may include a location server 230 that can communicate with the 5GC 210 to provide location assistance for the UE 204. The location server 230 can 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 can each correspond to a single server. The location server 230 can be configured to support one or more location services for the UE 204 that can be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). In addition, the location server 230 can be integrated into a component of the core network, or alternatively can be external to the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0071] Figure 2B Another example wireless network structure 240 is illustrated. 5GC 260 (which may correspond to Figure 2AThe 5GC 210 in the network can be functionally considered as a control plane function provided by the access and mobility management function (AMF) 264 and a user plane function provided by the user plane function (UPF) 262, which operate in conjunction to form the core network (i.e., the 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 of the UEs described herein) and a session management function (SMF) 266, a transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between the UE 204 and a short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and receives intermediate keys established as a result of the UE 204 authentication process. In case of UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM) based authentication, the AMF 264 retrieves security material from the AUSF. The functionality of the AMF 264 also includes Security Context Management (SCM). The SCM receives keys from the SEAF, which the SCM uses to derive access network specific keys. The functionality of the AMF 264 also includes location service management for regulatory services, for transmission of location service messages between the UE 204 and the Location Management Function (LMF) 270 (which acts as the location server 230), for transmission of location service messages between the NG-RAN 220 and the LMF 270, for allocation of Evolved Packet System (EPS) bearer identifiers for interoperation with EPS, and UE 204 mobility event notifications. In addition, the AMF 264 also supports functionality for non-3GPP (3rd Generation Partnership Project) access networks.

[0072] The functions of the UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), 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, user plane quality of service (QoS) handling (e.g., uplink / downlink rate enforcement, reflective QoS marking in downlink), uplink traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in 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 delivery of location service messages between the UE 204 and a location server (such as the SLP 272) on the user plane.

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

[0074] Another optional aspect may include an LMF 270 that can communicate with the 5GC 260 to provide location assistance for the UE 204. The LMF 270 can 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, each can correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can connect to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not shown). The SLP 272 may support similar functionality to the LMF 270, but whereas the LMF 270 may communicate with the AMF 264, the NG-RAN 220, and the UE 204 on a control plane (e.g., using interfaces and protocols intended to carry signaling messages rather than voice or data), the SLP 272 may communicate with the UE 204 and external clients (e.g., third-party servers 274) on a user plane (e.g., using protocols intended to carry voice and / or data, such as the Transmission Control Protocol (TCP) and / or IP).

[0075] Yet another optional aspect may include a third-party server 274 that can communicate with the LMF 270, SLP 272, 5GC 260 (e.g., via the AMF 264 and / or UPF 262), NG-RAN 220, and / or 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 servers 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.

[0076] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and AMF 264, respectively, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220. The interface between the gNB 222 and / or ng-eNB 224 and the AMF 264 is referred to as the "N2" interface, while the interface between the gNB 222 and / or ng-eNB 224 and the UPF 262 is referred to as the "N3" interface. The gNBs 222 and / or ng-eNBs 224 of the NG-RAN 220 can communicate directly with each other via a backhaul connection 223, referred to as an "Xn-C" interface. One or more of the gNBs 222 and / or ng-eNBs 224 can communicate with one or more UEs 204 over a wireless interface, referred to as a "Uu" interface.

[0077] The functionality of a gNB 222 is divided between a gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DUs) 228, and one or more gNB Radio Units (gNB-RUs) 229. The gNB-CU 226 is a logical node that includes base station functions, including delivery of user data, mobility control, radio access network sharing, positioning, session management, and more, in addition to those functions specifically assigned to the gNB-DU 228. More specifically, the gNB-CU 226 typically hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols for the gNB 222. The gNB-DU 228 is a logical node that typically hosts the Radio Link Control (RLC) and Medium Access Control (MAC) layers for 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-DUs 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of the gNB 222 is typically hosted by one or more independent gNB-RUs 229, which perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU 228 and the gNB-RU 229 is referred to as the "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC, SDAP, and PDCP layers, with the gNB-DU 228 via the RLC and MAC layers, and with the gNB-RU 229 via the PHY layer.

[0078] The deployment of a communication system such as a 5G NR system can be arranged in a variety of ways using various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element or a network equipment (such as a base station or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5GNB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also known as a standalone base station or a single-chip base station) or a decomposed base station.

[0079] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A decomposed 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, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

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

[0081] Figure 2C An example disaggregated base station architecture 250 according to aspects of the present disclosure is illustrated. Disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CUs 226), which may communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via backhaul links, or indirectly with the core network 267 through one or more disaggregated base station units (e.g., 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). CUs 280 may communicate with one or more distributed units (DUs) 285 (e.g., gNB-DUs 228) via corresponding midhaul links (e.g., an F1 interface). DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via corresponding fronthaul links. The RUs 287 can communicate with corresponding UEs 204 via one or more radio frequency (RF) access links. In some implementations, a UE 204 can be served by multiple RUs 287 simultaneously.

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

[0083] 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 be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 280. The CU 280 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some 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 unit may communicate bidirectionally with the CU-CP unit 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 signal transmission.

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

[0085] Lower layer functionality may be implemented by one or more RUs 287. In some deployments, a RU 287 controlled by a DU 285 may correspond to a logical node that hosts RF processing functionality or low PHY layer functionality (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 287 may be implemented to handle over-the-air (OTA) communications with one or more UEs 204. In some implementations, both real-time and non-real-time aspects of control and user plane communications with the RU 287 may be controlled by the corresponding DU 285. In some scenarios, this configuration may enable the implementation of the DU 285 and CU 280 in a cloud-based RAN architecture (such as a vRAN architecture).

[0086] The SMO framework 255 can be configured to support RAN deployment and provisioning of both non-virtualized 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, which can be managed via an operations and maintenance interface (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 Open Cloud (O-Cloud) 269) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, CU 280, DU 285, RU 287, and near-RT RIC 259. In some implementations, the SMO framework 255 can communicate with hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 261) via the O1 interface. Additionally, in some implementations, the SMO framework 255 can communicate directly with one or more RUs 287 via the O1 interface. The SMO framework 255 may also include a non-RT RIC 257 configured to support the functionality of the SMO framework 255 .

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

[0088] In some implementations, the non-RT RIC 257 may receive parameters or external enrichment information from an external server to generate an AI / ML model to be deployed in the near-RT RIC 259. Such information may be utilized by the near-RT RIC 259 and may 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 RAN behavior or performance. For example, the non-RT RIC 257 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions through the SMO framework 255 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0089] Figure 3A 、 Figure 3B and Figure 3C Several example components (represented by corresponding blocks) are illustrated 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 thereof). Figure 2A and Figure 2B The depicted NG-RAN 220 and / or 5GC 210 / 260 infrastructure, such as a dedicated network, is implemented to support operations as described herein. It should be understood that these components can be implemented in different types of devices with different specific implementations (e.g., in an ASIC, in a system on a chip (SoC), etc.). The illustrated components can also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. In addition, 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.

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

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

[0092] At least in some cases, UE 302 and base station 304 also include satellite signal receivers 330 and 370. Satellite signal receivers 330 and 370 can be connected to one or more antennas 336 and 376, respectively, and can provide components for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. If satellite signal receivers 330 and 370 are satellite positioning system receivers, satellite positioning / communication signals 338 and 378 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. If satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, satellite positioning / communication signals 338 and 378 can be communication signals (e.g., carrying control and / or user data) originating from a 5G network. Satellite signal receiver 330 and satellite signal receiver 370 may include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and satellite positioning / communication signals 378, respectively. Satellite signal receiver 330 and satellite signal receiver 370 may optionally request 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 determine the position of UE 302 and base station 304, respectively.

[0093] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, which provide means (e.g., means for transmitting, means for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, the 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, the 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 to communicate with other network entities 306 via one or more wired or wireless core network interfaces.

[0094] A transceiver can be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes transmitter circuitry (e.g., transmitter 314, transmitter 324, transmitter 354, transmitter 364) and receiver circuitry (e.g., receiver 312, receiver 322, receiver 352, receiver 362). In some implementations, a transceiver can be an integrated device (e.g., implementing transmitter circuitry and receiver circuitry in a single device), in some implementations can include separate transmitter circuitry and separate receiver circuitry, or in other implementations can be implemented in other ways. The transmitter circuitry and receiver circuitry of a wired transceiver (e.g., in some implementations, network transceiver 380 and network transceiver 390) can be coupled to one or more wired network interface ports. The wireless transmitter circuitry (e.g., transmitter 314, transmitter 324, transmitter 354, transmitter 364) may include or be coupled to multiple antennas (e.g., antenna 316, antenna 326, antenna 356, antenna 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform transmit "beamforming," as described herein. Similarly, the wireless receiver circuitry (e.g., receiver 312, receiver 322, receiver 352, receiver 362) may include or be coupled to multiple antennas (e.g., antenna 316, antenna 326, antenna 356, antenna 366), such as antenna arrays, which allow 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 can share the same multiple antennas (e.g., antenna 316, antenna 326, antenna 356, antenna 366), so that the corresponding device can only receive or only transmit at a given time, rather than both receive and transmit at the same time. The wireless transceivers (e.g., WWAN transceivers 310 and WWAN transceivers 350, short-range wireless transceivers 320 and short-range wireless transceivers 360) can also include a network listening module (NLM) for performing various measurements, etc.

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

[0096] UE 302, base station 304, and network entity 306 also include other components that can 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, as well as for providing other processing functionality. Thus, processors 332, 384, and 394 can provide means for processing, such as means for determining, means for computing, means for receiving, means for transmitting, means for indicating, and the like. In one aspect, processors 332, 384, and 394 can include, for example, one or more general-purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuits, or various combinations thereof.

[0097] UE 302, base station 304, and network entity 306, respectively, include memory circuitry implementing memory 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Thus, memories 340, 386, and 396 can provide means for storing, means for retrieving, means for maintaining, etc. In some cases, UE 302, base station 304, and network entity 306 can include positioning components 342, 388, and 398, respectively. Positioning components 342, 388, and 398 can be hardware circuitry that is part of or coupled to processors 332, 384, and 394, respectively, and that, when executed, causes UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, positioning 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, the positioning components 342, 388, and 398 can be memory modules stored in memories 340, 386, and 396, respectively, which, when executed by the processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, base station 304, and network entity 306 to perform the functionality described herein. Figure 3A Possible locations are illustrated for a location component 342, which can be, for example, part of one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or can be a standalone component. Figure 3B Possible locations are illustrated for a location component 388, which can be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or can be a standalone component. Figure 3C Possible locations are illustrated for a location component 398, which can be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or can be a standalone component.

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

[0099] In addition, the UE 302 includes a user interface 346 that provides means for providing indications to the 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, the base station 304 and the network entity 306 may also include a user interface.

[0100] Referring in more detail to the one or more processors 384, in the downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for the RRC layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. One or more processors 384 may provide: RRC layer functionality associated with broadcasting 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 (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0101] Transmitter 354 and receiver 352 may implement Layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / 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 coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to orthogonal frequency division multiplexing (OFDM) subcarriers, multiplexed with reference signals (e.g., pilots) in the time and / or frequency domain, and then combined 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 pre-decoded to generate multiple spatial streams. Channel estimates from a channel estimator can be used to determine the coding and modulation schemes and for spatial processing. The channel estimates can be derived based on a reference signal and / or channel condition feedback sent by the UE 302. Each spatial stream can then be provided to one or more different antennas 356. The transmitter 354 can modulate an RF carrier with the corresponding spatial stream for transmission.

[0102] At UE 302, receiver 312 receives the signal via its corresponding antenna 316. Receiver 312 recovers the information modulated onto the RF carrier and provides this 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 there are multiple spatial streams destined for UE 302, they can be combined by receiver 312 into a single OFDM symbol stream. Receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted 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.

[0103] In the downlink, one or more processors 332 provide demultiplexing between transport 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.

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

[0105] Channel estimates derived by a channel estimator from a reference signal or feedback sent by base station 304 may be used by transmitter 314 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by transmitter 314 may be provided to different antennas 316. Transmitter 314 may modulate an RF carrier with the corresponding spatial stream for transmission.

[0106] Uplink transmissions are processed at the base station 304 in a manner similar to that described in conjunction with the receiver functionality at the UE 302. The receiver 352 receives the signal through its respective antenna 356. The receiver 352 recovers the information modulated onto the RF carrier and provides the information to one or more processors 384.

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

[0108] For convenience, UE 302, base station 304 and / or network entity 306 Figure 3A 、 Figure 3B and Figure 3C1 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. In particular, 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 specific implementation of UE 302 may omit WWAN transceiver 310 (e.g., a wearable device or tablet or PC or laptop may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), or may omit short-range wireless transceiver 320 (e.g., only cellular, etc.), or may omit satellite signal receiver 330, or may omit sensor 344, etc. In another example, in Figure 3B In certain embodiments, a particular 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.

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

[0110] Figure 3A 、 Figure 3B and Figure 3C The components of can be implemented in various ways. In some implementations, Figure 3A 、 Figure 3B and Figure 3CThe components of the present invention 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 be combined with at least one memory component to store 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 appropriately configuring 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 appropriately configuring the processor components). In addition, 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 appropriately configuring the processor components). For simplicity, various operations, actions, and / or functions are described herein as being performed "by a UE," "by a base station," "by a 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 the UE302, base station 304, network entity 306, etc. (such as processors 332, 384, 394, transceivers 310, 320, 350 and 360, memories 340, 386 and 396, positioning components 342, 388 and 398, etc.).

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

[0112] Please note that Figure 3A The UE 302 illustrated in FIG3 may represent a “low-level” UE or an “advanced” UE. As further described below, although low-level UEs and advanced UEs may have the same types of components (e.g., both may have a WWAN transceiver 310, a processing system 332, a memory component 340, etc.), these components may have different levels of functionality (e.g., increased or decreased performance, more or less capabilities, etc.), depending on whether the UE 302 corresponds to a low-level UE or an advanced UE.

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

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

[0115] 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)) sent by the UE to multiple base stations. Specifically, the UE sends one or more uplink reference signals, which are measured by a reference base station and multiple non-reference base stations. Each base station then reports the time of receipt of the reference signal (referred to as relative time of arrival (RTOA)) to a positioning entity (e.g., a location server) that knows the position and relative timing of the base stations involved. Based on the receive-to-receive (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 positions of the base stations, and their known timing offsets, the positioning entity can use TDOA to estimate the position of the UE.

[0116] For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink receive beams. The positioning entity uses the signal strength measurements and the angle of the receive 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 UE's position.

[0117] Downlink and uplink-based positioning methods include enhanced cell ID (E-CID) positioning and multiple round-trip time (RTT) positioning (also known as "multi-cell RTT" and "multi-RTT"). In the RTT process, a first entity (e.g., a base station or UE) sends a first RTT-related signal (e.g., a PRS or SRS) to a second entity (e.g., a UE or base station), and the second entity sends a second RTT-related signal (e.g., an SRS or 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 called the received-to-transmit (Rx-Tx) time difference. The Rx-Tx time difference measurement can be performed or adjusted to include only the time difference between the nearest time slot boundary of the received signal and the transmitted signal. The two entities can then transmit their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round-trip propagation time (i.e., RTT) between the two entities based on the two Rx-Tx time difference measurements (e.g., 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, which then 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, as illustrated in scenario 430, a first entity (e.g., a UE or base station) performs an RTT positioning procedure with multiple second entities (e.g., multiple base stations or UEs) to enable the first entity's position to be determined (e.g., using multilateration) based on the distances to the second entities and the known positions of the second entities. 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.

[0118] 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 of detected neighboring base stations, estimated timing, and signal strength. The UE's position is then estimated based on this information and the known locations of the base stations.

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

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

[0121] NR supports or implements various sidelink positioning technologies. Figure 5A Various scenarios of interest for sidelink-only positioning or joint Uu and sidelink positioning according to various aspects of the present disclosure are illustrated. In scenario 510, at least one peer UE with a known location can improve the Uu-based positioning (e.g., multi-cell RTT, downlink time difference of arrival (DL-TDOA), etc.) of a target UE by providing an additional anchor (e.g., using sidelink round trip time (RTT) (SL-RTT)). In scenario 520, a low-end (e.g., reduced capability or "RedCap") target UE can obtain assistance from an advanced UE to determine its position using, for example, sidelink positioning and ranging procedures with the advanced UE. Compared to the low-end UE, the advanced UE can have more capabilities, such as more sensors, faster processors, more memory, more antenna elements, higher transmit power capability, access to additional frequency bands, or any combination thereof. In scenario 530, a relay UE (e.g., with a known location) participates in the positioning estimate of the remote UE without performing uplink positioning reference signal (PRS) transmission over the Uu interface. Scenario 540 illustrates joint positioning of multiple UEs. Specifically, in scenario 540, two UEs with unknown locations can be jointly located under non-line-of-sight (NLOS) conditions by utilizing constraints from nearby UEs.

[0122] Figure 5B Additional interesting scenarios for sidelink-only positioning or joint Uu and sidelink positioning according to aspects of the present disclosure are illustrated. In scenario 550, UEs used for public safety (e.g., used by police, firefighters, etc.) can perform peer-to-peer (P2P) positioning and ranging for public safety and other purposes. For example, in scenario 550, public safety UEs can be out of coverage of the network and use sidelink positioning techniques to determine the position or relative distance and relative positioning between public safety UEs. Similarly, scenario 560 shows multiple UEs that are out of coverage and use sidelink positioning techniques (such as SL-RTT) to determine the position or relative distance and relative positioning.

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

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

[0125] 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 tones, bins, etc. Each subcarrier can be modulated with data. Generally speaking, modulation symbols are transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. 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 a system bandwidth of 1.25 megahertz (MHz), 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, the nominal Fast Fourier Transform (FFT) size may be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be divided into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, respectively.

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

[0127] exist Figure 6 In the example, a 15 kHz parameter set is used. Therefore, in the time domain, a 10 ms frame is divided into 10 equally sized subframes, each 1 ms, and each subframe includes one time slot. Figure 6 , 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.

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

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

[0130] A set of resource elements (REs) used for transmitting PRS is called a "PRS resource." A set of resource elements may span multiple PRBs in the frequency domain and N (such as one or more) consecutive symbols within a slot in the time domain. In a given OFDM symbol in the time domain, a PRS resource occupies consecutive PRBs in the frequency domain.

[0131] The transmission of PRS resources 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 comb size 'N', the PRS is transmitted in every Nth subcarrier of one symbol of the PRB. For example, for comb-4, for each symbol of the PRS resource configuration, the REs corresponding to every fourth subcarrier (such as subcarriers 0, 4, and 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 6 An example PRS resource configuration for comb-4 (which spans four symbols) is illustrated. That is, the positions of the shaded REs (labeled "R") indicate a comb-4 PRS resource configuration.

[0132] Currently, DL-PRS resources can span 2, 4, 6, or 12 consecutive symbols within a slot using a full frequency domain staggered pattern. DL-PRS resources can be configured in any downlink or flexible (FL) symbol in a slot that is configured by higher layers. There may be a constant energy per resource element (EPRE) for all REs of a given DL-PRS resource. The following are the symbol-by-symbol frequency offsets for comb sizes of 2, 4, 6, and 12 over 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 Figure 6 ); 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}.

[0133] A "PRS resource set" is a set of PRS resources used to transmit a PRS signal, 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 muting pattern configuration, and the same repetition factor (such as "PRS-ResourceRepetitionFactor") across time slots. The 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 may have a length selected from the following: 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 may have a length selected from {1, 2, 4, 6, 8, 16, 32} slots.

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

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

[0136] A "positioning frequency layer" (also referred to simply as a "frequency layer") is a collection of one or more PRS resource sets with the same values ​​for certain parameters across one or more TRPs. Specifically, the set of PRS resource sets 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 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 that specifies a pair of physical radio channels for transmission and reception. The downlink PRS bandwidth can have a granularity of four PRBs, with a minimum value of 24 PRBs and a maximum value of 272 PRBs. Currently, up to four frequency layers have been defined, and up to two PRS resource sets can be configured per frequency layer per TRP.

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

[0138] On the one hand, Figure 6The reference signals carried on the REs marked with an "R" in the figure may be SRSs. The SRSs transmitted by the UE can be used by the base station to obtain channel state information (CSI) for the transmitting UE. CSI describes how the RF signal propagates from the UE to the base station and represents the combined effects of scattering, attenuation, and power loss over distance. Systems use SRSs for resource scheduling, link adaptation, massive MIMO, beam management, and more.

[0139] The set of REs used for SRS transmission is called an "SRS resource" and can be identified by the parameter "SRS-ResourceId". The set of resource elements can span multiple PRBs in the frequency domain and 'N' (e.g., one or more) consecutive symbols within a time slot in the time domain. In a given OFDM symbol, an SRS resource occupies one or more consecutive PRBs. An "SRS resource set" is a group of SRS resources used for transmission of an SRS signal and is identified by an SRS resource set ID ("SRS-ResourceSetId").

[0140] The transmission of the SRS 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 SRS resource configuration. Specifically, for comb size 'N', the SRS is transmitted in every Nth subcarrier of one symbol of the PRB. For example, for comb-4, for each symbol of the SRS resource configuration, the REs corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) are used to transmit the SRS of the SRS resource. Figure 6 In the example of FIG, the illustrated SRS is comb-tooth-4 on four symbols. That is, the position of the shaded SRS RE indicates the SRS resource configuration of comb-tooth-4.

[0141] Currently, an SRS resource with a comb size of Comb-2, Comb-4, or Comb-8 can span 1, 2, 4, 8, or 12 consecutive symbols within a slot. The following are the symbol-by-symbol frequency offsets for the currently supported SRS comb patterns. 1 symbol Comb-2: {0}; 2 symbols Comb-2: {0,1}; 2 symbols Comb-4: {0,2}; 4 symbols Comb-2: {0,1,0,1}; 4 symbols Comb-4: {0,2,1,3} (as in Figure 6 ); 8-symbol comb-4: {0,2,1,3,0,2,1,3}; 12-symbol comb-4: {0,2,1,3,0,2,1,3,0,2,1,3}; 4-symbol comb-8: {0,4,2,6}; 8-symbol comb-8: {0,4,2,6,1,5,3,7}; and 12-symbol comb-8: {0,4,2,6,1,5,3,7,0,4,2,6}.

[0142] Generally speaking, as described above, the UE sends the SRS so that the receiving base station (serving base station or neighboring base station) can measure the channel quality (i.e., CSI) between the UE and the base station. However, the SRS can also be specifically configured as an uplink positioning reference signal for uplink-based positioning processes, such as uplink time difference of arrival (UL-TDOA), round-trip time (RTT), uplink angle of arrival (UL-AoA), etc. As used herein, the term "SRS" may refer to an SRS configured for channel quality measurement or an SRS configured for positioning purposes. When it is necessary to distinguish between two types of SRS, the former may be referred to herein as "SRS for communication" and / or the latter may be referred to as "SRS for positioning" or "SRS for positioning".

[0143] Several enhancements to the previously defined SRS have been proposed for "SRS for Positioning" (also known as "UL-PRS"), such as a new interleaving pattern within the SRS resource (in addition to a single symbol / comb-2), a new comb type for SRS, a new sequence for SRS, a larger number of SRS resource sets per component carrier, and a larger number of SRS resources per component carrier. In addition, the parameters "SpatialRelationInfo" and "PathLossReference" are to be configured based on the downlink reference signal or SSB from a neighboring TRP. Furthermore, one SRS resource may be sent outside the active BWP, and one SRS resource may span multiple component carriers. Moreover, the SRS may be configured in the RRC connected state and sent only within the active BWP. In addition, there may be no frequency hopping, no repetition factor, a single antenna port, and new lengths for the SRS (e.g., 8 and 12 symbols). There may also be open-loop power control and no closed-loop power control, and comb-8 (i.e., SRS sent every eighth subcarrier in the same symbol) may be used. Finally, a UE may transmit from multiple SRS resources through the same transmit beam for UL-AoA. All of these are features in addition to the current SRS framework, which is configured through RRC higher layer signaling (and potentially triggered or activated through MAC Control Element (MAC-CE) or Downlink Control Information (DCI).

[0144] It should be noted that the terms "positioning reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "positioning reference signal" and "PRS" 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" may 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 distinction is needed between the types of PRS, the downlink positioning reference signal may be referred to as a "DL-PRS," the uplink positioning reference signal (e.g., the SRS used for positioning, i.e., PTRS) may be referred to as a "UL-PRS," and the sidelink positioning reference signal may be referred to as a "SL-PRS." In addition, for signals that can be sent in the downlink, uplink, and / or sidelink (e.g., DMRS), these signals may be prefixed with "DL," "UL," or "SL" to distinguish the direction. For example, "UL-DMRS" may be different from "DL-DMRS."

[0145] UEs can be classified into "reduced capability" (RedCap) UEs (e.g., wearable devices such as smart watches, glasses, rings, etc.) and advanced UEs (e.g., smartphones, tablets, laptops, etc.). RedCap UEs may alternatively be referred to as low-level NR UEs, NR-light UEs, light UEs, NR ultra-light UEs, or ultra-light UEs. Advanced UEs may alternatively be referred to as full-capability UEs or simply UEs. Compared to Advanced UEs, RedCap UEs typically have lower baseband processing capabilities, fewer antennas (e.g., one receiver antenna as a baseline in FR1 or FR2, with two receiver antennas optional), lower operating bandwidth capabilities (e.g., 20 MHz for FR1 without supplemental uplink or carrier aggregation, or 50 MHz or 100 MHz for FR2), only half-duplex frequency division duplex (HD-FDD) capability, a smaller HARQ buffer, reduced physical downlink control channel (PDCCH) monitoring, restricted modulation (e.g., 64QAM for downlink and 16QAM for uplink), relaxed processing timeline requirements, and / or lower uplink transmit power. Different UE classes can be distinguished by UE category and / or UE capabilities. For example, certain types of UEs can be assigned a "RedCap" category (e.g., by the original equipment manufacturer (OEM), the applicable wireless communication standard, etc.), while other types of UEs can be assigned an "Advanced" category. Certain classes of UEs can also report their type (e.g., "RedCap" or "Advanced") to the network. Additionally, certain resources and / or channels may be dedicated to certain types of UEs.

[0146] It should be understood that the accuracy of RedCap UE positioning may be limited. For example, RedCap UE may operate on a reduced bandwidth, such as 5MHz to 20MHz for wearable devices and "relaxed" IoT devices (i.e., IoT devices with relaxed or lower capability parameters (such as lower throughput, relaxed latency requirements, lower energy consumption, etc.)), which results in lower positioning accuracy. As another example, the receive processing capabilities of the RedCap UE may be limited due to its lower RF / baseband cost. Therefore, the reliability of the measurement and positioning calculation will be reduced. In addition, such RedCap UE may not be able to receive multiple PRSs from multiple TRPs, further reducing the positioning accuracy. As yet another example, the transmit power of the RedCap UE may be reduced, which means that there will be lower quality uplink measurements for the RedCap UE positioning.

[0147] Advanced UEs typically have a larger form factor and are more expensive than RedCap UEs, and have more features and capabilities than RedCap UEs. For example, with respect to positioning, Advanced UEs can operate over the full PRS bandwidth (such as 100 MHz) and measure PRS from more TRPs than RedCap UEs, both of which result in higher positioning accuracy. As another example, the receive processing capabilities of Advanced UEs may be higher (e.g., faster) due to their higher-capability RF / baseband. Furthermore, the transmit power of Advanced UEs can be higher than that of RedCap UEs. This increases the reliability of measurements and positioning calculations.

[0148] The goal of further defining the capabilities of RedCap UEs is to specify support for positioning RedCap UEs. To this end, it has been agreed to introduce PRS and SRS frequency hopping for RedCap UEs. Specifically, it has been proposed to specify support for frequency hopping beyond the maximum RedCap UE bandwidth for receiving DL-PRS and transmitting SRS for positioning. In addition, it has been proposed to specify RRM requirements for positioning, including RRM measurements and procedures for RedCap UEs with and without frequency hopping.

[0149] In receive frequency hopping (also known as "receive bandwidth hopping," "frequency splicing," "bandwidth splicing," etc.), a signal (e.g., PRS) is transmitted across the full bandwidth (e.g., 272 PRBs for DL-PRS) in each time opportunity (e.g., symbol, time slot). For example, the TRP may transmit a comb-12 / 12 symbol DL-PRS resource continuously in each of the 272 PRBs in the PRS bandwidth. The UE may then measure different portions (e.g., different symbols) of the PRS resource in different subsets of the 272 PRBs (optionally, over a span of multiple time slots). The measured subset of consecutive PRBs in the frequency domain is called a "hop," and the UE "splices" together the measurements of the PRS resource in each PRB subset (i.e., each hop) to determine the final measurement of the PRS resource.

[0150] In transmit frequency hopping (also known as "transmit bandwidth hopping," etc.), a signal is transmitted over multiple time opportunities, and in each time opportunity (e.g., one or more symbols), a different subset of the total bandwidth of the signal is transmitted. For example, for a 100 MHz SRS, a UE may transmit the SRS across five 20 MHz hops, with each hop spanning one or more symbols of a time slot to cover the 100 MHz bandwidth of the SRS. Note that as used herein, the term "frequency hopping" (or "bandwidth hopping," etc.) may refer to transmit and / or receive frequency hopping, depending on the context.

[0151] Regarding frequency hopping for positioning SRS, potential enhancements to positioning SRS to enable transmit frequency hopping, including but not limited to partial overlap between hops, hop bandwidth, and time gaps between hops, are under study. Potential enhancements to DL-PRS to enable transmit or receive frequency hopping, including but not limited to the impact on processing power, hop bandwidth in the positioning frequency layer, time gaps between hops, measurement period, and partial overlap between hops, are also under study.

[0152] For the evaluation of transmit / receive frequency hopping for positioning of RedCap UEs, the value of the gap between two consecutive hops may be at least from 100 microseconds (μs) to 5 milliseconds (ms), but smaller values ​​are not excluded. In addition, for the evaluation of transmit / receive frequency hopping for positioning of RedCap UEs, the value of the UE speed may include 3 kilometers per hour (km / h), 30 km / h, or 60 km / h, but other values ​​are not excluded.

[0153] It has also been agreed that in order to support PRS frequency hopping and SRS frequency hopping for positioning of RedCap UEs, the complexity of the corresponding capabilities of RedCap UEs should be addressed in order to introduce appropriate capabilities for RedCap UEs.

[0154] Certain parameters for RedCap UE frequency hopping may be specified in applicable wireless communication standards (e.g., 3GPP standards). These parameters may include the maximum tolerable phase error, timing gap, and timing error between hops. These parameters may also include or depend on the type of positioning scenario, such as Industrial IoT (IIoT), commercial, public safety, and V2X, as well as UE capabilities. Standardized parameters may also include details about transmit and / or receive hopping patterns, including frequency domain overlap between hops (if supported).

[0155] Figure 7 FIG700 is a diagram illustrating an example of overlapping bandwidth between hops according to aspects of the present disclosure. FIG700 illustrates two 24-PRB PRS hops in the frequency domain. Each PRS hop may span one or two symbols of the same slot in the time domain. Figure 8 FIG8 is a diagram illustrating an example of a switching gap between hops according to aspects of the present disclosure. FIG800 illustrates two 24-PRB PRS hops in the frequency domain. Each PRS hop may span one or two symbols of the same slot in the time domain.

[0156] Figure 9 FIG. 9 is a diagram illustrating an example frequency hopping pattern for SRS for positioning according to aspects of the present disclosure. Figure 9In the example of , there are five single-symbol SRS hops, each separated by a symbol retuning time of two symbols (approximately 70 μs). Each hop spans 20 MHz for a total of approximately 100 MHz of sounding within the uplink timeslot.

[0157] The frequency hopping pattern for positioning SRS can be specified in different ways. In the RRC_CONNECTED state, positioning SRS resources are configured within the UE's active BWP. As a first option, frequency hopping for positioning SRS can use an UL-BWP switching method (meaning that a portion of the SRS is transmitted in each BWP). However, this can result in longer switching times and only a maximum of four BWPs exist.

[0158] As a second option, a positioning SRS can be defined that is associated with a component carrier other than the active BWP. In this case, a new switching gap will need to be introduced. As a first sub-option, SRS frequency hopping can use the SRS switching time for SRS carrier switching as a starting point. In this case, the switching time is selected from the set {0μs, 30μs, 100μs, 140μs, 200μs, 300μs, 500μs, 900μs}. As a second sub-option, SRS frequency hopping can use the switching time of SRS transmission in the RRC inactive state. In this case, the switching time is selected from the set {100μs, 140μs, 200μs, 300μs, 500μs}.

[0159] As a third option, the settling time of a phase-locked loop (PLL) is approximately 100 μs. However, there is also a fast frequency hopping feature for the PLL, where retuning can be even faster. Therefore, a coarse tuning framework similar to SRS carrier switching can be used, where the UE pre-tunes its PLL to each frequency block (hop) and stores the PLL tuning code in memory. During switching, the PLL tuning code is restored to provide faster switching.

[0160] Figure 10 FIG1000 is a diagram illustrating an example positioning information exchange procedure according to aspects of the present disclosure. LMF 270 may initiate a positioning information exchange procedure to request positioning information of a target UE from an NG-RAN node (e.g., gNB 222). The messages exchanged during the positioning information exchange procedure are New Radio Positioning Protocol Type A (NRPPa) messages because communication between LMF 270 and the NG-RAN node is via NRPPa.

[0161] like Figure 10As shown, the LMF 270 may initiate this procedure by transmitting a Positioning Information Request message to the NG-RAN node. If the "Requested SRS Transmission Characteristics" information element (IE) is included in the Positioning Information Request message, the NG-RAN node may consider this information when configuring SRS transmission for the UE, and it includes the "SRS Configuration" IE and the "SFN Initialization Time" IE in the Positioning Information Response message.

[0162] If both the "Spatial Relationship Information for Each SRS Resource" IE and the "Periodic List" IE are included in the "Requested SRS Transmission Characteristics" IE, the NG-RAN node is expected to consider the "Spatial Relationship for Each SRS Resource Item" IE and the "Periodic List Item" IE to have a one-to-one mapping relationship.

[0163] Figure 11A and Figure 11B Table 1100 illustrating fields of a "Requested SRS Transmission Characteristics" IE according to aspects of the present disclosure is illustrated. This IE contains requested SRS configuration parameters for a UE and may be included in a Positioning Information Request message to an NG-RAN node.

[0164] If the positioning procedure fails for some reason, the target UE may provide the error cause to the location server, e.g., LMF 270. For example, for a multi-RTT positioning procedure, the UE may use the "NR-Multi-RTT-TargetDeviceErrorCauses" IE to provide the multi-RTT error cause to the location server. Figure 12 An example "NR-Multi-RTT-TargetDeviceErrorCauses" IE 1200 according to aspects of the present disclosure is illustrated. As shown, the target UE may use this IE to report SRS-related errors (specifically, the "ul-srs-configuration-missing" value of the "cause" field).

[0165] The present disclosure provides a technique for signaling between the LMF and the gNB for positioning SRS frequency hopping configuration request and selection. In Phase 1, the LMF transmits a request for SRS transmission characteristics (or parameters) for SRS frequency hopping to the serving gNB. The requested transmission characteristics may include (1) whether to perform SRS frequency hopping, (2) how many hops to perform, (3) the recommended specific frequency domain overlap (e.g., Figure 7 ), and / or (4) the time domain gap between hops (as shown in Figure 8 shown).

[0166] The requested characteristics (parameters) may be included in a location information request message (e.g. Figure 1011 ). For example, one or more fields may be added to the "Requested SRS Transmission Characteristics" IE for (1) an on / off Boolean flag for SRS frequency hopping, (2) the number of hops, (3) the number of RBs for frequency domain overlap, and / or (4) the time domain gap between hops.

[0167] The "overlap configuration" (e.g., the number of RBs used for frequency domain overlap) may correspond to (or may be interpreted as) the minimum or maximum frequency domain overlap requested by the LMF, and the final overlap may be determined by the serving gNB. In some cases, the LMF may request SRS hopping with frequency domain overlap but does not indicate the amount of overlap (e.g., 1 RB, 2 RBs, sub-RBs, etc.).

[0168] Before requesting the SRS frequency hopping feature from the gNB, the LMF will need to receive the UE capabilities regarding SRS frequency hopping. The UE capabilities may include whether the UE supports frequency hopping for SRS and the amount of overlap for hopping SRS transmissions. The LMF may receive these capabilities from the UE via LPP (e.g., in an LPP Provide Capabilities message) or from the serving gNB via NRPPa.

[0169] In Phase 2, the serving gNB may respond with the same or different SRS transmission characteristics as the SRS frequency hopping configuration. This response may be included in the Positioning Information Response message.

[0170] The "overlap configuration" (e.g., the number of RBs used for frequency overlap) returned by the serving gNB may correspond to (or be interpreted as) the minimum or maximum frequency overlap recommended by the serving gNB, and the final selection may depend on the LMF. The LMF may take into account the frequency overlap that may have been provided by other gNBs. Due to different signal-to-noise ratios (SNRs) of SRS, different gNBs may require different overlaps.

[0171] In Phase 3, the LMF transmits the SRS frequency hopping configuration received from the gNB (in the Positioning Information Response message) to all remaining gNBs that are expected to measure SRS. As a first option, the LMF can configure different overlaps for different SRS resources for the same UE. More specifically, each SRS resource set can be associated with a specific path loss reference and / or spatial relation reference and configuration. When this occurs, it means that this particular SRS resource is expected to be measured by a specific set of neighboring TRPs. The LMF can then configure more or less overlap for such SRS resources compared to SRS resources expected to be measured for different TRP sets.

[0172] Another case is to have the same overlapping configuration for all SRS sets requested by the LMF.A third case of this first option is to allow the LMF to have the option of requesting different overlapping configurations for different SRS resources of the same set.

[0173] As a second option, the LMF is only allowed to configure a single overlay for all SRS resources across all SRS resource sets of a single UE.

[0174] In Phase 4, the gNB (neighboring or serving) may report to the location server whether a particular frequency domain overlap or other SRS frequency hopping transmission characteristic is acceptable (or even whether it can accept such an SRS characteristic), or whether a different value of the characteristic is preferred. This phase may optionally be performed before Phase 1.

[0175] Other gNBs may also report if there are errors related to the selected SRS frequency overlap or other SRS frequency hopping characteristics (e.g. Figure 12 For example, the error message may be "Insufficient SRS overlap" or "SRS overlap not configured".

[0176] Alternatively, there may be a separate reporting IE within the TRP measurement report. For example, along with timing measurements (e.g., Rx-Tx time difference, RTOA, etc.), the gNB may report an indication that SRS frequency overlap is insufficient or not configured, or an indication of the estimated quality of frequency hopping for multiple SRS hops, or some other error related to SRS frequency hopping.

[0177] The above techniques also apply to sidelink positioning and SL-PRS frequency hopping and partial overlap of transmission. In resource allocation mode 2 (where the transmitting UE autonomously selects / reserves resources on which to transmit the SL-PRS), one or more receiving sidelink UEs may request a specific SL-PRS frequency hopping overlap configuration from the transmitting sidelink UE. In the event that the transmitting UE receives recommendations for SL-PRS overlap configurations from multiple UEs, the transmitting UE may select a single overlap for SL-PRS transmission. For example, the transmitting UE may select the overlap configuration corresponding to the maximum overlap among the recommended overlaps. Similar techniques may be used for other SL-PRS frequency hopping characteristics.

[0178] Figure 13 Illustrated is an example communication method 1300 in accordance with aspects of the present disclosure. In one aspect, the method 1300 may be performed by a location server (eg, LMF 270).

[0179] At 1310, the location server sends a request to a base station (e.g., gNB 222) serving a UE (e.g., a RedCap UE) for one or more transmit frequency hopping characteristics of a UL-PRS (e.g., a positioning SRS) to be transmitted by the UE during a positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the UL-PRS. In an aspect, operation 1310 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which may be considered means for performing the operation.

[0180] At 1320, the location server receives a response from the base station indicating acceptance of the one or more transmit frequency hopping characteristics or the modified value of the one or more transmit frequency hopping characteristics. In an aspect, operation 1320 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which may be considered means for performing the operation.

[0181] It should be understood that the technical advantage of method 1300 is that by requesting specific transmission frequency hopping characteristics of the positioning reference signal sent by the UE, the location server can share the transmission frequency hopping characteristics with other base stations that expect to measure the positioning reference signal, thereby improving the accuracy of its measurement.

[0182] Figure 14 An example method 1400 of wireless communication in accordance with aspects of the present disclosure is illustrated. In an aspect, the method 1400 may be performed by a UE (eg, any of the UEs described herein).

[0183] At 1410, the UE receives a request from one or more UEs for one or more transmit frequency hopping characteristics of a SL-PRS to be transmitted by the UE during a sidelink positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the SL-PRS. In an aspect, operation 1410 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered means for performing the operation.

[0184] At 1420, the UE transmits a SL-PRS to one or more UEs, the SL-PRS being configured according to one or more transmit frequency hopping characteristics or modified values ​​of one or more transmit frequency hopping characteristics. In one aspect, operation 1420 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered means for performing the operation.

[0185] It will be appreciated that a technical advantage of method 1400 is that by requesting specific transmit frequency hopping characteristics for positioning reference signals transmitted by the UE, receiver-side link UEs can specify transmit frequency hopping characteristics that they can measure.

[0186] In the above detailed description, it can be seen that different features are grouped together in each example. This disclosure should not be understood as an intention that the example clauses have more features than the features explicitly mentioned in each clause. On the contrary, the various aspects of the present disclosure may include less than all the features of the disclosed individual example clauses. Therefore, the following clauses should be considered to be incorporated into the description accordingly, wherein each clause itself can be used as a separate example. Although each dependent clause may refer to a specific combination of a clause with one of the other clauses in a clause, the aspects of the dependent clause are not limited to a specific combination. It should be understood that other example clauses may also include a combination of the dependent clause aspects with the subject matter of any other dependent clause or independent clause or a combination of any feature with other dependent clauses and independent clauses. The various aspects disclosed herein explicitly include these combinations, unless explicitly expressed or can be easily inferred that a specific combination is not intended to be used (for example, contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). In addition, it is also expected that various aspects of a clause may be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

[0187] Specific implementation examples are described in the following numbered clauses:

[0188] Clause 1. A method of communication performed by a location server, the method comprising: sending a request to a base station serving a user equipment (UE) for one or more transmit frequency hopping characteristics of an uplink positioning reference signal (UL-PRS) to be sent by the UE during a positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the UL-PRS; and receiving a response from the base station indicating acceptance of the one or more transmit frequency hopping characteristics or a modified value of the one or more transmit frequency hopping characteristics.

[0189] Clause 2. The method of clause 1, wherein the one or more transmit frequency hopping characteristics further comprise: an indication of whether transmit frequency hopping is requested for the UL-PRS, a number of the frequency domain hops of the UL-PRS, a time domain gap between the frequency domain hops of the UL-PRS, or any combination thereof.

[0190] Clause 3. The method of any of clauses 1 to 2, wherein the one or more transmit frequency hopping characteristics are included in a requested SRS transmit characteristics information element (IE).

[0191] Clause 4. The method of any one of clauses 1 to 3, wherein the frequency domain overlap parameter indicates: a minimum requested frequency domain overlap, or a maximum requested frequency domain overlap.

[0192] Clause 5. The method of clause 4, wherein the response comprises a selected frequency domain overlap that is greater than or equal to the minimum requested frequency domain overlap, or a selected frequency domain overlap that is less than or equal to the maximum requested frequency domain overlap.

[0193] Clause 6. The method of any one of clauses 1 to 5, further comprising: receiving a capability message indicating that the UE is capable of transmit frequency hopping, frequency domain overlapping of frequency domain hopping, or both.

[0194] Clause 7. The method of clause 6, wherein the capability message is received from: the UE via Long Term Evolution (LTE) Positioning Protocol (LPP) or from the base station via New Radio Positioning Protocol Type A (NRPPa).

[0195] Clause 8. The method of any one of clauses 1 to 7, wherein the frequency domain overlap parameter does not include a frequency domain overlap amount of the frequency domain hopping of the UL-PRS.

[0196] Clause 9. The method of any one of clauses 1 to 8, wherein the response indicates: minimum frequency domain overlap, or maximum frequency domain overlap.

[0197] Clause 10. The method of clause 9, further comprising: selecting a frequency domain overlap that is greater than or equal to the minimum frequency domain overlap or less than or equal to the maximum frequency domain overlap.

[0198] Clause 11. A method according to any one of clauses 1 to 10, the method further comprising: sending a second request to the base station for one or more second transmit frequency hopping characteristics of a second UL-PRS to be sent by the UE, wherein the one or more second transmit frequency hopping characteristics are different from the one or more transmit frequency hopping characteristics.

[0199] Clause 12. The method of clause 11, wherein the one or more second transmit frequency hopping characteristics are different from the one or more transmit frequency hopping characteristics based on the second UL-PRS being transmitted to a different set of base stations than the UL-PRS.

[0200] Clause 13. A method according to any one of clauses 11 to 12, wherein the second frequency domain overlapping parameter of the frequency domain hop of the second UL-PRS is: the same as the frequency domain overlapping parameter of the frequency domain hop of the UL-PRS, or different from the frequency domain overlapping parameter of the frequency domain hop of the UL-PRS.

[0201] Clause 14. A method according to any one of clauses 1 to 13, the method further comprising: sending the one or more transmit frequency hopping characteristics or the modified values ​​of the one or more transmit frequency hopping characteristics to one or more other base stations expected to measure the UL-PRS during the positioning session.

[0202] Clause 15. The method of clause 14, further comprising: receiving an indication that the values ​​of the one or more transmit frequency hopping characteristics are acceptable or an indication of a preferred value for at least one of the one or more transmit frequency hopping characteristics from at least one of the one or more other base stations expected to measure the UL-PRS during the positioning session.

[0203] Clause 16. The method of any of clauses 1 to 15, further comprising receiving an error message related to the one or more transmit frequency hopping characteristics from at least one base station intended to measure the UL-PRS during the positioning session.

[0204] Clause 17. A method according to any one of clauses 1 to 16, the method further comprising: receiving a measurement report from at least one base station expected to measure the UL-PRS during the positioning session, the measurement report comprising a timing measurement of the UL-PRS and an error message related to the one or more transmit frequency hopping characteristics or a quality estimate of the measurement of the frequency domain hopping of the UL-PRS.

[0205] Clause 18. A method as described in any of clauses 1 to 17, wherein the UE is a reduced capability (RedCap) UE.

[0206] Clause 19. The method of any of clauses 1 to 18, wherein the UL-PRS comprises a sounding reference signal (SRS) for positioning.

[0207] Clause 20. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving from one or more UEs a request for one or more transmit frequency hopping characteristics of a sidelink positioning reference signal (SL-PRS) to be sent by the UE during a sidelink positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the SL-PRS; and sending the SL-PRS to the one or more UEs, the SL-PRS being configured according to the one or more transmit frequency hopping characteristics or a modified value of the one or more transmit frequency hopping characteristics.

[0208] Clause 21. The method of clause 20, wherein: the one or more UEs include a plurality of UEs, and the modified values ​​of the one or more transmit frequency hopping characteristics are selected based on requested transmit frequency hopping characteristics from the plurality of UEs.

[0209] Clause 22. A method according to any one of clauses 20 to 21, wherein: the one or more UEs include a plurality of UEs, and the value of the frequency domain overlap parameter is selected based on the maximum overlap among the requested frequency domain overlap parameters from the plurality of UEs.

[0210] Clause 23. A location server, comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: send, via the at least one transceiver, to a base station serving a user equipment (UE) a request for one or more transmit frequency hopping characteristics of an uplink positioning reference signal (UL-PRS) to be sent by the UE during a positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the UL-PRS; and receive, via the at least one transceiver, from the base station a response indicating acceptance of the one or more transmit frequency hopping characteristics or a modified value of the one or more transmit frequency hopping characteristics.

[0211] Clause 24. The location server of clause 23, wherein the one or more transmit frequency hopping characteristics further comprise: an indication of whether transmit frequency hopping for the UL-PRS is requested, a number of the frequency domain hops for the UL-PRS, a time domain gap between the frequency domain hops for the UL-PRS, or any combination thereof.

[0212] Clause 25. The location server of any of clauses 23 to 24, wherein the one or more transmit frequency hopping characteristics are included in a requested SRS transmit characteristics information element (IE).

[0213] Clause 26. The location server of any one of clauses 23 to 25, wherein the frequency domain overlap parameter indicates: a minimum requested frequency domain overlap, or a maximum requested frequency domain overlap.

[0214] Clause 27. The location server of clause 26, wherein the response comprises a selected frequency domain overlap that is greater than or equal to the minimum requested frequency domain overlap or a selected frequency domain overlap that is less than or equal to the maximum requested frequency domain overlap.

[0215] Clause 28. A location server according to any of clauses 23 to 27, wherein the at least one processor is further configured to: receive, via the at least one transceiver, a capability message indicating that the UE is capable of transmit frequency hopping, frequency domain overlapping of frequency domain hopping, or both.

[0216] Clause 29. The location server of clause 28, wherein the capability message is received from: the UE via Long Term Evolution (LTE) Positioning Protocol (LPP) or from the base station via New Radio Positioning Protocol Type A (NRPPa).

[0217] Clause 30. The location server of any of clauses 23 to 29, wherein the frequency domain overlap parameter does not include a frequency domain overlap amount of the frequency domain hops of the UL-PRS.

[0218] Clause 31. The location server of any one of clauses 23 to 30, wherein the response indicates: a minimum frequency domain overlap, or a maximum frequency domain overlap.

[0219] Clause 32. The location server of clause 31, wherein the at least one processor is further configured to select a frequency domain overlap that is greater than or equal to the minimum frequency domain overlap or less than or equal to the maximum frequency domain overlap.

[0220] Clause 33. A location server according to any one of clauses 23 to 32, wherein the at least one processor is further configured to: send a second request to the base station via the at least one transceiver for one or more second transmit frequency hopping characteristics of a second UL-PRS to be sent by the UE, wherein the one or more second transmit frequency hopping characteristics are different from the one or more transmit frequency hopping characteristics.

[0221] Clause 34. The location server of clause 33, wherein the one or more second transmit frequency hopping characteristics are different from the one or more transmit frequency hopping characteristics based on the second UL-PRS being transmitted to a different set of base stations than the UL-PRS.

[0222] Clause 35. A location server according to any one of clauses 33 to 34, wherein the second frequency domain overlap parameter of the frequency domain hop of the second UL-PRS is: the same as the frequency domain overlap parameter of the frequency domain hop of the UL-PRS, or different from the frequency domain overlap parameter of the frequency domain hop of the UL-PRS.

[0223] Clause 36. A location server according to any one of clauses 23 to 35, wherein the at least one processor is further configured to: send, via the at least one transceiver, the one or more transmit frequency hopping characteristics or the modified values ​​of the one or more transmit frequency hopping characteristics to one or more other base stations expected to measure the UL-PRS during the positioning session.

[0224] Clause 37. A location server according to clause 36, wherein the at least one processor is further configured to: receive, via the at least one transceiver, an indication that the values ​​of the one or more transmit frequency hopping characteristics are acceptable or an indication of a preferred value for at least one of the one or more transmit frequency hopping characteristics from at least one of the one or more other base stations expected to measure the UL-PRS during the positioning session.

[0225] Clause 38. A location server according to any one of clauses 23 to 37, wherein the at least one processor is further configured to: receive, via the at least one transceiver, an error message related to the one or more transmit frequency hopping characteristics from at least one base station expected to measure the UL-PRS during the positioning session.

[0226] Clause 39. A location server according to any one of clauses 23 to 38, wherein the at least one processor is further configured to: receive, via the at least one transceiver, a measurement report from at least one base station expected to measure the UL-PRS during the positioning session, the measurement report comprising a timing measurement of the UL-PRS and an error message related to the one or more transmit frequency hopping characteristics or a quality estimate of the measurement of the frequency domain hopping of the UL-PRS.

[0227] Clause 40. The location server of any of clauses 23 to 39, wherein the UE is a reduced capability (RedCap) UE.

[0228] Clause 41. The location server of any of clauses 23 to 40, wherein the UL-PRS comprises a sounding reference signal (SRS) for positioning.

[0229] Clause 42. A user equipment (UE), comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, from one or more UEs via the at least one transceiver, a request for one or more transmit frequency hopping characteristics of a sidelink positioning reference signal (SL-PRS) to be sent by the UE during a sidelink positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter of the frequency domain hopping of the SL-PRS; and send, to the one or more UEs via the at least one transceiver, the SL-PRS being configured according to the one or more transmit frequency hopping characteristics or a modified value of the one or more transmit frequency hopping characteristics.

[0230] Clause 43. The UE of clause 42, wherein: the one or more UEs include a plurality of UEs, and the modified values ​​of the one or more transmit frequency hopping characteristics are selected based on requested transmit frequency hopping characteristics from the plurality of UEs.

[0231] Clause 44. A UE according to any one of clauses 42 to 43, wherein: the one or more UEs include a plurality of UEs, and the value of the frequency domain overlap parameter is selected based on the maximum overlap among the requested frequency domain overlap parameters from the plurality of UEs.

[0232] Clause 45. A location server comprising: a component for sending a request to a base station serving a user equipment (UE) for one or more transmit frequency hopping characteristics of an uplink positioning reference signal (UL-PRS) to be sent by the UE during a positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the UL-PRS; and a component for receiving a response from the base station indicating acceptance of the one or more transmit frequency hopping characteristics or a modified value of the one or more transmit frequency hopping characteristics.

[0233] Clause 46. The location server of clause 45, wherein the one or more transmit frequency hopping characteristics further comprise: an indication of whether transmit frequency hopping for the UL-PRS is requested, a number of the frequency domain hops for the UL-PRS, a time domain gap between the frequency domain hops for the UL-PRS, or any combination thereof.

[0234] Clause 47. The location server of any of clauses 45 to 46, wherein the one or more transmit frequency hopping characteristics are included in a requested SRS transmit characteristics information element (IE).

[0235] Clause 48. The location server of any one of clauses 45 to 47, wherein the frequency domain overlap parameter indicates: a minimum requested frequency domain overlap, or a maximum requested frequency domain overlap.

[0236] Clause 49. The location server of clause 48, wherein the response comprises a selected frequency domain overlap that is greater than or equal to the minimum requested frequency domain overlap or a selected frequency domain overlap that is less than or equal to the maximum requested frequency domain overlap.

[0237] Clause 50. The location server of any of clauses 45 to 49, further comprising means for receiving a capability message indicating that the UE is capable of transmit frequency hopping, frequency domain overlapping of frequency domain hopping, or both.

[0238] Clause 51. The location server of clause 50, wherein the capability message is received from: the UE via Long Term Evolution (LTE) Positioning Protocol (LPP) or from the base station via New Radio Positioning Protocol Type A (NRPPa).

[0239] Clause 52. The location server of any of clauses 45 to 51, wherein the frequency domain overlap parameter does not include a frequency domain overlap amount of the frequency domain hops of the UL-PRS.

[0240] Clause 53. The location server of any one of clauses 45 to 52, wherein the response indicates: a minimum frequency domain overlap, or a maximum frequency domain overlap.

[0241] Clause 54. The location server of clause 53, further comprising: a component for selecting a frequency domain overlap that is greater than or equal to the minimum frequency domain overlap or less than or equal to the maximum frequency domain overlap.

[0242] Clause 55. A location server according to any one of clauses 45 to 54, the location server further comprising: a component for sending a second request to the base station for one or more second transmit frequency hopping characteristics of a second UL-PRS to be sent by the UE, wherein the one or more second transmit frequency hopping characteristics are different from the one or more transmit frequency hopping characteristics.

[0243] Clause 56. The location server of clause 55, wherein the one or more second transmit frequency hopping characteristics differ from the one or more transmit frequency hopping characteristics based on the second UL-PRS being transmitted to a different set of base stations than the UL-PRS.

[0244] Clause 57. A location server according to any one of clauses 55 to 56, wherein the second frequency domain overlap parameter of the frequency domain hop of the second UL-PRS is: the same as the frequency domain overlap parameter of the frequency domain hop of the UL-PRS, or different from the frequency domain overlap parameter of the frequency domain hop of the UL-PRS.

[0245] Clause 58. A location server according to any one of clauses 45 to 57, the location server further comprising: means for sending the one or more transmit frequency hopping characteristics or the modified values ​​of the one or more transmit frequency hopping characteristics to one or more other base stations expected to measure the UL-PRS during the positioning session.

[0246] Clause 59. A location server according to clause 58, the location server further comprising: a component for receiving, from at least one of the one or more other base stations expected to measure the UL-PRS during the positioning session, an indication that the values ​​of the one or more transmit frequency hopping characteristics are acceptable or an indication of a preferred value for at least one of the one or more transmit frequency hopping characteristics.

[0247] Clause 60. The location server of any of clauses 45 to 59, further comprising means for receiving an error message related to the one or more transmit frequency hopping characteristics from at least one base station expected to measure the UL-PRS during the positioning session.

[0248] Clause 61. A location server according to any of clauses 45 to 60, the location server further comprising: a component for receiving a measurement report from at least one base station expected to measure the UL-PRS during the positioning session, the measurement report comprising a timing measurement of the UL-PRS and an error message related to the one or more transmit frequency hopping characteristics or a quality estimate of the measurement of the frequency domain hopping of the UL-PRS.

[0249] Clause 62. The location server of any of clauses 45 to 61, wherein the UE is a reduced capability (RedCap) UE.

[0250] Clause 63. The location server of any of clauses 45 to 62, wherein the UL-PRS comprises a sounding reference signal (SRS) for positioning.

[0251] Clause 64. A user equipment (UE), comprising: a component for receiving, from one or more UEs, a request for one or more transmit frequency hopping characteristics of a sidelink positioning reference signal (SL-PRS) to be sent by the UE during a sidelink positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the SL-PRS; and a component for sending the SL-PRS to the one or more UEs, the SL-PRS being configured according to the one or more transmit frequency hopping characteristics or a modified value of the one or more transmit frequency hopping characteristics.

[0252] Clause 65. The UE of clause 64, wherein: the one or more UEs include a plurality of UEs, and the modified values ​​of the one or more transmit frequency hopping characteristics are selected based on requested transmit frequency hopping characteristics from the plurality of UEs.

[0253] Clause 66. A UE according to any one of clauses 64 to 65, wherein: the one or more UEs include a plurality of UEs, and the value of the frequency domain overlap parameter is selected based on the maximum overlap among the requested frequency domain overlap parameters from the plurality of UEs.

[0254] Clause 67. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a location server, cause the location server to: send a request to a base station serving a user equipment (UE) for one or more transmit frequency hopping characteristics of an uplink positioning reference signal (UL-PRS) to be sent by the UE during a positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the UL-PRS; and receive a response from the base station indicating acceptance of the one or more transmit frequency hopping characteristics or a modified value of the one or more transmit frequency hopping characteristics.

[0255] Clause 68. A non-transitory computer-readable medium according to clause 67, wherein the one or more transmit frequency hopping characteristics further include: an indication of whether transmit frequency hopping is requested for the UL-PRS, a number of the frequency domain hops of the UL-PRS, a time domain gap between the frequency domain hops of the UL-PRS, or any combination thereof.

[0256] Clause 69. The non-transitory computer-readable medium of any of clauses 67 to 68, wherein the one or more transmit frequency hopping characteristics are included in a requested SRS transmit characteristics information element (IE).

[0257] Clause 70. The non-transitory computer-readable medium of any one of clauses 67 to 69, wherein the frequency domain overlap parameter indicates: a minimum requested frequency domain overlap, or a maximum requested frequency domain overlap.

[0258] Clause 71. A non-transitory computer-readable medium according to clause 70, wherein the response comprises a selected frequency domain overlap that is greater than or equal to the minimum requested frequency domain overlap, or a selected frequency domain overlap that is less than or equal to the maximum requested frequency domain overlap.

[0259] Clause 72. A non-transitory computer-readable medium according to any one of clauses 67 to 71, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the location server, cause the location server to: receive a capability message indicating that the UE is capable of transmitting frequency hopping, frequency domain overlapping of frequency domain hopping, or both.

[0260] Clause 73. The non-transitory computer-readable medium of clause 72, wherein the capability message is received from: from the UE via Long Term Evolution (LTE) Positioning Protocol (LPP), or from the base station via New Radio Positioning Protocol Type A (NRPPa).

[0261] Clause 74. The non-transitory computer-readable medium of any one of clauses 67 to 73, wherein the frequency domain overlap parameter does not include a frequency domain overlap amount of the frequency domain hops of the UL-PRS.

[0262] Clause 75. The non-transitory computer-readable medium of any one of clauses 67 to 74, wherein the response indicates: minimum frequency domain overlap, or maximum frequency domain overlap.

[0263] Clause 76. The non-transitory computer-readable medium of clause 75, further comprising computer-executable instructions which, when executed by the location server, cause the location server to: select a frequency domain overlap that is greater than or equal to the minimum frequency domain overlap or less than or equal to the maximum frequency domain overlap.

[0264] Clause 77. A non-transitory computer-readable medium according to any one of clauses 67 to 76, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the location server, cause the location server to: send to the base station a second request for one or more second transmit hopping characteristics for a second UL-PRS to be sent by the UE, wherein the one or more second transmit hopping characteristics are different from the one or more transmit hopping characteristics.

[0265] Clause 78. The non-transitory computer-readable medium of clause 77, wherein the one or more second transmit frequency hopping characteristics are different from the one or more transmit frequency hopping characteristics based on the second UL-PRS being transmitted to a different set of base stations than the UL-PRS.

[0266] Clause 79. A non-transitory computer-readable medium according to any one of clauses 77 to 78, wherein the second frequency domain overlap parameter of the frequency domain hop of the second UL-PRS is: the same as the frequency domain overlap parameter of the frequency domain hop of the UL-PRS, or different from the frequency domain overlap parameter of the frequency domain hop of the UL-PRS.

[0267] Clause 80. A non-transitory computer-readable medium according to any one of clauses 67 to 79, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the location server, cause the location server to: send the one or more transmit frequency hopping characteristics or the modified values ​​of the one or more transmit frequency hopping characteristics to one or more other base stations expected to measure the UL-PRS during the positioning session.

[0268] Clause 81. A non-transitory computer-readable medium according to clause 80, wherein the non-transitory computer-readable medium further comprises computer-executable instructions that, when executed by the location server, cause the location server to: receive an indication that the values ​​of the one or more transmit frequency hopping characteristics are acceptable or an indication of a preferred value for at least one of the one or more transmit frequency hopping characteristics from at least one of the one or more other base stations expected to measure the UL-PRS during the positioning session.

[0269] Clause 82. A non-transitory computer-readable medium according to any one of clauses 67 to 81, wherein the non-transitory computer-readable medium further comprises computer-executable instructions that, when executed by the location server, cause the location server to: receive an error message related to the one or more transmit frequency hopping characteristics from at least one base station that is expected to measure the UL-PRS during the positioning session.

[0270] Clause 83. A non-transitory computer-readable medium according to any one of clauses 67 to 82, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the location server, cause the location server to: receive a measurement report from at least one base station expected to measure the UL-PRS during the positioning session, the measurement report comprising a timing measurement of the UL-PRS and an error message relating to the one or more transmit frequency hopping characteristics or a quality estimate of the measurement of the frequency domain hopping of the UL-PRS.

[0271] Clause 84. The non-transitory computer-readable medium of any one of clauses 67 to 83, wherein the UE is a reduced capability (RedCap) UE.

[0272] Clause 85. The non-transitory computer-readable medium of any of clauses 67 to 84, wherein the UL-PRS comprises a sounding reference signal (SRS) for positioning.

[0273] Clause 86. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive from one or more UEs a request for one or more transmit frequency hopping characteristics of a sidelink positioning reference signal (SL-PRS) to be sent by the UE during a sidelink positioning session, the one or more transmit frequency hopping characteristics comprising at least a frequency domain overlap parameter for frequency domain hopping of the SL-PRS; and send to the one or more UEs the SL-PRS configured according to the one or more transmit frequency hopping characteristics or a modified value of the one or more transmit frequency hopping characteristics.

[0274] Clause 87. A non-transitory computer-readable medium according to clause 86, wherein: the one or more UEs include a plurality of UEs, and the modified values ​​of the one or more transmit frequency hopping characteristics are selected based on requested transmit frequency hopping characteristics from the plurality of UEs.

[0275] Clause 88. A non-transitory computer-readable medium according to any one of clauses 86 to 87, wherein: the one or more UEs include multiple UEs, and the value of the frequency domain overlap parameter is selected based on the maximum overlap among the requested frequency domain overlap parameters from the multiple UEs.

[0276] Those skilled in the art will appreciate that information and signals can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0277] In addition, it will be understood by those skilled in the art that the various illustrative logic blocks, modules, circuits, and algorithmic steps described in conjunction with the various aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be interpreted as resulting in a departure from the scope of this disclosure.

[0278] The various illustrative logical blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or performed 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 components, 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. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.

[0279] The methods, sequences and / or algorithms described in conjunction with the various aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, 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 so that the processor can read information from the storage medium and write information to the storage medium. In an 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., UE). In an alternative, the processor and the storage medium may reside in the user terminal as discrete components.

[0280] In one or more example aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or codes on a computer-readable medium or sent via a computer-readable medium. Computer-readable media include both computer storage media and communication media, which include any media that facilitate the transfer of a computer program from one place to another. Storage media can be any available medium 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 devices, magnetic disk storage devices, or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of an instruction or data structure and that can be accessed by a computer. In addition, any connection is appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc. Disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0281] Although the foregoing disclosure illustrates exemplary 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. Furthermore, the functions, steps, and / or actions of the method claims according to the various aspects of the present disclosure described herein do not need to be performed in any particular order. Furthermore, although elements of the present disclosure may be described or claimed in the singular, plural forms are also contemplated unless explicitly stated to be limited to the singular.

Claims

1. A method of communication performed by a location server, the method comprising: sending, to a base station serving a user equipment (UE), a request for one or more transmit frequency hopping characteristics of an uplink positioning reference signal (UL-PRS) to be sent by the UE during a positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the UL-PRS; as well as A response is received from the base station indicating acceptance of the one or more transmit frequency hopping characteristics or the modified value of the one or more transmit frequency hopping characteristics.

2. The method of claim 1 , wherein the one or more transmit frequency hopping characteristics further comprise: an indication of whether to request transmission frequency hopping for the UL-PRS, the number of frequency domain hops of the UL-PRS, The time domain gap between the frequency domain hops of the UL-PRS, or Any combination of them. 3 . The method of claim 1 , wherein the one or more transmit frequency hopping characteristics are included in a requested SRS transmit characteristics information element (IE).

4. The method according to claim 1, wherein the frequency domain overlap parameter indicates: Minimum requested frequency domain overlap, or Maximum requested frequency domain overlap.

5. The method of claim 4, wherein the response comprises a frequency domain overlap selected from: The selected frequency domain overlap is greater than or equal to the minimum requested frequency domain overlap, or the selected frequency domain overlap is less than or equal to the maximum requested frequency domain overlap.

6. The method according to claim 1, further comprising: A capability message is received indicating that the UE is capable of transmitting frequency hopping, frequency domain overlapping with frequency domain hopping, or both.

7. The method of claim 6, wherein the capability message is received from: The UE may receive the positioning information via Long Term Evolution (LTE) Positioning Protocol (LPP) or the base station may receive the positioning information via New Radio Positioning Protocol Type A (NRPPa).

8. The method according to claim 1, wherein the frequency domain overlap parameter does not include a frequency domain overlap amount of the frequency domain hopping of the UL-PRS.

9. The method of claim 1 , wherein the response indicates: Minimum frequency domain overlap, or Maximum frequency domain overlap.

10. The method according to claim 9, further comprising: A frequency domain overlap that is greater than or equal to the minimum frequency domain overlap or less than or equal to the maximum frequency domain overlap is selected.

11. The method according to claim 1 , further comprising: A second request is sent to the base station for one or more second transmit frequency hopping characteristics for a second UL-PRS to be sent by the UE, wherein the one or more second transmit frequency hopping characteristics are different from the one or more transmit frequency hopping characteristics.

12. The method of claim 11, wherein the one or more second transmit frequency hopping characteristics are different from the one or more transmit frequency hopping characteristics based on the second UL-PRS being transmitted to a different set of base stations than the first UL-PRS.

13. The method according to claim 11, wherein a second frequency domain overlap parameter of the frequency domain hopping of the second UL-PRS is: The frequency domain overlapping parameter is the same as the frequency domain overlapping parameter of the frequency domain hopping of the UL-PRS, or is different from the frequency domain overlapping parameter of the frequency domain hopping of the UL-PRS.

14. The method according to claim 1, further comprising: The one or more transmit frequency hopping characteristics or the modified values ​​of the one or more transmit frequency hopping characteristics are transmitted to one or more other base stations that are expected to measure the UL-PRS during the positioning session.

15. The method according to claim 14, further comprising: An indication that the values ​​of the one or more transmit frequency hopping characteristics are acceptable or an indication of a preferred value for at least one of the one or more transmit frequency hopping characteristics is received from at least one of the one or more other base stations expected to measure the UL-PRS during the positioning session.

16. The method according to claim 1, further comprising: An error message related to the one or more transmit frequency hopping characteristics is received from at least one base station expected to measure the UL-PRS during the positioning session.

17. The method according to claim 1, further comprising: and receiving a measurement report from at least one base station intended to measure the UL-PRS during the positioning session, the measurement report including a timing measurement of the UL-PRS and an error message related to the one or more transmit frequency hopping characteristics or a quality estimate of the frequency-domain hopping measurements of the UL-PRS.

18. The method of claim 1, wherein the UE is a reduced capability (RedCap) UE.

19. The method of claim 1, wherein the UL-PRS comprises a sounding reference signal (SRS) for positioning.

20. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving, from one or more UEs, a request for one or more transmit frequency hopping characteristics of a sidelink positioning reference signal (SL-PRS) to be transmitted by the UEs during a sidelink positioning session, the one or more transmit frequency hopping characteristics comprising at least a frequency domain overlap parameter for frequency domain hopping of the SL-PRS; as well as The SL-PRS is sent to the one or more UEs, where the SL-PRS is configured according to the one or more transmit frequency hopping characteristics or the modified values ​​of the one or more transmit frequency hopping characteristics.

21. The method according to claim 20, wherein: The one or more UEs include a plurality of UEs, and The modified values ​​of the one or more transmit frequency hopping characteristics are selected based on requested transmit frequency hopping characteristics from the plurality of UEs.

22. The method of claim 20, wherein: The one or more UEs include a plurality of UEs, and The value of the frequency domain overlap parameter is selected based on a maximum overlap among the requested frequency domain overlap parameters from the plurality of UEs.

23. A location server, comprising: 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: transmitting, via the at least one transceiver, to a base station serving a user equipment (UE), a request for one or more transmit frequency hopping characteristics of an uplink positioning reference signal (UL-PRS) to be transmitted by the UE during a positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the UL-PRS; as well as A response is received from the base station via the at least one transceiver indicating acceptance of the one or more transmit frequency hopping characteristics or the modified value of the one or more transmit frequency hopping characteristics.

24. The location server of claim 23, wherein the one or more transmission frequency hopping characteristics further comprise: an indication of whether to request transmission frequency hopping for the UL-PRS, the number of frequency domain hops of the UL-PRS, The time domain gap between the frequency domain hops of the UL-PRS, or Any combination of them.

25. The location server of claim 23, wherein the at least one processor is further configured to: A capability message is received via the at least one transceiver indicating that the UE is capable of transmit frequency hopping, frequency domain overlapping of frequency domain hopping, or both.

26. The location server of claim 23, wherein the at least one processor is further configured to: A second request for one or more second transmit frequency hopping characteristics for a second UL-PRS to be sent by the UE is sent to the base station via the at least one transceiver, wherein the one or more second transmit frequency hopping characteristics are different from the one or more transmit frequency hopping characteristics.

27. The location server of claim 23, wherein the at least one processor is further configured to: The one or more transmit frequency hopping characteristics or the modified values ​​of the one or more transmit frequency hopping characteristics are transmitted via the at least one transceiver to one or more other base stations that are expected to measure the UL-PRS during the positioning session.

28. The location server of claim 23, wherein the at least one processor is further configured to: An error message related to the one or more transmit frequency hopping characteristics is received via the at least one transceiver from at least one base station intended to measure the UL-PRS during the positioning session.

29. The location server of claim 23, wherein the at least one processor is further configured to: and receiving, via the at least one transceiver, a measurement report from at least one base station intended to measure the UL-PRS during the positioning session, the measurement report comprising a timing measurement of the UL-PRS and an error message related to the one or more transmit frequency hopping characteristics or a quality estimate of the frequency-domain hopping measurements of the UL-PRS.

30. A user equipment (UE), comprising: 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: receiving, via the at least one transceiver, from one or more UEs a request for one or more transmit frequency hopping characteristics of a sidelink positioning reference signal (SL-PRS) to be transmitted by the UE during a sidelink positioning session, the one or more transmit frequency hopping characteristics including at least a frequency domain overlap parameter for frequency domain hopping of the SL-PRS; as well as The SL-PRS is transmitted to the one or more UEs via the at least one transceiver, the SL-PRS being configured according to the one or more transmit frequency hopping characteristics or modified values ​​of the one or more transmit frequency hopping characteristics.

Images