WO2025241614A1

WO2025241614A1 - Management of uplink transmission

Info

Publication number: WO2025241614A1
Application number: PCT/CN2025/076878
Authority: WO
Inventors: Ran YUE; Haiming Wang; Bingchao LIU
Original assignee: Lenovo Beijing Ltd
Current assignee: Lenovo Beijing Ltd
Priority date: 2025-02-11
Filing date: 2025-02-11
Publication date: 2025-11-27
Anticipated expiration: 2027-08-11

Abstract

Various aspects of the present disclosure relate to management of UL transmission. In one aspect, a UE determines a PL offset for UL transmission. The UE determines whether the PL offset is valid. If the PL offset is valid, the UE performs the UL transmission to a UL only TRP based on the PL offset.

Description

MANAGEMENT OF UPLINK TRANSMISSION

TECHNICAL FIELD

The present disclosure relates to wireless communications, and more specifically to user equipment (UE) and method for supporting management of uplink (UL) transmission.

BACKGROUND

A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. Each network communication devices, such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as UE, or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) . Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .

It has been agreed that for the asymmetric downlink (DL) single transmit-receive point (sTRP) /UL multiple TRP (mTRP) deployment scenarios, there is support to associate a transmission configuration indicator (TCI) state with a path loss (PL) offset. When the TCI state associated with the PL offset is for a UL transmission, the UE shall calculate transmission power the UL transmission based on DL PL reference signals and PL offset associated with the TCI state.

SUMMARY

The present disclosure relates to UE and method that support management of UL transmission. With the present disclosure, the UE may perform UL transmission with a valid or accurate PL offset. Thus, performance of the UL transmission may be improved.

Some implementations of a UE described herein may include a processor and a transceiver coupled to the processor, wherein the processor is configured to: determine a PL offset for UL transmission; determine whether the PL offset is valid; and based on determining that the PL offset is valid, perform the UL transmission to a UL only TRP based on the PL offset.

In some implementations, the processor is configured to determine whether the PL offset is valid by: starting or restart a timer when the PL offset is considered as valid or when the PL offset is received; and upon expiration of the timer, determining the PL offset is invalid.

In some implementations, the timer is associated with the PL offset, or the timer is associated with a TCI state associated with the PL offset.

In some implementations, each of multiple time lengths of the timer is associated with one of mobility states of the UE.

In some implementations, the processor is further configured to: update a time length of the timer based on one of scaling factors, wherein each of the scaling factors is associated with one of mobility states of the UE. In such implementations, the processor is configured to determine whether the PL offset is valid by: upon expiration of the timer with the updated time length, determining the PL offset is invalid.

In some implementations, the processor is configured to determine whether the PL offset is valid by: based on determining that change of a PL between the UE and a first TRP exceeds a PL threshold, determining the PL offset is invalid, wherein the UE expects to receive DL transmission from the first TRP.

In some implementations, the processor is further configured to: receive multiple PL thresholds via the transceiver from a first TRP, wherein each of the multiple PL thresholds is associated with one of mobility states of the UE, and the multiple PL thresholds comprises the PL threshold.

In some implementations, the processor is configured to determine whether the PL offset is valid by: based on determining that the number of transmissions or retransmissions to a first TRP or the UL only TRP within a time duration exceeds a transmission or retransmission number threshold, determining the PL offset is invalid, wherein the UE expects to receive DL transmission from the first TRP.

In some implementations, the processor is further configured to: receive multiple transmission or retransmission number thresholds via the transceiver from the first TRP, wherein each of the multiple transmission or retransmission number thresholds is associated with one of mobility states of the UE, and the multiple transmission or retransmission number thresholds comprises the retransmission number threshold.

In some implementations, the time duration is associated with one of mobility states of the UE.

In some implementations, the processor is further configured to: update the time duration based on one of scaling factors, wherein each of the scaling factors is associated with one of mobility states of the UE; and determine whether the number of retransmissions to the first TRP or the UL only TRP within the updated time duration exceeds the retransmission number threshold.

In some implementations, the processor is configured to determine whether the PL offset is valid by: based on determining that a timing advance timer (TAT) associated with the UL only TRP or with a timing advance group (TAG) associated with the UL only TRP is running, determining the PL offset is valid; and based on determining that the TAT is not running, determining the PL offset is invalid.

In some implementations, the processor is configured to determine the PL offset by: updating the PL offset based on one of scaling factors, wherein each of the scaling factors is associated with one of mobility states of the UE.

In some implementations, the processor is further configured to: based on determining that the PL offset is invalid, suspend the UL transmission to the UL only TRP.

In some implementations, the processor is further configured to: based on determining that the PL offset is invalid, trigger a request for update of the PL offset via the transceiver to a first TRP or the UL only TRP, wherein the UE expects to receive DL transmission from the first TRP.

In some implementations, the processor is further configured to: trigger a request for update of the PL offset based on determining the following: the PL offset is invalid, there is a preconfigured UL resource related to the UL only TRP, and the UL transmission is to be transmitted; and wherein the UE expects to receive DL transmission from the first TRP.

In some implementations, the processor is further configured to: transmit a request for update of the PL offset via the transceiver to a first TRP or the UL only TRP based on determining the following: the PL offset is invalid, and a configured grant is configured for the UL only TRP; and wherein the UE expects to receive DL transmission from the first TRP.

In some implementations, the processor is further configured to: transmit a request for update of the PL offset via the transceiver to a first TRP or the UL only TRP based on determining the following: the PL offset is invalid, a configured grant is configured for the UL only TRP, and UL data which can be transmitted on the configured grant arrives; and wherein the UE expects to receive DL transmission from the first TRP.

In some implementations, the processor is further configured to: based on determining that the PL offset is invalid, perform the UL transmission to the UL only TRP based on a default PL offset.

