Non-cell-defined synchronization signal block (NCD-SSB) signaling for located neighbor cells

Abstract

Techniques for wireless communication are disclosed. In an aspect, a user equipment (UE) receives first configuration information of a first positioning reference signal (PRS) resource transmitted by a first neighboring transmit receive point (TRP), the first configuration information indicating a first quasi-co-location (QCL) relationship between the first PRS resource and a first synchronization signal block (SSB) transmitted by the first neighboring TRP, where the first SSB is a non-cell-defined SSB (NCD-SSB); and obtaining a first positioning measurement result of the first PRS resource based on a QCL relationship between the first PRS resource and an SSB transmitted by the first adjacent TRP.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to Greek Patent Application No. 20220100623, filed on August 1, 2022, entitled “SIGNALING FOR NEIGHBORING CELLS FOR POSITIONING”, which has been assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Background Art 1. Technical Field

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

[0005] 2. Description of related technologies

[0006] 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, wireless service with Internet capabilities, and fourth generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). There are many different types of wireless communication systems in use today, 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.

[0007] 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 reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technical enhancements compared to previous standards. These enhancements, along with the use of higher frequency bands, advances in PRS processes and technologies, and high-density deployments of 5G, enable high-precision positioning based on 5G. Summary of the invention

[0008] The following presents a simplified summary of the invention related to one or more aspects disclosed herein. Therefore, the following summary of the invention should neither be considered as an exhaustive overview related to all conceived aspects, nor should it be considered to identify key or decisive elements related to all conceived aspects or to delineate the scope associated with any particular aspect. Therefore, the sole purpose of the following summary of the invention is to present certain concepts related to one or more aspects of the mechanisms disclosed herein in a brief form before the detailed embodiments presented below.

[0009] In one aspect, a method for performing wireless communication by a user equipment (UE) includes: receiving first configuration information of a first positioning reference signal (PRS) resource sent by a first neighboring transmit reception point (TRP), the first configuration information indicating a first quasi-co-location (QCL) relationship between the first PRS resource and a first synchronization signal block (SSB) sent by the first neighboring TRP, wherein the first SSB is a non-cell-defined SSB (NCD-SSB); and obtaining a first positioning measurement result of the first PRS resource based on the QCL relationship between the first PRS resource and the SSB sent by the first neighboring TRP.

[0010] On the one hand, a method for performing wireless communication by a user equipment (UE) includes: receiving first configuration information of a first sounding reference signal (SRS) resource for positioning, the first configuration information indicating a first quasi-co-site (QCL) relationship between the first SRS resource for positioning and a first synchronization signal block (SSB) sent by a first adjacent transmit receive point (TRP), wherein the first SSB is a non-cell defined SSB (NCD-SSB); and sending the first SRS resource for positioning based on the QCL relationship between the first SRS resource for positioning and the SSB sent by the first adjacent TRP.

[0011] In one aspect, a user equipment (UE) includes: one or more memories; one or more transceivers; and one or more processors, the one or more processors being communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being configured individually or in combination to: receive, via the one or more transceivers, first configuration information of a first positioning reference signal (PRS) resource sent by a first neighboring transmit reception point (TRP), the first configuration information indicating a first quasi-co-location (QCL) relationship between the first PRS resource and a first synchronization signal block (SSB) sent by the first neighboring TRP, wherein the first SSB is a non-cell-defining SSB (NCD-SSB); and obtain a first positioning measurement result of the first PRS resource based on the QCL relationship between the first PRS resource and the SSB sent by the first neighboring TRP.

[0012] In one aspect, a user equipment (UE) includes: one or more memories; one or more transceivers; and one or more processors, the one or more processors being communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being configured individually or in combination to: receive, via the one or more transceivers, first configuration information of a first sounding reference signal (SRS) resource for positioning, the first configuration information indicating a first quasi-co-location (QCL) relationship between the first SRS resource for positioning and a first SSB sent by a first adjacent transmit receive point (TRP), wherein the first SSB is a non-cell defined SSB (NCD-SSB); and send, via the one or more transceivers, the first SRS resource for positioning based on the QCL relationship between the first SRS resource for positioning and the SSB sent by the first adjacent TRP.

[0013] In one aspect, a user equipment (UE) includes: a component for receiving first configuration information of a first positioning reference signal (PRS) resource sent by a first neighboring transmit reception point (TRP), the first configuration information indicating a first quasi-co-location (QCL) relationship between the first PRS resource and a first synchronization signal block (SSB) sent by the first neighboring TRP, wherein the first SSB is a non-cell-defined SSB (NCD-SSB); and a component for obtaining a first positioning measurement result of the first PRS resource based on the QCL relationship between the first PRS resource and the SSB sent by the first neighboring TRP.

[0014] In one aspect, a user equipment (UE) includes: a component for receiving first configuration information of a first sounding reference signal (SRS) resource for positioning, the first configuration information indicating a first quasi-co-location (QCL) relationship between the first SRS resource for positioning and a first SSB sent by a first adjacent transmit reception point (TRP), wherein the first SSB is a non-cell defined SSB (NCD-SSB); and a component for sending the first SRS resource for positioning based on the QCL relationship between the first SRS resource for positioning and the SSB sent by the first adjacent TRP.

[0015] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions, which when executed by a user equipment (UE) causes the UE to: receive first configuration information of a first positioning reference signal (PRS) resource sent by a first neighboring transmit reception point (TRP), the first configuration information indicating a first quasi-co-location (QCL) relationship between the first PRS resource and a first synchronization signal block (SSB) sent by the first neighboring TRP, wherein the first SSB is a non-cell-defined SSB (NCD-SSB); and obtain a first positioning measurement result of the first PRS resource based on the QCL relationship between the first PRS resource and the SSB sent by the first neighboring TRP.

[0016] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions, which when executed by a user equipment (UE) causes the UE to: receive first configuration information of a first sounding reference signal (SRS) resource for positioning, the first configuration information indicating a first quasi-co-location (QCL) relationship between the first SRS resource for positioning and a first SSB sent by a first adjacent transmit receive point (TRP), wherein the first SSB is a non-cell-defined SSB (NCD-SSB); and send the first SRS resource for positioning based on the QCL relationship between the first SRS resource for positioning and the SSB sent by the first adjacent TRP.

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

[0018] 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.

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

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

[0021] 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.

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

[0023] Figure 5 Example Long Term Evolution (LTE) Positioning Protocol (LPP) capability transfer procedures, assistance data transfer procedures, and location information transfer procedures between a target device and a location server according to aspects of the present disclosure are illustrated.

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

[0025] Figure 7 is a diagram illustrating various downlink channels within an example downlink time slot in accordance with aspects of the present disclosure.

[0026] Figure 8 Various aspects of radio resource control (RRC) bandwidth part (BWP) configuration for a reduced capability (RedCap) UE in accordance with aspects of the present disclosure are illustrated.

[0027] Fig. 9 is a diagram illustrating example relative frequency locations of various non-cell definition-synchronization signal block (NCD-SSB) based parameters in accordance with aspects of the present disclosure.

[0028] Fig.10 An example "BWP-DownlinkDedicated" RRC information element (IE) in accordance with aspects of the present disclosure is illustrated.

[0029] Fig.11 An example “nonCellDefiningSSB” RRC IE in accordance with aspects of the present disclosure is illustrated.

[0030] Fig.12 An example “NR-SSB-Config” LPP IE in accordance with aspects of the present disclosure is illustrated.

[0031] Fig.13 Various aspects of SSB association in LPP according to various aspects of the present disclosure are illustrated.

[0032] Fig.14 Various aspects of the technology that facilitates implementation of the present disclosure are illustrated according to various aspects of the present disclosure.

[0033] Fig.15 and Fig.16

[0013] Example methods of wireless communications in accordance with aspects of the present disclosure are illustrated. DETAILED DESCRIPTION

[0034] Various aspects of the present disclosure are provided in the following description and related drawings for various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of the present disclosure. In addition, 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.

[0035] 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.

[0036] Those skilled in the art will appreciate that any of a variety of different techniques and technologies 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 voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof, which depends in part on the specific application, in part on the desired design, in part on the corresponding technology, and so on.

[0037] In addition, many aspects are described in terms of a sequence of actions to be performed by, for example, an element of a computing device. It will be appreciated that the various actions described herein may be performed by a specific circuit (e.g., an application specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of the two. Additionally, the sequence of actions described herein may be considered to be fully embodied in any form of non-transient computer-readable storage medium, in which a corresponding computer instruction set is stored, which, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Therefore, various aspects of the present disclosure may be embodied in a variety of different forms, all of which have been 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."

[0038] 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 specific radio access technology (RAT). In general, a UE may be any wireless communication device (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, an augmented reality (AR) / virtual reality (VR) head-mounted device, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. A UE may be mobile or may be stationary (e.g., at certain times) and may communicate with a radio access network (RAN). As used herein, the term "UE" may be interchangeably referred to as an "access terminal" or "AT", "client device", "wireless device", "subscriber equipment", "subscriber terminal", "subscriber station", "user terminal" or "UT", "mobile device", "mobile terminal", "mobile station" or variations thereof. In general, a UE may communicate with a core network via a RAN, and through the core network, the UE may connect to external networks such as the Internet and to other UEs. Of course, other mechanisms are also possible for the UE to connect to the core network and / or the Internet, such as through a wired access network, a wireless local area network (WLAN) network (eg, based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.), etc.

[0039] A base station may operate according to one of several RATs to communicate with a UE, depending on the network in which the base station is deployed, and may alternatively be referred to as an access point (AP), a network node, a Node B, an evolved Node B (eNB), a next generation eNB (ng-eNB), a new radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be primarily used to support wireless access for UEs, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, a base station may only provide edge node signaling functions, while in other systems, it may provide additional control and / or network management functions. The communication link by which a UE may transmit a signal to a base station is referred to as an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link by which a base station may transmit a signal to a UE is referred to as 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 an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0040] 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 a 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. As used herein, since a TRP is a point by 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.

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

[0042] An "RF signal" includes an electromagnetic wave of a given frequency that transmits information through the space between a transmitter and a receiver. As used herein, a transmitter may 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 a "signal" where it is clear from the context that the term "signal" refers to a wireless signal or an RF signal.

[0043] 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 as "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.

[0044] 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)) through a backhaul link 122, and interface with one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) through the core network 170. The location server 172 may be part of the core network 170 or may be external to the core network 170. The location server 172 may be integrated with the base station 102. The UE 104 may communicate with the location server 172 directly or indirectly. For example, the UE 104 may communicate with the location server 172 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), and the like. For signaling purposes, communications 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.

[0045] Among other functions, the base station 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) via a backhaul link 134, which may be wired or wireless.

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

[0047] Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover area), some 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) that may provide services to a restricted group called a closed subscriber group (CSG).

[0048] The communication link 120 between the base station 102 and the UE 104 may include uplink (also referred to as reverse link) transmissions from the UE 104 to the base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use 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).

[0049] The wireless communication system 100 may also include a WLAN access point (AP) 150 that communicates with a wireless local area network (WLAN) station (STA) 152 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 listen before talk (LBT) procedure prior to communication to determine whether a channel is available.

[0050] 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 5GHz unlicensed spectrum used by the WLAN AP 150. The small cell base station 102' adopting 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.

[0051] The wireless communication system 100 may further include a millimeter wave (mmW) base station 180 that can operate in mmW frequencies and / or near mmW frequencies to communicate with UE 182. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz, with a wavelength between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near mmW can be extended down to a frequency of 3 GHz, with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands have high path loss and relatively short range. The mmW base station 180 and the UE 182 can utilize beamforming (transmitting and / or receiving) through 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 use mmW or near mmW and beamforming for transmission. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.

[0052] 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 a faster (in terms of data rate) and stronger RF signal to the receiving device. In order to change the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that broadcast the RF signal. For example, a network node can use an array of antennas (referred to as a "phased array" or "antenna array") that produces RF beams that can be "steered" to point in different directions without actually moving the antenna. Specifically, the RF current from the transmitter is fed to each antenna in the correct phase relationship so that the radio waves from the separate antennas are added together to increase the radiation in the desired direction while canceling to suppress the radiation in the undesired direction.

[0053] 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. Therefore, 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.

[0054] In receive beamforming, the receiver uses receive beams to amplify RF signals detected on a given channel. For example, the receiver may increase the gain setting of the antenna array in a particular direction and / or adjust the phase setting of the antenna array in a particular direction to amplify the RF signal received from that direction (e.g., increase its gain level). Therefore, when a receiver is said to perform beamforming in a certain direction, it means that the beam gain in that direction is high relative to the beam gain along other directions, or 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.) of the RF signal received from that direction.

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

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

[0057] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that, despite the portion of FR1 being 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 respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0058] 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 bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations 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.

[0059] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used in this document, the term "below 6 GHz" and the like can broadly refer to frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" and the like are used in this document, they can broadly refer to frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0060] 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 once an RRC connection is established between the UE 104 and the anchor carrier, and which can be used to provide additional radio resources. 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 usually 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 may have different downlink primary carriers. The same is true for the uplink primary carrier. The network is able to change the primary carrier of any UE104 / 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 on which a base station communicates, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. are used interchangeably.

[0061] For example, still referring to Figure 1 , one of the frequencies used by the macrocell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies used by the macrocell base station 102 and / or the mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers enables the 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 doubling of the data rate (i.e., 40 MHz) compared to the data rate obtained with a single 20 MHz carrier.

[0062] The wireless communication system 100 may also include a UE 164, which may communicate with the macrocell base station 102 via a communication link 120 and / or communicate 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.

