Timing advance effectiveness timer for location estimation based on enhanced cell identifier

Abstract

A technique for wireless communication is disclosed. In one aspect, the User Equipment (UE) determines that the timing advance is valid based on a timing advance (TA) validity timer associated with the location estimation based on Enhanced Cell Identity (eCID). The UE also sends an eCID measurement report, including eCID measurement information and an indication of the TA, to the location estimation entity. The location estimation entity determines the UE's location estimation based on the eCID measurement report.

Description

Background Technology 1. Technical Field

[0002] All aspects of this disclosure relate to wireless technology.

[0003] 2. Description of relevant technologies

[0004] Wireless communication systems have evolved through many generations, including first-generation analog radiotelephone service (1G), second-generation (2G) digital radiotelephone service (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data, wireless services with internet capabilities, and fourth-generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular systems and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog Advanced Mobile Phone Systems (AMPS), as well as 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 others.

[0005] The fifth-generation (5G) wireless standard, known as New Radio (NR), delivers higher data transfer speeds, more connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance (NGC), the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on Positioning Reference Signals (RS-P), such as downlink, uplink, or sidelink Positioning Reference Signals (PRS)), and other technological enhancements compared to previous standards. These enhancements, along with the use of higher frequency bands, advancements in the PRS process and technology, and the high-density deployment of 5G, enable high-accuracy positioning based on 5G. Summary of the Invention

[0006] The following is a simplified summary of the invention relating to one or more aspects disclosed herein. Therefore, this summary should not be considered an exhaustive overview relating to all conceived aspects, nor should it be considered to identify key or decisive elements relating to all conceived aspects or to depict the scope associated with any particular aspect. Thus, the sole purpose of this summary is to present, in a simplified form, certain concepts relating to one or more aspects involving the mechanisms disclosed herein, prior to the detailed description presented below.

[0007] In one aspect, a method of operating a user equipment (UE) includes: receiving a first timing advance associated with a first radio network component; determining a timing advance validity timer for positioning estimation based on enhanced cell identity (eCID); determining, based on the timing advance validity timer, that the first timing advance is valid; and, in response to determining that the first timing advance is valid, sending an eCID measurement report to a positioning estimation entity including eCID measurement information and a first indication of the first timing advance.

[0008] In one aspect, a method for operating a location estimation entity includes: receiving an enhanced cell identity (eCID) measurement report from a user equipment (UE), the eCID measurement report including eCID measurement information and a first indication of a first timing advance associated with a first radio network component, the first timing advance being associated with a timing advance validity timer for location estimation based on the enhanced cell identity eCID; and determining a location estimate of the UE based on the eCID measurement information and the first timing advance.

[0009] In one aspect, a user equipment (UE) includes: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to: receive a first timing advance associated with a first radio network component via the one or more transceivers; determine a timing advance validity timer for location estimation based on enhanced cell identity (eCID); determine that the first timing advance is valid based on the timing advance validity timer; and, in response to determining that the first timing advance is valid, send an eCID measurement report, including eCID measurement information and a first indication of the first timing advance, to a location estimation entity via the one or more transceivers.

[0010] In one aspect, a location estimation entity includes: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to: receive an enhanced cell identity (eCID) measurement report from a user equipment (UE) via the one or more transceivers, the eCID measurement report including eCID measurement information and a first indication of a first timing advance associated with a first radio network component, the first timing advance being associated with a timing advance validity timer for location estimation based on enhanced cell identity eCID; and determine a location estimate of the UE based on the eCID measurement information and the first timing advance.

[0011] In one aspect, a user equipment (UE) includes: components for receiving a first timing advance associated with a first radio network component; components for determining a timing advance validity timer for location estimation based on enhanced cell identity (eCID); components for determining that the first timing advance is valid based on the timing advance validity timer; and components for sending an eCID measurement report, including eCID measurement information and a first indication of the first timing advance, to a location estimation entity in response to determining that the first timing advance is valid.

[0012] In one aspect, a location estimation entity includes: components for receiving an enhanced cell identity (eCID) measurement report from a user equipment (UE), the eCID measurement report including eCID measurement information and a first indication of a first timing advance associated with a first radio network component, the first timing advance being associated with a timing advance validity timer for location estimation based on the enhanced cell identity eCID; and components for determining a location estimate of the UE based on the eCID measurement information and the first timing advance.

[0013] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive a first timing advance associated with a first radio network component; determine a timing advance validity timer for location estimation based on enhanced cell identity (eCID); determine, based on the timing advance validity timer, that the first timing advance is valid; and, in response to determining that the first timing advance is valid, send an eCID measurement report to a location estimation entity including eCID measurement information and a first indication of the first timing advance.

[0014] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a location estimation entity, cause the location estimation entity to: receive an enhanced cell identity (eCID) measurement report from a user equipment (UE), the eCID measurement report including eCID measurement information and a first indication of a first timing advance associated with a first radio network component, the first timing advance being associated with a timing advance validity timer for location estimation based on the enhanced cell identity eCID; and determine a location estimate of the UE based on the eCID measurement information and the first timing advance.

[0015] Based on the accompanying drawings and detailed description, other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art. Attached Figure Description

[0016] The accompanying drawings are provided to help describe various aspects of this disclosure, and are provided for illustrative purposes only and not to limit the aspects.

[0017] Figure 1 Example wireless communication systems according to various aspects of this disclosure are illustrated.

[0018] Figure 2A , Figure 2B and Figure 2C Example wireless network architectures based on various aspects of this disclosure are illustrated.

[0019] Figure 3A , Figure 3B and Figure 3C It is a simplified block diagram of several examples of components that can be used in user equipment (UE), base stations and network entities and configured to support communications as taught herein.

[0020] Figure 4 This is a diagram illustrating an example frame structure according to various aspects of this disclosure.

[0021] Figure 5 Different Radio Resource Control (RRC) states available in a New Radio (NR) according to various aspects of this disclosure are illustrated.

[0022] Figure 6 An example of a region identifier (ID) arrangement according to various aspects of this disclosure is illustrated.

[0023] Figure 7 An exemplary process of communication according to one aspect of this disclosure is illustrated.

[0024] Figure 8 An exemplary process of communication according to one aspect of this disclosure is illustrated. Detailed Implementation

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

[0026] The overall scope involves a timing advance (TA) validity timer for location estimation based on enhanced cell identifiers (ESIs). Location estimation based on New Radio (NR) enhanced cell identity (eCID) is one of the location technologies supported by 5G. TA, along with many other parameters, is one of the parameters that a user equipment (UE) can use for eCID-based location estimation. In some designs, reporting TA to the location estimation entity is optional in both UE-based eCID location estimation and UE-assisted eCID location estimation. However, this can improve location accuracy if TA is known to the location estimation entity. For eCID-based location estimation where the UE is in the Radio Resource Control (RRC)_INACTIVE state, the UE should generally not be transitioned to the RRC_CONNECTED state to obtain TA. For eCID-based location estimation, the current system does not specify how long TA (e.g., from a previous RRC_CONNECTED state) remains valid.

[0027] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. Aspects of this disclosure relate to a timing advance (TA) validity timer for eCID-based location estimation. In one aspect, the TA validity timer can be used to determine whether an associated TA is valid for an eCID-based location estimation session. If so, the TA can be reported to the location estimation entity and then used for eCID-based location estimation. Such aspects can provide various technical advantages, such as improved location accuracy for eCID-based location estimation.

[0028] The terms “exemplary” and / or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and / or “example” is not necessarily to be construed as superior to or better than other aspects. Similarly, the term “aspects of this disclosure” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed.

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

[0030] Furthermore, many aspects are described according to a sequence of actions to be performed by elements of, for example, a computing device. It will be appreciated that the various actions described herein can be performed by specific circuitry (e.g., an application-specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of both. Additionally, the sequence of actions described herein can be considered to be entirely embodied in any form of non-transitory computer-readable storage medium storing a corresponding set of computer instructions that, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Therefore, various aspects of this disclosure can be embodied in a variety of different forms, all of which are contemplated within the scope of the claimed subject matter. Furthermore, for each aspect described herein, any corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions."

[0031] As used herein, unless otherwise stated, the terms “User Equipment” (UE) and “Base Station” are not intended to be specific or otherwise limited to any particular Radio Access Technology (RAT). Generally, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., mobile phone, router, tablet computer, laptop computer, consumer asset positioning device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.). A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term “UE” can be interchangeably referred to as “Access Terminal” or “AT,” “Client Equipment,” “Wireless Equipment,” “Subscriber Equipment,” “Subscriber Terminal,” “Subscriber Station,” “User Terminal” or “UT,” “Mobile Equipment,” “Mobile Terminal,” “Mobile Station,” or variations thereof. Generally, a UE can communicate with a core network via the RAN, and through the core network, a UE can connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through wired access networks, wireless local area network (WLAN) networks (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, etc.).

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

[0033] The term "base station" can refer to a single physical transmit / receive point (TRP) or multiple physical TRPs that may or may not be co-located. For example, when the term "base station" refers to a single physical TRP, the physical TRP can be the antenna of a base station corresponding to a cell (or several cell sectors) of the base station. When the term "base station" refers to multiple co-located physical TRPs, the physical TRP can be the antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). When the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP can be a distributed antenna system (DAS) (a network of spatially separated antennas connected via a transmission medium to a common source) or a remote radio headend (RRH) (a remote base station connected to a serving base station). Alternatively, a non-co-located physical TRP can be the serving base station from which the UE receives measurement reports and a neighboring base station where the UE is measuring its reference radio frequency (RF) signal. Because, as used herein, a TRP is the point by which a base station transmits and receives radio signals, references to transmitting from or receiving at a base station should be understood to refer to a specific TRP of the base station.

[0034] In some specific implementations supporting UE positioning, the base station may not support the UE's radio access (e.g., it may not support data, voice, and / or signaling connections for the UE), but may instead transmit reference signals to the UE for measurement and / or receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of transmitting signals to the UE) and / or as a location measurement unit (e.g., in the case of receiving and measuring signals from the UE).

[0035] An “RF signal” refers to an electromagnetic wave of a given frequency that transmits information across the space between a transmitter and a receiver. As used herein, a transmitter may send a single “RF signal” or multiple “RF signals” to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple “RF signals” corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and 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 the context clearly indicates that the term “signal” refers to a wireless signal or an RF signal.

[0036] Figure 1 An example wireless communication system 100 according to various aspects of this disclosure is illustrated. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled "BS") and various UEs 104. Base station 102 may include macro cell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macro cell base station may include an eNB and / or an ng-eNB (wherein the wireless communication system 100 corresponds to an LTE network), or a gNB (wherein the wireless communication system 100 corresponds to an NR network), or a combination of both, and the small cell base station may include femtocells, picocells, microcells, etc.

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

[0038] In addition to other functions, base station 102 may perform functions associated with one or more of the following: transmitting 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, location, and delivery of warning messages. Base stations 102 may communicate with each other directly or indirectly (e.g., via EPC / 5GC) on backhaul link 134, which may be wired or wireless.

[0039] Base station 102 can wirelessly communicate with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells can 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., via a frequency resource, which is referred to as a carrier frequency, component carrier, carrier, frequency band, etc.) and can be associated with an identifier (e.g., Physical Cell Identifier (PCI), Enhanced Cell Identifier (ECI), Virtual Cell Identifier (VCI), Cell Global Identifier (CGI), etc.) used to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells can be configured according to different protocol types that can provide access for different types of UEs (e.g., Machine Type Communication (MTC), Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB), or other protocol types). Because a cell is supported by a specific base station, the term “cell” can refer to either or both of the logical communication entity and the base station supporting the logical communication entity, depending on the context. Furthermore, since the TRP is typically the physical transmission point of a cell, the terms "cell" and "TRP" can be used interchangeably. In some cases, the term "cell" can also refer to the geographical coverage area of ​​a base station (e.g., a sector), as long as the carrier frequency can be detected and used for communication within a portion of the geographical coverage area 110.

[0040] While the geographic coverage areas 110 of adjacent macro cell base stations 102 may partially overlap (e.g., in handover areas), some areas within geographic coverage areas 110 may substantially overlap with 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 macro cell base stations 102. A network that includes both small cell base stations and macro cell base stations can be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB) that can provide service to a restricted group referred to as a Closed Subscriber Group (CSG).

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

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

[0043] Small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell base station 102' can employ LTE or NR technology and use the same 5GHz unlicensed spectrum as WLAN AP 150. Small cell base station 102' employing LTE / 5G in unlicensed spectrum can improve the coverage and / or increase the capacity of the access network. NR in unlicensed spectrum may be referred to as NR-U. LTE in unlicensed spectrum may be referred to as LTE-U, Licensed Assisted Access (LAA), or MULTEFIRE. ® .

