WO2025096380A1

WO2025096380A1 - Pdcch order triggering prach transmission for multi-trp operation

Info

Publication number: WO2025096380A1
Application number: PCT/US2024/053330
Authority: WO
Inventors: Hong He; Chunxuan Ye; Dawei Zhang; Haitong Sun; Oghenekome Oteri; Seyed Ali Akbar Fakoorian; Wei Zeng
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2023-10-31
Filing date: 2024-10-29
Publication date: 2025-05-08
Anticipated expiration: 2026-04-30

Abstract

An apparatus configured to process, based on signals received from a base station, a Physical Downlink Control Channel (PDCCH)-order Downlink Control Information (DCI) indicating a contention free random access (CFRA) procedure is to be performed, wherein the apparatus is configured with two timing advances (TAs) with multi-DCI for multi-transmission and reception points (mTRPs) without cell switch (2TAs_mTRP) feature and a Layer 1/Layer 2 triggered mobility (2TAs_LTM) feature and determine, based on the PDCCH-order DCI, whether the CFRA procedure for the 2TAs_mTRP feature or the 2TAs_LTM feature is to be performed.

Description

PDCCH ORDER TRIGGERING PRACH TRANSMISSION FOR MULTI -TRP OPERATION

Inventors: Hong He, Chunxuan Ye, Dawei Zhang, Haitong Sun, Oghenekome Oteri, Seyed Ali Akbar Fakoorian and Wei Zeng

Priority/ Incorporation By Reference

[0001] This application claims priority to US Provisional Application Serial No. 63/594, 599 filed on October 31, 2023, entitled "PDCCH Order Triggering PRACH Transmission for multi- TRP Operation, " the entirety of which is incorporated by reference herein.

Background

[0002] A user equipment (UE) may communicate with multiple transmission and reception points (TRPs) of a network. There may be various manners for a UE to communicate with the multiple TRPs. In one example, the UE may operate in multi-TRP (mTRP) mode and simultaneously communicate with two or more TRPs. In another example, a UE may communicate with a first TRP and then perform a cell-switch procedure to communicate with a second TRP. Some UEs may be configured to operate in both these modes.

[0003] Both of these example manners of UE communicating with TRPs may include a random access procedure where a TRP transmits a Physical Downlink Control Channel (PDCCH) -order Downlink Control Information (DCI) message to the UE . However, the UE may have to react to this PDCCH-order DCI in a first manner when operating in mTRP mode and in a second different manner when operating in a cell-switch scenario. Thus, when a UE is configured to operate in both of the example modes, the UE may not be able to understand in which manner the UE should react to the PDCCH-order DCI .

Summary

[0004] Some example embodiments are related to an apparatus having processing circuitry configured to process, based on signals received from a base station, a Physical Downlink Control Channel ( PDCCH) -order Downlink Control Information (DCI) indicating a contention free random access (CERA) procedure is to be performed, wherein the apparatus is configured with two timing advances (TAs) with multi-DCI for multi-transmission and reception points (mTRPs) without cell switch (2TAs_mTRP) feature and a Layer 1/Layer 2 triggered mobility (2TAs LTM) feature and determine, based on the PDCCH-order DCI, whether the CFRA procedure for the 2TAs_mTRP feature or the 2TAs_LTM feature is to be performed.

[0005] Other example embodiments are related to an apparatus having processing circuitry configured to generate, for transmission to a user equipment (UE) , a Physical Downlink Control Channel ( PDCCH) -order Downlink Control Information (DCI) indicating a contention free random access (CFRA) procedure is to be performed by the UE, wherein the UE is configured with two timing advances (TAs) with multi-DCI for multi-transmission and reception points (mTRPs) without cell switch (2TAs mTRP) feature and a Layer 1/Layer 2 triggered mobility (2TAs LTM) feature.

[0006] Still further example embodiments are related to a user equipment (UE) having a transceiver configured to communicate with a base station and a processor communicatively coupled to the transceiver and configured to process, based on signals received from the base station, a Physical Downlink Control Channel ( PDCCH) -order Downlink Control Information (DCI) indicating a contention free random access (CFRA) procedure is to be performed, wherein the apparatus is configured with two timing advances (TAs) with multi-DCI for multi-transmission and reception points (mTRPs) without cell switch (2TAs_mTRP) feature and a Layer 1/Layer 2 triggered mobility (2TAs LTM) feature and determine, based on the PDCCH-order DCI, whether the CFRA procedure for the 2TAs_mTRP feature or the 2TAs_LTM feature is to be performed.

[0007] Additional example embodiments are related to an having processing circuitry configured to process, based on signals received from a base station, a Physical Downlink Control Channel ( PDCCH) -order Downlink Control Information (DCI) indicating a contention free random access (CFRA) procedure for a two timing advances (TAs) with multi-DCI for multitransmission and reception points (mTRPs) without cell switch (2TAs mTRP) feature is to be performed, wherein a first TRP of the mTRPs is associated with a first timing advance group (TAG) and a second TRP of the mTRPs is associated with a second TAG, process, based on signals received from a TRP that transmitted the PDCCH-order DCI, a random access response (RAR) message of the CFRA procedure, determine whether a closed loop power control (CLPC) index associated with the first TAG or the second TAG is to be reset based on receiving the RAR message and reset the determined CLPC of the associated first TAG or second TAG.

Brief Description of the Drawings

[0008] Fig. 1 shows an example network arrangement according to various example embodiments. [0009] Fig. 2 shows an example UE according to various example embodiments.

[0010] Fig. 3 shows an example base station according to various example embodiments.

[0011] Fig. 4 shows an example arrangement comprising a UE communicating with multiple TRPs when operating in mTRP mode according to various example embodiments.

[0012] Fig. 5 shows an example arrangement comprising a UE communicating with multiple TRPs when operating in a Layer 1/Layer 2 triggered mobility (LTM) mode according to various example embodiments.

[0013] Fig. 6 shows an example PDCCH-order DCI comprising a 1-bit flag indicator field to indicate whether the PDCCH-order is for the mTRP mode or LTM mode according to various example embodiments .

[0014] Fig. 7 shows an example slot order comprising a pattern to indicate whether the PDCCH-order is for the mTRP mode or LTM mode according to various example embodiments.

[0015] Fig. 8 shows an example CORESET ID order comprising a pattern to indicate whether the PDCCH-order is for the mTRP mode or LTM mode according to various example embodiments.