[0063] In some cases, UE 164 and UE 182 are capable of sidelink communication. A sidelink-capable UE (SL-UE) may communicate with base station 102 via communication link 120 using a Uu interface (i.e., an air interface between a UE and a base station). SL-UEs (e.g., UE 164, UE 182) may also communicate directly with each other via a wireless sidelink 160 using a PC5 interface (i.e., an 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 communicating through a base station. Sidelink communications may be unicast or multicast and may be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communications, vehicle-to-vehicle (V2X) communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more SL-UEs in a group of SL-UEs utilizing sidelink communications 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 may be unable to receive transmissions from the base station 102 for other reasons. In some cases, groups of SL-UEs communicating via sidelink communications may utilize a one-to-many (1:M) system, in which each SL-UE transmits to each other SL-UE in the group. In some cases, the base station 102 facilitates the scheduling of resources for sidelink communications. In other cases, sidelink communications are performed between the SL-UEs without involving the base station 102.

[0064] In one aspect, the sidelink 160 may operate on an interesting wireless communication medium that 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., covering one or more channels across one or more carriers). In one aspect, the interesting medium may correspond to at least a portion of an unlicensed band shared between various RATs. Although different licensed bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) in the United States), these systems (particularly those that employ small cell access points) have recently expanded operations into unlicensed bands such as the unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technology (most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include different variants of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single carrier FDMA (SC-FDMA) systems, and the like.

[0065] Note that although Figure 1 Only two of these UEs are illustrated as SL-UEs (i.e., UEs 164 and 182), but any of the illustrated UEs may be SL-UEs. Furthermore, although only UE 182 is described as being 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 base stations (e.g., base stations 102, 180, small cells 102', access point 150), and the like. Thus, in some cases, UE 164 and UE 182 may utilize beamforming via sidelink 160.

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

[0067] 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, etc., such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multifunction Satellite Augmentation System (MSAS), Global Positioning System (GPS) Assisted Geographic Augmented Navigation or GPS and Geographic Augmented Navigation System (GAGAN), etc. 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.

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

[0069] The wireless communication system 100 may further include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “side links”). Figure 1 In the example of FIG. 1 , 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), Bluetooth ® etc.

[0070] Figure 2A An example wireless network structure 200 is illustrated. For example, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can be functionally viewed as a control plane (C-plane) function 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and a user plane (U-plane) function 212 (e.g., UE gateway function, access to data networks, IP routing, etc.), which operate in conjunction to form a core network. A user plane interface (NG-U) 213 and a control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, and specifically to the user plane function 212 and the control plane function 214, respectively. In an additional configuration, the ng-eNB 224 can also be connected to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. In addition, the ng-eNB 224 can communicate directly with the gNB 222 via a backhaul connection 223. In some configurations, a 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 the gNB 222 or the ng-eNB 224 (or both) may communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0071] 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 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively may each correspond to a single server. The location server 230 may be configured to support one or more location services for the UE 204 that may be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). In addition, the location server 230 may be integrated into a component of the core network, or alternatively may be external to the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

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

[0073] The functions of 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. UPF 262 may also support the delivery of location service messages between UE 204 and a location server (such as SLP 272) on the user plane.

[0074] The functions of 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 UPF 262, partial control of policy enforcement and QoS, and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.

[0075] 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 can each correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can be connected to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not illustrated). SLP 272 may support similar functionality as LMF 270, but LMF 270 may communicate with AMF 264, NG-RAN 220, and UE 204 on a control plane (e.g., using interfaces and protocols intended to carry signaling messages rather than voice or data), and SLP 272 may communicate with 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 Transmission Control Protocol (TCP) and / or IP).

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

[0077] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and the 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, and 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 may 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 may communicate with one or more UEs 204 via a wireless interface referred to as a "Uu" interface.

[0078] The functionality of the gNB 222 may be divided between a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DU) 228, and one or more gNB radio units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically assigned to the gNB-DU 228, including delivery of user data, mobility control, radio access network sharing, positioning, session management, and the like. More specifically, the gNB-CU 226 generally hosts the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that generally hosts the radio link control (RLC) and medium access control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 may 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 layer, the SDAP layer, and the PDCP layer, communicates with the gNB-DU 228 via the RLC layer and the MAC layer, and communicates with the gNB-RU 229 via the PHY layer.

[0079] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or parts in a variety of ways. 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 stand-alone base station or a single-chip base station) or a decomposed base station.

[0080] 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 between 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 in 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).

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

[0082] Figure 2C An example disaggregated base station architecture 250 is illustrated in accordance with aspects of the present disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CUs 226) that may communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 259 via an E2 link or a non-real-time (non-RT) RIC 257 associated with a service management and orchestration (SMO) framework 255, or both. The CU 280 may communicate with one or more distributed units (DUs) 285 (e.g., gNB-DUs 228) via respective midhaul links, such as an F1 interface. The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via respective fronthaul links. The RU 287 can communicate with a corresponding UE 204 via one or more radio frequency (RF) access links. In some implementations, a UE 204 can be served by multiple RUs 287 simultaneously.

[0083] 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 send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these 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 a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a 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 send signals or both to one or more of the other units via a wireless transmission medium.

[0084] In some aspects, 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 CU 280. 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, 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, CU 280 may be implemented to communicate with DU 285 for network control and signaling.

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

[0086] The 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 functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, 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, real-time and non-real-time aspects of control plane 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 the CU 280 in a cloud-based RAN architecture (such as a vRAN architecture).

[0087] The SMO framework 255 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 255 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 255 may be configured to interact with a cloud computing platform (such as an 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 an 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 specific implementations, the SMO framework 255 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 261) via the O1 interface. Additionally, in some specific implementations, the SMO framework 255 may 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 .

[0088] The non-RT RIC 257 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 259. The non-RT RIC 257 may be coupled to or in communication with the near-RT RIC 259 (such as via an A1 interface). The near-RT RIC 259 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as 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.

[0089] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 259, the non-RT RIC 257 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 259 and may be received from a non-network data source or from a network function 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 of 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).

[0090] Figure 3A , Figure 3B and Figure 3C Several example components (represented by corresponding blocks) are illustrated, which may be incorporated into UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270, or alternatively may be independent of Figure 2A and Figure 2B The depicted NG-RAN 220 and / or 5GC 210 / 260 infrastructure, such as a dedicated network, is implemented to support the operations described herein. It should be understood that these components may 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 may also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Moreover, a given device may include one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0091] 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 transmitting, 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 may each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes (such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc.) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) on a wireless communication medium of interest (e.g., a certain set of time / frequency resources in a specific spectrum). The WWAN transceivers 310 and 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 signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, the WWAN transceivers 310 and 350 include: one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.

[0092] At least in some cases, UE 302 and base station 304 each further include one or more short-range wireless transceivers 320 and 360, respectively. Short-range wireless transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide for communicating over the wireless communication medium of interest via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth ® 、Zigbee ® 、Z-Wave ®, PC5, dedicated short-range communication (DSRC), wireless access for vehicle environments (WAVE), near field communication (NFC), ultra-wideband (UWB), etc.) and other network nodes (such as other UEs, access points, base stations, etc.) (e.g., components for sending, components for receiving, components for measuring, components for tuning, components for preventing sending, etc.). The short-range wireless transceivers 320 and 360 can be configured in different ways to send and encode signals 328 and 368 (e.g., messages, indications, information, etc.) according to the 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 respectively include: one or more transmitters 324 and 364 for sending 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 specific examples, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Bluetooth ® Transceiver, Zigbee ® and / or Z-Wave ® transceiver, NFC transceiver, UWB transceiver or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceiver.

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

[0094] 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 communicate with other network entities 306 via one or more wired or wireless core network interfaces.

[0095] The transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes a transmitter circuit (e.g., transmitters 314, 324, 354, 364) and a receiver circuit (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., implementing the transmitter circuit and the receiver circuit in a single device), in some implementations may include separate transmitter circuits and separate receiver circuits, or may be implemented in other ways in other implementations. The transmitter circuit and the receiver circuit of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. The wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as 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, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 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 circuitry and the receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 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 (eg, WWAN transceivers 310 and 350 , short-range wireless transceivers 320 and 360 ) may also include a network listening module (NLM) or the like for performing various measurements.

[0096] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360 in some implementations, and network transceivers 380 and 390) and wired transceivers (e.g., network transceivers 380 and 390 in some implementations) may be generally characterized as a "transceiver," "at least one transceiver," or "one or more transceivers." Thus, whether a particular transceiver is a wired 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.

[0097] 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 include one or more processors 332, 384, and 394, respectively, for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 332, 384, and 394 may provide means for processing, such as means for determining, means for calculating, means for receiving, means for sending, means for indicating, etc. In one aspect, processors 332, 384, and 394 may include, for example, one or more general purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuits, or various combinations thereof.

[0098] UE 302, base station 304, and network entity 306 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, memory 340, 386, and 396 may provide means for storing, means for retrieving, means for maintaining, etc. In some cases, UE 302, base station 304, and network entity 306 may include positioning components 342, 388, and 398, respectively. Positioning components 342, 388, and 398, respectively, may be hardware circuits that are part of or coupled to processors 332, 384, and 394, respectively, which, when executed, cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, positioning components 342, 388, and 398 may 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, the base station 304 and the network entity 306 to perform the functionality described herein. Figure 3A Possible locations for a location component 342 are illustrated, which may be, for example, part of one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a standalone component. Figure 3B Possible locations for a location component 388 are illustrated, which may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a standalone component. Figure 3C Possible locations for a location component 398 are illustrated, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a stand-alone component.

[0099] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide a means for sensing or detecting movement and / or orientation information that is 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 receivers 330. As an example, sensor 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. In addition, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate positioning in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

[0100] In addition, the UE 302 includes a user interface 346, which 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.

[0101] Referring to the one or more processors 384 in more detail, in a downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. 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), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0102] The transmitter 354 and the 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. The transmitter 354 processes 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 split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to 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 may be used to determine coding and modulation schemes and for spatial processing. Channel estimates may be derived from a reference signal and / or channel condition feedback sent by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with a corresponding spatial stream for transmission.

[0103] At the UE 302, the receiver 312 receives the signal through its corresponding antenna 316. The receiver 312 recovers the information modulated onto the RF carrier and provides the information to one or more processors 332. The transmitter 314 and the receiver 312 implement layer 1 functionality associated with various signal processing functions. The receiver 312 can perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they can be combined into a single OFDM symbol stream by the receiver 312. The receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the signal constellation point that is most likely to be sent by the 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 sent by the 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.

[0104] 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.

[0105] 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 transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, 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.

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

[0107] The 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.

[0108] In the uplink, one or more processors 384 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from UE 302. 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.

[0109] For convenience, UE 302, base station 304 and / or network entity 306 may Figure 3A , Figure 3B and Figure 3C, is shown as including various components that can be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionality in different designs. Specifically, FIG. 3A to FIG. 3C The 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), may omit short-range wireless transceiver 320 (e.g., only cellular, etc.), may omit satellite signal receiver 330, may omit sensor 344, etc. In another example, in Figure 3B In the case of a wireless network, a specific implementation of the base station 304 may omit the WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), may omit the short-range wireless transceiver 360 (e.g., cellular only, etc.), 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.

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

[0111] Figure 3A , Figure 3B and Figure 3C The components of can be implemented in various ways. In some specific implementations, Figure 3A , Figure 3B and Figure 3CThe components of 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 for storing information or executable code used by the circuit to provide the functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by a processor and memory component of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by a processor and memory component of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Moreover, some or all of the functionality represented by blocks 390 to 398 may be implemented by a processor and memory component of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). 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, it should be understood that such operations, actions and / or functions may actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity 306, etc. (such as processors 332, 384, 394, transceivers 310, 320, 350 and 360, memories 340, 386 and 396, positioning components 342, 388 and 398, etc.).

[0112] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be operated separately from a network operator or a 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).

[0113] Please note that Figure 3A The UE 302 illustrated in the figure may represent a "reduced capability" ("RedCap") UE or an "advanced" UE. As further described below, although a RedCap UE and an advanced UE may have the same types of components (e.g., both may have one or more WWAN transceivers 310, one or more processors 332, memory 340, etc.), these components may have different degrees of functionality (e.g., increased or reduced performance, more or less capabilities, etc.), depending on whether the UE 302 corresponds to a RedCap UE or an advanced UE.

[0114] NR supports a variety of cellular network-based positioning technologies, 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 procedure 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.

[0115] For DL-AoD positioning 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 position of the UE based on the determined angle and the known position of the transmitting base station.

[0116] 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 reception time of the reference signal (referred to as relative time of arrival (RTOA)) to a positioning entity (e.g., a location server) that knows the location 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 locations of the base stations, and their known timing offsets, the positioning entity can use TDOA to estimate the position of the UE.

[0117] 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 location of the UE.

[0118] Downlink and uplink based positioning methods include: enhanced cell ID (E-CID) positioning and multiple round trip time (RTT) positioning (also referred to as "multi-cell RTT" and "multi-RTT"). In the RTT procedure, 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 a 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 transmitted (Rx-Tx) time difference. The Rx-Tx time difference measurement can be made 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 may 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., calculated as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity may transmit its Rx-Tx time difference measurements to the other entity, which then calculates the RTT. The distance between the two entities may be determined based on the RTT and a known signal speed (e.g., the speed of light). For multi-RTT positioning illustrated in scenario 430, a first entity (e.g., a UE or a base station) performs an RTT positioning procedure with a plurality of second entities (e.g., a plurality of base stations or UEs) to enable the position of the first entity to be determined (e.g., using multilateration) based on the distance to the second entities and the known positions of the second entities. RTT and multi-RTT methods may be combined with other positioning techniques (such as UL-AoA and DL-AoD) to improve position accuracy, as illustrated in scenario 440.

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

[0120] To assist the positioning operation, 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, the silent sequence, the frequency hopping sequence, the reference signal identifier, the reference signal bandwidth, etc.), and / or other parameters applicable to a specific positioning method. Alternatively, the assistance data may originate directly from the base station itself (e.g., in an overhead message broadcast periodically, etc.). In some cases, the UE itself may be able to detect neighboring network nodes without the use of assistance data.

[0121] In the case of OTDOA or DL-TDOA positioning procedures, the assistance data may further include an expected RSTD value and an associated uncertainty or a search window around the expected RSTD. In some cases, the expected RSTD value range may be + / -500 microseconds (µs). In some cases, when any resource used for positioning measurements is 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.

[0122] The position estimate may be referred to by other names, such as a position estimate, position, position fix, position fix, fix, etc. The position estimate may be geodetic and include coordinates (e.g., latitude, longitude, and possibly altitude), or may be municipal and include a street address, postal address, or some other verbal description of the location. The position estimate may be further defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possibly altitude). The 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 contained with some specified or default confidence level).

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

[0124] An LPP session typically includes at least a capability transfer or indication procedure, an assistance data transfer or delivery procedure, and a location information transfer or delivery procedure. Figure 5 An example LPP capability transfer procedure 510, LPP assistance data transfer procedure 530, and LPP location information transfer procedure 550 between a target device (labeled "target") and a location server (labeled "server") in accordance with aspects of the present disclosure are illustrated.

