Autonomous region validity timer extension or restart

Abstract

Techniques for wireless communication are disclosed. In an aspect, a user equipment (UE): performs cell reselection from a first camping cell to a second camping cell while in a Radio Resource Control (RRC) non-connected state, where the first camping cell and the second camping cell are within a same uplink channel transmission validity area; and in response to the cell reselection, extending or restarting a timing adjustment (TA) validity timer based on one or more criteria, where the TA validity timer indicates a time period that allows the UE to transmit the one or more uplink channels while in the RRC non-connected state without updating the uplink transmission timing of the UE.

Description

Cross-references to related applications

[0001] This patent application claims priority to Greek patent application No. 20230100716, filed on September 7, 2023, entitled “AUTONOMOUS AREA VALIDITYTIMER EXTENSION OR RESTART”, which has been assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Technical Field

[0002] All aspects of this disclosure relate to wireless communications. Background Technology

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

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

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

[0006] In one aspect, a method of wireless communication performed by a user equipment (UE) includes: performing cell reselection from a first camping cell to a second camping cell while in a Radio Resource Control (RRC) disconnected state, wherein the first camping cell and the second camping cell are in the same uplink channel transmission validity area; and in response to the cell reselection, extending or restarting a timing adjustment (TA) validity timer based on one or more criteria, wherein the TA validity timer indicates a period of time during which the UE is allowed to transmit one or more uplink channels while in an RRC disconnected state.

[0007] In one aspect, a method of wireless communication performed by a network node includes: receiving one or more uplink channels from a user equipment (UE) while the UE is operating in a Radio Resource Control (RRC) disconnected state; and sending a paging message to the UE to configure the UE to restart or extend a timing advance (TA) validity timer, wherein the TA validity timer indicates a period of time during which the UE is allowed to transmit one or more uplink channels while in an RRC disconnected state.

[0008] 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 configured individually or in combination to: perform cell reselection from a first camping cell to a second camping cell while in a Radio Resource Control (RRC) disconnected state, wherein the first camping cell and the second camping cell are in the same uplink channel transmission validity area; and in response to cell reselection, extend or restart a Timing Adjustment (TA) validity timer based on one or more criteria, wherein the TA validity timer indicates a period of time during which the UE is allowed to transmit one or more uplink channels while in an RRC disconnected state.

[0009] In one aspect, a network node 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 one or more uplink channels from the UE via the one or more transceivers when the user equipment (UE) is operating in a Radio Resource Control (RRC) disconnected state; and send a paging message to the UE via the one or more transceivers to configure the UE to restart or extend a Timing Advance (TA) validity timer, wherein the TA validity timer indicates a period of time during which the UE is allowed to transmit one or more uplink channels while in an RRC disconnected state.

[0010] In one aspect, a user equipment (UE) includes: components for performing cell reselection from a first camping cell to a second camping cell while in a Radio Resource Control (RRC) disconnected state, wherein the first camping cell and the second camping cell are within the same uplink channel transmission validity area; and components for extending or restarting a Timing Adjustment (TA) validity timer based on one or more criteria in response to the cell reselection, wherein the TA validity timer indicates a period of time during which the UE is allowed to transmit one or more uplink channels while in an RRC disconnected state.

[0011] In one aspect, a network node includes: components for receiving one or more uplink channels from a user equipment (UE) when the UE is operating in a Radio Resource Control (RRC) disconnected state; and components for sending a paging message to the UE configuring the UE to restart or extend a timing advance (TA) validity timer, wherein the TA validity timer indicates a period of time during which the UE is allowed to send one or more uplink channels while in an RRC disconnected state.

[0012] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: perform a cell reselection from a first camping cell to a second camping cell while in a Radio Resource Control (RRC) disconnected state, wherein the first camping cell and the second camping cell are within the same uplink channel transmission validity area; and, in response to the cell reselection, extend or restart a Timing Adjustment (TA) validity timer based on one or more criteria, wherein the TA validity timer indicates a period of time during which the UE is allowed to transmit one or more uplink channels while in an RRC disconnected state.

[0013] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a network node, cause the network node to: receive one or more uplink channels from the user equipment (UE) while the UE is operating in a Radio Resource Control (RRC) disconnected state; and send a paging message to the UE configuring the UE to restart or extend a timing advance (TA) validity timer, wherein the TA validity timer indicates a period of time during which the UE is permitted to send one or more uplink channels while in an RRC disconnected state.

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

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

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

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

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

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

[0020] Figure 5 Examples of various positioning methods supported in new radios (NR) according to various aspects of this disclosure are illustrated.

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

[0022] Figure 7A and Figure 7B An example of a delayed Mobile Termination Location Request (MTLR) procedure for a positioning method based on downlink and uplink according to various aspects of this disclosure is illustrated.

[0023] Figure 8 An example RRC “SRS-PosRRC-Inactive” IE is illustrated according to various aspects of this disclosure.

[0024] Figure 9A and Figure 9B An example of a delayed MT LR process is illustrated for a positioning method based on downlink and uplink with positioning SRS pre-configuration according to various aspects of this disclosure.

[0025] Figure 10 This is an illustration of an example UE mobility scenario across multiple regions according to various aspects of this disclosure.

[0026] Figure 11 This is a diagram illustrating the structure of a pre-configured positioning detection reference signal (SRS) according to various aspects of this disclosure.

[0027] Figure 12This is a diagram illustrating the relationship between the validity timer "inactivePosSRS-TimeAlignmentTimer" and SRS transmission according to various aspects of this disclosure.

[0028] Figure 13 This is a diagram illustrating an example of a timer extending a cell area according to various aspects of this disclosure.

[0029] Figure 14 This is a diagram illustrating example SRS validity areas according to various aspects of this disclosure.

[0030] Figure 15 and Figure 16 Example methods of wireless communication according to various aspects of this disclosure are illustrated. Detailed Implementation

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

[0032] Various aspects collectively relate to the validity region used for detecting reference signal (SRS) transmissions. Some aspects more specifically relate to the extension or restarting of implicit SRS validity region validity timers. In some examples, a user equipment (UE) can restart a validity timer whenever the signal strength of a given cell exceeds a predetermined threshold. The network node communicatively coupled to the UE can configure the threshold, the observation window for checking the threshold, and / or the number M of measurement opportunities for checking the threshold. In some examples, the network can define a timer extension region within the UE's validity region. The timer extension region can be at least a subset of the validity region. In some examples, the validity timer can be extended based on SRS reception on the network side. Alternatively, the network can configure a list of cells from which the UE can (or may not) extend / restart the validity timer.

[0033] Specific aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages. In some examples, by allowing the UE to extend or restart the validity timer, the described techniques can be used to reduce power consumption at the UE by reducing the need for the UE to transition to a connected state to obtain a new timing advance (TA) command.

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

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

[0036] 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 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, the corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions."

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

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

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

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

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

[0042] Figure 1An 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.

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

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

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

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

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

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

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

[0050] 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 can be referred to as millimeter waves. Near-mmW extends down to 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.

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

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

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

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

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

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

[0057] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR studies have designated the operating bands for these IF bands 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 IF band frequencies. Furthermore, 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.

[0058] In light of the above, unless otherwise specifically stated, it should be understood that when the term "below 6 GHz" is used herein, it 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 when the term "millimeter wave" is used herein, it 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.

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

[0060] For example, still refer to Figure 1 One 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0078] Communication systems, such as 5G NR systems, can be deployed in various ways with a variety of 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, access points (APs), transmit / receive points (TRPs), or cells) can be implemented as aggregated base stations (also known as self-contained base stations or monolithic base stations) or decomposed base stations.

[0079] 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 can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed across one or more other RAN nodes. DUs can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0080] Base station type operation or network design can 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. ® Decomposition 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 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 for wired or wireless communication with at least one other unit.

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

[0082] Each of the units (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 of the units, 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.

[0083] In some aspects, the CU 280 can host one or more higher-level control functions. Such control functions may include RRC, PDCP, Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to 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.

[0084] 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 based on functional partitioning (such as that provided by the 3rd Generation Partnership Project (3GPP)). ® The DU285 is configured to host one or more of the following functional partitions: the RLC layer, the 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 also host one or more low-PHY layers. Each layer (or module) can be implemented using an interface configured to communicate with other layers (and modules) hosted by the DU285 or with control functions hosted by the CU280.

[0085] 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, 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 cloud-based RAN architectures (such as vRAN architectures).

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

[0087] 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 an interface, such as via 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.

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

[0089] Figure 3A , Figure 3B and Figure 3C Several example components (represented by corresponding boxes) are illustrated, which 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 LMF 270, or alternatively may be independent of UE 302). Figure 2A and Figure 2BThe NG-RAN 220 and / or 5GC 210 / 260 infrastructures depicted herein (such as dedicated networks) are used to support the operations described herein. It should be understood that these components can be implemented in different specific implementations in different types of devices (e.g., in ASICs, in System-on-Chip (SoCs), etc.). The illustrated components can also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. 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.

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

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