[0016] Fig. 9 shows an example PDCCH-order DCI comprising a 3-bit cell indicator field and a 1-bit Physical Cell ID (PCI) indicator field to indicate whether the PDCCH-order is for the mTRP mode or LTM mode according to various example embodiments.

[0017] Fig. 10 shows an example table providing information related to the 3-bit cell indicator field and the 1-bit PCI indicator field to indicate whether the PDCCH-order is for the mTRP mode or LTM mode according to various example embodiments.

[0018] Fig. 11 shows an example arrangement comprising a UE communicating with multiple TRPs when operating in mTRP mode or LTM mode according to various example embodiments.

[0019] Fig. 12 shows an example PDCCH-order DCI comprising a 1-bit closed loop power control (CLPC) indicator field to indicate which of two CLPC indices is to be reset according to various example embodiments.

[0020] Fig. 13 shows an example table for associating a Synchronization Signal Block (SSB) /PRACH pair or an SSB index with a CLPC index according to various example embodiments.

Detailed Description

[0021] The example embodiments may be further understood with reference to the following description and the related appended drawings, wherein like elements are provided with the same reference numerals. The example embodiments relate to a user equipment (UE) being triggered to perform a contention free access (CFRA) procedure in a multiple transmission and reception point (TRP) scenario. In a first aspect of the example embodiments, the triggering message includes information allowing the UE to distinguish between different multiple TRP scenarios to perform the correct CFRA procedure. In a second aspect, information is provided to the UE for the UE to reset a correct closed loop power control (CLPC) during a CFRA procedure for mTRP operations .

[0022] The example embodiments are described with regard to a user equipment (UE) . However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and/or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any electronic component.

[0023] The example embodiments are also described with reference to a 5G New Radio (NR) network. The example embodiments may also be implemented in other types of networks, including but not limited to legacy cellular networks (e.g., Long Term Evolution (LTE) ) , future evolutions of the cellular protocol (e.g., 5G advanced, 6G, etc.) , or any other type of network .

[0024] The example embodiments are also described with regard to a base station (e.g., next generation node B (gNB) ) that is configured with multiple transmission and reception points (TRPs) . Throughout this description, a TRP generally refers to a set of components configured to transmit and/or receive a beam. In some embodiments, multiple TRPs may be deployed locally at the gNB. For example, the gNB may include multiple antenna arrays/panels that are each configured to generate a different beam. In other example embodiments, multiple TRPs may be deployed at various different locations and connected to the gNB via a backhaul connection. For example, multiple small cells may be deployed at different locations and connected to the gNB. However, these examples are merely provided for illustrative purposes. TRPs are configured to be adaptable to a wide variety of different conditions and deployment scenarios. Thus, any reference to a TRP being a particular network component or multiple TRPs being deployed in a particular arrangement is merely provided for illustrative purposes. The TRPs described herein may represent any type of network component configured to transmit and/or receive a beam.

[0025] The example embodiments are described with reference to two different scenarios of a UE communicating with multiple TRPs. In a first scenario, the UE may be operating in mTRP mode having a feature related to two timing advances (TAs) with multi-DCI (mDCI) for mTRP (two TAs with mDCI mTRP) without cell switch. This means that the UE is supplied a TA value for each TRP the UE is communicating with in mTRP mode. Throughout this description, this scenario will be referred to as "2TAs mTRP".

[0026] In a second scenario, the UE may be operating in a Layer 1/Layer 2 triggered mobility (LTM) mode where the UE may have a feature to perform a cell-switch from a first TRP to a second TRP based on the Layer 1 and/or Layer 2 measurements performed by the UE . Again, the UE may use two different TAs to communicate with the first TRP and second TRP. Throughout this description, this scenario will be referred to as "2TAs LTM". Each of these scenarios will be described in greater detail below. The UE may report its support of the 2TAs_LTM feature and/or the 2TAs mTRP feature in a UE capability report. [0027] In some example embodiments, the UE is triggered by the network to perform a CERA procedure for the purposes of communicating with the multiple TRPs . The triggering message may be a Physical Downlink Control Channel ( PDCCH) -order Downlink Control Information (DCI) . The CFRA procedure may be for the 2TAs LTM or 2TAs mTRP scenario. The UE may perform different operations for the CFRA procedure depending on whether the CFRA procedure is for the 2TAs_LTM or 2TAs_mTRP scenario. The example embodiments provide manners for the UE to distinguish between a triggering message for the 2TAs LTM scenario or the 2TAs mTRP scenario .

[0028] In other example embodiments, a CLPC may be reset when a UE receives a random access response (RAR) message during a CFRA procedure. When the RAR message is received during a CFRA procedure related to mDCI mTRP, the UE may not understand to which CLPC of a timing advance group (TAG) of the mTRP the reset is to be applied. The example embodiments also include providing information to the UE for the UE to understand the CLPC that is to be reset. These and other enhancements related to performing CFRA procedures for multiple TRP scenarios are described in greater detail below.

[0029] Fig. 1 shows an example network arrangement 100 according to various example embodiments. The example network arrangement 100 includes a UE 110. The UE 110 may be any type of electronic component that is configured to communicate via a network, e.g. , mobile phones, tablet computers, desktop computers, smartphones, phablets, embedded devices, wearables, Internet of Things (loT) devices (including connected vehicles) , etc. An actual network arrangement may include any number of UEs being used by any number of users. Thus, the example of one UE 110 is merely provided for illustrative purposes.

[0030] The UE 110 may be configured to communicate with one or more networks. In the example of the network configuration 100, the network with which the UE 110 may wirelessly communicate is a 5G NR radio access network (RAN) 120. The UE 110 may also communicate with other types of networks (e.g., 5G cloud RAN, a next generation RAN (NG-RAN) , a legacy cellular network, etc. ) and the UE 110 may also communicate with networks over a wired connection. With regard to the example embodiments, the UE 110 may establish a connection with the 5G NR RAN 120. Therefore, the UE 110 may have a 5G NR chipset to communicate with the NR RAN 120.

