Method and apparatus for SRS configuration with activity region

Abstract

Aspects of the present disclosure relate to methods and apparatus for sounding reference signal (SRS) configuration with a region of validity. In accordance with an embodiment of the present disclosure, a user equipment (UE) may include: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive a first configuration including an area-specific time alignment timer associated with an SRS validity area; and transmitting, when the UE is in a non-connected state, an indication to acquire, activate, or deactivate a second configuration associated with the SRS validity region, where the second configuration includes an SRS configuration, a time alignment configuration, or a timing advance (TA) command.

Description

TECHNICAL FIELD

[0001] This disclosure relates to wireless communication, and more specifically to methods and apparatus for sounding reference signal (SRS) configuration with validity area. BACKGROUND

[0002] A wireless communication system can include one or more network communication devices, such as a base station (BS), which can support wireless communication for one or more user communication devices, which can also be referred to in other ways as user equipment (UE) or other suitable terminology. A wireless communication system can support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system, such as time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.). Moreover, a wireless communication system can support wireless communication across various radio access technologies, including third generation (3G) radio access technologies, fourth generation (4G) radio access technologies, fifth generation (5G) radio access technologies, and beyond 5G other suitable radio access technologies (e.g., sixth generation (6G)). SUMMARY

[0003] The article “a” preceding an element does not exclude the existence of additional such elements, and a single element can be employed. The term “at least one” is used to include one or more elements. The term “or” is used to refer to a nonexclusive or, such that “A or B” means A, B, or AB. The term “based on” is used to mean “based, at least in part, on” unless otherwise indicated. The term “set” is used to mean one or more elements. The term “plurality” is used to mean at least two elements.

[0004] Some embodiments of the methods and devices described herein can include a UE for wireless communication. The UE can include at least one memory and at least one processor coupled with the at least one memory and configured to cause the UE to receive a first configuration including a zone-specific time alignment timer associated with a SRS validity zone, and transmit, while the UE is in a non-connected state, an indication for acquiring, activating, or deactivating a second configuration associated with the SRS validity zone, where the second configuration includes a SRS configuration, a time alignment configuration, or a timing advance (TA) command.

[0005] In some embodiments of the UE described herein, the indication is a SRS configuration request or a SRS activation request, and the at least one processor is further configured to cause the UE to receive, in response to the SRS configuration request or the SRS activation request, the TA command for a successfully completed random access procedure.

[0006] In some embodiments of the UE described herein, the indication is a TA command request, and the at least one processor is further configured to cause the UE to receive, in response to the indication, the TA command.

[0007] In some embodiments of the UE described herein, the TA command request is transmitted periodically based on a periodicity, or transmitted based on an event, or transmitted based on an embodiment of the UE; and the periodicity or the event is configured or pre-configured to the UE, or predefined.

[0008] In some embodiments of the UE described herein, the event is a difference of a reference signal received power (RSRP) value relative to a reference value being greater than a first threshold for a first time period, or a moving speed of the UE being greater than a second threshold for a second time period; and the first threshold, the first time period, the second threshold, or the second time period is configured or pre-configured to the UE, or predefined.

[0009] In some embodiments of the UE described herein, the at least one processor is further configured to cause the UE to monitor for the TA command from a serving BS for a time period after each SRS transmission is performed.

[0010] In some embodiments of the UE described herein, the at least one processor is further configured to cause the UE to start or restart the zone-specific time alignment timer in response to receiving the TA command.

[0011] In some embodiments of the UE described herein, the at least one processor is further configured to cause the UE to: start or restart the zone-specific time alignment timer in response to receiving an indication to start the zone-specific time alignment timer; or stop the zone-specific time alignment timer in response to receiving an indication to stop the zone-specific time alignment timer.

[0012] In some embodiments of the UE described herein, the at least one processor is further configured to cause the UE to: transmit the indication in response to expiration of the zone-specific time alignment timer and an SRS configuration not being released, wherein the indication is a deactivation request to deactivate the SRS configuration that is not released; receive a deactivation response to deactivate the SRS configuration that is not released in response to the deactivation request; and deactivate the SRS configuration that is not released.

[0013] In some embodiments of the UE described herein, the at least one processor is further configured to cause the UE to: release the SRS configuration that is not released when there is no SRS transmission during a time period after expiration of the zone-specific time alignment timer.

[0014] In some embodiments of the UE described herein, the at least one processor is further configured to cause the UE to: transmit the indication in case of expiration of the zone-specific time alignment timer and an SRS configuration not being released, wherein the indication is an activation request to activate the SRS configuration that is not released, and wherein the activation request indicates: the SRS configuration that is not released and a cause value; or a service type or a quality of service (QoS) requirement.

[0015] In some embodiments of the UE described herein, the at least one processor is further configured to cause the UE to: transmit the indication in case of expiration of the zone-specific time alignment timer and an SRS configuration not being released, wherein the indication is a request to obtain the time alignment configuration indicating another zone-specific time alignment timer, and the request indicates the SRS configuration that is not released and a cause value.

[0016] In some embodiments of the UE described herein, the at least one processor is further configured to cause the UE to: receive a paging message in case of expiration of the zone-specific time alignment timer; and transmit the indication after receiving the paging message, wherein the indication is a request to obtain the time alignment configuration indicating another zone-specific time alignment timer.

[0017] In some embodiments of the UE described herein, the at least one processor is further configured to cause the UE to: stop SRS transmissions and release SRS configuration in response to expiration of the zone-specific time alignment timer; and transmit the indication in the case that there is a pending location service, wherein the indication is a request to acquire a new SRS configuration, and the request indicates a cause value.

[0018] In some embodiments of the UE described herein, the at least one processor is further configured to cause the UE to: maintain one of the zone-specific time alignment timer and a cell-specific time alignment timer based on the received SRS configuration simultaneously; or invalidate a cell-specific time alignment configuration in response to receiving the first configuration; or not receive a cell-specific SRS configuration and a valid zone-specific SRS configuration simultaneously; or not activate a cell-specific SRS configuration and a valid zone-specific SRS configuration simultaneously.

[0019] In some embodiments of the UE described herein, the at least one processor is further configured to cause the UE to: receive a third configuration indicating a cell-specific time alignment timer; and start or restart the zone-specific time alignment timer and the cell-specific time alignment timer simultaneously in response to receiving a TA command or an indication to start the zone-specific time alignment timer or the cell-specific time alignment timer.

[0020] In some embodiments of the UE described herein, in the case that the cell-specific time alignment timer expires but the zone-specific time alignment timer is running, the at least one processor is further configured to cause the UE to: continue SRS transmissions; determine an uplink (UL) out-of-sync for cell-specific UL transmissions; stop all cell-specific UL transmissions; or initiate a TA command update or request a cell-specific time alignment configuration when a cell-specific UL transmission occurs.

[0021] In some embodiments of the UE described herein, in the case that the UE reselects to a new cell within the SRS validity zone and different from a cell associated with the cell-specific time alignment timer, the at least one processor is further configured to cause the UE to: stop or restart the cell-specific time alignment timer; and keep the zone-specific time alignment timer running.

[0022] In some embodiments of the UE described herein, in the case that the zone-specific time alignment timer expires, the at least one processor is further configured to cause the UE to: stop SRS transmissions; and stop the cell-specific time alignment timer.

[0023] In some embodiments of the UE described herein, the first configuration further indicates a plurality of SRS configurations for a plurality of SRS validity zones and is received via a radio resource control (RRC) release message or a positioning system information block (posSIB) message.

[0024] In some embodiments of the UE described herein, the first configuration further indicates a SRS configuration of the plurality of SRS configurations used by the UE; or the at least one processor is further configured to cause the UE to determine a SRS configuration of the plurality of SRS configurations used by the UE based on a cell identification (ID) and validity zone information indicating the plurality of SRS validity zones.

[0025] In some embodiments of the UE described herein, the indication is an activation request to activate a SRS configuration of the plurality of SRS configurations.

[0026] In some embodiments of the UE described herein, the at least one processor is further configured to cause the UE to receive an activation response in response to the activation request, wherein the activation response indicates a SRS configuration of the plurality of SRS configurations and a TA command used by the UE.

[0027] In some embodiments of the UE described herein, the activation request indicates the SRS configuration, and the at least one processor is further configured to cause the UE to: receive an acknowledgement (ACK) in response to the activation request if the indicated SRS configuration is available; or receive an activation response in response to the activation request if the indicated SRS configuration is not available, wherein the activation response indicates a different SRS configuration of the plurality of SRS configurations.

[0028] In some embodiments of the UE described herein, the activation request indicates a cause value.

