WO2023158014A1

WO2023158014A1 - Method and ue for managing uplink carrier for performing rach procedure

Info

Publication number: WO2023158014A1
Application number: PCT/KR2022/005119
Authority: WO
Inventors: Subbarayudu Mutya; Jajohn Mathew Mattam; Shreyas SREENIVASA
Original assignee: Samsung Electronics Co., Ltd.
Priority date: 2022-02-16
Filing date: 2022-04-08
Publication date: 2023-08-24

Abstract

Various embodiments herein provide a method for managing an UL carrier for performing a RACH procedure by a UE. The method includes determining that a RACH procedure is completed with a network entity through a first UL carrier. The method includes starting timers to suspend triggering of a subsequent RACH procedure through a second UL carrier. The method includes determining whether the timers are expired upon detecting that a RACH triggering criteria is met. The method includes waiting till expiry of the timers, and triggering the subsequent RACH procedure through the second UL carrier when the RACH triggering criteria is met after expiry of the timers, upon determining that the timers are not expired. The method includes triggering the subsequent RACH procedure through the second UL carrier, upon determining that the timers are expired.

Description

METHOD AND UE FOR MANAGING UPLINK CARRIER FOR PERFORMING RACH PROCEDURE

The present disclosure relates to a wireless communication system, for example, to a method and a user equipment (UE) for managing an uplink (UL) carrier for performing a random-access channel (RACH) procedure in the wireless communication system.

High frequency wireless transmission always leads to higher path loss and smaller coverage compared to lower frequency wireless transmission. Therefore, a lower-frequency carrier is additionally used in a UE for UL transmission in addition to a high frequency carrier which is generally used for downlink (DL) and UL transmissions. The additional lower-frequency carrier is called supplementary uplink (SUL) carrier, whereas the high frequency carrier is called as normal UL (NUL) carrier.

FIG. 1A is a schematic diagram illustrating coverage of a SUL carrier and a NUL carrier for UL transmission at a UE, according to a prior art.

As shown in FIG. 1A, the SUL carrier provides more coverage to the UE (10) for the UL transmission than a coverage provided by the NUL carrier. Existing methods allow the UE (10) to switch between the SUL carrier and the NUL carrier for efficient UL transmission in response to meeting a RACH triggering criteria. The UE (10) triggers a RACH procedure in the uplink carrier to which the UE (10) wishes to switch.

A network entity (20) (e.g. base station) that is connected to the UE (10) is capable to allocate uplink resources on both the NUL carrier and the SUL carrier. However, the existing methods are only applicable and useful when the allocation of the uplink resources are only on single uplink carrier i.e. either the NUL carrier or the SUL carrier. When the network entity (20) allocates the uplink resources in both NUL and SUL, then triggering of the RACH procedure on single uplink carrier unnecessarily occurs without checking a nature of the resource allocation which does not make any change in a network behavior in allocating the uplink resources and worsens a UL transmission performance of the UE (10). If the network entity (20) randomly allocates the uplink resources over both the uplink carriers, this results in unnecessarily triggering the RACH procedure multiple times in one uplink carrier (e.g. NUL carrier) as the nature of the resource allocation will not get changed even if the UE (10) triggers the RACH procedure towards other uplink carrier (e.g. SUL carrier). Therefore, the existing methods are not providing an efficient uplink carrier switching mechanism.

FIGS. 1B and 1C are sequential diagrams illustrating signaling between the UE and a network entity for allocating uplink resources for the UL transmission at the UE, according to a prior art.

In an existing method as shown in FIG. 1B, the network entity (20) allocates the uplink resources to the UE (10) for the UL transmission through a UL carrier (NW UL A) (20A) at A31.

At A32, the UE (10) determines that the RACH triggering criteria is met after allocating the uplink resources.

At A33, the UE (10) triggers the RACH procedure to the network entity (20) through a UL carrier (NW UL B) (20B) in response to detecting that the triggering criteria is met. Further, the network entity (20) starts allocating the uplink resources for the UL transmission to the UE (10) through the NW UL B (20B).

In an existing method as shown in FIG. 1C, the network entity (20) allocates the uplink resources to the UE (10) for the UL transmission through the NW UL A (20A) and the NW UL B (20B) at B31.