[0125] The purpose of the LPP capability transfer procedure 510 is to enable capabilities to be transferred from a target device (e.g., UE 204) to a location server (e.g., LMF 270). In this context, capabilities refer to positioning and protocol capabilities related to LPP and positioning methods supported by LPP. In the LPP capability transfer procedure 510, the location server (e.g., LMF 270) indicates the type of capabilities required by the target device (e.g., UE 204) in an LPP request capabilities message. The target device responds with an LPP offer capabilities message. The capabilities included in the LPP offer capabilities message should correspond to any capability type specified in the LPP request capabilities message. Specifically, for each positioning method for which a request for capabilities is included in the LPP request capabilities message, if the target device supports the positioning method, the target device includes the capabilities of the target device for the supported positioning methods in the LPP offer capabilities response message. For the LPP capability indication procedure, the target device provides unsolicited (i.e., does not receive an LPP request capabilities message) capabilities to the location server in an LPP offer capabilities message.

[0126] The purpose of the LPP assistance data delivery procedure 530 is to enable the target device to request assistance data from the location server to assist in positioning, and to enable the location server to deliver the assistance data to the target device without request. In the LPP assistance data delivery procedure 530, the target device transmits an LPP request assistance data message to the location server. The location server responds to the target device with an LPP provide assistance data message containing the assistance data. The delivered assistance data should match or be a subset of the assistance data requested in the LPP request assistance data. The location server may also provide any unrequested information that it deems useful to the target device. The location server may also send one or more additional LPP provide assistance data messages containing further assistance data to the target device. For the LPP assistance data delivery procedure, the location server provides the unsolicited assistance data necessary for positioning. Assistance data may be provided periodically or aperiodically.

[0127] The purpose of the LPP location information delivery procedure 550 is to enable a location server to request location measurement data and / or location estimates from a target device, and to enable a target device to deliver location measurement data and / or location estimates to a location server without a request. In the LPP location information delivery procedure 550, the location server transmits an LPP request location information message to the target device to request location information, thereby indicating the type of location information required and potentially associated QoS. The target device responds to the location server with an LPP provide location information message to deliver location information. Unless the location server explicitly allows additional location information, the delivered location information should match or be a subset of the location information requested by the LPP request location information. More specifically, if the requested information is compatible with the capabilities and configuration of the target device, the target device includes the requested information in the LPP provide location information message. Otherwise, if the target device does not support one or more of the requested positioning methods, the target device continues to process the message as if the message only contains information of the supported positioning methods, and handles the signaling content of the unsupported positioning method through LPP error detection. If requested by the LPP Request Location Information message, the target device transmits an Additional LPP Provide Location Information message to the location server to deliver additional location information.The LPP Location Information Delivery procedure supports the delivery of positioning estimates based on unsolicited services.

[0128] Various frame structures may be used to support downlink and uplink transmissions between network nodes (eg, base stations and UEs). Figure 6 600 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.

[0129] 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 called tones, frequency bins, etc. Each subcarrier can be modulated with data. In general, 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 spacing of the subcarriers can be 15 kilohertz (kHz), and the minimum resource allocation (resource block) can be 12 subcarriers (or 180kHz). 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 partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, respectively.

[0130] 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 15kHz SCS (µ=0), there is one slot per subframe, 10 slots per frame, the slot duration is 1 millisecond (ms), the symbol duration is 66.7 microseconds (µs), and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 50. For 30kHz SCS (µ=1), there are two slots per subframe, 20 slots per frame, the slot duration is 0.5ms, the symbol duration is 33.3µs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 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.

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

[0132] A resource grid may be used to represent a time slot, each of which includes one or more time-concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into a plurality of 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 of , 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.

[0133] Some 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 (SSB), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink communication or downlink communication. Figure 6 Example locations of REs carrying reference signals (labeled “R”) are illustrated.

[0134] A set of resource elements (REs) used for transmission of PRS is referred to as a "PRS resource". A set of resource elements may span multiple PRBs in the frequency domain and "N" (such as 1 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.

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

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

[0137] 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, a 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: 2^µ*{4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120,10240} slots, where µ=0, 1, 2, 3. The repetition factor may have a length selected from {1, 2, 4, 6, 8, 16, 32} slots.

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

[0139] A "PRS instance" or "PRS opportunity" is an instance of a periodically repeated time window (such as a group of one or more consecutive time slots) in which a PRS is expected to be sent. 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".

[0140] A "positioning frequency layer" (also referred to simply as a "frequency layer") is a set 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 of 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 used for transmission and reception. The downlink PRS bandwidth can have a granularity of four PRBs, and the minimum value is 24 PRBs and the maximum value is 272 PRBs. Currently, up to four frequency layers have been defined, and up to two PRS resource sets can be configured per TRP per frequency layer.

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

[0142] The UE reports its ability to process PRS in a capability update (e.g., in the LPP capability transfer procedure 510). The assistance data received based on the UE's capability information (e.g., in the LPP assistance data transfer procedure 530) includes information required to perform measurements of PRS for the positioning session (e.g., configuration of PRS resources to be measured from one or more base stations / TRPs / cells). However, the assistance data may identify significantly more PRS resources to be measured than the UE is capable of processing. For example, the UE may only be able to process up to five PRS resources, while the PRS assistance data may identify 20 PRS resources to be measured.

[0143] Currently, in this case, the UE selects the first five PRS resources for processing. Specifically, it has been agreed that when the UE is configured with a number of PRS resources in the assistance data of the positioning method that exceeds its capabilities, the UE assumes that the PRS resources in the assistance data are sorted in descending order of measurement priority. According to the current structure of the assistance data, the following priorities are assumed: the 64 TRPs of each frequency layer are sorted according to priority, and the two PRS resource sets of each TRP of the frequency layer are sorted according to priority. The four frequency layers may or may not be sorted according to priority, and the 64 PRS resources in the PRS resource set of each TRP of each frequency layer may or may not be sorted according to priority. It should be noted that the reference PRS resources indicated by the "nr-DL-PRS-ReferenceInfo-r16" LPP information element for each frequency layer have the highest priority at least for DL-TDOA.

[0144] On the one hand, Figure 6 The reference signal carried on the RE marked with "R" in the figure can be an SRS. The SRS sent 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 effect of scattering, attenuation, and power attenuation with distance. The system uses SRS for resource scheduling, link adaptation, massive MIMO, beam management, etc.

[0145] The set of REs used for transmission of SRS is called "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 set of SRS resources used for transmission of SRS signals and is identified by an SRS resource set ID ("SRS-ResourceSetId").

[0146] 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 a 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. 1 , 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.

[0147] Currently, SRS resources 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-Symbol Comb-2: {0, 1}; 2-Symbol Comb-4: {0, 2}; 4-Symbol Comb-2: {0, 1, 0,1}; 4-Symbol 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}.

[0148] In general, as mentioned, the UE sends the SRS to enable the receiving base station (serving base station or neighboring base station) to measure the channel quality (i.e., CSI) between the UE and the base station. However, the SRS may also be specifically configured as an uplink positioning reference signal for uplink-based positioning procedures, 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 as "SRS for communication" and / or the latter may be referred to as "SRS for positioning" or "positioning SRS" in this article.

[0149] Several enhancements compared to the previous definition of SRS may be available for "SRS for positioning" (also known as "UL-PRS"), such as a new staggering pattern within the SRS resource (other than 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 downlink reference signals or SSBs from neighboring TRPs. Further, 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, the UE may transmit from multiple SRS resources through the same transmit beam for UL-AoA. All of these are features outside 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)).

[0150] 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., an 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 (e.g., DMRS) that can be sent in the downlink, uplink, and / or sidelink, these signals may be prepended with "DL," "UL," or "SL" to distinguish the direction. For example, "UL-DMRS" is different from "DL-DMRS."

[0151] Figure 7700 is a diagram illustrating various downlink channels within an example downlink time slot. Figure 7 In , 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. Figure 7 In the example of , a 15 kHz parameter set is used. Therefore, in the time domain, the illustrated time slot length is one millisecond (ms), divided into 14 symbols.

[0152] In NR, the channel bandwidth or system bandwidth is divided into multiple bandwidth parts (BWPs). A BWP is a set of contiguous RBs selected from a contiguous subset of common RBs for a given set of parameters on a given carrier. In general, a maximum of four BWPs can be specified in the downlink and uplink. That is, the UE can be configured with up to four BWPs on the downlink and up to four BWPs on the uplink. Only one BWP (uplink or downlink) can be active at a given time, which means that the UE can only receive or transmit on one BWP at a time. On the downlink, the bandwidth of each BWP should be equal to or greater than the bandwidth of the SSB, but it may or may not contain the SSB.

[0153] refer to Figure 7 , the primary synchronization signal (PSS) is used by the UE to determine the subframe / symbol timing and the physical layer identification. The secondary synchronization signal (SSS) is used by the UE to determine the physical layer cell identification group number and the radio frame timing. Based on the physical layer identification and the physical layer cell identification group number, the UE can determine the PCI. Based on the PCI, the UE can determine the location of the aforementioned DL-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form an SSB (also referred to as SS / PBCH). The MIB provides the number of RBs in the downlink system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information that is not sent through the PBCH (such as the system information block (SIB)), and paging messages.

[0154] The physical downlink control channel (PDCCH) carries downlink control information (DCI) in one or more control channel elements (CCEs), each CCE includes one or more RE group (REG) bundles (which can span multiple symbols in the time domain), each REG bundle includes one or more REGs, each REG corresponds to 12 resource elements (one resource block) in the frequency domain and one OFDM symbol in the time domain. The set of physical resources used to carry PDCCH / DCI is called a control resource set (CORESET) in NR. In NR, PDCCH is confined to a single CORESET and is transmitted with its own DMRS. This enables UE-specific beamforming for PDCCH.

[0155] exist Figure 7 In the example of NR, there is one CORESET per BWP, and the CORESET spans three symbols in the time domain (although it could be just one symbol or two symbols). Unlike LTE control channels that occupy the entire system bandwidth, in NR, the PDCCH channel is localized to a specific region (i.e., CORESET) in the frequency domain. Therefore, Figure 7 The frequency components of the PDCCH shown in FIG are illustrated as less than a single BWP in the frequency domain. Note that although the illustrated CORESETs are continuous in the frequency domain, the CORESETs do not need to be continuous. Furthermore, the CORESETs may span less than three symbols in the time domain.

[0156] The DCI within the PDCCH carries information about uplink resource allocations (persistent and non-persistent) and descriptions of downlink data sent to the UE (referred to as uplink grants and downlink grants, respectively). More specifically, the DCI indicates resources scheduled for downlink data channels (e.g., PDSCH) and uplink data channels (e.g., physical uplink shared channel (PUSCH)). Multiple (e.g., up to eight) DCIs may be configured in the PDCCH, and these DCIs may have one of a variety of formats. For example, there are different DCI formats for uplink scheduling, downlink scheduling, uplink transmit power control (TPC), etc. The PDCCH may be transmitted by 1, 2, 4, 8, or 16 CCEs to accommodate different DCI payload sizes or coding rates.

[0157] UEs may be classified into RedCap UEs (e.g., wearable devices such as smart watches, glasses, rings, etc.) and advanced UEs (e.g., smart phones, tablet computers, laptop computers, etc.). Alternatively, RedCap UEs may be referred to as low-level UEs, light UEs, or ultra-light UEs. Advanced UEs are alternatively 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, optionally with two receiver antennas), lower operating bandwidth capabilities (e.g., 20 MHz for FR1 without supplementary uplink or carrier aggregation, or 50 MHz or 100 MHz for FR2), only half-duplex frequency division duplex (HD-FDD) capabilities, smaller HARQ buffers, reduced physical downlink control channel (PDCCH) monitoring, restricted modulation (e.g., 64 QAM for downlink and 16 QAM for uplink), relaxed processing timeline requirements, and / or lower uplink transmit power. Different UE classes may be distinguished by UE category and / or UE capabilities. For example, certain types of UEs may be assigned a "RedCap" category (e.g., by an original equipment manufacturer (OEM), an applicable wireless communication standard, etc.), while other types of UEs may be assigned an "Advanced" category. Certain classes of UEs may also report the type of these UEs (e.g., "RedCap" or "Advanced") to the network (e.g., AMF 264). In addition, certain resources and / or channels may be dedicated to certain types of UEs.

[0158] 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 calculations 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 can be reduced, which means that there will be lower quality uplink measurement results for the RedCap UE positioning.

[0159] 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 may operate over a 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. In addition, the transmit power of Advanced UEs may be higher than that of RedCap UEs. The reliability of measurements and positioning calculations will therefore be increased.

[0160] As mentioned above, RedCap UEs may use only a subset of the available bandwidth. Figure 7 As shown, SSBs may not occupy the entire bandwidth of a BWP, and therefore, a bandwidth subset used by a RedCap UE may not have SSBs transmitted therein. Therefore, when a UE operates in a RedCap-specific initial BWP or a dedicated BWP, the UE may be configured (e.g., via RRC signaling) with non-cell defined (NCD) SSBs to be used. Support for an active downlink BWP without cell defined (CD) SSBs and CORESET #0 is a mandatory feature for RedCap UEs. Furthermore, the network is expected to configure the paging search space in the RRC-configured BWP of the RedCap UE. Figure 8 Various aspects of RRC BWP configuration for a RedCap UE in accordance with various aspects of the present disclosure are illustrated. Diagram 800 illustrates various example aspects of a RedCap UE operating in an active RRC BWP without CD SSB. Diagram 850 illustrates various example aspects of a RedCap UE obtaining SIBs in an active RRC BWP without CORESET #0.

[0161] The following table illustrates the characteristics of NCD-SSB.

[0162]

[0163] Table 1

[0164] Fig. 9 900 is a diagram illustrating example relative frequency positions of various NCD-SSB based parameters according to aspects of the present disclosure. Specifically, Fig. 9 The initial downlink (DL) BWP of a RedCap UE, CORESET #0, CD-SSB, NCD-SSB, RRC uplink (UL) BWP of the UE, and RRC DL BWP of the UE are illustrated.

[0165] There are various measurement scenarios for RedCap UEs related to maximum bandwidth reduction. For serving cell measurements, the serving cell active BWP includes CD-SSB and, for RedCap UEs, may also include NCD-SSB. Some or all of the neighboring cells may include NCD-SSB at the same frequency location as the NCD-SSB of the serving cell. For neighbor cell measurements, the RRM requirements for neighbor cell measurements may be based on CD-SSB or NCD-SSB.