[0029] Some embodiments of the method and device described herein can include a processor for wireless communication. The processor can include at least one controller coupled with at least one memory and configured to cause the processor to: receive a first configuration including a zone-specific time alignment timer associated with a SRS validity zone; and transmit an indication for acquiring, activating, or deactivating a second configuration associated with the SRS validity zone when a UE including the processor is in a non-connected state, wherein the second configuration includes a SRS configuration, a time alignment configuration, or a TA command.

[0030] Some embodiments of the methods and devices described herein can include a BS for wireless communication. The BS can include at least one memory and at least one processor coupled with the at least one memory and configured to cause the BS to transmit, to a UE, a first configuration including a zone-specific time alignment timer associated with a SRS validity zone, and receive, while the UE is in a non-connected state, an indication for acquiring, activating, or deactivating a second configuration associated with the SRS validity zone, where the second configuration includes a SRS configuration, a time alignment configuration, or a TA command.

[0031] In some embodiments of the BS described herein, the indication is a SRS configuration request or a SRS activation request, and the at least one processor is further configured to cause the BS to transmit, in response to the SRS configuration request or the SRS activation request, the TA command for a successfully completed random access procedure.

[0032] In some embodiments of the BS described herein, the indication is a TA command request, and the at least one processor is further configured to cause the BS to transmit, in response to the indication, the TA command.

[0033] In some embodiments of the BS described herein, the TA command request is received periodically based on a periodicity, or based on an event; and the periodicity or the event is configured or preconfigured to the UE, or is predefined.

[0034] In some embodiments of the BS described herein, the event is a difference of a RSRP value relative to a reference value being greater than a first threshold for a first time period, or a moving speed of the UE being greater than a second threshold for a second time period; and the first threshold, the first time period, the second threshold, or the second time period is configured or preconfigured to the UE, or is predefined.

[0035] In some embodiments of the BS described herein, the at least one processor is further configured to cause the BS to transmit, to the UE, an indication for starting the zone-specific time alignment timer or an indication for stopping the zone-specific time alignment timer.

[0036] In some embodiments of the BS described herein, the at least one processor is further configured to cause the BS to receive the indication in response to an expiration of the zone-specific time alignment timer and a SRS configuration not being released, where the indication is a deactivation request for deactivating the not-released SRS configuration, transmit, in response to the deactivation request, a deactivation response for deactivating the not-released SRS configuration, and deactivate the not-released SRS configuration.

[0037] In some embodiments of the BS described herein, the at least one processor is further configured to cause the BS to release the unreleased SRS configuration when there is no SRS transmission during a time period after expiration of the zone-specific time alignment timer.

[0038] In some embodiments of the BS described herein, the at least one processor is further configured to cause the BS to receive the indication in a case where the zone-specific time alignment timer expires and an SRS configuration is not released, wherein the indication is an activation request to activate the unreleased SRS configuration, and wherein the activation request indicates: the unreleased SRS configuration and a cause value; or a service type or a QoS requirement.

[0039] In some embodiments of the BS described herein, the at least one processor is further configured to cause the BS to receive the indication in a case where the zone-specific time alignment timer expires and an SRS configuration is not released, wherein the indication is a request to obtain the time alignment configuration indicating another zone-specific time alignment timer, and the request indicates the unreleased SRS configuration and a cause value.

[0040] In some embodiments of the BS described herein, the at least one processor is further configured to cause the BS to transmit a paging message in a case where the zone-specific time alignment timer expires; and receive the indication after transmitting the paging message, wherein the indication is a request to obtain the time alignment configuration indicating another zone-specific time alignment timer.

[0041] In some embodiments of the BS described herein, the at least one processor is further configured to cause the BS to release an SRS configuration in response to expiration of the zone-specific time alignment timer; and receive the indication in a case where there is a pending location service, wherein the indication is a request to obtain a new SRS configuration, and the request indicates a cause value.

[0042] In some embodiments of the BS described herein, the at least one processor is further configured to cause the BS to: based on the transmitted SRS configuration, maintain one of the zone-specific time alignment timer and a cell-specific time alignment timer simultaneously; or in response to transmitting the first configuration, invalidate a cell-specific time alignment configuration; or not transmit a cell-specific SRS configuration and a validity zone-specific SRS configuration simultaneously; or not activate a cell-specific SRS configuration and a validity zone-specific SRS configuration simultaneously.

[0043] In some embodiments of the BS described herein, the first configuration further indicates a plurality of SRS configurations for a plurality of SRS validity zones and is transmitted via a RRC release message or a posSIB message.

[0044] In some embodiments of the BS described herein, the first configuration further indicates a SRS configuration of the plurality of SRS configurations used by the UE; or the at least one processor is further configured to cause the BS to determine a SRS configuration of the plurality of SRS configurations used by the UE based on a cell ID and validity zone information indicating the plurality of SRS validity zones.

[0045] In some embodiments of the BS described herein, the indication is an activation request to activate a SRS configuration of the plurality of SRS configurations.

[0046] In some embodiments of the BS described herein, the at least one processor is further configured to cause the BS to transmit an activation response in response to an activation request, wherein the activation response indicates a SRS configuration of the plurality of SRS configurations and a TA command used by the UE.

[0047] In some embodiments of the BS described herein, the activation request indicates the SRS configuration, and the at least one processor is further configured to cause the BS to: transmit an ACK in response to the activation request if the indicated SRS configuration is available; or transmit an activation response in response to the activation request if the indicated SRS configuration is not available, wherein the activation response indicates a different SRS configuration of the plurality of SRS configurations.

[0048] In some embodiments of the BS described herein, the activation request indicates a cause value.

[0049] Some embodiments of the methods and devices described herein can include a method performed by a UE. The method can include receiving a first configuration including a zone-specific time alignment timer associated with a SRS validity zone; and transmitting an indication for acquiring, activating, or deactivating a second configuration associated with the SRS validity zone when the UE is in a non-connected state, wherein the second configuration includes a SRS configuration, a time alignment configuration, or a TA command.

[0050] Some embodiments of the method and apparatus described herein can include a method performed by a BS. The method can include transmitting, to a UE, a first configuration including a zone-specific time alignment timer associated with a SRS validity zone; and receiving, when the UE is in a non-connected state, an indication for acquiring, activating, or deactivating a second configuration associated with the SRS validity zone, wherein the second configuration includes a SRS configuration, a time alignment configuration, or a TA command. BRIEF DESCRIPTION OF DRAWINGS

[0051] In order to describe the manner in which the application can be obtained, a description of the application is presented herein in reference to particular embodiments thereof. These descriptions and examples set forth in connection with the application are intended to be illustrative, and not in a limiting sense. Since the application can be practiced in a variety of embodiments, it is to be understood that the application is not limited in scope by the specificity of the exemplary embodiments described herein.

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

[0053] Figure 2 An exemplary zone-specific time alignment timer in accordance with aspects of the present disclosure is illustrated.

[0054] Figure 3 Flowcharts of exemplary methods performed by a UE and a BS in accordance with aspects of the present disclosure are illustrated.

[0055] Figure 4 An example of a UE in accordance with aspects of the present disclosure is illustrated.

[0056] Figure 5 An example of a processor in accordance with aspects of the present disclosure is illustrated.

[0057] Figure 6 An example of a BS in accordance with aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0058] The detailed description set forth above is presented as a description of the application and is not intended for limiting the application as defined in the claims. The spatial descriptions (e.g., "above," "below," "up," "down," "top," "bottom," etc.) relate to the application as it is oriented in the drawing figures. The relative terms do not denote an absolute position in the structures. It is understood that these embodiments can be practiced with the exceptions of the

[0059] Although operations are depicted in a particular order in the figures, one skilled in the art will readily understand that the ordering of such operations can not be required to achieve the desired results, or that all illustrated operations can not be required to achieve the desired results, sometimes an operation or multiple operations can be skipped, combined, or performed in a different order than as shown. Moreover, the figures can schematically depict one or more example processes in the form of a flowchart. However, other operations that are not depicted can be incorporated into the example processes that are schematically illustrated. For example, one or more additional operations can be performed before, after, simultaneously with, or between any of the illustrated operations. In certain circumstances, multitasking and parallel processing can be advantageous.

[0060] Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. In order to facilitate understanding, embodiments are provided under a specific network architecture and new service scenarios, such as 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) and LTE-Advanced, 3GPP 5G New Radio (NR), 5G-Advanced, 6G, etc. It is considered that all embodiments in the present application are also applicable to similar technical problems as the network architecture and new service scenarios develop; and furthermore, the terms stated in the present application can change, which should not affect the principles of the present application.

[0061] Aspects of the disclosure are described in the context of a wireless communication system.