[0031] The 5G NR RAN 120 may be portions of a cellular network that may be deployed by a network carrier (e.g., Verizon, AT&T, T-Mobile, etc. ) . The RAN 120 may include cells or base stations that are configured to send and receive traffic from UEs that are equipped with the appropriate cellular chip set. In this example, the 5G NR RAN 120 includes the gNB 120A. However, reference to a gNB is merely provided for illustrative purposes, any appropriate base station or cell may be deployed (e.g., Node Bs, eNodeBs, HeNBs, eNBs, gNBs, gNodeBs, macrocells, microcells, small cells, femtocells, etc. ) .

[0032] Any association procedure may be performed for the UE 110 to connect to the 5G NR RAN 120. For example, as discussed above, the 5G NR RAN 120 may be associated with a particular network carrier where the UE 110 and/or the user thereof has a contract and credential information (e.g., stored on a SIM card) . Upon detecting the presence of the 5G NR RAN 120, the UE 110 may transmit the corresponding credential information to associate with the 5G NR RAN 120. More specifically, the UE 110 may associate with a specific cell (e.g., gNB 120A) .

[0033] The network arrangement 100 also includes a cellular core network 130, the Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160. The cellular core network 130 manages the traffic that flows between the cellular network and the Internet 140. The IMS 150 may be generally described as an architecture for delivering multimedia services to the UE 110 using the IP protocol. The IMS 150 may communicate with the cellular core network 130 and the Internet 140 to provide the multimedia services to the UE 110. The network services backbone 160 is in communication either directly or indirectly with the Internet 140 and the cellular core network 130. The network services backbone 160 may be generally described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a suite of services that may be used to extend the functionalities of the UE 110 in communication with the various networks.

[0034] Fig. 2 shows an example UE 110 according to various example embodiments. The UE 110 will be described with regard to the network arrangement 100 of Fig. 1. The UE 110 may represent any electronic device and may include a processor 205, a memory arrangement 210, a display device 215, an input/output (I/O) device 220, a transceiver 225, and other components 230. The other components 230 may include, for example, an audio input device, an audio output device, a battery that provides a limited power supply, a data acquisition device, ports to electrically connect the UE 110 to other electronic devices, sensors to detect conditions of the UE 110, one or more antenna panels, etc.

[0035] The processor 205 may be configured to execute a plurality of engines for the UE 110. For example, the engines may include a 2TAs engine 235 and a CLPC engine 240 for performing operations related to CFRA procedures in a multiple TRP scenario. The operations may include, but are not limited to, receiving a triggering message for a CFRA procedure, determining a scenario to which the CFRA procedure applies, performing a correct CFRA procedure based on information provided in the triggering message, determining whether a CLPC should be reset and applying the CLPC reset to a correct TAG. These and other example operations are described in further detail below.

[0036] The above referenced engines being application ( s ) (e.g., a program) executed by the processor 205 is only example. The functionality associated with the engines may also be represented as a separate incorporated component of the UE 110 or may be a modular component coupled to the UE 110, e.g. , an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. The engines may also be embodied as one application or separate applications. In addition, in some UEs, the functionality described for the processor 205 is split among two or more processors such as a baseband processor and an applications processor. The example embodiments may be implemented in any of these or other configurations of a UE .

[0037] The memory arrangement 210 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 may be a hardware component configured to show data to a user while the I/O device 220 may be a hardware component that enables the user to enter inputs. The display device 215 and the I/O device 220 may be separate components or integrated together such as a touchscreen.

[0038] The transceiver 225 may be a hardware component configured to establish a connection with the 5G-NR RAN 120. Accordingly, the transceiver 225 may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies) . The transceiver 225 includes circuitry configured to transmit and/or receive signals (e.g. , control signals, data signals) . Such signals may be encoded with information implementing any one of the methods described herein. The processor 205 may be operably coupled to the transceiver 225 and configured to receive from and/or transmit signals to the transceiver 225. The processor 205 may be configured to encode, decode and/or process signals (e.g. , signaling from a base station of a network) for implementing any one of the methods described herein.

[0039] Fig. 3 shows an example base station 300 according to various example embodiments. The base station 300 may represent the gNB 120A or any other access node through which the UE 110 may establish a connection and manage network operations. [0040] The base station 300 may include a processor 305, a memory arrangement 310, an input/output (I/O) device 315, a transceiver 320, other components 325, and one or more transmission and reception points (TRPs) 330. The other components 325 may include, for example, an audio input device, an audio output device, a battery, a data acquisition device, ports to electrically connect the base station 300 to other electronic devices and/or power sources, etc.

[0041] The processor 305 may be configured to execute a plurality of engines for the base station 300. For example, the engines may include a 2TAs configuration engine 335 and a CLPC engine 340 for performing operations related to triggering a UE to perform a CFRA procedure in a multiple TRP scenario. The operations may include, but are not limited to, configuring a triggering message to initiate the CFRA procedure by the UE that includes information for the UE to distinguish between different multiple TRP scenarios for which the CFRA procedure is to be performed, performing the CFRA procedure with the UE and indicating to the UE a CLPC that is to be reset during the CFRA procedure. These and other example operations are described in further detail below.

[0042] The above referenced engines being application ( s ) (e.g., a program) executed by the processor 305 is only example. The functionality associated with the engines may also be represented as a separate incorporated component of the base station 300 or may be a modular component coupled to the base station 300, e.g. , an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. The engines may also be embodied as one application or separate applications. In addition, in some base stations, the functionality described for the processor 305 is split among two or more processors such as a baseband processor and an applications processor. The example embodiments may be implemented in any of these or other configurations of a base station.

[0043] The memory arrangement 310 may be a hardware component configured to store data related to operations performed by the base station 300. The I/O device 315 may be a hardware component or ports that enable a user to interact with the base station 300.

[0044] The transceiver 320 may be a hardware component configured to exchange data with the UE 110 and any other UE in the network arrangement 100. The transceiver 320 may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies) . Therefore, the transceiver 320 may include one or more components (e.g., radios) to enable the data exchange with the various networks and UEs. The transceiver 320 includes circuitry configured to transmit and/or receive signals (e.g., control signals, data signals) . Such signals may be encoded with information implementing any one of the methods described herein. The processor 305 may be operably coupled to the transceiver 320 and configured to receive from and/or transmit signals to the transceiver 320. The processor 305 may be configured to encode, decode and/or process signals (e.g., signaling from a UE) for implementing any one of the methods described herein. [0045] Fig. 4 shows an example arrangement 400 comprising a UE 110 communicating with multiple TRPs 410 and 420 when operating in mTRP mode according to various example embodiments. In the example arrangement 400 there are two TRPs 410 and 420 communicating with the UE 110. When the UE 110 operates in mTRP mode, the UE 110 may also include a feature related to two timing advances (TAs) with multi-DCI (mDCI) for mTRP (two TAs with mDCI mTRP) without cell switch, e.g. , the 2TAs_mTRP scenario or use case. This means that the UE 110 is supplied a TA value for the TRP 410 and a second different TA value for the TRP 420, which are used to communicate with the TRPs 410 and 420 when operating in mTRP mode.