In some implementations, the processor is further configured to: apply an updated PL offset at one of the following: a first time instance when the updated PL offset is received, a second time instance when the updated PL offset is confirmed to be received, a third time instance after the updated PL offset is received, or a fourth time instance which is indicated by a first TRP, wherein the UE expects to receive DL transmission from the first TRP; or apply the updated PL offset upon expiration of a configured or predefined time duration, wherein a starting point of the configured or predefined time duration is the fourth time instance.

In some implementations, the processor is further configured to: apply an updated PL offset when a TCI state associated with the PL offset is activated; or apply an updated PL offset when a TCI state associated with the PL offset is applied.

In some implementations, the processor is further configured to: receive a signaling comprising an updated PL offset via the transceiver from a first TRP, wherein a TCI state associated with the updated PL offset is activated by the signaling, and wherein the UE expects to receive DL transmission from the first TRP.

Some implementations of a method described herein may include: determining a PL offset for UL transmission; determining whether the PL offset is valid; and based on determining that the PL offset is valid, performing the UL transmission to a UL only TRP based on the PL offset.

Some implementations of a processor described herein may include at least one memory and a controller coupled with the at least one memory and configured to cause the controller to: determine a PL offset for UL transmission; determine whether the PL offset is valid; and based on determining that the PL offset is valid, perform the UL transmission to a UL only TRP based on the PL offset.

It is to be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

Fig. 1 illustrates an example of a wireless communications system that supports management of UL transmission in accordance with aspects of the present disclosure;

Fig. 2 illustrates an example of a wireless communications system that supports management of UL transmission in accordance with aspects of the present disclosure;

Fig. 3 illustrate a flowchart of a method that supports management of UL transmission in accordance with aspects of the present disclosure;

Fig. 4 illustrates an example of change of PLs in accordance with some aspects of the present disclosure;

Fig. 5 illustrates an example of misalignment of applying of a PL offset with the applying of a TCI state associated with the PL offset;

Fig. 6 illustrates an example of a device that supports management of UL transmission in accordance with some aspects of the present disclosure; and

Fig. 7 illustrates an example of a processor that supports management of UL transmission in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

Principles of the present disclosure will now be described with reference to some embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein may be implemented in various manners other than the ones described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

References in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It shall be understood that although the terms “first” and “second” or the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and/or “including” , when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof.

As described above, when the TCI state associated with the PL offset is for a UL transmission, the UE shall calculate transmission power the UL transmission based on DL PL reference signals and PL offset associated with the TCI state. For example, the TCI state associated with the PL offset may be applied for transmission of at least one of the following: PUSCH, PUCCH or SRS. The TCI state may be a joint or UL TCI state.

It was agreed that a PL offset value can be updated for any configured TCI states with radio resource control (RRC) configured PL offset, i.e., not limited to activated TCI states.

Also, it was pointed out that a network may need to update the PL offset even for deactivated TCIs due to movement of a UE. Thus, the PL offset may be not accurate and may be not frequently updated for some cases. If the UE performs UL transmission with an in accurate PL offset, performance of the UL transmission may be degraded.

In view of the above, the present disclosure provides a solution that supports management of UL transmission. In this solution, a UE determines a PL offset for UL transmission. The UE determines whether the PL offset is valid. If the PL offset is valid, the UE performs the UL transmission to a UL only TRP based on the PL offset. With this solution, the UE may perform UL transmission with a valid or accurate PL offset. Thus, performance of the UL transmission may be improved.

Aspects of the present disclosure are described in the context of a wireless communications system.

Fig. 1 illustrates an example of a wireless communications system 100 that supports management of UL transmission in accordance with aspects of the present disclosure. The wireless communications system 100 may include one at least one of network entities 102 (also referred to as network equipment (NE) ) , one or more terminal devices or UEs 104, a core network 106, and a packet data network 108. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.

The network entities 102 may be collectively referred to as network entities 102 or individually referred to as a network entity 102. Hereinafter, some implementations of the present disclosure will be described by taking a base station as an example of the network entity 102. Thus, the network entity 102 may be used interchangeably with the base station 102.

The network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station (BS) , a network element, a radio access network (RAN) node, a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. A network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signalling, transmit signalling) over a Uu interface.

A network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112. For example, a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies. In some implementations, a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an internet-of-things (IoT) device, an internet-of-everything (IoE) device, or machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In some other implementations, a UE 104 may be mobile in the wireless communications system 100.

The one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in Fig. 1. A UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in Fig. 1. Additionally, or alternatively, a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.

A UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

A network entity 102 may support communications with the core network 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) . In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102) . In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) . In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) . An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .

In some implementations, the network entity 102 may be implemented as a satellite. For example, the network entity 102-3 may be implemented as a satellite. Thus, network entity 102-3 is also referred to as a satellite 102-3. The network entity 102-3 may have full or part of an eNB/gNB on board. The communication link 110 between the satellite 102-3 and the UE 104, the communication link 116 between the satellite 102-3 and the network entity 102, and the communication link 116 between the satellite 102-3 and the core network 106 may be used for a non-terrestrial network (NTN) transparent mode. The communication link 110 between the satellite 102-3 and the UE 104, and the communication link 116 between the satellite 102-3 (with a base station on board) and the core network 106 may be used for a NTN regenerative mode.

In some implementations, a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open radio access network (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) . For example, a network entity 102 may include one or more of a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a RAN intelligent controller (RIC) (e.g., a near-real time RIC (Near-RT RIC) , a non-real time RIC (Non-RT RIC) ) , a service management and orchestration (SMO) system, or any combination thereof.

An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) . In some implementations, one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .

Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU. For example, a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signalling (e.g., radio resource control (RRC) , service data adaption protocol (SDAP) , packet data convergence protocol (PDCP) ) . The CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signalling, and may each be at least partially controlled by the CU 160.

Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or multiple different cells (e.g., via one or more RUs) . In some implementations, a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .

A CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u) , and a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface) . In some implementations, a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.

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

The core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102. The core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) . The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106) .