[0092] In at least some cases, UE 302 and base station 304 also include satellite signal receivers 330 and 370. Satellite signal receivers 330 and 370 can be connected to one or more antennas 336 and 376 respectively, and can provide components for receiving and / or measuring satellite positioning / communication signals 338 and 378 respectively. Where satellite signal receivers 330 and 370 are satellite positioning system receivers, satellite positioning / communication signals 338 and 378 can be Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, etc. ®The signals include Galileo signals, BeiDou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. When satellite signal receivers 330 and 370 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 330 and 370 can include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request information and operations from other systems as needed, 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.

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

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

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

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

[0097] 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 positioning components 342, 388, and 398. Positioning components 342, 388, and 398 may be hardware circuitry that is part of or coupled to processors 332, 384, and 394, respectively, which, when executed, cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, positioning components 342, 388, and 398 may be external to processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, positioning components 342, 388, and 398 may be memory modules stored in memories 340, 386, and 396, respectively, which, when executed by processors 332, 384, and 394 (or modem processing system, another processing system, etc.), enable UE 302, base station 304, and network entity 306 to perform the functionality described herein. Figure 3A Possible locations for the positioning component 342 are illustrated. The positioning component may be part of, for example, one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a standalone component. Figure 3BPossible locations for the positioning component 388 are illustrated. The positioning 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 may be a standalone component. Figure 3C Possible locations for the positioning component 398 are illustrated. The positioning 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 may be a standalone component.

[0098] UE 302 may include one or more sensors 344 coupled to one or more processors 332 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 receivers 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.

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

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

[0101] 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 scheme, as well as for spatial processing. The channel estimates can be derived from reference signals 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.

[0102] 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 332. Transmitter 314 and receiver 312 implement Layer 1 functionality associated with various signal processing functions. Receiver 312 can perform spatial processing on the information to recover any spatial streams destined for UE 302. If multiple spatial streams are destined for UE 302, they can be combined by receiver 312 into a single OFDM symbol stream. Receiver 312 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 304 on the physical channel. Then, data and control signals are provided to one or more processors 332, which implement layer 3 (L3) and layer 2 (L2) functionality.

[0103] In the downlink, one or more processors 332 provide demultiplexing, 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 332 are also responsible for error detection.

[0104] Similar to the functionality described in conjunction with downlink transmissions performed by base station 304, one or more processors 332 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 upper-layer PDU delivery, 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.

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

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

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

[0108] For convenience, UE 302, base station 304 and / or network entity 306 are in Figure 3A , Figure 3B and Figure 3C The 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). ® (e.g., cellular only), or the short-range wireless transceiver 320 can be omitted (e.g., cellular only), or the satellite signal receiver 330 can be omitted, or the sensor 344 can be omitted, etc. For 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 receiver 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.

[0109] Various components of UE 302, base station 304, and network entity 306 can be communicatively coupled to each other via data buses 334, 382, ​​and 392, respectively. In one aspect, data buses 334, 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 334, 382, ​​and 392 can provide communication between these different logical entities.

[0110] 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 3C The 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). Moreover, 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, as will be understood, such operations, actions and / or functions can actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity 306, etc. (such as processors 332, 384, 394, transceivers 310, 320, 350 and 360, memory 340, 386 and 396, positioning components 342, 388 and 398, etc.).

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

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

[0113] Figure 4 Figure 400 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 410. After a random access procedure, the UE moves to the RRC connected state 420. 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 430. The UE can resume its session by performing a random access procedure to transition back to the RRC connected state 420. Therefore, regardless of whether the UE is in the RRC idle state 410 or the RRC inactive state 430, the UE needs to perform a random access procedure to transition to the RRC connected state 420.

[0114] Operations performed in RRC Idle State 410 include Public Land Mobile Network (PLMN) selection, broadcasting of system information, cell reselection mobility, paging for mobile station called data (initiated and managed by the 5GC), and Discontinuous Reception (DRX) for core network paging (configured by the Non-Access Stratum (NAS)). Operations performed in RRC Connected State 420 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 430 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.

[0115] NR supports various cellular network-based positioning technologies, including downlink-based positioning methods, uplink-based positioning methods, and positioning methods based on both downlink and uplink. Downlink-based positioning methods include: Observed Time Difference of Arrival (OTDOA) in LTE, Downlink Time Difference of Arrival (DL-TDOA) in NR, and Downlink Angle of Departure (DL-AoD) in NR. Figure 5 Examples of various positioning methods according to aspects of this disclosure are illustrated. In the OTDOA or DL-TDOA positioning process illustrated in scenario 510, 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) measurement) 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 measurement, 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.

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

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

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

[0119] Downlink and uplink-based positioning methods include Enhanced Cell ID (E-CID) positioning and Multiple Round-Trip Time (RTT) positioning (also known as "Multi-Cell RTT" and "Multi-RTT"). 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 the multi-RTT positioning illustrated in scenario 530, 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) to enable the location of the first entity to be determined based on the distance to the second entities and the known location of the second entities (e.g., using polygonal measurements). RTT and multi-RTT methods can be combined with other positioning technologies (such as UL-AoA and DL-AoD) to improve location accuracy, as illustrated in scenario 540.

[0120] The E-CID positioning method is based on Radio Resource Management (RRM) measurements. In E-CID, the UE reports the serving cell ID, timing advance (TA), 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.

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

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

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

[0124] Various frame structures can be used to support downlink and uplink transmission between network nodes (e.g., base stations and UEs). Figure 6 Figure 600 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.

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

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

[0127] exist Figure 6 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 1ms long, and each subframe includes one time slot. Figure 6 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.

[0128] 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 6In 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.

[0129] 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 6 An example location (labeled "R") of an RE carrying a reference signal is shown.

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

[0131] 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 6 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.

[0132] 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 6 (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}.

[0133] 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 a TRP ID). Additionally, PRS resources in a PRS resource set share the same periodicity, common silent mode configuration, and the same repetition factor (such as “PRS-ResourceRepetitionFactor”) across time slots. Periodicity is the time from the first repetition of the first PRS resource in the first PRS instance to the same first repetition of the same first PRS resource in the next PRS instance. The periodicity can have a length chosen from the following: 2^µ*{4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240} time slots, where µ = 0, 1, 2, 3. The repetition factor can have a length chosen from {1, 2, 4, 6, 8, 16, 32} time slots.

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

[0135] 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.”

[0136] A “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 uses 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.

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

[0138] On the one hand, Figure 6The 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.

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

[0140] 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 6 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.

[0141] 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 6(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}.

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

[0143] Several enhancements to the previously defined SRS have been proposed 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 the downlink reference signal or SSB from the adjacent TRP. 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. All of these are features outside the current SRS framework, which is configured via higher-level RRC signaling (and potentially triggered or activated via MAC control elements (MAC-CE) or downlink control information (DCI)).

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

[0145] Low Power High Accuracy Positioning (LPHAP) technology has been introduced, which allows the UE to perform positioning operations while in an RRC inactive state. Utilizing the Small Data Transmission (SDT) feature, the UE can also transmit data and / or NAS signaling while remaining in this RRC inactive state, thereby allowing the UE to participate in downlink- and uplink-based positioning processes and / or uplink-based positioning processes, rather than just downlink-based positioning processes.

[0146] The Deferred Mobility Termination Location Request (MT-LR) procedure provides an effective means of location tracking for mobile devices or assets. During the initialization phase, location instructions (e.g., the location method to use, QoS, etc.) and possible auxiliary data can be provided to the target device. The target device then monitors for events, performs location measurements upon detection, and provides the location results to the network. Various event types are supported, such as entering, leaving, or remaining within a predefined geographic area, moving beyond a predefined distance from a previous location, or periodic locations. The procedure is defined to allow the UE to remain in an RRC inactive state during the location measurement and event reporting phases.

[0147] Figure 7A and Figure 7BAn example of a delayed Mobile Termination Location Request (MT-LR) procedure for a downlink- and uplink-based positioning method (e.g., multiple RTT) according to various aspects of this disclosure is illustrated. This procedure consists of two event reports: such as... Figure 7A The illustrated event report #1 (phase 3-10) for requesting / configuring SRS for location is shown, and as... Figure 7B The example is Event Report #2 (Phase 12-16) used to report location measurements.

[0148] At Phase 1, Phases 1-21 of the delayed 5GC-MT-LR procedure for periodic or triggered location events, as specified in 3GPP Technical Specification (TS) 23.273, Clause 6.3.1 (which is publicly available and incorporated herein by reference in its entirety), are executed. The LMF 270 may perform one or more positioning procedures at Phase 15 of the delayed 5GC-MT-LR procedure for periodic or triggered location events (as specified in 3GPP TS 23.273, Clause 6.3.1) to request and obtain UE 204 positioning capabilities or to provide any necessary auxiliary data to the target device. The Location Services (LCS) periodic triggered location call at Phase 16 of the Deferred 5GC-MT-LR process for periodic or triggered location events (as specified in 3GPP TS23.273, Clause 6.3.1) includes an embedded LPP Request Location Information message that indicates a permitted or required multi-RTT location measurement for each reported location event.

[0149] At some point, UE 204 is released from RRC connection to RRC inactivity by the last serving gNB via "RRCRelease" with "SuspendConfig".

