Synchronization assistance data for sidelink and UU positioning

By acquiring and utilizing the synchronization state between TRPs in the wireless communication system, the problem of insufficient synchronization auxiliary data in the positioning session is solved, thereby improving positioning accuracy and efficiency.

CN118922734APending Publication Date: 2024-11-08QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380030072.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-12
Filing Date
2023-02-24
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

Existing wireless communication systems lack effective synchronization auxiliary data in positioning sessions, resulting in the inaccurate acquisition and utilization of the synchronization status between anchor nodes, which affects positioning accuracy and efficiency.

Method used

By communicating between the user equipment (UE) and the location server, the synchronization status between multiple transmit/receive points (TRPs) is obtained, and the positioning procedure is executed using the synchronization status to provide synchronization auxiliary data to improve positioning accuracy.

Benefits of technology

It improves the positioning accuracy and efficiency in wireless communication systems, ensures that the synchronization status of anchor nodes is accurately acquired and utilized, thereby enhancing the accuracy and reliability of positioning sessions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118922734A_ABST
    Figure CN118922734A_ABST
Patent Text Reader

Abstract

Techniques for wireless communication are disclosed. In an aspect, a user equipment (UE) receives synchronization assistance data for a positioning session, the synchronization assistance data indicating at least a synchronization state of each of a plurality of anchor nodes with respect to other anchor nodes of the plurality of anchor nodes, and during the positioning session, the synchronization assistance data indicates a synchronization state of each of the plurality of anchor nodes with respect to the other anchor nodes of the plurality of anchor nodes. At least one positioning procedure is performed with at least one anchor node of the plurality of anchor nodes based on the synchronization state of the at least one anchor node.
Need to check novelty before this filing date? Find Prior Art

Description

Background Art 1. Technical Field

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

[0002] 2. Description of related technologies

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

[0004] 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 a reference signal for positioning (RS-P), such as a downlink, uplink, or sidelink positioning reference signal (PRS)), and other technical enhancements compared to previous standards.

[0005] In addition, leveraging the increased data rates and reduced latency of 5G, vehicle-to-everything (V2X) communication technologies are being implemented to support autonomous driving applications, such as wireless communications between vehicles, between vehicles and roadside infrastructure, between vehicles and pedestrians, and so on. Summary of the invention

[0006] The following presents a simplified summary of the invention related to one or more aspects disclosed herein. Thus, 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.

[0007] In one aspect, a method of wireless communication performed by a user equipment (UE) includes: receiving synchronization assistance data for a positioning session, the synchronization assistance data at least indicating a synchronization state of each of a plurality of anchor nodes relative to other anchor nodes of the plurality of anchor nodes; and during the positioning session, based on the synchronization state of at least one anchor node of the plurality of anchor nodes, performing at least one positioning procedure using the at least one anchor node.

[0008] On the one hand, a communication method performed by a location server includes: obtaining a synchronization status of each of a plurality of transmit receive points (TRPs) relative to other TRPs in the plurality of TRPs; and sending synchronization assistance data for a positioning session to a user equipment (UE), the synchronization assistance data at least indicating the synchronization status of each of the plurality of TRPs.

[0009] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive synchronization assistance data for a positioning session via the at least one transceiver, the synchronization assistance data at least indicating a synchronization state of each of a plurality of anchor nodes relative to other anchor nodes of the plurality of anchor nodes; and during the positioning session, perform at least one positioning procedure using the at least one anchor node based on the synchronization state of at least one anchor node of the plurality of anchor nodes.

[0010] In one aspect, a location server includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: obtain a synchronization state of each of a plurality of transmit receive points (TRPs) relative to other TRPs in the plurality of TRPs; and send synchronization assistance data for a positioning session to a user equipment (UE) via the at least one transceiver, the synchronization assistance data at least indicating the synchronization state of each of the plurality of TRPs.

[0011] In one aspect, a user equipment (UE) includes: a component for receiving synchronization assistance data for a positioning session, the synchronization assistance data at least indicating a synchronization state of each of a plurality of anchor nodes relative to other anchor nodes of the plurality of anchor nodes; and a component for performing at least one positioning procedure using at least one anchor node of the plurality of anchor nodes based on the synchronization state of the at least one anchor node during the positioning session.

[0012] On the one hand, a location server includes: a component for obtaining a synchronization status of each of a plurality of transmit receive points (TRPs) relative to other TRPs in the plurality of TRPs; and a component for sending synchronization assistance data for a positioning session to a user equipment (UE), the synchronization assistance data at least indicating the synchronization status of each of the plurality of TRPs.

[0013] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive synchronization assistance data for a positioning session, the synchronization assistance data indicating at least a synchronization state of each of a plurality of anchor nodes relative to other anchor nodes of the plurality of anchor nodes; and during the positioning session, perform at least one positioning procedure using at least one anchor node of the plurality of anchor nodes based on the synchronization state of the at least one anchor node.

[0014] On the one hand, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a location server, cause the location server to: obtain a synchronization state of each of a plurality of transmit receive points (TRPs) relative to other TRPs in the plurality of TRPs; and send synchronization assistance data for a positioning session to a user equipment (UE), the synchronization assistance data at least indicating the synchronization state of each of the plurality of TRPs.

[0015] 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

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

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

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

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

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

[0021] Figure 5 An example Long Term Evolution (LTE) Positioning Protocol (LPP) call flow between a UE and a location server for performing positioning operations is illustrated.

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

[0023] Figure 7 is a diagram illustrating an example sidelink ranging and positioning procedure in accordance with aspects of the present disclosure.

[0024] Figure 8 is a diagram illustrating an example of sidelink based positioning utilizing different sets of synchronous and asynchronous anchor nodes in accordance with aspects of the present disclosure.

[0025] Fig. 9 is a diagram illustrating an example of Uu-based positioning using different sets of synchronous and asynchronous transmit receive points (TRPs) in accordance with aspects of the present disclosure.

[0026] Fig.10 and Fig.11 Example communication methods according to aspects of the present disclosure are illustrated. DETAILED DESCRIPTION

[0027] 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. Additionally, well-known elements of the present disclosure will not be described in detail or will be omitted to avoid making the relevant details of the present disclosure difficult to understand.

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

[0029] Those skilled in the art will appreciate that any of a variety of different techniques and methods may be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the following description may be represented by 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.

[0030] 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. In addition, 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".

[0031] As used herein, the terms "user equipment" (UE), "vehicle UE" (V-UE), "pedestrian UE" (P-UE), and "base station" are not intended to be dedicated to or otherwise limited to any particular radio access technology (RAT), unless otherwise specified. In general, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., a vehicle onboard computer, a vehicle navigation device, a mobile phone, a router, a tablet computer, a laptop computer, an asset location device, a wearable device (e.g., a smart watch, glasses, an augmented reality (AR) / virtual reality (VR) headset, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.). A UE can be mobile or (e.g., at certain times) can be stationary and can communicate with a radio access network (RAN). As used herein, the term "UE" can be interchangeably referred to as a "mobile device", "access terminal" or "AT", "client device", "wireless device", "subscriber device", "subscriber terminal", "subscriber station", "user terminal" or UT, "mobile terminal", "mobile station" or variations thereof.

[0032] A V-UE is a type of UE and may be any vehicle-mounted wireless communication device, such as a navigation system, an alarm system, a head-up display (HUD), an onboard computer, an in-vehicle infotainment system, an automated driving system (ADS), an advanced driver assistance system (ADAS), etc. Alternatively, a V-UE may be a portable wireless communication device (e.g., a cellular phone, a tablet computer, etc.) carried by a driver of a vehicle or an occupant in the vehicle. The term "V-UE" may refer to an in-vehicle wireless communication device or the vehicle itself, depending on the context. A P-UE is a type of UE and may be a portable wireless communication device carried by a pedestrian (i.e., a user who is not driving or riding a vehicle). In general, a UE may communicate with a core network via a RAN, and through the core network, the UE may be connected to an external network such as the Internet and to other UEs. Of course, other mechanisms for connecting to a core network and / or the Internet are also possible for a UE, such as through a wired access network, a wireless local area network (WLAN) network (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc.), etc.

[0033] 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 a UE, including supporting data, voice, and / or signaling connections for the supported UE. In some systems, a base station may provide only 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 a UL / reverse or DL / forward traffic channel.

[0034] 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 an adjacent base station whose reference radio frequency (RF) signal the UE is measuring. Because, as used herein, 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.

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

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

[0037] 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 102 may include eNBs and / or ng-eNBs (where the wireless communication system 100 corresponds to an LTE network), or gNBs (where the wireless communication system 100 corresponds to an NR network), or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0038] 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 through 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., the 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.

[0039] 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) over a backhaul link 134, which may be wired or wireless.

[0040] 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 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. Because a cell is supported by a specific base station, the term "cell" may refer to one or both of a logical communication entity and a base station supporting it, depending on the context. In some cases, the term “cell” may also refer to a geographic coverage area (eg, a sector) of a base station, as long as a carrier frequency can be detected and used for communications within some portion of the geographic coverage area 110 .

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

[0042] 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).

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

[0044] 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' using LTE / 5G in the unlicensed spectrum can improve the coverage of the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum can be referred to as NR-U. LTE in the unlicensed spectrum can be referred to as LTE-U, Licensed Assisted Access (LAA) or MulteFire.