In the wireless communications system 100, the network entities 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) . In some implementations, the network entities 102 and the UEs 104 may support different resource structures. For example, the network entities 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the network entities 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) . The network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.

One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may 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., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames) . Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) . In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (510 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) . In some implementations, the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) . In some implementations, FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) . For example, FR1 may be associated with a first numerology (e.g., μ=0) , which includes 15 kHz subcarrier spacing; a second numerology (e.g., μ=1) , which includes 30 kHz subcarrier spacing; and a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) . For example, FR2 may be associated with a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., μ=3) , which includes 120 kHz subcarrier spacing.

Fig. 2 illustrates an example of a wireless communications system 200 that supports management of UL transmission in accordance with aspects of the present disclosure. The wireless communications system 200 may be considered as an example implementation of the wireless communications system 100 in Fig. 1.

As shown in Fig. 2, the wireless communications system 200 may comprise UEs 210, 212, 214 and 216, UL only TRPs 220 and 222 as well as a first TRP 230.

In some implementations, each of the UEs 210, 212, 214 and 216 may be implemented as the UE 104 in Fig. 1.

In some implementations, each of the UL only TRPs 220 and 222 as well as the first TRP 230 may be implemented as the network entity 102 in Fig. 1.

In some implementations, the UE 210 may perform UL transmission toward at least one of the UL only TRP 220 and the first TRP 230.

In some implementations, from the perspective of the UE, if the UE is configured with a PL offset in joint/UL TCI state (s) , the UE does not expect to receive DL transmission from UL TRP(s) , else, the UE may expect to receive DL transmission from at least one UL TRP.

For example, if the UE 210 is configured with at least one PL offset, each PL offset is associated with a joint/UL TCI state, the UE 210 does not expect to receive synchronization signal block (SSB) from the UL only TRP 220.

In some implementations, the first TRP 230 is capable of DL transmission and UL reception or the first TRP 230 is capable of DL transmission. For example, the first TRP 230 is capable of DL transmission to any of the UEs 210, 212, 214 and 216. Each of the UEs 210, 212, 214 and 216 may expect to receive DL transmission e.g. SSB from the first TRP 230.

In the present disclosure, if the UE 210 expects to receive DL transmission from a TRP, the TRP is referred to as a UL TRP or a DL/UL capable TRP or a DL/UL TRP or a DL TRP. For example, the first TRP 230 is also referred to as a UL TRP 230 or a DL/UL capable TRP 230 or a DL/UL TRP 230 or a DL TRP 230.

In some implementations, the UE 212 may perform UL transmission toward at least one of the UL only TRP 220 and the first TRP 230. The UE 212 does not expect to receive DL transmission e.g. SSB from the UL only TRP 220.

In some implementations, the UE 214 may only perform UL transmission toward the UL only TRP 222. The UE 214 does not expect to receive DL transmission from the UL only TRP 222. The UE 214 may only perform DL reception from the first TRP 230.

In some implementations, the UE 216 may perform UL transmission toward the first TRP 230. The UE 212 may expect to receive DL transmission from the first TRP 230.

In some implementations, the wireless communications system 200 may comprise a further UE (not shown) which may perform UL transmissions toward more than one UL only TRPs.

It may be understood that Fig. 2 illustrates an asymmetric DL sTRP/UL mTRP deployment scenario. In this scenario, the wireless communications system 200 comprises a DL sTRP (i.e., the first TRP 230) and UL mTRP (i.e., the UL only TRPs 220 and 222 as well as the first TRP 230) .

Fig. 3 illustrate a flowchart of a method 300 that supports management of UL transmission in accordance with aspects of the present disclosure. In some implementations, the method 300 can be implemented at a UE, such as the UE 210, 212 or 214 as shown in Fig. 2. For the purpose of discussion, the method 300 will be described with reference to Fig. 2 by taking the UE 210 as example.

At 310, the UE 210 determines a PL offset for UL transmission.

At 320, the UE 210 determines whether the PL offset is valid.

In the present disclosure, the term “invalid” may be used interchangeably with the term “unavailable” , and the term “valid” may be used interchangeably with the term “available” .

At 330, if the PL offset is valid, the UE 210 performs the UL transmission to the UL only TRP 220 based on the PL offset.

With the method 300, the UE 210 may perform UL transmission with a valid or accurate PL offset. Thus, performance of the UL transmission may be improved.

Hereinafter, some implementations of determining whether the PL offset is valid will be described.

In some implementations, a timer may be defined or configured to control validity of a PL offset. The UE 210 may start or restart the timer when the PL offset is considered as valid or when the PL offset is received by the UE 210. Upon expiration of the timer, the UE 210 may determine the PL offset is invalid.

In some implementations, the timer may be associated with the PL offset, or the timer may be associated with a TCI state associated with the PL offset.

In some implementations, a PL threshold may be predefined or configured to monitor change of the UE 210 and the first TRP 230. If change of a PL between the UE 210 and the first TRP 230 exceeds the PL threshold, the UE 210 may determine the PL offset is invalid.

In some implementations, if change of the PL between the UE 210 and the first TRP 230 exceeds the PL threshold, the UE 210 may determine the PL offset is invalid before an updated PL offset is indicated by the first TRP 230.

In some implementations, the change of the PL between the UE 210 and the first TRP 230 may be relative to a PL between the UE 210 and the first TRP 230 measured at reference time. This will be described with reference to Fig. 4.

Fig. 4 illustrates an example of change of PLs in accordance with some aspects of the present disclosure. In the example of Fig. 4, at T0, the UE 210 may receive an indication from the first TRP 230. For example, at T0, the UE 210 may receive reference signal received power (RSRP) of DL transmission from the first TRP 230. T0 may be used as reference time for determining change of the PL between the UE 210 and the first TRP 230. At T0, the UE 210 measures a PL#0 between the UE 210 and the first TRP 230. The PL#0 may be used as a PL reference. Then, the change of the PL between the UE 210 and the first TRP 230 may be relative to the PL#0 measured at reference time T0.