[0166] Intra-frequency measurements may be defined for the above measurement scenarios as follows. The center frequency of the reference SSB of the serving cell is the same as the center frequency of the SSB of the neighboring cell, and the subcarrier spacing of these two SSBs is also the same. The reference SSB is the SSB defined in the BWP-specific "servingCellMO" parameter under the "BWP-DownlinkDedicated" parameter of the active downlink BWP. If this field is not present, the reference SSB is the SSB defined in the "servingCellMO" parameter of the "ServingCellConfig" parameter.

[0167] There are various use cases for NCD-SSB in Layer 1 (L1) processing. NCD-SSB can be used for (1) radio link monitoring, (2) beam failure detection, (3) candidate beam detection for beam failure recovery procedure, (4) reference SSB during random access channel (RACH) transmission, and / or (5) uplink transmission timing accuracy. If NCD-SSB is in the RRC active BWP, it is expected that these requirements are defined based on NCD-SSB.

[0168] Fig.10An example "BWP-DownlinkDedicated" RRC information element (IE) according to various aspects of the present disclosure is illustrated. "BWP-DownlinkDedicated" is used to configure dedicated (UE-specific) parameters for a downlink BWP. When the UE is in an RRC connected state, the "nonCellDefiningSSB" parameter is configured to the UE in "BWP-DownlinkDedicated". If the UE is configured with the "nonCellDefiningSSB" parameter, the UE operating in this BWP uses the SSB for purposes for which it would otherwise use the CD-SSB of the serving cell (e.g., obtaining synchronization, measurements, radio link management (RLM)), etc.). In addition, other parts of the BWP configuration that refer to the SSB (e.g., "SSB" configured in the "QCL-Info" IE, "ssb-Index", "CFRA-SSB-Resource", "PRACH-ResourceDedicatedBFR" configured in the "RadioLinkMonitoringRS" IE) implicitly refer to the NCD-SSB. NCD-SSB has the same values ​​for the characteristics of the corresponding CD-SSB (eg, "ssb-PositionsInBurst", PCI, "ssb-periodicity", "ssb-PBCH-BlockPower"), except for the values ​​of the characteristics configured in the "NonCellDefiningSSB" IE.

[0169] Fig.11 An example "nonCellDefiningSSB" RRC IE according to various aspects of the present disclosure is illustrated. The "NonCellDefiningSSB" IE is used to configure the NCD-SSB to be used when the UE operates in a dedicated BWP. The "NonCellDefiningSSB" IE includes fields "absoluteFrequencySSB" and "ssb-Periodicity". The "absoluteFrequencySSB" field indicates the frequency of the NCD-SSB. The network configures this field so that the SSB is within the bandwidth of the BWP configured in the "BWP-DownlinkCommon" IE. The "ssb-Periodicity" field indicates the periodicity of the NCD-SSB. The network only configures a periodicity that is greater than the periodicity of the CD-SSB of the serving cell. If this field does not exist, the UE applies the SSB periodicity of the CD-SSB ("ssb-periodicityServingCell" configured in "ServingCellConfigCommon").

[0170] Fig.12 An example "NR-SSB-Config" LPP IE in accordance with aspects of the present disclosure is illustrated. The "NR-SSB-Config" IE configured to the UE in the "NR-DL-AssistanceData" IE defines the SSB configuration. The following table provides a field description of the "NR-SSB-Config" IE.

[0171]

[0172] Table 2

[0173] In LPP, there is an association of SSBs for each TRP, but there is no information about serving NCD-SSBs and non-serving NCD-SSBs. This raises the question of whether it is necessary to have information indicating whether an SSB is a CD-SSB or an NCD-SSB.

[0174] Fig.13 Various aspects of SSB association in LPP according to various aspects of the present disclosure are illustrated. Specifically, Fig.13 As shown, the "NR-DL-PRS-Resource" LPP IE includes a "dl-PRS-QCL-Info" field that points to the "DL-PRS-QCL-Info" LPP IE. The "NR-DL-PRS-Resource" IE includes various fields that define the SSB associated with the DL-PRS resource. More specifically, in the LPP, each DL-PRS resource may be associated with a single SSB. Whether the SSB is an NCD-SSB or a CD-SSB depends on the network / LMF. However, as Fig.13 As indicated by the single "ssb" field in the , there is no option to include both. This means that the UE will have to measure a specific / identified SSB without knowing that there is a second SSB with similar QCL characteristics (e.g. NCD-SSB if the designated SSB is CD-SSB).

[0175] On the uplink, for SRS transmissions, RRC signaling provides SSB information for spatial / path loss measurements of SRS transmissions. This is configured to the UE via the "ssb-Ncell" field in the "SRS-SpatialRelationInfoPos" RRC IE. In RRC, each SRS resource can be associated with a single SSB. Whether that SSB is an NCD-SSB or a CD-SSB depends on the network / LMF. However, there is no option to include both (i.e., there is a single "ssb-Ncell" field in the "SRS-SpatialRelationInfoPos" RRC IE). This means that the UE will have to measure a specific / identified SSB without knowing that there is a second SSB with similar QCL characteristics (e.g., a CD-SSB if the specified SSB is an NCD-SSB).

[0176] Fig.14 Various aspects of the technology that facilitates the implementation of the present disclosure are illustrated in accordance with various aspects of the present disclosure. Fig.14 In the example of FIG. 4 , a UE is operating in a reduced capability (RedCap) framework. The UE has been configured to measure DL-PRS resources transmitted by a first TRP (labeled as “TRP1”) and a second TRP (labeled as “TRP2”). The first TRP may be a serving TRP of the UE, and the second TRP may be a neighboring TRP. The UE may be configured with a measurement gap (MG) to measure the DL-PRS resources from the second TRP.

[0177] If the CD-SSBs of the UE’s serving cell and neighboring cells are defined in the same initial BWP (this is not Fig.14 ), the UE can measure the SSBs of both the serving cell and the neighboring cell without any BWP switching. Fig.14 As shown in the example of , there will be a situation where CD-SSB is not defined for the serving cell or neighboring cells on all BWPs. This scenario is not handled by LPP signaling. Similarly, NCD-SSB can be used in the case where CD-SSB is defined in a given BWP. However, NCD-SSB and LPP signaling are not defined.

[0178] like Fig.14 As shown in diagram 1400 of FIG. 1 , the UE operates in a first dedicated BWP (labeled “Dedicated BWP #1”). In this case, the UE will need to switch to a second dedicated BWP (labeled “Dedicated BWP #2”) to measure the CD-SSB of the second TRP (“TRP2”). Fig.14As shown in diagram 1450 of FIG. 14 , the UE operates in a second dedicated BWP (labeled “Dedicated BWP #2”). The UE will need to switch to the first dedicated BWP to measure the CD-SSB of the first TRP (“TRP1”).

[0179] The present disclosure provides techniques for providing NCD-SSB configuration in LPP (for DL-PRS) and RRC (for UL-SRS). For LPP, for use cases with reduced capability, the LMF may provide NCD-SSB information along with SSB information for each TRP in auxiliary data (e.g., LPP Provides Assistance Data message). Multiple TRPs may share the same NCD-SSB / SSB configuration. If multiple dedicated BWPs are configured for a serving cell, the LMF shall provide a list of NCD-SSBs. The LMF may obtain NCD-SSB information from the UE's serving base station and neighboring base stations (e.g., via New Radio Positioning Protocol Type A (NRPPa) signaling).

[0180] For RRC, the NCD-SSB configuration for neighbor cells may be provided in the "SRS-config" RRC IE. For the reduced capability use case, the serving base station provides the NCD-SSB information of neighbor cells (if any) for SSBs that are the QCL relation or path loss reference source for SRS used for positioning.

[0181] The present disclosure also provides UE-side techniques to opportunistically use the NCD-SSB information provided by RRC for PRS measurements. Consider an example scenario where the LMF only provides the CD-SSB configuration for the first TRP (denoted as "TRP1") in the assistance data (e.g., the LPP provides the assistance data message). In this case, the CD-SSB of TRP1 is defined for the first BWP (denoted as "BWP1"). However, before the positioning session, the UE switches to the second BWP (denoted as "BWP2"). Therefore, without BWP switching or measurement gap configuration, the UE can no longer use the specified CD-SSB.

[0182] To solve this problem, the UE can check the NCD-SSB provided by RRC for TRP1. Or the UE can search based on the PCI, cell identifier (CI) and / or ARFCN provided in the auxiliary data. If the UE finds a matching NCD-SSB for TRP1 in the RRC message, the UE can measure the NCD-SSB to measure the DL-PRS from TRP1.

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

[0184] At 1510, the UE receives first configuration information for a first PRS resource transmitted by a first neighboring TRP, the first configuration information indicating a first QCL relationship between the first PRS resource and a first SSB transmitted by the first neighboring TRP, wherein the first SSB is an NCD-SSB. In an aspect, operation 1510 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] At 1520, the UE obtains a first positioning measurement result for the first PRS resource based on a QCL relationship between the first PRS resource and the SSB transmitted by the first neighboring TRP. In an aspect, operation 1520 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 as means for performing the operation.

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

[0187] At 1610, the UE receives first configuration information of a first SRS resource for positioning, the first configuration information indicating a first QCL relationship between the first SRS resource for positioning and a first SSB transmitted by a first neighboring TRP, wherein the first SSB is an NCD-SSB. In one aspect, operation 1610 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 as means for performing the operation.

[0188] At 1620, the UE transmits the first SRS resource for positioning based on a QCL relationship between the first SRS resource for positioning and the SSB transmitted by the first neighboring TRP. In an aspect, operation 1620 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 as means for performing the operation.

[0189] It should be understood that the technical advantage of methods 1500 and 1600 is that it enables the UE to obtain the QCL relationship of the TRP based on the first SSB (e.g., CD-SSB) or the second SSB (e.g., NCD-SSB).

[0190] 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, 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, where each clause itself can be used as a separate example. Although each subordinate clause may refer to a specific combination of one clause with other clauses in the clause, the aspects of the subordinate clause are not limited to specific combinations. It should be understood that other example clauses may also include a combination of the subject matter of the subordinate clause aspect with any other subordinate clause or independent clause or any feature with other subordinate clauses and independent clauses. The various aspects disclosed herein explicitly include these combinations, unless it is clearly 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 the clause may be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

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

[0192] Clause 1. A method for performing wireless communication by a user equipment (UE), the method comprising: receiving first configuration information of a first positioning reference signal (PRS) resource sent by a first adjacent transmit receive point (TRP), the first configuration information indicating a first quasi-co-location (QCL) relationship between the first PRS resource and a first synchronization signal block (SSB) sent by the first adjacent TRP; receiving second configuration information, the second configuration information indicating a second QCL relationship between the first PRS resource and a second SSB sent by the first adjacent TRP; and obtaining a first positioning measurement result of the PRS resource based on the first QCL relationship between the first PRS resource and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first PRS resource and the second SSB sent by the first adjacent TRP, or both.

[0193] Clause 2. The method of clause 1, wherein the first SSB is a cell-definition SSB (CD-SSB) and the second SSB is a non-cell-definition SSB (NCD-SSB).

[0194] Clause 3. The method according to clause 2, wherein the second configuration information includes association information between the NCD-SSB and the CD-SSB.

[0195] Clause 4. A method as described in any of clauses 2 to 3, wherein the second configuration information includes an association of the first PRS resource with the NCD-SSB.

[0196] Clause 5. A method according to any one of clauses 1 to 4, wherein: the first SSB sent by the first adjacent TRP is sent within the bandwidth of a first bandwidth part (BWP), the second SSB sent by the first adjacent TRP is sent within the bandwidth of a second BWP, and the first positioning measurement result is obtained based on the measurement result of the first PRS resource in the bandwidth of the second BWP rather than in the bandwidth of the first BWP.

[0197] Clause 6. According to the method described in any one of clauses 1 to 5, the method further includes: receiving third configuration information of a second PRS resource sent by a second adjacent TRP, the third configuration information indicating a first QCL relationship between the second PRS resource and the first SSB sent by the second adjacent TRP; receiving fourth configuration information, the fourth configuration information indicating a second QCL relationship between the second PRS resource and the second SSB sent by the second adjacent TRP; obtaining a second positioning measurement result of the second PRS resource based on the first QCL relationship between the second PRS resource and the CD-SSB sent by the second adjacent TRP, the second QCL relationship between the second PRS resource and the NCD-SSB sent by the second adjacent TRP, or both.

[0198] Clause 7. A method according to Clause 6, wherein: the first SSB sent by the second adjacent TRP and the second SSB sent by the first adjacent TRP are sent in the bandwidth of a first BWP, the first SSB sent by the first adjacent TRP is sent in the bandwidth of a second BWP, and the first positioning measurement result is obtained based on the measurement result of the first PRS resource in the bandwidth of the first BWP rather than in the bandwidth of the second BWP.

[0199] Clause 8. A method according to any one of clauses 1 to 7, wherein the first configuration information indicating the first QCL relationship between the first PRS resource and the first SSB and the second QCL relationship between the first PRS resource and the second SSB includes a DL-PRS-QCL-Info information element in the configuration information indicating both the first SSB and the second SSB.

[0200] Clause 9. A method according to any one of clauses 1 to 8, wherein the first configuration information indicating the first QCL relationship between the first PRS resource and the first SSB and the second QCL relationship between the first PRS resource and the second SSB includes a DL-PRS-Resource information element indicating the first QCL relationship and the second QCL relationship in the configuration information.

[0201] Clause 10. The method of any of clauses 1 to 9, wherein the first configuration information is received from a location server in Long Term Evolution (LTE) Positioning Protocol (LPP) assistance data.

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

[0203] Clause 12. A method for performing wireless communication by a user equipment (UE), the method comprising: receiving first configuration information of a first sounding reference signal (SRS) resource, the first configuration information indicating a first quasi-co-location (QCL) relationship between the first SRS resource and a first SSB sent by a first adjacent transmit receive point (TRP); receiving second configuration information, the second configuration information indicating a second QCL relationship between the first SRS resource and a second SSB sent by the first adjacent TRP; and sending the first SRS resource based on the first QCL relationship between the first SRS resource and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first SRS resource and the second SSB sent by the first adjacent TRP, or both.

[0204] Clause 13. The method of clause 12, wherein the first SSB is a cell-defining SSB (CD-SSB) and the second SSB is a non-cell-defining SSB (NCD-SSB).

[0205] Clause 14. The method of clause 13, wherein the second configuration information includes association information between the NCD-SSB and the CD-SSB.