[0150] At Phase 2, UE 204 monitors the occurrence of triggered or periodic events requested during Phase 1.

[0151] At Phase 3, when an event is detected (or slightly earlier), UE 204 transmits an RRC UL information delivery message containing the ULNAS transmission message along with an RRC recovery request via Small Data Transmission (SDT). UE 204 includes an LCS event report in the payload container of the UL NAS transmission message, and a deferred route identifier received during Phase 1 in the additional information of the UL NAS transmission message. The LCS event report includes an embedded LPP request assistance data message, where IE “NR-Multi-RTT-RequestAssistanceData” and “nr-AdType” are set to “ul-srs” to request UL-SRS for multi-RTT positioning. Note that the gNB received by UE 204 when UE 204 is performing Phase 3 may be the same as or different from the last serving gNB when UE 204 is released to the RRC inactive state.

[0152] At phase 4, the receiving gNB transmits an LCS event report with an LPP request auxiliary data message to the serving AMF 264 in a Next Generation Application Protocol (NGAP) uplink NAS transport message. AMF 264 determines the LMF 270 based on the deferred routing identifier received in the UL NAS transport message's Additional Information IE, and forwards the LCS event report with an embedded LPP message to the LMF 270 via triggering the Namf_Communication_N1MessageNotify service operation. AMF 264 also includes the payload container type and related identifiers set as the deferred routing identifier. Note that if the anchor gNB has not changed from the last serving gNB to the receiving gNB, the LCS event report can be forwarded from the receiving gNB to the last serving gNB via Xn Application Protocol (XnAP) message RRC. Subsequent downlink / uplink messages can also be forwarded between the last serving gNB and the receiving gNB via XnAP message RRC.

[0153] At phase 5, LMF 270 transmits a New Radio Positioning Protocol Type A (NRPPa) Location Information Request message to the receiving gNB to request UL-SRS for the target device (i.e., UE 204).

[0154] At stage 6, the receiving gNB determines the resources available for UL-SRS.

[0155] At stage 7, the gNB provides UL-SRS configuration information to the LMF 270 in the NRPPa positioning information response message.

[0156] At stage 8, the LMF 270 transmits an NRPPa measurement request, including the UL-SRS measurement configuration, to the gNB group.

[0157] At phase 9, LMF 270 transmits a Supplemental Service (SS) LCS event report acknowledgment to the receiving gNB. Then, at phase 9b, the receiving gNB provides the SS event report acknowledgment to UE 204 via subsequent DL SDT.

[0158] At phase 10, the gNB receives a “RRCRelease” message with “suspendConfig” to keep UE 204 in an RRC inactive state. The “RRCRelease” message includes the UL-SRS configuration.

[0159] At phase 11, UE 204 performs DL-PRS measurements, and each configured TRP performs UL-SRS measurements.

[0160] At phase 12, UE 204 transmits an RRC UL information delivery message containing the UL NAS transmission message along with an RRC recovery request via SDT. UE 204 includes an LCS event report and an LPP location information provision message in the payload container of the UL NAS transmission message, as well as a delayed route identifier received during phase 1 from the additional information in the UL NAS transmission message.

[0161] At phase 13, the gNB receives an LCS event report with an LPP-provided location information message in an NGAP uplink NAS transport message and transmits it to the serving AMF 264. AMF 264 determines the LMF 270 based on the deferred routing identifier received in the UL NAS transport message's additional information IE, and forwards the LCS event report with an embedded LPP message to the LMF 270 via triggering the Namf_Communication_N1MessageNotify service operation. AMF 264 also includes the payload container type and related identifiers set as deferred routing identifiers.

[0162] At stage 14, after performing the UL-SRS measurement, the gNB provides the UL measurement to the LMF 270 in the NRPPa measurement response message.

[0163] At stage 15, once all LPP location information messages have been received, LMF 270 transmits an SS LCS event report acknowledgment to the receiving gNB. Then, at stage 15b, the receiving gNB provides an SS event report acknowledgment to UE 204 via a subsequent DL SDT.

[0164] At phase 16, the gNB receives a “RRCRelease” message with “suspendConfig” to keep UE 204 in an RRC inactive state.

[0165] At stage 17, stages 28-31 of the delayed 5GC-MT-LR process for periodic or triggered location events, as specified in TS 23.273, Clause 6.3.1, are executed.

[0166] In the aforementioned process, whenever an event report is triggered (e.g., when a periodic timer expires), a new positioning SRS can be "negotiated" between the LMF and the serving / receiving gNB (as in...). Figure 7A (At stages 3-10 in the process). This results in large signaling activity for periodic events with relatively small periodicity (e.g., 15 to 30 seconds), and thus additional latency and processing, which may also adversely affect power consumption at the target device.

[0167] To reduce the amount of SRS configuration signaling, pre-configuration of the SRS has been proposed. This assumes, for example, that it can be configured during the initialization phase of the MT-LR process (…). Figure 7A Phase 1) provides a single positioning SRS, which can then be activated as needed. Instead of... Figure 7A In stages 3 and 4, the event report is transmitted to LMF 270 to request SRS location from LMF 270. UE 204 could potentially use lower-layer signaling (e.g., MAC control element (CE) (MAC-CE)) to directly transmit the request to NG-RAN 220 (receiving gNB) to activate the pre-configured SRS location. In this case, it would be unnecessary or could be simplified. Figure 7A Phases 5-7 and 9a.

[0168] However, due to mobility, a UE can request "SRS activation" in a different cell than the one from which it has already received a pre-configured location SRS. The location SRS used is typically UE- and location-specific. Currently, the location SRS configuration is only valid in cells from which the UE has already received the SRS configuration. This is because the SRS configuration includes (at least coarsely) parameters dependent on the UE's location, such as spatial relation information and path loss reference information (both are provided for neighboring cells, and neighboring cells are typically different for different serving cells), as well as information determined by the receiving / serving gNB, such as timing advance information. Currently, the UE releases the location SRS configuration when cell reselection occurs. However, because the location SRS configuration also includes parameters that can be valid for a large portion of the network (multiple cells), at least a portion of the SRS configuration can be pre-configured.

[0169] To enable pre-configuration of the location SRS, the location SRS parameters can be divided into two parts. The first part (referred to as "part (a)") is a set of parameters valid for multiple cells. The area where this parameter set is valid can be indicated by a list of cell IDs. This list of cell IDs can be considered "area IDs" in which the location SRS parameter set is applicable or valid. The second part (referred to as "part (b)") is a location / cell-specific set of parameters. Part (a) of the SRS used for location configuration can be pre-configured, while part (b) will be provided in the SRS activation message.

[0170] Figure 8 This is an illustration 800 illustrating a pre-configured positioning SRS structure according to various aspects of this disclosure. For example... Figure 8 As shown, each pre-configured positioning SRS includes an identifier.

[0171] The positioning SRS configuration for RRC inactive states currently includes the following parameters as specified in 3GPP TS 38.331 (which is publicly available and incorporated herein by reference in its entirety). The “SRS-PosResourceSet” includes the parameters “srs-PosResourceSetId”, “srs-PosResourceIdList”, “resourceType”, “alpha”, “p0”, and “pathlossReferenceRS-Pos”. The “srs-PosResourceSetId” parameter indicates the ID of this resource set. It is unique within the context of the BWP defining the positioning SRS. The “srs-PosResourceIdList” parameter indicates the ID of the SRS used for positioning resources in this “SRS-PosResourceSet”. The “resourceType” parameter defines the temporal behavior of the SRS resource configuration (e.g., periodic, semi-persistent, aperiodic). The “alpha” parameter indicates the value of the positioning SRS power control, which defines fractional path loss compensation. The UE multiplies the alpha value by the path loss estimate. For full path loss compensation, alpha equals 1. The “p0” parameter indicates the value for the location SRS power control, which can be described as the “desired received power” at the TRP. That is, the SRS used to determine the location transmit power is based on p0 + alpha × PL, where PL is the path loss estimate. The “pathlossReferenceRS-Pos” parameter defines the reference DL signal to be used for path loss estimation. The downlink reference signal can be an SSB or DL-PRS from the serving TRP or a neighboring TRP.

[0172] The "SRS-PosResource" parameter includes "srs-PosResourceId", "transmissionComb", "resourceMapping", "freqDomainShift", "freqHopping", "groupOrSequenceHopping", "resourceType", "sequenceId", and "spatialRelationInfoPos". The "srs-PosResourceId" parameter indicates the SRS used to identify the location of a specific SRS resource. The "transmissionComb" parameter defines the comb size N of the location SRS (e.g., N=2, 4, or 8), the comb offset of the first symbol of the location SRS resource (0 ... N-1), and the cyclic offset used to generate the reference sequence. "resourceMapping" (which includes "startPosition" and "nrofSymbols") defines the position of the first OFDM symbol of the location SRS resource in the time slot (e.g., 0, 1, 2, ..., 13) and the number of symbols for the location SRS resource (e.g., 1, 2, 4, 8, or 12). The `freqDomainShift` parameter defines the frequency domain location of the SRS resource. The `freqHopping` parameter (or `c-SRS`) defines the bandwidth of the SRS resource. The `groupOrSequenceHopping` parameter defines whether group or sequence hopping is used. Hopping modes are used to randomize sequence reuse in the system. The `resourceType` parameter defines the type of SRS resource (periodic, semi-persistent, aperiodic) and the periodicity of semi-persistent and periodic SRSs. The `sequenceId` parameter defines the sequence ID used to initialize pseudo-random group and sequence hopping. The `spatialRelationInfoPos` parameter defines the spatial relationship between the reference signal and the target SRS. The reference signal can be an SSB, CSI-RS, DL-PRS, or SRS.