[0062] Figure 1 An example of a wireless communication system 100 according to aspects of the disclosure is illustrated. The wireless communication system 100 can include one or more network equipment (NE) (e.g., BS) 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 can support various radio access technologies. In some embodiments, the wireless communication system 100 can be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other embodiments, the wireless communication system 100 can be an NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G-Ultra Wideband (5G-UWB) network. In other embodiments, the wireless communication system 100 can be a combination of a 4G network and a 5G network, or other suitable radio access technologies, including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communication system 100 can support a post-5G radio access technology, such as 6G. Moreover, the wireless communication system 100 can support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0063] One or more NEs 102 can be dispersed throughout a geographic area to provide wireless communication coverage to the wireless communication system 100. One or more of the NEs 102 described herein can be or include or can be referred to as a network node, base station, network element, network function, network entity, radio access network (RAN), NodeB, eNodeB (eNB), next generation NodeB (gNB), or other suitable terminology. The NEs 102 and the UEs 104 can communicate via communication links, which can be wireless or wired connections. For example, the NEs 102 and the UEs 104 can perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0064] The NEs 102 can provide geographic coverage areas with which a NE 102 can support service for one or more UEs 104 within the geographic coverage areas. For example, the NEs 102 and the UEs 104 can support wireless communication of signals related to service (e.g., voice, video, packet data, messaging, broadcast, etc.) in accordance with one or more radio access technologies. In some embodiments, the NEs 102 can be mobile, such as satellites associated with non-terrestrial networks (NTNs). In some embodiments, different geographic coverage areas associated with the same or different radio access technologies can overlap, although different geographic coverage areas can be associated with different NEs 102.

[0065] One or more UEs 104 can be dispersed throughout the geographic area of the wireless communication system 100. A UE 104 can include or can be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some embodiments, a UE 104 can be referred to as a unit, a station, a terminal, or a client, among other examples. Also or alternatively, a UE 104 can be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples.

[0066] A UE 104 can be capable of wireless communication with other UEs 104 directly. For example, a UE 104 can support wireless communication with another UE 104 over a device-to-device (D2D) communication link. In some embodiments, the communication link can be referred to as a sidelink, such as in vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments. For example, a UE 104 can support wireless communication with another UE 104 over a PC5 interface.

[0067] The NE 102 can support communication with the CN 106 or with another NE 102, or both. For example, the NE 102 can interface with other NEs 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N3, or network interfaces). In some embodiments, the NEs 102 can communicate directly with each other. In some other embodiments, the NEs 102 can communicate with each other indirectly (e.g., via the CN 106). In some embodiments, one or more of the NEs 102 can include subcomponents such as an access network entity, which can be an example of an access node controller (ANC). The ANC can communicate with one or more UEs 104 through one or more other access network transmission entities, which can be referred to as a radio head, a smart radio head, or a transmission-reception point (TRP).

[0068] The CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 can be an evolved packet core (EPC) or 5G core (5GC), which can include a control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) that manages access and mobility, and a user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) that routes packets or interconnections between using network functions. In some embodiments, the control plane entity can manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management (e.g., for data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more NEs 102 associated with the CN 106.

[0069] The CN 106 can communicate with a packet data network through one or more backhaul links (e.g., via SI, N2, N3, or another network interface). The packet data network can include application servers. In some embodiments, one or more UEs 104 can communicate with an application server. The UEs 104 can establish a session (e.g., a protocol data unit (PDU) session, etc.) with the CN 106 via the NE 102. The CN 106 can route traffic (e.g., control information, data, etc.) between the UEs 104 and the application server using the established session (e.g., the established PDU session). The PDU session can be an instance of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0070] In the wireless communication system 100, the NEs 102 and the UEs 104 can use resources (e.g., time resources or frequency resources) of the wireless communication system 100 to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 can support different resource structures. For example, the NEs 102 and the UEs 104 can support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, the NEs 102 and the UEs 104 can support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 can support various frame structures based on one or more numerologies.

[0071] One or more numerologies can be supported in the wireless communication system 100, and a numerology can include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., m = 0) can be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., m = 0) associated with the first subcarrier spacing (e.g., 15 kHz) can utilize one slot per subframe. A second numerology (e.g., m = 1) can be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., m = 2) can be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., m = 3) can be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., m = 4) can be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0072] Time intervals of resources (e.g., communication resources) can be organized as frames, which can also be referred to as radio frames. Each frame can have a certain duration, such as a 10 millisecond (ms) duration. In some implementations, each frame can include a number of subframes. For example, each frame can include 10 subframes, and each subframe can have a certain duration, such as a 1 ms duration. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0073] Additionally, or alternatively, time intervals of resources (e.g., communication resources) can be organized as slots, for example. A subframe can contain a certain number (quantity) of slots. The number of slots in each subframe can also depend on the parameter set(s) supported in the wireless communications system 100. For example, a first, second, third, fourth, and fifth parameter set (i.e., m = 0, m = 1, m = 2, m = 3, m = 4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz can utilize one slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot can contain a certain number (quantity) of symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols). In some embodiments, the number (quantity) of slots of a subframe can depend on the parameter set. For a normal cyclic prefix, a slot can contain 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot can contain 12 symbols. The relationship between the number of symbols per slot for normal and extended cyclic prefixes, the number of slots per subframe, and the number of slots per frame can depend on the parameter set. It will be understood that reference to a first parameter set (e.g., m = 0) associated with a first subcarrier spacing (e.g., 15 kHz) can be used interchangeably between subframes and slots.

[0074] In the wireless communications system 100, the electromagnetic (EM) spectrum can be partitioned into various classes, bands, channels, and / or the like. By way of example, the wireless communications system 100 can support one or more operating bands, such as frequency range designations FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some embodiments, the NEs 102 and the UEs 104 can perform wireless communications on one or more of the operating bands. In some embodiments, FR1 can be used by the NEs 102 and the UEs 104, among other apparatuses or devices, for cellular communications traffic (e.g., control information, data). In some embodiments, FR2 can be used by the NEs 102 and the UEs 104, among other apparatuses or devices, for short-range, high data rate capabilities.

[0075] FR1 can be associated with one or more numerologies (e.g., at least three numerologies). For example, FR1 can be associated with a first numerology including 15 kHz subcarrier spacing (e.g., m = 0); a second numerology including 30 kHz subcarrier spacing (e.g., m = 1); and a third numerology including 60 kHz subcarrier spacing (e.g., m = 2). FR2 can be associated with one or more numerologies (e.g., at least 2 numerologies). For example, FR2 can be associated with the third numerology including 60 kHz subcarrier spacing (e.g., m = 2); and a fourth numerology including 120 kHz subcarrier spacing (e.g., m = 3).

[0076] SRS, as an uplink reference signal transmitted from a UE to a BS, can be used for UL positioning. SRS positioning validity area (also referred to as SRS validity area or validity area) for UL positioning in a non-connected state (e.g., RRC_INACTIVE state or RRC_IDLE state) can avoid SRS configuration at cell reselection, and thus is recommended for use in low power high accuracy positioning (LPHAP). For example, a UE can be configured with an SRS configuration and an SRS validity area, where the SRS validity area includes one or more cells (e.g., a list of cells) in which the SRS configuration is valid, and the one or more cells include a cell in which the UE receives the SRS configuration. When the UE is in a non-connected state, if the UE reselects to another cell within the SRS validity area during SRS transmission (e.g., positioning SRS transmission), the UE can continue SRS transmission without SRS reconfiguration. In some embodiments of the present disclosure, an SRS configuration with an SRS validity area can be configured to a UE via an RRC release message (e.g., RRCRelease as specified in TS 38.331) or a posSIB message. In some embodiments of the present disclosure, multiple SRS configurations for multiple SRS validity areas can be configured to a UE via an RRC release message or a posSIB message.

[0077] In a conventional manner, a UE can be configured with a time alignment timer (e.g., denoted as: inactivePosSRS-TimeAlignmentTimer) that can control how long a medium access control (MAC) entity of the UE considers SRS transmissions within a cell to be uplink time aligned when the UE is in a non-connected state. Such a time alignment timer can be referred to as a cell-specific time alignment timer. The UE can start or restart the cell-specific time alignment timer upon receiving a TA command and stop the cell-specific time alignment timer upon receiving an indication from the BS (e.g., the BS transmits the indication to the UE via upper layer signaling and the MAC entity of the UE receives the indication from the upper layer of the UE) or upon reselecting to a new cell that is different from the cell in which the UE receives the cell-specific time alignment timer. When the cell-specific time alignment timer expires, the UE can inform the RRC layer to release the positioning SRS configuration for the non-connected state. According to embodiments of the present disclosure, to maintain a valid TA for SRS transmissions in the non-connected state and corresponding to a validity zone-specific SRS configuration (i.e., a SRS configuration with a validity zone for SRS transmissions in the non-connected state for positioning), a zone-specific time alignment timer (also referred to as a SRS validity zone-specific time alignment timer) of the UE can be defined to control the validity zone-specific SRS transmissions within a SRS validity zone in the non-connected state. For example, the zone-specific time alignment timer can control how long a MAC entity of the UE considers SRS transmissions within the SRS validity zone to be uplink time aligned.