[0046] As shown in Fig. 4, when operating in two TAs with mDCI mTRP mode, the UE 110 may perform a contention free access procedure (CFRA) with the TRPs 410 and 420 to initiate communication with the TRP 420. This CFRA may be triggered by the UE 110 receiving a Physical Downlink Control Channel

( PDCCH) -order Downlink Control Information (DCI) message (step 0) from the TRP 410. In response to receiving the PDCCH-order DCI, the UE 110 may send a Physical Random Access Channel (PRACH) message to the TRP 420 (step 1) .

[0047] As part of the CERA procedure, the UE 110 may also monitor for Type-1 Common Search Space (CSS) signals for random access response (RAR) from the TRP 410 (step 2) . The RAR is monitored because the RAR message includes the TA values for the TRP 420. Thus, in two TAs with mDCI mTRP operation, the UE 110 receives the TA value for the second TRP, e.g. , TRP 420, during the CERA procedure. [0048] Fig. 5 shows an example arrangement 500 comprising a UE 110 communicating with multiple TRPs 510 and 520 when operating in a Layer 1/Layer 2 triggered mobility (LTM) mode according to various example embodiments. Similar to the example arrangement 400 of Fig. 4, in the example arrangement 500 there are two TRPs 510 and 520 communicating with the UE 110. In LTM mode, the UE 110 perform a cell-switch from the TRP 510 to the TRP 520 based on the Layer 1 and/or Layer 2 measurements performed by the UE 110 on the signals transmitted by the TRPs 510 and 520. When the UE 110 operates in LTM mode, the UE 110 may also include the feature of using two TAs for communicating with the respective TRPs 510 and 520, e.g. , the 2TAs_LTM scenario or use case.

[0049] As shown in Fig. 5, when operating in LTM mode, the UE 110 may perform a CFRA procedure with the TRPs 510 and 520 to initiate the cell-switch from the TRP 510 to the TRP 520. This CFRA procedure may be triggered by the UE 110 receiving a PDCCH- order DCI message (step 0) from the TRP 510. In response to receiving the PDCCH-order DCI, the UE 110 may send a PRACH message to the TRP 520 (step 1) . It can be seen from the Figs. 4 and 5 and the corresponding description that the CFRA steps 0 and 1 are the same for the UE 110 when operating in two TAs with mDCI mTRP mode as when operating in LTM mode.

[0050] The difference between operating modes may occur after step 1 of the CFRA procedure. In LTM mode, the UE 110 does not need to monitor for the RAR message from the TRP 510 because the TA for the TRP 520 is obtained at a later time, e.g. , from a cell-switch command Medium Access Control Control Element (MAC- CE) . As stated above, the UE 110 may be capable of operating in both the two TAs with mDCI mTRP mode and the LTM mode. When this occurs and the UE 110 performs the CERA procedure with the TRPs, the UE 110 may not understand whether the UE 110 should monitor for the RAR message because the UE 110 does not know if the CERA procedure is being performed for the 2TAs mTRP scenario or use case or the 2TAs_LTM scenario or use case.

[0051] Thus, throughout this description, when referring to the UE 110 performing a CERA procedure for the 2TAs_mTRP feature, this may include the UE 110 monitoring for the RAR message. Similarly, when referring to the UE 110 performing a CFRA procedure for the 2TAs_LTM feature, this may include the UE 110 omitting to monitor for the RAR message.

[0052] In a first aspect of the example embodiments, various manners of indicating the use case of a PDCCH-ordered CFRA procedure when the UE is configured with both two TAs with mDCI mTRP mode without cell switch, e.g. , the 2TAs_mTRP feature, and LTM mode, e.g., the 2TAs LTM feature.

[0053] In some example embodiments of the first aspect, a 1- bit flag indicator field may be included in the PDCCH-order DCI to indicate the use case for the PDCCH-order, e.g., '2TAs mTRP' or '2TAs_LTM' . Fig. 6 shows an example PDCCH-order DCI 600 comprising a 1-bit flag indicator field to indicate whether the PDCCH-order is for the mTRP mode or LTM mode according to various example embodiments. The PDCCH-order DCI 600 includes the currently used fields 610, reserved fields 630 and the CRC 640. In addition, a 1-bit flag indicator field 620 is introduced by repurposing a reserved bit. [0054] In one example, when the 1-bit flag indicator field

620 is set to a value 'O' , this indicates the triggered PRACH is for '2TAs_mTRP' and therefore the UE 110 may monitor the Type-1 CSS for RAR reception to receive the TA for the second TRP . In another example, when the 1-bit flag indicator field 620 is set to a value '1' , this indicates the triggered PRACH is for

'2TAs LTM' and therefore the UE 110 does not need to monitor the Type-1 CSS for RAR reception.

[0055] In other example embodiments of the first aspect, a slot index may be used to indicate the use case for the PDCCH- order, e.g. , '2TAs_mTRP' or '2TAs_LTM' . Fig. 7 shows an example slot order 700 comprising a pattern to indicate whether the PDCCH-order is for the mTRP mode or LTM mode according to various example embodiments. The slot order 700 shows a series of slots having slot indices 0-9. The slot order 700 may be used to indicate the use case for the PDCCH-ordered CFRA based on the slot index where the PDCCH-order DCI is detected by the UE 110. For example, if the PDCCH-order DCI is detected in an even slot (e.g., slot index 0, 2, 4, 6, 8) , the UE 110 may determine the target use case is '2TAs_LTM' as shown in Fig. 7. On the other hand, if the PDCCH-order DCI is detected in an odd slot (e.g., slot index 1, 3, 5, 7, 9) , the UE 110 may determine the target use case is '2TAs_mTRP' as shown in Fig. 7. The opposite indexing may also be used, e.g., even slots indicate '2TAs mTRP' and odd slots indicate '2TAs LTM' .