At B32, the UE (10) determines that the RACH triggering criteria is met after allocating the uplink resources on both the the UL carriers (20A, 20B).

At B33, the network entity (20) reallocates the uplink resources to the UE (10) for the UL transmission through the UL carriers (20A, 20B) in response to detecting that the triggering criteria is met.

Reallocation of the uplink resources repeats whenever the RACH triggering criteria is met as given at B34 and B35. Thus, the network entity (20) allocates the resources in both the UL carriers (20A, 20B) and there is no use of the triggering RACH procedure when the network entity (20) is allocating the uplink resources over both the UL carriers (20A, 20B) (e.g. SUL carrier and the NUL carrier). Thus, it is desired to provide a solution that efficiently switches the uplink carriers at the UE (10).

The principal object of the embodiments herein is to provide a method and a UE for managing an UL carrier for performing a RACH procedure in a wireless communication system. The UE includes three new configurable timers, i.e. a RACH timer, a NUL timer, and a SUL timer, to avoid unnecessarily triggering the RACH procedure in other UL carrier while the UE is currently using one UL carrier. The timers help to avoid ping pong between SUL and NUL. Thus, the UE avoids unnecessary consumption of RACH resources, enables data continuity, and reduces network congestions.

Accordingly, various example embodiments herein provide a method for managing an UL carrier for performing a RACH procedure in a wireless communication system. The method includes determining, by a UE of the wireless communication system, that a RACH procedure is completed with a network entity of the wireless communication system through a first UL carrier. The method includes starting, by the UE, one or more timers to suspend triggering of a subsequent RACH procedure through a second UL carrier. The method includes detecting, by the UE, that a RACH triggering criteria is met. The method includes determining, by the UE, whether the one or more timers is expired. The method includes triggering the subsequent RACH procedure through the second UL carrier, in response to determining that the one or more timers is expired.

Accordingly, various ezample embodiments herein provide the UE for managing the UL carrier for performing the RACH procedure in the wireless communication system. The UE includes a memory, one or more timers, and at least one processor. The processor is configured for determining that the RACH procedure is completed with the network entity of the wireless communication system through the first UL carrier. The processor is configured for starting the one or more timers to suspend triggering of the subsequent RACH procedure through the second UL carrier. The processor is configured for detecting that the RACH triggering criteria is met. The processor is configured for determining whether the one or more timers is expired. The processor is configured for triggering the subsequent RACH procedure through the second UL carrier, in response to determining that the one or more timers is expired.

These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating various embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments, and the embodiments herein include all such modifications.

This invention is illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

FIG. 1A is a schematic diagram illustrating coverage of a SUL carrier and a NUL carrier for UL transmission at a UE, according to a prior art;

FIGS. 1B and 1C are sequential diagrams illustrating signaling between the UE and a network entity for allocating uplink resources for the UL transmission at the UE, according to a prior art;

FIG. 2 is a block diagram of a UE for managing an UL carrier for performing a subsequent RACH procedure in a wireless communication system, according to various embodiments of the disclosure;

FIG. 3 is a flow diagram illustrating a method for managing the UL carrier for performing the subsequent RACH procedure in the wireless communication system, according to various embodiments of the disclosure; and

FIG. 4 is a flow diagram illustrating a method for managing the UL carrier for performing the subsequent RACH procedure in the wireless communication system, according to various embodiments of the disclosure.

The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. The term "or" as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

As is traditional in the field, embodiments may be described and illustrated in terms of blocks which carry out a described function or functions.　These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.　The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block.　Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure.　Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another.

As defined in a 3GPP technical specification (TS) 38.321 switching between a SUL carrier and a NUL carrier in a wireless communication system is based on a reference signal received power (RSRP) threshold value (rsrp-ThresholdSSB-SUL). Switching between the NUL carrier and the SUL carrier means that UL transmission moves from one carrier to other carrier, which is done by an indication in downlink control information (DCI) and a RACH procedure. There are 2 carriers for UL i.e. SUL carrier and the NUL carrier, and 1 carrier for downlink (DL) corresponding to NUL, i.e. normal downlink (NDL) carrier used in the wireless communication system. RSRP is measured based on the NDL carrier.