[0173] Additional parameters include BWP information, which defines the BWP configuration of the SRS used for positioning, including the frequency domain position and the bandwidth, subcarrier spacing, and cyclic prefix of that bandwidth portion. The “inactivePosSRS-TimeAlignmentTimer” parameter indicates the timer value for the SRS used for positioning transmission. The “inactivePosSRS-RSRP-changeThreshold” parameter indicates the RSRP threshold for increasing / decreasing for time alignment verification.

[0174] The possible set of partial (a) parameters valid for multiple cells may include: “SRS-PosResourceSet”, “srs-PosResourceSetId”, “srs-PosResourceIdList”, “resourceType”, “SRS-PosResource”, “srs-PosResourceId”, “transmissionComb”, “resourceMapping” (“startPosition”, “nrofSymbols”), “freqDomainShift”, “freqHopping” (“c-SRS”), “groupOrSequenceHopping”, “resourceType”, and “sequenceId”. The possible set of partial (b) parameters valid for a single (serving / receiving) cell may include: “alpha”, “p0”, “pathlossReferenceRS-Pos”, “spatialRelationInfoPos”, BWP information, time alignment timers (e.g., timing advance timers), and RSRP change thresholds. However, specific implementations / deployments are free to divide the SRS used for locating parameters into two sets (partial (a) and partial (b)) as needed. In special cases, all parameters may be eligible for use in “part (a)” SRS, such as when path loss references or spatial relationships are not required.

[0175] The pre-configuration will include part of the parameter set (a). The remaining parameters (part of (b)) will be provided during the SRS activation process. Figure 7A and Figure 7B The process shown can then be followed as follows Figure 9A and Figure 9B Make the modifications as shown.

[0176] Figure 9A and Figure 9B An example delayed MT-LR procedure for a downlink- and uplink-based positioning method (e.g., multiple RTT) with pre-configured positioning SRS is illustrated according to various aspects of this disclosure. At phase 1, phases 1-21 of the delayed 5GC-MT-LR procedure for periodic or triggered location events, as specified in 3GPP TS 23.273, clause 6.3.1, are performed. Phases 1a, 1b, and 1c may be performed during the delayed MT-LR configuration phase of the delayed 5GC-MT-LR procedure for periodic or triggered location events (e.g., during phase 15 of the delayed 5GC-MT-LR procedure for periodic or triggered location events, as specified in 3GPP TS 23.273, clause 6.3.1).

[0177] At phase 1a, LMF 270 transmits an NRPPa location information request message to serving gNB 222, including a request for a pre-configured location SRS. This request may include one or more "Requested SRS Transmission Characteristics" (IEs), each defining the desired location SRS configuration. LMF 270 may include path loss reference, spatial relationships, and SSB information for each gNB in ​​the area. This "auxiliary information" may be used by the serving / receiving gNB 222 to compile a portion of the parameters (b) that will be valid for the current UE location at a later time. For example, for each considered cell ID, the auxiliary information may include a list of neighboring cells with SSB or DL-PRS information that can be used as a path loss reference or spatial relationship for location SRS.

[0178] At phase 1b, the serving gNB 222 determines one or more location SRS configurations and provides these configurations to the target device (UE 204) so ​​that the target device can send location SRS at a later time (i.e., the target device does not send any location SRS when pre-configured). Each location SRS configuration has the following characteristics: Figure 8 The associated identifier is shown. Each location SRS may have a validity period and / or a validity area. The "validity area" may be defined by a list of cell IDs that define where the SRS configuration is applicable / valid.

[0179] At phase 1c, the service gNB 222 provides the LMF 270 with a pre-configured set of location SRSs (e.g., one or more "SRS Configuration" IEs, where each location SRS has as follows). Figure 8 (As shown by the associated ID).

[0180] At phase 3, after (or slightly earlier) an event is detected, UE 204 transmits an SRS activation request message along with an RRC recovery request to receiving gNB 222. The SRS activation request message may include an identifier of the desired pre-configured SRS configuration to be activated (e.g., in priority order).

[0181] At phase 4, the receiving gNB 222 uses the Inactive Radio Network Temporary Identifier (I-RNTI) to identify the last serving gNB 222 and retrieves the UE context (including pre-configured positioning SRS information) using the Xn-AP UE context retrieval procedure. The receiving gNB 222 determines the positioning SRS configuration based on the pre-configuration during phase 1. The receiving gNB 222 may determine some parameters (b), such as path loss reference information (e.g., “alpha”, “p0”, “pathlossReferenceRS-Pos”) or spatial relation information (e.g., “spatialRelationInfoPos”) for the positioning SRS valid for the receiving gNB 222. The receiving gNB 222 may also determine the time alignment timer and RSRP change threshold (e.g., “inactivePosSRS-TimeAlignmentTimer”, “inactivePosSRS-RSRP-changeThreshold”). The receiving gNB 222 may use the auxiliary information received from LMF 270 at phase 1a to determine the above set of SRS parameters.

[0182] At phase 5, after receiving gNB 222, an SRS activation message can be transmitted to UE 204. This SRS activation message includes the ID of the pre-configured SRS to be activated and some (b) SRS information (e.g., path loss reference, spatial relationship, timing advance (TA) timer, and RSRP change threshold). The SRS activation message can be an RRC message, a MAC-CE, or a DCI. Then, UE 204 begins transmitting positioning SRS according to the activated configuration.

[0183] At stage 6, the gNB 222 receives an NRPPa location information update message from the LMF 270, which includes the ID of the activated location SRS.

[0184] At phase 7, the LMF 270 transmits an NRPPa measurement request message to the gNB / TRP group, which includes the location SRS measurement configuration (i.e., based on the ID received at phase 6).

[0185] At phase 8, gNB 222 transmits an RRC release message to UE 204 to release UE 204 into an RRC inactive state. If phase 5 does not occur, the RRC release message includes an SRS activation message. Then, various network entities execute... Figure 7B Stages 11-17 as exemplified in .

[0186] and Figure 7A and Figure 7BCompared to the process illustrated, no signaling is required for SRS configuration (phases 5, 6, 7, and 9), thus reducing SRS configuration latency and consequently reducing power consumption (i.e., reducing...). Figure 7A The UE "wake-up time" between stage 3 and stage 10.

[0187] Pre-configured SRS auxiliary data can consist of multiple pre-configured SRS configurations, each applicable to a different SRS-valid area within the network. Each pre-configured SRS configuration can be associated with an area identifier (ID). This area ID includes a list of cells that the UE can camp on (in RRC inactive state) or that the UE can connect to (in RRC connected state). The applicable area ID for the UE's location is selected based on the cell the UE camps on / connects to. If the UE camps on or connects to one of the cells indicated in the cell list within that area ID, the pre-configured SRS configuration is valid / selected.

[0188] Figure 10 Figure 1000 illustrates an example UE mobility scenario through multiple SRS validity areas according to various aspects of this disclosure. Figure 10 In the example, there are six area IDs (labeled "AreaID1" to "AreaID6"), and each area ID includes multiple cells (labeled "PCI1" to "PCI16"). Note that although... Figure 10 The example illustrates each physical cell site with a single cell / PCI, but this is for simplicity, and it should be understood that a cell site can support multiple cells. Furthermore, in Figure 10 In the examples, some cells may belong to more than one area ID. For example, PCI4 may belong to both AreaID1 and AreaID2. Similarly, PCI7 may belong to both AreaID3 and AreaID4.

[0189] For SRS configuration, refer to Figure 10 The UE can be configured using the pre-configured SRS configuration for each of AreaID1 through AreaID6. Since the UE is currently located in AreaID4, the pre-configured SRS configuration associated with AreaID4 is valid / selected if the UE is camped on or connected to one of the cells associated with areaID4 (e.g., PCI3, PCI7, PCI11, PCI15).

[0190] To enable greater network control over the transmission of location SRS (or location-related SRS) after cell reselection, the LPP “Area-ID-CellList” information element (IE) has been introduced for (pre)configured location SRS. Compared to the validity of DL-PRS auxiliary data, the “Area-ID-CellList” IE for location SRS will be UE-specific. If the UE camps on a cell whose ID is included in the “Area-ID-CellList” IE, the UE will be allowed to continue transmitting (associated) location SRS in the new cell after cell reselection. That is, if the UE participates in an uplink-based or downlink-and-uplink-based location process where the UE transmits location SRS and is handed over / reattached to a different cell, the UE can continue transmitting the same location SRS as long as that cell is included in the “Area-ID-CellList” IE.