[0078] In some embodiments of the present disclosure, the UE can start or restart the zone-specific time alignment timer upon its reception of a TA command. In some embodiments of the present disclosure, the UE can stop the zone-specific time alignment timer upon its reselection to a cell outside the SRS validity zone. In some embodiments of the present disclosure, the UE can stop SRS transmissions upon expiration of the zone-specific time alignment timer.

[0079] Figure 2 An exemplary zone-specific time alignment timer according to aspects of the present disclosure is illustrated.

[0080] With reference to Figure 2 , the UE can receive a SRS configuration with a SRS validity zone via an RRC release message. The SRS configuration can also include a zone-specific time alignment timer. The UE can enter a non-connected state after receiving the RRC release message. In the non-connected state, in response to receiving a TA command, the UE can start or restart the zone-specific time alignment timer and perform SRS transmissions based on the SRS configuration. When the zone-specific time alignment timer expires, the UE can stop SRS transmissions even though the UE is still within the SRS validity zone.

[0081] There are some issues to be solved when designing SRS configuration with SRS validity zone and zone-specific time alignment timer.

[0082] Issue #1 is how to acquire TA command. As stated above, UE can start or restart zone-specific time alignment timer when it receives TA command. Traditionally, TA command is received in random access response message of serving cell. However, UE can not always perform SRS transmission, and if UE does not initiate uplink transmission when it is in SRS validity zone, network can not know which cell UE currently resides in. Therefore, UE can not receive TA command from network for a long time if no uplink request is initiated according to tradition. In view of this, how to acquire TA command needs to be solved.

[0083] Issue #2 is how to handle SRS configuration associated with SRS validity zone (i.e., validity zone-specific SRS configuration) when zone-specific time alignment timer expires. Traditionally, when cell-specific time alignment timer expires, UE's MAC entity can inform RRC layer to release positioning SRS configuration. However, whether to release validity zone-specific SRS configuration when zone-specific time alignment timer expires needs further consideration.

[0084] Issue #3 is how to handle the relationship between zone-specific time alignment timer and cell-specific time alignment timer, and how to determine the maintenance of zone-specific time alignment timer and cell-specific time alignment timer. For example, in wireless communication system, both zone-specific time alignment timer and cell-specific time alignment timer can be supported, but the relationship between the two timers for positioning SRS transmission is not clear. In view of this, the interaction / maintenance of the two timers should be considered.

[0085] Issue #4 is how to determine SRS configuration to be used by UE when multiple SRS configurations for multiple SRS validity zones are configured for UE. For example, network can provide multiple SRS configurations for multiple SRS validity zones at the same time, and the principle for UE to determine which SRS configuration to use and switch between different SRS configurations needs to be defined.

[0086] Embodiments of the present disclosure provide solutions for SRS configuration with validity zone, which can solve at least one of the above issues. More details will be described in the following text in conjunction with the drawings.

[0087] Figure 3 A flowchart illustrating exemplary methods performed by a UE and a BS according to aspects of the present disclosure is described. Although the methods are performed by a UE and a BS (e.g., as described above), the methods can be performed by any suitable apparatus for performing the functions described below. In this regard, the methods can be implemented at least in part by a machine, such as a computer system. Figure 1The methods implemented in the UE and the methods implemented in the BS can be implemented separately and consolidated by other devices with similar functions, as can be appreciated by one skilled in the art, while the UE 104 and the NE 102 are illustrated at the system level. In some embodiments, a UE can execute a set of instructions to control the functional elements of the UE to perform the described operations or functions. In some embodiments, a BS can execute a set of instructions to control the functional elements of the BS to perform the described operations or functions.

[0088] As shown in Figure 3 In step 302, the BS can transmit a first configuration to the UE, as shown in the middle. The first configuration can include (or indicate) a zone-specific time alignment timer associated with the SRS validity zone (e.g., denoted as inactivePosSRSArea-TimeAlignmentTimer). Thus, in step 304, the UE can receive the first configuration from the BS.

[0089] In step 306, the UE can transmit an indication for acquiring, activating, or deactivating a second configuration associated with the SRS validity zone when the UE is in a non-connected state. The non-connected state can be an RRC_INACTIVE state or an RRC_IDLE state. The second configuration includes an SRS configuration or a time alignment configuration or a TA command. Thus, in step 308, the BS can receive the indication from the UE when the UE is in the non-connected state.

[0090] Embodiments of the methods described can include, but are not limited to, the following examples, which illustrate details of steps 302-308 in different cases.

[0091] Example 1

[0092] The solution in Embodiment 1 can solve, for example, Problem #1 described above.

[0093] In Embodiment 1, the first configuration transmitted by the BS in step 302 and received by the UE in step 304 can include (or indicate) an SRS configuration with the SRS validity zone, e.g., the SRS configuration can include SRS validity zone information indicating the SRS validity zone. The first configuration can also include (or indicate) a zone-specific time alignment timer associated with the SRS configuration (and thus also associated with the SRS validity zone). For example, the first configuration can include a zone-specific time alignment configuration indicating the zone-specific time alignment timer. In some instances, the SRS configuration can indicate or include the zone-specific time alignment timer. In some other instances, the SRS configuration can not indicate or include the zone-specific time alignment timer.

[0094] A SRS validity zone can include one or more cells (e.g., a list of cells) in which a SRS configuration is valid. A zone-specific time alignment timer can control validity zone-specific SRS transmissions (e.g., SRS transmissions within the SRS validity zone). For example, the zone-specific time alignment timer can control how long the UE’s MAC entity considers SRS transmissions within the SRS validity zone to be uplink time aligned.

[0095] In some embodiments, the first configuration can be transmitted by the BS and received by the UE via an RRC release message (e.g., RRCRelease as specified in TS 38.331). In some embodiments, the first configuration can be transmitted by the BS and received by the UE via a posSIB message.

[0096] In embodiment 1, the indication transmitted by the UE in step 306 and received by the BS in step 308 can be an indication to acquire a TA command. That is, the second configuration can include a TA command.

[0097] In some embodiments, the indication to acquire a TA command can be an uplink request, e.g., a SRS activation request, a SRS configuration request, a SRS configuration update request, etc. In some embodiments, the uplink request can be transmitted via: MSG1 in a 4-step random access procedure, MSG3 in a 4-step random access procedure, MSGA in a 2-step random access procedure, or a piggybacked MAC control element (CE) of MSG1, MSG3, or MSGA.

[0098] In response to receiving the uplink request, the BS can transmit a TA command to the UE for a successfully completed random access procedure. In some embodiments, the TA command can be transmitted within a downlink (DL) message, e.g., via MSG2 in a 4-step random access procedure when the uplink request is transmitted via MSG1 or a piggybacked MAC CE of a 4-step random access procedure, via MSG4 in a 4-step random access procedure when the uplink request is transmitted via MSG3 or a piggybacked MAC CE of a 4-step random access procedure, or via MSGB in a 2-step random access procedure when the uplink request is transmitted via MSGA or a piggybacked MAC CE of a 2-step random access procedure.

[0099] In some embodiments, the indication to acquire a TA command can be a TA command request, e.g., when no SRS activation request or SRS configuration (update) request is initiated.

[0100] As an example, the TA command request can be periodically transmitted by the UE based on a periodicity. The periodicity can be configured by the BS or pre-configured to the UE, or predefined.

[0101] As another example, the TA command request can be transmitted by the UE based on an event. For example, the UE can transmit the TA command request when an event occurs or is detected by the UE. The event can be configured or pre-configured to the UE by the BS, or be predefined.

[0102] For example, the event can be that a difference of an RSRP value relative to a reference value is greater than a first threshold value for a first time period. The first threshold value and / or the first time period can be configured or pre-configured to the UE by the BS, or can be predefined. The UE can store the RSRP value as the reference value when it receives a time alignment configuration (e.g., a zone-specific time alignment configuration).

[0103] As another example, the event can be that a moving speed of the UE is greater than a second threshold value for a second time period. The second threshold value and / or the second time period can be configured or pre-configured to the UE by the BS, or can be predefined.

[0104] As yet another example, the TA command request can be transmitted based on an implementation of the UE.

[0105] In response to receiving the TA command request, the BS can transmit a TA command to the UE.

[0106] In some embodiments, the UE can monitor for a TA command from a BS (which is a serving BS of the UE) for a time period after each SRS transmission is performed.