[0056] In further example embodiments of the first aspect, a Control Resource Set Identification (CORESET ID) or search space ID may be used to indicate the use case for the PDCCH-order, e.g., '2TAs mTRP' or '2TAs LTM' . Fig. 8 shows an example CORESET ID order 800 comprising a pattern to indicate whether the PDCCH- order is for the mTRP mode or LTM mode according to various example embodiments. Fig. 8 shows a series of CORSETs with CORESET IDs, e.g. , CORESET 1-4. The CORESET IDs may be used to indicate the use case for the PDCCH-ordered CFRA. For example, if the PDCCH-order DCI is detected in a CORESET (or search space ID) with an odd CORESET ID (e.g., CORESET 1, CORESET 3, etc. ) , the UE 110 may determine the target use case is '2TAs mTRP' as shown in Fig. 8. On the other hand, if the PDCCH-order DCI is detected in a CORESET (or search space ID) with an even CORESET ID (e.g. , CORESET 2, CORESET 4, etc. ) , the UE 110 may determine the target use case is '2TAs_LTM' as shown in Fig. 8. The opposite correlation may also be used, e.g., even CORESET IDs indicate '2TAs mTRP' and odd CORESET IDs indicate '2TAs LTM' .

[0057] In these example embodiments, a first option may be that the rule, e.g. , correlating the CORESET ID to the use case, may be defined in standards, e.g., 3GPP Technical Specifications. In a second option, radio resource control (RRC) signaling may be used to configure the target use case for each CORESET or each search space.

[0058] In additional example embodiments of the first aspect, the PDCCH-order DCI may include two separate fields to indicate the use case for the PDCCH-order, e.g., '2TAs mTRP' or '2TAs_LTM' . Fig. 9 shows an example PDCCH-order DCI 900 comprising a 3-bit cell indicator field and a 1-bit Physical Cell ID (PCI) indicator field to indicate whether the PDCCH- order is for the mTRP mode or LTM mode according to various example embodiments. [0059] The PDCCH-order DCI 900 includes the currently used fields 910, reserved fields 940 and the CRC 950. In addition, a 3-bit cell indicator field 920 and a 1-bit PCI indicator field 940 may be introduced by repurposing reserved bits. The use of the 3-bit cell indicator field 920 and the 1-bit PCI indicator field 940 to indicate the use case for the PDCCH-order will be described with reference to Figs. 10 and 11.

[0060] Fig. 10 shows an example table 1000 providing information related to the 3-bit cell indicator field 920 and the 1-bit PCI indicator field 930 to indicate whether the PDCCH- order is for the mTRP mode or LTM mode according to various example embodiments.

[0061] Fig. 11 shows an example arrangement 1100 comprising a UE 110 communicating with multiple TRPs when operating in mTRP mode or LTM mode according to various example embodiments. In the example of Fig. 11, the UE 110 is connected to the serving TRP 1110. There are six (6) candidate TRPs configured for LTM operations, e.g., for cell-switch for the UE . These six (6) candidate TRPs are TRPs 1120-1170. Three (3) of the candidate TRPs 1120-1140 are configured with an EarlyUlSyncConf ig information element (IE) . The IE EarlyUlSync-Conf ig IE is used to configure random access resources for the early uplink (UL) synchronization procedure. This essentially means that when in the LTM mode, the UE 110 will attempt to cell-switch to these candidate TRPs. In addition, the candidate TRP is configured as an additional PCI in the two TAs mTRP configuration.

[0062] The table 1000 is configured for this scenario. For example, the network may configure the UE 110 with this table for using the 3-bit cell indicator field 920 and the 1-bit PCI indicator field 930 for this scenario. This network configuration may be sent to the UE via any signaling method, e.g., RRC signaling, MAC-CE signaling, etc. When the UE 110 is in other multiple TRP scenarios, the network may configure a table that is similar table 1000 for the other multiple TRP scenarios .

[0063] The use of the 3-bit cell indicator field 920 and the 1-bit PCI indicator field 930 will now be described. When the UE 110 receives the PDCCH-order DCI 900, the UE 110 may first check the value of the 3-bit cell indicator field 920. If the 3-bit cell indicator field 920 is set to '000' , the UE 110 determines the PDCCH ordered CERA procedure is triggered for the '2TAs mTRP' use case. This is shown in table 1000 as Index 0 or 1 with the cell indicator field 920 value of '000' .

[0064] When the cell indicator field 920 indicates the '2TAs_mTRP' use case, the UE 110 may then check the 1-bit PCI indicator field 930. When the PCI indicator field 930 has a value of 'O' , the UE 110 determines the PDCCH order is triggered for the serving TRP, e.g., TRP 1110. This is shown as Index 0 in the table 1000, e.g., cell indicator field 920 value of '000' and PCI indicator field 930 value of '0' . When the PCI indicator field 930 has a value of '1' , the UE 110 determines the PDCCH order is triggered for a non-serving TRP, e.g., TRP 1130. This is shown as Index 1 in the table 1000, e.g., cell indicator field 920 value of '000' and PCI indicator field 930 value of '1' .

[0065] When the cell indicator field 920 is set to other values except '000' , the UE 110 determines the PDCCH ordered CFRA procedure is triggered for the '2TAs LTM' use case. As shown in table 1000, the 3-bit cell indicator field 920 is mapped to one of the candidate TRPs configured with the higher layer parameter EarlyUlSyncConf ig, e.g., cell indicator field 920 value of '001' for the candidate TRP 1120 (table 1000 Index 2) , cell indicator field 920 value of '010' for the candidate TRP 1130 (table 1000 Index 3) or cell indicator field 920 value of 'Oil' for the candidate TRP 1140 (table 1000 Index 4) . Thus, there is a 1: 1 mapping between the codepoints of the cell indicator field 920 and the candidate TRPs configured with the higher layer parameter EarlyUlSyncConf ig .

[0066] In the example of the '2TAs LTM' use case, e.g. , the cell indicator field 920 is set to any value except '000' , the UE 110 may ignore the PCI indicator field 930 because this field is only associated with the '2TAs mTRP' use case. This is shown in table 1000 as the PCI indicator field 930 being set to any value because the UE 110 will ignore this field for the '2TAs LTM' use case.

[0067] In a second aspect of the example embodiments, a manner of determining whether a closed loop power control (CLPC) is to be reset during the CFRA procedure for the 2TAs mTRP scenario is described.