[0044] The wireless communication system 100 may also include a millimeter-wave (mmW) base station 180, which can operate at mmW and / or near-mmW frequencies to communicate with the UE 182. Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). EHF has a range of 30 GHz to 300 GHz, with wavelengths between 1 mm and 10 mm. Radio waves in this band are referred to as millimeter waves. Near-mmW extends down to frequencies of 3 GHz with wavelengths of 100 mm. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz, and are also referred to as centimeter waves. Communication using mmW / near-mmW radio bands has high path loss and relatively short range. The mmW base station 180 and the UE 182 can utilize beamforming (transmit and / or receive) on the mmW communication link 184 to compensate for the extremely high path loss and short range. Furthermore, it should be understood that, in alternative configurations, 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 examples are merely illustrative and should not be construed as limiting the various aspects disclosed herein.

[0045] Transmit beamforming is a technique used to focus RF signals 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). Using transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thus providing the receiving device with a faster and stronger RF signal (in terms of data rate). To change the directivity of the RF signal during transmission, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, the network node can use an array of antennas (called a "phased array" or "antenna array") that forms an RF beam that can be "manipulated" to be pointed in different directions without actually moving the antennas. Specifically, RF currents from the transmitters are fed to individual antennas with the correct phase relationship, such that radio waves from the individual antennas add up in the desired direction to increase radiation, while canceling out in the undesired direction to suppress radiation.

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

[0047] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, the receiver may increase the gain setting of an 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 described as performing 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 that the beam gain in that direction is the highest compared to the beam gain of all other receive beams available to the receiver in that direction. 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.

[0048] The transmit and receive beams can be spatially correlated. Spatial correlation means that parameters for a second beam (e.g., transmit or receive beam) for a second reference signal can be derived based on information about a first beam (e.g., receive or transmit beam) for a first reference signal. For example, a UE can 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 can then form a transmit beam for transmitting an uplink reference signal (e.g., a sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.

[0049] It is important to note that, depending on the entity forming the "downlink" beam, the beam can be either a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to transmit a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam for receiving the downlink reference signal. Similarly, depending on the entity forming the "uplink" beam, the beam can be either a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, the uplink beam is an uplink receive beam, while if the UE is forming an uplink beam, the uplink beam is an uplink transmit beam.

[0050] 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 designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. A similar naming issue sometimes occurs with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this differs from the designation used by the International Telecommunication Union. ® Extremely high frequency (EHF) bands (30 GHz to 300 GHz) are designated as “millimeter wave” bands.

[0051] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have designated the operating bands for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been designated as the frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0052] In light of the foregoing, unless otherwise specifically stated, it should be understood that, as used herein, the term "below 6 GHz" and the like can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that, as used herein, the term "millimeter wave" and the like can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR4-a or FR4-1 and / or FR5, or within the EHF band.

[0053] In multi-carrier systems such as 5G, one of the carrier frequencies is referred to as the "primary carrier," "anchor carrier," "primary serving cell," or "PCell," and the remaining carrier frequencies are referred to as "secondary carriers," "secondary serving cells," or "SCell." In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) used by UE 104 / 182 and the cell, where 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 on a licensed frequency (however, this is not always the case). The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured and used to provide additional radio resources once an RRC connection is established between UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier on an unlicensed frequency. Secondary carriers may contain only the necessary signaling information and signals. For example, since the primary uplink and primary downlink carriers are typically UE-specific, the UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 within a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to the carrier frequency / component carrier through which a base station communicates, the terms "cell," "serving cell," "component carrier," and "carrier frequency" can be used interchangeably.

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

[0055] The wireless communication system 100 may also include a UE 164, which can communicate with the macro cell base station 102 via communication link 120 and / or with the mmW base station 180 via mmW communication link 184. For example, the macro cell base station 102 may support PCells and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0056] In some cases, UE 164 and UE 182 may be able to communicate via sidelink. A sidelink-capable UE (SL-UE) can communicate with base station 102 via communication link 120 using the Uu interface (i.e., the air interface between the UE and the base station). SL-UEs (e.g., UE 164, UE 182) can also communicate directly with each other via radio sidelink 160 using the PC5 interface (i.e., the air interface between sidelink-capable UEs). Radio sidelink (or simply "sidelink") is an adaptation of core cellular network (e.g., LTE, NR) standards that allows direct communication between two or more UEs without the need for communication through a base station. Sidelink communication can be unicast or multicast and can be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, emergency rescue applications, etc. One or more SL-UEs in a group of SL-UEs utilizing sidelink communication may be located within the geographical coverage area 110 of base station 102. Other SL-UEs in this group may be outside the geographical coverage area 110 of base station 102, or may be unable to receive transmissions from base station 102 for other reasons. In some cases, the groups of SL-UEs communicating via sidelink communication may utilize a one-to-many (1:M) system, where each SL-UE transmits to every other SL-UE in the group. In some cases, base station 102 facilitates the scheduling of resources used for sidelink communication. In other cases, sidelink communication is performed between the individual SL-UEs without involving base station 102.

[0057] On one hand, the sidelink 160 can operate via a wireless communication medium of interest that can be shared with other vehicles and / or infrastructure access points and other RATs for wireless communication. "Medium" can include one or more time, frequency, and / or space communication resources (e.g., covering one or more channels across one or more carriers) associated with wireless communication between one or more transmitter / receiver pairs. On another hand, the medium of interest may correspond to at least a portion of unlicensed frequency bands shared among various RATs. While different licensed frequency bands have been reserved for certain communication systems (e.g., by government entities such as the U.S. Federal Communications Commission (FCC), these systems (particularly those employing small cell access points) have recently extended their operation to unlicensed National Information Infrastructure (U-NII) bands used by Wireless Local Area Network (WLAN) technologies (most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include various variants of CDMA, TDMA, FDMA, Orthogonal FDMA (OFDMA), Single-Carrier FDMA (SC-FDMA), and so on.

[0058] It should be noted that, although Figure 1 Only two of these UEs are exemplified as SL-UEs (i.e., UE 164 and UE 182), but any UE exemplified can be an SL-UE. Furthermore, although only UE 182 is described as capable of beamforming, any UE exemplified (including UE 164) can be capable of beamforming. When SL-UEs are capable of beamforming, they can beamform towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UE 104), towards base stations (e.g., base station 102, base station 180, small cell 102', access point 150), etc. Therefore, in some cases, UE 164 and UE 182 can utilize beamforming via sidelink 160.

[0059] exist Figure 1 In the example, the UE shown (for simplicity, in) Figure 1Any UE (shown as a single UE 104) can receive signal 124 from one or more Earth-orbiting spacecraft (SV) 112 (e.g., satellites). In one aspect, SV 112 may be part of a satellite positioning system that allows UE 104 to use as an independent source of location information. Satellite positioning systems typically include a system of transmitters (e.g., SV 112) positioned such that a receiver (e.g., UE 104) can determine its location on or above the Earth based at least in part on positioning signals (e.g., signal 124) received from the transmitters. Such transmitters typically transmit signals marked with a set number of repeating pseudo-random noise (PN) codes. While typically located in SV 112, transmitters may sometimes be located at ground-based control stations, base stations 102, and / or other UEs 104. UE 104 may include one or more dedicated receivers specifically designed to receive signal 124 in order to derive geographic location information from SV 112.

[0060] In a satellite positioning system, the use of signal 124 can be enhanced by various satellite-based augmentation systems (SBAS), which may be associated with or otherwise made capable of being used with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential correction, etc., such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlap Service (EGNOS), Multifunctional Satellite Augmentation System (MSAS), GPS-assisted geographic augmentation navigation, or GPS and geographic augmentation navigation system (GAGAN). Therefore, 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.

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

[0062] The wireless communication system 100 may also include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "side links"). Figure 1 In one example, UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of the base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through this D2D P2P link), and has a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through this D2D P2P link). In one example, D2D P2P links 192 and 194 can utilize any known D2D RAT (such as LTE Direct (LTE-D), Wi-Fi Direct). ® ,Bluetooth ® (etc.) to support.

[0063] Figure 2A An example wireless network architecture 200 is illustrated. For instance, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can be functionally viewed as control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.), which work together to form the 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, specifically to user plane functions 212 and control plane functions 214, respectively. In an additional configuration, the ng-eNB 224 can also connect 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. Furthermore, the ng-eNB 224 can communicate directly with the gNB 222 via a backhaul connection 223. In some configurations, the next-generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of both ng-eNBs 224 and gNBs 222. Either or both of the gNBs 222 or ng-eNBs 224 can communicate with one or more UEs 204 (e.g., any of the UEs described herein).

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

[0065] Figure 2B Another example wireless network architecture 240.5GC 260 is illustrated (which can be used with...). Figure 2AThe 5GC 210 (corresponding to 5GC 210) can be functionally considered as a control plane function provided by the Access and Mobility Management Function (AMF) 264 and a user plane function provided by the User Plane Function (UPF) 262, which work together to form the core network (i.e., 5GC 260). The functions of AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and the 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 the Short Message Service Function (SMSF) (not shown), and Secure Anchoring Functionality (SEAF). AMF 264 also interacts with the Authentication Server Function (AUSF) (not shown) and UE 204 and receives an intermediate key established as a result of the UE 204's authentication process. In the case of UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM) authentication, AMF 264 retrieves security material from the AMF. AMF 264 also includes Security Context Management (SCM). The SCM receives a key from the SEAF and uses this key to derive an access network-specific key. AMF 264 functionality also includes location service management for regulatory services, transmission of location service messages between UE 204 and Location Management Function (LMF) 270 (which acts as location server 230), transmission of location service messages between NG-RAN 220 and LMF 270, Evolved Packet System (EPS) bearer identifier allocation for EPS interoperability, and UE 204 mobility event notification. Furthermore, AMF 264 also supports non-3GPP... ® (Third Generation Partner Program) Access network functionality.

[0066] The functions of UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (where applicable), acting as an external Protocol Data Unit (PDU) session point interconnecting to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., strobing, redirection, traffic steering), lawful eavesdropping (user plane collection), traffic usage reporting, quality of service (QoS) processing for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (Service Data Flow (SDF) to QoS flow mapping), transport-level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and delivering 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 location servers (such as SLP 272) on the user plane.

[0067] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, service orientation configuration at UPF 262 for routing services to the correct destination, 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.

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

[0069] Another optional aspect may include a third-party server 274, which can communicate with 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 estimation) of UE 204. Therefore, in some cases, the third-party server 274 may be referred to as a Location Services (LCS) client or an external client. The third-party 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, each may correspond to a single server.

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

[0071] The functionality of the gNB 222 is divided among the gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DU) 228, and one or more gNB Radio Units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically allocated to the gNB-DU 228, including user data delivery, mobility control, radio access network sharing, location, session management, etc. More specifically, the gNB-CU 226 typically hosts the Radio Resource Control (RRC), Serving 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 Media Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and a cell is supported by only one gNB-DU 228. The interface 232 between gNB-CU 226 and one or more gNB-DU 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of gNB 222 is typically managed by one or more independent gNB-RU 229s, which perform functions such as power amplification and signal transmission / reception. The interface between gNB-DU 228 and gNB-RU 229 is referred to as the "Fx" interface. Therefore, UE 204 communicates with gNB-CU 226 via the RRC, SDAP, and PDCP layers, with gNB-DU 228 via the RLC and MAC layers, and with gNB-RU 229 via the PHY layer.

[0072] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, or network equipment (such as base stations or one or more units (or components) performing base station functions) can be implemented in aggregated or decomposed architectures. For example, base stations (such as Node B (NB), evolved NB (eNB), NR base stations, 5GNB, AP, TRP, cells, etc.) can be implemented as aggregated base stations (also known as standalone base stations or monolithic base stations) or decomposed base stations.

[0073] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0074] Base station type operation or network design can consider the aggregation characteristics of base station functionality. For example, decomposed base stations can be used in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN) (such as those developed by the O-RAN Alliance), and other similar networks. ® This can be used in proposed network configurations or virtualized radio access networks (vRAN, also known as cloud radio access networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which allows for flexibility in network design. Various units in a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

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

[0076] Each unit in the cells (i.e., CU 280, DU 285, RU 287, and near-RT RIC 259, non-RT RIC 257, and SMO frame 255) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the cells, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals or transmit signals to one or more other units, or both, via wireless transmission media.

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

[0078] DU 285 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 287s. In some aspects, DU 285 may be at least partially defined according to functional partitioning (such as by the 3rd Generation Partnership Project (3GPP)). ®The DU285 is functionally partitioned to host one or more of the RLC layer, MAC layer, and one or more high-PHY layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation). In some respects, the DU285 may further host one or more low-PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU285 or with control functions hosted by the CU280.

[0079] Lower-layer functionality can be implemented by one or more RU 287s. In some deployments, an RU287 controlled by a DU 285 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, or both, at least in part based on functional decomposition (such as lower-layer functional decomposition). In this architecture, the RU 287 may be implemented to handle over-the-air (OTA) communications with one or more UE 204s. In some specific implementations, the 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 enables the implementation of the DU 285 and CU 280 in a cloud-based RAN architecture (such as a vRAN architecture).

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