[0206] Clause 15. A method as described in any of clauses 13 to 14, wherein the second configuration information includes an association of the first SRS resource with the NCD-SSB.

[0207] Clause 16. A method according to any one of clauses 12 to 15, wherein: the first SSB sent by the first adjacent TRP is sent in the bandwidth of a first bandwidth part (BWP), the second SSB sent by the first adjacent TRP is sent in the bandwidth of a second BWP, and the first SRS is sent based on the measurement result of the second SSB in the bandwidth of the second BWP instead of the measurement result of the first SSB in the bandwidth of the first BWP.

[0208] Clause 17. A method according to any one of clauses 12 to 16, wherein the first configuration information indicating the first QCL relationship between the first SRS resource and the first SSB and the second QCL relationship between the first SRS resource and the second SSB includes an SRS-SpatialRelationInfo information element in the configuration information indicating a first SSB configuration for the first SSB and a second SSB configuration for the second SSB.

[0209] Clause 18. A method according to any one of clauses 12 to 17, wherein the first configuration information indicating the first QCL relationship between the first PRS resource and the first SSB and the second QCL relationship between the first PRS resource and the second SSB includes an SSB-Configuration information element in the configuration information indicating configuration information for both the first SSB and the second SSB.

[0210] Clause 19. A method as described in any of clauses 12 to 18, wherein the first configuration information is received from a serving base station via radio resource control (RRC) signaling.

[0211] Clause 20. A method as described in any of clauses 12 to 19, wherein the UE is a reduced capability (RedCap) UE.

[0212] Clause 21. A user equipment (UE), the 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, via the at least one transceiver, first configuration information of a first positioning reference signal (PRS) resource transmitted by a first adjacent transmit receive point (TRP), the first configuration information indicating a first quasi co-location (QCL) relationship between the first PRS resource and a first synchronization signal block (SSB) transmitted by the first adjacent TRP; receive, via the at least one transceiver, second configuration information indicating a second QCL relationship between the first PRS resource and a second SSB transmitted by the first adjacent TRP; and obtain a first positioning measurement result of the PRS resource based on the first QCL relationship between the first PRS resource and the first SSB transmitted by the first adjacent TRP, the second QCL relationship between the first PRS resource and the second SSB transmitted by the first adjacent TRP, or both.

[0213] Clause 22. The UE of clause 21, wherein the first SSB is a cell-defined SSB (CD-SSB) and the second SSB is a non-cell-defined SSB (NCD-SSB).

[0214] Clause 23. A UE according to Clause 22, wherein the second configuration information includes association information between the NCD-SSB and the CD-SSB.

[0215] Clause 24. A UE as set forth in any of clauses 22 to 23, wherein the second configuration information comprises an association of the first PRS resource with the NCD-SSB.

[0216] Clause 25. A UE according to any one of clauses 21 to 24, wherein: the first SSB sent by the first adjacent TRP is sent within the bandwidth of a first bandwidth part (BWP), the second SSB sent by the first adjacent TRP is sent within the bandwidth of a second BWP, and the first positioning measurement result is obtained based on the measurement result of the first PRS resource in the bandwidth of the second BWP rather than in the bandwidth of the first BWP.

[0217] Clause 26. A UE according to any one of clauses 21 to 25, wherein the at least one processor is further configured to: receive, via the at least one transceiver, third configuration information of a second PRS resource sent by a second adjacent TRP, the third configuration information indicating a first QCL relationship between the second PRS resource and a first SSB sent by the second adjacent TRP; receive, via the at least one transceiver, fourth configuration information indicating a second QCL relationship between the second PRS resource and a second SSB sent by the second adjacent TRP; and obtain a second positioning measurement result of the second PRS resource based on the first QCL relationship between the second PRS resource and the CD-SSB sent by the second adjacent TRP, the second QCL relationship between the second PRS resource and the NCD-SSB sent by the second adjacent TRP, or both.

[0218] Clause 27. A UE according to Clause 26, wherein: the first SSB sent by the second adjacent TRP and the second SSB sent by the first adjacent TRP are sent in the bandwidth of a first BWP, the first SSB sent by the first adjacent TRP is sent in the bandwidth of a second BWP, and the first positioning measurement result is obtained based on the measurement result of the first PRS resource in the bandwidth of the first BWP rather than in the bandwidth of the second BWP.

[0219] Clause 28. A UE according to any one of clauses 21 to 27, wherein the first configuration information indicating the first QCL relationship between the first PRS resource and the first SSB and the second QCL relationship between the first PRS resource and the second SSB includes a DL-PRS-QCL-Info information element in the configuration information indicating both the first SSB and the second SSB.

[0220] Clause 29. A UE according to any one of clauses 21 to 28, wherein the first configuration information indicating the first QCL relationship between the first PRS resource and the first SSB and the second QCL relationship between the first PRS resource and the second SSB includes a DL-PRS-Resource information element indicating the first QCL relationship and the second QCL relationship in the configuration information.

[0221] Clause 30. A UE as set forth in any of clauses 21 to 29, wherein the first configuration information is received from a location server in Long Term Evolution (LTE) Positioning Protocol (LPP) assistance data.

[0222] Clause 31. A UE as set forth in any of clauses 21 to 30, wherein the UE is a reduced capability (RedCap) UE.

[0223] Clause 32. A user equipment (UE), the 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 first configuration information of a first sounding reference signal (SRS) resource via the at least one transceiver, the first configuration information indicating a first quasi-co-location (QCL) relationship between the first SRS resource and a first SSB sent by a first adjacent transmit receive point (TRP); receive second configuration information via the at least one transceiver, the second configuration information indicating a second QCL relationship between the first SRS resource and a second SSB sent by the first adjacent TRP); and send the first SRS resource via the at least one transceiver based on the first QCL relationship between the first SRS resource and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first SRS resource and the second SSB sent by the first adjacent TRP, or both.

[0224] Clause 33. The UE of clause 32, wherein the first SSB is a cell-defined SSB (CD-SSB) and the second SSB is a non-cell-defined SSB (NCD-SSB).

[0225] Clause 34. A UE according to clause 33, wherein the second configuration information includes association information between the NCD-SSB and the CD-SSB.

[0226] Clause 35. A UE as described in any of clauses 33 to 34, wherein the second configuration information includes an association of the first SRS resource with the NCD-SSB.

[0227] Clause 36. A UE according to any one of clauses 32 to 35, wherein: the first SSB sent by the first adjacent TRP is sent in the bandwidth of a first bandwidth part (BWP), the second SSB sent by the first adjacent TRP is sent in the bandwidth of a second BWP, and the first SRS is sent based on the measurement result of the second SSB in the bandwidth of the second BWP instead of the measurement result of the first SSB in the bandwidth of the first BWP.

[0228] Clause 37. A UE according to any one of clauses 32 to 36, wherein the first configuration information indicating the first QCL relationship between the first SRS resource and the first SSB and the second QCL relationship between the first SRS resource and the second SSB includes an SRS-SpatialRelationInfo information element in the configuration information indicating a first SSB configuration for the first SSB and a second SSB configuration for the second SSB.

[0229] Clause 38. A UE according to any one of clauses 32 to 37, wherein the first configuration information indicating the first QCL relationship between the first PRS resource and the first SSB and the second QCL relationship between the first PRS resource and the second SSB includes an SSB-Configuration information element in the configuration information indicating configuration information for both the first SSB and the second SSB.

[0230] Clause 39. A UE as set forth in any of clauses 32 to 38, wherein the first configuration information is received from a serving base station via radio resource control (RRC) signaling.

[0231] Clause 40. A UE as set out in any of clauses 32 to 39, wherein the UE is a reduced capability (RedCap) UE.

[0232] Clause 41. A user equipment (UE), the user equipment (UE) comprising: a component for receiving first configuration information of a first positioning reference signal (PRS) resource sent by a first adjacent transmit receive point (TRP), the first configuration information indicating a first quasi-co-location (QCL) relationship between the first PRS resource and a first synchronization signal block (SSB) sent by the first adjacent TRP; a component for receiving second configuration information, the second configuration information indicating a second QCL relationship between the first PRS resource and a second SSB sent by the first adjacent TRP; and a component for obtaining a first positioning measurement result of the first PRS resource based on the first QCL relationship between the first PRS resource and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first PRS resource and the second SSB sent by the first adjacent TRP, or both.

[0233] Clause 42. The UE of clause 41, wherein the first SSB is a cell-defined SSB (CD-SSB) and the second SSB is a non-cell-defined SSB (NCD-SSB).

[0234] Clause 43. The UE of clause 42, wherein the second configuration information comprises association information between the NCD-SSB and the CD-SSB.

[0235] Clause 44. A UE as set forth in any of clauses 42 to 43, wherein the second configuration information comprises an association of the first PRS resource with the NCD-SSB.

[0236] Clause 45. A UE according to any one of clauses 41 to 44, wherein: the first SSB sent by the first adjacent TRP is sent within the bandwidth of a first bandwidth part (BWP), the second SSB sent by the first adjacent TRP is sent within the bandwidth of a second BWP, and the first positioning measurement result is obtained based on the measurement result of the first PRS resource in the bandwidth of the second BWP rather than in the bandwidth of the first BWP.

[0237] Clause 46. A UE according to any one of clauses 41 to 45, wherein the UE further includes: a component for receiving third configuration information of a second PRS resource sent by a second adjacent TRP, the third configuration information indicating a first QCL relationship between the second PRS resource and the first SSB sent by the second adjacent TRP; a component for receiving fourth configuration information, the fourth configuration information indicating a second QCL relationship between the second PRS resource and the second SSB sent by the second adjacent TRP; and a component for obtaining a second positioning measurement result of the second PRS resource based on the first QCL relationship between the second PRS resource and the CD-SSB sent by the second adjacent TRP, the second QCL relationship between the second PRS resource and the NCD-SSB sent by the second adjacent TRP, or both.

[0238] Clause 47. A UE according to clause 46, wherein: the first SSB sent by the second adjacent TRP and the second SSB sent by the first adjacent TRP are sent in the bandwidth of a first BWP, the first SSB sent by the first adjacent TRP is sent in the bandwidth of a second BWP, and the first positioning measurement result is obtained based on the measurement result of the first PRS resource in the bandwidth of the first BWP rather than in the bandwidth of the second BWP.

[0239] Clause 48. A UE according to any one of clauses 41 to 47, wherein the first configuration information indicating the first QCL relationship between the first PRS resource and the first SSB and the second QCL relationship between the first PRS resource and the second SSB includes a DL-PRS-QCL-Info information element in the configuration information indicating both the first SSB and the second SSB.

[0240] Clause 49. A UE according to any one of clauses 41 to 48, wherein the first configuration information indicating the first QCL relationship between the first PRS resource and the first SSB and the second QCL relationship between the first PRS resource and the second SSB includes a DL-PRS-Resource information element indicating the first QCL relationship and the second QCL relationship in the configuration information.

[0241] Clause 50. A UE as set forth in any of clauses 41 to 49, wherein the first configuration information is received from a location server in Long Term Evolution (LTE) Positioning Protocol (LPP) assistance data.

[0242] Clause 51. A UE as set out in any of clauses 41 to 50, wherein the UE is a reduced capability (RedCap) UE.

[0243] Clause 52. A user equipment (UE), the user equipment (UE) comprising: a component for receiving first configuration information of a first sounding reference signal (SRS) resource, the first configuration information indicating a first quasi-co-location (QCL) relationship between the first SRS resource and a first SSB sent by a first adjacent transmit receive point (TRP); a component for receiving second configuration information, the second configuration information indicating a second QCL relationship between the first SRS resource and a second SSB sent by the first adjacent TRP); and a component for sending the first SRS resource based on the first QCL relationship between the first SRS resource and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first SRS resource and the second SSB sent by the first adjacent TRP, or both.

[0244] Clause 53. The UE of clause 52, wherein the first SSB is a cell-defined SSB (CD-SSB) and the second SSB is a non-cell-defined SSB (NCD-SSB).

[0245] Clause 54. The UE of clause 53, wherein the second configuration information comprises association information between the NCD-SSB and the CD-SSB.

[0246] Clause 55. A UE as described in any of clauses 53 to 54, wherein the second configuration information comprises an association of the first SRS resource with the NCD-SSB.

[0247] Clause 56. A UE according to any one of clauses 52 to 55, wherein: the first SSB sent by the first adjacent TRP is sent in the bandwidth of a first bandwidth part (BWP), the second SSB sent by the first adjacent TRP is sent in the bandwidth of a second BWP, and the first SRS is sent based on the measurement result of the second SSB in the bandwidth of the second BWP instead of the measurement result of the first SSB in the bandwidth of the first BWP.

[0248] Clause 57. A UE according to any one of clauses 52 to 56, wherein the first configuration information indicating the first QCL relationship between the first SRS resource and the first SSB and the second QCL relationship between the first SRS resource and the second SSB includes an SRS-SpatialRelationInfo information element in the configuration information indicating a first SSB configuration for the first SSB and a second SSB configuration for the second SSB.

[0249] Clause 58. A UE according to any one of clauses 52 to 57, wherein the first configuration information indicating the first QCL relationship between the first PRS resource and the first SSB and the second QCL relationship between the first PRS resource and the second SSB includes an SSB-Configuration information element in the configuration information indicating configuration information for both the first SSB and the second SSB.

[0250] Clause 59. A UE as set forth in any of clauses 52 to 58, wherein the first configuration information is received from a serving base station via radio resource control (RRC) signaling.

[0251] Clause 60. A UE as set out in any of clauses 52 to 59, wherein the UE is a reduced capability (RedCap) UE.

[0252] Clause 61. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), causes the UE to: receive first configuration information for a first positioning reference signal (PRS) resource sent by a first adjacent transmit receive point (TRP), the first configuration information indicating a first quasi-co-location (QCL) relationship between the first PRS resource and a first synchronization signal block (SSB) sent by the first adjacent TRP; receive second configuration information, the second configuration information indicating a second QCL relationship between the first PRS resource and a second SSB sent by the first adjacent TRP; and obtain a first positioning measurement result for the PRS resource based on the first QCL relationship between the first PRS resource and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first PRS resource and the second SSB sent by the first adjacent TRP, or both.

[0253] Clause 62. The non-transitory computer-readable medium of Clause 61, wherein the first SSB is a cell-definition SSB (CD-SSB) and the second SSB is a non-cell-definition SSB (NCD-SSB).

[0254] Clause 63. The non-transitory computer-readable medium of Clause 62, wherein the second configuration information comprises association information between the NCD-SSB and the CD-SSB.