[0107] In some cases of embodiment 1, in response to receiving a TA command from the BS, the UE (e.g., a MAC entity of the UE) can start or restart a zone-specific time alignment timer. For example, if there is an ongoing positioning SRS transmission in the non-connected state, the UE can start or restart the zone-specific time alignment timer. The BS can perform a similar operation. For example, in response to transmitting the TA command, the BS (e.g., a MAC entity of the BS) can start or restart the zone-specific time alignment timer.

[0108] In some cases of embodiment 1, the BS can transmit an indication to start the zone-specific time alignment timer. For example, the indication can be transmitted via RRC signaling. In response to receiving the indication, the UE (e.g., a MAC entity of the UE) can start or restart the zone-specific time alignment timer. For example, after an upper layer (e.g., an RRC layer) of the UE receives the indication from the BS, the upper layer of the UE can transmit an indication to start the zone-specific time alignment timer to a MAC entity of the UE, and the MAC entity can start or restart the zone-specific time alignment timer in response to receiving the indication from the upper layer of the UE.

[0109] In some cases of embodiment 1, the BS can transmit an indication for stopping the zone-specific time alignment timer. For example, the indication can be transmitted via RRC signaling (e.g., RRCResume message or RRCSetup message as specified in TS 38.331). In response to receiving the indication, the UE (e.g., MAC entity of the UE) can stop the zone-specific time alignment timer. For example, after the UE’s upper layer (e.g., RRC layer) receives the indication from the BS, the UE’s upper layer can transmit an indication for stopping the zone-specific time alignment timer to the MAC entity of the UE, and the MAC entity can stop the zone-specific time alignment timer in response to receiving the indication from the UE’s upper layer.

[0110] Example 2

[0111] The solution in embodiment 2 can solve, for example, problem #2 as aforementioned.

[0112] All the definitions as provided in embodiment 1 with respect to the first configuration transmitted by the BS in step 302 and received by the UE in step 304 can also apply in embodiment 2, for simplicity, the definitions are omitted here.

[0113] In some cases of embodiment 2, when the zone-specific time alignment timer expires, the UE can stop the SRS transmission, but the SRS configuration is not released.

[0114] In some instances, in step 306, the UE can transmit the indication in response to the expiration of the zone-specific time alignment timer and the SRS configuration not being released. In these instances, the indication can be a deactivation request for deactivating the SRS configuration that is not released. That is, the second configuration can include the SRS configuration that is not released.

[0115] For example, the deactivation request can be transmitted via: MSG1 in a 4-step random access procedure, MSG3 in a 4-step random access procedure, MSGA in a 2-step random access procedure, a piggybacked MAC CE of MSG1, MSG3, or MSGA, or a small data transmission (SDT) procedure.

[0116] In response to receiving the deactivation request from the UE, the BS can transmit a deactivation response to the UE for deactivating the unreleased SRS configuration. The deactivation response can be transmitted via MSG2 in a 4-step random access procedure when the deactivation request is transmitted via MSG1 in the 4-step random access procedure, via MSG4 in the 4-step random access procedure when the deactivation request is transmitted via MSG3 in the 4-step random access procedure, via MSGB in a 2-step random access procedure when the deactivation request is transmitted via MSGA in the 2-step random access procedure, or via a piggyback MAC CE of MSG2, MSG4, or MSGB when the deactivation request is transmitted via a piggyback MAC CE of MSG1, MSG3, or MSGA. In response to receiving the deactivation response, the UE can deactivate the unreleased SRS configuration. The BS can also deactivate the unreleased SRS configuration.

[0117] In some instances, the UE and the BS can release the unreleased SRS configuration when there is no SRS transmission during a time period after expiration of the zone-specific time alignment timer. The time period can be configured to the UE by the BS (e.g., indicated by the first configuration or the SRS configuration in the first configuration), or can be pre-configured to the UE by the BS, or can be predefined.

[0118] In some instances, in step 306, the UE can transmit an indication in case the zone-specific time alignment timer expires and the SRS configuration is not released, where the indication is an activation request for activating the unreleased SRS configuration. That is, the second configuration can include the unreleased SRS configuration.

[0119] For example, the activation request can be transmitted via MSG1 in a 4-step random access procedure, MSG3 in the 4-step random access procedure, MSGA in a 2-step random access procedure, a piggyback MAC CE of MSG1, MSG3, or MSGA, or an SDT procedure.

[0120] In response to receiving the activation request from the UE, the BS can transmit an activation response to the UE for activating the unreleased SRS configuration. The activation response in response to the activation request can be transmitted via MSG2 in a 4-step random access procedure when the activation request is transmitted via MSG1 in the 4-step random access procedure, via MSG4 in the 4-step random access procedure when the activation request is transmitted via MSG3 in the 4-step random access procedure, via MSGB in a 2-step random access procedure when the activation request is transmitted via MSGA in the 2-step random access procedure, or via a piggyback MAC CE of MSG2, MSG4, or MSGB when the activation request is transmitted via a piggyback MAC CE of MSG1, MSG3, or MSGA. In response to receiving the activation response, the UE can activate the unreleased SRS configuration. The BS can also activate the unreleased SRS configuration.

[0121] As an example, the activation request can indicate a non-released SRS configuration (e.g., include an index or identification of a non-released SRS configuration or a detailed parameter list) and a cause value (e.g., zone-specific time alignment timer expiration). In such an example, the activation response can be an ACK indicating that the non-released SRS configuration indicated by the activation request is activated.

[0122] As another example, the activation request can be initiated in response to a service. In such an example, since the BS can need to know which SRS configuration is suitable for the service, the activation request can indicate a service type or QoS requirement to assist the BS in determining a non-released SRS configuration to activate. In such an example, the activation response can indicate a non-released SRS configuration to activate (e.g., include an index of a non-released SRS configuration), and then the UE and the BS can activate the non-released SRS configuration indicated by the activation response.

[0123] In some examples, in step 306, in case the zone-specific time alignment timer expires and the SRS configuration is not released, the UE can transmit an indication, where the indication is for obtaining a request indicating a time alignment configuration of another zone-specific time alignment timer. That is, the second configuration can include the time alignment configuration.

[0124] In response to receiving the request from the UE, the BS can transmit to the UE a time alignment configuration indicating another zone-specific time alignment timer. The time alignment configuration in response to the request can be transmitted via RRC signaling (e.g., RRCRelease message).

[0125] As an example, the other zone-specific time alignment timer can be for a non-released SRS configuration. In such an example, the request can indicate the non-released SRS configuration and a cause value (e.g., zone-specific time alignment timer expiration).

[0126] As an example, in response to receiving the request from the UE, the BS can further transmit to the UE a time alignment configuration indicating another zone-specific time alignment timer. In addition, a new TA command is also transmitted with the time alignment configuration. In response to receiving the new TA command, the UE can start another zone-specific time alignment timer.

[0127] In some instances, upon expiration of the zone-specific time alignment timer, the BS can transmit a paging message to the UE to page the UE. The paging message can include a paging cause value (e.g., zone-specific time alignment timer expiration). Upon receiving the paging message, in step 306, the UE can transmit an indication to the BS, where the indication is a request for acquiring a time alignment configuration indicating another zone-specific time alignment timer (e.g., via an RRCResumeRequest message as specified in TS 38.331). That is, the second configuration can include the time alignment configuration.

[0128] In response to receiving the request from the UE, the BS can transmit a time alignment configuration indicating another zone-specific time alignment timer to the UE.

[0129] In some other cases of Embodiment 2, in response to expiration of the zone-specific time alignment timer, the UE can stop SRS transmission and release the SRS configuration.

[0130] In some instances, in the presence of undecided bit services (e.g., after expiration of the zone-specific time alignment timer or when the UE is outside the SRS validity zone), in step 306, the UE can transmit an indication to the BS, where the indication is a request for acquiring a new SRS configuration (i.e., updating the SRS configuration) (e.g., via an RRCResumeRequest message as specified in TS 38.331). The request for acquiring a new SRS configuration can indicate a cause value. The cause value can be: zone-specific time alignment timer expiration, outside the SRS validity zone, etc. In response to receiving the request, the BS can provide a new SRS configuration to the UE. The new time alignment configuration can also be provided to the UE together with the new SRS configuration.

[0131] Example 3

[0132] In some cases, both zone-specific time alignment timer and cell-specific time alignment timer can be supported in the system simultaneously. Embodiment 3 provides a solution in this case. That is, the solution in Embodiment 3 can solve, for example, Problem #3 aforementioned.