[0081] The non-RT RIC 257 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 259. The non-RT RIC 257 can be coupled to or communicate with the near-RT RIC 259, such as via an A1 interface. The near-RT RIC 259 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via data collection and actions through an interface such as an E2 interface, connecting one or more CU 280s, one or more DU 285s, or both, and O-eNBs to the near-RT RIC 259.

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

[0083] Figure 3A , Figure 3B and Figure 3C Examples are shown that can be incorporated into UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF270, or alternatively may be independent of UE 302). Figure 2A and Figure 2BSeveral example components (represented by corresponding boxes) in the NG-RAN 220 and / or 5GC 210 / 260 infrastructure (such as private networks) depicted herein support the operation as described herein. It should be understood that these components may be implemented in different specific implementations in different types of devices (e.g., in ASICs, in System-on-Chip (SoCs), etc.). The illustrated components may also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Furthermore, a given device may contain 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.

[0084] UE 302 and base station 304 each include one or more Wireless Wide Area Network (WWAN) transceivers 310 and 350, which provide components (e.g., components for transmitting, components for receiving, components for measuring, components for tuning, components for blocking transmission, etc.) for communication 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 for communication with other network nodes (such as other UEs, access points, base stations (e.g., eNB, gNB), etc.) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) through a wireless communication medium of interest (e.g., a time / frequency resource set in a specific spectrum). WWAN transceivers 310 and 350 can be configured in different ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, to receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, WWAN transceivers 310 and 350 each include: one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively; and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.

[0085] In at least 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 access over a wireless communication medium of interest via at least one designated RAT (e.g., Wi-Fi, LTE Direct, Bluetooth). ® ZIGBEE ® Z-WAVE ® Components (e.g., components for transmitting, components for receiving, components for measuring, components for tuning, components for blocking transmission, etc.) that enable communication between PC5, Dedicated Short-Range Communication (DSRC), Wireless Access for Vehicle Environments (WAVE), Near Field Communication (NFC), Ultra-Wideband (UWB), etc.) and other network nodes (such as other UEs, access points, base stations, etc.). Short-range transceivers 320 and 360 can be configured in different ways to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.) respectively according to a specified RAT, and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.) respectively. Specifically, the short-range wireless transceiver 320 and short-range wireless transceiver 360 each include: one or more transmitters 324 and 364 respectively for transmitting and encoding signals 328 and 368, and one or more receivers 322 and 362 respectively for receiving and decoding signals 328 and 368. As a specific example, the short-range wireless transceiver 320 and short-range wireless transceiver 360 can be Wi-Fi transceivers, Bluetooth transceivers, etc. ® Transceiver, Zigbee ® and / or Z-WAVE ® Transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

[0086] In at least some cases, UE 302 and base station 304 also include satellite signal interfaces 330 and 370, each satellite signal interface including one or more satellite signal receivers 332 and 372, and optionally including one or more satellite signal transmitters 334 and 374, respectively. In some cases, base station 304 may be a terrestrial base station that can communicate with a spacecraft (e.g., spacecraft 112) via satellite signal interface 370. In other cases, base station 304 may be a spacecraft (or other non-terrestrial entity) that uses satellite signal interface 370 to communicate with terrestrial networks and / or other spacecraft.

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

[0088] Optional satellite signal transmitters 334 and 374 (when present) can be connected to one or more antennas 336 and 376, respectively, and can be provided with components for transmitting satellite positioning / communication signals 338 and 378, respectively. When satellite signal transmitter 374 is a satellite positioning system transmitter, the satellite positioning / communication signal 378 can be a GPS signal, GLONASS signal, etc. ® Signals include Galileo signals, BeiDou signals, NAVIC signals, and QZSS signals. When satellite signal transmitters 334 and 374 are NTN transmitters, satellite positioning / communication signals 338 and 378 can be communication signals originating from a 5G network (e.g., carrying control and / or user data). Satellite signal transmitters 334 and 374 can include any suitable hardware and / or software for transmitting satellite positioning / communication signals 338 and 378, respectively. Satellite signal transmitters 334 and 374 can request appropriate information and operations from other systems.

[0089] Base station 304 and network entity 306 each include one or more network transceivers 380 and 390, which provide components (e.g., transmitting components, receiving components, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, base station 304 may use 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. Similarly, network entity 306 may use one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or to communicate with other network entities 306 via one or more wired or wireless core network interfaces.

[0090] Transceivers can be configured to communicate via wired or wireless links. A transceiver (whether wired or wireless) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). In some embodiments, the transceiver may be an integrated device (e.g., implementing transmitter and receiver circuitry in a single device), in some embodiments it may include separate transmitter and receiver circuitry, or in other embodiments it may be implemented in a different manner. The transmitter and receiver circuitry of a wired transceiver (e.g., network transceiver 380 and network transceiver 390 in some embodiments) may be coupled to one or more wired network interface ports. Wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the corresponding device (e.g., UE 302, base station 304) to perform transmit beamforming, as described herein. Similarly, wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter and receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366), such that the corresponding device may perform only receive or only transmit at a given time, rather than both receive and transmit simultaneously. Wireless transceivers (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include network listening modules (NLMs) for performing various measurements.

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

[0092] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operation disclosed herein. UE 302, base station 304, and network entity 306 each include one or more processors 342, 384, and 394 for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 342, 384, and 394 may provide components for processing, such as components for determining, components for calculating, components for receiving, components for transmitting, components for indicating, etc. In one aspect, processors 342, 384, and 394 may include, for example, one or more general-purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), other programmable logic devices or processing circuits, or various combinations thereof.

[0093] UE 302, base station 304, and network entity 306 each include memory circuitry implementing memories 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Therefore, memories 340, 386, and 396 can provide components for storage, retrieval, maintenance, etc. In some cases, UE 302, base station 304, and network entity 306 may each include TA validity timer components 348, 388, and 398. TA validity timer components 348, 388, and 398 may be hardware circuitry that is part of or coupled to processors 342, 384, and 394, respectively, which, when executed, enable UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other respects, TA validity timer components 348, 388, and 398 may be external to processors 342, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, TA validity timer components 348, 388, and 398 may be memory modules stored in memories 340, 386, and 396, respectively, which, when executed by processors 342, 384, and 394 (or the modem processing system, another processing system, etc.), cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. Figure 3A Possible locations of the TA validity timer component 348 are illustrated. This TA validity timer component may be part of, for example, one or more WWAN transceivers 310, memory 340, one or more processors 342, or any combination thereof, or it may be a standalone component. Figure 3B Possible locations of the TA validity timer component 388 are illustrated. This TA validity timer component may be part of, for example, one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or it may be a standalone component. Figure 3C Possible locations of the TA validity timer component 398 are illustrated. This TA validity timer component may be part of, for example, one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or it may be a standalone component.

[0094] UE 302 may include one or more sensors 344 coupled to one or more processors 342 to provide components for sensing or detecting motion and / or orientation information independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal interfaces 330. By way of example, sensor 344 may include accelerometers (e.g., microelectromechanical systems (MEMS) devices), gyroscopes, geomagnetic sensors (e.g., compasses), altimeters (e.g., barometric altimeters), and / or any other type of motion detection sensor. Furthermore, 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 multi-axis accelerometers and orientation sensors to provide the ability to calculate positioning in two-dimensional (2D) and / or three-dimensional (3D) coordinate systems.

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

[0096] Referring more specifically to one or more processors 384, in the downlink, IP packets from network entity 306 can be provided to processor 384. One or more processors 384 can implement functionality for the RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. One or more processors 384 may provide: RRC layer functionality associated with broadcasting system information (e.g., Master Information Block (MIB), System Information Block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer PDUs, error correction via Automatic Repeat Request (ARQ), concatenation, segmentation, and reassembly of RLC Service Data Units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority processing, and logical channel priority ordering.

[0097] Transmitter 354 and receiver 352 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) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. Transmitter 354 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to orthogonal frequency division multiplexing (OFDM) subcarriers, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM symbol stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from the channel estimator can be used to determine the decoding and modulation schemes, as well as for spatial processing. The channel estimates can be derived from a reference signal transmitted by UE 302 and / or channel condition feedback. Each spatial stream can then be provided to one or more different antennas 356. The transmitter 354 can use the corresponding spatial stream to modulate an RF carrier for transmission.

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

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

[0100] Similar to the functionality described in conjunction with downlink transmissions performed by base station 304, one or more processors 342 provide: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with the delivery of upper-layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via Hybrid Automatic Repeat Request (HARQ), priority processing, and logical channel priority ordering.

[0101] The channel estimate derived by the channel estimator from the reference signal or feedback transmitted by the base station 304 can be used by the transmitter 314 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the transmitter 314 can be provided to different antennas 316. The transmitter 314 can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0102] Uplink transmissions are processed at base station 304 in a manner similar to that described in conjunction with the receiver function at UE 302. Receiver 352 receives signals via its corresponding antenna 356. Receiver 352 recovers the information modulated onto the RF carrier and provides this information to one or more processors 384.

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

[0104] For convenience, UE 302, base station 304 and / or network entity 306 are in Figure 3A , Figure 3B and Figure 3CThe document 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 functionalities in different designs. In particular, Figures 3A to 3C Various components are optional in alternative configurations, and various aspects include configurations that can vary due to design choices, cost, equipment usage, or other considerations. For example, in Figure 3A In certain cases, specific implementations of UE 302 may omit WWAN transceiver 310 (e.g., wearable devices, tablets, personal computers (PCs), or laptops may have Wi-Fi and / or Bluetooth). ® (Without cellular capability), or the short-range wireless transceiver 320 can be omitted (e.g., cellular only), or the satellite signal interface 330 can be omitted, or the sensor 344 can be omitted, etc. In another example, in Figure 3B In certain cases, specific implementations of base station 304 may omit WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or short-range wireless transceiver 360 (e.g., cellular only), or satellite signal interface 370, etc. For the sake of brevity, examples of various alternative configurations are not provided herein, but will be readily understood by those skilled in the art.

[0105] Various components of UE 302, base station 304, and network entity 306 can be communicatively coupled to each other via data buses 308, 382, ​​and 392, respectively. In one aspect, data buses 308, 382, ​​and 392 can form or be part of the communication interfaces of UE 302, base station 304, and network entity 306, respectively. For example, in cases where different logical entities are embodied in the same device (e.g., gNB and location server functionality integrated into the same base station 304), data buses 308, 382, ​​and 392 can provide communication between these logical entities.

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

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

[0108] Various frame structures can be used to support downlink and uplink transmission between network nodes (e.g., base stations and UEs). Figure 4 Figure 400 illustrates an example frame structure according to various aspects of this disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.

[0109] LTE (and in some cases NR) uses Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single-Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option to use OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are often referred to as tones, frequency slots, etc. Each subcarrier can be modulated using data. Generally, modulation symbols are transmitted using OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kHz, and the minimum resource allocation (resource block) can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, the nominal Fast Fourier Transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband can cover 1.08 MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, there can be 1, 2, 4, 8, or 16 subbands, respectively.

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

[0111] exist Figure 4 In the example, a parameter set of 15kHz is used. Therefore, in the time domain, a 10ms frame is divided into 10 equal-sized subframes, each subframe being 1ms long, and each subframe including one time slot. Figure 4 In the diagram, time is represented horizontally (on the X-axis), with time increasing from left to right, while frequency is represented vertically (on the Y-axis), with frequency increasing (or decreasing) from bottom to top.

[0112] A resource grid can be used to represent time slots, each of which includes one or more time-concurrent resource blocks (RBs) (also known as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE corresponds to a symbol length in the time domain and a subcarrier in the frequency domain. Figure 4In the parameter set, for a normal cyclic prefix, the RB can contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, the RB can contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0113] Some REs may carry reference (pilot) signals (RS). These reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSB), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communication. Figure 4 An example location (labeled "R") of an RE carrying a reference signal is shown.

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

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

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

[0117] A “PRS resource set” is a collection of PRS resources used to transmit PRS signals, where each PRS resource has a PRS resource ID. Furthermore, PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and associated with a specific TRP (identified by the TRP ID). Additionally, PRS resources in a PRS resource set have the same periodicity, common silence mode configuration, and the same repetition factor (such as “PRS-ResourceRepetitionFactor”) across time slots. Periodicity is the time from the first repetition of the first PRS resource in the first PRS instance to the same first repetition of the same first PRS resource in the next PRS instance. Periodicity can have a length selected from: 2^µ The time slots are {4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240}, where µ = 0, 1, 2, 3. The repetition factor can have a length selected from {1, 2, 4, 6, 8, 16, 32} time slots.

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

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