A network entity in the wireless communication system configures the RSRP threshold value based the UL carrier on which the RACH procedure has to be triggered by a UE at a time of establishing connection with the network entity. If a measured RSRP of the NDL is less than the RSRP threshold value, the UE triggers the RACH procedure towards the SUL carrier. If the measured RSRP of the NDL is better than the RSRP threshold value, the UE triggers the RACH procedure towards the NUL carrier. Once the UE is in connected mode, i.e. the connection is established with the network entity, even when the measured RSRP goes below or above the RSRP threshold value, the UE does not switch the UL carrier until an established connection session ends. If there is no proper switching between the uplink carriers occurs, result in generating high transmit power at the UE which further drains a battery of the UE quickly.

As a solution to avoid a ping pong between the UL carriers, an existing method allows the UE to estimate a transmit power on both UL carriers and the RSRP, and check whether a RSRP triggering criteria is met using the estimated transmit power and the RSRP to switch between the uplink carriers.

If the RACH procedure is recently triggered over the NUL carrier, then the existing method allows the UE to monitor whether the measured RSRP < (RSRP threshold value - c_offset). c_offset is an offset used to avoid the ping pong between the UL carriers if the RSRP is near the RSRP threshold value and is continuously fluctuating above and below the RSRP threshold value. If the UE detects that the measured RSRP < (RSRP threshold value - c_offset), then the UE triggers the RACH on the SUL carrier. Similarly, if the RACH procedure is recently triggered over the SUL carrier, then the UE monitors whether the measured RSRP >= (RSRP threshold value + c_offset). If the UE detects that the measured RSRP >= (RSRP threshold value + c_offset), then the UE triggers the RACH on the NUL carrier.

Alternately, if the RACH procedure is recently triggered over the NUL carrier, then the existing method allows the UE to monitor whether (transmit power required for the SUL carrier + p_offset) < transmit power required for the NUL carrier. The p_offset is an offset used to avoid the ping pong between the UL carriers if the transmit power required for both the UL carriers are almost similar and is continuously fluctuating. If the UE detects that (transmit power required for the SUL carrier + p_offset) < transmit power required for the NUL carrier, then the UE triggers the RACH on the SUL carrier. Similarly, if the RACH procedure is recently triggered over the SUL carrier, then the UE monitors whether (transmit power required for the NUL carrier + p_offset) < transmit power required for the SUL carrier. If the UE detects that (transmit power required for the NUL carrier + p_offset) < transmit power required for the SUL carrier, then the UE triggers the RACH on the NUL carrier.

Accordingly, the embodiments herein provide a method for managing an UL carrier for performing a subsequent RACH procedure in a wireless communication system. The method includes determining, by a UE of the wireless communication system, that a RACH procedure is completed with a network entity of the wireless communication system through a first UL carrier. The method includes starting, by the UE, one or more timers to suspend triggering of the subsequent RACH procedure through a second UL carrier. The method includes detecting, by the UE, that a RACH triggering criteria is met. The method includes determining, by the UE, whether the one or more timers is expired. The method includes waiting till expiry of the one or more timers, and triggering the subsequent RACH procedure through the second UL carrier when the RACH triggering criteria is met after expiry of the one or more timers, in response to determining that the one or more timers is not expired. The method includes triggering the subsequent RACH procedure through the second UL carrier, in response to determining that the one or more timers is expired.

Accordingly, the embodiments herein provide the UE for managing the UL carrier for performing the subsequent RACH procedure in the wireless communication system. The UE includes a memory, a processor, the one or more timers, and a RACH triggering engine. The RACH triggering engine is configured for determining that the RACH procedure is completed with the network entity of the wireless communication system through the first UL carrier. The RACH triggering engine is configured for starting the one or more timers to suspend triggering of the subsequent RACH procedure through the second UL carrier. The RACH triggering engine is configured for detecting that the RACH triggering criteria is met. The RACH triggering engine is configured for determining whether the one or more timers is expired. The RACH triggering engine is configured for waiting till expiry of the one or more timers, and triggering the subsequent RACH procedure through the second UL carrier when the RACH triggering criteria is met after expiry of the one or more timers, in response to determining that the one or more timers is not expired. The RACH triggering engine is configured for triggering the subsequent RACH procedure through the second UL carrier, in response to determining that the one or more timers is expired.