[0191] Figure 11 An example RRC “SRS-PosRRC-Inactive” IE 1100 is illustrated according to various aspects of this disclosure. This IE configures one or more location SRS configurations for the UE to use when in RRC inactive state 430. Specifically, the “SRS-PosRRC-Inactive” IE 1100 provides a set of up to a maximum of “maxPreConfig” location SRS configurations, each of which can be identified by the “srs-PosID” field. The “srs-ValidityArea” field provides a list of cell IDs in which the SRS configurations are valid. If the UE reselects to a cell included in the LPP “Area-ID-CellList” IE, the UE is allowed to continue SRS transmission during and after the cell reselection. It should be noted that the “Area-ID-CellList” IE may not necessarily be consistent with the RNA, but may be a dedicated, UE-specific uplink location area.

[0192] The RRC "SRS-PosRRC-Inactive" IE 1100 avoids interrupting SRS transmission during cell reselection, which reduces the amount of SRS configuration signaling required, reduces the latency of the positioning session, and thus reduces power consumption at the target device.

[0193] Enhancements to SRS configuration regarding TA verification and maintenance have been introduced for LPHAP. For example, a region-specific TA timer (e.g., with a large value) for SRS validity area can be provided for UEs in an RRC inactive state for location purposes. A UE can start or restart the region-specific TA timer (also referred to as the "SRS validity timer," "TA validity timer," "validity timer," or "TA timer") when it receives a TA command, and stop SRS transmission when the region-specific TA timer expires. When a UE reselects to a cell outside the SRS validity area (or simply the "validity area"), it can stop the region-specific TA timer. In some cases, the network node determining the validity area across gNBs and / or coordinating can be a location server (e.g., LMF 270).

[0194] In some cases, to determine the uplink timing of the SRS sent for positioning by a UE in an RRC inactive state within the SRS positioning validity area, the valid TA can be determined in the following ways: (1) the downlink reference timing follows the downlink timing of the currently camped cell, (2) by default, the UE maintains the TA from the previous serving cell (the UE can adjust its uplink timing according to changes in the downlink reference timing), and / or (3) if configured by the network, the UE can autonomously adjust the TA when performing cell reselection, subject to the UE's capabilities.

[0195] Figure 12 Figure 1200 illustrates the relationship between the validity timer "inactivePosSRS-TimeAlignmentTimer" and SRS transmission according to various aspects of this disclosure. Currently, the validity timer "inactivePosSRS-TimeAlignmentTimer" is entirely controlled by the network. As described above and as... Figure 12 As shown, the UE starts or restarts a validity area-specific TA timer upon receiving a TA command, and stops SRS transmission when the validity area-specific TA timer expires. Currently, there are no rules for the UE to implicitly restart the validity timer, nor are there rules for the UE to implicitly extend the validity timer. Therefore, each time the validity timer expires, the UE needs to switch to RRC connection mode to obtain a new TA command / SRS configuration, which is costly in terms of power consumption. It should be noted that the network does not maintain the validity timer and therefore is unaware of its expiration.

[0196] Therefore, this disclosure provides techniques for extending or restarting implicit validity area-specific TA timers, particularly for LPHAP operation. As a first technique described herein, implicit rules can be provided for restarting (or extending) the current TA of a UE. For example, if configured by the network and influenced by UE capabilities, the TA timer can be extended or restarted when a cell reselection is performed within the same area, provided it is performed autonomously by the UE to adjust its TA. This behavior may apply when the downlink reference timing difference between the last camped cell and the currently camped cell exceeds a threshold.

[0197] As a first option, the extension amount can be associated with or a function of the initial value of the TA timer. For example, in some cases, the extension amount may not be greater than the initial value of the TA timer. As a second option, the extension amount can be configured together with the initial TA timer value (i.e., when the UE receives a TA command).

[0198] On the UE side, in some cases, the UE may autonomously extend or restart the TA timer whenever the signal strength (e.g., signal-to-noise ratio (SNR), RSRP, and / or RSRQ) of a given camped cell in the same valid area exceeds a configured threshold. In some cases, the network may configure (1) a signal strength threshold, (2) an observation window (of length N) for checking the threshold (meaning, for example, the UE may restart the timer only after measuring a signal strength that satisfies the threshold for an observation window of length N), and / or (3) the number of measurement instances M for checking the threshold (meaning, for example, the UE may restart the timer only after measuring a signal strength that satisfies the threshold for M consecutive measurement moments).

[0199] In some cases, the network can define a timer extension area within the SRS validity area that allows the UE to extend / restart the validity timer. As a first option, the timer extension area can be a subset of the SRS validity area. As a second option, the timer extension area can be the same as the SRS validity area. In some cases, the network can provide a list of cells included in the timer extension area.

[0200] Figure 13 Figure 1300 illustrates an example of a timer extending a cell area according to various aspects of this disclosure. Figure 13 In this diagram, each circle represents a cell, and the valid area is defined as all the instances of the cell. Figure 13 In the example, the timer extension region is a subset of the SRS validity region. In other words, the cells in the timer extension region are a subset of the cells in the validity region.

[0201] In some cases, based on SRS reception at the base station, the network can determine the SRS validity timer on the UE side. In other cases, the network can provide this information to the UE via a paging procedure (referred to as "paging-based timer extension"). The paging message can indicate to the UE whether to restart the timer or extend the timer. In the latter case, the paging message can also indicate the extended value.

[0202] In some cases, the network can configure a list of cells for which the UE can restart its validity timer, a list of cells for which the UE can extend its validity timer by a pre-configured value, or both. In other cases, the network can additionally or alternatively configure a list of cells for which the UE may not extend or restart its validity timer. For cells for which the UE may not extend or restart its validity timer, the UE is expected to follow currently defined behavior (i.e., the UE transitions to an RRC connected state to obtain new TA commands and SRS configurations, such as...). Figure 12 (As shown).

[0203] Figure 14 This is a diagram 1400 illustrating example SRS validity areas according to various aspects of this disclosure. Figure 14 In this diagram, each circle represents a cell, and the SRS validity area is defined as all the instances of the cell. Figure 14 In the example, the SRS validity region includes a subset of cells that allow the UE to restart the validity timer after cell reselection, a subset of cells that allow the UE to extend the validity timer after cell reselection, and the expected behavior of the UE to follow the currently defined behavior (i.e., the UE transitions to the RRC connected state to obtain new TA commands and SRS configuration, such as...). Figure 12 A subset of the communities shown.

[0204] In some cases, the aforementioned techniques can be applied to other uplink transmissions (reference signals or channels) when the RRC is inactive or idle (collectively referred to as "connectionless" RRC states). For example, uplink transmissions may include SRS, SL-PRS, UL-DMRS, Physical Uplink Shared Channel (PUSCH), and / or Physical Uplink Control Channel (PUCCH) transmissions.

[0205] Figure 15 An example method 1500 for wireless communication according to various aspects of this disclosure is illustrated. In one aspect, method 1500 may be performed by a UE (e.g., any of the UEs described herein).

[0206] At operation 1510, the UE performs cell reselection from a first camped cell to a second camped cell while in an RRC disconnected state, wherein the first camped cell and the second camped cell are within the same uplink channel transmission validity area. In one aspect, operation 1510 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning components 342, any or all of which can be considered as components for performing the operation.

[0207] At operation 1520, in response to cell reselection, the UE extends or restarts the TA validity timer based on one or more criteria, wherein the TA validity timer indicates a period of time during which the UE is permitted to transmit one or more uplink channels while in an RRC disconnected state. In one aspect, operation 1520 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning components 342, any or all of which may be considered as components for performing the operation.

[0208] Figure 16 An example method 1600 for wireless communication according to various aspects of this disclosure is illustrated. In one aspect, method 1600 may be performed by a network node (e.g., any of the base stations or base station components described herein).

[0209] At operation 1610, when the UE is operating in an RRC disconnected state, the network node receives one or more uplink channels from the UE (e.g., any of the UEs described herein). In one aspect, operation 1610 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or positioning components 388, any or all of which may be considered as components for performing the operation.

[0210] At operation 1620, the network node sends a paging message to the UE configuring the UE to restart or extend the TA validity timer, wherein the TA validity timer indicates a time period during which the UE is permitted to transmit one or more uplink channels while in an RRC disconnected state. In one aspect, operation 1620 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or positioning components 388, any or all of which can be considered as components for performing the operation.

[0211] It should be understood that the technical advantage of methods 1500 and 1600 is to reduce power consumption at the UE by reducing the need for the UE to switch to RRC connection mode to obtain new TA commands.

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

[0213] Specific implementation examples are described in the following numbered clauses.

[0214] Clause 1. A method of wireless communication performed by a user equipment (UE), the method comprising: performing a cell reselection from a first camped cell to a second camped cell while in a Radio Resource Control (RRC) disconnected state, wherein the first camped cell and the second camped cell are in the same uplink channel transmission validity area; and in response to the cell reselection, extending or restarting a Timing Adjustment (TA) validity timer based on one or more criteria, wherein the TA validity timer indicates a period of time during which the UE is permitted to transmit one or more uplink channels while in the RRC disconnected state.