[0255] Clause 64. The non-transitory computer-readable medium of any of Clauses 62 to 63, wherein the second configuration information comprises an association of the first PRS resource with the NCD-SSB.

[0256] Clause 65. A non-transitory computer-readable medium according to any one of clauses 61 to 64, wherein: the first SSB sent by the first adjacent TRP is sent within the bandwidth of a first bandwidth part (BWP), the second SSB sent by the first adjacent TRP is sent within the bandwidth of a second BWP, and the first positioning measurement result is obtained based on the measurement result of the first PRS resource in the bandwidth of the second BWP rather than in the bandwidth of the first BWP.

[0257] Clause 66. A non-transitory computer-readable medium according to any one of clauses 61 to 65, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the UE, cause the UE to: receive third configuration information of a second PRS resource sent by a second adjacent TRP, the third configuration information indicating a first QCL relationship between the second PRS resource and a first SSB sent by the second adjacent TRP; receive fourth configuration information indicating a second QCL relationship between the second PRS resource and a second SSB sent by the second adjacent TRP; and obtain a second positioning measurement result of the second PRS resource based on the first QCL relationship between the second PRS resource and the CD-SSB sent by the second adjacent TRP, the second QCL relationship between the second PRS resource and the NCD-SSB sent by the second adjacent TRP, or both.

[0258] Clause 67. A non-transitory computer-readable medium according to clause 66, wherein: the first SSB sent by the second adjacent TRP and the second SSB sent by the first adjacent TRP are sent in the bandwidth of a first BWP, the first SSB sent by the first adjacent TRP is sent in the bandwidth of a second BWP, and the first positioning measurement result is obtained based on the measurement result of the first PRS resource in the bandwidth of the first BWP rather than in the bandwidth of the second BWP.

[0259] Clause 68. A non-transitory computer-readable medium according to any one of clauses 61 to 67, wherein the first configuration information indicating the first QCL relationship between the first PRS resource and the first SSB and the second QCL relationship between the first PRS resource and the second SSB includes a DL-PRS-QCL-Info information element in the configuration information indicating both the first SSB and the second SSB.

[0260] Clause 69. A non-transitory computer-readable medium according to any one of clauses 61 to 68, wherein the first configuration information indicating the first QCL relationship between the first PRS resource and the first SSB and the second QCL relationship between the first PRS resource and the second SSB includes a DL-PRS-Resource information element indicating the first QCL relationship and the second QCL relationship in the configuration information.

[0261] Clause 70. The non-transitory computer-readable medium of any one of clauses 61 to 69, wherein the first configuration information is received from a location server in Long Term Evolution (LTE) Positioning Protocol (LPP) assistance data.

[0262] Clause 71. The non-transitory computer-readable medium of any of clauses 61 to 70, wherein the UE is a reduced capability (RedCap) UE.

[0263] Clause 72. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), cause the UE to: receive first configuration information for a first sounding reference signal (SRS) resource, the first configuration information indicating a first quasi-co-location (QCL) relationship between the first SRS resource and a first SSB sent by a first adjacent transmit receive point (TRP); receive second configuration information, the second configuration information indicating a second QCL relationship between the first SRS resource and a second SSB sent by the first adjacent TRP; and send the first SRS resource based on the first QCL relationship between the first SRS resource and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first SRS resource and the second SSB sent by the first adjacent TRP, or both.

[0264] Clause 73. The non-transitory computer-readable medium of Clause 72, wherein the first SSB is a cell-definition SSB (CD-SSB) and the second SSB is a non-cell-definition SSB (NCD-SSB).

[0265] Clause 74. The non-transitory computer-readable medium of Clause 73, wherein the second configuration information comprises association information between the NCD-SSB and the CD-SSB.

[0266] Clause 75. The non-transitory computer-readable medium of any of clauses 73 to 74, wherein the second configuration information comprises an association of the first SRS resource with the NCD-SSB.

[0267] Clause 76. A non-transitory computer-readable medium according to any one of clauses 72 to 75, wherein: the first SSB sent by the first adjacent TRP is sent in the bandwidth of a first bandwidth part (BWP), the second SSB sent by the first adjacent TRP is sent in the bandwidth of a second BWP, and the first SRS is sent based on the measurement result of the second SSB in the bandwidth of the second BWP rather than the measurement result of the first SSB in the bandwidth of the first BWP.

[0268] Clause 77. A non-transitory computer-readable medium according to any one of clauses 72 to 76, wherein the first configuration information indicating the first QCL relationship between the first SRS resource and the first SSB and the second QCL relationship between the first SRS resource and the second SSB includes an SRS-SpatialRelationInfo information element in the configuration information indicating a first SSB configuration for the first SSB and a second SSB configuration for the second SSB.

[0269] Clause 78. A non-transitory computer-readable medium according to any one of clauses 72 to 77, wherein the first configuration information indicating the first QCL relationship between the first PRS resource and the first SSB and the second QCL relationship between the first PRS resource and the second SSB includes an SSB-Configuration information element in the configuration information indicating configuration information for both the first SSB and the second SSB.

[0270] Clause 79. The non-transitory computer-readable medium of any of clauses 72 to 78, wherein the first configuration information is received from a serving base station via radio resource control (RRC) signaling.

[0271] Clause 80. The non-transitory computer-readable medium of any of clauses 72 to 79, wherein the UE is a reduced capability (RedCap) UE.

[0272] Additional specific implementation examples are described in the following numbered clauses:

[0273] Clause 1. A method for performing wireless communication by a user equipment (UE), the method comprising: receiving first configuration information of a first positioning reference signal (PRS) resource sent by a first neighboring transmit reception point (TRP), the first configuration information indicating a first quasi-co-location (QCL) relationship between the first PRS resource and a first synchronization signal block (SSB) sent by the first neighboring TRP, wherein the first SSB is a non-cell-defined SSB (NCD-SSB); and obtaining a first positioning measurement result of the first PRS resource based on the QCL relationship between the first PRS resource and the SSB sent by the first neighboring TRP.

[0274] Clause 2. The method according to clause 1 further includes: determining second configuration information, the second configuration information indicating a second QCL relationship between the first PRS resource and a second SSB sent by the first adjacent TRP, wherein the second SSB is a cell-defined SSB (CD-SSB).

[0275] Clause 3. A method according to Clause 2, wherein obtaining the first positioning measurement result of the first PRS resource based on the QCL relationship between the first PRS resource and the SSB sent by the first adjacent TRP includes: obtaining the first positioning measurement result of the first PRS resource based on the first QCL relationship between the first PRS resource and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first PRS resource and the second SSB sent by the first adjacent TRP, or both.

[0276] Clause 4. The method of any of clauses 2 to 3, wherein determining the second configuration information comprises receiving the second configuration information from a location server via Long Term Evolution (LTE) Positioning Protocol (LPP) signaling.

[0277] Clause 5. A method according to any one of clauses 2 to 4, wherein the second configuration information includes association information between the NCD-SSB and the CD-SSB.

[0278] Clause 6. A method as described in any of clauses 2 to 5, wherein the second configuration information includes an association of the first PRS resource with the NCD-SSB.

[0279] Clause 7. A method according to any one of clauses 2 to 6, wherein the DL-PRS-QCL-Info information element in the first configuration information indicates both the first SSB and the second SSB.

[0280] Clause 8. A method according to any one of clauses 2 to 7, wherein a DL-PRS-Resource information element in the first configuration information indicates the first QCL relationship and the second QCL relationship.

[0281] Clause 9. A method according to any one of clauses 2 to 8, wherein: the first SSB sent by the first adjacent TRP is sent within the bandwidth of a first bandwidth part (BWP), the second SSB sent by the first adjacent TRP is sent within the bandwidth of a second BWP, and the first positioning measurement result is obtained based on the measurement result of the first PRS resource in the bandwidth of the second BWP rather than in the bandwidth of the first BWP.

[0282] Clause 10. According to the method described in any one of clauses 1 to 9, the method further includes: receiving third configuration information of a second PRS resource sent by a second adjacent TRP, the third configuration information indicating a first QCL relationship between the second PRS resource and the first SSB sent by the second adjacent TRP; determining fourth configuration information, the fourth configuration information indicating a second QCL relationship between the second PRS resource and the second SSB sent by the second adjacent TRP; and obtaining a second positioning measurement result of the second PRS resource based on the first QCL relationship between the second PRS resource and the CD-SSB sent by the second adjacent TRP, the second QCL relationship between the second PRS resource and the NCD-SSB sent by the second adjacent TRP, or both.

[0283] Clause 11. A method according to Clause 10, wherein: the first SSB sent by the second adjacent TRP and the second SSB sent by the first adjacent TRP are sent in the bandwidth of a first BWP, the first SSB sent by the first adjacent TRP is sent in the bandwidth of a second BWP, and the first positioning measurement result is obtained based on the measurement result of the first PRS resource in the bandwidth of the first BWP rather than the bandwidth of the second BWP.

[0284] Clause 12. A method as described in any of clauses 1 to 11, wherein the first configuration information is received from a location server in LPP positioning assistance data.

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

[0286] Clause 14. A method for performing wireless communication by a user equipment (UE), the method comprising: receiving first configuration information of a first sounding reference signal (SRS) resource for positioning, the first configuration information indicating a first quasi-co-location (QCL) relationship between the first SRS resource for positioning and a first SSB sent by a first adjacent transmit receive point (TRP), wherein the first SSB is a non-cell defined SSB (NCD-SSB); and sending the first SRS resource for positioning based on the QCL relationship between the first SRS resource for positioning and the SSB sent by the first adjacent TRP.

[0287] Clause 15. The method according to clause 14 further includes: determining second configuration information, the second configuration information indicating a second QCL relationship between the first SRS resource used for positioning and a second SSB sent by the first neighboring TRP, wherein the second SSB is a cell-defined SSB (CD-SSB).

[0288] Clause 16. A method according to Clause 15, wherein sending the first SRS resource for positioning based on the QCL relationship between the first SRS resource for positioning and the SSB sent by the first adjacent TRP includes: sending the first SRS resource for positioning based on the first QCL relationship between the first SRS resource for positioning and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first SRS resource for positioning and the second SSB sent by the first adjacent TRP, or both.

[0289] Clause 17. A method as described in any of clauses 15 to 16, wherein determining the second configuration information comprises: receiving the second configuration information from a serving TRP via radio resource control (RRC) signaling.

[0290] Clause 18. The method according to any one of clauses 15 to 17, wherein the second configuration information includes association information between the NCD-SSB and the CD-SSB.

[0291] Clause 19. A method as described in any of clauses 15 to 18, wherein the second configuration information includes an association of the first SRS resource for positioning with the NCD-SSB.

[0292] Clause 20. A method according to any one of clauses 15 to 19, wherein: the first SSB sent by the first adjacent TRP is sent in the bandwidth of a first bandwidth part (BWP), the second SSB sent by the first adjacent TRP is sent in the bandwidth of a second BWP, and the first SRS resource is sent based on the measurement result of the second SSB in the bandwidth of the second BWP rather than the measurement result of the first SSB in the bandwidth of the first BWP.

[0293] Clause 21. A method according to any one of clauses 15 to 20, wherein the SRS-SpatialRelationInfo information element in the first configuration information indicates a first SSB configuration for the first SSB and a second SSB configuration for the second SSB.

[0294] Clause 22. A method according to any one of clauses 15 to 21, wherein the SSB-Configuration information element in the first configuration information indicates configuration information of both the first SSB and the second SSB.

[0295] Clause 23. A method as described in any of clauses 14 to 22, wherein the first configuration information is received from a serving base station via RRC signaling.

[0296] Clause 24. A method as described in any of clauses 14 to 23, wherein the UE is a reduced capability (RedCap) UE.

[0297] Clause 25. A user equipment (UE), the user equipment (UE) comprising: one or more memories; one or more transceivers; and one or more processors, the one or more processors being communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being configured individually or in combination to: receive, via the one or more transceivers, first configuration information of a first positioning reference signal (PRS) resource sent by a first neighboring transmit reception point (TRP), the first configuration information indicating a first quasi-co-location (QCL) relationship between the first PRS resource and a first synchronization signal block (SSB) sent by the first neighboring TRP, wherein the first SSB is a non-cell-defined SSB (NCD-SSB); and obtain a first positioning measurement result of the first PRS resource based on the QCL relationship between the first PRS resource and the SSB sent by the first neighboring TRP.

[0298] Clause 26. A UE according to clause 25, wherein the one or more processors are further configured, individually or in combination, to: determine second configuration information, the second configuration information indicating a second QCL relationship between the first PRS resource and a second SSB sent by the first adjacent TRP, wherein the second SSB is a cell-defined SSB (CD-SSB).

[0299] Clause 27. A UE according to Clause 26, wherein the one or more processors configured to obtain the first positioning measurement result of the first PRS resource based on the QCL relationship between the first PRS resource and the SSB sent by the first adjacent TRP include the one or more processors configured, individually or in combination, to perform the following operations: obtain the first positioning measurement result of the first PRS resource based on the first QCL relationship between the first PRS resource and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first PRS resource and the second SSB sent by the first adjacent TRP, or both.

[0300] Clause 28. A UE according to any one of clauses 26 to 27, wherein the one or more processors configured to determine the second configuration information include the one or more processors configured, individually or in combination, to perform the following operations: receiving the second configuration information from a location server via Long Term Evolution (LTE) Positioning Protocol (LPP) signaling via the one or more transceivers.

[0301] Clause 29. A UE as described in any of clauses 26 to 28, wherein the second configuration information includes association information between the NCD-SSB and the CD-SSB.

[0302] Clause 30. A UE as set forth in any of clauses 26 to 29, wherein the second configuration information comprises an association of the first PRS resource with the NCD-SSB.

[0303] Clause 31. A UE according to any of clauses 26 to 30, wherein the DL-PRS-QCL-Info information element in the first configuration information indicates both the first SSB and the second SSB.

[0304] Clause 32. A UE as described in any of clauses 26 to 31, wherein a DL-PRS-Resource information element in the first configuration information indicates the first QCL relationship and the second QCL relationship.

[0305] Clause 33. A UE according to any one of clauses 26 to 32, wherein: the first SSB sent by the first adjacent TRP is sent within the bandwidth of a first bandwidth part (BWP), the second SSB sent by the first adjacent TRP is sent within the bandwidth of a second BWP, and the first positioning measurement result is obtained based on the measurement result of the first PRS resource in the bandwidth of the second BWP rather than in the bandwidth of the first BWP.