Unlike existing methods and systems, the proposed UE includes three new configurable timers, i.e. a RACH timer, a NUL timer, and a SUL timer, to avoid unnecessarily triggering the RACH procedure in other UL carrier while the UE is currently using one UL carrier. The RACH timer is a timer which starts when a RACH procedure is completed in any UL carrier. The RACH timer is used to prohibit the UE from sending a RACH in other UL when it is running and avoid the ping pong between a SUL and a NUL. The SUL timer is a timer which starts when a DCI is received with UL resource for the SUL when a latest RACH procedure was triggered in the NUL. When the SUL timer is running and if the latest RACH procedure was triggered over the NUL, the UE does not trigger the subsequent RACH procedure towards the SUL. This is to avoid the ping pong between the SUL and the NUL. The NUL timer is a timer which starts when the DCI is received with the UL resource for the NUL when the latest RACH was triggered in the SUL. When the NUL timer is running and if the latest RACH was triggered over the SUL, the UE does not trigger the subsequent RACH procedure towards the NUL. This is to avoid the ping pong between the SUL and the NUL. Therefore, the propose method allows the UE to avoid unnecessary consumption of RACH resources, enable data continuity, and reduce network congestions.

Referring now to the drawings, and more particularly to FIGS. 2 and 4, there are shown various embodiments.

FIG. 2 is a block diagram of a UE (100) for managing an UL carrier for performing a subsequent RACH procedure in a wireless communication system, according to various embodiments as disclosed herein.

An example of the wireless communication system is a cellular communication system. In an embodiment, the wireless communication system includes the UE (100) and a network entity (not shown in figures), where the UE (100) is authorized to access services providing by the network entity. Example of the network entity includes, but not limited to a base station, an access and mobility management function (AMF), etc. Examples of the UE (100) includes, but not limited to a smart phone, a tablet computer, a personal digital assistance (PDA), a desktop computer, an internet of things (IoT), a wearable device, etc. In an embodiment, the UE (100) includes a RACH triggering engine (110), a memory (120), a processor (130), a communicator (140), and one or more timers (150). The one or more timers (150) are a RACH timer (151), a NUL timer (D_timer_N) (152) and a SUL timer (D_timer_S) (153). The RACH triggering engine (110) is coupled to the memory (120) and the processor (130). The RACH triggering engine (110) and the one or more timers (150) are implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.

The RACH triggering engine (110) determines that a RACH procedure is completed by the UE (100) with the network entity through a first UL carrier. The RACH triggering engine (110) starts the one or more timers (150) to suspend triggering of the subsequent RACH procedure through a second UL carrier. In an example, if the first UL carrier is a SUL carrier, then the second UL carrier is a NUL carrier, whereas if the first UL carrier is the NUL carrier, then the second UL carrier is the SUL carrier.

In an embodiment, the RACH triggering engine (110) starts the RACH timer (151) to suspend triggering of the subsequent RACH procedure through the second UL carrier. Further, the RACH triggering engine (110) receives a DCI from the network entity for allocating uplink resources. Further, the RACH triggering engine (110) allocates the uplink resources based on the DCI. Further, the RACH triggering engine (110) starts the SUL timer (153) or the NUL timer (152) based on the DCI to suspend triggering of the subsequent RACH procedure through the second UL carrier if the latest RACH procedure was triggered over the first UL carrier. In an embodiment, the RACH triggering engine (110) restarts the SUL timer (153) and the NUL timer (152) in response to receiving another DCI from the network entity. In an embodiment, the RACH triggering engine (110) restarts the RACH timer (151) in response to completion of the RACH procedure in the first UL carrier or the second UL carrier.

The RACH triggering engine (110) detects that a RACH triggering criteria is met. The RACH triggering criteria includes an uplink block error ratio (BLER), a number of radio link control (RLC) non-acknowledgments (NACKs), a signal condition, a transmission power, a power headroom, and a number of random access failures in a UL path. The RACH triggering engine (110) determines whether the one or more timers (150) are expired. In an embodiment, the RACH triggering engine (110) waits till expiry of the one or more timers (150), in response to determining that the one or more timers (150) are not expired. Further, the RACH triggering engine (110) triggers the subsequent RACH procedure through the second UL carrier when the RACH triggering criteria is met after expiry of the one or more timers (150). In another embodiment, the RACH triggering engine (110) triggers the subsequent RACH procedure through the second UL carrier, in response to determining that the one or more timers (150) are expired.