[0068] Currently, a UE resets the CLPC adjustment (1=0) when the UE receives a RAR during the PRACH procedure. However, in the case of the 2TAs mTRP scenario, there may be two timing advance groups (TAGs) where a cross-TRP CFRA operation is supported to obtain the TA for the second TRP as was described above with reference to Fig. 4. Thus, when two CLPC (e.g. , 1=0, 1) are configured for mDCI mTRP, resetting the CPLC for both TAGs may result in unnecessary power ramping and inappropriate transmission power towards one or more of the TRPs . The second aspect of the example embodiments addresses this issue.

[0069] In a first example of the second aspect, a 1-bit CLPC indicator field may be included in the PDCCH-order DCI to indicate which of the two CLPC indices (e.g., 1 = 0, 1) is to be reset after receiving the associated RAR. Fig. 12 shows an example PDCCH-order DCI 1200 comprising a 1-bit closed loop power control (CLPC) indicator field to indicate which of two CLPC indices is to be reset according to various example embodiments .

[0070] The PDCCH-order DCI 1200 includes the currently used fields 1210, reserved fields 1230 and the CRC 1240. In addition, a 1-bit CLPC indicator field 1220 is introduced by repurposing a reserved bit. This CLPC indicator field 1220 may be used to indicate which of the two CLPC indices (e.g., 1 = 0, 1) is to be reset after receiving the associated RAR. For example, when the CLPC indicator field 1220 is set to a value 'O' , this may indicate resetting the CLPC index 1=0, whereas when the CLPC indicator field 1220 is set to a value

this may indicate resetting the CLPC index 1=1. In this manner, the UE 110 will understand which of the CLPC indices is to be reset and avoids resetting a CLPC that does not need to be reset.

[0071] In a second example of the second aspect, dedicated RRC signaling is used to associate each pair of <SSB #X, PRACH #Y> or each SSB index with a CLPC index (e.g. , 1 = 0, 1) . Fig. 13 shows an example table 1300 for associating a Synchronization Signal Block (SSB) /PRACH pair or an SSB index with a CLPC index according to various example embodiments. As described above, the UE 110 may receive the table 1300 via RRC signaling from the network .

[0072] As shown in table 1300, the UE 110 may reset the corresponding CLPC (e.g. , 1 = 0, 1) based on the pair <SSB #X, PRACH #Y> or the SSB index indicated in the PDCCH-order DCI . For example, referring to the table 1300, if Index 2 is indicated by PDCCH-order DCI (e.g., <SSB #2, PRACH #1> or SSB#2, the UE 110 may reset the CLPC index 1 = 1 after receiving the RAR.

[0073] In a third example of the second aspect, a 1-bit CLPC indicator field may be included in the DCI that schedules the RAR Physical Downlink Shared Channel (PDSCH) to indicate which of the two CLPC indices (e.g. , 1 = 0, 1) is to be reset after receiving the associated RAR. This 1-bit CLPC indicator field of the third example may be used by the UE 110 in the same manner as the 1-bit CLPC indicator field described above for the first example of the second aspect.

[0074] In a fourth example of the second aspect, the resetting of the CLPC may be based on a value of the TAG-ID field in the Rel-18 RAR. The RAR MAC Protocol Data Unit (PDU) may include a TAG-ID field. If a value 'O' is indicated in the TAG-ID field of the RAR MAC PDU, the UE may reset the CLPC for the TAG 1 = 0. If a value '1' is indicated in the TAG-ID field of the RAR MAC PDU, the UE may reset the CLPC for the TAG 1 = 1.

[0075] In a fifth example of the second aspect, for intercell mDCI mTRP, the resetting of the CLPC may be based on a fixed rule to determine which CLPC index (e.g., 1 = 0,1) is reset after RAR reception. For example, the rule may be defined as the UE 110 resets the CLPC (1 = 1) if the additional PCI is indicated (e.g., the TRP 1130 of Fig. 11) and the UE resets the CLPC (1 = 0) if the serving cell PCI is indicated, (e.g., the TRP 1110 of Fig. 11) .

Examples

[0076] In a first example, a method, comprising decoding, based on signals received from a base station, a Physical Downlink Control Channel (PDCCH) -order Downlink Control Information (DCI) indicating the UE performs a contention free random access (CFRA) procedure, wherein a user equipment (UE) is configured with a two timing advances (TAs) with multi-DCI for multi-transmission and reception points (mTRPs) without cell switch (2TAs mTRP) feature and a Layer 1/Layer 2 triggered mobility (2TAs LTM) feature based on capabilities reported by the UE, determining whether the UE performs the CFRA procedure for the 2TAs mTRP feature or the 2TAs LTM feature based on the PDCCH-order DCI and performing the CFRA procedure for the determined 2TAs_mTRP feature or the 2TAs_LTM feature.

[0077] In a second example, the method of the first example, wherein the PDCCH-order DCI comprises a cell indicator field and a Physical Cell Identification (PCI) indicator field, wherein the processing circuitry determines whether the UE performs the CFRA procedure for the 2TAs_mTRP feature or the 2TAs_LTM feature based on the cell indicator field.

[0078] In a third example, the method of the second example, wherein the cell indicator field comprises a 3-bit field, wherein a first value of the cell indicator field indicates the UE performs the CFRA procedure for the 2TAs mTRP feature .

[ 0079] In a fourth example , the method of the third example , wherein the PCI indicator field comprises a 1-bit field, wherein a first value of the PCI indicator field combined with the first value of the cell indicator field in a same PDCCH-order DCI indicates the UE performs the CFRA procedure for a transmission and reception point ( TRP ) of a serving cell and wherein a second value of the PCI indicator field combined with the first value of the cell indicator field in a same PDCCH-order DCI indicates the UE performs the CFRA procedure for a TRP of a non-serving cell .

[ 0080 ] In a fi fth example , the method of the third example, wherein any value of the cell indicator field that is not the first value indicates the UE performs the CFRA procedure for the 2TAs LTM feature .

[ 0081 ] In a sixth example , the method of the fifth example, wherein each of the values of the cell indicator field that is not the first value indicates a corresponding candidate cell with which the UE performs the CFRA procedure for the 2TAs LTM feature .