[0306] Clause 34. A UE according to any one of clauses 25 to 33, wherein the one or more processors are further configured, individually or in combination, to: receive, via the one or more transceivers, third configuration information of a second PRS resource sent by a second adjacent TRP, the third configuration information indicating a first QCL relationship between the second PRS resource and a first SSB sent by the second adjacent TRP; determine fourth configuration information, the fourth configuration information indicating a second QCL relationship between the second PRS resource and a second SSB sent by the second adjacent TRP; and obtain a second positioning measurement result of the second PRS resource based on the first QCL relationship between the second PRS resource and the CD-SSB sent by the second adjacent TRP, the second QCL relationship between the second PRS resource and the NCD-SSB sent by the second adjacent TRP, or both.

[0307] Clause 35. A UE according to clause 34, wherein: the first SSB sent by the second adjacent TRP and the second SSB sent by the first adjacent TRP are sent in the bandwidth of a first BWP, the first SSB sent by the first adjacent TRP is sent in the bandwidth of a second BWP, and the first positioning measurement result is obtained based on the measurement result of the first PRS resource in the bandwidth of the first BWP rather than in the bandwidth of the second BWP.

[0308] Clause 36. A UE as set forth in any of clauses 25 to 35, wherein the first configuration information is received in LPP positioning assistance data from a location server.

[0309] Clause 37. A UE as set out in any of clauses 25 to 36, wherein the UE is a reduced capability (RedCap) UE.

[0310] Clause 38. A user equipment (UE), the user equipment (UE) comprising: one or more memories; one or more transceivers; and one or more processors, the one or more processors being communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being configured individually or in combination to: receive, via the one or more transceivers, first configuration information of a first sounding reference signal (SRS) resource for positioning, the first configuration information indicating a first quasi-co-location (QCL) relationship between the first SRS resource for positioning and a first SSB sent by a first adjacent transmit receive point (TRP), wherein the first SSB is a non-cell defined SSB (NCD-SSB); and send, via the one or more transceivers, the first SRS resource for positioning based on the QCL relationship between the first SRS resource for positioning and the SSB sent by the first adjacent TRP.

[0311] Clause 39. A UE according to clause 38, wherein the one or more processors are further configured, individually or in combination, to: determine second configuration information, the second configuration information indicating a second QCL relationship between the first SRS resource used for positioning and a second SSB sent by the first adjacent TRP, wherein the second SSB is a cell-defined SSB (CD-SSB).

[0312] Clause 40. A UE according to clause 39, wherein the one or more processors configured to send the first SRS resource for positioning based on the QCL relationship between the first SRS resource for positioning and the SSB sent by the first adjacent TRP include the one or more processors configured, individually or in combination, to perform the following operations: sending the first SRS resource for positioning via the one or more transceivers based on the first QCL relationship between the first SRS resource for positioning and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first SRS resource for positioning and the second SSB sent by the first adjacent TRP, or both.

[0313] Clause 41. A UE according to any one of clauses 39 to 40, wherein the one or more processors configured to determine the second configuration information include the one or more processors configured, individually or in combination, to perform the following operations: receiving the second configuration information from a serving TRP via radio resource control (RRC) signaling via the one or more transceivers.

[0314] Clause 42. A UE as described in any of clauses 39 to 41, wherein the second configuration information includes association information between the NCD-SSB and the CD-SSB.

[0315] Clause 43. A UE as described in any of clauses 39 to 42, wherein the second configuration information comprises an association of the first SRS resource for positioning with the NCD-SSB.

[0316] Clause 44. A UE according to any one of clauses 39 to 43, wherein: the first SSB sent by the first adjacent TRP is sent in the bandwidth of a first bandwidth part (BWP), the second SSB sent by the first adjacent TRP is sent in the bandwidth of a second BWP, and the first SRS resource is sent based on the measurement result of the second SSB in the bandwidth of the second BWP rather than the measurement result of the first SSB in the bandwidth of the first BWP.

[0317] Clause 45. A UE according to any of clauses 39 to 44, wherein the SRS-SpatialRelationInfo information element in the first configuration information indicates a first SSB configuration for the first SSB and a second SSB configuration for the second SSB.

[0318] Clause 46. A UE according to any of clauses 39 to 45, wherein the SSB-Configuration information element in the first configuration information indicates configuration information of both the first SSB and the second SSB.

[0319] Clause 47. A UE as set forth in any of clauses 38 to 46, wherein the first configuration information is received from a serving base station via RRC signaling.

[0320] Clause 48. A UE as set out in any of clauses 38 to 47, wherein the UE is a reduced capability (RedCap) UE.

[0321] Clause 49. A user equipment (UE), the user equipment (UE) comprising: a component for receiving first configuration information of a first positioning reference signal (PRS) resource sent by a first neighboring transmit reception point (TRP), the first configuration information indicating a first quasi-co-location (QCL) relationship between the first PRS resource and a first synchronization signal block (SSB) sent by the first neighboring TRP, wherein the first SSB is a non-cell-defined SSB (NCD-SSB); and a component for obtaining a first positioning measurement result of the first PRS resource based on the QCL relationship between the first PRS resource and the SSB sent by the first neighboring TRP.

[0322] Clause 50. A UE according to clause 49, the UE further comprising: a component for determining second configuration information, the second configuration information indicating a second QCL relationship between the first PRS resource and a second SSB sent by the first neighboring TRP, wherein the second SSB is a cell-defined SSB (CD-SSB).

[0323] Clause 51. A UE according to clause 50, wherein the component for obtaining the first positioning measurement result of the first PRS resource based on the QCL relationship between the first PRS resource and the SSB sent by the first adjacent TRP includes: a component for obtaining the first positioning measurement result of the first PRS resource based on the first QCL relationship between the first PRS resource and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first PRS resource and the second SSB sent by the first adjacent TRP, or both.

[0324] Clause 52. A UE as set forth in any of clauses 50 to 51, wherein the means for determining the second configuration information comprises means for receiving the second configuration information from a location server via Long Term Evolution (LTE) Positioning Protocol (LPP) signaling.

[0325] Clause 53. A UE as described in any of clauses 50 to 52, wherein the second configuration information includes association information between the NCD-SSB and the CD-SSB.

[0326] Clause 54. A UE as set forth in any of clauses 50 to 53, wherein the second configuration information comprises an association of the first PRS resource with the NCD-SSB.

[0327] Clause 55. A UE as described in any of clauses 50 to 54, wherein the DL-PRS-QCL-Info information element in the first configuration information indicates both the first SSB and the second SSB.

[0328] Clause 56. A UE as set forth in any of clauses 50 to 55, wherein a DL-PRS-Resource information element in the first configuration information indicates the first QCL relationship and the second QCL relationship.

[0329] Clause 57. A UE according to any one of clauses 50 to 56, wherein: the first SSB sent by the first adjacent TRP is sent within the bandwidth of a first bandwidth part (BWP), the second SSB sent by the first adjacent TRP is sent within the bandwidth of a second BWP, and the first positioning measurement result is obtained based on the measurement result of the first PRS resource in the bandwidth of the second BWP rather than in the bandwidth of the first BWP.

[0330] Clause 58. A UE according to any one of clauses 49 to 57, wherein the UE further includes: a component for receiving third configuration information of a second PRS resource sent by a second adjacent TRP, the third configuration information indicating a first QCL relationship between the second PRS resource and the first SSB sent by the second adjacent TRP; a component for determining fourth configuration information, the fourth configuration information indicating a second QCL relationship between the second PRS resource and the second SSB sent by the second adjacent TRP; and a component for obtaining a second positioning measurement result of the second PRS resource based on the first QCL relationship between the second PRS resource and the CD-SSB sent by the second adjacent TRP, the second QCL relationship between the second PRS resource and the NCD-SSB sent by the second adjacent TRP, or both.

[0331] Clause 59. A UE according to Clause 58, wherein: the first SSB sent by the second adjacent TRP and the second SSB sent by the first adjacent TRP are sent in the bandwidth of a first BWP, the first SSB sent by the first adjacent TRP is sent in the bandwidth of a second BWP, and the first positioning measurement result is obtained based on the measurement result of the first PRS resource in the bandwidth of the first BWP rather than in the bandwidth of the second BWP.

[0332] Clause 60. A UE as set forth in any of clauses 49 to 59, wherein the first configuration information is received in LPP positioning assistance data from a location server.

[0333] Clause 61. A UE as set out in any of clauses 49 to 60, wherein the UE is a reduced capability (RedCap) UE.

[0334] Clause 62. A user equipment (UE), the user equipment (UE) comprising: a component for receiving first configuration information of a first sounding reference signal (SRS) resource for positioning, the first configuration information indicating a first quasi-co-location (QCL) relationship between the first SRS resource for positioning and a first SSB sent by a first adjacent transmit receive point (TRP), wherein the first SSB is a non-cell defined SSB (NCD-SSB); and a component for sending the first SRS resource for positioning based on the QCL relationship between the first SRS resource for positioning and the SSB sent by the first adjacent TRP.

[0335] Clause 63. The UE according to clause 62 further includes: a component for determining second configuration information, wherein the second configuration information indicates a second QCL relationship between the first SRS resource used for positioning and a second SSB sent by the first adjacent TRP, wherein the second SSB is a cell-defined SSB (CD-SSB).

[0336] Clause 64. A UE according to clause 63, wherein the component for sending the first SRS resource for positioning based on the QCL relationship between the first SRS resource for positioning and the SSB sent by the first adjacent TRP includes: a component for sending the first SRS resource for positioning based on the first QCL relationship between the first SRS resource for positioning and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first SRS resource for positioning and the second SSB sent by the first adjacent TRP, or both.

[0337] Clause 65. A UE as set forth in any of clauses 63 to 64, wherein the means for determining the second configuration information comprises means for receiving the second configuration information from a serving TRP via radio resource control (RRC) signaling.

[0338] Clause 66. A UE as described in any of clauses 63 to 65, wherein the second configuration information includes association information between the NCD-SSB and the CD-SSB.

[0339] Clause 67. A UE as set forth in any of clauses 63 to 66, wherein the second configuration information comprises an association of the first SRS resource for positioning with the NCD-SSB.

[0340] Clause 68. A UE according to any one of clauses 63 to 67, wherein: the first SSB sent by the first adjacent TRP is sent in the bandwidth of a first bandwidth part (BWP), the second SSB sent by the first adjacent TRP is sent in the bandwidth of a second BWP, and the first SRS resource is sent based on the measurement result of the second SSB in the bandwidth of the second BWP rather than the measurement result of the first SSB in the bandwidth of the first BWP.

[0341] Clause 69. A UE according to any of clauses 63 to 68, wherein the SRS-SpatialRelationInfo information element in the first configuration information indicates a first SSB configuration for the first SSB and a second SSB configuration for the second SSB.

[0342] Clause 70. A UE according to any of clauses 63 to 69, wherein the SSB-Configuration information element in the first configuration information indicates configuration information for both the first SSB and the second SSB.

[0343] Clause 71. A UE as set forth in any of clauses 62 to 70, wherein the first configuration information is received from a serving base station via RRC signaling.

[0344] Clause 72. A UE as set forth in any of clauses 62 to 71, wherein the UE is a reduced capability (RedCap) UE.

[0345] Clause 73. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), causes the UE to: receive first configuration information of a first positioning reference signal (PRS) resource sent by a first neighboring transmit reception point (TRP), the first configuration information indicating a first quasi-co-location (QCL) relationship between the first PRS resource and a first synchronization signal block (SSB) sent by the first neighboring TRP, wherein the first SSB is a non-cell-defined SSB (NCD-SSB); and obtain a first positioning measurement result of the first PRS resource based on the QCL relationship between the first PRS resource and the SSB sent by the first neighboring TRP.

[0346] Clause 74. A non-transitory computer-readable medium according to clause 73, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the UE, cause the UE to: determine second configuration information, the second configuration information indicating a second QCL relationship between the first PRS resource and a second SSB sent by the first adjacent TRP, wherein the second SSB is a cell-defined SSB (CD-SSB).

[0347] Clause 75. A non-transitory computer-readable medium according to clause 74, wherein the computer executable instructions that, when executed by the UE, cause the UE to obtain the first positioning measurement result of the first PRS resource based on the QCL relationship between the first PRS resource and the SSB sent by the first adjacent TRP include computer executable instructions that, when executed by the UE, cause the UE to perform the following operations: obtain the first positioning measurement result of the first PRS resource based on the first QCL relationship between the first PRS resource and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first PRS resource and the second SSB sent by the first adjacent TRP, or both.

[0348] Clause 76. A non-transitory computer-readable medium according to any one of clauses 74 to 75, wherein the computer-executable instructions that, when executed by the UE, cause the UE to determine the second configuration information include computer-executable instructions that, when executed by the UE, cause the UE to perform the following operations: receiving the second configuration information from a location server via Long Term Evolution (LTE) Positioning Protocol (LPP) signaling.

[0349] Clause 77. The non-transitory computer-readable medium of any one of clauses 74 to 76, wherein the second configuration information comprises association information between the NCD-SSB and the CD-SSB.

[0350] Clause 78. The non-transitory computer-readable medium of any of clauses 74 to 77, wherein the second configuration information comprises an association of the first PRS resource with the NCD-SSB.

[0351] Clause 79. A non-transitory computer-readable medium as described in any of clauses 74 to 78, wherein the DL-PRS-QCL-Info information element in the first configuration information indicates both the first SSB and the second SSB.

[0352] Clause 80. The non-transitory computer-readable medium of any one of clauses 74 to 79, wherein a DL-PRS-Resource information element in the first configuration information indicates the first QCL relationship and the second QCL relationship.

[0353] Clause 81. A non-transitory computer-readable medium according to any one of clauses 74 to 80, wherein: the first SSB sent by the first adjacent TRP is sent within the bandwidth of a first bandwidth part (BWP), the second SSB sent by the first adjacent TRP is sent within the bandwidth of a second BWP, and the first positioning measurement result is obtained based on the measurement result of the first PRS resource in the bandwidth of the second BWP rather than in the bandwidth of the first BWP.

[0354] Clause 82. A non-transitory computer-readable medium according to any one of clauses 73 to 81, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the UE, cause the UE to: receive third configuration information of a second PRS resource sent by a second adjacent TRP, the third configuration information indicating a first QCL relationship between the second PRS resource and a first SSB sent by the second adjacent TRP; determine fourth configuration information, the fourth configuration information indicating a second QCL relationship between the second PRS resource and a second SSB sent by the second adjacent TRP; and obtain a second positioning measurement result of the second PRS resource based on the first QCL relationship between the second PRS resource and a CD-SSB sent by the second adjacent TRP, the second QCL relationship between the second PRS resource and a NCD-SSB sent by the second adjacent TRP, or both.