At T1, the UE 210 measures a PL#1 between the UE 210 and the first TRP 230. A difference of the PL#0 and the PL#1 may be below the PL threshold. In other words, change of the PL between the UE 210 and the first TRP 230 does not exceed the PL threshold.

At T2, the UE 210 measures a PL#2 between the UE 210 and the first TRP 230. A difference of the PL#0 and the PL#2 may exceed the PL threshold. In other words, change of the PL between the UE 210 and the first TRP 230 exceeds the PL threshold. Thus, the UE 210 may determine the PL offset is invalid. In some implementations, if the UE 210 determines the PL offset is invalid, the UE 210 may perform an appropriate action. This will be described later.

At T3, the UE 210 may receive an updated PL offset from the first TRP 230 or an RRC reconfiguration message from the first TRP 230. T3 may be used as new reference time for determining change of the PL between the UE 210 and the first TRP 230. Then, the change of the PL between the UE 210 and the first TRP 230 may be relative to a PL measured at the new reference time T3. It shall be noted that the reference time is not limited to the time point for update of PL offset in the present disclosure.

In some implementations, a time duration and a transmission number threshold may be predefined or configured to control validity of a PL offset. If the number of transmissions to or from the first TRP 230 or the UL only TRP 220 within the time duration exceeds the transmission number threshold, the UE 210 may determine the PL offset is invalid. For example, if the number of UL transmissions to the first TRP 230 or the UL only TRP 220 within the time duration exceeds the transmission number threshold, the UE 210 may determine the PL offset is invalid. Alternatively, if the number of DL transmissions from the first TRP 230 within the time duration exceeds the transmission number threshold, the UE 210 may determine the PL offset is invalid.

In some implementations, a time duration and a retransmission number threshold may be predefined or configured to control validity of a PL offset. If the number of retransmissions to the first TRP 230 or the UL only TRP 220 within the time duration exceeds the transmission number threshold, the UE 210 may determine the PL offset is invalid. For example, if the number of UL retransmissions to the first TRP 230 or the UL only TRP 220 within the time duration exceeds the retransmission number threshold, the UE 210 may determine the PL offset is invalid. Alternatively, if the number of DL retransmissions from the first TRP 230 within the time duration exceeds the retransmission number threshold, the UE 210 may determine the PL offset is invalid. In some implementations, the retransmissions may be Hybrid Automatic Repeat reQuest (HARQ) retransmissions or RLC retransmissions.

In some implementations, if a timing advance timer (TAT) associated with the UL only TRP 220 or with a timing advance group (TAG) associated with the UL only TRP 220 is running, the UE 210 may determine the PL offset is valid. If the TAT is not running, the UE 210 may determine the PL offset is invalid.

In some implementations, there is a need to improve UL performance in different mobility states of the UE 210 especially for the UE 210 supporting multiple transmission antennas. In general, it is the UE 210 itself that identifies the mobility state other than the network node 102. Therefore, the effect of the mobility state on the PL offset may also be discussed.

In some implementations, the mobility state of the UE 210 may comprise one of the following: a high-mobility state, a medium-mobility state and a normal-mobility state.

In some implementations, if number of handovers during time period T_CRmax exceeds N_{CR_H}, the mobility state of the UE 210 may be the high-mobility state. Alternatively, if number of handovers during time period T_CRmax is greater than N_{CR_H}, the mobility state of the UE 210 may be the high-mobility state.

In some implementations, if number of handovers during time period T_CRmax exceeds N_{CR_M} and not exceeds N_{CR_H}, the mobility state of the UE 210 may be the medium-mobility state. Alternatively, if number of handovers during time period T_CRmax is greater than or equal to N_{CR_M} but less than or equal to N_{CR_H}, the mobility state of the UE 210 may be the medium-mobility state.

In some implementations, if number of handovers during time period T_CRmax is less than N_{CR_M}, the mobility state of the UE 210 may be the normal-mobility state.

In some implementations, a timer may be defined or configured to control validity of a PL offset. The UE 210 may start or restart the timer when the PL offset is considered as valid or when the PL offset is received by the UE 210. Upon expiration of the timer, the UE 210 may determine the PL offset is invalid. In some implementations, multiple time lengths of the timer may be predefined or configured for different mobility states of the UE 210. Each of the multiple time lengths of the timer may be associated with one of mobility states of the UE 210.

For example, a first time length, a second time length and a third time length of the timer may be predefined or configured for the high-mobility state of the UE 210, the medium-mobility state of the UE 210, and a normal-mobility state of the UE 210, respectively.

If the UE 210 is in the high-mobility state and the timer expires after starting or restarting to run for the first time length, the UE 210 may determine the PL offset is invalid.

If the UE 210 is in the medium-mobility state and the timer expires after starting or restarting to run for the second time length, the UE 210 may determine the PL offset is invalid.

If the UE 210 is in the normal-mobility state and the timer expires after starting or restarting to run for the third time length, the UE 210 may determine the PL offset is invalid.

In some implementations, multiple PL thresholds may be predefined or configured to monitor change of the UE 210 and the first TRP 230. If change of a PL between the UE 210 and the first TRP 230 exceeds one of the multiple PL thresholds, the UE 210 may determine the PL offset is invalid.

For example, a first PL threshold, a second PL threshold and a third PL threshold may be predefined or configured for the high-mobility state of the UE 210, the medium-mobility state of the UE 210, and a normal-mobility state of the UE 210, respectively.

If the UE 210 is in the high-mobility state and change of a PL between the UE 210 and the first TRP 230 exceeds the first PL threshold, the UE 210 may determine the PL offset is invalid.

If the UE 210 is in the medium-mobility state and change of a PL between the UE 210 and the first TRP 230 exceeds the second PL threshold, the UE 210 may determine the PL offset is invalid.