[0133] In some cases of embodiment 3, the UE can maintain only one of the zone-specific time alignment timer and the cell-specific time alignment timer based on the received SRS configuration. For example, in the case that the UE receives an SRS configuration associated with an SRS validity zone (e.g., a validity zone-specific SRS configuration), the UE starts or restarts only the zone-specific time alignment timer when it receives a TA command or an indication to start the time alignment timer from the BS. As another example, in the case that the UE receives a cell-specific SRS configuration, the UE starts or restarts only the cell-specific time alignment timer when it receives a TA command or an indication to start the time alignment timer from the BS. The BS can perform similar operations. That is, the BS can maintain only one of the zone-specific time alignment timer and the cell-specific time alignment timer based on the transmitted SRS configuration.

[0134] In some instances, the UE can invalidate a cell-specific time alignment configuration (which can indicate a cell-specific time alignment timer) in response to receiving a zone-specific time alignment configuration (which can indicate a zone-specific time alignment timer).

[0135] In some instances, a UE (e.g., a UE with LPHAP capability) is not allowed to be configured with both cell-specific SRS and zone-specific SRS simultaneously. In such instances, the BS can not transmit both a cell-specific SRS configuration and a validity zone-specific SRS configuration simultaneously; and the UE can not receive both a cell-specific SRS configuration and a validity zone-specific SRS configuration simultaneously.

[0136] In some instances, if both a cell-specific SRS configuration and a validity zone-specific SRS are configured, a UE (e.g., a UE with LPHAP capability) is not allowed to activate both the cell-specific SRS configuration and the validity zone-specific SRS simultaneously. In such instances, the BS can also not activate both the cell-specific SRS configuration and the validity zone-specific SRS configuration simultaneously.

[0137] In some cases of embodiment 3, a SDT procedure can be triggered for uplink transmission. In such cases, the UE can start or restart a SDT time alignment timer (e.g., a cg-SDT-TimeAlignmentTimer as specified in TS 38.321). The SDT time alignment timer is independent of the zone-specific time alignment timer and the cell-specific time alignment timer. That is, the operation with respect to the SDT time alignment timer is independent of the zone-specific time alignment timer and the cell-specific time alignment timer.

[0138] In some cases of embodiment 3, the UE can maintain both the zone-specific time alignment timer and the cell-specific time alignment timer simultaneously.

[0139] In this case, the first configuration transmitted by the BS in step 302 and received by the UE in step 304 can include an SRS configuration with an SRS validity area including a list of cells (e.g., including cell #1, cell #2, and cell #3) and a zone-specific time alignment timer (e.g., defined as inactivePosSRSArea-TimeAlignmentTimer) associated with the SRS validity area. In addition to the first configuration, the BS can transmit to the UE a third configuration indicating a cell-specific time alignment timer (e.g., inactivePosSRS-TimeAlignmentTimer or cg-SDT-TimeAlignmentTimer as specified in TS 38.321) associated with a cell (e.g., cell #1) in the list of cells.

[0140] As an example, the UE can simultaneously start or restart the zone-specific time alignment timer and the cell-specific time alignment timer in response to receiving a TA command or an indication to start a time alignment timer (zone-specific time alignment timer or cell-specific time alignment timer) from the BS. The BS can perform similar operations. For example, the BS can simultaneously start or restart the zone-specific time alignment timer and the cell-specific time alignment timer in response to transmitting a TA command or an indication to start a time alignment timer to the UE.

[0141] As another example, when the cell-specific time alignment timer expires but the zone-specific time alignment timer is running, the UE can perform at least one of the following: continue SRS transmission; determine UL not synchronized for cell-specific UL transmission; stop all cell-specific UL transmission; or when cell-specific UL transmission occurs (e.g., UL data arrival, UL feedback caused by DL data, etc.), initiate TA command update (e.g., by transmitting a request for TA command) or request cell-specific time alignment configuration (e.g., by transmitting a request for cell-specific time alignment configuration). The BS can perform corresponding operations. For example, the BS can receive a request for TA command or a request for cell-specific time alignment configuration, and transmit a corresponding response to the UE.

[0142] As another example, the UE can reselect to a new cell (e.g., cell #2) within the SRS validity area and different from the cell (e.g., cell #1) associated with the cell-specific time alignment timer, the UE can stop or restart the cell-specific time alignment timer, and keep the zone-specific time alignment timer running. The BS can perform similar operations.

[0143] As another example, when the zone-specific time alignment timer expires, the UE can stop SRS transmission. If the cell-specific time alignment timer is still running, the UE can also stop the timer. The BS can perform similar operations. For example, the BS can stop the cell-specific time alignment timer.

[0144] Example 4

[0145] The solution in Embodiment 4 can solve, for example, the aforementioned problem #4.

[0146] In Embodiment 4, the first configuration transmitted by the BS in step 302 and received by the UE in step 304 can include (or indicate) a plurality of SRS configurations for (or associated with) a plurality of SRS validity zones. An SRS configuration in the plurality of SRS configurations can or can not include validity zone information indicating an SRS validity zone associated with the SRS configuration. For example, the first configuration can include three SRS configurations with validity zone information (e.g., denoted as srsconfigl-area1, srsconfig2-area2, and srsconfig3-area3) or SRS configurations without validity zone information (e.g., denoted as srsconfigl, srsconfig2, and srsconfig3). The first configuration can also include, for each SRS configuration in the plurality of SRS configurations, a corresponding zone-specific time alignment timer associated with the SRS configuration.

[0147] Embodiment 4 can be divided into Embodiment 4-1 and Embodiment 4-2.

[0148] Example 4-1

[0149] In Embodiment 4-1, the first configuration can be transmitted by the BS to the UE via an RRC release message (e.g., an RRCRelease message as specified in TS 38.331).

[0150] In an embodiment, the first configuration can also indicate an SRS configuration in the plurality of SRS configurations used by the UE. For example, the first configuration can include an index or ID of the SRS configuration used by the UE.

[0151] In another embodiment, each SRS configuration of the plurality of SRS configurations can include validity zone information indicating a corresponding SRS validity zone. The UE or the BS can determine an SRS configuration of the plurality of SRS configurations used by the UE based on a cell ID and the validity zone information of the plurality of SRS configurations indicating a plurality of SRS validity zones. For example, if three SRS configurations with validity zone information (e.g., denoted as srsconfigl-areal, srsconfig2-areal, and srsconfig3-areal) are configured to the UE, and areal includes a list of cells including cell #1, cell #2, and cell #3, in a case that the UE is camped in cell #1, the UE can determine to use srsconfigl-areal from the plurality of SRS configurations.

[0152] Example 4-2

[0153] In embodiment 4-2, the first configuration can be transmitted by the BS to the UE via a posSIB message.

[0154] After receiving the first configuration including the plurality of SRS configurations, in step 306, the UE can transmit an indication to the BS, and the BS can receive the indication in step 308, where the indication can be an activation request for activating an SRS configuration of the plurality of SRS configurations.

[0155] In some instances, the BS can transmit an activation response to the UE in response to the activation request. The activation response can indicate an SRS configuration of the plurality of SRS configurations and a TA command used by the UE. For example, the activation response can include an index or an ID of the SRS configuration.

[0156] In some instances, the activation request can indicate an SRS configuration of the plurality of SRS configurations. For example, the activation response can include an index or an ID of the SRS configuration.

[0157] In a case that the indicated SRS configuration is available, the BS can transmit an ACK in response to the activation request. After receiving the ACK in response to the activation request, the UE can activate the indicated SRS configuration.

[0158] In a case that the indicated SRS configuration is not available, the BS can transmit an activation response in response to the activation request, where the activation response can indicate a new SRS configuration of the plurality of SRS configurations different from the indicated SRS configuration. In some instances, the activation response can also include a TA command used by the UE. After receiving the activation response, the UE can activate the new SRS configuration.

[0159] The activation request transmitted by the UE can indicate a cause value, for example, the cause value can be: zone-specific time alignment timer expiration, outside of an SRS validity zone, etc.

[0160] In some instances, the activation request can be transmitted via MSG1 in a 4-step random access procedure, MSG3 in a 4-step random access procedure, MSGA in a 2-step random access procedure, RRC signaling, or UL MAC CE of MSG1, MSG3, or MSGA. When the activation request is transmitted via MSG1 of a 4-step random access procedure, the ACK or activation response in response to the activation request can be transmitted via MSG2 in a 4-step random access procedure, when the activation request is transmitted via MSG3 of a 4-step random access procedure, via MSG4 in a 4-step random access procedure, when the activation request is transmitted via MSGA of a 2-step random access procedure, via MSGB of a 2-step random access procedure, when the activation request is transmitted via RRC signaling, via RRC signaling, or when the activation request is transmitted via UL MAC CE of MSG1, MSG3, or MSGA, via DL MAC CE of MSG2, MSG4, or MSGB.

[0161] In some instances, when the UE moves out of the current SRS validity area or the current SRS configuration is invalid (e.g., the area-specific time alignment timer expires), the UE needs to activate a new SRS configuration from the plurality of SRS configurations. All the above described operations described above in Embodiment 4-2 can also apply here to cause the UE to activate the new SRS configuration.

[0162] Figure 4 An example of a UE 400 in accordance with aspects of the present disclosure is illustrated. The UE 400 can include at least one processor 402 and at least one memory 404. In addition, the UE 400 can also include one or more of at least one controller 406 or at least one transceiver 408. The processor 402, memory 404, controller 406, or transceiver 408, or various combinations thereof or various components thereof, can be examples of means for performing various aspects of the present disclosure as described herein. These components can be coupled with or to each other via one or more interfaces, e.g., operatively, communicatively, functionally, electronically, electrically.

[0163] The processor 402, memory 404, controller 406, or transceiver 408, or various combinations thereof or components thereof, can be implemented in hardware (e.g., circuitry). The hardware can include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or a combination thereof, configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0164] The processor 402 can include an intelligent hardware device, (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some embodiments, the processor 402 can be configured to operate the memory 404. In some other embodiments, the memory 404 can be integrated into the processor 402. The processor 402 can be configured to execute computer-readable instructions stored in the memory 404 to cause the UE 400 to perform various functions of the present disclosure.

[0165] The memory 404 can include volatile or non-volatile memory. The memory 404 can store computer-readable, computer-executable code including instructions that, when executed by the processor 402, cause the UE 400 to perform various functions described herein. The code can be stored in a non-transitory computer-readable medium, such as the memory 404 or

[0166] In some embodiments, the processor 402 and the memory 404 coupled with the processor 402 can be configured to cause the UE 400 to perform one or more of the functions described herein (e.g., by the processor 402 executing instructions stored in the memory 404). For example, the processor 402 can support wireless communication at the UE 400 in accordance with examples as disclosed herein. The UE 400 can be configured to support means for performing operations of the methods described in embodiments of the present disclosure. In embodiments, the processor 402 can be configured to cause the UE 400 to: receive a first configuration including a zone-specific time alignment timer associated with a SRS validity zone; and transmit an indication for acquiring, activating, or deactivating a second configuration associated with the SRS validity zone when the UE is in a non-connected state, where the second configuration includes a SRS configuration, a time alignment configuration, or a TA command.

[0167] The controller 406 can manage peripherals of the UE 400. In some embodiments, the controller 406 can utilize an operating system, such as the controller 406 can be implemented as part of the processor 402.

[0168] In some implementations, the UE 400 can include at least one transceiver 408. In some other implementations, the UE 400 can have more than one transceiver 408. The transceiver 408 can represent a wireless transceiver. The transceiver 408 can include one or more receiver chains 410, one or more transmitter chains 412, or a combination thereof.

[0169] The receiver chain 410 can be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 410 can include one or more antennas for receiving signals over the air or wireless medium. The receiver chain 410 can include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 410 can include at least one demodulator configured to demodulate the received signal and obtain transmitted data by reversing the modulation techniques applied during transmission of the signal. The receiver chain 410 can include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0170] The transmitter chain 412 can be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 412 can include at least one modulator for modulating data onto a carrier signal in preparation for transmission of the signal over a wireless medium. The at least one modulator can be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or a digital modulation scheme like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 412 can also include at least one power amplifier configured to amplify the modulated signal to a proper power level for transmission over the wireless medium. The transmitter chain 412 can also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0171] Figure 5 An example of a processor 500 in accordance with aspects of the present disclosure is illustrated. The processor 500 can be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 500 can include a controller 502 configured to perform various operations in accordance with examples as described herein. The processor 500 can optionally include at least one memory 504, which can be, for example, a level 1 (LI), level 2 (L2), or level 3 (L3) cache. Additionally or alternatively, the processor 500 can optionally include one or more arithmetic logic units (ALUs) 506. One or more of these components can be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0172] The processor 500 can be a processor chipset and include a protocol stack (e.g., software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset can include one or more cores, one or more caches (e.g., located locally or included in memory of the processor chipset (e.g., processor 500)) or other memory (e.g., random access memory (RAM), read only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), etc.).