[0045] The wireless communication system 100 may also include a mmW base station 180, which may operate in millimeter wave (mmW) frequencies and / or near mmW frequencies to communicate with UE 182. Extremely high frequency (EHF) is a part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz, with a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW may extend downward 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, and is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands have high path loss and relatively short distances. The mmW base station 180 and the UE 182 may utilize beamforming (transmitting and / or receiving) on ​​the mmW communication link 184 to compensate for extremely high path loss and short distances. 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.

[0046] 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 (called a "phased array" or "antenna array") that creates RF beams that can be "steered" to point in different directions without actually moving the antennas. 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.

[0047] The transmit beams can be quasi-co-located, which means that they appear to the receiver (e.g., UE) to have the same parameters, regardless of whether the network node's own transmit antenna is 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.

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

[0049] 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 based on 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.

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

[0051] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, 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 various documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0052] The 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, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR 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.

[0053] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used in this article, the term "below 6 GHz" and the like can be broadly referred to as 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 article, they can be broadly referred to as 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.

[0054] 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), which can be configured and used to provide additional radio resources once an RRC connection is established between the UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier 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 UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Because 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.

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

[0056] 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 ) can receive a signal 124 from one or more earth orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SV 112 can be part of a satellite positioning system that the UE 104 can use as an independent source of 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 SV 112, the transmitter may sometimes be located on a ground-based control station, base station 102, and / or other UE 104. The UE 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 SV 112.

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

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

[0059] Especially taking advantage of the increased data rates and reduced latency of NR, vehicle-to-everything (V2X) communication technology is being implemented to support intelligent transportation system (ITS) applications, such as wireless communications between vehicles (vehicle-to-vehicle (V2V)), between vehicles and roadside infrastructure (vehicle-to-infrastructure (V2I)), and between vehicles and pedestrians (vehicle-to-pedestrian (V2P)). The goal is to enable vehicles to sense the environment around them and communicate that information to other vehicles, infrastructure, and personal mobile devices. Such vehicle communications will enable safety, mobility, and environmental advances that current technology cannot provide. Once fully implemented, the technology is expected to reduce non-fault vehicle collisions by 80%.

[0060] Still reference Figure 1 , the wireless communication system 100 may include a plurality of V-UEs 160 that may communicate with a base station 102 over a communication link 120 using a Uu interface (i.e., an air interface between a UE and a base station). The V-UEs 160 may also communicate directly with each other over a wireless side link 162, with a roadside unit (RSU) 164 (roadside access point) over a wireless side link 166, or with a sidelink-capable UE 104 over a wireless side link 168 using a PC5 interface (i.e., an air interface between sidelink-capable UEs). A wireless side link (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, V2V communications, V2X communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more V-UEs in a group of V-UEs 160 utilizing sidelink communication may be within the geographic coverage area 110 of the base station 102. Other V-UEs 160 in such a group may be outside the geographic coverage area 110 of the base station 102, or otherwise unable to receive transmissions from the base station 102. In some cases, each group of V-UEs 160 communicating via sidelink communication may utilize a one-to-many (1:M) system, where each V-UE 160 transmits to each other V-UE 160 in the group. In some cases, the base station 102 facilitates the scheduling of resources for sidelink communication. In other cases, the sidelink communication is performed between the V-UEs 160 without involving the base station 102.

[0061] In one aspect, the sidelinks 162, 166, 168 may operate over a wireless communication medium of interest 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 (e.g., covering one or more channels across one or more carriers) associated with wireless communications between one or more transmitter / receiver pairs.

[0062] In one aspect, the sidelinks 162, 166, 168 may be cV2X links. The first generation of cV2X has been standardized in LTE, and the next generation is expected to be defined in NR. cV2X is a cellular technology that also enables device-to-device communications. In the United States and Europe, cV2X is expected to operate in the licensed ITS bands below 6 GHz. Other frequency bands may be allocated in other countries. Thus, as a specific example, the medium of interest utilized by the sidelinks 162, 166, 168 may correspond to at least a portion of the licensed ITS bands below 6 GHz. However, the present disclosure is not limited to this frequency band or cellular technology.

[0063] In one aspect, the side links 162, 166, 168 may be dedicated short-range communication (DSRC) links. DSRC is a unidirectional or bidirectional short-range to medium-range wireless communication protocol that uses the Wireless Access in Vehicular Environment (WAVE) protocol (also known as IEEE 802.11p) for V2V, V2I, and V2P communications. IEEE 802.11p is an approved modification to the IEEE 802.11 standard and operates in the licensed ITS band of 5.9 GHz (5.85 GHz-5.925 GHz) in the United States. In Europe, IEEE 802.11p operates in the ITS G5A band (5.875 GHz-5.905 MHz). Other bands may be allocated in other countries. The V2V communications briefly described above occur on a safety channel, which is typically a 10 MHz channel dedicated to safety purposes in the United States. The remainder of the DSRC band (total bandwidth is 75 MHz) is intended for other services of interest to drivers, such as road regulations, toll collection, parking automation, etc. Thus, as a specific example, the medium of interest utilized by the sidelinks 162, 166, 168 may correspond to at least a portion of the licensed ITS band at 5.9 GHz.

[0064] Alternatively, the medium of interest may correspond to at least a portion of an unlicensed frequency band shared among the various RATs. Although different licensed frequency bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) in the United States), these systems (particularly those employing small cell access points) have recently expanded operations into unlicensed frequency bands such as the Unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technologies (most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include different variations of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single carrier FDMA (SC-FDMA) systems, and the like.

[0065] Communication between V-UEs 160 is referred to as V2V communication, communication between V-UEs 160 and one or more RSUs 164 is referred to as V2I communication, and communication between V-UEs 160 and one or more UEs 104 (where these UEs 104 are P-UEs) is referred to as V2P communication. V2V communication between V-UEs 160 may include, for example, information about the position, speed, acceleration, heading, and other vehicle data of these V-UEs 160. V2I information received at V-UEs 160 from one or more RSUs 164 may include, for example, road rules, parking automation information, etc. V2P communication between V-UEs 160 and UEs 104 may include information about, for example, the position, speed, acceleration, and heading of the V-UEs 160 and the position, speed (for example, in the case where the UE 104 is carried by a user on a bicycle) and heading of the UEs 104.

[0066] Note that although Figure 1 Only two of the UEs are illustrated as V-UEs (V-UE 160), but any of the illustrated UEs (e.g., UE 104, 152, 182, 190) may be V-UEs. In addition, although only these V-UEs 160 and a single UE 104 have been illustrated as being connected via a side link, Figure 1Any of the illustrated UEs, whether V-UEs, P-UEs, etc., may be capable of sidelink communications. Furthermore, although only UE 182 is described as being capable of beamforming, any of the illustrated UEs (including V-UE 160) may be capable of beamforming. In the event that V-UE 160 is capable of beamforming, they may beamform toward each other (i.e., toward other V-UEs 160), toward RSU 164, toward other UEs (e.g., UE 104, 152, 182, 190), etc. Thus, in some cases, V-UE 160 may utilize beamforming on sidelinks 162, 166, and 168.

[0067] The wireless communication system 100 may also include one or more UEs (such as UE 190) indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) 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), Etc. As another example, D2D P2P links 192 and 194 may be side links, as described above with reference to side links 162 , 166 , and 168 .

[0068] Figure 2AAn 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. The user plane interface (NG-U) 213 and the 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 the 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).

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

[0070] 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 considered 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., 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 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 the case of authentication based on the UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), the AMF 264 retrieves security material from the AUSF. The functionality of the AMF 264 also includes security context management (SCM). The SCM receives keys from the SEAF, which it uses to derive access network specific keys. The functionality of the AMF 264 also includes location service management for regulatory services, for the transmission of location service messages between the UE 204 and the Location Management Function (LMF) 270 (which acts as a location server 230), for the transmission of location service messages between the NG-RAN 220 and the LMF 270, for the allocation of Evolved Packet System (EPS) bearer identifiers for interoperation with EPS, and UE 204 mobility event notifications. In addition, the AMF 264 also supports functionality for non-3GPP (Third Generation Partnership Project) access networks.

[0071] 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, service steering), lawful interception (user plane collection), service usage reporting, user plane quality of service (QoS) handling (e.g., uplink / downlink rate enforcement, reflective QoS marking in downlink), uplink service 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 can also support the delivery of location service messages between UE 204 and a location server (such as SLP 272) on the user plane.

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

[0073] 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).

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

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

[0076] The functionality of the gNB 222 is 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, etc. More specifically, the gNB-CU 226 typically hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that typically hosts the Radio Link Control (RLC) and Medium Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or 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.