If the UE 210 is in the normal-mobility state and change of a PL between the UE 210 and the first TRP 230 exceeds the third PL threshold, the UE 210 may determine the PL offset is invalid.

In some implementations, a time duration and multiple transmission or retransmission number thresholds may be predefined or configured to control validity of a PL offset. Each of the multiple transmission or retransmission number thresholds may be associated with one of mobility states of the UE 210.

For example, a first transmission or retransmission number threshold, a second transmission or retransmission number threshold and a third transmission or retransmission number threshold may be predefined or configured for the high-mobility state of the UE 210, the medium-mobility state of the UE 210, and a normal-mobility state of the UE 210, respectively.

If the UE 210 is in the high-mobility state and the number of transmissions or retransmissions within the time duration exceeds the first transmission or retransmission number threshold, the UE 210 may determine the PL offset is invalid.

If the UE 210 is in the medium-mobility state and the number of transmissions or retransmissions within the time duration exceeds the second transmission or retransmission number threshold, the UE 210 may determine the PL offset is invalid.

If the UE 210 is in the normal-mobility state and the number of transmissions or retransmissions within the time duration exceeds the third transmission or retransmission number threshold, the UE 210 may determine the PL offset is invalid.

In some implementations, the transmissions or retransmissions within the time duration may be transmissions or retransmissions to the first TRP 230 or the UL only TRP 220 within the time duration. Alternatively, the transmissions or retransmissions within the time duration may be transmissions or retransmissions from the first TRP 230 within the time duration.

In some implementations, the retransmissions may be HARQ retransmissions or RLC retransmissions.

In some implementations, multiple time durations and a transmission or retransmission number threshold may be predefined or configured to control validity of a PL offset. The multiple time durations may be predefined or configured for different mobility states of the UE 210. Each of the multiple time durations may be associated with one of mobility states of the UE 210.

For example, a first time duration, a second time duration and a third time duration may be predefined or configured for the high-mobility state of the UE 210, the medium-mobility state of the UE 210, and a normal-mobility state of the UE 210, respectively.

If the UE 210 is in the high-mobility state and the number of transmissions or retransmissions within the first time duration exceeds the transmission or retransmission number threshold, the UE 210 may determine the PL offset is invalid.

If the UE 210 is in the medium-mobility state and the number of transmissions or retransmissions within the second time duration exceeds the transmission or retransmission number threshold, the UE 210 may determine the PL offset is invalid.

If the UE 210 is in the normal-mobility state and the number of transmissions or retransmissions within the third time duration exceeds the transmission or retransmission number threshold, the UE 210 may determine the PL offset is invalid.

In some implementations, multiple PL offsets may be configured for the UE 210. If the UE 210 determines one of the multiple PL offsets is invalid, the UE 210 may determines all of the multiple PL offsets are invalid.

In some implementations, multiple PL offsets may be configured for the UE 210. If the UE 210 determines one of the multiple PL offsets is invalid, the UE 210 may determines the PL offset associated with an active TCI state is invalid.

In some implementations, multiple scaling factors may be predefined or configured for the UE 210. Each of the scaling factors may be associated with one of mobility states of the UE 210. The UE 210 may update the PL offset based on one of scaling factors.

For example, a first scaling factor, a second scaling factor and a third scaling factor may be predefined or configured for the high-mobility state of the UE 210, the medium-mobility state of the UE 210, and a normal-mobility state of the UE 210, respectively.

If the UE 210 is in the high-mobility state, the UE 210 may update the PL offset based on the first scaling factor. For example, the UE 210 may update a configured PL offset to be the configured PL offset multiplied by the first scaling factor.

If the UE 210 is in the medium-mobility state, the UE 210 may update the PL offset based on the second scaling factor. For example, the UE 210 may update a configured PL offset to be the configured PL offset multiplied by the second scaling factor.

If the UE 210 is in the normal-mobility state, the UE 210 may update the PL offset based on the third scaling factor. For example, the UE 210 may update a configured PL offset to be the configured PL offset multiplied by the third scaling factor.

As described above, in some implementations, a timer may be defined or configured to control validity of a PL offset. In such implementations, multiple scaling factors may be predefined or configured for the UE 210. Each of the scaling factors may be associated with one of mobility states of the UE 210. The UE 210 may update a time length of the timer based on one of scaling factors. The UE 210 may start or restart the timer when the PL offset is considered as valid or when the PL offset is received by the UE 210. Upon expiration of the timer with the updated time length, the UE 210 may determine the PL offset is invalid. In other words, when the timer expires after starting or restarting to run for the updated time length, the UE 210 may determine the PL offset is invalid.

If the UE 210 is in the high-mobility state, the UE 210 may update the time length of the timer based on the first scaling factor. For example, the UE 210 may update the time length of the timer to be the time length multiplied by the first scaling factor. When the timer expires after starting or restarting to run for the updated time length, the UE 210 may determine the PL offset is invalid.

If the UE 210 is in the medium-mobility state, the UE 210 may update the time length of the timer based on the second scaling factor. For example, the UE 210 may update the time length of the timer to be the time length multiplied by the second scaling factor. When the timer expires after starting or restarting to run for the updated time length, the UE 210 may determine the PL offset is invalid.

If the UE 210 is in the normal-mobility state, the UE 210 may update the time length of the timer based on the third scaling factor. For example, the UE 210 may update the time length of the timer to be the time length multiplied by the third scaling factor. When the timer expires after starting or restarting to run for the updated time length, the UE 210 may determine the PL offset is invalid.

Hereinafter, some implementations of UE behaviors when the PL offset is invalid will be described.

In some implementations, if the PL offset is invalid, the UE 210 may suspend the UL transmission to the UL only TRP 220.

In some implementations, the UE 210 may receive, from the first TRP 230, a signaling to activate a TCI state while the PL offset associated with the new active TCI state is invalid. The UE 210 may activate the TCI state based on the signaling. Then, the UE 210 may determines that the PL offset associated with the new active TCI state is invalid. In turn, the UE 210 may suspend the UL transmission to the UL only TRP 220.