[0215] Clause 2. The method according to Clause 1, wherein the one or more criteria include: determining that the difference in downlink reference timing between the first stationary cell and the second stationary cell is greater than a threshold.

[0216] Clause 3. The method according to any one of Clauses 1 to 2, wherein extending or restarting the TA validity timer includes extending the TA validity timer.

[0217] Clause 4. The method according to Clause 3, wherein: the amount of the extension of the TA validity timer is a function of the initial value of the TA validity timer, or the amount of the extension of the TA validity timer is configured to the UE using the initial value of the TA validity timer.

[0218] Clause 5. The method according to any one of Clauses 1 to 4, wherein extending or restarting the TA validity timer includes restarting the TA validity timer.

[0219] Clause 6. The method according to Clause 5, wherein one or more criteria include: the signal strength of the second camp cell is greater than a configuration threshold within a configuration time window.

[0220] Clause 7. The method according to Clause 6, the method further comprising: receiving the configuration threshold and the configuration time window from a network entity.

[0221] Clause 8. The method according to any one of Clauses 6 to 7, wherein the configuration time window includes: the length of time or the number of consecutive measurement opportunities.

[0222] Clause 9. The method according to any one of Clauses 1 to 8, the method further comprising: receiving a configuration of a timer extension region, within which the UE is allowed to autonomously extend or restart the TA validity timer.

[0223] Clause 10. The method according to Clause 9, wherein the timer extension region is a sub-region of the uplink channel transmission validity region, or is the same as the uplink channel transmission validity region.

[0224] Clause 11. The method according to any one of Clauses 9 to 10, wherein the configuration includes a list of cells included in the timer extension region.

[0225] Clause 12. The method according to any one of Clauses 1 to 11, the method further comprising: receiving from the second camped cell a paging message configuring the UE to restart the TA validity timer.

[0226] Clause 13. The method according to any one of Clauses 1 to 12, the method further comprising: receiving from the second camped cell a paging message configuring the UE to extend the TA validity timer by a certain extension amount.

[0227] Clause 14. The method according to Clause 13, the method further comprising: receiving the extended quantity from the second resident cell.

[0228] Clause 15. The method according to any one of Clauses 1 to 14, the method further comprising: receiving a first list of cells that allow the UE to restart the TA validity timer; receiving a second list of cells that allow the UE to extend the TA validity timer; receiving a third list of cells that do not allow the UE to restart or extend the TA validity timer; or any combination thereof.

[0229] Clause 16. The method according to any one of Clauses 1 to 15, wherein the one or more uplink channels comprise: one or more sounding reference signal (SRS) resources, one or more side link positioning reference signal (SL-PRS) resources, one or more uplink demodulation reference signals (UL-DMRS) and physical uplink shared channel (PUSCH) or physical uplink control channel (PUCCH).

[0230] Clause 17. The method according to any one of Clauses 1 to 16, wherein: the uplink channel transmits a valid region that is a probe reference signal (SRS) for locating a valid region, and the one or more uplink channels are one or more SRSs for locating resources.

[0231] Clause 18. The method according to any one of Clauses 1 to 17, wherein the RRC disconnected state includes: RRC inactive state or RRC idle state.

[0232] Clause 19. The method according to any one of Clauses 1 to 18, wherein the TA validity timer indicates the time period during which the UE is allowed to transmit the one or more uplink channels while in the RRC disconnected state without updating the UE's uplink transmission timing.

[0233] Clause 20. A method of wireless communication performed by a network node, the method comprising: receiving one or more uplink channels from a user equipment (UE) while the UE is operating in a Radio Resource Control (RRC) disconnected state; and sending a paging message to the UE configuring the UE to restart or extend a timing advance (TA) validity timer, wherein the TA validity timer indicates a period of time during which the UE is permitted to transmit the one or more uplink channels while in the RRC disconnected state.

[0234] Clause 21. The method according to Clause 20, wherein the paging message configures the UE to restart the TA validity timer.

[0235] Clause 22. The method according to any one of Clauses 20 to 21, wherein the paging message configures the UE to extend the TA validity timer by a certain extension amount.

[0236] Clause 23. The method according to Clause 22, wherein the paging message further includes the extended quantity.

[0237] Clause 24. The method according to any one of Clauses 20 to 23, wherein the TA validity timer indicates the time period during which the UE is allowed to transmit the one or more uplink channels while in the RRC disconnected state without updating the UE's uplink transmission timing.

[0238] Clause 25. 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: perform cell reselection from a first camping cell to a second camping cell while in a Radio Resource Control (RRC) disconnected state, wherein the first camping cell and the second camping cell are in the same uplink channel transmission validity area; and in response to the cell reselection, extend or restart a Timing Adjustment (TA) validity timer based on one or more criteria, wherein the TA validity timer indicates a period of time during which the UE is permitted to transmit one or more uplink channels while in the RRC disconnected state.

[0239] Clause 26. The UE as described in Clause 25, wherein the one or more criteria include: determining that the difference in downlink reference timing between the first camped cell and the second camped cell is greater than a threshold.

[0240] Clause 27. The UE according to any one of Clauses 25 to 26, wherein the one or more processors configured to extend or restart the TA validity timer includes the one or more processors configured individually or in combination to extend the TA validity timer.

[0241] Clause 28. The UE as described in Clause 27, wherein: the amount of the extension of the TA validity timer is a function of the initial value of the TA validity timer, or the amount of the extension of the TA validity timer is configured to the UE using the initial value of the TA validity timer.

[0242] Clause 29. The UE according to any one of Clauses 25 to 28, wherein the one or more processors configured to extend or restart the TA validity timer includes the one or more processors configured individually or in combination to restart the TA validity timer.

[0243] Clause 30. The UE as described in Clause 29, wherein one or more of the criteria include: the signal strength of the second camped cell is greater than a configured threshold within a configured time window.

[0244] Clause 31. The UE according to Clause 30, wherein the one or more processors are individually or in combination further configured to receive the configuration threshold and the configuration time window from the network entity via the one or more transceivers.

[0245] Clause 32. The UE according to any one of Clauses 30 to 31, wherein the configuration time window includes: the length of time or the number of consecutive measurement opportunities.

[0246] Clause 33. The UE according to any one of Clauses 25 to 32, wherein the one or more processors are individually or in combination further configured to: receive via the one or more transceivers a configuration of a timer extension region, within which the UE is allowed to autonomously extend or restart the TA validity timer.

[0247] Clause 34. The UE as described in Clause 33, wherein the timer extension region is: a sub-region of the uplink channel transmission validity region, or the same as the uplink channel transmission validity region.

[0248] Clause 35. The UE pursuant to any one of Clauses 33 to 34, wherein the configuration includes a list of cells included in the timer extension region.

[0249] Clause 36. The UE according to any one of Clauses 25 to 35, wherein the one or more processors are individually or in combination further configured to receive, via the one or more transceivers, from the second camped cell a paging message configuring the UE to restart the TA validity timer.

[0250] Clause 37. The UE according to any one of Clauses 25 to 36, wherein the one or more processors are individually or in combination further configured to: receive, via the one or more transceivers, from the second camped cell a paging message configuring the UE to extend the TA validity timer by a certain extension amount.

[0251] Clause 38. The UE as described in Clause 37, wherein the one or more processors are further configured individually or in combination to receive the extended quantity from the second camped cell via the one or more transceivers.

[0252] Clause 39. The UE pursuant to any one of Clauses 25 to 38, wherein the one or more processors are individually or in combination further configured to: receive via the one or more transceivers a first list of cells that allow the UE to restart the TA validity timer; receive via the one or more transceivers a second list of cells that allow the UE to extend the TA validity timer; receive via the one or more transceivers a third list of cells that do not allow the UE to restart or extend the TA validity timer; or any combination thereof.

[0253] Clause 40. The UE pursuant to any one of Clauses 25 to 39, wherein the one or more uplink channels comprise: one or more sounding reference signal (SRS) resources, one or more sidelink positioning reference signal (SL-PRS) resources, one or more uplink demodulation reference signals (UL-DMRS) and physical uplink shared channel (PUSCH) or physical uplink control channel (PUCCH).

[0254] Clause 41. The UE according to any one of Clauses 25 to 40, wherein: the uplink channel transmits a valid region that is a probe reference signal (SRS) for locating a valid region, and the one or more uplink channels are one or more SRSs for locating resources.

[0255] Clause 42. The UE pursuant to any one of Clauses 25 to 41, wherein the RRC disconnected state includes: RRC inactive state or RRC idle state.

[0256] Clause 43. A UE pursuant to any one of Clauses 25 to 42, wherein the TA validity timer indicates the time period during which the UE is permitted to transmit the one or more uplink channels while in the RRC disconnected state without updating the UE's uplink transmission timing.

[0257] Clause 44. A network node 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 one or more uplink channels from the user equipment (UE) via the one or more transceivers when the user equipment (UE) is operating in a Radio Resource Control (RRC) disconnected state; and send a paging message to the UE via the one or more transceivers configuring the UE to restart or extend a Timing Advance (TA) validity timer, wherein the TA validity timer indicates a period of time during which the UE is permitted to transmit the one or more uplink channels while in the RRC disconnected state.