The memory (120) stores instructions to be executed by the processor (130). The memory (120) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (120) may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (120) is non-movable. In some examples, the memory (120) may be configured to store larger amounts of information than its storage space. In certain examples, a non-transitory storage medium may store data that may, over time, change (e.g., in random access memory (RAM) or cache). The memory (120) may be an internal storage unit or it may be an external storage unit of the UE (100), a cloud storage, or any other type of external storage.

The processor (130) is configured to execute instructions stored in the memory (120). The processor (130) may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU) and the like. The processor (130) may include multiple cores to execute the instructions. The communicator (140) is configured for communicating internally between hardware components in the UE (100). Further, the communicator (140) is configured to facilitate the communication between the UE (100) and other devices via one or more networks (e.g. radio technology). The communicator (140) includes an electronic circuit specific to a standard that enables wired or wireless communication.

Although the FIG. 2 shows the hardware components of the UE (100) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the UE (100) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the invention. One or more components may be combined together to perform same or substantially similar function for managing the UL carrier for performing the subsequent RACH procedure.

FIG. 3 is a flow diagram (300) illustrating a method for managing the UL carrier for performing the subsequent RACH procedure in the wireless communication system, according to various embodiments as disclosed herein.

The method allows the RACH triggering engine (110) to perform steps 301-307 of the flow diagram (300). At operation 301, the method includes determining that the RACH procedure is completed with the network entity through the first UL carrier.

At operation 302, the method includes starting the one or more timers (150) to suspend triggering of the subsequent RACH procedure through the second UL carrier.

At operation 303, the method includes detecting that the RACH triggering criteria is met.

At operation 304, the method includes determining whether the one or more timers (150) are expired.

At operation 305, the method includes triggering the subsequent RACH procedure through the second UL carrier, in response to determining that the one or more timers (150) are expired.

At operation 306, the method includes waiting till expiry of the one or more timers (150), in response to determining that the one or more timers (150) are not expired.

At operation 307, the method includes detecting that the RACH triggering criteria is met after expiry of the one or more timers (150). In response to detecting that the RACH triggering criteria is met after expiry of the one or more timers (150), the method further follows the operation 305.

FIG. 4 is a flow diagram (400) illustrating a method for managing the UL carrier for performing the subsequent RACH procedure in the wireless communication system, according to various embodiments as disclosed herein.

The method allows the RACH triggering engine (110) to perform operations 401-410 of the flow diagram (400). At operation 401, the method includes determining that the RACH procedure is completed with the network entity through the first UL carrier.

At operation 402, the method includes starting the RACH timer (151) to suspend triggering of the subsequent RACH procedure through the second UL carrier.

At operation 403, the method includes receiving the DCI from the network entity for allocating the uplink resources.

At operation 404, the method includes allocating the uplink resources based on the DCI.

At operation 405, the method includes starting the SUL timer (153) or the NUL timer (152) based on the DCI to suspend triggering of the subsequent RACH procedure through the second UL carrier if the latest RACH procedure was triggered over the first UL carrier.

At operation 406, the method includes monitoring the RACH triggering criteria.

At operation 407, the method includes determining whether the RACH triggering criteria is met. The method follows the operation 406, in response to determining that the RACH triggering criteria is not met.

At operation 408, the method includes determining whether the RACH timer (151) and the SUL timer (153) or the NUL timer (152) are expired, in response to determining that the RACH triggering criteria is met.

At operation 409, the method includes triggering the subsequent RACH procedure through the second UL carrier, in response to determining that the RACH timer (151), and SUL timer (153) or the NUL timer (152) are expired.

At operation 410, the method includes waiting till expiry of the RACH timer (151), and SUL timer (153) or the NUL timer (152), in response to determining that the RACH timer (151) or the SUL timer (153) or the NUL timer (152) is not expired. In response to detecting that the RACH timer (151), and SUL timer (153) or the NUL timer (152) are expired, the method further follows the operation 406.