[ 0082 ] In a seventh example , the method of the sixth example , wherein each of the values of the cell indicator field that is not the first value comprises a one-to-one mapping with the corresponding candidate cell , wherein the one-to-one mapping is based on candidate cells configured with Physical Random Access Channel ( PRACH) resources for early synchroni zation in an order of increasing candidate cell identification (ID) of the candidate cells.

[0083] In an eighth example, the method of the first example, wherein, when performing the CFRA procedure for the determined 2TAs_mTRP feature, the method further comprises monitoring a Type-1 Common Search Space (CSS) for receiving a random access response (RAR) from a transmission and reception point (TRP) that transmitted the PDCCH-order DCI .

[0084] In a ninth example, the method of the first example, wherein, when performing the CFRA procedure for the determined 2TAs LTM feature, a Type-1 Common Search Space (CSS) for receiving a random access response (RAR) from a transmission and reception point (TRP) that transmitted the PDCCH-order DCI is not monitored.

[0085] In a tenth example, the method of the first example, wherein the PDCCH-order DCI comprises a flag indicator field, wherein a first value first value indicates the UE performs the CFRA procedure for the 2TAs_mTRP feature and a second value indicates the UE performs the CFRA procedure for the 2TAs LTM feature .

[0086] In an eleventh example, the method of the first example, further comprising determining a value of a slot index in which the PDCCH-order DCI was received, wherein the UE determines the CFRA procedure for the 2TAs mTRP feature or the 2TAs LTM feature based on the value of the slot index. [0087] In a twelfth example, the method of the eleventh example, wherein the UE determines the CERA procedure for the 2TAs_mTRP feature or the 2TAs_LTM feature based on whether the value of the slot index where the PDCCH-order DCI is received is an even value or an odd value.

[0088] In a thirteenth example, the method of the first example, further comprising determining a value of a Control Resource Set Identification (CORESET ID) or search space ID in which the PDCCH-order DCI was received, wherein the UE determines the CERA procedure for the 2TAs mTRP feature or the 2TAs_LTM feature based on the value of the CORESET ID or search space ID in which the PDCCH-order DCI was received.

[0089] In a fourteenth example, a processor configured to perform any of the methods of the first through thirteenth examples .

[0090] In a fifteenth example, a user equipment (UE) configured to perform any of the methods of the first through thirteenth examples.

[0091] In a sixteenth example, a method, comprising decoding, based on signals received from a base station, a Physical Downlink Control Channel (PDCCH) -order Downlink Control Information (DCI) indicating a user equipment (UE) performs a contention free random access (CERA) procedure for a two timing advances (TAs) with multi-DCI for multi-transmission and reception points (mTRPs) without cell switch (2TAs mTRP) feature of the UE, wherein a first TRP of the mTRPs is associated with a first timing advance group (TAG) and a second TRP of the mTRPs is associated with a second TAG, decoding, based on signals received from a TRP that transmitted the PDCCH-order DCI, a random access response (RAR) message of the CFRA procedure, determining whether the UE resets a closed loop power control (CLPC) index associated with the first TAG or the second TAG based on receiving the RAR message and resetting the determined CLPC of the associated first TAG or second TAG.

[0092] In a seventeenth example, the method of the sixteenth example, wherein the PDCCH-order DCI comprises a CLPC indicator field, wherein a first value first value indicates the UE resets the CLPC of the first TAG and a second value indicates the UE resets the CLPC of the second TAG.

[0093] In an eighteenth example, the method of the sixteenth example, further comprising decoding, based on radio resource control (RRC) signaling received from a network, one-to-one mapping information between a Synchronization Signal Block (SSB) /Physical Random Access Channel (PRACH) pairs or SSB indices and TAG indices, wherein the determined first TAG or second TAG to reset is based on the one-to-one mapping information and a value of the SSB/PRACH pair or SSB index indicated in the PDCCH-order DCI.

[0094] In a nineteenth example, the method of the sixteenth example, further comprising decoding, based on signals received from a network, DCI scheduling a scheduled Physical Downlink Shared Channel (PDSCH) resource for the RAR message, wherein the DCI further comprises a CLPC indicator field, wherein a first value indicates the UE resets the CLPC of the first TAG and a second value indicates the UE resets the CLPC of the second TAG. [ 0095 ] In a twentieth example, the method of the sixteenth example , wherein the RAR message comprises a TAG Identification ( TAG-ID) field, wherein the determined first or second TAG is based on a value of the TAG- ID field .

[ 0096] In a twenty first example , the method of the sixteenth example , wherein the PDCCH-order DCI comprises a Physical Cell Identity ( PCI ) field, wherein the determined first or second TAG is based on a value of the PCI field .

[ 0097 ] In a twenty second example , a processor configured to perform any of the methods of the sixteenth through twenty first examples .

[ 0098 ] In a twenty third example , a user equipment (UE ) configured to perform any of the methods of the sixteenth through twenty first examples .

[ 0099] Those skilled in the art will understand that the above-described example embodiments may be implemented in any suitable software or hardware configuration or combination thereof . An example hardware platform for implementing the example embodiments may include , for example, an Intel x86 based platform with compatible operating system, a Windows OS , a Mac platform and MAC OS , a mobile device having an operating system such as iOS , Android, etc . The example embodiments of the above described method may be embodied as a program containing lines of code stored on a non-transitory computer readable storage medium that , when compiled, may be executed on a processor or microprocessor . [ 0100 ] Although this application described various embodiments each having different features in various combinations , those skilled in the art will understand that any of the features of one embodiment may be combined with the features of the other embodiments in any manner not speci fically disclaimed or which is not functionally or logically inconsistent with the operation of the device or the stated functions of the disclosed embodiments .

[ 0101 ] It is well understood that the use of personally identi fiable information should follow privacy policies and practices that are generally recogni zed as meeting or exceeding industry or governmental requirements for maintaining the privacy of users . In particular, personally identifiable information data should be managed and handled so as to minimi ze risks of unintentional or unauthori zed access or use , and the nature of authori zed use should be clearly indicated to users .

[ 0102 ] It will be apparent to those skilled in the art that various modi fications may be made in the present disclosure , without departing from the spirit or the scope of the disclosure . Thus , it is intended that the present disclosure cover modifications and variations of this disclosure provided they come within the scope of the appended claims and their equivalent .

Claims

What is claimed :

1 . An apparatus comprising processing circuitry configured to : process , based on signals received from a base station, a