[0173] The controller 502 can be configured to manage and coordinate the various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 500 to enable the processor 500 to support various operations in accordance with examples as described herein. For example, the controller 502 can operate as a control unit of the processor 500, generating control signals that manage the operation of the individual components of the processor 500. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0174] The controller 502 can be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 504 and determine subsequent instructions to execute to enable the processor 500 to support various operations in accordance with examples as described herein. The controller 502 can be configured to track memory addresses of instructions associated with the memory 504. The controller 502 can be configured to decode instructions to determine operations to perform and operands involved. For example, the controller 502 can be configured to interpret instructions and determine control signals to output to other components of the processor 500 to enable the processor 500 to support various operations in accordance with examples as described herein. Additionally or alternatively, the controller 502 can be configured to manage data flow within the processor 500. The controller 502 can be configured to control data transfers between registers, ALUs, and other functional units of the processor 500.

[0175] The memory 504 can include one or more caches (e.g., located locally or included in the processor 500, or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some implementations, the memory 504 can reside within or on a processor chipset (e.g., located locally to the processor 500). In some other implementations, the memory 504 can reside outside of the processor chipset (e.g., remote from the processor 500).

[0176] The memory 504 can store computer-readable, computer-executable code including instructions that, when executed by the processor 500, cause the processor 500 to perform various functions described herein. The code can be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. The controller 502 and / or the processor 500 can be configured to execute computer-readable instructions stored in the memory 504 to cause the processor 500 to perform various functions. For example, the processor 500 and / or the controller 502 can be coupled with or to the memory 504, which can be configured to perform the various functions described herein. In some examples, the processor 500 can include multiple processors, and the memory 504 can include multiple memories. One or more of the multiple processors can be coupled with one or more of the multiple memories, which can be individually or collectively configured to perform the various functions herein.

[0177] The one or more ALUs 506 can be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 506 can reside within or on a processor chipset (e.g., the processor 500). In some other implementations, the one or more ALUs 506 can reside outside of the processor chipset (e.g., the processor 500). The one or more ALUs 506 can perform one or more computations on data, such as addition, subtraction, multiplication, and division. For example, the one or more ALUs 506 can receive input operands and an operation code, which determines the operation to be performed. The one or more ALUs 506 can be configured with various logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, the one or more ALUs 506 can support logical operations, such as AND, OR, exclusive OR (XOR), or NOT (NOR), and NAND, enabling the one or more ALUs 506 to handle conditional operations, comparisons, and bitwise operations.

[0178] The processor 500 can support wireless communication in accordance with examples as disclosed herein. The processor 500 can be configured to or operable to support means for performing operations of the methods described in embodiments of the disclosure. In embodiments, the controller 502 can cause the processor 500 to: receive a first configuration including a zone-specific time alignment timer associated with a SRS validity zone; and transmit an indication for acquiring, activating, or deactivating a second configuration associated with the SRS validity zone when a UE including the processor 500 is in a non-connected state, where the second configuration includes a SRS configuration, a time alignment configuration, or a TA command.

[0179] Figure 6 An example of a BS 600 in accordance with aspects of the disclosure is described. The BS 600 can include at least one processor 602 and at least one memory 604. Further, the BS 600 can also include one or more of at least one controller 606 or at least one transceiver 608. The processor 602, the memory 604, the controller 606, or the transceiver 608, or various combinations thereof or various components thereof, can be examples of means for performing various aspects of the disclosure as described herein. These components can be coupled with or to each other via one or more interfaces, e.g., operatively, communicatively, functionally, electronically, electrically.

[0180] The processor 602, the memory 604, the controller 606, or the transceiver 608, or various combinations thereof or components thereof, can be implemented in hardware (e.g., circuitry). The hardware can include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof, configured as or otherwise supporting means for performing the functions described in this disclosure.

[0181] The processor 602 can include an intelligent hardware device, e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof. In some embodiments, the processor 602 can be configured to operate the memory 604. In some other embodiments, the memory 604 can be integrated into the processor 602. The processor 602 can be configured to execute computer-readable instructions stored in the memory 604 to cause the BS 600 to perform various functions of the disclosure.

[0182] Memory 604 can include volatile or nonvolatile memory. Memory 604 can store computer-readable, computer-executable code including instructions that, when executed by processor 602, cause BS 600 to perform various functions described herein. The code can be stored in a non-transitory computer-readable medium, such as memory 604 or another type of memory. Computer-readable media include both volatile and nonvolatile media, removable and nonremovable media, and communication media. Non-transitory computer-readable media include all computer-readable media excluding a transitory, propagating signal.

[0183] In some implementations, processor 602 and memory 604 coupled with processor 602 can be configured to cause BS 600 to perform one or more of the functions described herein (e.g., by processor 602 executing instructions stored in memory 604). For example, processor 602 can support wireless communication at BS 600 in accordance with examples as disclosed herein. BS 600 can be configured to support means for performing operations of the methods described in embodiments of the present disclosure. In embodiments, processor 602 can be configured to cause BS 600 to transmit, to a UE, a first configuration including a zone-specific time alignment timer associated with a SRS validity zone; and receive, when the UE is in a non-connected state, an indication for acquiring, activating, or deactivating a second configuration associated with the SRS validity zone, where the second configuration includes a SRS configuration, a time alignment configuration, or a TA command.

[0184] Controller 606 can manage incoming and outgoing signals for BS 600. Controller 606 can also manage peripherals not integrated into BS 600. In some embodiments, controller 606 can utilize an operating system, such as Windows®, iOS®, Android®, macOS®, or other operating systems. In some embodiments, controller 606 can be implemented as part of processor 602.

[0185] In some embodiments, BS 600 can include at least one transceiver 608. In some other embodiments, BS 600 can have more than one transceiver 608. Transceiver 608 can represent a wireless transceiver. Transceiver 608 can include one or more receiver chains 610, one or more transmitter chains 612, or a combination thereof.

[0186] The receiver chain 610 can be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 610 can include one or more antennas for receiving signals over the air or wireless medium. The receiver chain 610 can include at least one amplifier (e.g., a low noise amplifier (LNA)) configured to amplify the received signals. The receiver chain 610 can include at least one demodulator configured to demodulate the received signals and obtain transmitted data by reversing the modulation techniques applied during transmission of the signals. The receiver chain 610 can include at least one decoder for decoding the demodulated signals to receive the transmitted data.

[0187] The transmitter chain 612 can be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 612 can include at least one modulator for modulating data onto a carrier signal in preparation for transmission of the signal over a wireless medium. The at least one modulator can be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or a digital modulation scheme, like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 612 can also include at least one power amplifier configured to amplify the modulated signal to a proper power level for transmission over a wireless medium. The transmitter chain 612 can also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0188] The description herein is presented to enable a person of ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive a first configuration including a zone-specific time alignment timer associated with a sounding reference signal (SRS) validity zone; and transmit, while the UE is in a non-connected state, an indication for acquiring, activating, or deactivating a second configuration associated with the SRS validity zone, wherein the second configuration includes an SRS configuration, a time alignment configuration, or a timing advance (TA) command.