In some implementations, if the PL offset is invalid, a MAC entity of the UE 210 may suspend the UL transmission to the UL only TRP 220. For example, if the PL offset is invalid, the MAC entity may stop at least one of the following UL operations: RACH, scheduling request (SR) , sounding reference signal (SRS) and HARQ on the UL only TRP 220.

In some implementations, if the PL offset is invalid, the MAC entity may perform at least one of the following: notifying an RRC entity of the UE 210 to release physical uplink control channel (PUCCH) , if configured for the UL only TRP 220; notifying the RRC entity to release SRS, if configured for the UL only TRP 220; clearing any configured downlink assignments and configured uplink grants for the UL only TRP 220; or clearing any physical uplink shared channel (PUSCH) resource for semi-persistent channel state information (CSI) reporting for the UL only TRP 220.

In some implementations, the UE 210 (such as the MAC entity of the UE 210) may resume the UL transmission to the UL only TRP 220 when receiving an indication of an updated PL offset associated the active TCI state or when another TCI state (for which the PL offset is valid) used for the UL only TRP 220 is activated.

In some implementations, if the PL offset is invalid, the UE 210 may trigger a request for update of the PL offset.

In some implementations, the UE 210 may trigger a request for update of the PL offset based on determining the following: the PL offset is invalid, there is a preconfigured UL resource related to the UL only TRP 220, and the UL transmission is to be transmitted.

In some implementations, the UE 210 may trigger a request for update of the PL offset based on determining the following: the PL offset is invalid, and a configured grant is configured for the UL only TRP 220.

In some implementations, the UE 210 may trigger a request for update of the PL offset based on determining the following: the PL offset is invalid, a configured grant is configured for the UL only TRP 220, and UL data which can be transmitted on the configured grant arrives

In some implementations, the UE 210 may transmit the triggered request for update of the PL offset to the first TRP 230 or the UL only TRP 220.

In some implementations, if the UE 210 receives an updated PL offset from the first TRP 230 before transmitting the triggered request for update of the PL offset, the UE 210 may cancel the triggered request for update of the PL offset. Thus, the UE 210 may not transmit the triggered request for update of the PL offset to the first TRP 230 or the UL only TRP 220.

In some implementations, a default PL offset may be defined or configured for the UE 210. For example, the default PL offset may be an allowed maximum value of a PL offset. If the PL offset is invalid, the UE 210 may perform the UL transmission to the UL only TRP 220 based on the default PL offset.

In some implementations, the UE 210 may be configured with multiple PL offsets, each of which is associated with a TCI state. If one of the PL offsets is invalid, the UE 210 may update all of the configured PL offsets to be the default PL offset. Alternatively, if at least one of the PL offsets is invalid, the UE 210 may update all of the at least one invalid PL offset to be the default PL offset.

In some implementations, a default PL offset may be defined or configured for the UE 210. If the PL offset is invalid, the UE 210 may suspend the UL transmission to the UL only TRP 220 based on the invalid PL offset. For example, if the PL offset is invalid, the MAC entity may stop at least one of the following UL operations based on the invalid PL offset: RACH, SR, SRS and HARQ on the UL only TRP 220. Then, the UE 210 may perform the UL transmission to the UL only TRP 220 based on the default PL offset.

In some implementations, a first MAC CE may be used for update of a PL offset and a second MAC CE may be used for activating a TCI state associated with the updated PL offset. The first MAC CE and the second MAC CE may not be transmitted simultaneously. Thus, there could be a scenario where an initial value of a PL offset associated with a TCI state is configured to the UE 210, then the TCI state is activated. The first MAC CE for updating the PL offset is received before the TCI state is applied. Thus, the applying of the PL offset may not align with the applying of the TCI state, which may lead to a failed UL transmission. There could be another scenario where the TCI state associated with the PL offset is activated before an updated value of the PL offset associated with the TCI state is received. This may also lead to a failed UL transmission.

Fig. 5 illustrates an example of misalignment of applying of a PL offset with the applying of a TCI state associated with the PL offset. In the example of Fig. 5, at T1, a network node transmits a first MAC CE comprising a PL offset #1 to a UE. The UE may apply the PL offset #1 after a time duration. For example, the UE may apply the PL offset #1 at T2 after T1. Then, at T3 after T1, the network node transmits a second MAC CE for activating a TCI state associated with the PL offset #1. The UE may apply the TCI state after a time duration. For example, the UE may apply the TCI state at T4 after T3. When the UE applies the TCI state at T4, the UE may assume a PL offset #0 which was applied at T2. Thus, the time (T3) when the PL offset #1 is applied does not align with the time (T4) when the TCI state associated with the PL offset #1 is applied, which may lead to a failed UL transmission.

In order to solve the above issue, in some implementations, the UE 210 may apply an updated PL offset as soon as possible. For example, the UE 210 may apply an updated PL offset as soon as possible based on capability of the UE 210.

In some implementations, the UE 210 may apply an updated PL offset at a first time instance when the updated PL offset is received.

Alternatively, in some implementations, the UE 210 may apply the updated PL offset at a second time instance when the updated PL offset is confirmed to be received.

Alternatively, in some implementations, the UE 210 may apply the updated PL offset at a third time instance after the updated PL offset is received. For example, the UE 210 may apply the updated PL offset in a next frame, subframe or slot after a frame, subframe or slot where the updated PL offset is received.

Alternatively, in some implementations, the UE 210 may apply the updated PL offset at a fourth time instance which is indicated by the first TRP 230.

For example, the first TRP 230 may transmit, to the UE 210, a MAC CE comprising the updated PL offset and the fourth time instance.

For another example, the first TRP 230 may transmit, to the UE 210, a first MAC CE comprising the updated PL offset and a second MAC CE comprising the fourth time instance.