[0120] A “positioning frequency layer” (also simply “frequency layer”) is a collection of one or more PRS resource sets with identical values ​​for certain parameters across one or more TRPs. Specifically, the collection of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning that all parameter sets supported for the Physical Downlink Shared Channel (PDSCH) are also supported by the PRS), the same point A, the same downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The point A parameter takes the value of the parameter “ARFCN-ValueNR” (where “ARFCN” stands for “Absolute Radio Channel Number”) and is an identifier / code specifying a pair of physical radio channels used for transmission and reception. The downlink PRS bandwidth can have a granularity of four PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs. Currently, up to four frequency layers have been defined, and up to two PRS resource sets can be configured per frequency layer per TRP.

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

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

[0123] On the one hand, Figure 4 The reference signal carried on the RE marked "R" can be the SRS. The SRS transmitted by the UE can be used by the base station to obtain the Channel State Information (CSI) used to transmit the UE. The CSI describes how the RF signal propagates from the UE to the base station and represents the combined effects of scattering, attenuation, and power decay with distance. The system uses the SRS for resource scheduling, link adaptation, massive MIMO, beam management, etc.

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

[0125] The transmission of SRS resources within a given PRB has a specific comb size (also known as "comb density"). The comb size "N" represents the subcarrier spacing (or frequency / tone spacing) within each symbol of the SRS resource configuration. Specifically, for a comb size "N", SRS is transmitted in every Nth subcarrier of a symbol within the PRB. For example, for comb size -4, for each symbol of the SRS resource configuration, the RE corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) is used to transmit the SRS of the SRS resource. Figure 4 In the example, the illustrated SRS is comb tooth-4 spanning four symbols. That is, the position of the shaded SRS RE indicates the SRS resource configuration of comb tooth-4.

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

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

[0128] Several enhancements to the previously defined SRS may be available for “SRS for Positioning” (also known as “UL-PRS”), such as new interleaving patterns within SRS resources (other than single symbol / comb-2), new comb types for SRS, new sequences of SRS, a larger set of SRS resources per component carrier, and a larger number of SRS resources per component carrier. Furthermore, the parameters “SpatialRelationInfo” and “PathLossReference” are configured based on downlink reference signals or SSBs from adjacent TRPs. Further, an SRS resource can be transmitted outside the active BWP, and an SRS resource can span multiple component carriers. Moreover, SRS can be configured in RRC connected state and transmitted only within the active BWP. Additionally, there may be no frequency hopping, no repetition factor, a single antenna port, and new SRS lengths (e.g., 8 and 12 symbols). Open-loop power control may also exist, but closed-loop power control is not possible, and comb-8 (i.e., SRS transmitted every eighth subcarrier in the same symbol) can be used. Finally, the UE can transmit from multiple SRS resources using the same transmit beam for UL-AoA. These features can be configured via higher-layer RRC signaling (and potentially triggered or activated via MAC control elements (MAC-CE) or downlink control information (DCI)).

[0129] Following the random access procedure, the UE is in the RRC connected state. The RRC protocol is used on the air interface between the UE and the base station. The main functions of the RRC protocol include connection establishment and release, broadcasting system information, radio bearer establishment, reconfiguration, release, RRC connection mobility procedures, paging notification and release, and outer loop power control. In LTE, the UE can be in one of two RRC states (connected or idle), but in NR, the UE can be in one of three RRC states (connected, idle, or inactive). Different RRC states have different radio resources associated with them, which the UE can use when in a given state. Note that, as above, the different RRC states are usually written in uppercase; however, this is not mandatory, and these states can also be written in lowercase.

[0130] Figure 5Figure 500 illustrates the different RRC states (also referred to as RRC modes) available in the NR according to various aspects of this disclosure. When the UE powers on, it is initially in the RRC disconnect / idle state 510. After a random access procedure, the UE moves to the RRC connected state 520. If there is no activity at the UE for a short period of time, the UE can suspend its session by moving to the RRC inactive state 530. The UE can resume its session by performing a random access procedure to transition back to the RRC connected state 520. Therefore, regardless of whether the UE is in the RRC idle state 510 or the RRC inactive state 530, the UE needs to perform a random access procedure to transition to the RRC connected state 520.

[0131] Operations performed in RRC Idle State 510 include Public Land Mobile Network (PLMN) selection, broadcasting of system information, cell reselection mobility, paging for mobile station called data (initiated and managed by 5GC), and Discontinuous Reception (DRX) for core network paging (configured by Non-Access Stratum (NAS)). Operations performed in RRC Connected State 520 include 5GC (e.g., 5GC 260) and NG-RAN (e.g., NG-RAN 220) connection establishment (both control plane and user plane), UE context storage at NG-RAN and UE, NG-RAN knowledge of the UE's cell, unicast data transfer to / from the UE, and network-controlled mobility. Operations performed in RRC inactive state 530 include broadcasting system information, cell reselection for mobility, paging (initiated by NG-RAN), RAN-based notification area (RNA) management (performed by NG-RAN), DRX for RAN paging (configured by NG-RAN), 5GC and NG-RAN connection establishment for the UE (both control plane and user plane), storage of UE context in NG-RAN and the UE, and NG-RAN knowledge of the RNA to which the UE belongs.