2. The UE of claim 1, wherein the indication is a TA command request, and the at least one processor is further configured to cause the UE to receive the TA command in response to the indication.

3. The UE of claim 2, wherein: the TA command request is transmitted periodically based on a periodicity, or is transmitted based on an event, or is transmitted based on an implementation of the UE; the periodicity or the event is configured or pre-configured to the UE, or is pre-defined; the event is a difference in a reference signal received power (RSRP) value relative to a reference value being greater than a first threshold for a first time period, or a moving speed of the UE being greater than a second threshold for a second time period; and the first threshold, the first time period, the second threshold, or the second time period is configured or pre-configured to the UE, or is pre-defined.

4. The UE of claim 1, wherein the at least one processor is further configured to cause the UE to monitor for the TA command from a serving base station (BS) for a time period after each SRS transmission is performed.

5. The UE of claim 1, wherein the at least one processor is further configured to cause the UE to: start or restart the zone-specific time alignment timer in response to receiving an indication for starting the zone-specific time alignment timer; or stop the zone-specific time alignment timer in response to receiving an indication for stopping the zone-specific time alignment timer.

6. The UE of claim 1, wherein the at least one processor is further configured to cause the UE to: transmit the indication in response to an expiration of the zone-specific time alignment timer and an SRS configuration not being released, wherein the indication is a deactivation request for deactivating the unreleased SRS configuration; receive a deactivation response for deactivating the unreleased SRS configuration in response to the deactivation request; and deactivate the unreleased SRS configuration.

7. The UE of claim 1, wherein the at least one processor is further configured to cause the UE to: transmit the indication in case the zone-specific time alignment timer expires and an SRS configuration is not released, wherein the indication is an activation request for activating the unreleased SRS configuration, and wherein the activation request indicates: the unreleased SRS configuration and a cause value; or a service type or a quality of service (QoS) requirement.

8. The UE of claim 1, wherein the at least one processor is further configured to cause the UE to: transmit the indication in a case that the zone-specific time alignment timer expires and an SRS configuration is not released, wherein the indication is a request for acquiring the time alignment configuration indicating another zone-specific time alignment timer, and the request indicates the SRS configuration that is not released and a cause value.

9. The UE of claim 1, wherein the at least one processor is further configured to cause the UE to: receive a paging message in a case that the zone-specific time alignment timer expires; and transmit the indication after receiving the paging message, wherein the indication is a request for acquiring the time alignment configuration indicating another zone-specific time alignment timer.

10. The UE of claim 1, wherein the at least one processor is further configured to cause the UE to: stop SRS transmission and release an SRS configuration in response to expiration of the zone-specific time alignment timer; and transmit the indication in a case that there is a pending location service, wherein the indication is a request for acquiring a new SRS configuration, and the request indicates a cause value.

11. The UE of claim 1, wherein the at least one processor is further configured to cause the UE to: maintain one of the zone-specific time alignment timer and a cell-specific time alignment timer based on a received SRS configuration; or deactivate a cell-specific time alignment configuration in response to receiving the first configuration; or not receive a cell-specific SRS configuration and a validity zone-specific SRS configuration simultaneously; or not activate a cell-specific SRS configuration and a validity zone-specific SRS configuration simultaneously.

12. The UE of claim 1, wherein the at least one processor is further configured to cause the UE to: receive a third configuration indicating a cell-specific time alignment timer; and start or restart the zone-specific time alignment timer and the cell-specific time alignment timer in response to receiving a TA command or an indication to start the zone-specific time alignment timer or the cell-specific time alignment timer.

13. The UE of claim 12, wherein in a case that the cell-specific time alignment timer expires but the zone-specific time alignment timer is running, the at least one processor is further configured to cause the UE to: continue SRS transmission; determine an uplink (UL) out of sync for cell-specific UL transmission; stop all cell-specific UL transmission; or initiate a TA command update or request a cell-specific time alignment configuration when cell-specific UL transmission occurs.

14. The UE of claim 12, wherein in a case that the zone-specific time alignment timer expires, the at least one processor is further configured to cause the UE to: stop SRS transmission; and stop the cell-specific time alignment timer.

15. The UE of claim 1, wherein the first configuration further indicates a plurality of SRS configurations for a plurality of SRS validity zones and is received via a radio resource control (RRC) release message or a positioning system information block (posSIB) message.

16. The UE of claim 15, wherein the indication is an activation request to activate an SRS configuration of the plurality of SRS configurations.

17. The UE of claim 16, wherein the at least one processor is further configured to cause the UE to receive an activation response in response to the activation request, wherein the activation response indicates an SRS configuration of the plurality of SRS configurations and a TA command to use by the UE; or wherein the activation request indicates the SRS configuration, and the at least one processor is further configured to cause the UE to: receive an acknowledgement (ACK) in response to the activation request if the indicated SRS configuration is available; or receive an activation response in response to the activation request if the indicated SRS configuration is not available, wherein the activation response indicates a different SRS configuration of the plurality of SRS configurations; or wherein the activation request indicates a cause value.

18. A processor for wireless communication comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive a first configuration including a zone-specific time alignment timer associated with a sounding reference signal (SRS) validity zone; and transmit, when a user equipment including the processor is in a non-connected state, an indication for acquiring, activating, or deactivating a second configuration associated with the SRS validity zone, wherein the second configuration includes an SRS configuration, a time alignment configuration, or a timing advance (TA) command.

19. A base station (BS) for wireless communication comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the BS to: transmit, to a user equipment (UE), a first configuration including a zone-specific time alignment timer associated with a sounding reference signal (SRS) validity zone; and receive, when the UE is in a non-connected state, an indication for acquiring, activating, or deactivating a second configuration associated with the SRS validity zone, wherein the second configuration includes an SRS configuration, a time alignment configuration, or a timing advance (TA) command.

20. A method performed by a user equipment (UE), the method comprising: receiving a first configuration including a zone-specific time alignment timer associated with a sounding reference signal (SRS) validity zone; and transmitting, when the UE is in a non-connected state, an indication for acquiring, activating, or deactivating a second configuration associated with the SRS validity zone, wherein the second configuration includes an SRS configuration, a time alignment configuration, or a timing advance (TA) command.

Images