Physical Downlink Control Channel ( PDCCH) -order Downlink Control Information ( DCI ) indicating a contention free random access ( CFRA) procedure is to be performed, wherein the apparatus is configured with two timing advances ( TAs ) with multi-DCI for multi-transmission and reception points (mTRPs ) without cell switch ( 2TAs_mTRP ) feature and a Layer 1 /Layer 2 triggered mobility ( 2TAs LTM) feature ; and determine , based on the PDCCH-order DCI , whether the CFRA procedure for the 2TAs_mTRP feature or the 2TAs_LTM feature is to be performed .

2 . The apparatus of claim 1 , wherein the PDCCH-order DCI comprises a cell indicator field, wherein the processing circuitry determines whether to perform the CFRA procedure for the 2TAs_mTRP feature or the 2TAs_LTM feature based on the cell indicator field .

3 . The apparatus of claim 2 , wherein the cell indicator field comprises a 3-bit field, wherein a first value of the cell indicator field indicates the CFRA procedure for the 2TAs mTRP feature is to be performed .

4 . The apparatus of claim 3 , wherein the PDCCH-order DCI further comprises a 1-bit indicator field, wherein a first value of the 1-bit indicator field combined with the first value of the cell indicator field in a same PDCCH-order DCI indicates the CFRA procedure is to be performed for a transmission and reception point ( TRP ) of a serving cell and wherein a second value of the 1-bit indicator field combined with the first value of the cell indicator field in a same PDCCH-order DCI indicates the CFRA procedure is to be performed for a TRP of a non-serving cell .

5. The apparatus of claim 3, wherein any value of the cell indicator field that is not the first value indicates the CFRA procedure is to be performed for the 2TAs LTM feature.

6. The apparatus of claim 5, wherein each of the values of the cell indicator field that is not the first value indicates a corresponding candidate cell with which the CFRA procedure is to be performed for the 2TAs LTM feature.

7. The apparatus of claim 6, wherein each of the values of the cell indicator field that is not the first value comprises a one-to-one mapping with the corresponding candidate cell, wherein the one-to-one mapping is based on candidate cells configured with Physical Random Access Channel (PRACH) resources for early synchronization in an order of increasing candidate cell identification (ID) of the candidate cells.

8. The apparatus of claim 1, wherein the processing circuitry is further configured to: perform the CFRA procedure for the determined 2TAs mTRP feature or the 2TAs LTM feature.

9. The apparatus of claim 8, wherein, when performing the CFRA procedure for the determined 2TAs mTRP feature, the processing circuitry is configured to monitor a Type-1 Common Search Space (CSS) for receiving a random access response (RAR) from a transmission and reception point (TRP) that transmitted the PDCCH-order DCI.

10. The apparatus of claim 8, wherein, when performing the CFRA procedure for the determined 2TAs LTM feature, the processing circuitry does not monitor a Type-1 Common Search Space (CSS) for receiving a random access response (RAR) from a transmission and reception point (TRP) that transmitted the PDCCH-order DCI.

11. An apparatus comprising processing circuitry configured to: generate, for transmission to a user equipment (UE) , a

Physical Downlink Control Channel ( PDCCH) -order Downlink Control Information (DCI) indicating a contention free random access (CFRA) procedure is to be performed by the UE, wherein the UE is configured with two timing advances (TAs) with multi-DCI for multi-transmission and reception points (mTRPs) without cell switch (2TAs mTRP) feature and a Layer 1/Layer 2 triggered mobility (2TAs_LTM) feature.

12. The apparatus of claim 11, wherein the PDCCH-order DCI comprises a cell indicator field configured to indicate whether the UE performs the CFRA procedure for the 2TAs mTRP feature or the 2TAs LTM feature.

13. The apparatus of claim 12, wherein the cell indicator field comprises a 3-bit field, wherein a first value of the cell indicator field indicates the UE is to perform the CFRA procedure for the 2TAs mTRP feature.

14. The apparatus of claim 13, wherein the PDCCH-order DCI further comprises a 1-bit indicator field, wherein a first value of the 1-bit indicator field combined with the first value of the cell indicator field in a same PDCCH-order DCI indicates the UE is to perform the CERA procedure for a transmission and reception point ( TRP ) of a serving cell and wherein a second value of the 1-bit indicator field combined with the first value of the cell indicator field in a same PDCCH-order DCI indicates the UE is to perform the CERA procedure for a TRP of a nonserving cell .

15 . The apparatus of claim 13 , wherein any value of the cell indicator field that is not the first value indicates the UE is to perform the CERA procedure for the 2TAs_LTM feature .

16 . The apparatus of claim 15 , wherein each of the values of the cell indicator field that is not the first value indicates a corresponding candidate cell with which the UE is to perform the CERA procedure for the 2TAs_LTM feature .

17 . The apparatus of claim 16 , wherein each of the values of the cell indicator field that is not the first value comprises a one-to-one mapping with the corresponding candidate cell , wherein the one-to-one mapping is based on candidate cells configured with Physical Random Access Channel ( PRACH) resources for early synchroni zation in an order of increasing candidate cell identi fication ( ID) of the candidate cells .

18 . A user equipment (UE ) , comprising : a transceiver configured to communicate with a base station; and a processor communicatively coupled to the transceiver and configured to : process, based on signals received from the base station, a Physical Downlink Control Channel ( PDCCH) -order Downlink Control Information (DCI) indicating a contention free random access (CFRA) procedure is to be performed, wherein the apparatus is configured with two timing advances (TAs) with multi-DCI for multi-transmission and reception points (mTRPs) without cell switch (2TAs mTRP) feature and a Layer 1/Layer 2 triggered mobility (2TAs_LTM) feature; and determine, based on the PDCCH-order DCI, whether the CFRA procedure for the 2TAs mTRP feature or the 2TAs LTM feature is to be performed.

19. The UE of claim 18, wherein the PDCCH-order DCI comprises a cell indicator field, wherein the processor determines whether the UE performs the CFRA procedure for the 2TAs_mTRP feature or the 2TAs LTM feature based on the cell indicator field.

20. The US of claim 19, wherein the cell indicator field comprises a 3-bit field, wherein a first value of the cell indicator field indicates the CFRA procedure for the 2TAs mTRP feature is to be performed and any value of the cell indicator field that is not the first value indicates the CFRA procedure is to be performed for the 2TAs LTM feature.