For a further example, the first TRP 230 may transmit, to the UE 210, a first MAC CE comprising the updated PL offset and downlink control information (DCI) comprising the fourth time instance. The DCI may schedule transmission of the first MAC CE.

Alternatively, in some implementations, the UE 210 may apply the updated PL offset upon expiration of a configured or predefined time duration. A starting point of the configured or predefined time duration is the fourth time instance. For example, the first TRP 230 may transmit, to the UE 210, an RRC message, a MAC CE or DCI comprising the time duration.

Alternatively, in some implementations, the UE 210 may apply an updated PL offset when a TCI state associated with the PL offset is activated.

Alternatively, in some implementations, the UE 210 may apply an updated PL offset when a TCI state associated with the PL offset is applied.

Alternatively, in some implementations, if a the time gap or time difference between the first MAC CE for update of the PL offset and the second MAC CE for activating the TCI state associated with the updated PL offset is less than a predefined/configured time length, the UE 210 may apply the updated PL offset at one of the following: the first time instance, the second time instance, the third time instance or the fourth time instance.

Alternatively, in some implementations, if a the time gap or time difference between the first MAC CE for update of the PL offset and the second MAC CE for activating the TCI state associated with the updated PL offset is less than a predefined/configured time length, the UE 210 may apply the updated PL offset upon expiration of the configured or predefined time duration. The starting point of the configured or predefined time duration is the fourth time instance.

Alternatively, in some implementations, if a the time gap or time difference between the first MAC CE for update of the PL offset and the second MAC CE for activating the TCI state associated with the updated PL offset is less than a predefined/configured time length, the UE 210 may apply an updated PL offset when a TCI state associated with the PL offset is activated.

Alternatively, in some implementations, if a the time gap or time difference between the first MAC CE for update of the PL offset and the second MAC CE for activating the TCI state associated with the updated PL offset is less than a predefined/configured time length, the UE 210 may apply an updated PL offset when a TCI state associated with the PL offset is applied.

In some implementations, the UE 210 may receive a signaling comprising an updated PL offset from the first TRP 230. A TCI state associated with the updated PL offset is activated by the signaling. For example, the first TRP 230 may transmit, to the UE 210, a MAC CE comprising the updated PL offset. The MAC CE also activates the TCI state associated with the updated PL offset.

In such implementations, the UE 210 may apply the updated PL offset and the TCI state associated with the updated PL offset in the first slot that is after slotwhere k is the slot where the UE 210 would transmit a PUCCH with HARQ-ACK information for the physical downlink shared channel (PDSCH) providing the MAC CE, is the number of slots per subframe, μ is the sub-carrier spacing (SCS) configuration for the PUCCH transmission that is determined in the slot when the MAC CE is applied.

Fig. 6 illustrates an example of a device 600 that support management of UL transmission in accordance with aspects of the present disclosure. The device 600 may be an example of a network entity 102 or a UE 104 as described herein. The device 600 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 600 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 602, a memory 604, a transceiver 606, and, optionally, an I/O controller 608. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 602, the memory 604, the transceiver 606, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 602, the memory 604, the transceiver 606, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

In some implementations, the processor 602, the memory 604, the transceiver 606, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 602 and the memory 604 coupled with the processor 602 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 602, instructions stored in the memory 604) .

For example, the processor 602 may support wireless communication at the device 600 in accordance with examples as disclosed herein. The processor 602 may be configured to operable to support a means for performing the following: determining a PL offset for UL transmission; determining whether the PL offset is valid; and based on determining that the PL offset is valid, performing the UL transmission to a UL only TRP based on the PL offset.

The processor 602 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some implementations, the processor 602 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 602. The processor 602 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 604) to cause the device 600 to perform various functions of the present disclosure.

The memory 604 may include random access memory (RAM) and read-only memory (ROM) . The memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 602 cause the device 600 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 602 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 604 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The I/O controller 608 may manage input and output signals for the device 600. The I/O controller 608 may also manage peripherals not integrated into the device M02. In some implementations, the I/O controller 608 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 608 may utilize an operating system such asor another known operating system. In some implementations, the I/O controller 608 may be implemented as part of a processor, such as the processor 606. In some implementations, a user may interact with the device 600 via the I/O controller 608 or via hardware components controlled by the I/O controller 608.

In some implementations, the device 600 may include a single antenna 610. However, in some other implementations, the device 600 may have more than one antenna 610 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 606 may communicate bi-directionally, via the one or more antennas 610, wired, or wireless links as described herein. For example, the transceiver 606 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 606 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 610 for transmission, and to demodulate packets received from the one or more antennas 610. The transceiver 606 may include one or more transmit chains, one or more receive chains, or a combination thereof.

A transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) . The transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) . The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmit chain may also include one or more antennas 610 for transmitting the amplified signal into the air or wireless medium.

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

Fig. 7 illustrates an example of a processor 700 that support management of UL transmission in accordance with aspects of the present disclosure. The processor 700 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 700 may include a controller 702 configured to perform various operations in accordance with examples as described herein. The processor 700 may optionally include at least one memory 704, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 700 may optionally include one or more arithmetic-logic units (ALUs) 706. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 700 may be a processor chipset and include a protocol stack (e.g., a 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 may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 700) 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) , and others) .

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

The controller 702 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 704 and determine subsequent instruction (s) to be executed to cause the processor 700 to support various operations in accordance with examples as described herein. The controller 702 may be configured to track memory address of instructions associated with the memory 704. The controller 702 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 702 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 700 to cause the processor 700 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 702 may be configured to manage flow of data within the processor 700. The controller 702 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 700.