[0132] NR supports various cellular network-based positioning technologies, including downlink-based positioning methods, uplink-based positioning methods, and downlink-and-uplink-based positioning methods. Downlink-based positioning methods include: Observed Time Difference of Arrival (OTDOA) in LTE, Downlink Time Difference of Arrival (DL-TDOA) in NR, and Downlink Angle of Departure (DL-AoD) in NR. During OTDOA or DL-TDOA positioning, the UE measures the difference between the times of arrival (ToA) of reference signals (e.g., positioning reference signals (PRS)) received from paired base stations (referred to as Reference Signal Time Difference (RSTD) or Time Difference of Arrival (TDOA) measurements) and reports these differences to the 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 locations of the base stations involved and the RSTD measurements, the positioning entity (e.g., a UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the UE's location.

[0133] For DL-AoD positioning, the positioning entity uses measurement reports from the UE regarding the received signal strength of multiple downlink transmitted beams to determine the angle between the UE and the transmitting base station. The positioning entity can then estimate the UE's location based on the determined angle and the known location of the transmitting base station.

[0134] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle of arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but is based on uplink reference signals (e.g., sounding reference signals (SRS)) transmitted by the UE to multiple base stations. Specifically, the UE transmits 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 received-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 the TDOA to estimate the UE's location.

[0135] 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 measurement and the angle of the receive beam 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.

[0136] Downlink and uplink-based positioning methods include enhanced cell ID (eCID) positioning and multiple round-trip time (RTT) positioning (also known as "multi-cell RTT" and "multi-RTT"). During RTT, a first entity (e.g., a base station or a UE) sends a first RTT-related signal (e.g., PRS or SRS) to a second entity (e.g., a UE or a base station), which then sends a second RTT-related signal (e.g., SRS or PRS) back to the first entity. Each entity measures the time difference between the time of arrival (ToA) of the received RTT-related signal and the time of transmission of the transmitted RTT-related signal. This time difference is called the receive-to-transmit (Rx-Tx) time difference. The Rx-Tx time difference measurement can be performed or adjusted to include only the time difference between the nearest time slot boundary of the received signal and the transmitted signal. The two entities can then transmit their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round-trip time (RTT) between the two entities based on these two Rx-Tx time difference measurements (e.g., calculated as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity can transmit its Rx-Tx time difference measurement to another entity, which then calculates the RTT. The distance between the two entities can be determined based on the RTT and a known signal speed (e.g., the speed of light). For multi-RTT positioning, a first entity (e.g., a UE or base station) performs an RTT positioning process with multiple second entities (e.g., multiple base stations or UEs) such that the location of the first entity can be determined based on the distance to the second entities and the known location of the second entities (e.g., using multipoint positioning). RTT and multi-RTT methods can be combined with other positioning technologies (such as UL-AoA and DL-AoD) to improve location accuracy.

[0137] The eCID positioning method is based on Radio Resource Management (RRM) measurements. In eCID, the UE reports the serving cell ID, timing advance (TA), identifiers of detected neighboring base stations, estimated timing, and signal strength. The UE's location is then estimated based on this information and the known locations of the base stations.

[0138] To assist in positioning operations, a location server (e.g., location server 230, LMF 270, SLP 272) may provide auxiliary data to the UE. For example, auxiliary data may include: the identifier of the base station (or the cell / TRP of the base station) from which the reference signal is measured, reference signal configuration parameters (e.g., including the number of consecutive time slots of the PRS, the periodicity of consecutive time slots of the PRS, silence sequences, frequency hopping sequences, reference signal identifier, reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, auxiliary data may be derived directly from the base station itself (e.g., in periodically broadcast overhead messages, etc.). In some cases, the UE may be able to detect neighboring network nodes without using auxiliary data.

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

[0140] Location estimates can be referred to by other names, such as location estimation, location, positioning, fixed location, etc. Location estimates can be geodesic and include coordinates (e.g., latitude, longitude, and possible elevation), or they can be municipal and include street addresses, postal addresses, or some other verbal description of the location. Location estimates can be further defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possible elevation). Location estimates can include expected errors or uncertainties (e.g., by including the area or volume that the location is expected to include with a specified or default confidence level).

[0141] In some designs, multiple instances of PRS auxiliary data (AD) can be supported in the LPP. For example, one or more NR-DL-PRS-AssistanceData-r16 elements can be provided in one or more LPP auxiliary data messages. The area ID corresponds to the set of cells on which the UE can use the associated AD (e.g., when camped / connected to the corresponding cell in that set of cells). In some designs, the cell IDs associated with the area ID can be explicitly listed in the LPP along with the auxiliary data. This list can be provided for each instance of auxiliary data. In some designs, if the PRS AD is associated with an area ID, the UE does not need to report the area ID along with the PRS measurement to the LMF.

[0142] In some designs, the area ID can be broadcast in the system information (e.g., this has no specification impact if the area ID is limited to something already broadcast in the system information). If the UE receives auxiliary data for a PRS-ID and cell ID combination for which the UE has already stored auxiliary data, the UE rewrites the stored auxiliary data. If the UE receives auxiliary data for a PRS-ID and cell ID combination for which the UE has not yet stored auxiliary data, the UE maintains its stored auxiliary data for other PRS-ID and cell ID combinations. In some designs, the UE can report its UE capability for the number of PRS-ID and cell ID combinations for which the UE can store AD. In some designs (e.g., 3GPP Release 17), validity timers are not used for AD.

[0143] Figure 6 An example of a region ID arrangement 600 according to various aspects of this disclosure is illustrated. In one aspect, the region ID arrangement 600 may be associated with location estimation based on eCID.

[0144] refer to Figure 6 The area ID arrangement 600 includes area IDs #1 to #6. Figure 6 In this context, UE 302 is depicted moving along path 610 through some of the cells associated with area IDs #1 to #6. Each area ID from #1 to #6 is associated with a corresponding group of radio nodes (e.g., TRPs or cells), as follows:

[0145]

[0146] Table 1: Relationship between Region ID and TRP

[0147] As noted above, DL-PRS auxiliary data (with associated validity criteria) can be provided to the UE (before or during an ongoing LPP positioning session) for subsequent use in potential positioning measurements at future times (e.g., for MT-LR of delay). Pre-configured DL-PRS auxiliary data can include multiple instances, each applicable to a different area within the network. Each DL-PRS auxiliary data instance can be associated with an area ID. The area ID is associated with a list of TRPs (or cells) where the UE can camp / connect. The applicable area ID at the UE's location is selected based on the cell where the UE camps or is radio-coupled. If the UE camps or is radio-coupled to one of the cells indicated in the list of cells associated with the area ID, the instance of auxiliary data is valid / selected.

[0148] On one hand, Low Power High Accuracy Positioning (LPHAP) can include various objectives. One example LPHAP objective is to extend the eDRX cycle time to over 10.24s in the RRC_INACTIVE state to meet LPHAP battery life requirements. Another example LPHAP objective for UL and DL+UL positioning of UEs in the RRC_INACTIVE state is to specify SRS configuration enhancements based on the SRS positioning validity area to avoid frequent RRC connection establishment due to SRS (re)configuration. Another example LPHAP objective is to specify solutions for DL ​​PRS measurements for UEs in the RRC_IDLE state and for reporting measurements in the RRC_CONNECTED state. Another example LPHAP objective is to specify solutions for alignment between eDRX and PRS configurations. Yet another example LPHAP objective is to specify corresponding new core requirements, and to identify and specify the impact on existing RAN4 specifications, including RRM measurements and procedures.

[0149] On the one hand, a subset of SRS configuration parameters can be shared across multiple cells. Therefore, in some designs, it is feasible to at least partially pre-configure SRS across multiple cells, for example:

[0150]

[0151] Table 1

[0152] In some designs, parameters such as SRS (SRS-P) configuration identifiers for positioning, cell identifier lists (area IDs), and / or SRS-P parameters valid for multiple cells indicated by the area IDs can be pre-configured. In some designs, parameters such as SRS-P parameters valid for the current serving cell (a single serving cell) can be provided to the UE via an activation message.

[0153] In some designs, timing advance (TA) verification and time extension can be defined for SRS. On one hand, an SRS-P validity area-specific TA timer (e.g., with a large value) can be defined for a UE in the RRC_INACTIVE state. On one hand, the UE starts / restarts the area-specific TA timer when it receives a TA command. On one hand, the UE stops SRS transmission when the area-specific TA timer expires. On one hand, the UE stops the area-specific TA timer when it reselects to a cell outside the SRS validity area. On one hand, other stop / restart conditions can be defined. In some designs, TA can be autonomously adjusted by the UE in the RRC_INACTIVE state. On one hand, determining the UL timing for transmitting SRS-P within the SRS-P validity area by the UE in the RRC_INACTIVE state may include: setting the DL reference timing to the DL timing of the currently camped cell, and by default, using TA from the last serving cell for the UE to maintain. On one hand, the UE can adjust its UL timing based on changes in the DL reference timing. If configured by the network, the UE can autonomously adjust TA when performing cell reselection, depending on its capabilities.

[0154] NR Enhanced Cell ID (NR eCID) positioning refers to a technique that uses additional UE measurements and / or NR radio resources, as well as other measurements, to improve UE location estimation. Although NR eCID positioning can utilize some of the same measurements as the measurement control system in the RRC protocol, it is generally not expected that the UE will perform additional measurements for the sole purpose of positioning; that is, the positioning process does not provide measurement configuration or measurement control messages, and the UE reports its available measurements rather than being asked to take additional measurement actions.

[0155] NR Enhanced Cell ID (NR eCID) positioning refers to a technique that uses UE and / or NR radio resource-related measurements to improve UE location estimation. In some designs, for the NR eCID positioning method, the UE only reports its available measurements without being required to take additional measurement actions. Therefore, the measurement gap request procedure is not applicable to the NR eCID positioning method.

[0156] In some designs, NR eCID measurements may include UE measurements such as SS Reference Signal Received Power (SS-RSRP), SS Reference Signal Received Quality (SS-RSRQ), CSI Reference Signal Received Power (CSI-RSRP), and CSI Reference Signal Received Quality (CSI-RSRQ). In some designs, these UE measurements may be aggregated at the cell level or measured per SSB or CSI-RS resource. Various techniques can use these measurements to estimate the UE's location.

[0157] The IE ECID-SignalMeasurementInformation is used by the target device to provide various UE measurements to the location server, and can be configured as follows:

[0158]

[0159]

[0160]

[0161] Table 2: Description of Optional Fields in ECID-SignalMeasurementInformation

[0162]

[0163] Table 3: Description of ECID-SignalMeasurementInformation Field

[0164] In some designs, the UE Rx-Tx time difference is defined as T UE-RX -T UE-TX T UE-RX T is the UE reception timing of downlink radio frame #i from the serving cell, which is defined in time by the first detection path. UE-TX This refers to the UE transmission timing of uplink radio frame #i. The reference point for UE Rx-Tx time difference measurement should be the UE antenna connector. In some designs, for HD-FDD UEs, if the UE does not receive any DL transmissions in radio frame #i, the UE should compensate for radio frame #i and the transmissions it did receive in it for Tx. UE-RX The estimated difference in the timing of receiving radio frames transmitted by DL.

[0165] As noted above, NR eCID-based location estimation is one of the positioning technologies supported by 5G. Along with many other parameters, TA (Target Aspect) is one of the parameters that the UE can use for eCID-based location estimation. In some designs, reporting TA to the location estimation entity is optional in both UE-based eCID location estimation and UE-assisted eCID location estimation. However, this can improve positioning accuracy if TA is known to the location estimation entity. For eCID-based location estimation where the UE is in the RRC_INACTIVE state, the UE should generally not be transitioned to the RRC_CONNECTED state to obtain TA. For eCID-based location estimation, the current system does not specify how long TA (e.g., from a previous RRC_CONNECTED state) remains valid.

[0166] Various aspects of this disclosure relate to providing a timing advance (TA) validity timer for eCID-based location estimation. In one aspect, the TA validity timer can be used to determine whether an associated TA is valid for an eCID-based location estimation session. If the TA is valid, it can be reported to the location estimation entity and then used for eCID-based location estimation. Such aspects can provide various technical advantages, such as improved location accuracy for eCID-based location estimation.

[0167] Figure 7 An exemplary process 700 of communication according to one aspect of this disclosure is illustrated. Figure 7 The process 700 is performed by the UE (such as UE 302).

[0168] refer to Figure 7 At 710, UE 302 (e.g., receiver 312 or 322, etc.) receives a first timing advance associated with the first radio network component.

[0169] refer to Figure 7 At 720, UE 302 (e.g., processor 342, TA validity timer component 348, etc.) determines a timing advance validity timer for location estimation based on enhanced cell identity (eCID).

[0170] refer to Figure 7 At 730, UE 302 (e.g., processor 342, TA validity timer component 348, etc.) determines that the first timing advance is valid based on the timing advance validity timer.

[0171] refer to Figure 7At 740, UE 302 (e.g., receiver 312 or 322, transmitter 314 or 324, etc.) responds to determining that the first timing advance is valid by sending an eCID measurement report to the positioning estimation entity, including eCID measurement information and a first indication of the first timing advance. In some designs, the first indication may be configured as a bit field having a value indexed to a TA value in a pre-configured or predefined table known to UE 302 and the positioning estimation entity. In a specific example, the first indication may be configured as a 6-bit TA command field mapped to a TA table having up to 64 TA values ​​ranging from -16.3 microseconds to +16.3 microseconds. In some designs, the positioning estimation entity may correspond to a network component (e.g., an LMF integrated at gNB / BS 304 or O-RAN component, or a remote location server such as network entity 306, etc.). In other designs, the location estimation entity may correspond to another UE (e.g., a sidelink anchored UE or a sidelink server UE) or to the target UE itself (e.g., for UE-based location estimation, in which case any Rx / Tx operation between the UE and the location estimation entity may correspond to information transfer between different logical components of the UE via a data bus).

[0172] Figure 8 An exemplary process 800 of communication according to one aspect of this disclosure is illustrated. Figure 8 The process 800 is performed by a location estimation entity. In some designs, this location estimation entity may correspond to a network component (e.g., an LMF integrated in a gNB / BS 304 or O-RAN component, or a remote location server such as network entity 306). In other designs, the location estimation entity may correspond to another UE (e.g., a sidelink anchored UE or a sidelink server UE) or to the target UE itself (e.g., for UE-based location estimation, in which case any Rx / Tx operation between the UE and the location estimation entity may correspond to information transfer between different logical components of the UE via a data bus, etc.). On the other hand, at the location estimation entity... Figure 8 The process 800 can be used with and at wireless measurement entities Figure 7 The process corresponds to the parallel execution of 700 processes.

[0173] refer to Figure 8At 810, the location estimation entity (e.g., receiver 312 or 322 or 352 or 362, network transceiver 380 or 390, data bus 308, etc.) receives an enhanced cell identity (eCID) measurement report from the user equipment (UE). This eCID measurement report includes eCID measurement information and a first indication of a first timing advance associated with a first radio network component, which is associated with a timing advance validity timer for location estimation based on the enhanced cell identity eCID. In some designs, the first indication may be configured as a bit field with a value indexed to a TA value in a pre-configured or predefined table known to the UE 302 and the location estimation entity. In one specific example, the first indication may be configured as a 6-bit TA command field mapped to a TA table with up to 64 TA values ​​ranging from -16.3 microseconds to +16.3 microseconds.

[0174] refer to Figure 8 At 820, the location estimation entity (e.g., processor 342 or 384 or 394, TA validity timer component 348 or 388 or 398, etc.) determines the UE's location estimate based on eCID measurement information and a first timing advance.

[0175] refer to Figures 7 to 8 In some designs, the timing advance validity timer is defined in a fixed time unit. In some designs, the first timing advance is determined independently at the UE, or the first timing advance is indicated to the UE via Radio Resource Control (RRC) signaling, or the first timing advance is indicated to the UE via auxiliary data, or the first timing advance is set to be equal to the second timing advance associated with the transmission of the Sound Reference Signal (SRS) in the RRC_INACTIVE state.

[0176] refer to Figures 7 to 8 In some designs, the timing advance validity timer is based on one or more Reference Signal Received Power (RSRP) measurements associated with the first radio network component. In one aspect, the timing advance validity timer is based on an RSRP change threshold. In another aspect, the RSRP change threshold is determined independently at the UE, or the RSRP change threshold is indicated to the UE via Radio Resource Control (RRC) signaling, or the RSRP change threshold is indicated to the UE via auxiliary data, or the RSRP change threshold is set equal to a second timing advance associated with the transmission of a Sound Reference Signal (SRS) in the RRC_INACTIVE state.

[0177] refer to Figures 7 to 8In some designs, the eCID measurement report also includes one or more signal metrics associated with a first time of receiving the first timing advance. In one aspect, these one or more signal metrics are included in the eCID measurement report based on the first time of receiving the first timing advance and a second time associated with the transmission of the eCID measurement report being higher than a threshold. In another aspect, the threshold is determined independently at the UE, or the threshold is indicated to the UE via Radio Resource Control (RRC) signaling, or the threshold is indicated to the UE via auxiliary data, or the threshold is set equal to the second timing advance associated with the transmission of the Sound Reference Signal (SRS) in the RRC_INACTIVE state.

[0178] refer to Figures 7 to 8 In some designs, the UE also receives a second timing advance associated with a second radio network component and determines whether the second timing advance is valid based on a timing advance validity timer. In one aspect, in response to determining that the second timing advance is valid, the eCID measurement report also includes a second indication of the second timing advance.

[0179] refer to Figures 7 to 8 In some designs, the first timing advance is static and specific to the first wireless network component, or the first timing advance is static and specific to each wireless network component in a group of wireless network components that includes the first wireless network component.

[0180] refer to Figures 7 to 8 In some designs, the first timing advance is dynamic and specific to the first wireless network component, or the first timing advance is dynamic and specific to each wireless network component in a group of wireless network components that includes the first wireless network component.

[0181] refer to Figures 7 to 8 In some designs, the first timing advance is associated with a validity region, outside of which the first timing advance is invalid.

[0182] refer to Figures 7 to 8 In some designs, one or more parameters associated with the first timing advance are set to be equal to one or more corresponding parameters associated with the transmission of the probe reference signal (SRS) in the RRC_INACTIVE state.

[0183] refer to Figures 7 to 8 In some designs, the location estimation entity corresponds to the UE, another UE, a first radio network component, another radio network component, or a location server.

[0184] refer to Figures 7 to 8In some designs, eCID measurement reports include indications of timing advance validity timers, either pre-configured or pre-defined. On one hand, knowledge of the validity of eCID measurement reports relative to specific eCID timing advance validity timers helps ensure that valid positioning measurements are used for positioning estimation, which contributes to improved positioning accuracy.

[0185] refer to Figures 7 to 8 In one specific example, the timing advance validity timer can be configured via a timer-based solution. For example, the UE can use a TA value of up to T seconds. In the first example, the timer (T) may depend on the specific UE implementation. In the second example, the timer (T) can be configured via RRC configuration release. In the third example, the timer (T) can be part of AD or IE ECID-ProvideLocationInformation. In the fourth example, the timer (T) can be defined as the same as the corresponding timer used for SRS TA in 3GPP Release 17 and / or Release 18. In one specific example, the timer (T) can be set to 10.24 seconds. In another specific example, a longer value for the timer (T) (e.g., one minute or more) can be used for various purposes (e.g., reducing power consumption at the UE in scenarios where the UE is stationary and periodically performs eCID-based location estimation). In one aspect, the UE and / or the network can configure a higher value for the timer (T).

[0186] refer to Figures 7 to 8 In one specific example, the timing advance validity timer can be configured via a solution based on RSRP changes. For example, if the RSRP does not change the XdB threshold, the UE can use the TA value. In one aspect, the UE stores the RSRP value when it receives the TA as RSRP_ref. Then, if RSRP_ref - RSRP ≤ X, the UE will use the TA. In the first example, the threshold (X) may depend on the specific UE implementation. In the second example, the threshold (X) can be configured via RRC configuration release. In the third example, the threshold (X) can be part of AD or IE ECID-ProvideLocationInformation. In the fourth example, the threshold (X) can be defined as the same as the corresponding timer used for SRS TA in 3GPP Release 17 and / or Release 18. In one specific example, the value of X can be {1, 2, 3, 4, …N}. 5dB. In this case, the increment step for the X value is 5dB, but in other aspects of this disclosure, the step size can be higher or lower. In another specific example, the value of X can be set directly without using a step size.

[0187] refer to Figures 7 to 8 In one specific example, the timing advance validity timer can be configured via a TA with a snapshot-based solution. For example, the UE can store the TA value and the corresponding signal metric when it receives the TA. These signal metrics can be characterized as TA snapshots. If the difference between the TA snapshot and the reporting time is greater than a threshold (Y), the UE will report the eCID measurement along with the TA snapshot. In the first example, the threshold (Y) may depend on the specific UE implementation. In the second example, the threshold (Y) can be configured via RRC configuration release. In the third example, the threshold (Y) can be part of AD or IE ECID-ProvideLocationInformation. In the fourth example, the threshold (Y) can be defined as the same as the corresponding timer used for SRS TA in 3GPP Release 17 and / or Release 18. In one specific example, the threshold (Y) can be set to 10.24 seconds. In another specific example, a longer value of the threshold (Y) (e.g., one minute or more) can be used for various purposes (e.g., reducing power consumption at the UE in scenarios where the UE is stationary and periodically performs eCID-based location estimation). On the one hand, the UE and / or network can configure a higher value for the threshold (Y).

[0188] refer to Figures 7 to 8 In a specific example, based on the configuration of a timing advance validity timer, the UE can obtain TAs from multiple cells. On one hand, if the corresponding TA is valid, the UE can send TAs from multiple cells.

[0189] refer to Figures 7 to 8 In a specific example, the timing advance validity timer can be defined in a region-specific manner. On one hand, a static timer (e.g., predefined or RRC-configured) is used for each cell. On another hand, a static timer (e.g., predefined or RRC-configured) is used for multiple cells. On another hand, a dynamic timer (e.g., predefined or RRC-configured) is used for each cell. On yet another hand, a dynamic timer (e.g., predefined or RRC-configured) is used for multiple cells.

[0190] refer to Figures 7 to 8 In specific examples, eCID-specific validity regions can be defined. In one aspect, such eCID-specific validity regions can be defined similarly to the SRS validity regions defined with respect to 3GPP Releases 17 and 18.

[0191] refer to Figures 7 to 8In a specific example, the timing advance validity timer can be configured according to the SRS RRC_INACTIVE TA framework. For example, the UE can support SRS-P in the RRC_INACTIVE state. The UE can be configured via the network using various parameters to support SRS transmission in the RRC_INACTIVE state (e.g., TA validity, SRS validity area, RSRP threshold, etc.). In one aspect, these SRS-related parameters can be reused for eCID-based positioning in combination with any of the aspects described above.

[0192] As can be seen in the detailed description above, different features are grouped together in the examples. This manner of disclosure should not be construed as an intention to have more features than those explicitly mentioned in each clause. Rather, the various aspects of this disclosure may include fewer features than those in the individual example clauses disclosed. Therefore, the following clauses should be regarded accordingly as incorporated into the description, where each clause may serve as a separate example. Although each dependent clause may refer in the clause to a specific combination with one of the other clauses, the aspect of that dependent clause is not limited to that specific combination. It should be understood that other example clauses may also include combinations of aspects of a dependent clause with the subject matter of any other dependent or independent clause, or combinations of any feature with other dependent and independent clauses. The various aspects disclosed herein explicitly include these combinations unless explicitly stated or readily inferred that a particular combination is not intended for use (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). Furthermore, it is contemplated that aspects of a clause may be included in any other independent clause, even if that clause does not directly depend on the independent clause.

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

[0194] Clause 1. A method of operating a user equipment (UE), the method comprising: receiving a first timing advance associated with a first radio network component; determining a timing advance validity timer for positioning estimation based on enhanced cell identity (eCID); determining, based on the timing advance validity timer, that the first timing advance is valid; and, in response to determining that the first timing advance is valid, sending an eCID measurement report to a positioning estimation entity including eCID measurement information and a first indication of the first timing advance.

[0195] Clause 2. The method described in Clause 1, wherein the timing advance validity timer is defined in a fixed time unit.

[0196] Clause 3. The method according to Clause 2, wherein the first timing advance is determined independently at the UE, or wherein the first timing advance is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the first timing advance is indicated to the UE via auxiliary data, or wherein the first timing advance is set to be equal to the second timing advance associated with the transmission of a Sound Reference Signal (SRS) in the RRC_INACTIVE state.

[0197] Clause 4. The method according to any one of Clauses 1 to 3, wherein the timing advance validity timer is based on one or more reference signal received power (RSRP) measurements associated with the first wireless network component.

[0198] Clause 5. The method according to Clause 4, wherein the timing advance validity timer is based on an RSRP change threshold.

[0199] Clause 6. The method according to Clause 5, wherein the RSRP change threshold is determined independently at the UE, or wherein the RSRP change threshold is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the RSRP change threshold is indicated to the UE via auxiliary data, or wherein the RSRP change threshold is set to be equal to a second timing advance associated with the transmission of a probe reference signal (SRS) in the RRC_INACTIVE state.

[0200] Clause 7. The method according to any one of Clauses 1 to 6, wherein the eCID measurement report further includes one or more signal metrics associated with the first time the first timing advance was received.

[0201] Clause 8. The method according to Clause 7, wherein the one or more signal metrics are included in the eCID measurement report based on the first time the first timing advance was received and the second time associated with the transmission of the eCID measurement report being higher than a threshold.

[0202] Clause 9. The method according to Clause 8, wherein the threshold is determined independently at the UE, or wherein the threshold is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the threshold is indicated to the UE via auxiliary data, or wherein the threshold is set to be equal to a second timing advance associated with the transmission of a probe reference signal (SRS) in the RRC_INACTIVE state.

[0203] Clause 10. The method according to any one of Clauses 1 to 9, the method further comprising: receiving a second timing advance associated with a second wireless network component; determining that the second timing advance is valid based on the timing advance validity timer, wherein in response to determining that the second timing advance is valid, the eCID measurement report further comprises a second indication of the second timing advance.

[0204] Clause 11. The method according to any one of Clauses 1 to 10, wherein the first timing advance is static and specific to the first wireless network component, or wherein the first timing advance is static and specific to each of the wireless network components in the group of wireless network components including the first wireless network component.

[0205] Clause 12. The method according to any one of Clauses 1 to 11, wherein the first timing advance is dynamic and specific to the first wireless network component, or wherein the first timing advance is dynamic and specific to each of the wireless network components in the group of wireless network components including the first wireless network component.

[0206] Clause 13. The method according to any one of Clauses 1 to 12, wherein the first timing advance is associated with a validity region, outside of which the first timing advance is invalid.

[0207] Clause 14. The method according to any one of Clauses 1 to 13, wherein one or more parameters associated with the first timing advance are set equal to one or more corresponding parameters associated with the transmission of the probe reference signal (SRS) in the RRC_INACTIVE state.

[0208] Clause 15. The method according to any one of Clauses 1 to 14, wherein the location estimation entity corresponds to the UE, another UE, the first wireless network component, another wireless network component, or a location server.

[0209] Clause 16. A method for operating a location estimation entity, the method comprising: receiving an enhanced cell identity (eCID) measurement report from a user equipment (UE), the eCID measurement report including eCID measurement information and a first indication of a first timing advance associated with a first radio network component, the first timing advance being associated with a timing advance validity timer for location estimation based on the enhanced cell identity eCID; and determining a location estimate of the UE based on the eCID measurement information and the first timing advance.

[0210] Clause 17. The method according to Clause 16, wherein the eCID measurement report includes an indication of the timing advance validity timer, or wherein the timing advance validity timer is pre-configured, or wherein the timing advance validity timer is predefined.

[0211] Clause 18. The method according to any one of Clauses 16 to 17, wherein the timing advance validity timer is defined in a fixed time unit.

[0212] Clause 19. The method according to Clause 18, wherein the first timing advance is determined independently at the UE, or wherein the first timing advance is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the first timing advance is indicated to the UE via auxiliary data, or wherein the first timing advance is set to be equal to the second timing advance associated with the transmission of a Sound Reference Signal (SRS) in the RRC_INACTIVE state.

[0213] Clause 20. The method according to any one of Clauses 16 to 19, wherein the eCID measurement report further includes one or more signal metrics associated with the first time the first timing advance was received.

[0214] Clause 21. The method according to Clause 20, wherein the one or more signal metrics are included in the eCID measurement report based on the first time the first timing advance was received and the second time associated with the transmission of the eCID measurement report being higher than a threshold.

[0215] Clause 22. The method according to Clause 21, wherein the threshold is determined independently at the UE, or wherein the threshold is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the threshold is indicated to the UE via auxiliary data, or wherein the threshold is set to be equal to a second timing advance associated with the transmission of a probe reference signal (SRS) in the RRC_INACTIVE state.

[0216] Clause 23. The method according to any one of Clauses 16 to 22, wherein the eCID measurement report further includes a second indication of a second timing advance associated with the second wireless network component.

[0217] Clause 24. The method according to any one of Clauses 16 to 23, wherein the first timing advance is static and specific to the first wireless network component, or wherein the first timing advance is static and specific to each of the wireless network components in a group of wireless network components including the first wireless network component.

[0218] Clause 25. The method according to any one of Clauses 16 to 24, wherein the first timing advance is dynamic and specific to the first wireless network component, or wherein the first timing advance is dynamic and specific to each of the wireless network components in the group of wireless network components including the first wireless network component.

[0219] Clause 26. The method according to any one of Clauses 16 to 25, wherein the first timing advance is associated with a validity region, outside of which the first timing advance is invalid.

[0220] Clause 27. The method according to any one of Clauses 16 to 26, wherein one or more parameters associated with the first timing advance are set equal to one or more corresponding parameters associated with the transmission of the probe reference signal (SRS) in the RRC_INACTIVE state.

[0221] Clause 28. The method according to any one of Clauses 16 to 27, wherein the location estimation entity corresponds to the UE, another UE, the first wireless network component, another wireless network component, or a location server.

[0222] Clause 29. A user equipment (UE) comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to: receive, via the one or more transceivers, a first timing advance associated with a first radio network component; determine a timing advance validity timer for location estimation based on enhanced cell identity (eCID); determine, based on the timing advance validity timer, that the first timing advance is valid; and, in response to determining that the first timing advance is valid, transmit an eCID measurement report, including eCID measurement information and a first indication of the first timing advance, to a location estimation entity via the one or more transceivers.

[0223] Clause 30. The UE as described in Clause 29, wherein the timing advance validity timer is defined in a fixed time unit.

[0224] Clause 31. The UE according to Clause 30, wherein the first timing advance is determined independently at the UE, or wherein the first timing advance is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the first timing advance is indicated to the UE via auxiliary data, or wherein the first timing advance is set to be equal to the second timing advance associated with the transmission of a Sounding Reference Signal (SRS) in the RRC_INACTIVE state.

[0225] Clause 32. The UE according to any one of Clauses 29 to 31, wherein the timing advance validity timer is based on one or more reference signal received power (RSRP) measurements associated with the first radio network component.

[0226] Clause 33. The UE as described in Clause 32, wherein the timing advance validity timer is based on an RSRP change threshold.

[0227] Clause 34. The UE as described in Clause 33, wherein the RSRP change threshold is determined independently at the UE, or wherein the RSRP change threshold is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the RSRP change threshold is indicated to the UE via auxiliary data, or wherein the RSRP change threshold is set to be equal to a second timing advance associated with the transmission of a Sounding Reference Signal (SRS) in the RRC_INACTIVE state.

[0228] Clause 35. The UE pursuant to any one of Clauses 29 to 34, wherein the eCID measurement report further includes one or more signal metrics associated with the first time the first timing advance was received.

[0229] Clause 36. The UE as described in Clause 35, wherein one or more signal metrics are included in the eCID measurement report based on the first time the first timing advance was received and the second time associated with the transmission of the eCID measurement report being higher than a threshold.

[0230] Clause 37. The UE as described in Clause 36, wherein the threshold is determined independently at the UE, or wherein the threshold is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the threshold is indicated to the UE via auxiliary data, or wherein the threshold is set to be equal to a second timing advance associated with the transmission of a Sounding Reference Signal (SRS) in the RRC_INACTIVE state.

[0231] Clause 38. The UE according to any one of Clauses 29 to 37, wherein the one or more processors are individually or in combination further configured to: receive a second timing advance associated with a second radio network component via the one or more transceivers; determine that the second timing advance is valid based on the timing advance validity timer, wherein in response to determining that the second timing advance is valid, the eCID measurement report further includes a second indication of the second timing advance.

[0232] Clause 39. The UE pursuant to any one of Clauses 29 to 38, wherein the first timing advance is static and specific to the first radio network component, or wherein the first timing advance is static and specific to each of the radio network components in the group of radio network components including the first radio network component.

[0233] Clause 40. The UE pursuant to any one of Clauses 29 to 39, wherein the first timing advance is dynamic and specific to the first radio network component, or wherein the first timing advance is dynamic and specific to each of the radio network components in the group of radio network components including the first radio network component.

[0234] Clause 41. The UE pursuant to any one of Clauses 29 to 40, wherein the first timing advance is associated with a validity region, and outside the validity region, the first timing advance is invalid.

[0235] Clause 42. The UE according to any one of Clauses 29 to 41, wherein one or more parameters associated with the first timing advance are set equal to one or more corresponding parameters associated with the transmission of the probe reference signal (SRS) in the RRC_INACTIVE state.

[0236] Clause 43. The UE pursuant to any one of Clauses 29 to 42, wherein the location estimation entity corresponds to the UE, another UE, the first radio network component, another radio network component, or a location server.

[0237] Clause 44. A location estimation entity comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors being individually or in combination configured to: receive an enhanced cell identity (eCID) measurement report from a user equipment (UE) via the one or more transceivers, the eCID measurement report including eCID measurement information and a first indication of a first timing advance associated with a first radio network component, the first timing advance being associated with a timing advance validity timer for location estimation based on the enhanced cell identity eCID; and determine a location estimate of the UE based on the eCID measurement information and the first timing advance.

[0238] Clause 45. The location estimation entity as described in Clause 44, wherein the eCID measurement report includes an indication of the timing advance validity timer, or wherein the timing advance validity timer is pre-configured, or wherein the timing advance validity timer is pre-defined.

[0239] Clause 46. The positioning estimation entity pursuant to any one of Clauses 44 to 45, wherein the timing advance validity timer is defined in a fixed time unit.

[0240] Clause 47. The positioning estimation entity as described in Clause 46, wherein the first timing advance is determined independently at the UE, or wherein the first timing advance is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the first timing advance is indicated to the UE via auxiliary data, or wherein the first timing advance is set to be equal to the second timing advance associated with the transmission of a Sounding Reference Signal (SRS) in the RRC_INACTIVE state.

[0241] Clause 48. The positioning estimation entity according to any one of Clauses 44 to 47, wherein the eCID measurement report further includes one or more signal metrics associated with the first time of receiving the first timing advance.

[0242] Clause 49. The positioning estimation entity as described in Clause 48, wherein one or more signal metrics are included in the eCID measurement report based on the first time the first timing advance was received and the second time associated with the transmission of the eCID measurement report being higher than a threshold.

[0243] Clause 50. The positioning estimation entity as described in Clause 49, wherein the threshold is determined independently at the UE, or wherein the threshold is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the threshold is indicated to the UE via auxiliary data, or wherein the threshold is set to be equal to a second timing advance associated with the transmission of a probe reference signal (SRS) in the RRC_INACTIVE state.

[0244] Clause 51. The location estimation entity pursuant to any one of Clauses 44 to 50, wherein the eCID measurement report further includes a second indication of a second timing advance associated with the second wireless network component.

[0245] Clause 52. The location estimation entity pursuant to any one of Clauses 44 to 51, wherein the first timing advance is static and specific to the first wireless network component, or wherein the first timing advance is static and specific to each of the wireless network components in a group of wireless network components including the first wireless network component.

[0246] Clause 53. The location estimation entity pursuant to any one of Clauses 44 to 52, wherein the first timing advance is dynamic and specific to the first wireless network component, or wherein the first timing advance is dynamic and specific to each of the wireless network components in a group of wireless network components including the first wireless network component.

[0247] Clause 54. A positioning estimation entity according to any one of Clauses 44 to 53, wherein the first timing advance is associated with a validity region, outside of which the first timing advance is invalid.

[0248] Clause 55. The positioning estimation entity according to any one of Clauses 44 to 54, wherein one or more parameters associated with the first timing advance are set equal to one or more corresponding parameters associated with the transmission of the sounding reference signal (SRS) in the RRC_INACTIVE state.

[0249] Clause 56. A location estimation entity according to any one of Clauses 44 to 55, wherein the location estimation entity corresponds to the UE, another UE, the first wireless network component, another wireless network component, or a location server.

[0250] Clause 57. A user equipment (UE) comprising: means for receiving a first timing advance associated with a first radio network component; means for determining a timing advance validity timer for location estimation based on enhanced cell identity (eCID); means for determining that the first timing advance is valid based on the timing advance validity timer; and means for sending an eCID measurement report, including eCID measurement information and a first indication of the first timing advance, to a location estimation entity in response to determining that the first timing advance is valid.

[0251] Clause 58. The UE as described in Clause 57, wherein the timing advance validity timer is defined in a fixed time unit.

[0252] Clause 59. The UE as described in Clause 58, wherein the first timing advance is determined independently at the UE, or wherein the first timing advance is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the first timing advance is indicated to the UE via auxiliary data, or wherein the first timing advance is set to be equal to the second timing advance associated with the transmission of a Sound Reference Signal (SRS) in the RRC_INACTIVE state.

[0253] Clause 60. The UE pursuant to any one of Clauses 57 to 59, wherein the timing advance validity timer is based on one or more reference signal received power (RSRP) measurements associated with the first radio network component.

[0254] Clause 61. The UE as described in Clause 60, wherein the timing advance validity timer is based on an RSRP change threshold.

[0255] Clause 62. The UE according to Clause 61, wherein the RSRP change threshold is determined independently at the UE, or wherein the RSRP change threshold is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the RSRP change threshold is indicated to the UE via auxiliary data, or wherein the RSRP change threshold is set to be equal to a second timing advance associated with the transmission of a Sounding Reference Signal (SRS) in the RRC_INACTIVE state.

[0256] Clause 63. The UE pursuant to any one of Clauses 57 to 62, wherein the eCID measurement report further includes one or more signal metrics associated with the first time of receiving the first timing advance.

[0257] Clause 64. The UE as described in Clause 63, wherein one or more signal metrics are included in the eCID measurement report based on the first time the first timing advance was received and the second time associated with the transmission of the eCID measurement report being higher than a threshold.

[0258] Clause 65. The UE as described in Clause 64, wherein the threshold is determined independently at the UE, or wherein the threshold is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the threshold is indicated to the UE via auxiliary data, or wherein the threshold is set to be equal to a second timing advance associated with the transmission of a probe reference signal (SRS) in the RRC_INACTIVE state.

[0259] Clause 66. The UE according to any one of Clauses 57 to 65, the UE further comprising: means for receiving a second timing advance associated with a second radio network component; and means for determining that the second timing advance is valid based on the timing advance validity timer, wherein in response to determining that the second timing advance is valid, the eCID measurement report further comprises a second indication of the second timing advance.

[0260] Clause 67. The UE pursuant to any one of Clauses 57 to 66, wherein the first timing advance is static and specific to the first radio network component, or wherein the first timing advance is static and specific to each of the radio network components in the group of radio network components including the first radio network component.

[0261] Clause 68. The UE pursuant to any one of Clauses 57 to 67, wherein the first timing advance is dynamic and specific to the first radio network component, or wherein the first timing advance is dynamic and specific to each of the radio network components in the group of radio network components including the first radio network component.

[0262] Clause 69. The UE pursuant to any one of Clauses 57 to 68, wherein the first timing advance is associated with a validity region, and outside the validity region, the first timing advance is invalid.

[0263] Clause 70. The UE according to any one of Clauses 57 to 69, wherein one or more parameters associated with the first timing advance are set equal to one or more corresponding parameters associated with the transmission of the probe reference signal (SRS) in the RRC_INACTIVE state.

[0264] Clause 71. The UE pursuant to any one of Clauses 57 to 70, wherein the location estimation entity corresponds to the UE, another UE, the first radio network component, another radio network component, or a location server.

[0265] Clause 72. A location estimation entity, the location estimation entity comprising: components for receiving an enhanced cell identity (eCID) measurement report from a user equipment (UE), the eCID measurement report including eCID measurement information and a first indication of a first timing advance associated with a first radio network component, the first timing advance being associated with a timing advance validity timer for location estimation based on the enhanced cell identity eCID; and components for determining a location estimate of the UE based on the eCID measurement information and the first timing advance.

[0266] Clause 73. The location estimation entity as described in Clause 72, wherein the eCID measurement report includes an indication of the timing advance validity timer, or wherein the timing advance validity timer is pre-configured, or wherein the timing advance validity timer is predefined.

[0267] Clause 74. The positioning estimation entity pursuant to any one of Clauses 72 to 73, wherein the timing advance validity timer is defined in a fixed time unit.

[0268] Clause 75. The positioning estimation entity as described in Clause 74, wherein the first timing advance is determined independently at the UE, or wherein the first timing advance is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the first timing advance is indicated to the UE via auxiliary data, or wherein the first timing advance is set to be equal to the second timing advance associated with the transmission of a Sounding Reference Signal (SRS) in the RRC_INACTIVE state.

[0269] Clause 76. The positioning estimation entity according to any one of Clauses 72 to 75, wherein the eCID measurement report further includes one or more signal metrics associated with the first time the first timing advance was received.

[0270] Clause 77. The positioning estimation entity as described in Clause 76, wherein one or more signal metrics are included in the eCID measurement report based on the first time the first timing advance was received and the second time associated with the transmission of the eCID measurement report being higher than a threshold.

[0271] Clause 78. The positioning estimation entity pursuant to Clause 77, wherein the threshold is determined independently at the UE, or wherein the threshold is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the threshold is indicated to the UE via auxiliary data, or wherein the threshold is set to be equal to a second timing advance associated with the transmission of a probe reference signal (SRS) in the RRC_INACTIVE state.

[0272] Clause 79. The location estimation entity pursuant to any one of Clauses 72 to 78, wherein the eCID measurement report further includes a second indication of a second timing advance associated with the second wireless network component.

[0273] Clause 80. The location estimation entity pursuant to any one of Clauses 72 to 79, wherein the first timing advance is static and specific to the first wireless network component, or wherein the first timing advance is static and specific to each of the wireless network components in a group of wireless network components including the first wireless network component.

[0274] Clause 81. The location estimation entity pursuant to any one of Clauses 72 to 80, wherein the first timing advance is dynamic and specific to the first wireless network component, or wherein the first timing advance is dynamic and specific to each of the wireless network components in a group of wireless network components including the first wireless network component.

[0275] Clause 82. A positioning estimation entity according to any one of Clauses 72 to 81, wherein the first timing advance is associated with a validity region, outside of which the first timing advance is invalid.

[0276] Clause 83. The positioning estimation entity according to any one of Clauses 72 to 82, wherein one or more parameters associated with the first timing advance are set equal to one or more corresponding parameters associated with the transmission of the sounding reference signal (SRS) in the RRC_INACTIVE state.

[0277] Clause 84. A location estimation entity according to any one of Clauses 72 to 83, wherein the location estimation entity corresponds to the UE, another UE, the first radio network component, another radio network component, or a location server.

[0278] Clause 85. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive a first timing advance associated with a first radio network component; determine a timing advance validity timer for location estimation based on enhanced cell identity (eCID); determine, based on the timing advance validity timer, that the first timing advance is valid; and, in response to determining that the first timing advance is valid, send an eCID measurement report to a location estimation entity including eCID measurement information and a first indication of the first timing advance.

[0279] Clause 86. The non-transitory computer-readable medium as described in Clause 85, wherein the timing advance validity timer is defined in a fixed time unit.

[0280] Clause 87. The non-transitory computer-readable medium as described in Clause 86, wherein the first timing advance is determined independently at the UE, or wherein the first timing advance is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the first timing advance is indicated to the UE via auxiliary data, or wherein the first timing advance is set to be equal to a second timing advance associated with the transmission of a probe reference signal (SRS) in the RRC_INACTIVE state.

[0281] Clause 88. A non-transitory computer-readable medium pursuant to any one of Clauses 85 to 87, wherein the timing advance validity timer is based on one or more reference signal received power (RSRP) measurements associated with the first wireless network component.

[0282] Clause 89. The non-transitory computer-readable medium as described in Clause 88, wherein the timing advance validity timer is based on an RSRP change threshold.

[0283] Clause 90. The non-transitory computer-readable medium pursuant to Clause 89, wherein the RSRP change threshold is determined independently at the UE, or wherein the RSRP change threshold is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the RSRP change threshold is indicated to the UE via auxiliary data, or wherein the RSRP change threshold is set to be equal to a second timing advance associated with the transmission of a probe reference signal (SRS) in the RRC_INACTIVE state.

[0284] Clause 91. A non-transitory computer-readable medium according to any one of Clauses 85 to 90, wherein the eCID measurement report further includes one or more signal metrics associated with a first time of receiving the first timing advance.

[0285] Clause 92. The non-transitory computer-readable medium according to Clause 91, wherein the one or more signal metrics are included in the eCID measurement report based on the first time of receiving the first timing advance and the second time associated with the transmission of the eCID measurement report being higher than a threshold.

[0286] Clause 93. The non-transitory computer-readable medium according to Clause 92, wherein the threshold is determined independently at the UE, or wherein the threshold is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the threshold is indicated to the UE via auxiliary data, or wherein the threshold is set to be equal to a second timing advance associated with the transmission of a probe reference signal (SRS) in the RRC_INACTIVE state.

[0287] Clause 94. A non-transitory computer-readable medium according to any one of Clauses 85 to 93, the non-transitory computer-readable medium further comprising computer-executable instructions that, when executed by the UE, cause the UE to: receive a second timing advance associated with a second radio network component; determine, based on the timing advance validity timer, that the second timing advance is valid, wherein, in response to determining that the second timing advance is valid, the eCID measurement report further comprises a second indication of the second timing advance.

[0288] Clause 95. A non-transitory computer-readable medium pursuant to any one of Clauses 85 to 94, wherein the first timing advance is static and specific to the first wireless network component, or wherein the first timing advance is static and specific to each of a group of wireless network components including the first wireless network component.

[0289] Clause 96. A non-transitory computer-readable medium pursuant to any one of Clauses 85 to 95, wherein the first timing advance is dynamic and specific to the first wireless network component, or wherein the first timing advance is dynamic and specific to each of a group of wireless network components including the first wireless network component.

[0290] Clause 97. A non-transitory computer-readable medium according to any one of Clauses 85 to 96, wherein the first timing advance is associated with a validity region, outside of which the first timing advance is invalid.

[0291] Clause 98. A non-transitory computer-readable medium according to any one of Clauses 85 to 97, wherein one or more parameters associated with the first timing advance are set equal to one or more corresponding parameters associated with the transmission of the probe reference signal (SRS) in the RRC_INACTIVE state.

[0292] Clause 99. A non-transitory computer-readable medium pursuant to any one of Clauses 85 to 98, wherein the location estimation entity corresponds to the UE, another UE, the first wireless network component, another wireless network component, or a location server.

[0293] Clause 100. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a location estimation entity, cause the location estimation entity to: receive an enhanced cell identity (eCID) measurement report from a user equipment (UE), the eCID measurement report including eCID measurement information and a first indication of a first timing advance associated with a first radio network component, the first timing advance being associated with a timing advance validity timer for location estimation based on the enhanced cell identity eCID; and determine a location estimate of the UE based on the eCID measurement information and the first timing advance.

[0294] Clause 101. The non-transitory computer-readable medium as described in Clause 100, wherein the eCID measurement report includes an indication of the timing advance validity timer, or wherein the timing advance validity timer is pre-configured, or wherein the timing advance validity timer is pre-defined.

[0295] Clause 102. A non-transitory computer-readable medium according to any one of Clauses 100 to 101, wherein the timing advance validity timer is defined in a fixed time unit.

[0296] Clause 103. The non-transitory computer-readable medium according to Clause 102, wherein the first timing advance is determined independently at the UE, or wherein the first timing advance is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the first timing advance is indicated to the UE via auxiliary data, or wherein the first timing advance is set to be equal to the second timing advance associated with the transmission of a probe reference signal (SRS) in the RRC_INACTIVE state.

[0297] Clause 104. A non-transitory computer-readable medium according to any one of Clauses 100 to 103, wherein the eCID measurement report further includes one or more signal metrics associated with a first time of receiving the first timing advance.

[0298] Clause 105. The non-transitory computer-readable medium as described in Clause 104, wherein one or more signal metrics are included in the eCID measurement report based on the first time of receiving the first timing advance and the second time associated with the transmission of the eCID measurement report being higher than a threshold.

[0299] Clause 106. The non-transitory computer-readable medium according to Clause 105, wherein the threshold is determined independently at the UE, or wherein the threshold is indicated to the UE via Radio Resource Control (RRC) signaling, or wherein the threshold is indicated to the UE via auxiliary data, or wherein the threshold is set to be equal to a second timing advance associated with the transmission of a probe reference signal (SRS) in the RRC_INACTIVE state.

[0300] Clause 107. A non-transitory computer-readable medium pursuant to any one of Clauses 100 to 106, wherein the eCID measurement report further includes a second indication of a second timing advance associated with the second wireless network component.

[0301] Clause 108. A non-transitory computer-readable medium pursuant to any one of Clauses 100 to 107, wherein the first timing advance is static and specific to the first wireless network component, or wherein the first timing advance is static and specific to each of a group of wireless network components including the first wireless network component.

[0302] Clause 109. A non-transitory computer-readable medium pursuant to any one of Clauses 100 to 108, wherein the first timing advance is dynamic and specific to the first wireless network component, or wherein the first timing advance is dynamic and specific to each of a group of wireless network components including the first wireless network component.

[0303] Clause 110. A non-transitory computer-readable medium according to any one of Clauses 100 to 109, wherein the first timing advance is associated with a validity region, outside of which the first timing advance is invalid.

[0304] Clause 111. A non-transitory computer-readable medium according to any one of Clauses 100 to 110, wherein one or more parameters associated with the first timing advance are set equal to one or more corresponding parameters associated with the transmission of the probe reference signal (SRS) in the RRC_INACTIVE state.

[0305] Clause 112. A non-transitory computer-readable medium according to any one of Clauses 100 to 111, wherein the location estimation entity corresponds to the UE, another UE, the first wireless network component, another wireless network component, or a location server.

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

[0307] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various exemplary components, blocks, modules, circuits, and steps have been described above in general terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application; however, such implementation decisions should not be construed as departing from the scope of this disclosure.

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

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

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

[0311] While the foregoing disclosure illustrates exemplary aspects of this disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of this disclosure as defined by the appended claims. For example, the functions, steps, and / or actions of the method claims according to aspects of this disclosure described herein need not be performed in any particular order. Furthermore, no component, function, action, or instruction described or claimed herein should be construed as critical or essential unless explicitly stated otherwise. Additionally, as used herein, the terms “set,” “group,” etc., are intended to include one or more of the stated elements. Furthermore, as used herein, the terms “having,” “comprising,” “including,” etc., do not exclude the presence of one or more additional elements (e.g., element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be open-ended when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one”), or these alternatives are mutually exclusive (e.g., “one or more” should not be interpreted as “one and more”). Additionally, although components, functions, actions, and instructions may be described or claimed in the singular, plural forms may also be considered unless explicitly stated to be limited to the singular. Therefore, as used herein, the articles “a,” “an,” “the,” and “described” are intended to include one or more of the stated elements. Additionally, as used herein, the terms “at least one” and “one or more” include “one” component, function, action, or instruction that performs or is capable of performing the described or claimed functionality, and also include “two or more” components, functions, actions, or instructions that perform or are capable of performing the described or claimed functionality in combination.

Claims

1. A method for operating user equipment (UE), the method comprising: Receive the first timing advance associated with the first wireless network component; Determine the timing advance validity timer for location estimation based on enhanced cell identity (eCID); The first timing advance is determined to be effective based on the timing advance validity timer. as well as In response to determining that the first timing advance is valid, an eCID measurement report including eCID measurement information and a first indication of the first timing advance is sent to the positioning estimation entity.

2. The method according to claim 1, wherein the timing advance validity timer is defined in a fixed time unit.

3. The method according to claim 2, Wherein the first timing advance is determined independently at the UE, or The first timing advance is indicated to the UE via Radio Resource Control (RRC) signaling, or The first timing advance is indicated to the UE via auxiliary data, or The first timing advance is set to be equal to the second timing advance associated with the transmission of the probe reference signal (SRS) in the RRC_INACTIVE state.

4. The method of claim 1, wherein the timing advance validity timer is based on one or more reference signal received power (RSRP) measurements associated with the first wireless network component.

5. The method according to claim 4, wherein the timing advance validity timer is based on an RSRP change threshold.

6. The method according to claim 5, The RSRP change threshold is determined independently at the UE, or The RSRP change threshold is indicated to the UE via Radio Resource Control (RRC) signaling, or The RSRP change threshold is indicated to the UE via auxiliary data, or The RSRP change threshold is set to be equal to the second timing advance associated with the transmission of the probe reference signal (SRS) in the RRC_INACTIVE state.

7. The method of claim 1, wherein the eCID measurement report further includes one or more signal metrics associated with a first time of receiving the first timing advance.

8. The method of claim 7, wherein the one or more signal metrics are included in the eCID measurement report based on the first time the first timing advance was received and the second time associated with the transmission of the eCID measurement report being higher than a threshold.

9. The method according to claim 8, The threshold is determined independently at the UE, or The threshold is indicated to the UE via Radio Resource Control (RRC) signaling, or The threshold is indicated to the UE via auxiliary data, or The threshold is set to be equal to the second timing advance associated with the transmission of the probe reference signal (SRS) in the RRC_INACTIVE state.

10. The method according to claim 1, further comprising: Receive the second timing advance associated with the second wireless network component; as well as The second timing advance is determined to be valid based on the timing advance validity timer. In response to determining that the second timing advance is valid, the eCID measurement report also includes a second indication of the second timing advance.

11. The method according to claim 1, Wherein the first timing advance is static and specific to the first wireless network component, or The first timing advance is static and specific to each wireless network component in the group of wireless network components that includes the first wireless network component.

12. The method according to claim 1, Wherein the first timing advance is dynamic and specific to the first wireless network component, or The first timing advance is dynamic and specific to each wireless network component in the group of wireless network components that includes the first wireless network component.

13. The method of claim 1, wherein the first timing advance is associated with a validity region, outside of which the first timing advance is invalid.

14. The method of claim 1, wherein one or more parameters associated with the first timing advance are set equal to one or more corresponding parameters associated with the transmission of the probe reference signal (SRS) in the RRC_INACTIVE state.

15. The method of claim 1, wherein the location estimation entity corresponds to the UE, another UE, the first wireless network component, another wireless network component, or a location server.

16. A method for locating and estimating an entity, the method comprising: Receive an enhanced cell identity (eCID) measurement report from a user equipment (UE), the eCID measurement report including eCID measurement information and a first indication of a first timing advance associated with a first radio network component, the first timing advance being associated with a timing advance validity timer for eCID-based location estimation; as well as The location estimate of the UE is determined based on the eCID measurement information and the first timing advance.

17. The method according to claim 16, The eCID measurement report includes an indication of the timing advance effectiveness timer, or The aforementioned timing advance validity timer is pre-configured, or The timing advance validity timer mentioned above is predefined.

18. The method of claim 16, wherein the timing advance validity timer is defined in a fixed time unit.

19. The method according to claim 18, Wherein the first timing advance is determined independently at the UE, or The first timing advance is indicated to the UE via Radio Resource Control (RRC) signaling, or The first timing advance is indicated to the UE via auxiliary data, or The first timing advance is set to be equal to the second timing advance associated with the transmission of the probe reference signal (SRS) in the RRC_INACTIVE state.

20. The method of claim 16, wherein the eCID measurement report further includes one or more signal metrics associated with a first time of receiving the first timing advance.

21. The method of claim 20, wherein the one or more signal metrics are included in the eCID measurement report based on the first time the first timing advance was received and the second time associated with the transmission of the eCID measurement report being higher than a threshold.

22. The method according to claim 21, The threshold is determined independently at the UE, or The threshold is indicated to the UE via Radio Resource Control (RRC) signaling, or The threshold is indicated to the UE via auxiliary data, or The threshold is set to be equal to the second timing advance associated with the transmission of the probe reference signal (SRS) in the RRC_INACTIVE state.

23. The method of claim 16, wherein the eCID measurement report further includes a second indication of a second timing advance associated with the second wireless network component.

24. The method according to claim 16, Wherein the first timing advance is static and specific to the first wireless network component, or The first timing advance is static and specific to each wireless network component in the group of wireless network components that includes the first wireless network component.

25. The method according to claim 16, Wherein the first timing advance is dynamic and specific to the first wireless network component, or The first timing advance is dynamic and specific to each wireless network component in the group of wireless network components that includes the first wireless network component.

26. The method of claim 16, wherein the first timing advance is associated with a validity region, outside of which the first timing advance is invalid.

27. The method of claim 16, wherein one or more parameters associated with the first timing advance are set equal to one or more corresponding parameters associated with the transmission of the probe reference signal (SRS) in the RRC_INACTIVE state.

28. The method of claim 16, wherein the location estimation entity corresponds to the UE, another UE, the first wireless network component, another wireless network component, or a location server.

29. A user equipment (UE), the user equipment (UE) comprising: One or more memory units; One or more transceivers; and One or more processors, communicatively coupled to one or more memories and one or more transceivers, wherein the one or more processors are configured individually or in combination to: Receive a first timing advance associated with the first wireless network component via the one or more transceivers; Determine the timing advance validity timer for location estimation based on enhanced cell identity (eCID); The first timing advance is determined to be effective based on the timing advance validity timer. as well as In response to determining that the first timing advance is valid, an eCID measurement report, including eCID measurement information and a first indication of the first timing advance, is sent to the positioning estimation entity via the one or more transceivers.

30. A location estimation entity, the location estimation entity comprising: One or more memory units; One or more transceivers; and One or more processors, communicatively coupled to one or more memories and one or more transceivers, wherein the one or more processors are configured individually or in combination to: The enhanced cell identity (eCID) measurement report is received from the user equipment (UE) via the one or more transceivers. The eCID measurement report includes eCID measurement information and a first indication of a first timing advance associated with a first radio network component. The first timing advance is associated with a timing advance validity timer for positioning estimation based on enhanced cell identity (eCID). as well as The location estimate of the UE is determined based on the eCID measurement information and the first timing advance.

Images