[0258] Clause 45. A network node as described in Clause 44, wherein the paging message configures the UE to restart the TA validity timer.

[0259] Clause 46. A network node pursuant to any one of Clauses 44 to 45, wherein the paging message configures the UE to extend the TA validity timer by a certain amount.

[0260] Clause 47. The network node as described in Clause 46, wherein the paging message further includes the extended quantity.

[0261] Clause 48. A network node pursuant to any one of Clauses 44 to 47, wherein the TA validity timer indicates the time period during which the UE is permitted to transmit the one or more uplink channels while in the RRC disconnected state without updating the UE's uplink transmission timing.

[0262] Clause 49. A user equipment (UE) comprising: means for performing cell reselection from a first camped cell to a second camped cell while in a Radio Resource Control (RRC) disconnected state, wherein the first camped cell and the second camped cell are in the same uplink channel transmission validity area; and means for extending or restarting a Timing Adjustment (TA) validity timer based on one or more criteria in response to the cell reselection, wherein the TA validity timer indicates a period of time during which the UE is permitted to transmit one or more uplink channels while in the RRC disconnected state.

[0263] Clause 50. The UE as described in Clause 49, wherein the one or more criteria include: determining that the difference in downlink reference timing between the first camped cell and the second camped cell is greater than a threshold.

[0264] Clause 51. The UE according to any one of Clauses 49 to 50, wherein the component for extending or restarting the TA validity timer includes a component for extending the TA validity timer.

[0265] Clause 52. The UE according to Clause 51, wherein: the amount of the extension of the TA validity timer is a function of the initial value of the TA validity timer, or the amount of the extension of the TA validity timer is configured to the UE using the initial value of the TA validity timer.

[0266] Clause 53. The UE according to any one of Clauses 49 to 52, wherein the component for extending or restarting the TA validity timer includes a component for restarting the TA validity timer.

[0267] Clause 54. The UE as described in Clause 53, wherein one or more of the criteria include: the signal strength of the second camped cell is greater than a configured threshold within a configured time window.

[0268] Clause 55. The UE as described in Clause 54 further includes: a component for receiving the configuration threshold and the configuration time window from a network entity.

[0269] Clause 56. The UE according to any one of Clauses 54 to 55, wherein the configuration time window includes: the length of time or the number of consecutive measurement opportunities.

[0270] Clause 57. The UE according to any one of Clauses 49 to 56, the UE further includes: a component for receiving configuration of a timer extension region, within which the UE is allowed to autonomously extend or restart the TA validity timer.

[0271] Clause 58. The UE as described in Clause 57, wherein the timer extension region is: a sub-region of the uplink channel transmission validity region, or the same as the uplink channel transmission validity region.

[0272] Clause 59. The UE pursuant to any one of Clauses 57 to 58, wherein the configuration includes a list of cells included in the timer extension region.

[0273] Clause 60. The UE according to any one of Clauses 49 to 59, the UE further comprising: a component for receiving from the second camped cell a paging message configuring the UE to restart the TA validity timer.

[0274] Clause 61. The UE according to any one of Clauses 49 to 60, the UE further comprising: a component for receiving from the second camped cell a paging message configuring the UE to extend the TA validity timer by a certain extension amount.

[0275] Clause 62. The UE according to Clause 61, the UE further includes: a component for receiving the extended amount from the second camped cell.

[0276] Clause 63. The UE according to any one of Clauses 49 to 62, the UE further comprising: means for receiving a first list of cells that allow the UE to restart the TA validity timer; means for receiving a second list of cells that allow the UE to extend the TA validity timer; means for receiving a third list of cells that do not allow the UE to restart or extend the TA validity timer; or any combination thereof.

[0277] Clause 64. The UE pursuant to any one of Clauses 49 to 63, wherein the one or more uplink channels comprise: one or more sounding reference signal (SRS) resources, one or more sidelink positioning reference signal (SL-PRS) resources, one or more uplink demodulation reference signals (UL-DMRS) and physical uplink shared channel (PUSCH) or physical uplink control channel (PUCCH).

[0278] Clause 65. The UE according to any one of Clauses 49 to 64, wherein: the uplink channel transmits a valid region that is a probe reference signal (SRS) for locating a valid region, and the one or more uplink channels are one or more SRSs for locating resources.

[0279] Clause 66. The UE pursuant to any one of Clauses 49 to 65, wherein the RRC disconnected state includes: RRC inactive state or RRC idle state.

[0280] Clause 67. A UE pursuant to any one of Clauses 49 to 66, wherein the TA validity timer indicates the time period during which the UE is permitted to transmit the one or more uplink channels while in the RRC disconnected state without updating the UE's uplink transmission timing.

[0281] Clause 68. A network node comprising: means for receiving one or more uplink channels from a user equipment (UE) when the UE is operating in a Radio Resource Control (RRC) disconnected state; and means for sending a paging message to the UE configuring the UE to restart or extend a timing advance (TA) validity timer, wherein the TA validity timer indicates a period of time during which the UE is permitted to transmit the one or more uplink channels while in the RRC disconnected state.

[0282] Clause 69. A network node as described in Clause 68, wherein the paging message configures the UE to restart the TA validity timer.

[0283] Clause 70. A network node pursuant to any one of Clauses 68 to 69, wherein the paging message configures the UE to extend the TA validity timer by a certain amount.

[0284] Clause 71. The network node as described in Clause 70, wherein the paging message further includes the extended quantity.

[0285] Clause 72. A network node pursuant to any one of Clauses 68 to 71, wherein the TA validity timer indicates the time period during which the UE is permitted to transmit the one or more uplink channels while in the RRC disconnected state without updating the UE's uplink transmission timing.

[0286] Clause 73. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), allow the UE to: perform a cell reselection from a first camping cell to a second camping cell while in a Radio Resource Control (RRC) disconnected state, wherein the first camping cell and the second camping cell are within the same uplink channel transmission validity area; and, in response to the cell reselection, extend or restart a Timing Adjustment (TA) validity timer based on one or more criteria, wherein the TA validity timer indicates a period of time during which the UE is permitted to transmit one or more uplink channels while in the RRC disconnected state.

[0287] Clause 74. The non-transitory computer-readable medium as described in Clause 73, wherein the one or more criteria include: determining that the difference in downlink reference timing between the first stationary cell and the second stationary cell is greater than a threshold.

[0288] Clause 75. A non-transitory computer-readable medium according to any one of Clauses 73 to 74, wherein the computer-executable instructions that cause the UE to extend or restart the TA validity timer when executed by the UE include computer-executable instructions that cause the UE to extend the TA validity timer when executed by the UE.

[0289] Clause 76. The non-transitory computer-readable medium according to Clause 75, wherein: the amount of extension of the TA validity timer is a function of the initial value of the TA validity timer, or the amount of extension of the TA validity timer is configured to the UE using the initial value of the TA validity timer.

[0290] Clause 77. A non-transitory computer-readable medium according to any one of Clauses 73 to 76, wherein the computer-executable instructions that cause the UE to extend or restart the TA validity timer when executed by the UE include computer-executable instructions that cause the UE to restart the TA validity timer when executed by the UE.

[0291] Clause 78. The non-transitory computer-readable medium as described in Clause 77, wherein one or more of the criteria include: the signal strength of the second camped cell is greater than a configured threshold within a configured time window.

[0292] Clause 79. The non-transitory computer-readable medium according to Clause 78 further includes computer-executable instructions that, when executed by the UE, cause the UE to: receive the configuration threshold and the configuration time window from a network entity.

[0293] Clause 80. A non-transitory computer-readable medium according to any one of Clauses 78 to 79, wherein the configuration time window includes: a time length or a number of consecutive measurement opportunities.

[0294] Clause 81. A non-transitory computer-readable medium according to any one of Clauses 73 to 80, the non-transitory computer-readable medium further comprising computer-executable instructions, which, when executed by the UE, cause the UE to: receive a configuration of a timer extension region, within which the UE is permitted to autonomously extend or restart the TA validity timer.

[0295] Clause 82. The non-transitory computer-readable medium according to Clause 81, wherein the timer extension region is: a sub-region of the uplink channel transmission validity region, or the same as the uplink channel transmission validity region.

[0296] Clause 83. A non-transitory computer-readable medium pursuant to any one of Clauses 81 to 82, wherein the configuration includes a list of cells included in the timer extension region.

[0297] Clause 84. The non-transitory computer-readable medium according to any one of Clauses 73 to 83, the non-transitory computer-readable medium further comprising computer-executable instructions, which, when executed by the UE, cause the UE to: receive from the second camped cell a paging message configuring the UE to restart the TA validity timer.

[0298] Clause 85. The non-transitory computer-readable medium according to any one of Clauses 73 to 84, the non-transitory computer-readable medium further comprising computer-executable instructions, which, when executed by the UE, cause the UE to: receive from the second camped cell a paging message configuring the UE to extend the TA validity timer by a certain extension amount.