The memory 704 may include one or more caches (e.g., memory local to or included in the processor 700 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 704 may reside within or on a processor chipset (e.g., local to the processor 700) . In some other implementations, the memory 704 may reside external to the processor chipset (e.g., remote to the processor 700) .

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

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

The processor 700 may support wireless communication at the device 600 in accordance with examples as disclosed herein. The processor 700 may be configured to operable to support a means for performing the following: determining a PL offset for UL transmission; determining whether the PL offset is valid; and based on determining that the PL offset is valid, performing the UL transmission to a UL only TRP based on the PL offset.
[0001]It shall be noted that implementations of the present disclosure which have been
described with reference to Figs. 1 to 5 are also applicable to the device 600 and the processor 700.

It should be noted that the methods described herein describes possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

As used herein, including in the claims, an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

A user equipment (UE) , comprising:

a processor; and

a transceiver coupled to the processor,

wherein the processor is configured to:

determine a path loss (PL) offset for uplink (UL) transmission;

determine whether the PL offset is valid; and

based on determining that the PL offset is valid, perform the UL transmission to a UL only transmission reception point (TRP) based on the PL offset.
The UE of claim 1, wherein the processor is configured to determine whether the PL offset is valid by:

starting or restarting a timer when the PL offset is considered as valid or when the PL offset is received; and

upon expiration of the timer, determining the PL offset is invalid.
The UE of claim 2, wherein each of multiple time lengths of the timer is associated with one of mobility states of the UE.
The UE of claim 2, wherein the processor is further configured to:

update a time length of the timer based on one of scaling factors, wherein each of the scaling factors is associated with one of mobility states of the UE; and

wherein the processor is configured to determine whether the PL offset is valid by:

upon expiration of the timer with the updated time length, determining the PL offset is invalid.
The UE of claim 1, wherein the processor is configured to determine whether the PL offset is valid by:

based on determining that change of a PL between the UE and a first TRP exceeds a PL threshold, determining the PL offset is invalid, wherein the UE expects to receive downlink (DL) transmission from the first TRP.
The UE of claim 1, wherein the processor is configured to determine whether the PL offset is valid by:

based on determining that the number of transmissions or retransmissions to a first TRP or the UL only TRP within a time duration exceeds a transmission or retransmission number threshold, determining the PL offset is invalid, wherein the UE expects to receive downlink (DL) transmission from the first TRP.
The UE of claim 6, wherein the processor is further configured to:

receive multiple transmission or retransmission number thresholds via the transceiver from the first TRP, wherein each of the multiple transmission or retransmission number thresholds is associated with one of mobility states of the UE, and the multiple transmission or retransmission number thresholds comprises the retransmission number threshold.
The UE of claim 1, wherein the processor is configured to determine whether the PL offset is valid by:

based on determining that a timing advance timer (TAT) associated with the UL only TRP or with a timing advance group (TAG) associated with the UL only TRP is running, determining the PL offset is valid; and

based on determining that the TAT is not running, determining the PL offset is invalid.
The UE of claim 1, wherein the processor is configured to determine the PL offset by:

updating the PL offset based on one of scaling factors, wherein each of the scaling factors is associated with one of mobility states of the UE.
The UE of claim 1, wherein the processor is further configured to:

based on determining that the PL offset is invalid, suspend the UL transmission to the UL only TRP.
The UE of claim 1, wherein the processor is further configured to:

based on determining that the PL offset is invalid, trigger a request for update of the PL offset via the transceiver to a first TRP or the UL only TRP, wherein the UE expects to receive downlink (DL) transmission from the first TRP.
The UE of claim 1, wherein the processor is further configured to:

trigger a request for update of the PL offset based on determining the following:

the PL offset is invalid,

there is a preconfigured UL resource related to the UL only TRP, and

the UL transmission is to be transmitted; and

wherein the UE expects to receive downlink (DL) transmission from the first TRP.
The UE of claim 1, wherein the processor is further configured to:

trigger a request for update of the PL offset via the transceiver to a first TRP or the UL only TRP based on determining the following:

the PL offset is invalid, and

a configured grant is configured for the UL only TRP; and

wherein the UE expects to receive downlink (DL) transmission from the first TRP.
The UE of claim 1, wherein the processor is further configured to:

trigger a request for update of the PL offset via the transceiver to a first TRP or the UL only TRP based on determining the following:

the PL offset is invalid,

a configured grant is configured for the UL only TRP, and

UL data which can be transmitted on the configured grant arrives; and

wherein the UE expects to receive downlink (DL) transmission from the first TRP.
The UE of claim 1, wherein the processor is further configured to:

based on determining that the PL offset is invalid, perform the UL transmission to the UL only TRP based on a default PL offset.
The UE of claim 1, wherein the processor is further configured to:

apply an updated PL offset at one of the following:

a first time instance when the updated PL offset is received,

a second time instance when the updated PL offset is confirmed to be received,

a third time instance after the updated PL offset is received, or

a fourth time instance which is indicated by a first TRP, wherein the UE expects to receive downlink (DL) transmission from the first TRP; or

apply the updated PL offset upon expiration of a configured or predefined time duration, wherein a starting point of the configured or predefined time duration is the fourth time instance.
The UE of claim 1, wherein the processor is further configured to:

apply an updated PL offset when a transmission configuration indicator (TCI) state associated with the PL offset is activated; or

apply an updated PL offset when a transmission configuration indicator (TCI) state associated with the PL offset is applied.
The UE of claim 1, wherein the processor is further configured to:

receive a signaling comprising an updated PL offset via the transceiver from a first TRP, wherein a transmission configuration indicator (TCI) state associated with the updated PL offset is activated by the signaling, and wherein the UE expects to receive downlink (DL) transmission from the first TRP.
A processor for wireless communication, comprising:

at least one memory; and

a controller coupled with the at least one memory and configured to cause the controller to:

determine a path loss (PL) offset for uplink (UL) transmission;

determine whether the PL offset is valid; and

based on determining that the PL offset is valid, perform the UL transmission to a UL only transmission reception point (TRP) based on the PL offset.
A method for wireless communication, comprising:

determining a path loss (PL) offset for uplink (UL) transmission;

determining whether the PL offset is valid; and

based on determining that the PL offset is valid, performing the UL transmission to a UL only transmission reception point (TRP) based on the PL offset.