[0077] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, 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) performing base station functionality) can be implemented in a clustered or decomposed architecture. For example, a base station (such as a B node (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as a clustered base station (also called an independent base station or a single-chip base station) or a decomposed base station.

[0078] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack 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 a CU, a DU, and a RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

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

[0080] Figure 2C2 is a diagram illustrating an example disaggregated base station architecture according to aspects of the present disclosure. The disaggregated base station 250 architecture 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 a 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 corresponding 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 corresponding 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.

[0081] 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, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via 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 on a wireless transmission medium.

[0082] 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 configured to communicate signals with other control functions hosted by CU 280. CU 280 may be configured to handle user plane functions (i.e., central unit-user plane (CU-UP)), control plane functions (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.

[0083] DU 285 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 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 functional splits such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 285 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 285 or with control functions hosted by CU 280.

[0084] The lower layer functions may be implemented by one or more RUs 287. In some deployments, the RU 287 controlled by the 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 functional splitting (such as lower layer functional splitting). 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 specific 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).

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

[0086] 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 communicate 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.

[0087] 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).

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

[0089] 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 the specified RAT, and conversely, receive and decode the 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 the signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding the signals 318 and 358, respectively.

[0090] 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 via at least one designated RAT (e.g., WiFi, LTE-D, The short-range wireless transceivers 320 and 360 are components (e.g., components for sending, components for receiving, components for measuring, components for tuning, components for preventing sending, etc.) for communicating with other network nodes (such as other UEs, access points, base stations, etc.) using a PC5, dedicated short-range communication (DSRC), wireless access for vehicle environments (WAVE), near field communication (NFC), 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 a specified RAT, and conversely, receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, the short-range wireless transceivers 320 and 360 include: one or more transmitters 324 and 364 for 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 a specific example, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Transceiver, and / or transceiver, NFC transceiver or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceiver.

[0091] 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 positions of UE 302 and base station 304, respectively.

[0092] 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 sending, 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.

[0093] 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 system (e.g., transmitters 314, 324, 354, 364) and a receiver circuit system (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., implementing the transmitter circuit system and the receiver circuit system in a single device), may include separate transmitter circuit systems and separate receiver circuit systems in some implementations, or may be implemented in other ways in other implementations. The transmitter circuit system and the receiver circuit system 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., receivers 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.

[0094] 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 transceiver or a 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.

[0095] 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 can 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 can include, for example, one or more general purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuit systems, or various combinations thereof.

[0096] 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, the positioning components 342, 388, and 398 can be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning components 342, 388, and 398 can be memory modules stored in the 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 Illustrating possible locations of the positioning component 342, the positioning component may be, for example, part of the one or more WWAN transceivers 310, the memory 340, the one or more processors 332, or any combination thereof, or may be a stand-alone component. Figure 3BIllustrated are possible locations for the location component 388, which may be, for example, part of the one or more WWAN transceivers 350, the memory 386, the one or more processors 384, or any combination thereof, or may be a stand-alone component. Figure 3C Illustrated are possible locations for the location component 398, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a stand-alone component.

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

[0098] In addition, the UE 302 includes a user interface 346 that provides means for providing indications to a user (e.g., audible and / or visual indications) and / or for receiving user input (e.g., when a 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.

[0099] 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 (encryption, decryption, 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.

[0100] 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 physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols may then be separated 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 state 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.

[0101] 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 on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point 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.

[0102] In the uplink, 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.

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

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

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

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

[0107] 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), or may omit short-range wireless transceiver 320 (e.g., only cellular, etc.), or may omit satellite signal receiver 330, or may omit sensor 344, etc. In another example, in Figure 3B In the case of a wireless network, a specific implementation of the base station 304 may omit the WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or may omit the short-range wireless transceiver 360 (e.g., cellular only, etc.), or may omit the satellite 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.

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

[0109] 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 3C The 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). In addition, 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," and the like. 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.).

[0110] 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 differently from a network operator or cellular network infrastructure (e.g., NG RAN 220 and / or 5GC 210 / 260). For example, the network entity 306 may be a component of a dedicated network that may be configured to communicate with the UE 302 via the base station 304 or independently of the base station 304 (e.g., via a non-cellular communication link such as WiFi).

[0111] NR supports several cellular network-based positioning techniques (also known as RAT-dependent positioning or Uu positioning), 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 an OTDOA or DL-TDOA positioning procedure, as illustrated in scenario 410, the UE measures the difference between the arrival times (ToA) of reference signals (e.g., positioning reference signals (PRS), which are broadband positioning signals defined in LTE and NR) 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 auxiliary 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.

[0112] For DL-AoD positioning, 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, as shown in scenario 420. The positioning entity can then estimate the position of the UE based on the determined angle and the known location of the transmitting base station.

[0113] 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 UL-TDOA 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 location of the base stations, and their known timing offsets, the positioning entity can use TDOA to estimate the position of the UE.

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

[0115] 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. The time difference is called the received-to-transmit (Rx-Tx) time difference. The Rx-Tx time difference measurement can be performed or adjusted to include only the time difference between the nearest time slot boundary of the received signal and the transmitted signal. The two entities 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, as shown in scenario 430, a first entity (e.g., a UE or a base station) performs an RTT positioning procedure with multiple second entities (e.g., multiple base stations or UEs) to enable the location of the first entity to be determined (e.g., using multilateration) based on the distance to the second entity and the known location of the second entity. RTT and multi-RTT methods may be combined with other positioning techniques (such as UL-AoA and DL-AoD) to improve location accuracy, as shown in scenario 440.

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

[0117] To assist the positioning operation, the 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 particular 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 using assistance data.

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

[0119] In addition to RAT-related positioning technologies, the UE may also support one or more RAT-independent positioning technologies, such as global navigation satellite system (GNSS) positioning, WLAN positioning (e.g., Wi-Fi positioning), Bluetooth positioning, ground beacon system (TBS) positioning, and sensor-based positioning (using, for example, motion sensors, pressure sensors, etc.). In some cases, the UE may also support hybrid positioning, which uses both RAT-related and RAT-independent technologies. For example, the UE may be able to use assisted GNSS (A-GNSS) and OTDOA hybrid positioning.

[0120] The position estimate may be referred to by other names, such as a position estimate, a position, a fix, a position fix, a 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, a postal address, or some other verbal description of the location. The position estimate may be further defined relative to some other known location or 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).

[0121] Figure 5An example Long Term Evolution (LTE) Positioning Protocol (LPP) procedure 500 is illustrated for performing positioning operations between a UE 504 and a location server (illustrated as a Location Management Function (LMF) 570). Figure 5 As illustrated, positioning of the UE 504 (via one or more RAT-dependent or RAT-independent technologies) is supported via the exchange of LPP messages between the UE 504 and the LMF 570. The LPP messages may be exchanged between the UE 504 and the LMF 570 via the serving base station of the UE 504 (illustrated as the serving gNB 502) and the core network (not shown). The LPP procedure 500 may be used to locate the UE 504 in order to support various location-related services, such as for the UE 504 (or for a user of the UE 504), or for routing, or for providing an accurate location to a public safety answering point (PSAP) in association with an emergency call from the UE 504 to the PSAP, or for navigation for some other reason. The LPP procedure 500 may also be referred to as a positioning session, and there may be multiple positioning sessions for different types of positioning methods (e.g., downlink time difference of arrival (DL-TDOA), round trip time (RTT), enhanced cell identification (E-CID), etc.).

[0122] Initially, at stage 510, the UE 504 may receive a request for its positioning capabilities (e.g., an LPP Request Capabilities message) from the LMF 570. At stage 520, the UE 504 provides its positioning capabilities with respect to the LPP protocol to the LMF 570 by transmitting an LPP Provide Capabilities message to the LMF 570 indicating that the UE 504 uses the positioning methods supported by the LPP and the characteristics of these positioning methods. In some aspects, the capabilities indicated in the LPP Provide Capabilities message may indicate the types of positioning supported by the UE 504 (e.g., DL-TDOA, RTT, E-CID, etc.) and may indicate the ability of the UE 504 to support those positioning types.

[0123] Upon receiving the LPP Provide Capability message, at stage 520, the LMF 570 determines a particular type of positioning method to be used (e.g., DL-TDOA, RTT, E-CID, etc.) based on the indicated positioning types supported by the UE 504, and determines a set of one or more Transmit Reception Points (TRPs) from which the UE 504 will measure downlink positioning reference signals or to which the UE 504 will send uplink positioning reference signals. At stage 530, the LMF 570 transmits an LPP Provide Assistance Data message to the UE 504 identifying the set of TRPs.

[0124] In some implementations, in response to an LPP request assistance data message ( Figure 5(not shown), the LPP provide assistance data message at stage 530 may be transmitted by the LMF 570 to the UE 504. The LPP request assistance data message may include an identifier of the serving TRP of the UE 504 and a request for PRS configuration of a neighboring TRP.

[0125] At stage 540, the LMF 570 transmits a request for location information to the UE 504. The request may be an LPP Request Location Information message. The message typically includes information elements defining the type of location information, the expected accuracy of the location estimate, and the response time (i.e., the expected latency). Note that a low latency requirement allows for a longer response time, while a high latency requirement requires a shorter response time. However, a long response time is referred to as high latency, and a short response time is referred to as low latency.

[0126] Note that in some implementations, the LPP Provide Assistance Data message transmitted at stage 530 may be transmitted after the LPP Request Location Information at stage 540, for example, if the UE 504 transmits a request for assistance data to the LMF 570 after receiving the request for location information at stage 540 (e.g., in the LPP Request Assistance Data message, Figure 5 This is the case (not shown).

[0127] At stage 550, the UE 504 utilizes the assistance information received at stage 530 and any additional data received at stage 540 (e.g., desired position accuracy or maximum response time) to perform positioning operations (e.g., measurement of DL-PRS, transmission of UL-PRS, etc.) for the selected positioning method.

[0128] At stage 560, UE 504 may transmit an LPP Provide Location Information message to LMF 570 that conveys the results of any measurements (e.g., time of arrival (ToA), reference signal time difference (RSTD), received to transmitted (Rx-Tx), etc.) obtained at stage 550 and before or at the expiration of any maximum response time (e.g., the maximum response time provided by LMF 570 at stage 540). The LPP Provide Location Information message at stage 560 may also include one or more times at which the positioning measurements were obtained and an identification of the TRP from which the positioning measurements were obtained. Note that the time between the request for location information at 540 and the response at 560 is the "response time" and indicates the latency of the positioning session.

[0129] LMF 570 uses an appropriate positioning technique (eg, DL-TDOA, RTT, E-CID, etc.) to compute an estimated location of UE 504 based at least in part on the measurements received in the LPP Provide Location Information message at stage 560 .

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

[0131] Figure 6B Additional scenarios of interest for sidelink-only or joint Uu and sidelink positioning in accordance with various aspects of the present disclosure are illustrated. In scenario 650, UEs used for public safety (e.g., used by police, firefighters, etc.) may perform peer-to-peer (P2P) positioning and ranging for public safety and other purposes. For example, in scenario 650, public safety UEs may be outside the coverage of the network and use sidelink positioning techniques to determine the position or relative distance and relative positioning between public safety UEs. Similarly, scenario 660 shows multiple UEs that are out of coverage and use sidelink positioning techniques (such as SL-RTT) to determine the position or relative distance and relative positioning.

[0132] Fig. 6A and Figure 6B The various sidelink positioning techniques illustrated in the figure can utilize sidelink ranging techniques. Sidelink-based ranging enables the determination of relative distances between UEs and optionally their absolute positions, where the absolute position of at least one of the involved UEs is known. This technique is valuable in situations where GNSS positioning is degraded or unavailable (e.g., tunnels, urban canyons, etc.), and can also enhance ranging and positioning accuracy when GNSS is available. Sidelink-based ranging can be implemented using a three-way handshake for session establishment, followed by the exchange of PRSs, and finally messaging based on PRS transmission and reception from peer UEs to exchange measurements.

[0133] Sidelink ranging is based on calculating the inter-UE round trip time (RTT) measurement, as determined from the transmission and reception times of the sidelink PRS (SL-PRS). Each UE reports the RTT measurement to all other participating UEs along with its location (if known). For UEs whose locations are not known at all or not known accurately, the RTT procedure produces an inter-UE distance between the involved UEs. For UEs whose locations are known accurately, the distance produces an absolute position. UE participation, PRS transmission, and subsequent RTT calculations are coordinated by an initial three-way messaging handshake (PRS request, PRS response, and PRS confirmation) and a message exchange after PRS transmission (post-PRS message) for sharing measurements after receiving the PRS of the peer UE.

[0134] Figure 7 An example sidelink ranging and positioning procedure 700 according to various aspects of the present disclosure is illustrated. The sidelink ranging and positioning procedure 700 may also be referred to as a sidelink RTT positioning procedure. Sidelink ranging is based on calculating inter-UE RTT measurements, as determined from the transmission and reception times of PRS (a wideband reference signal defined in LTE and NR for positioning). Each UE reports the RTT measurement to all other participating UEs along with its location (if known). For UEs whose locations are not known at all or not known accurately, the RTT procedure produces an inter-UE distance between the involved UEs. For UEs whose locations are known accurately, the ranging produces an absolute location. UE participation, PRS transmission, and subsequent RTT calculations are coordinated by an initial three-way messaging handshake (PRS request, PRS response, and PRS confirmation) and a message exchange after PRS transmission (post-PRS message) for sharing measurements after receiving the PRS of a peer UE.

[0135] The sidelink ranging and positioning procedure 700 (or session) begins at stage 705 with the broadcast of capability information by the peer UEs involved. Figure 7 As shown, one of the peer UEs, UE 204-1 (e.g., any of the UEs with sidelink capabilities described herein) can serve as an anchor node for the sidelink ranging and positioning procedure 700, which means that the position of the UE is known or the variance of the position of the UE is lower than the typical error estimate for the UE position. For example, the anchor node can be an RSU or a dedicated anchor point, similar to a terrestrial beacon system (TBS), a transmission point (TP), or a reception point (RP).

[0136] The anchor UE 204-1 includes in its capabilities message an indication that it is capable of being an anchor node for the sidelink ranging and positioning procedure 700. The capabilities message may also include the location of the anchor UE 204-1, or the location may be provided later. Another UE, UE 204-2 (e.g., any other UE in the UE with sidelink capabilities described herein) is a target UE, which means that the location of the UE is unknown or inaccurate and the UE is attempting to be located. Based on the capability information received from the anchor UE 204-1 indicating that the anchor UE 204-1 is an anchor node, the target UE 204-2 knows that it will be able to determine its location based on performing the sidelink ranging and positioning procedure 700 with the anchor UE 204-1.

[0137] After the initial capability exchange, the involved UEs 204 perform a three-way messaging handshake. At stage 710, the anchor UE 204-1 sends a PRS request (labeled "PRSrequest") to the target UE 204-2. At stage 715, the target UE 204-2 sends a PRS response (labeled "PRSresponse") to the anchor UE 204-1. At stage 720, the anchor UE 204-1 sends a PRS acknowledgement to the target UE 204-2. At this point, the three-way messaging handshake is complete. Note that although Figure 7 It is illustrated that the anchor UE 204-1 initiates the three-way message handshake, but it may be initiated by the target UE 204-2 instead.

[0138] At stages 725 and 730, the involved peer UEs 204 transmit PRS to each other. The resources on which the PRS are transmitted may be configured / allocated by the network (e.g., a serving base station of one of the UEs 204), or negotiated by the UEs 204 during a three-way messaging handshake. The anchor UE 204-1 measures the transmit-to-receive (Tx-Rx) time difference between the transmit time of the PRS at stage 725 and the receive time of the PRS at stage 730. The target UE 204-2 measures the receive-to-receive (Rx-Tx) time difference between the receive time of the PRS at stage 725 and the transmit time of the PRS at stage 730. Note that although Figure 7 It is illustrated that the anchor UE 204-1 transmits the PRS first, but the target UE 204-2 may transmit the PRS first instead.

[0139] At stages 735 and 740, the peer UEs 204 exchange their respective time difference measurements in a post-PRS message (labeled "postPRS"). If the anchor UE 204-1 has not yet provided its position to the target UE 204-2, it does so at this time. Each UE 204 is then able to determine the RTT between each UE 204 based on the Tx-Rx and Rx-Tx time difference measurements (specifically, the difference between the Tx-Rx and Rx-Tx time difference measurements). Based on the RTT measurements and the speed of light, each UE 204 can then estimate the distance (or range) between the two UEs 204 (specifically, the RTT measurement multiplied by half the speed of light). Since the target UE 204-2 also has the absolute position (e.g., geographic coordinates) of the anchor UE 204-1, the target UE 204-2 can use this position and the distance to the anchor UE 204-1 to determine its own absolute position.

[0140] Note that although Figure 7 Two UEs 204 are illustrated, but the UE may perform or attempt to perform the sidelink ranging and positioning procedure 700 with multiple UEs, such as Fig. 6A and Figure 6B As illustrated in various scenarios.

[0141] With further reference to RAT-related positioning, within the positioning frequency layer (side link or downlink) where the PRS is sent, it is usually the case that one of the RAT-related methods is selected. If the TRPs are synchronized with each other, the TDOA method is usually used. However, if the TRPs are not synchronized, the RTT-based method is usually used. Whether the TRPs are synchronized with each other will depend on the deployment.

[0142] With reference to synchronization relative to sidelink based positioning, anchor nodes can be synchronous or asynchronous. When anchor nodes are synchronized, synchronization can be maintained by GPS based techniques or by the system operator. Asynchronous is the default scenario where no synchronization procedures are performed between nodes.

[0143] Knowing the synchronization status of the anchor node allows the target UE to use appropriate and efficient positioning techniques for sidelink-based positioning. For example, if certain anchor nodes are synchronized with each other, the target UE can use these nodes to perform TDOA-based positioning techniques. However, if the anchor node is not synchronized with any other node, the target UE cannot use TDOA-based positioning using the anchor node, but can use RTT positioning procedures using the node.

[0144] Figure 8 800 is a diagram illustrating an example of sidelink-based positioning using different sets of synchronous and asynchronous anchor nodes in accordance with aspects of the present disclosure. Figure 8In the example of , the target UE can measure the sidelink PRS from the six anchor nodes labeled "anchor node 1" to "anchor node 6". Regarding their synchronization status, anchor nodes 1, 5 and 6 are synchronized with each other, anchor nodes 3 and 4 are synchronized with each other, and anchor node 2 is not synchronized with any other anchor node. Since anchor nodes 1, 5 and 7 are synchronized with each other, the target UE can use these anchor nodes to perform a TDOA-based positioning procedure (using one of these anchor nodes as a reference node and using the other anchor nodes as non-reference nodes). Similarly, since anchor nodes 3 and 4 are synchronized with each other, the target UE can also use these anchor nodes to perform a TDOA-based positioning procedure (also using one of these anchor nodes as a reference node and using the other anchor node as a non-reference node). However, since anchor node 2 is not synchronized with any other anchor node, the target UE uses anchor node 2 to perform an RTT-based positioning procedure. It should be noted that different TDOA and RTT positioning procedures can be performed in the same or different positioning sessions.

[0145] Currently, the target UE may not know the synchronization status of the anchor node. Therefore, the present disclosure provides a technique for providing synchronization information to the target UE to assist the target UE in determining a positioning technique for sidelink-based positioning.

[0146] As a first technique, the network (e.g., LMF 270, base station) may provide synchronization assistance data indicating the synchronization status of different anchor nodes to the target UE. The synchronization information may be provided in different formats. As a first format option, the assistance data may include a grouping (e.g., a list) of synchronization nodes. For example, referring to Figure 8 , the assistance data may include groups of {anchor node 1, anchor node 5, anchor node 6} and {anchor node 3, anchor node 4}. As a second option, the assistance data may include a synchronization indicator (or identifier) ​​for each identified anchor node, which is called a "sync id". Anchor nodes with the same synchronization indicator will synchronize with each other. For example, refer to Figure 8 , the auxiliary data may be {anchor node 1, synchronization id=1}, {anchor node 2, synchronization id=0}, {anchor node 3, synchronization id=2}, {anchor node 4, synchronization id=2}, {anchor node 5, synchronization id=1}, {anchor node 6, synchronization id=1}. It should be understood that the synchronization indicators "0", "1" and "2" are only examples.

[0147] The network may send the synchronization assistance data to the target UE in various ways. As a first option, the assistance data may be broadcast as part of an existing positioning system information block (Pos-SIB) used to broadcast other assistance data. As a second option, the assistance data may be broadcast as part of a new Pos-SIB dedicated to delivering synchronization assistance data. As a third option, the assistance data may be unicast to the UE or multicast to a group of UEs (e.g. associated with the same group identifier).

[0148] As a fourth option, the assistance data may be provided to a specific UE as part of an on-demand SIB (i.e., a SIB that the target UE has requested). This situation corresponds to a scenario where the target UE is performing sidelink positioning and has detected one or more anchor nodes within communication range. The UE may request synchronization assistance data from the network and may optionally identify or otherwise indicate an anchor node of interest (e.g., an anchor node that the UE has discovered and is able to perform a positioning procedure with). The network may respond with the synchronization status of the requested anchor node and optionally other anchor nodes that may be within the communication range of the UE (e.g., anchor nodes in the same or adjacent tracking area or registration area as the target UE).

[0149] For Uu-based positioning, the location server (e.g., LMF 270) may employ different positioning technologies within the same positioning session, depending on the synchronization status of different TRPs. The location server may obtain synchronization information of the TRP from one or more gNBs that control the TRP (e.g., via New Radio (NR) Positioning Protocol Type A (NRPPa) signaling). The location server then determines the different positioning technologies that can be used for the UE positioning session based on the synchronization information and instructs the UE to perform positioning measurements accordingly.

[0150] Fig. 9 900 is a diagram illustrating an example of Uu-based positioning using different sets of synchronous and asynchronous TRPs in accordance with aspects of the present disclosure. Fig. 9In the example of , the target UE can measure DL-PRS from six TRPs labeled "TRP 1" to "TRP 6". Regarding their synchronization status, TRP 1, TRP 5 and TRP 6 are synchronized with each other, TRP 3 and TRP 4 are synchronized with each other, and TRP 2 is not synchronized with any other TRP. Since TRP 1, TRP 5 and TRP 7 are synchronized with each other, the target UE can use these TRPs to perform TDOA-based positioning procedures (using one of these TRPs as a reference node and using the other TRPs as non-reference nodes). Similarly, since TRP 3 and TRP 4 are synchronized with each other, the target UE can also use these TRPs to perform TDOA-based positioning procedures (also using one of these TRPs as a reference node and using another TRP as a non-reference node). However, since TRP 2 is not synchronized with any other TRP, the target UE uses TRP 2 to perform RTT-based positioning procedures. It should be noted that different TDOA and RTT positioning procedures can be performed in the same or different positioning sessions.

[0151] Different synchronization conditions (i.e., synchronous or asynchronous) between TRPs may be based on specific deployment states. For example, in small deployments, it is expected that synchronization across different gNBs is easier to maintain, while in large deployments, synchronization may be more difficult to maintain. In this case, the network may maintain synchronization information per certain area unit (e.g., tracking area, registration area, etc.).

[0152] Due to various reasons (such as hardware failure, synchronization process failure, etc.), synchronization at some TRPs may be lost (e.g., temporarily lost). However, loss of synchronization at a certain TRP does not mean that this TRP cannot be used for positioning, even if all other TRPs of the same gNB are synchronized. Instead, asynchronous TRPs may be used in RTT-based procedures with the UE and thus may still contribute to the final positioning estimate (e.g., Fig. 9 TRP 2).

[0153] Note that a UE may perform different positioning procedures using different groups of UEs or TRPs (grouped based on synchronization status) during the same or different positioning sessions.

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

[0155] At 1010, the UE receives synchronization assistance data for a positioning session, the synchronization assistance data indicating at least a synchronization state of each of a plurality of anchor nodes relative to other anchor nodes of the plurality of anchor nodes. In one aspect, operation 1010 may be performed by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, 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.

[0156] At 1020, the UE performs at least one positioning procedure with at least one of the plurality of anchor nodes based on a synchronization state of the at least one anchor node during the positioning session. In one aspect, operation 1020 may be performed by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, 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.

[0157] It should be appreciated that the technical advantage of method 1000 is that it enables the UE to determine which anchor nodes among the plurality of anchor nodes to utilize to perform which type of positioning procedure, thereby improving positioning efficiency and latency. For example, if it is known that all nodes are synchronized, UL-TDOA can be used, where only the UE transmits and can only transmit one SRS, as opposed to the case where the nodes are asynchronous and the UE utilizes all of these nodes to perform RTT procedures. In the latter case, each node (e.g., TRP) must transmit a PRS, resulting in more energy usage and more latency.

[0158] Fig.11 An example communication method 1100 is illustrated in accordance with aspects of the present disclosure. In one aspect, the method 1100 may be performed by a location server (eg, LMF 270).

[0159] At 1110, the location server obtains a synchronization state of each TRP in the plurality of TRPs relative to other TRPs in the plurality of TRPs. In one aspect, operation 1110 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which may be considered as means for performing the operation.

[0160] At 1120, the location server sends synchronization assistance data for the positioning session to the UE (e.g., any UE described herein), the synchronization assistance data indicating at least a synchronization state of each TRP in the plurality of TRPs. In one aspect, operation 1120 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which may be considered as means for performing the operation.

[0161] It should be appreciated that the technical advantage of method 1100 is that it enables the UE to determine which TRPs among a plurality of TRPs to utilize to perform which type of positioning procedure, thereby improving positioning efficiency and latency. With knowledge of the synchronization state, the minimum number of transmissions may be requested / used to obtain a positioning estimate for the UE, thereby reducing latency and minimizing air transmissions and power usage.

[0162] In the above specific embodiments, 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 can refer to a specific combination of one clause with other clauses in a 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 explicitly expressed or can be easily inferred that a specific combination is not intended to be used (for example, contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). In addition, it is also expected that various aspects of the clause can be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

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

[0164] Clause 1. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving synchronization assistance data for a positioning session, the synchronization assistance data at least indicating a synchronization state of each of a plurality of anchor nodes relative to other anchor nodes of the plurality of anchor nodes; and during the positioning session, based on the synchronization state of at least one anchor node of the plurality of anchor nodes, performing at least one positioning procedure using the at least one anchor node.

[0165] Clause 2. The method of clause 1, wherein: the synchronization assistance data comprises one or more groups of the plurality of anchor nodes, and the anchor nodes within each of the one or more groups are expected to be synchronized with each other.

[0166] Clause 3. A method according to any one of clauses 1 to 2, wherein: the synchronization assistance data comprises a synchronization indicator for each of the plurality of anchor nodes, and anchor nodes of the plurality of anchor nodes having the same synchronization indicator are expected to be synchronized with each other.

[0167] Clause 4. A method as described in any of clauses 1 to 3, wherein the synchronization assistance data is received from a base station in one or more Positioning System Information Blocks (Pos-SIBs) carrying additional assistance data for the positioning session.

[0168] Clause 5. A method as described in any of clauses 1 to 4, wherein the synchronization assistance data is received from a base station in one or more Pos-SIBs dedicated to sending the synchronization assistance data.

[0169] Clause 6. A method as described in any of clauses 1 to 5, wherein the synchronization assistance data is received from a base station in one or more on-demand SIBs.

[0170] Clause 7. A method as described in any of clauses 1 to 6, wherein the synchronization assistance data is received via unicast or multicast signaling.

[0171] Clause 8. A method as described in any of clauses 1 to 7, wherein the synchronization assistance data is received from a location server in one or more Long Term Evolution (LTE) Positioning Protocol (LPP) messages.

[0172] Clause 9. The method of any one of clauses 1 to 8, further comprising: detecting one or more anchor nodes of the plurality of anchor nodes; and sending a request for the synchronization assistance data based on the detection of the one or more anchor nodes.

[0173] Clause 10. The method of Clause 9, wherein the request identifies the one or more anchor nodes.

[0174] Clause 11. A method as described in any of clauses 9 to 10, wherein anchor nodes other than the one or more anchor nodes of the plurality of anchor nodes are included in the synchronization assistance data based on the anchor nodes being expected to be measurable by the UE.

[0175] Clause 12. A method as described in any of clauses 1 to 11, wherein the plurality of anchor nodes comprises a plurality of sidelink UEs.

[0176] Clause 13. The method of any one of clauses 1 to 12, wherein the plurality of anchor nodes comprises a plurality of transmit reception points (TRPs).

[0177] Clause 14. A method according to any one of clauses 1 to 13, wherein: the at least one anchor node includes multiple anchor nodes, and the at least one positioning procedure includes a positioning procedure based on arrival time difference (TDOA), a multiple round trip time (multi-RTT) positioning procedure, or both.

[0178] Clause 15. The method of any of clauses 1 to 14, wherein: the at least one anchor node comprises a single anchor node, and the at least one positioning procedure comprises a round trip time (RTT) positioning procedure.

[0179] Clause 16. The method according to any one of clauses 1 to 15, wherein: the at least one anchor node comprises at least two groups of synchronization anchor nodes, and the at least one positioning procedure comprises a positioning procedure performed using each of the at least two groups of synchronization anchor nodes.

[0180] Clause 17. A communication method performed by a location server, the method comprising: obtaining a synchronization status of each of a plurality of transmit receive points (TRPs) relative to other TRPs in the plurality of TRPs; and sending synchronization assistance data for a positioning session to a user equipment (UE), the synchronization assistance data at least indicating the synchronization status of each of the plurality of TRPs.

[0181] Clause 18. The method of clause 17, wherein the synchronization state of the TRP is obtained from a base station controlling each of the plurality of TRPs.

[0182] Clause 19. A method according to any one of clauses 17 to 18, wherein: the synchronization assistance data includes one or more groups of the multiple TRPs, and the TRPs within each of the one or more groups are expected to be synchronized with each other.

[0183] Clause 20. A method according to any one of clauses 17 to 19, wherein: the synchronization assistance data includes a synchronization indicator for each TRP in the plurality of TRPs, and TRPs in the plurality of TRPs having the same synchronization indicator are expected to be synchronized with each other.

[0184] Clause 21. A method according to any one of clauses 17 to 20, the method further comprising: sending auxiliary data for the positioning session to the UE, wherein the auxiliary data indicates one or more types of positioning procedures performed by the UE using one or more groups of the multiple TRPs, wherein the one or more groups of the multiple TRPs are based on the synchronization state of each TRP in the multiple TRPs, and wherein the TRPs in the multiple TRPs within each group of the one or more groups are expected to be synchronized with each other.

[0185] Clause 22. A method according to clause 21, wherein the one or more types of positioning procedures include a time difference of arrival (TDOA) based positioning procedure, a multiple round trip time (multi-RTT) positioning procedure, a round trip time (RTT) positioning procedure, or any combination thereof.

[0186] Clause 23. A method according to any one of clauses 21 to 22, wherein the auxiliary data configures the UE to perform a different positioning procedure using each group of the multiple TRPs.

[0187] Clause 24. A method according to any one of clauses 21 to 23, wherein the assistance data comprises the synchronization assistance data.

[0188] Clause 25. The method of any one of clauses 17 to 24, further comprising: receiving a request for the synchronization assistance data.

[0189] Clause 26. A method according to clause 25, wherein the request identifies one or more TRPs among the multiple TRPs that can be detected by the UE.

[0190] Clause 27. A method according to any one of clauses 25 to 26, wherein TRPs of the plurality of TRPs other than the one or more TRPs are included in the synchronization assistance data based on the TRPs being expected to be measurable by the UE.

[0191] Clause 28. A method according to any one of clauses 17 to 27, wherein the synchronization state of each TRP in the plurality of TRPs is obtained via New Radio (NR) Positioning Protocol Type A (NRPPa) signaling.

[0192] Clause 29. A user equipment (UE), comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive synchronization assistance data for a positioning session via the at least one transceiver, the synchronization assistance data at least indicating a synchronization state of each of a plurality of anchor nodes relative to other anchor nodes of the plurality of anchor nodes; and during the positioning session, perform at least one positioning procedure using the at least one anchor node based on the synchronization state of at least one of the plurality of anchor nodes.

[0193] Clause 30. The UE of clause 29, wherein: the synchronization assistance data comprises one or more groups of the plurality of anchor nodes, and the anchor nodes within each group of the one or more groups are expected to be synchronized with each other.

[0194] Clause 31. A UE according to any of clauses 29 to 30, wherein: the synchronization assistance data comprises a synchronization indicator for each of the plurality of anchor nodes, and anchor nodes of the plurality of anchor nodes having the same synchronization indicator are expected to be synchronized with each other.

[0195] Clause 32. A UE as set forth in any of clauses 29 to 31, wherein the synchronization assistance data is received from a base station in one or more Positioning System Information Blocks (Pos-SIBs) carrying additional assistance data for the positioning session.

[0196] Clause 33. A UE as set out in any of clauses 29 to 32, wherein the synchronization assistance data is received from a base station in one or more Pos-SIBs dedicated to sending the synchronization assistance data.

[0197] Clause 34. A UE as set forth in any of clauses 29 to 33, wherein the synchronization assistance data is received from a base station in one or more on-demand SIBs.

[0198] Clause 35. A UE as set forth in any of clauses 29 to 34, wherein the synchronization assistance data is received via unicast or multicast signaling.

[0199] Clause 36. A UE as set forth in any of clauses 29 to 35, wherein the synchronization assistance data is received from a location server in one or more Long Term Evolution (LTE) Positioning Protocol (LPP) messages.

[0200] Clause 37. A UE according to any one of clauses 29 to 36, wherein the at least one processor is further configured to: detect one or more anchor nodes among the plurality of anchor nodes; and send a request for the synchronization assistance data via the at least one transceiver based on the detection of the one or more anchor nodes.

[0201] Clause 38. The UE of clause 37, wherein the request identifies the one or more anchor nodes.

[0202] Clause 39. A UE as described in any of clauses 37 to 38, wherein anchor nodes of the plurality of anchor nodes other than the one or more anchor nodes are included in the synchronization assistance data based on the anchor nodes being expected to be measurable by the UE.

[0203] Clause 40. A UE as set forth in any of clauses 29 to 39, wherein the plurality of anchor nodes comprises a plurality of sidelink UEs.

[0204] Clause 41. A UE as set forth in any of clauses 29 to 40, wherein the plurality of anchor nodes comprises a plurality of transmit reception points (TRPs).

[0205] Clause 42. A UE according to any one of clauses 29 to 41, wherein: the at least one anchor node includes multiple anchor nodes, and the at least one positioning procedure includes a time difference of arrival (TDOA) based positioning procedure, a multiple round trip time (multi-RTT) positioning procedure, or both.

[0206] Clause 43. A UE as set forth in any of clauses 29 to 42, wherein the at least one anchor node comprises a single anchor node and the at least one positioning procedure comprises a round trip time (RTT) positioning procedure.

[0207] Clause 44. A UE as described in any of clauses 29 to 43, wherein: the at least one anchor node comprises at least two groups of synchronization anchor nodes, and the at least one positioning procedure comprises a positioning procedure performed with each of the at least two groups of synchronization anchor nodes.

[0208] Clause 45. A location server, comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: obtain a synchronization state of each of a plurality of transmit receive points (TRPs) relative to other TRPs in the plurality of TRPs; and send synchronization assistance data for a positioning session to a user equipment (UE) via the at least one transceiver, the synchronization assistance data at least indicating the synchronization state of each of the plurality of TRPs.

[0209] Clause 46. A location server according to Clause 45, wherein the synchronization state of the TRP is obtained from a base station controlling each TRP in the plurality of TRPs.

[0210] Clause 47. A location server according to any one of clauses 45 to 46, wherein: the synchronization assistance data includes one or more groups of the plurality of TRPs, and the TRPs within each of the one or more groups are expected to be synchronized with each other.

[0211] Clause 48. A location server according to any one of clauses 45 to 47, wherein: the synchronization assistance data includes a synchronization indicator for each TRP in the plurality of TRPs, and TRPs in the plurality of TRPs having the same synchronization indicator are expected to be synchronized with each other.

[0212] Clause 49. A location server according to any one of clauses 45 to 48, wherein the at least one processor is further configured to: send auxiliary data for the positioning session to the UE via the at least one transceiver, wherein the auxiliary data indicates one or more types of positioning procedures performed by the UE using one or more groups of the multiple TRPs, wherein the one or more groups of the multiple TRPs are based on the synchronization state of each TRP in the multiple TRPs, and wherein the TRPs in the multiple TRPs within each of the one or more groups are expected to be synchronized with each other.

[0213] Clause 50. A location server according to Clause 49, wherein the one or more types of positioning procedures include a time difference of arrival (TDOA) based positioning procedure, a multiple round trip time (multi-RTT) positioning procedure, a round trip time (RTT) positioning procedure, or any combination thereof.

[0214] Clause 51. A location server according to any one of clauses 49 to 50, wherein the assistance data configures the UE to perform a different positioning procedure using each group of the multiple TRPs.

[0215] Clause 52. The location server of any one of clauses 49 to 51, wherein the assistance data comprises the synchronization assistance data.

[0216] Clause 53. The location server of any of clauses 45 to 52, wherein the at least one processor is further configured to: receive, via the at least one transceiver, a request for the synchronization assistance data.

[0217] Clause 54. A location server according to clause 53, wherein the request identifies one or more TRPs among the plurality of TRPs that can be detected by the UE.

[0218] Clause 55. A location server according to any one of clauses 53 to 54, wherein TRPs of the plurality of TRPs other than the one or more TRPs are included in the synchronization assistance data based on the TRPs being expected to be measurable by the UE.

[0219] Clause 56. A location server according to any one of clauses 45 to 55, wherein the synchronization state of each TRP in the plurality of TRPs is obtained via New Radio (NR) Positioning Protocol Type A (NRPPa) signaling.

[0220] Clause 57. A user equipment (UE), comprising: a component for receiving synchronization assistance data for a positioning session, the synchronization assistance data at least indicating a synchronization state of each of a plurality of anchor nodes relative to other anchor nodes of the plurality of anchor nodes; and a component for performing at least one positioning procedure using the at least one anchor node among the plurality of anchor nodes based on the synchronization state of the at least one anchor node during the positioning session.

[0221] Clause 58. The UE of clause 57, wherein: the synchronization assistance data comprises one or more groups of the plurality of anchor nodes, and the anchor nodes within each group of the one or more groups are expected to be synchronized with each other.

[0222] Clause 59. A UE according to any of clauses 57 to 58, wherein: the synchronization assistance data comprises a synchronization indicator for each of the plurality of anchor nodes, and anchor nodes of the plurality of anchor nodes having the same synchronization indicator are expected to be synchronized with each other.

[0223] Clause 60. A UE as set forth in any of clauses 57 to 59, wherein the synchronization assistance data is received from a base station in one or more Positioning System Information Blocks (Pos-SIBs) carrying additional assistance data for the positioning session.

[0224] Clause 61. A UE as set out in any of clauses 57 to 60, wherein the synchronization assistance data is received from a base station in one or more Pos-SIBs dedicated to sending the synchronization assistance data.

[0225] Clause 62. A UE as set forth in any of clauses 57 to 61, wherein the synchronization assistance data is received from a base station in one or more on-demand SIBs.

[0226] Clause 63. A UE as set forth in any of clauses 57 to 62, wherein the synchronization assistance data is received via unicast or multicast signaling.

[0227] Clause 64. A UE as set forth in any of clauses 57 to 63, wherein the synchronization assistance data is received from a location server in one or more Long Term Evolution (LTE) Positioning Protocol (LPP) messages.

[0228] Clause 65. A UE according to any of clauses 57 to 64, the UE further comprising: means for detecting one or more anchor nodes of the plurality of anchor nodes; and means for sending a request for the synchronization assistance data based on the detection of the one or more anchor nodes.

[0229] Clause 66. The UE of clause 65, wherein the request identifies the one or more anchor nodes.

[0230] Clause 67. A UE as set forth in any of clauses 65 to 66, wherein anchor nodes of the plurality of anchor nodes other than the one or more anchor nodes are included in the synchronization assistance data based on the anchor nodes being expected to be measurable by the UE.

[0231] Clause 68. A UE as set forth in any of clauses 57 to 67, wherein the plurality of anchor nodes comprises a plurality of sidelink UEs.

[0232] Clause 69. A UE as set forth in any of clauses 57 to 68, wherein the plurality of anchor nodes comprises a plurality of transmit reception points (TRPs).

[0233] Clause 70. A UE according to any one of clauses 57 to 69, wherein: the at least one anchor node comprises a plurality of anchor nodes, and the at least one positioning procedure comprises a time difference of arrival (TDOA) based positioning procedure, a multiple round trip time (multi-RTT) positioning procedure, or both.

[0234] Clause 71. A UE as set forth in any of clauses 57 to 70, wherein the at least one anchor node comprises a single anchor node and the at least one positioning procedure comprises a round trip time (RTT) positioning procedure.

[0235] Clause 72. A UE according to any of clauses 57 to 71, wherein: the at least one anchor node comprises at least two groups of synchronization anchor nodes, and the at least one positioning procedure comprises a positioning procedure performed using each of the at least two groups of synchronization anchor nodes.

[0236] Clause 73. A location server, comprising: a component for obtaining a synchronization status of each of a plurality of transmit receive points (TRPs) relative to other TRPs in the plurality of TRPs; and a component for sending synchronization assistance data for a positioning session to a user equipment (UE), the synchronization assistance data at least indicating the synchronization status of each of the plurality of TRPs.

[0237] Clause 74. A location server according to clause 73, wherein the synchronization state of the TRP is obtained from a base station controlling each TRP in the plurality of TRPs.

[0238] Clause 75. A location server according to any one of clauses 73 to 74, wherein: the synchronization assistance data includes one or more groups of the plurality of TRPs, and the TRPs within each of the one or more groups are expected to be synchronized with each other.

[0239] Clause 76. A location server according to any one of clauses 73 to 75, wherein: the synchronization assistance data includes a synchronization indicator for each TRP in the plurality of TRPs, and TRPs in the plurality of TRPs having the same synchronization indicator are expected to be synchronized with each other.

[0240] Clause 77. A location server according to any one of clauses 73 to 76, wherein the location server further includes: a component for sending auxiliary data for the positioning session to the UE, wherein the auxiliary data indicates one or more types of positioning procedures performed by the UE using one or more groups of the multiple TRPs, wherein the one or more groups of the multiple TRPs are based on the synchronization state of each TRP in the multiple TRPs, and wherein the TRPs in the multiple TRPs within each of the one or more groups are expected to be synchronized with each other.

[0241] Clause 78. A location server according to clause 77, wherein the one or more types of positioning procedures include a time difference of arrival (TDOA) based positioning procedure, a multiple round trip time (multi-RTT) positioning procedure, a round trip time (RTT) positioning procedure, or any combination thereof.

[0242] Clause 79. A location server according to any one of clauses 77 to 78, wherein the assistance data configures the UE to perform a different positioning procedure using each group of the multiple TRPs.

[0243] Clause 80. The location server of any one of clauses 77 to 79, wherein the assistance data comprises the synchronization assistance data.

[0244] Clause 81. The location server of any of clauses 73 to 80, further comprising means for receiving a request for the synchronization assistance data.

[0245] Clause 82. A location server according to clause 81, wherein the request identifies one or more TRPs among the plurality of TRPs that can be detected by the UE.

[0246] Clause 83. A location server according to any one of clauses 81 to 82, wherein TRPs of the plurality of TRPs other than the one or more TRPs are included in the synchronization assistance data based on the TRPs being expected to be measurable by the UE.

[0247] Clause 84. A location server according to any one of clauses 73 to 83, wherein the synchronization state of each TRP in the plurality of TRPs is obtained via New Radio (NR) Positioning Protocol Type A (NRPPa) signaling.

[0248] Clause 85. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), causes the UE to: receive synchronization assistance data for a positioning session, the synchronization assistance data at least indicating a synchronization state of each of a plurality of anchor nodes relative to other of the plurality of anchor nodes; and during the positioning session, perform at least one positioning procedure using the at least one anchor node based on the synchronization state of the at least one anchor node of the plurality of anchor nodes.

[0249] Clause 86. The non-transitory computer-readable medium of clause 85, wherein: the synchronization assistance data comprises one or more groups of the plurality of anchor nodes, and the anchor nodes within each of the one or more groups are expected to be synchronized with each other.

[0250] Clause 87. A non-transitory computer-readable medium according to any one of clauses 85 to 86, wherein: the synchronization assistance data includes a synchronization indicator for each of the plurality of anchor nodes, and anchor nodes in the plurality of anchor nodes having the same synchronization indicator are expected to be synchronized with each other.

[0251] Clause 88. A non-transitory computer-readable medium as described in any of clauses 85 to 87, wherein the synchronization assistance data is received from a base station in one or more positioning system information blocks (Pos-SIBs) carrying additional assistance data for the positioning session.

[0252] Clause 89. The non-transitory computer-readable medium of any of clauses 85 to 88, wherein the synchronization assistance data is received from a base station in one or more Pos-SIBs dedicated to sending the synchronization assistance data.

[0253] Clause 90. The non-transitory computer-readable medium of any of clauses 85 to 89, wherein the synchronization assistance data is received from a base station in one or more on-demand SIBs.

[0254] Clause 91. The non-transitory computer-readable medium of any one of clauses 85 to 90, wherein the synchronization assistance data is received via unicast or multicast signaling.

[0255] Clause 92. The non-transitory computer-readable medium of any one of clauses 85 to 91, wherein the synchronization assistance data is received from a location server in one or more Long Term Evolution (LTE) Positioning Protocol (LPP) messages.

[0256] Clause 93. A non-transitory computer-readable medium according to any one of clauses 85 to 92, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the UE, cause the UE to: detect one or more anchor nodes among the multiple anchor nodes; and send a request for the synchronization assistance data based on the detection of the one or more anchor nodes.

[0257] Clause 94. The non-transitory computer-readable medium of Clause 93, wherein the request identifies the one or more anchor nodes.

[0258] Clause 95. A non-transitory computer-readable medium as described in any of clauses 93 to 94, wherein anchor nodes of the plurality of anchor nodes other than the one or more anchor nodes are included in the synchronization assistance data based on the anchor nodes being expected to be measurable by the UE.

[0259] Clause 96. The non-transitory computer-readable medium of any of clauses 85 to 95, wherein the plurality of anchor nodes comprises a plurality of sidelink UEs.

[0260] Clause 97. The non-transitory computer-readable medium of any one of clauses 85 to 96, wherein the plurality of anchor nodes comprises a plurality of transmit-receive points (TRPs).

[0261] Clause 98. A non-transitory computer-readable medium as described in any one of clauses 85 to 97, wherein: the at least one anchor node includes multiple anchor nodes, and the at least one positioning procedure includes a time difference of arrival (TDOA) based positioning procedure, a multiple round trip time (multi-RTT) positioning procedure, or both.

[0262] Clause 99. The non-transitory computer-readable medium of any one of clauses 85 to 98, wherein: the at least one anchor node comprises a single anchor node, and the at least one positioning procedure comprises a round trip time (RTT) positioning procedure.

[0263] Clause 100. A non-transitory computer-readable medium according to any one of clauses 85 to 99, wherein: the at least one anchor node includes at least two groups of synchronization anchor nodes, and the at least one positioning procedure includes a positioning procedure performed using each group of synchronization anchor nodes in the at least two groups of synchronization anchor nodes.

[0264] Clause 101. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a location server, cause the location server to: obtain a synchronization state of each of a plurality of transmit receive points (TRPs) relative to other TRPs in the plurality of TRPs; and send synchronization assistance data for a positioning session to a user equipment (UE), the synchronization assistance data at least indicating the synchronization state of each of the plurality of TRPs.

[0265] Clause 102. The non-transitory computer-readable medium of clause 101, wherein the synchronization state of the TRP is obtained from a base station controlling each of the plurality of TRPs.

[0266] Clause 103. A non-transitory computer-readable medium as described in any of clauses 101 to 102, wherein: the synchronization assistance data includes one or more groups of the multiple TRPs, and the TRPs within each of the one or more groups are expected to be synchronized with each other.

[0267] Clause 104. A non-transitory computer-readable medium as described in any one of clauses 101 to 103, wherein: the synchronization assistance data includes a synchronization indicator for each TRP in the plurality of TRPs, and TRPs in the plurality of TRPs having the same synchronization indicator are expected to be synchronized with each other.

[0268] Clause 105. A non-transitory computer-readable medium according to any one of clauses 101 to 104, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the location server, cause the location server to: send auxiliary data for the positioning session to the UE, wherein the auxiliary data indicates one or more types of positioning procedures performed by the UE using one or more groups of the multiple TRPs, wherein the one or more groups of the multiple TRPs are based on the synchronization state of each TRP in the multiple TRPs, and wherein the TRPs in the multiple TRPs within each of the one or more groups are expected to be synchronized with each other.

[0269] Clause 106. A non-transitory computer-readable medium as described in clause 105, wherein the one or more types of positioning procedures include a time difference of arrival (TDOA) based positioning procedure, a multiple round trip time (multi-RTT) positioning procedure, a round trip time (RTT) positioning procedure, or any combination thereof.

[0270] Clause 107. A non-transitory computer-readable medium as described in any of clauses 105 to 106, wherein the assistance data configures the UE to perform a different positioning procedure with each grouping of the multiple TRPs.

[0271] Clause 108. The non-transitory computer-readable medium of any one of clauses 105 to 107, wherein the auxiliary data comprises the synchronization auxiliary data.

[0272] Clause 109. The non-transitory computer-readable medium of any one of clauses 101 to 108, further comprising computer-executable instructions which, when executed by the location server, cause the location server to: receive a request for the synchronization assistance data.

[0273] Clause 110. A non-transitory computer-readable medium as described in clause 109, wherein the request identifies one or more TRPs of the plurality of TRPs that are detectable by the UE.

[0274] Clause 111. A non-transitory computer-readable medium as described in any of clauses 109 to 110, wherein TRPs of the plurality of TRPs other than the one or more TRPs are included in the synchronization assistance data based on the TRPs being expected to be measurable by the UE.

[0275] Clause 112. A non-transitory computer-readable medium as described in any of clauses 101 to 111, wherein the synchronization state of each TRP in the plurality of TRPs is obtained via New Radio (NR) Positioning Protocol Type A (NRPPa) signaling.

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

[0277] 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 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, blocks, modules, circuits and steps have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on specific applications 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 a departure from the scope of the present disclosure.

[0278] The various illustrative logical blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in 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.

[0279] 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 a 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.

[0280] In one or more example aspects, the function can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the function can be stored on a computer-readable medium or sent by 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 a computer program from one place to another. Storage media can be any available medium that can be accessed by a computer. As an example and not by way of limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store desired program codes 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, a server, or other remote sources 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.

[0281] 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. In addition, 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, although the elements of the present disclosure may be described or claimed in the singular, plural forms may also be considered unless explicitly stated to be limited to the singular.

Claims

1. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving synchronization assistance data for a positioning session, the synchronization assistance data indicating at least a synchronization state of each anchor node of a plurality of anchor nodes relative to other anchor nodes of the plurality of anchor nodes; as well as During the positioning session, at least one positioning procedure is performed with at least one anchor node among the plurality of anchor nodes based on the synchronization state of the at least one anchor node.

2. The method according to claim 1, wherein: The synchronization assistance data includes one or more packets of the plurality of anchor nodes, and The anchor nodes within each of the one or more groups are expected to be synchronized with each other.

3. The method according to claim 1, wherein: The synchronization assistance data includes a synchronization indicator for each of the plurality of anchor nodes, and The anchor nodes having the same synchronization indicator among the plurality of anchor nodes are expected to be synchronized with each other.

4. The method of claim 1, wherein the synchronization assistance data is received from a base station in one or more Positioning System Information Blocks (Pos-SIBs) carrying additional assistance data for the positioning session.

5. The method of claim 1, wherein the synchronization assistance data is received from a base station in one or more Pos-SIBs dedicated to transmitting the synchronization assistance data.

6. The method of claim 1, wherein the synchronization assistance data is received from a base station in one or more on-demand SIBs. The method of claim 1 , wherein the synchronization assistance data is received via unicast or multicast signaling.

8. The method of claim 1, wherein the synchronization assistance data is received from a location server in one or more Long Term Evolution (LTE) Positioning Protocol (LPP) messages.

9. The method according to claim 1, further comprising: detecting one or more anchor nodes among the plurality of anchor nodes; as well as A request for the synchronization assistance data is sent based on the detection of the one or more anchor nodes.

10. The method of claim 9, wherein the request identifies the one or more anchor nodes.

11. The method of claim 9, wherein anchor nodes other than the one or more anchor nodes of the plurality of anchor nodes are included in the synchronization assistance data based on the anchor nodes being expected to be measurable by the UE.

12. The method of claim 1, wherein the plurality of anchor nodes comprises a plurality of sidelink UEs.

13. The method of claim 1, wherein the plurality of anchor nodes comprises a plurality of Transmission Reception Points (TRPs).

14. The method of claim 1, wherein: The at least one anchor node includes a plurality of anchor nodes, and The at least one positioning procedure includes a time difference of arrival (TDOA) based positioning procedure, a multiple round trip time (multi-RTT) positioning procedure, or both.

15. The method of claim 1, wherein: The at least one anchor node comprises a single anchor node, and The at least one positioning procedure comprises a round trip time (RTT) positioning procedure.

16. The method of claim 1, wherein: The at least one anchor node includes at least two groups of synchronization anchor nodes, and The at least one positioning procedure includes a positioning procedure performed using each of the at least two groups of synchronization anchor nodes.

17. A communication method performed by a location server, the method comprising: Obtaining a synchronization state of each of a plurality of transmit receive points (TRPs) relative to other TRPs of the plurality of TRPs; as well as Synchronization assistance data for a positioning session is sent to a user equipment (UE), and the synchronization assistance data at least indicates the synchronization status of each TRP in the multiple TRPs.

18. The method of claim 17, wherein the synchronization state of the TRP is obtained from a base station controlling each of the plurality of TRPs.

19. The method of claim 17, wherein: The synchronization assistance data includes one or more groups of the plurality of TRPs, and the TRPs within each of the one or more groups are expected to be synchronized with each other.

20. The method of claim 17, wherein: The synchronization assistance data includes a synchronization indicator for each TRP in the plurality of TRPs, and TRPs in the plurality of TRPs having the same synchronization indicator are expected to be synchronized with each other.

21. The method according to claim 17, further comprising: Sending auxiliary data for the positioning session to the UE, wherein the auxiliary data indicates one or more types of positioning procedures performed by the UE using one or more groups of the multiple TRPs, wherein the one or more groups of the multiple TRPs are based on the synchronization state of each TRP in the multiple TRPs, and wherein the TRPs in the multiple TRPs within each group of the one or more groups are expected to be synchronized with each other.

22. The method of claim 21, wherein the one or more types of positioning procedures include a time difference of arrival (TDOA) based positioning procedure, a multiple round trip time (multi-RTT) positioning procedure, a round trip time (RTT) positioning procedure, or any combination thereof.

23. The method of claim 21, wherein the auxiliary data configures the UE to perform different positioning procedures using each group of the multiple TRPs.

24. The method of claim 21, wherein the assistance data comprises the synchronization assistance data.

25. The method of claim 17, further comprising: A request for the synchronization assistance data is received.

26. A method according to claim 25, wherein the request identifies one or more TRPs among the multiple TRPs that can be detected by the UE.

27. A method according to claim 25, wherein TRPs among the multiple TRPs other than the one or more TRPs are included in the synchronization assistance data based on the TRP being expected to be measurable by the UE.

28. The method of claim 17, wherein the synchronization state of each TRP in the plurality of TRPs is obtained via New Radio (NR) Positioning Protocol Type A (NRPPa) signaling.

29. A user equipment (UE), the user equipment (UE) comprising: 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: receiving, via the at least one transceiver, synchronization assistance data for a positioning session, the synchronization assistance data indicating at least a synchronization state of each of a plurality of anchor nodes relative to other anchor nodes of the plurality of anchor nodes; as well as During the positioning session, at least one positioning procedure is performed with at least one anchor node among the plurality of anchor nodes based on the synchronization state of the at least one anchor node.

30. A location server, comprising: 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: Obtaining a synchronization state of each of a plurality of transmit receive points (TRPs) relative to other TRPs of the plurality of TRPs; as well as Synchronization assistance data for a positioning session is sent to a user equipment (UE) via the at least one transceiver, and the synchronization assistance data at least indicates the synchronization status of each TRP in the multiple TRPs.