[0355] Clause 83. A non-transitory computer-readable medium according to clause 82, wherein: the first SSB sent by the second adjacent TRP and the second SSB sent by the first adjacent TRP are sent in the bandwidth of a first BWP, the first SSB sent by the first adjacent TRP is sent in the bandwidth of a second BWP, and the first positioning measurement result is obtained based on the measurement result of the first PRS resource in the bandwidth of the first BWP rather than in the bandwidth of the second BWP.

[0356] Clause 84. The non-transitory computer-readable medium of any one of clauses 73 to 83, wherein the first configuration information is received in LPP positioning assistance data from a location server.

[0357] Clause 85. The non-transitory computer-readable medium of any of clauses 73 to 84, wherein the UE is a reduced capability (RedCap) UE.

[0358] Clause 86. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), causes the UE to: receive first configuration information of a first sounding reference signal (SRS) resource for positioning, the first configuration information indicating a first quasi-co-location (QCL) relationship between the first SRS resource for positioning and a first SSB sent by a first adjacent transmit receive point (TRP), wherein the first SSB is a non-cell defined SSB (NCD-SSB); and send the first SRS resource for positioning based on the QCL relationship between the first SRS resource for positioning and the SSB sent by the first adjacent TRP.

[0359] Clause 87. A non-transitory computer-readable medium according to clause 86, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the UE, cause the UE to: determine second configuration information, the second configuration information indicating a second QCL relationship between the first SRS resource used for positioning and a second SSB sent by the first adjacent TRP, wherein the second SSB is a cell-defined SSB (CD-SSB).

[0360] Clause 88. A non-transitory computer-readable medium according to clause 87, wherein the computer executable instructions that, when executed by the UE, cause the UE to send the first SRS resource for positioning based on the QCL relationship between the first SRS resource for positioning and the SSB sent by the first adjacent TRP include computer executable instructions that, when executed by the UE, cause the UE to perform the following operations: sending the first SRS resource for positioning based on the first QCL relationship between the first SRS resource for positioning and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first SRS resource for positioning and the second SSB sent by the first adjacent TRP, or both.

[0361] Clause 89. A non-transitory computer-readable medium according to any one of clauses 87 to 88, wherein the computer-executable instructions that, when executed by the UE, cause the UE to determine the second configuration information include computer-executable instructions that, when executed by the UE, cause the UE to perform the following operations: receive the second configuration information from a serving TRP via radio resource control (RRC) signaling.

[0362] Clause 90. The non-transitory computer-readable medium of any one of clauses 87 to 89, wherein the second configuration information comprises association information between the NCD-SSB and the CD-SSB.

[0363] Clause 91. The non-transitory computer-readable medium of any of clauses 87 to 90, wherein the second configuration information comprises an association of the first SRS resource for positioning with the NCD-SSB.

[0364] Clause 92. A non-transitory computer-readable medium according to any one of clauses 87 to 91, wherein: the first SSB sent by the first adjacent TRP is sent in the bandwidth of a first bandwidth part (BWP), the second SSB sent by the first adjacent TRP is sent in the bandwidth of a second BWP, and the first SRS resource is sent based on the measurement result of the second SSB in the bandwidth of the second BWP rather than the measurement result of the first SSB in the bandwidth of the first BWP.

[0365] Clause 93. A non-transitory computer-readable medium according to any one of clauses 87 to 92, wherein the SRS-SpatialRelationInfo information element in the first configuration information indicates a first SSB configuration for the first SSB and a second SSB configuration for the second SSB.

[0366] Clause 94. A non-transitory computer-readable medium according to any one of clauses 87 to 93, wherein an SSB-Configuration information element in the first configuration information indicates configuration information of both the first SSB and the second SSB.

[0367] Clause 95. The non-transitory computer-readable medium of any of clauses 86 to 94, wherein the first configuration information is received from a serving base station via RRC signaling.

[0368] Clause 96. The non-transitory computer-readable medium of any of clauses 86 to 95, wherein the UE is a reduced capability (RedCap) UE.

[0369] It should be understood by those skilled in the art that information and signals may 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 voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0370] In addition, it will be appreciated by those skilled in the art that the various exemplary 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 exemplary components, frames, modules, circuits and steps have been generally described in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints proposed to the entire system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing deviations from the scope of the present disclosure.

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

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

[0373] In one or more example aspects, the function may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the function may be stored on a computer-readable medium or sent via a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, including any medium that facilitates the transfer of computer programs from one place to another. The storage medium may be any available medium that can be accessed by a computer. Exemplarily and not restrictively, 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 also be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer. Moreover, 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 coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of the 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, where 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.

[0374] Although the foregoing disclosure shows the 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. For example, 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. In addition, any component, function, action or instruction described or claimed herein should not be interpreted as critical or necessary unless explicitly described as such. In addition, as used herein, the terms "set" and "group" and the like are intended to include one or more items and can be used interchangeably with "at least one" and "one or more". Moreover, as used herein, the terms "having" and the like are intended to be open terms that do not limit the elements they modify (for example, an element "having" A may also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated. Moreover, as used herein, the term "or" when used in a series is intended to be open-ended and can be used interchangeably with "and / or" unless otherwise expressly stated (e.g., if used in conjunction with "either" or "only one"), or these alternatives are mutually exclusive (e.g., "one or more" should not be interpreted as "one and more"). In addition, although components, functions, actions, and instructions may be described or claimed in the singular, the plural form is also contemplated unless expressly stated to be limited to the singular. Therefore, as used herein, the articles "one", "a", "the", and "said" are intended to include one or more items and can be used interchangeably with "at least one" and "one or more", etc. Additionally, as used herein, the terms "at least one" and "one or more" include "one" component, function, action, or instruction that performs or is capable of performing the functionality described or claimed, and also include "two or more" components, functions, actions, or instructions that perform or are capable of performing the functionality described or claimed in combination.

Claims

1. A method for performing wireless communication by a user equipment (UE), the method comprising: Receiving first configuration information of a first positioning reference signal (PRS) resource transmitted by a first neighboring transmit reception point (TRP), the first configuration information indicating a first quasi co-location (QCL) relationship between the first PRS resource and a first synchronization signal block (SSB) transmitted by the first neighboring TRP, wherein the first SSB is a non-cell definition SSB (NCD-SSB); as well as A first positioning measurement result of the first PRS resource is obtained based on a QCL relationship between the first PRS resource and the SSB sent by the first adjacent TRP.

2. The method according to claim 1, further comprising: Determine second configuration information indicating a second QCL relationship between the first PRS resource and a second SSB sent by the first neighboring TRP, wherein the second SSB is a cell-defined SSB (CD-SSB).

3. The method of claim 2, wherein obtaining the first positioning measurement result of the first PRS resource based on the QCL relationship between the first PRS resource and the SSB transmitted by the first neighboring TRP comprises: The first positioning measurement result of the first PRS resource is obtained based on the first QCL relationship between the first PRS resource and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first PRS resource and the second SSB sent by the first adjacent TRP, or both.

4. The method according to claim 2, wherein determining the second configuration information comprises: The second configuration information is received from a location server via Long Term Evolution (LTE) Positioning Protocol (LPP) signaling.

5. The method according to claim 2, wherein the second configuration information includes association information between the NCD-SSB and the CD-SSB.

6. The method of claim 2, wherein the second configuration information comprises an association of the first PRS resource with the NCD-SSB.

7. The method of claim 2, wherein the DL-PRS-QCL-Info information element in the first configuration information indicates both the first SSB and the second SSB. 8 . The method according to claim 2 , wherein a DL-PRS-Resource information element in the first configuration information indicates the first QCL relationship and the second QCL relationship.

9. The method according to claim 2, wherein: the first SSB sent by the first neighboring TRP is sent within a bandwidth of a first bandwidth part (BWP), The second SSB sent by the first neighboring TRP is sent within the bandwidth of a second BWP, and The first positioning measurement result is obtained based on a measurement result of the first PRS resource in the bandwidth of the second BWP but not in the bandwidth of the first BWP.

10. The method according to claim 1, further comprising: receiving third configuration information of a second PRS resource sent by a second adjacent TRP, the third configuration information indicating a first QCL relationship between the second PRS resource and a first SSB sent by the second adjacent TRP; Determining fourth configuration information, the fourth configuration information indicating a second QCL relationship between the second PRS resource and a second SSB sent by the second adjacent TRP; as well as A second positioning measurement result of the second PRS resource is obtained based on the first QCL relationship between the second PRS resource and the CD-SSB sent by the second adjacent TRP, the second QCL relationship between the second PRS resource and the NCD-SSB sent by the second adjacent TRP, or both.

11. The method according to claim 10, wherein: the first SSB sent by the second neighboring TRP and the second SSB sent by the first neighboring TRP are sent in a bandwidth of a first BWP, The first SSB sent by the first neighboring TRP is sent in the bandwidth of the second BWP, and The first positioning measurement result is obtained based on a measurement result of the first PRS resource in the bandwidth of the first BWP but not in the bandwidth of the second BWP.

12. The method of claim 1, wherein the first configuration information is received from a location server in LPP positioning assistance data.

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

14. A method of performing wireless communication by a user equipment (UE), the method comprising: Receiving first configuration information of a first sounding reference signal (SRS) resource for positioning, the first configuration information indicating a first quasi co-location (QCL) relationship between the first SRS resource for positioning and a first SSB transmitted by a first neighboring transmit reception point (TRP), wherein the first SSB is a non-cell definition SSB (NCD-SSB); as well as The first SRS resource for positioning is sent based on a QCL relationship between the first SRS resource for positioning and the SSB sent by the first adjacent TRP.

15. The method according to claim 14, further comprising: Determine second configuration information, wherein the second configuration information indicates a second QCL relationship between the first SRS resource used for positioning and a second SSB sent by the first neighboring TRP, wherein the second SSB is a cell-defined SSB (CD-SSB).

16. The method of claim 15, wherein transmitting the first SRS resource for positioning based on the QCL relationship between the first SRS resource for positioning and the SSB transmitted by the first neighboring TRP comprises: The first SRS resource for positioning is sent based on the first QCL relationship between the first SRS resource for positioning and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first SRS resource for positioning and the second SSB sent by the first adjacent TRP, or both.

17. The method of claim 15, wherein determining the second configuration information comprises: The second configuration information is received from a serving TRP via radio resource control (RRC) signaling.

18. The method according to claim 15, wherein the second configuration information includes association information between the NCD-SSB and the CD-SSB.

19. The method according to claim 15, wherein the second configuration information includes an association of the first SRS resource for positioning with the NCD-SSB.

20. The method of claim 15, wherein: the first SSB sent by the first neighboring TRP is sent in a bandwidth of a first bandwidth part (BWP), The second SSB sent by the first neighboring TRP is sent in the bandwidth of a second BWP, and The first SRS resource is sent based on a measurement result of the second SSB in the bandwidth of the second BWP instead of a measurement result of the first SSB in the bandwidth of the first BWP.

21. The method of claim 15, wherein the SRS-SpatialRelationInfo information element in the first configuration information indicates a first SSB configuration for the first SSB and a second SSB configuration for the second SSB.

22. The method of claim 15, wherein an SSB-Configuration information element in the first configuration information indicates configuration information of both the first SSB and the second SSB.

23. The method of claim 14, wherein the first configuration information is received from a serving base station via RRC signaling.

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

25. A user equipment (UE), the user equipment (UE) comprising: one or more memories; one or more transceivers; and one or more processors, the one or more processors being communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to: receiving, via the one or more transceivers, first configuration information of a first positioning reference signal (PRS) resource transmitted by a first neighboring transmit reception point (TRP), the first configuration information indicating a first quasi co-location (QCL) relationship between the first PRS resource and a first synchronization signal block (SSB) transmitted by the first neighboring TRP, wherein the first SSB is a non-cell definition SSB (NCD-SSB); as well as A first positioning measurement result of the first PRS resource is obtained based on a QCL relationship between the first PRS resource and the SSB sent by the first adjacent TRP.

26. The UE of claim 25, wherein the one or more processors, alone or in combination, are further configured to: Determine second configuration information indicating a second QCL relationship between the first PRS resource and a second SSB sent by the first neighboring TRP, wherein the second SSB is a cell-defined SSB (CD-SSB).

27. The UE of claim 26, wherein the one or more processors configured to obtain the first positioning measurement result of the first PRS resource based on the QCL relationship between the first PRS resource and the SSB transmitted by the first neighboring TRP comprises the one or more processors configured to perform the following operations individually or in combination: The first positioning measurement result of the first PRS resource is obtained based on the first QCL relationship between the first PRS resource and the first SSB sent by the first adjacent TRP, the second QCL relationship between the first PRS resource and the second SSB sent by the first adjacent TRP, or both.

28. The UE of claim 25, wherein the one or more processors, alone or in combination, are further configured to: receiving, via the one or more transceivers, third configuration information for a second PRS resource transmitted by a second adjacent TRP, the third configuration information indicating a first QCL relationship between the second PRS resource and a first SSB transmitted by the second adjacent TRP; Determining fourth configuration information, the fourth configuration information indicating a second QCL relationship between the second PRS resource and a second SSB sent by the second adjacent TRP; as well as A second positioning measurement result of the second PRS resource is obtained based on the first QCL relationship between the second PRS resource and the CD-SSB sent by the second adjacent TRP, the second QCL relationship between the second PRS resource and the NCD-SSB sent by the second adjacent TRP, or both.

29. The UE of claim 25, wherein the first configuration information is received from a location server in LPP positioning assistance data.

30. A user equipment (UE), the user equipment (UE) comprising: one or more memories; one or more transceivers; and one or more processors, the one or more processors being communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to: receiving, via the one or more transceivers, first configuration information of a first sounding reference signal (SRS) resource for positioning, the first configuration information indicating a first quasi co-location (QCL) relationship between the first SRS resource for positioning and a first SSB transmitted by a first neighboring transmit reception point (TRP), wherein the first SSB is a non-cell definition SSB (NCD-SSB); as well as The first SRS resource for positioning is sent via the one or more transceivers based on a QCL relationship between the first SRS resource for positioning and the SSB sent by the first adjacent TRP.

Images