The various actions, acts, blocks, steps, or the like in the flow diagrams (300, 400) may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the invention.

The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of various embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.

Claims

A method for managing an uplink (UL) carrier for performing a random-access channel (RACH) procedure in a wireless communication system, comprising:

determining, by a user equipment (UE), that a RACH procedure is completed with a network entity through a first UL carrier;

starting, by the UE, at least one timer to suspend triggering of a subsequent RACH procedure through a second UL carrier;

detecting, by the UE, that a RACH triggering criteria is met;

determining, by the UE, whether the at least one timer is expired; and

in response to determining that the at least one timer is expired, triggering, by the UE, the subsequent RACH procedure through the second UL carrier.
The method as claimed in claim 1, further comprising:

in response to determining that the at least one timer is not expired, waiting, by the UE, till expiry of the at least one timer; and

triggering the subsequent RACH procedure through the second UL carrier when the RACH triggering criteria is met after expiry of the at least one timer.
The method as claimed in claim 1, wherein the step of starting, by the UE, the at least one timer to suspend triggering of the subsequent RACH procedure through the second UL carrier compriing:

starting, by the UE, a RACH timer of the at least one timer to suspend triggering of the subsequent RACH procedure through the second UL carrier;

receiving, by the UE, a downlink control information (DCI) from the network entity;

allocating, by the UE, the uplink resources based on the DCI; and

starting, by the UE, one of a supplementary uplink (SUL) timer and a normal Uplink (NUL) timer of the at least one timer based on the DCI to suspend triggering of the subsequent RACH procedure through the second UL carrier in response that a latest RACH procedure was triggered over the first UL carrier.
The method as claimed in claim 3, further comprising:

restarting, by the UE, the SUL timer and the NUL timer in response to receiving another DCI from the network entity.
The method as claimed in claim 3, further comprising:

restarting, by the UE, the RACH timer in response to completion of the RACH procedure in the first UL carrier or the second UL carrier.
A user equipment (UE) for managing an uplink (UL) carrier for performing a random-access channel (RACH) procedure in a wireless communication system, the UE comprising:

a memory;

at least one timer; and

at least one processor coupled to the memory, configured for:

determining that a RACH procedure is completed with a network entity through a first UL carrier,

starting the at least one timer to suspend triggering of a subsequent RACH procedure through a second UL carrier,

detecting that a RACH triggering criteria is met,

determining whether the at least one timer (150) is expired, and

in response to determining that the at least one timer is expired, triggering, by the UE, the subsequent RACH procedure through the second UL carrier.
The UE (100) as claimed in claim 6, wherein the processor is further configured for:

in response to determining that the at least one timer is not expired, waiting till expiry of the at least one timer, and

triggering the subsequent RACH procedure through the second UL carrier when the RACH triggering criteria is met after expiry of the at least one timer.
The UE as claimed in claim 7, wherein the processor is further configured for:

starting a RACH timer of the at least one timer to suspend triggering of the subsequent RACH procedure through the second UL carrier;

receiving a downlink control information (DCI) from the network entity;

allocating the uplink resources based on the DCI; and

starting one of a supplementary uplink (SUL) timer and a normal uplink (NUL) timer of the at least one timer based on the DCI to suspend triggering of the subsequent RACH procedure through the second UL carrier in response that a latest RACH procedure was triggered over the first UL carrier.
The UE as claimed in claim 8, wherein the processor is further configured for:

restarting the SUL timer and the NUL timer in response to receiving another DCI from the network entity.
The UE as claimed in claim 8, wherein the processor is further configured for:

restarting the RACH timer in response to completion of the RACH procedure in the first UL carrier or the second UL carrier.
A non-transitory, computer-readable storage medium storing one or more programs, the one or more programs containing instructions, which when executed by a processor, cause a user equipment (UE) to: determine that a RACH procedure is completed with a network entity through a first UL carrier;

start at least one timer to suspend triggering of a subsequent RACH procedure through a second UL carrier;

detect that a RACH triggering criteria is met;

determine whether the at least one timer is expired; and

in response to determining that the at least one timer is expired, trigger the subsequent RACH procedure through the second UL carrier.