[0299] Clause 86. The non-transitory computer-readable medium according to Clause 85 further includes computer-executable instructions that, when executed by the UE, cause the UE to: receive the extended quantity from the second camped cell.

[0300] Clause 87. A nontransitory computer-readable medium according to any one of Clauses 73 to 86, the nontransitory computer-readable medium further comprising computer-executable instructions, which, when executed by the UE, cause the UE to: receive a first list of cells that allow the UE to restart the TA validity timer; receive a second list of cells that allow the UE to extend the TA validity timer; receive a third list of cells that do not allow the UE to restart or extend the TA validity timer; or any combination thereof.

[0301] Clause 88. A non-transitory computer-readable medium pursuant to any one of Clauses 73 to 87, wherein the one or more uplink channels comprise: one or more sounding reference signal (SRS) resources, one or more sidelink positioning reference signal (SL-PRS) resources, one or more uplink demodulation reference signals (UL-DMRS) and a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).

[0302] Clause 89. A non-transitory computer-readable medium according to any one of Clauses 73 to 88, wherein: the uplink channel transmits a valid region that is a probe reference signal (SRS) for locating a valid region, and the one or more uplink channels are one or more SRSs for locating resources.

[0303] Clause 90. A nontransitory computer-readable medium pursuant to any one of Clauses 73 to 89, wherein the RRC disconnected state includes: an RRC inactive state or an RRC idle state.

[0304] Clause 91. A non-transitory computer-readable medium according to any one of Clauses 73 to 90, wherein the TA validity timer indicates the time period during which the UE is permitted to transmit the one or more uplink channels while in the RRC disconnected state without updating the UE's uplink transmission timing.

[0305] Clause 92. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network node, cause the network node to: receive one or more uplink channels from a user equipment (UE) while the UE is operating in a Radio Resource Control (RRC) disconnected state; and send a paging message to the UE configuring the UE to restart or extend a Timing Advance (TA) validity timer, wherein the TA validity timer indicates a period of time during which the UE is permitted to transmit one or more uplink channels while in the RRC disconnected state.

[0306] Clause 93. The non-transitory computer-readable medium as described in Clause 92, wherein the paging message configures the UE to restart the TA validity timer.

[0307] Clause 94. A non-transitory computer-readable medium according to any one of Clauses 92 to 93, wherein the paging message configures the UE to extend the TA validity timer by an extension amount.

[0308] Clause 95. The non-transitory computer-readable medium as described in Clause 94, wherein the paging message further includes the extended quantity.

[0309] Clause 96. A non-transitory computer-readable medium according to any one of Clauses 92 to 95, wherein the TA validity timer indicates the time period during which the UE is permitted to transmit the one or more uplink channels while in the RRC disconnected state without updating the UE's uplink transmission timing.

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

[0311] 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, but such specific implementation decisions should not be construed as departing from the scope of this disclosure.

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

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

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

[0315] 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 expressly 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 expressly stated as limited to the singular. Therefore, as used herein, the articles “a,” “an,” “the,” and “the” are intended to include one or more of the described elements. Furthermore, 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 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: Cell reselection from the first camping cell to the second camping cell is performed when the radio resource control (RRC) is in a disconnected state, wherein the first camping cell and the second camping cell are in the same uplink channel transmission validity area; as well as In response to the cell reselection, the timing adjustment (TA) validity timer is extended or restarted based on one or more criteria, wherein the TA validity timer indicates a period of time during which the UE is allowed to transmit one or more uplink channels while in the RRC disconnected state.

2. The UE according to claim 1, wherein the one or more standards include: It is determined that the difference in downlink reference timing between the first stationed cell and the second stationed cell is greater than a threshold.

3. The UE of claim 1, wherein the one or more processors configured to extend or restart the TA validity timer includes the one or more processors configured individually or in combination to extend the TA validity timer.

4. The UE according to claim 3, wherein: The extension of the TA validity timer is a function of the initial value of the TA validity timer, or The extended amount of the TA validity timer is configured to the UE using the initial value of the TA validity timer.

5. The UE of claim 1, wherein the one or more processors configured to extend or restart the TA validity timer includes the one or more processors configured individually or in combination to restart the TA validity timer.

6. The UE of claim 5, wherein the one or more standards comprise: The signal strength of the second stationed cell is greater than the configured threshold within the configured time window.

7. The UE of claim 6, wherein the one or more processors are further configured individually or in combination to: The configuration threshold and the configuration time window are received from the network entity via the one or more transceivers.

8. The UE according to claim 6, wherein the configuration time window includes: Duration, or The number of times continuous measurement is performed.

9. The UE of claim 1, wherein the one or more processors are further configured individually or in combination to: The configuration of the timer extension region received via the one or more transceivers allows the UE to autonomously extend or restart the TA validity timer within the timer extension region.

10. The UE of claim 9, wherein the timer extension region: It is a sub-region of the uplink channel transmission validity region, or It is the same as the uplink channel transmission validity area.

11. The UE of claim 9, wherein the configuration includes a list of cells included in the timer extension region.

12. The UE of claim 1, wherein the one or more processors are further configured individually or in combination to: The UE is received from the second camped cell via one or more transceivers as a paging message that configures the UE to restart the TA validity timer.

13. The UE of claim 1, wherein the one or more processors are further configured individually or in combination to: The UE is configured to extend the TA validity timer by a certain amount by receiving a paging message from the second camped cell via the one or more transceivers.

14. The UE of claim 13, wherein the one or more processors are further configured individually or in combination to: The extended quantity is received from the second residential cell via the one or more transceivers.

15. The UE of claim 1, wherein the one or more processors are further configured individually or in combination to: Receive, via the one or more transceivers, a first list of cells that allow the UE to restart the TA validity timer; Receive a second list of cells that allow the UE to extend the TA validity timer via the one or more transceivers; Receive a third list of cells that the UE is not allowed to restart or extend the TA validity timer via the one or more transceivers; or Any combination of them.

16. The UE of claim 1, wherein the one or more uplink channels comprise: One or more Sounding Reference Signal (SRS) resources, One or more sidelink positioning reference signal (SL-PRS) resources, One or more uplink demodulation reference signals (UL-DMRS) and physical uplink shared channel (PUSCH), or Physical Uplink Control Channel (PUCCH).

17. The UE according to claim 1, wherein: The uplink channel transmits a valid region, which is a detection reference signal (SRS) used to locate the valid region. The one or more uplink channels are one or more SRSs used for locating resources.

18. The UE according to claim 1, wherein the RRC disconnected state includes: RRC inactive state, or RRC is in idle state.

19. The UE of claim 1, wherein the TA validity timer indicates the time period during which the UE is allowed to transmit the one or more uplink channels while in the RRC disconnected state without updating the UE's uplink transmission timing.

20. A network node, the network node 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: When the user equipment (UE) is operating in a Radio Resource Control (RRC) disconnected state, one or more uplink channels are received from the UE via the one or more transceivers; as well as The paging message is sent to the UE via the one or more transceivers to configure the UE to restart or extend the timing advance (TA) validity timer, wherein the TA validity timer indicates a period of time during which the UE is allowed to transmit the one or more uplink channels while in the RRC disconnected state.

21. The network node of claim 20, wherein the paging message configures the UE to restart the TA validity timer.

22. The network node according to claim 20, wherein the paging message configures the UE to extend the TA validity timer by a certain amount.

23. The network node of claim 22, wherein the paging message further includes the extended quantity.

24. The network node of claim 20, wherein the TA validity timer indicates the time period during which the UE is allowed to transmit the one or more uplink channels while in the RRC disconnected state without updating the UE's uplink transmission timing.

25. A method for wireless communication performed by a user equipment (UE), the method comprising: Cell reselection from the first camping cell to the second camping cell is performed when the radio resource control (RRC) is in a disconnected state, wherein the first camping cell and the second camping cell are in the same uplink channel transmission validity area; as well as In response to the cell reselection, the timing adjustment (TA) validity timer is extended or restarted based on one or more criteria, wherein the TA validity timer indicates a period of time during which the UE is allowed to transmit one or more uplink channels while in the RRC disconnected state.

26. The method according to claim 25, further comprising: The configuration of the receive timer extension region allows the UE to autonomously extend or restart the TA validity timer within the timer extension region.

27. The method of claim 25, further comprising: Receive a paging message from the second camped cell to configure the UE to restart the TA validity timer.

28. The method of claim 25, further comprising: Receive a paging message from the second camped cell that configures the UE to extend the TA validity timer by a certain amount.

29. The method according to claim 25, further comprising: Receive a first list of cells that allow the UE to restart the TA validity timer; Receive a second list of cells that allow the UE to extend the TA validity timer; Receive a third list of cells from which the UE is not allowed to restart or extend the TA validity timer; or Any combination of them.

30. A method for wireless communication performed by a network node, the method comprising: When the user equipment (UE) is operating in a Radio Resource Control (RRC) disconnected state, one or more uplink channels are received from the UE; as well as Send a paging message to the UE to configure the UE to restart or extend the timing advance (TA) validity timer, wherein the TA validity timer indicates a period of time during which the UE is allowed to transmit the one or more uplink channels while in the RRC disconnected state.

Images