Multiple TA values in multi-TRP scenario in wireless communication system

Abstract

A method in a user equipment, UE, comprises receiving (906), from a radio access network, RAN, a configuration comprising a first timing advance, TA, value and a second TA value for use in a serving cell; receiving (908), from the RAN, a spatial indication for communicating signals between the UE and the RAN; selecting (914) a TA value from among the first TA value and the second TA value based on the spatial indication; and communicating (922, 926) a signal with the RAN using the selected TA value.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of priority and filing date of Provisional U.S. Patent Application No. 63 / 393,814, entitled “ENABLING MULTIPLE TA VALUES IN MULTIPLE-TRP SCENARIOS IN A WIRELESS COMMUNICATION SYSTEM,” filed on July 29, 2022. The entire contents of this provisional application are hereby expressly incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to wireless communications, and more particularly to using multiple TA values ​​in a serving cell at the UE side or NW / base station (BS) side. The technology can be applicable to multiple transmission and / or reception point (M-TRP) scenarios. Background Art

[0004] This background description is provided for the purpose of generally presenting the context of the present disclosure. The work of the presently named inventors, to the extent that it is described in this background section, and aspects of the specification that might not have been identified as prior art at the time of filing are neither explicitly nor implicitly admitted to be prior art to the present disclosure.

[0005] Generally speaking, a base station operating a cellular radio access network (RAN) uses a specific radio access technology (RAT) and multiple layers of a protocol stack to communicate with a user equipment (UE). For example, the physical layer (PHY) of the RAT provides a transport channel to the medium access control (MAC) sublayer, which in turn provides a logical channel to the radio link control (RLC) sublayer, and the RLC sublayer in turn provides data transfer services to the packet data convergence protocol (PDCP) sublayer. The radio resource control (RRC) sublayer is arranged above the PDCP sublayer.

[0006] The RRC sublayer specifies: an RRC_IDLE state, in which the UE does not have an active radio connection with a base station; an RRC_CONNECTED state, in which the UE has an active radio connection with a base station; and an RRC_INACTIVE state, which allows the UE to transition back to the RRC_CONNECTED state more quickly due to radio access network (RAN) level base station coordination and RAN paging procedures. In some cases, a UE in the RRC_IDLE or RRC_INACTIVE state has only one relatively small packet to transmit. In some such cases, a UE in the RRC_IDLE or RRC_INACTIVE state performs early data transmission without transitioning to the RRC_CONNECTED state.

[0007] Regarding the PHY layer, in some cases, different channel or reference signal (RS) configurations correspond to different beam indication techniques. For most DL transmissions (e.g., physical downlink shared channel (PDSCH), physical downlink control channel (PDCCH), or channel state information (CSI) resource signal (CSI-RS)), the transmission configuration indication (TCI) framework and TCI state are applicable and configured for such transmissions. However, in some cases, PDCCH transmission requires MAC-CE to further indicate the TCI state within the configured TCI state, and for this, PDSCH transmission similarly requires MAC-CE and downlink control information (DCI). For the physical uplink shared channel (PUSCH), the UL beam indication depends on the index of the sounding reference signal (SRS) resource on which the UE has transmitted at least once. In some cases, for the physical uplink control channel (PUCCH), the MAC-CE indication is used by the UE to derive the spatial relationship of the UL beam. Further, the spatial relationship is sometimes also configured in an SRS resource set, which indicates the same UL beam applicable to all SRS resources in the SRS resource set. However, these messages result in large signaling overhead when many channels or RSs share the same beam. Summary of the invention

[0008] An example embodiment of the technology of the present disclosure is a method in a UE. The method includes: receiving a configuration including a first timing advance (TA) value and a second TA value for use in a serving cell from a RAN; receiving a spatial indication for communicating signals between the UE and the RAN from the RAN; selecting a TA value from among the first TA value and the second TA value based on the spatial indication; and communicating a signal with the RAN using the selected TA value.

[0009] Another example embodiment of the techniques is a method in a RAN. The method includes: sending a configuration including a first timing advance (TA) value and a second TA value for use in a serving cell to a UE; sending (564) from the RAN a spatial indication for communicating signals between the UE and the RAN, the spatial indication being associated with one of the first TA value or the second TA value; and communicating (576) a signal with the UE based on the spatial indication.

[0010] Yet another example embodiment of the techniques is a device comprising a transceiver configured to communicate with a radio interface and processing hardware configured to implement one of the methods described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1A is a block diagram of an example system in which distributed base stations and / or user equipment (UE) may implement the techniques of the present disclosure;

[0012] Figure 1B Yes Figure 1A A block diagram of an example base station operating in a system of the invention, the example base station comprising a central unit (CU) and a distributed unit (DU) of a distributed base station;

[0013] Figure 2A yes Figure 1A to Figure 1B A block diagram of an example protocol stack according to which a UE may communicate with a base station;

[0014] Figure 2B yes Figure 1A to Figure 1B A block diagram of an example protocol stack according to which a UE may communicate with a DU and a CU of a base station; and

[0015] Figure 3A Yes Figure 2A and / or Figure 2B A block diagram of the detailed structure of each sub-layer of the depicted protocol stack, including scheduling and / or priority handling functions;

[0016] Figure 3B is with Figure 3A A block diagram of the detailed structure of the various sub-layers of a similar protocol stack, but wherein the structure includes a logical channel prioritization function;

[0017] Figure 4A is a block diagram of a HARQ entity including multiple HARQ processes and communicating using transport channels to multiple TRPs;

[0018] Figure 4B is with Figure 4AA block diagram of a HARQ entity similar to that of a HARQ entity, but wherein the HARQ entity includes multiple HARQ process groups associated with multiple transport channels to multiple TRPs;

[0019] Figure 4C is with Figure 4A A block diagram of a HARQ entity similar to that of a HARQ entity, but wherein the HARQ entity communicates with a single TRP;

[0020] Figure 5A is a message passing diagram for an example scenario in which a UE is synchronized with a first TRP and / or a second TRP for performing communications with a base station;

[0021] Figure 5B is with Figure 5A Messaging diagram for a similar example scenario, but where the UE receives UL and DL configuration parameters in separate radio resource configuration messages;

[0022] Figure 5C is with Figure 5A A message passing diagram for a similar example scenario, but where the base station sends the UL configuration parameters to the UE via the second TRP instead of the first TRP;

[0023] Figure 5D is with Figure 5A a message passing diagram for a similar example scenario, but where the UE receives a response from the base station while performing a random access procedure via the first TRP instead of the second TRP;

[0024] Figure 5E is with Figure 5A Message passing diagram for a similar example scenario, but where the UE receives the PDCCH order via the first TRP instead of the second TRP;

[0025] Figure 6 is a flowchart of an example method, wherein Figure 1A and / or Figure 1B The UE determines whether to send an UL transmission to the base station using a first TA value or a second TA value based on which TA value the UL transmission is associated with;

[0026] Figure 7 is with Figure 6 A flow chart of a similar example method, but wherein the UE determines whether to send an UL transmission using a first TA value or a second TA value based on whether the configuration of the UL transmission includes a first index or a second index;

[0027] Figure 8 is with Figure 6A flow chart of a similar example method, but wherein the UE determines whether to send an UL transmission using a first TA value or a second TA value based on whether the CORESET is associated with a first index or a second index;

[0028] Fig. 9A is with Figure 6 A flow chart of a similar example method, but wherein the UE determines whether to send an UL transmission using a first TA value or a second TA value based on whether the spatial indication is associated with a first index or a second index;

[0029] Fig. 9B is with Fig. 9A A flow chart of a similar example method, but wherein the UE determines whether to send an UL transmission using a first TA value or a second TA value based on whether the reference signal is associated with a first index or a second index;

[0030] Fig.10 is with Figure 6 A flow chart of a similar example method, but wherein the UE determines whether to send an UL transmission using a first TA value or a second TA value based on whether the path loss reference signal is associated with a first index or a second index;

[0031] Fig.11 is with Figure 6 A flow chart of a similar example method, but wherein the UE determines whether to send an UL transmission using a first TA value or a second TA value based on whether the UL transmission is included in a first group or a second group; and

[0032] Fig.12 is with Figure 6 Flowchart of a similar example method, but wherein the UE determines whether to send an UL transmission using a first TA value or a second TA value based on whether the HARQ process is included in a first set of HARQ processes or a second set of HARQ processes. DETAILED DESCRIPTION

[0033] The techniques discussed below are applicable at least to M-TRP scenarios involving multiple timing advance (TA) values, where the UE maintains multiple TA values ​​in at least one serving cell. The methods discussed below allow the device to correctly associate a channel or reference signal (RS) with a TA value so that the UE determines which TA value to apply for an UL transmission (e.g., an RS transmission). These techniques also allow the UE to report on the ability to support multiple TA values.

[0034] First reference Figure 1A, the example wireless communication system 100 includes a UE 102, a base station (BS) 104, a base station 106, and a core network (CN) 110. The base stations 104 and 106 may operate in a RAN 105 connected to the core network (CN) 110. The CN 110 may be implemented as, for example, an evolved packet core (EPC) 111 or a fifth generation (5G) core (5GC) 160. In another example, the CN 110 may also be implemented as a sixth generation (6G) core.

[0035] Base station 104 may utilize one or more transmission and / or reception points (TRPs) to cover one or more cells (e.g., cells 124 and 125), and base station 106 may similarly utilize one or more TRPs to cover one or more cells (e.g., cell 126). For example, base station 104 operates cell 124 using TRPs 107-1 and 107-2 and operates cell 125 using TRP 107-3, and base station 106 operates cell 126 using TRPs 108-1 and 108-2. Cells 124 and 125 operate on one or more of the same carrier frequencies. Cell 126 may operate on the same one or more carrier frequencies as cells 124 and 125. Alternatively, cell 126 may operate on one or more carrier frequencies different from cells 124 and 125. In some implementations, base station 104 connects each of TRPs 107-1, 107-2, and 107-3 via a fiber optic connection or an Ethernet connection. If base station 104 is a gNB, cells 124 and 125 are NR cells. If base station 104 is an (ng-)eNB, cells 124 and 125 are Evolved Universal Terrestrial Radio Access (EUTRA) cells. Similarly, if base station 106 is a gNB, cell 126 is an NR cell, and if base station 106 is an (ng-)eNB, cell 126 is an EUTRA cell. Cells 124, 125, and 126 may be located in the same radio access network notification area (RNA) or in different RNAs. In general, RAN 105 may include any number of base stations, and each of the base stations may cover one, two, three, or any other suitable number of cells. UE 102 may support at least 5G NR (or simply "NR") or E-UTRA air interface to communicate with base station 104 via TRP 107-1, TRP 107-2, and / or TRP 107-3. Similarly, UE 102 may support at least 5G NR (or simply "NR") or E-UTRA air interface to communicate with base station 106 via TRP 108-1 and / or TRP 108-2. Each of base stations 104, 106 may be connected to CN 110 via an interface (e.g., S1 or NG interface). Base stations 104 and 106 may also be interconnected via an interface (e.g., X2 or Xn interface) for interconnecting NG RAN nodes.

[0036] When a base station (e.g., base station 104 or 106) sends DL data via a TRP (e.g., TRP 107-1, TRP 107-2, TRP 107-3, TRP 108-1, or TRP 108-2), the base station 104 may generate a packet including the data and send the packet to the TRP 107-1. For example, the packet may be a fronthaul transmission protocol data unit. The TRP extracts the data from the packet and sends the data. In some implementations, the base station 104 may include control information for time-critical control and management information directly related to the data in the packet, and the TRP may send the data based on the control information. In some implementations, the data includes in-phase and quadrature (IQ) data, a physical layer bit sequence, or a MAC PDU. When the TRP receives data from a UE (e.g., UE 102), the TRP generates a packet including the data and sends the packet to the base station 104. In some implementations, the data includes IQ data, a physical layer bit sequence, or a MAC PDU.

[0037] Among other components, the EPC 111 may include a serving gateway (SGW) 112, a mobility management entity (MME) 114, and a packet data network gateway (PGW) 116. Generally speaking, the SGW 112 is configured to deliver user plane packets related to audio calls, video calls, Internet traffic, etc., and the MME 114 is configured to manage authentication, registration, paging, and other related functions. The PGW 116 provides connectivity from the UE 102 to one or more external packet data networks (e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network). The 5GC 160 includes a user plane function (UPF) 162 and an access and mobility management function (AMF) 164 and / or a session management function (SMF) 166. Generally, UPF 162 is configured to pass user plane packets associated with audio calls, video calls, Internet traffic, etc., AMF 164 is configured to manage authentication, registration, paging and other related functions, and SMF 166 is configured to manage PDU sessions.

[0038] like Figure 1A As shown, base station 104 supports cells 124 and 125, and base station 106 supports cell 126. Cells 124, 125, and 126 may partially overlap, so that UE 102 may select, reselect, or switch from one of cells 124, 125, and 126 to another. In order to exchange messages or information directly, base station 104 and base station 106 may support an X2 or Xn interface. In general, CN 110 may be connected to any suitable number of base stations supporting NR cells and / or EUTRA cells.

[0039] The base station 104 is equipped with processing hardware 130, which may include one or more general-purpose processors (e.g., CPUs) and non-transitory computer-readable memory storing instructions executed by the one or more general-purpose processors. Additionally or alternatively, the processing hardware 130 may include a dedicated processing unit. The processing hardware 130 may include a PHY controller 132, which is configured to send data and control signals on physical DL channels and DL reference signals with one or more user devices (e.g., UE 102) via one or more TRPs (e.g., TRP 107-1, TRP 107-2, and / or TRP 107-3). The PHY controller 132 is also configured to receive data and control signals on physical UL channels and / or UL reference signals with one or more user devices via one or more TRPs (e.g., TRP 107-1, TRP 107-2, and / or TRP 107-3). In an example implementation, the processing hardware 130 includes a MAC controller 134 configured to perform a random access (RA) procedure with one or more user devices, manage UL timing advance for one or more user devices, receive UL MAC PDUs from one or more user devices, and send DL MAC PDUs to one or more user devices. The processing hardware 130 may further include an RRC controller 136 to implement procedures and messaging at the RRC sublayer of the protocol communication stack. The base station 106 may include processing hardware 140 similar to the processing hardware 130. In particular, components 142, 144, and 146 may be similar to components 132, 134, and 136, respectively.

[0040] UE 102 is equipped with processing hardware 150, which may include one or more general-purpose processors (such as CPUs) and non-transitory computer-readable memory storing machine-readable instructions that can be executed on one or more general-purpose processors, and / or dedicated processing units. PHY controller 152 is also configured to receive data and control signals on physical DL channels and / or DL ​​reference signals with base stations 104 or 106 via one or more TRPs (e.g., TRP 107-1, TRP 107-2, TRP 107-3, TRP 108-1, and / or TRP 108-2). PHY controller 152 is also configured to send data and control signals on physical UL channels and / or UL reference signals with base stations 104 or 106 via one or more TRPs (e.g., TRP 107-1, TRP 107-2, TRP 107-3, TRP 108-1, and / or TRP 108-2). In an example implementation, the processing hardware 150 includes a MAC controller 154 configured to perform a random access procedure with the base station 104 or 106, manage UL timing advance for one or more user devices, send UL MAC PDUs to the base station 104 or 106, and receive DL MAC PDUs from the base station 104 or 106. The processing hardware 150 may further include an RRC controller 156 to implement procedures and messaging at the RRC sublayer of the protocol communication stack.

[0041] Figure 1B An example distributed or decomposed implementation of one or both of the base stations 104, 106 is depicted. In this implementation, each of the base stations 104 or 106 includes a central unit (CU) 172 and one or more distributed units (DU) 174. The CU 172 includes processing hardware, such as one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions that can be executed on the general-purpose processors, and / or a dedicated processing unit. For example, the CU 172 may include a PDCP controller (e.g., PDCP controllers 134, 144), an RRC controller (e.g., RRC controllers 136, 146), and / or an RRC inactive controller (e.g., RRC inactive controllers 138, 148). In some implementations, the CU 172 may include an RLC controller that is configured to manage or control one or more RLC operations or processes. In other implementations, the CU 172 does not include an RLC controller.

[0042] Each DU in DU 174 also includes processing hardware, which may include one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions that can be executed on one or more general-purpose processors, and / or a dedicated processing unit. For example, the processing hardware may include a MAC controller (e.g., MAC controllers 132, 142) configured to manage or control one or more MAC operations or processes (e.g., random access processes); and / or an RLC controller configured to manage or control one or more RLC operations or processes. The processing hardware may also include a physical layer controller configured to manage or control one or more physical layer operations or processes.

[0043] In some implementations, the RAN 105 supports integrated access and backhaul (IAB) functionality. In some implementations, the DU 174 operates as an (IAB) node and the CU 172 operates as an IAB donor.

[0044] In some implementations, the CU 172 may include a logical node CU-CP 172A that hosts a control plane portion of a PDCP protocol of the CU 172. The CU 172 may also include a logical node CU-UP 172B that hosts a user plane portion of a PDCP protocol and / or SDAP protocol of the CU 172. The CU-CP 172A may send control information (e.g., RRC messages, F1 application protocol messages), and the CU-UP 172B may send data packets (e.g., SDAP PDUs or IP packets).

[0045] The CU-CP 172A may be connected to multiple CU-UPs 172B via an E1 interface. The CU-CP 172A selects an appropriate CU-UP 172B for the requested service of the UE 102. In some implementations, a single CU-UP 172B may be connected to multiple CU-CPs 172A via an E1 interface. If the CU-CP 172A and the DU 174 belong to a gNB, the CU-CP 172A may be connected to one or more DUs 174 via an F1-C interface and / or an F1-U interface. If the CU-CP 172A and the DU 174 belong to an ng-eNB, the CU-CP 172A may be connected to the DU 174 via a W1-C interface and / or a W1-U interface. In some implementations, one DU 174 may be connected to multiple CU-UPs 172B under the control of the same CU-CP 172A. In such implementations, connectivity between the CU-UP 172B and the DU 174 is established by the CU-CP 172A using bearer context management functions.

[0046] Figure 2A An example protocol stack 200 is illustrated in a simplified manner according to which a UE 102 may communicate with an eNB / ng-eNB or gNB (e.g., one or more of base stations 104, 106).

[0047] In the example stack 200, the physical layer (PHY) 202A of EUTRA provides transport channels to the EUTRA MAC sublayer 204A, which in turn provides logical channels to the EUTRA RLC sublayer 206A. The EUTRA RLC sublayer 206A in turn provides RLC channels to the EUTRA PDCP sublayer 208 and, in some cases, to the NR PDCP sublayer 210. Similarly, the NR PHY 202B provides transport channels to the NR MAC sublayer 204B, which in turn provides logical channels to the NR RLC sublayer 206B. The NR RLC sublayer 206B in turn provides data transfer services to the NR PDCP sublayer 210. The NR PDCP sublayer 210 may in turn provide data to the SDAP sublayer 212 or the RRC sublayer ( Figure 2A (not shown) provides data transfer services. In some implementations, such as Figure 2A As shown, UE 102 supports both EUTRA and NR stacks to support handover between EUTRA and NR base stations and / or support dual connectivity (DC) implemented through EUTRA and NR interfaces. Figure 2A As shown, the UE 102 can support NR PDCP 210 layered on EUTRA RLC 206A and SDAP sublayer 212 layered on NR PDCP sublayer 210.

[0048] The EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 receive packets, which may be referred to as SDUs (e.g., from an IP layer layered directly or indirectly on the PDCP layer 208 or 210), and output packets, which may be referred to as PDUs (e.g., to the RLC layer 206A or 206B). For simplicity, this disclosure refers to both SDUs and PDUs as "packets," except where the difference between SDUs and PDUs is relevant.

[0049] On the control plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 may provide the RRC sublayer ( Figure 2AThe NR PDCP sublayer 210 may provide a signaling radio bearer (SRB) to exchange, for example, RRC messages or NAS messages. On the user plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 may provide a data radio bearer (DRB) to support data exchange. The data exchanged on the NR PDCP sublayer 210 may be an SDAP PDU, an IP packet, or an Ethernet packet.

[0050] Therefore, it is possible to functionally partition the radio protocol stack, e.g. Figure 2B 206B, NR MAC 204B, and NR PHY 202B) are delegated to the DU. To support the connection to the 5GC, the NR PDCP 210 provides SRBs to the RRC 214, and the NR PDCP 210 provides DRBs to the SDAP 212 and provides SRBs to the RRC 214.

[0051] Figure 3A Detailed structure 300A of the NR layer 2 protocol stack 200 or 250 of the base station 104 or 106 is shown. PHY 202 ( Figure 3A The MAC sublayer 204 includes a scheduling and / or priority handling function for scheduling DL and UL transmissions with one or more user devices and / or prioritizing the DL and UL transmissions. The MAC sublayer 204 also includes a multiplexing function for DL ​​transmissions and / or a demultiplexing function for UL transmissions with a specific user device. The MAC sublayer 204 further includes a hybrid automatic repeat request (HARQ) entity for DL ​​transmissions and / or UL transmissions with a specific user device on a specific DL component carrier (CC) and / or a specific UL CC. The RLC sublayer 206 includes a segmentation and automatic repeat request (ARQ) function for DL ​​data and UL data communicated with one or more UEs. The PDCP sublayer 210 provides a radio bearer to the SDAP sublayer 212 and includes (i) security and (ii) robust header compression (ROHC) functions for (i) integrity protection and / or encryption / description and (ii) header compression / decompression, respectively. The SDAP sublayer 212 provides 5GC QoS flow to the upper layer.

[0052] Figure 3B Detailed structure 300B of the NR layer 2 protocol stack 200 or 250 of the UE 102 is illustrated similar to structure 300A. PHY202 ( Figure 3BThe MAC sublayer 204 includes one or more HARQ entities, each for DL ​​transmission and / or UL transmission with the base station 104 or 106 on a specific DL CC and / or a specific UL CC. The MAC sublayer 204 also includes logical channel prioritization and multiplexing functions for UL transmission to the base station 104 or 106, and includes a demultiplexing function for DL ​​transmission from the base station 104 or 106. The RLC sublayer 206 includes segmentation and automatic repeat request (ARQ) functions for DL ​​data and UL data communicated with the base station 104 and / or 106. The PDCP sublayer 210 provides radio bearers to the SDAP sublayer 212, and includes (i) security and (ii) robust header compression (ROHC) functions for (i) integrity protection and / or encryption / description and (ii) header compression / decompression, respectively. The SDAP sublayer 212 provides 5GC QoS flow to the upper layer.

[0053] FIG. 4A to FIG. 4C Example for a specific CC y Different implementations of HARQ entities for multi-TRP (mTRP) operation on (e.g., UL CC or DL ​​CC), which can be implemented in UE 102, base station 104 or 106, or DU 174 of base station 104 or 106.

[0054] First reference Figure 4A , which depicts a HARQ entity 400A. In some implementations, the HARQ entity 400A includes HARQ processes 1, ..., N for communicating with TPRs 1, ..., m. N is an integer and greater than zero, and m is an integer and greater than zero. For example, N is 8, 16, 32, etc., and m is 2, 3, 4, etc.

[0055] Next, Figure 4B A further implementation of a HARQ entity 400B is depicted that is similar to the HARQ entity 400A. The difference between the implementations of the HARQ entity 400B and 400A is that the HARQ entity 400B divides the HARQ processes 1, ..., N into m groups, where each group is used for communication with a specific TRP.

[0056] Next, Figure 4C 4. An implementation of a HARQ entity 400C (eg, HARQ entity k) similar to the HARQ entity 400A is depicted. The difference between the implementations of the HARQ entities 400C and 400A is that the HARQ entity 400C is used to perform a multi-step process in a specific CC (eg, CC k ) with a specific TRP (e.g., TRP k), where 1<=k<=m. In other words, UE 102 uses HARQ entities 1, ..., m on each UL CC to communicate with a RAN node (e.g., base station 104 or 106, or DU 174) via TRP 1, ..., m, respectively. Similarly, the RAN node uses HARQ entities 1, ..., m on each DL CC to communicate with UE 102 via TRP 1, ..., m of the RAN node (e.g., base station 104 or 106, or DU 174), respectively.

[0057] Next, refer to FIG. 5A to FIG. 5E To discuss the Figure 1A The various components of and several example scenarios related to mTRP operation. FIG. 5A to FIG. 5E Identical events are marked with the same reference numerals.

[0058] First reference Figure 5A , in scenario 500A, base station 104 operates cell 124, TRP 107-1, and TRP 107-2. In scenario 500A, base station 104 broadcasts (e.g., periodically) 504, 506 one or more synchronization signal blocks (SSBs) via TRP 107-1 and broadcasts 508, 510 system information. In some implementations, the system information includes a master information block (MIB) and / or a system information block (SIB). In some examples, the SIB includes SIB1, and further includes SIB2, SIB3, SIB4, and / or SIB5. UE 102 initially operates 502 in an idle state (e.g., RRC_IDLE state). UE 102 in the idle state receives 504, 506 SSBs from base station 104 via TRP 107-1 and receives 508, 510 system information. In some implementations, the UE 102 detects that the base station 104 transmits the SSB via the TRP 107-1. In some implementations, the UE 102 then uses one of the SSBs to perform downlink synchronization with the base station 104 on the cell 124 via the TRP 107-1, and receives 508, 510 system information via the TRP 107-1 based on the SSB.

[0059] Later, the UE 102 determines to perform 590 a random access procedure to perform 592 an RRC connection establishment procedure. In response to the determination, the UE 102 sends 512 a first random access preamble to the TRP 107-1 on a time / frequency resource and / or a random access channel (RACH) opportunity. The TRP 107-1 then forwards 514 the first random access preamble to the base station 104. In some implementations, the UE 102 selects an SSB from the SSBs for which the RSRP obtained by the UE 102 is higher than a first threshold (e.g., rsrp-ThresholdSSB) for the random access procedure. In other implementations, in the event that the RSRP for any SSB in the SSBs is not higher than the first threshold, the UE 102 selects an SSB from the SSBs and uses the SSB to determine the first random access preamble. In some such cases, the UE 102 selects the SSB from the SSBs randomly, or selects based on the UE implementation. Then, the UE 102 determines a first random access preamble, a time / frequency resource, and / or a RACH opportunity based on the selected SSB and a random access configuration parameter included in the system information (e.g., SIB1). In some implementations, the random access configuration parameter indicates one or more associations between (i) the SSB and (ii) the random access preamble, the RACH opportunity, and / or the time / frequency resource. Based on the selected SSB and the association, the UE 102 determines a first random access preamble, a RACH opportunity, and / or a time / frequency resource for sending the first random access preamble.

[0060] In response to the first random access preamble, the base station 104 sends 516 a first random access response to the TRP 107-1. The TRP 107-1 then forwards 518 the first random access response to the UE 102. In some implementations, the base station 104 or the TRP 107-1 identifies the SSB associated with the first random access preamble, RACH opportunity, and / or time / frequency resource. In some cases where a single SSB is associated with the first random access preamble, RACH opportunity, and / or time / frequency resource, the identified SSB is the SSB selected by the UE 102. In some cases where multiple SSBs are associated with the first random access preamble, RACH opportunity, and / or time / frequency resource, the identified SSB is the same as or different from the SSB selected by the UE 102. In such implementations, the base station 104 sends the first random access response to the UE 102 via the TRP 107-1 based on the identified SSB. The base station 104 includes the first preamble ID and the first TA command in the first random access response. The first preamble ID identifies the first random access preamble, and the first TA command includes a first TA value. The UE applies the first TA value and determines or maintains 520 an uplink synchronized (e.g., time aligned) with the TRP 107-1 after applying the first TA value (e.g., in response to applying the first TA value). The UE 102 applies the first TA value for sending UL transmissions (e.g., PUCCH transmissions, PUSCH transmissions, and / or sounding reference signal transmissions) until a new or different TA value that updates the first TA value is received from the base station 104. In some implementations, the UE 102 starts a first time alignment timer (TAT) after or upon receiving the first TA command to maintain a UL synchronization state with the TRP 107-1 or the base station 104. In some implementations, the base station 104 includes a UL grant (i.e., a RAR grant) in the random access response.

[0061] In some implementations, after sending a random access response or a first TA command to UE 102, base station 104 starts a first TAT to maintain first UL synchronization for UL and / or DL ​​communications with UE 102 via TRP 107-1. In some implementations, TRP 107-1 generates timing information for or based on a first random access preamble received from UE 102, and sends the timing information to base station 104. In some examples, the timing information indicates a propagation delay or a propagation delay offset. Based on the timing information received from TRP 107-1, base station 104 determines a first TA value.

[0062] Blocks 512, 514, 516, 518, and 520 are Figure 5A It is collectively referred to as the random access process 590.

[0063] During or after the random access procedure 590, the UE 102 sends 522, 524 an RRC setup request message (e.g., an RRCSetupRequest message) to the base station via TRP 107-1. In some implementations, the UE 102 sends the RRC setup request message using the UL grant received in the random access response. In response to the RRC setup request message, the base station 104 sends 526, 528 an RRC setup message (e.g., an RRCSetup message) to the UE 102 via TRP 107-1. In some implementations, the base station 104 sends a MAC PDU including contention resolution (e.g., a MAC control element (CE)) to the UE 102 to resolve contention for the random access procedure. In some implementations, the base station 104 includes the RRC setup message in the MAC PDU. In further implementations, after sending the MAC PDU, the base station 104 sends another MAC PDU including the RRC setup message to the UE 102. In response to the RRC setup message, the UE 102 transitions 530 to a connected state (e.g., RRC_CONNECTED) and sends 532, 534 an RRC setup complete message (e.g., RRCSetupComplete message) to the base station 104 via the TRP 107-1. In some implementations, after performing the RRC connection establishment procedure with the UE 102, the base station 104 performs a security activation procedure with the UE 102 to activate security protection (e.g., integrity protection / integrity check and encryption / decryption) for UL data and DL data communicated between the UE 102 and the base station 104. In further implementations, after performing the RRC connection establishment procedure or the security activation procedure, the base station 104 performs a radio bearer configuration procedure with the UE 102 to configure SRB2 and / or DRB for the UE 102.

[0064] After performing an RRC connection establishment procedure, a security activation procedure, or a radio bearer configuration procedure, the base station 104 sends 536, 538 an RRC reconfiguration message (e.g., an RRCReconfiguration message) to the UE 102 via TRP 107-1, the RRC reconfiguration message including a channel state information (CSI) resource configuration and a CSI report configuration. In response, the UE 102 sends 540, 542 an RRC reconfiguration completion message (e.g., an RRCReconfigurationComplete message) to the base station 104 via TRP 107-1. In some implementations, the CSI resource configuration includes configuring configuration parameters of a channel state information reference signal (CSI-RS) for measurement by the UE 102. The base station 104 sends the CSI-RS via TRP 107-2 according to the CSI resource configuration. The UE 102 performs measurements on the CSI-RS according to the CSI resource configuration. In some implementations, the CSI resource configuration includes configuring configuration parameters of an SSB for measurement by the UE 102. The base station 104 sends the SSB via TRP 107-2. The UE 102 performs measurements on the SSB according to the CSI resource configuration. In other implementations, the RRC reconfiguration message or the CSI resource configuration does not include configuration parameters to configure the SSB. In some such cases, the base station 104 still sends the SSB via TRP 107-2, and the UE 102 performs measurements on the SSB. Based on the CSI report configuration, the UE 102 generates a CSI report from the measurement of the CSI-RS or SSB, and sends 544, 546 the CSI report to the base station 104 via TRP 107-1. In some implementations, the UE 102 sends the CSI report to the base station 104 on the PUCCH via TRP 107-1. In some implementations, the CSI report configuration configures periodic or semi-persistent reporting, or the CSI report configuration configures semi-persistent or aperiodic reporting triggered by DCI. The CSI report includes a periodic CSI report, a semi-persistent CSI report and / or an aperiodic CSI report.

[0065] In some implementations, the base station 104 includes the CSI resource configuration and / or the CSI report configuration in a CSI measurement configuration (e.g., CSI-MeasConfig IE). The base station 104 then includes the CSI measurement configuration in the RRC reconfiguration message of events 536, 538. In other implementations, the CSI resource configuration includes NZP-CSI-RS-Resource IE, NZP-CSI-RS-ResourceSet IE, CSI-SSB-ResourceSet IE, CSI-ResourceConfig IE, and / or CSI-ReportConfig IE.

[0066] Boxes 536, 538, 540, 542, 544, and 546 are Figure 5A The process is collectively referred to as CSI resource configuration and CSI reporting process 594.

[0067] After receiving the CSI report at event 546, the base station 104 determines, based on the CSI report, to communicate with the UE 102 via TRP 107-2 while maintaining a link with the UE 102 via TRP 107-1. In some implementations, the base station 104 makes the determination based on one or more capabilities of the UE 102. In response to the determination, the base station 104 sends 548, 550 an RRC reconfiguration message to the UE 102 via TRP 107-1, the RRC reconfiguration message including DL and UL configuration parameters for DL ​​and UL communications, respectively, with the base station 104 via TRP 107-2. In some implementations, the base station 104 includes the DL and UL configuration parameters in a CellGroupConfig IE and includes the CellGroupConfig IE in the RRC reconfiguration message. In some implementations, the base station 104 includes the DL configuration parameters in a bandwidth part (BW) IE such as a BWP-DownlinkDedicated IE, and includes the BWP-DownlinkDedicated IE in the RRC reconfiguration message. In some implementations, the base station 104 includes the UL configuration parameters in a BWP-UplinkDedicated IE, and includes the BWP-UplinkDedicated IE in the RRC reconfiguration message.

[0068] In response to the RRC reconfiguration complete message, UE 102 sends 552, 554 an RRC reconfiguration complete message to base station 104 via TRP 107-1. In some implementations, UE 102 applies the DL configuration parameters upon receiving the RRC reconfiguration message at event 554. In such implementations, UE 102 performs 556 DL communications with base station 104 via TRP 107-2 in accordance with the DL configuration parameters while performing DL and UL communications with base station 104 via TRP 107-1. In some implementations, UE 102 refrains from performing UL communications in accordance with the UL configuration parameters until after performing a random access procedure with base station 104 via TRP 107-2 at event 598. In further implementations, UE 102 refrains from performing DL communications with base station 104 via TRP 107-2 until after performing a random access procedure with base station 104 via TRP 107-2 at event 598. In some implementations, base station 104 avoids performing UL communications and / or configuring UL configuration parameters until after a random access procedure with base station 104 via TRP 107-2 is completed at event 598. In some implementations, base station 104 avoids performing DL communications and / or configuring DL configuration parameters until after a random access procedure with base station 104 via TRP 107-2 is completed at event 598.

[0069] In some implementations, base station 104 and UE 102 use Figure 4A , Figure 4B or Figure 4C 107-2 to perform DL communication with base station 104 via TRP 107-1 and TRP 107-2 at event 556. Figure 4B In some cases of the HARQ entity 400B of the present invention, the DL configuration parameters of events 548 and 550 include HARQ configuration parameters. The HARQ configuration parameters configure the first HARQ process ID set and the second HARQ process ID set. In some cases, the first HARQ process ID set and the second HARQ process ID set are used for TRP 107-1 and TRP 107-2, respectively. The first HARQ process ID set and the second HARQ process ID set identify the first HARQ process set of the HARQ entity and the second HARQ process set of the HARQ entity, respectively. In some implementations, none of the first HARQ process ID set and the second HARQ process ID set are the same. In other implementations, some of the first HARQ process ID set and the second HARQ process ID set are the same, and others are different.

[0070] In some implementations, the base station 104 sends one or more MAC control elements (CEs) or DCIs to the UE 102 to change or update one or more HARQ process IDs in the first HARQ process ID set. In some implementations, the base station 104 sends one or more MAC CEs or DCIs to the UE 102 to change or update one or more HARQ process IDs in the second HARQ process ID set. In some alternative implementations, the base station 104 does not configure the first HARQ process ID set and the second HARQ process ID set in the DL configuration parameters. In some implementations, the base station 104 determines the first HARQ process ID set and the second HARQ process ID set for mTRP operation based on pre-configuration. In further implementations, the first HARQ process ID set and the second HARQ process ID set are specific, predetermined IDs (e.g., as specified in the 3GPP specification). In yet further implementations, the base station 104 determines the first HARQ process ID set and the second HARQ process ID set based on rules.

[0071] In some implementations, when the base station 104 determines to schedule the UE 102 to receive a DL transmission for the TRP 107-1, the base station 104 selects a HARQ process ID from the first set of HARQ process IDs, and sends a DCI including a DL assignment and the selected HARQ process ID to the UE 102. The UE 102 uses the HARQ process identified by the selected HARQ process ID, and uses the HARQ process and the UL grant to receive the DL transmission from the base station 104. Similarly, when the base station 104 determines to schedule the UE 102 to send a UL transmission to the TRP 107-2, the base station 104 selects a HARQ process ID from the second set of HARQ process IDs, and sends a DCI including a UL grant and the selected HARQ process ID to the UE 102. The UE 102 uses the HARQ process identified by the selected HARQ process ID, and uses the HARQ process and the DL assignment to receive the DL transmission from the base station 104.

[0072] In some implementations, the one or more capabilities include at least one first capability indicating that the UE 102 supports mTRP operation (e.g., a Release 16 capability field / IE and / or a Release 17 capability field / IE for mTRP operation in 3GPP specification 38.306 or 38.331 v17.1.0 or later). In some implementations, the base station 104 determines, based on the at least one first capability, DL configuration parameters configured for DL ​​communication with the base station 104 via the TRP 107-2. In some implementations, the base station 104 determines, based on the at least one first capability, UL configuration parameters for UL communication with the base station 104 via the TRP 107-2. In the case where the base station 104 includes the DU 174 and the CU 172, the DU 174 makes the determination.

[0073] In some implementations, the one or more capabilities include at least one second capability. In some such implementations, the at least one second capability indicates that the UE 102 supports multiple UL transmission timings for mTRP operation with the serving cell (i.e., operation of two or more TAs). In further implementations, the at least one second capability indicates that the UE 102 supports multiple UL transmission timings (for mTRP operation) with the serving cell and the non-serving cell. The physical cell index (PCI) of the non-serving cell is different from the PCI of the serving cell. In some implementations, the at least one second capability includes the number of UL transmission timings supported by the UE 102 with the serving cell (for mTRP operation) and / or across all serving cells configured / activated for the UE 102. In further implementations, the at least one second capability does not include the number of UL transmission timings (for mTRP operation) and indicates that the UE 102 supports a default number (e.g., 2) of UL transmission timings. In some implementations, the base station 104 determines the UL configuration parameters configured for UL communication with the base station 104 via TRP 107-2 based on the at least one second capability. Where the base station 104 includes a DU 174 and a CU 172, the DU 174 makes the determination.

[0074] In some implementations, the base station 104 receives one or more capabilities from the UE 102 after receiving the RRC setup complete message or performing a security activation procedure with the UE 102. In some implementations, the base station 104 sends a UE capability query message (e.g., a UECapabilityEnquiry message) to the UE 102, and in response, receives a UE capability information message (e.g., a UECapabilityInformation message) including one or more capabilities from the UE.

[0075] In other implementations, base station 104 receives a CN to BS message including one or more capabilities from CN 110 (e.g., after receiving the RRC setup complete message). In some implementations, base station 104 sends a BS to CN message to CN 110 after receiving the RRC setup complete message, and CN 110 sends a CN to BS message after receiving the BS to CN message (e.g., in response to receiving the BS to CN message). In some implementations, UE 102 sends a NAS message (e.g., a registration request message or a registration complete message) including a capability ID identifying one or more capabilities to CN 110, and CN 110 obtains the one or more capabilities from the capability ID. In other implementations, UE 102 performs a registration procedure with CN 110 via a base station (e.g., base station 104 or 106) prior to event 502 to register with CN 110. During the registration process, UE 102 receives a UE capability query message (e.g., UECapabilityEnquiry message) from the base station and sends a UE capability information message (e.g., UECapabilityInformation message) including one or more capabilities to the base station. The base station sends a BS to CN message including one or more capabilities to CN 110, and CN 110 stores the one or more capabilities. In some implementations, the CN to BS message and the BS to CN message are NG Application Protocol (NGAP) messages. In the case where the base station 104 includes a DU 174 and a CU 172, the CU 172 sends a CU to DU message including one or more capabilities to the DU 174. In some implementations, the CU to DU message is an F1 Application Protocol (F1AP) message.

[0076] In some implementations, the base station 104 may include the random access configuration parameters in the RRC reconfiguration message for the UE 102 to use in performing 598 the random access procedure. In some implementations, the random access configuration parameters are dedicated to the UE 102. For example, the base station 104 generates a RACH configuration (e.g., a RACH-ConfigDedicated, RACH-ConfigDedicated-r18, or RACH-ConfigDedicated-v1800 IE) that includes the random access configuration parameters dedicated to the UE 102. In some implementations, the format of the RRCReconfiguration message includes a ReconfigurationWithSync IE, and the ReconfigurationWithSync IE includes a RACH-ConfigDedicated IE (e.g., a RACH configuration or includes a random access configuration parameter) (e.g., as specified in 3GPP specification 38.331 v17.0.0 or later). In the case where the RRC reconfiguration message is an RRCReconfiguration message, the base station 104 includes the RACH configuration or random access configuration parameters of the RRCReconfiguration message in the RRCReconfiguration message, instead of including the ReconfigurationWithSync IE and wrapping the RACH configuration or random access configuration parameters in the ReconfigurationWithSync IE. If the base station 104 uses the ReconfigurationWithSync IE to include the random access configuration parameters, the ReconfigurationWithSync IE causes the UE 102 to perform a handover, which results in a communication interruption between the UE 102 and the base station 104. In other implementations, the base station 104 avoids including the random access configuration parameters in the RRC reconfiguration message.

[0077] In some implementations, the base station 104 indicates in the RRC reconfiguration message that UL synchronization is required (i.e., for communication with the base station 104 via the second TRP). That is, the base station 104 configures the UE 102 to obtain the (second) UL synchronization for communication between the UE 102 and the TRP 107-1, while maintaining the first UL synchronization for communication between the UE 102 and the TRP 107-2. In other words, the base station 104 configures the UE to maintain two TA values ​​for communication between the UE 102 and the base station 104 (e.g., between the UE 102 and the TRP 107-1 and between the UE 102 and the TRP 107-2, respectively). In a further implementation, the base station 104 includes a configuration (e.g., a field or IE (e.g., an RRC Release 18 field or IE)) indicating that UL synchronization is required for communication between the UE 102 and the TRP 107-2 in the RRC reconfiguration message. In other words, the configuration enables operation of two TA values ​​for communication between UE 102 and base station 104 (e.g., between UE 102 and TRP 107-1 and between UE 102 and TRP 107-2, respectively).

[0078] In some implementations, the UE 102 initiates a random access procedure 598 in response to receiving the field or IE before sending an UL transmission (e.g., a channel state information (CSI) report, a sounding reference signal (SRS), a PUCCH transmission, and / or a PUSCH transmission) to the base station via TRP 107-2. In some such implementations, if the RRC reconfiguration message does not include the field or IE, the UE 102 does not initiate a random access procedure and sends an UL transmission to the base station via TRP 107-2. In further implementations, the UE 102 avoids sending an UL transmission to the base station via TRP 107-2 in response to receiving the field or IE. In some such cases, the UE 102 does not send a random access preamble to the base station 104 via TRP 107-2 until a PDCCH order is received from the base station (e.g., events 558, 560, 559, 561).

[0079] Blocks 548, 550, 552, 554, and 556 are Figure 5A This is collectively referred to as the TRP configuration process 596A.

[0080] In some implementations, after receiving the RRC reconfiguration message at event 538, after performing the CSI resource configuration and CSI reporting process 594, or after performing the TRP configuration process 596A with the base station 104, the UE 102 receives 562, 564 RS from the base station 104 via TRP 107-2. Depending on the implementation, the RS is configured in the CSI resource configuration at event 538, and the events 562, 564 occur after receiving the RRC reconfiguration message at event 538, during or after the CSI configuration resource and CSI reporting process 594, or during or after the TRP configuration process 596A. After performing the TRP configuration process 596A with the base station 104, the UE 102 initiates 598 a random access procedure. In response to initiating the random access procedure, the UE 102 sends 566, 568 a second random access preamble to the base station 104 via TRP 107-2 on the time / frequency resources and random access channel (RACH) opportunity. In response to the second random access preamble, the base station 104 sends 570, 572 a second random access response to the UE 102 via the TRP 107-2. The base station 104 includes the second preamble ID and the second TA command in the second random access response. The second preamble ID identifies the second random access preamble, and the second TA command includes a second TA value. The UE applies the second TA value and determines or maintains 574 an uplink synchronized with the TRP 107-2 after applying the second TA value (e.g., in response to applying the second TA value). The UE 102 applies the second TA value to send UL transmissions (e.g., PUCCH transmissions, PUSCH transmissions, and / or SRS transmissions) until the UE 102 receives a new or different TA value that updates the second TA value from the base station 104. In some implementations, the UE 102 starts a second TAT after or upon receiving the second TA command to maintain or manage a UL synchronization state with the TRP 107-2 or the base station 104. In some implementations, the base station 104 includes a UL grant (e.g., a RAR grant) in the second random access response, and the UE 102 sends a UL MAC PDU to the base station 104 via the TRP 107-2 according to the UL grant. In the case where the random access procedure is a contention-based random access procedure, the UE 102 includes the C-RNTI of the UE 102 in the UL MAC PDU. The base station 104 identifies the UE 102 based on the C-RNTI. In response to the identification, the base station 104 generates a DCI and a CRC for the DCI, scrambles the CRC using the C-RNTI, and sends the DCI and the scrambled CRC to the UE 102 on the PDCCH. In some implementations, the DCI includes an n UL grant.Upon receiving the DCI and the scrambled CRC on the PDCCH, the UE 102 determines that the contention-based random access procedure 598 is successfully performed. In the case where the random access procedure 598 is a contention-free random access procedure, the UE 102 determines that the contention-based random access procedure 598 is successfully performed in response to receiving the second random access response message.

[0081] In some implementations, after sending the second TA command to the UE 102 (e.g., in response to sending the second TA command to the UE 102), the base station 104 starts a second TAT to maintain second UL synchronization for UL and / or DL ​​communications with the UE 102 via the TRP 107-2. In some implementations, the TRP 107-1 generates timing information for a second random access preamble received from the UE 102 and sends the timing information to the base station 104. As an example, the timing information indicates a propagation delay or a propagation delay offset. Based on the timing information received from the TRP 107-2, the base station 104 determines a second TA value.

[0082] Boxes 566, 568, 570, 572, and 574 are Figure 5A It is collectively referred to as the random access process 598.

[0083] In some implementations, the UE 102 suspends communication (e.g., reception of DL channels / RSs or transmission of UL channels / RSs) with the base station 104 via the TRP 107-1 while performing the random access procedure 598. Depending on the implementation, the UE 102 does so if it cannot simultaneously perform the random access procedure based on a UL beam or RS (i.e., toward a TRP) and communicate UL and DL transmissions based on another UL beam or RS (i.e., toward another TRP) (i.e., not related to the random access procedure). In other implementations, the UE 102 continues to communicate with the base station 104 via the TRP 107-2 while performing the random access procedure 598. After successfully completing 598 the random access procedure, the UE performs 576 DL and UL communications with the BS via the TRP 107-1 and the TRP 107-2 according to the first TA value and the second TA value, respectively.

[0084] In some implementations, the base station 104 and the UE 102 use a HARQ entity (e.g. Figure 4A , Figure 4B or Figure 4C ) to perform UL communication with base station 104 via TRP 107-1 and TRP 107-2 at event 576. In some cases (e.g., using Figure 4BIn some implementations, the UL configuration parameters of events 548 and 550 include HARQ configuration parameters. The HARQ configuration parameters configure a first HARQ process ID set and a second HARQ process ID set. In some cases, the first HARQ process ID set and the second HARQ process ID set are used for TRP 107-1 and TRP 107-2, respectively. The first HARQ process ID set and the second HARQ process ID set identify a first HARQ process set of a HARQ entity and a second HARQ process set of a HARQ entity, respectively. In some implementations, none of the first HARQ process ID set and the second HARQ process ID set are the same. In other implementations, some of the first HARQ process ID set and the second HARQ process ID set are the same, and others are different.

[0085] In some implementations, the base station 104 sends one or more MAC CEs or DCIs to the UE 102 to change or update one or more HARQ process IDs in the first HARQ process ID set. In some further implementations, the base station 104 sends one or more MAC CEs or DCIs to the UE 102 to change or update one or more HARQ process IDs in the second HARQ process ID set. In some alternative implementations, the base station 104 does not configure the first HARQ process ID set and the second HARQ process ID set in the UL configuration parameters. In some implementations, the base station 104 determines the first HARQ process ID set and the second HARQ process ID set for mTRP operation based on pre-configuration. In a further implementation, the first HARQ process ID set and the second HARQ process ID set are specified sets (e.g., as specified in the 3GPP specification). In a further implementation, the base station 104 determines the first HARQ process ID set and the second HARQ process ID set based on a rule.

[0086] In some implementations, when the base station 104 determines to schedule the UE 102 to send an UL transmission to the TRP 107-1, the base station 104 selects a HARQ process ID from the first set of HARQ process IDs, and sends a DCI including an UL grant and the selected HARQ process ID to the UE 102. The UE 102 uses the HARQ process identified by the selected HARQ process ID, and uses the HARQ process and the UL grant to send an UL transmission to the base station 104. Similarly, when the base station 104 determines to schedule the UE 102 to send an UL transmission to the TRP 107-2, the base station 104 selects a HARQ process ID from the second set of HARQ process IDs, and sends a DCI including an UL grant and the selected HARQ process ID to the UE 102. The UE 102 uses the HARQ process identified by the selected HARQ process ID, and uses the HARQ process and the UL grant to send an UL transmission to the base station 104.

[0087] In some implementations, after receiving the RRC reconfiguration complete message at event 554, the base station 104 sends 558, 560 a PDCCH command to the UE 102 via TRP 107-2 to cause the UE 102 to initiate a random access procedure 598 with the base station 104 via TRP 107-2. In some implementations, the PDCCH command includes an RS index and a random access preamble index. Alternatively, the base station 104 sends the PDCCH command to the UE 102 via TRP 107-1. In response to the PDCCH command, the UE 102 sends a random access preamble to the base station 104 via TRP 107-2 at event 566. In some implementations, the random access preamble index includes a value of a second preamble ID identifying a second random access preamble. Therefore, the UE 102 determines the second random access preamble according to the random access preamble index. In other implementations, the random access preamble index includes a value indicating or instructing the UE 102 to determine the random access preamble. Therefore, the UE 102 determines the second random access preamble by (randomly) selecting the second random access preamble from the random access preambles configured in the system information.

[0088] In some implementations, the PDCCH command is a DCI. The base station 104 generates a DCI and a CRC for the DCI, scrambles the CRC using the C-RNTI, and sends the DCI and the scrambled CRC to the TRP 107-2 (e.g., via an optical fiber connection). Then, the TRP 107-2 sends the DCI and the scrambled CRC to the UE 102 on the PDCCH. In some implementations, the base station 104 sends a first packet including the DCI and the scrambled CRC to the TRP 107-2. In some implementations, the base station 104 sends control information configuring or indicating time and / or frequency resources for the PDCCH to the TRP 107-2. In some implementations, the time and / or frequency resources include subcarriers, resource elements, or physical resource blocks. The TRP 107-2 sends the DCI and the scrambled CRC on the time and / or frequency resources according to the control information. In some implementations, the base station 104 includes the control information in the first packet. In other implementations, base station 104 sends a second packet including control information to TRP 107-2 instead of the first packet. In other implementations, base station 104 does not send control information for the DCI and the scrambled CRC to TRP 107-2. In such implementations, TRP 107-2 determines the time and / or frequency resources for the PDCCH and sends the DCI and the scrambled CRC on the time and / or frequency resources.

[0089] In some implementations, the RS index (e.g., SSB index) identifies one of the SSBs. In some such implementations, the base station 104 determines or decodes the SSB index indicated in the CSI report. In further implementations, the base station 104 determines or decodes the SSB index based on a radio resource (e.g., PUCCH resource) at which the base station 104 receives one of the CSI reports for the SSB. In some such implementations, the base station 104 configures different radio resources for the UE 102 to send a CSI report for each of the SSBs. In some examples, the base station 104 includes a configuration of configuring different radio resources (e.g., PUCCH resources) for the UE 102 to send a CSI report for each of the SSBs in the RRC reconfiguration message of event 536. In some implementations, UE 102 determines the time / frequency resources and / or RACH timing based on the SSB (e.g., indicated in the RS index) and the random access configuration parameters received in the system information, and sends the second random access preamble on the time / frequency resources and / or RACH timing. In other implementations, UE 102 determines the time / frequency resources and / or RACH timing based on the SSB (e.g., indicated in the RS index) and the random access configuration parameters received in the RRC reconfiguration message of event 550, and sends the second random access preamble on the time / frequency resources and / or RACH timing.

[0090] In other implementations, the RS index (e.g., CSI-RS index) identifies one of the CSI-RSs. In some implementations, the base station 104 determines or decodes the CSI-RS index indicated in the CSI report. In further implementations, the base station 104 determines or decodes the CSI-RS index based on the radio resources (e.g., PUCCH resources) where the base station 104 receives the CSI report for the CSI-RS. In some such implementations, the base station 104 configures different radio resources for the UE 102 to send a CSI report for each of the CSI-RSs. In some examples, the base station 104 includes a configuration of configuring different radio resources (e.g., PUCCH resources) for the UE 102 to send a CSI report for each of the CSI-RSs in the RRC reconfiguration message of event 536. In some implementations, UE 102 determines the time / frequency resources and / or RACH opportunities based on the CSI-RS (e.g., indicated in the RS index) and random access configuration parameters in the RRC reconfiguration message received by UE 102 at event 550. UE 102 sends the second random access preamble on the time / frequency resources and / or RACH opportunities. In some implementations, the random access configuration parameters indicate one or more associations between the CSI-RS and the RACH opportunities and / or the time / frequency resources.

[0091] In some implementations, UE 102 determines a transmission characteristic (e.g., a spatial transmission filter / parameter) based on or by reference to an RS index in a PDCCH order, and sends a second random access preamble to TRP 107-2 using the determined transmission characteristic. In some examples, UE 102 uses a reception characteristic for receiving 564 an RS identified by an RS index to derive the transmission characteristic. In some implementations, the transmission characteristic includes a phase, a power, and / or a transmission precoder. In some implementations, UE 102 further uses DL and / or UL configuration parameters of event 550 to determine the transmission characteristic. In further implementations, UE 102 uses configuration parameters in system information of event 510 to determine the transmission characteristic. In some implementations, UE 102 does not determine the transmission characteristic (e.g., a spatial transmission filter / parameter) based on or by reference to an RS index in a PDCCH order, and sends a second random access preamble to TRP 107-2 using the determined transmission characteristic.

[0092] In some implementations, UE 102 initiates 598 a random access procedure in response to receiving the random access configuration parameters at event 550 and after receiving the RS at event 564. In such implementations, base station 104 does not send a PDCCH order to cause UE 102 to perform random access procedure 598.

[0093] In some implementations, the RRC reconfiguration message of event 550 includes configuration parameters (e.g., for PDCCH configuration, search space configuration, and / or control resource set (CORESET) configuration) for UE 102 to receive DL transmissions from TRP 107-2. In some implementations, UE 102 receives a second random access response according to the configuration parameters. In other implementations, the system information of event 510 includes configuration parameters for UE 102 to receive a random access response from TRP 107-2. In such implementations, UE 102 receives a second random access response according to the configuration parameters. In some implementations, UE 102 receives a second random access response from TRP 107-2 using the reception characteristics for receiving 564 RS.

[0094] Although TRP 107-2 is used in scenario 500A, the above description can be applied to a scenario where TRP 107-3 is used instead of TRP 107-2. In this scenario, after successfully completing the random access procedure with the base station via TRP 107-3 and cell 125, similar to process 598, the UE performs DL and UL communications with the base station via TRP 107-1 and TRP 107-3 according to the first TA value and the second TA value, respectively.

[0095] In some scenarios or implementations, the base station 104 sends a third TA command including a first new TA value to update the first TA value to the UE 102 via the TRP 107-1 or the TRP 107-2. In some implementations, the third TA command is a MAC control element (CE). The UE 102 applies the first new TA value to the first UL synchronization and restarts the first TAT of the UE 102 in response to receiving the third TA command. The base station 104 restarts the first TAT of the base station 104 in response to sending the third TA command. In some scenarios or implementations, the base station 104 sends a fourth TA command including a second new TA value to update the second TA value to the UE 102 via the TRP 107-1 or the TRP 107-2. In some implementations, the fourth TA command is a MAC CE. The UE 102 applies the second new TA value to the second UL synchronization and restarts the second TAT in response to receiving the fourth TA command. In some scenarios or implementations, the base station 104 sends a single TA command including a first new TA value and a second new TA value to update the first TA value and the second TA value, respectively, to the UE 102 via the TRP 107-1 or the TRP 107-2. In some implementations, the single TA command is a new or existing MAC control element (CE) (e.g., as defined in 3GPP specification 38.321 V17.1.0).

[0096] In some implementations, TRP 107-1 generates timing information based on UL transmissions received from UE 102, and sends the timing information to base station 104. In some examples, the timing information indicates a propagation delay or a propagation delay offset. Based on the timing information received from TRP 107-1, base station 104 determines whether to update the first TA value. In some implementations, if the propagation delay or the propagation delay offset is greater than or equal to a first threshold, base station 104 determines to update the first TA value. Otherwise, if the propagation delay or the propagation delay offset is less than a second threshold, base station 104 determines not to update the first TA value. In some implementations, if base station 104 determines to update the first TA value, base station 104 generates a first new TA value. In some implementations, TRP 107-2 generates timing information based on UL transmissions received from UE 102, and sends the timing information to base station 104. In some examples, the timing information indicates a propagation delay or a propagation delay offset. Based on the timing information received from TRP 107-2, base station 104 determines whether to update the second TA value. In some implementations, if the propagation delay or the propagation delay offset is greater than or equal to the third threshold, the base station 104 determines to update the second TA value. Otherwise, if the propagation delay or the propagation delay offset is less than the fourth threshold, the base station 104 determines not to update the first TA value. In some implementations, if the base station 104 determines to update the second TA value, the base station 104 generates a second new TA value. Depending on the implementation, the first, second, third, and fourth thresholds are the same or different.

[0097] Go to Figure 5B, scenario 500B is similar to scenario 500A, and the differences are described below. In scenario 500B, the base station 104 sends 549, 551 an RRC reconfiguration message to the UE 102 via TRP 107-1, and the RRC reconfiguration message includes DL configuration parameters for DL ​​communication with the base station 104 via TRP 107-2. In some implementations, the base station 104 includes UL configuration parameters for UL communication with the base station 104 via TRP 107-1 in the RRC reconfiguration message (e.g., to configure or enable DL communication with the base station 104 via TRP 107-2). In some implementations, the base station 104 includes the DL configuration parameters in a CellGroupConfig IE and includes the CellGroupConfig IE in the RRC reconfiguration message. In some implementations, the base station 104 includes the DL configuration parameters in a BWP-DownlinkDedicated IE and includes the BWP-DownlinkDedicated IE in the RRC reconfiguration message. The RRC reconfiguration message of events 549, 551 is similar to the RRC reconfiguration message of events 548, 550, except that the base station 104 excludes or avoids including UL configuration parameters for UL communication with the base station 104 via TRP 107-2 in the RRC reconfiguration message of events 549, 551. Instead, the base station 104 sends 578, 580 another RRC reconfiguration message to the UE 102 via TRP 107-1, which includes UL configuration parameters for UL communication with the base station 104 via TRP 107-2. In response, the UE 102 sends 582, 584 an RRC reconfiguration complete message to the base station 104 via TRP 107-1. In some implementations, the base station 104 includes the UL configuration parameters in the CellGroupConfig IE and includes the CellGroupConfig IE in the RRC reconfiguration messages of events 578, 580. In some implementations, the base station 104 includes the UL configuration parameters in a BWP-UplinkDedicated IE, and includes the BWP-UplinkDedicated IE in the RRC reconfiguration message.

[0098] Boxes 549, 551, 552, 554, 556, 578, 580, 582, and 584 are Figure 5B596B. After receiving the RRC reconfiguration message at event 538, after performing the CSI resource configuration and CSI reporting process 594, or after performing the TRP configuration process 596B with the base station 104, the UE 102 receives 562, 564 RS from the base station 104 via TRP 107-2. After performing the TRP configuration process 596A with the base station 104, the UE 102 performs 598 a random access process with the base station 104 via TRP 107-2.

[0099] Next reference Figure 5C , scenario 500C is similar to scenarios 500A and 500B, and the differences are described below.

[0100] After sending 549, 550 the RRC reconfiguration message or receiving 552, 554 the RRC reconfiguration complete message, the base station 104 sends 579, 581 another RRC reconfiguration message to the UE 102 via TRP 107-2, the other RRC reconfiguration message including UL configuration parameters for UL communication with the base station 104 via TRP 107-2. The RRC reconfiguration messages of events 579, 581 are similar to the RRC reconfiguration messages of events 578, 580, except that the base station 104 sends 579, 581 the RRC reconfiguration to the UE 102 via TRP 107-2 instead of TRP 107-1.

[0101] Boxes 549, 551, 552, 554, 556, 579, 581, 582, and 584 are Figure 5C It is collectively referred to as TRP configuration process 596C.

[0102] Next reference Figure 5D , scenario 500D is similar to scenarios 500A, 500B, and 500C, and the differences are described below.

[0103] After UE 102 performs a TRP configuration procedure 596A, 596B, or 596C with base station 104, UE 102 initiates 599 a random access procedure. In response to the initiation, UE 102 sends 566, 568 a second random access preamble to base station 104 via TRP 107-2. In response, base station 104 sends 571, 573 a second random access response to UE 102 via TRP 107-1 instead of TRP 107-2.

[0104] Next reference Figure 5E , scenario 500E is similar to scenarios 500A, 500B, 500C, and 500D, and the differences are described below.

[0105] In some implementations, after receiving the RRC reconfiguration complete message at event 554, base station 104 sends 559, 561 PDCCH commands to UE 102 via TRP 107-1 to enable UE 102 to initiate a random access process 598 or 599 with base station 104 via TRP 107-2, which is similar to events 558, 560.

[0106] Figures 6 to 12 is a flowchart depicting an example method that a UE (e.g., UE 102) can implement to enable multiple TA value operations in a multi-TRP scenario. Figures 6 to 12 Depicting some methods for a UE to determine which TA value to apply for sending an UL transmission. The first TRP and the second TRP described below may be, for example, TRP 107-1 and TRP 107-2. In another example, the first TRP and the second TRP described below may be TRP 107-1 and TRP 107-3.

[0107] Some general descriptions are given below, which may be applicable to the following flow charts and / or embodiments.

[0108] In some implementations, the UE performs DL reception from a first TRP (e.g., one of TRP 107-1, TRP 107-2, TRP 107-3, TRP 108-1, and / or TRP 108-2) and / or UL transmission to the first TRP. In some such implementations, the UE performs DL reception from a second TRP (e.g., one of TRP 107-1, TRP 107-2, TRP 107-3, TRP 108-1, and / or TRP 108-2) and / or UL transmission to the second TRP. In some implementations, the first TRP is located in a serving cell. In further implementations, the second TRP is located in a serving cell. Alternatively, the second TRP is located in a neighboring cell. In some implementations, the second TRP is located in a neighboring cell or a non-serving cell, wherein the neighboring cell or non-serving cell is a cell having a PCI different from the PCI of the serving cell.

[0109] In some implementations, the UE includes or is equipped with one or more panels. In some implementations, some or all of the one or more panels are used and / or activated for DL ​​reception (e.g., performed at the same time or at the same time interval). In further implementations, some or all of the one or more panels are used and / or activated for UL transmission (e.g., performed at the same time or at the same time interval). In some implementations, the set of panels used and / or activated for DL ​​reception is at least partially the same as the set of panels used and / or activated for UL transmission. In further implementations, the set of panels used and / or activated for DL ​​reception is at least partially different from the set of panels used and / or activated for UL transmission.

[0110] In some implementations, each TRP (e.g., TRP 107-1, TRP 107-2, TRP 107-3, TRP 108-1, and / or TRP 108-2) is associated with or identified by a TRP identifier. In some implementations, a base station (e.g., base station 104 or 106) includes the TRP identifier in a UL configuration, which the base station sends to a UE (e.g., UE 102) for UL transmission via the TRP identified by the TRP identifier. In some implementations, the UL configuration includes a DCI sent on a PDCCH, and / or a PUSCH configuration, a PUCCH configuration, and / or an SRS configuration included in an RRC message (e.g., an RRC reconfiguration message or an RRC recovery message) sent by the base station to the UE. In some implementations, the UL transmission includes a PUSCH transmission, a PUCCH transmission, and / or an SRS transmission. In some implementations, the base station includes the TRP identifier in a DL configuration that the base station sends to the UE 102 for DL ​​transmission via the TRP identified by the TRP identifier. In some implementations, the DL configuration includes DCI sent on the PDCCH, and / or a CSI resource configuration, a PDSCH configuration, and / or a PDCCH configuration included in an RRC message (e.g., an RRC reconfiguration message or an RRC recovery message) sent by the base station to the UE. In some implementations, the DL transmission includes a CSI-RS transmission, an SSB transmission, a PDSCH transmission, and / or a PDCCH transmission.

[0111] In other implementations, the base station does not send a TRP identifier to the UE and uses an implicit indication to indicate the TRP to the UE. In some implementations, the implicit indication is one of the following configuration parameters: CORESETPoolIndex, a value or value candidate for CORESETPoolIndex, dataScramblingIdentityPDSCH, dataScramblingIdentityPDSCH2-r16, or PUCCH-ResourceGroup-r16. In such implementations, the UE derives the TRP (identifier) ​​from the implicit indication. In some implementations, the base station sends an RRC message (e.g., an RRC reconfiguration message or an RRC recovery message) including the configuration parameters to the UE.

[0112] In some implementations, the base station configures or indicates a first TRP identifier to the UE. In some implementations, the UE derives the first TRP identifier and / or identifier value. In some implementations, the base station configures or indicates a second TRP identifier and / or identifier value to the UE. In some implementations, the UE derives the second TRP identifier and / or identifier value.

[0113] In some cases, the UE maintains multiple TA values. In some such implementations, the UE maintains multiple TA values, wherein all TA values ​​in the multiple TA values ​​are indicated or signaled to the UE. In further such implementations, the UE maintains multiple TA values, wherein all TA values ​​in the multiple TA values ​​are derived by the UE. In some implementations, the UE maintains multiple TA values, wherein at least one TA value in some of the TA values ​​is indicated or signaled to the UE, and at least one TA value in the remaining TA values ​​is derived by the UE. In further implementations, the UE maintains or operates multiple TA values ​​in a serving cell. In some implementations, the base station indicates or configures the UE corresponding IDs for multiple TA values. In some implementations, the UE derives corresponding IDs for multiple TA values. In some such implementations, each TA value in the multiple TA values ​​has a separate ID. In some such cases, the UE maintains multiple TA values ​​for a serving cell or in a serving cell.

[0114] In some cases, the base station configures or activates a first serving cell set for the UE. In some cases, the base station configures or activates a second serving cell set for the UE. In some implementations, the first serving cell set has the same serving cell elements as the second serving cell set. In some implementations, the first serving cell set has serving cell elements that are different from those of the second serving cell set.

[0115] In some cases, the base station configures or activates a third serving cell set for the UE. In some implementations, the third serving cell set includes at least the first serving cell set. In a further implementation, the third serving cell set includes at least the second serving cell set. In some implementations, the third serving cell set includes at least the first serving cell set and the second serving cell set. In some implementations, the third serving cell set is the union of the first serving cell set and the second serving cell set. In some implementations, the third serving cell set is the intersection of the first serving cell set and the second serving cell set.

[0116] In some cases, the UE may maintain a first TA value among multiple TA values. In some cases, the UE may maintain a second TA value among multiple TA values. In some implementations, the first TA value may be associated with a first TRP. In some implementations, the second TA value may be associated with a second TRP.

[0117] Depending on the implementation, the first TA value: (i) is applied to or is associated with a first set of service cells, (ii) is applied to or is associated with a first TRP, (iii) is applied to or is associated with a UL channel / RS transmission sent to the first TRP, and / or (iv) is applied to or is associated with a UL channel / RS transmission associated with a first TRP identifier and / or identifier value.

[0118] Depending on the implementation, the second TA value: (i) is applied to or is associated with a second set of service cells, (ii) is applied to or is associated with a second TRP, (iii) is applied to or is associated with a UL channel / RS transmission sent to the second TRP, and / or (iv) is applied to or is associated with a UL channel / RS transmission associated with a second TRP identifier and / or identifier value.

[0119] In some cases, the base station indicates or configures an ID of a first TA value for the UE. In some cases, the UE derives an ID of the first TA value. In some cases, the base station indicates or configures an ID of a second TA value for the UE. In some cases, the UE derives an ID of the second TA value.

[0120] In some cases, the base station configures or indicates one or more TA groups for the UE. In some implementations, a TA group (TAG) includes or is associated with one or more serving cells and / or indices. In some implementations, each serving cell included in or associated with the same TAG uses one or more TA values ​​or operates with one or more TA values. In some implementations, a TAG includes or is associated with one or more TA values. In some implementations, the corresponding IDs of one or more TA groups are indicated or configured to the UE, or the UE derives the corresponding IDs of one or more TA groups. In some such implementations, each TAG has a separate ID.

[0121] In some cases, the base station configures or indicates the first TAG for the UE. In some implementations, the first TAG is among one or more TA groups. In some implementations, the first TA value or the ID of the first TA value is associated with the first TAG or is included in the first TAG.

[0122] In some cases, the base station configures or indicates the second TAG for the UE. In some implementations, the second TAG is among one or more TA groups. In some implementations, the second TA value or the ID of the second TA value is associated with the second TAG or is included in the second TAG.

[0123] In some cases, the first TA value and the second TA value are associated with or included in the same TAG.

[0124] In some implementations, the first TAG is associated with a first TRP or a first TRP identifier and / or an identifier value. In some implementations, the first TAG includes or is associated with a first set of service cells. In some implementations, the first set of service cells is configured with or is associated with a first TRP or a first TRP identifier and / or an identifier value. In some implementations, in each service cell in the first set of service cells, at least one CORESET is configured with or is associated with CORESETPoolIndex #0.

[0125] In some implementations, the first TAG includes or is associated with one or more TA values, wherein the one or more TA values: (i) are applied to or are associated with a first set of service cells, (ii) are applied to or are associated with a first TRP, (iii) are applied to or are associated with a UL channel / RS transmission associated with the first TRP or a first TRP identifier and / or identifier value, and / or (iv) are applied to or are associated with a third set of service cells.

[0126] In some implementations, the second TAG is associated with a second TRP or a second TRP identifier and / or an identifier value. In some implementations, the second TAG includes a second set of service cells or is associated with a second set of service cells. In some implementations, the second set of service cells is configured with a second TRP or a second TRP identifier and / or an identifier value or is associated with a second TRP or a second TRP identifier and / or an identifier value. In some implementations, in each service cell in the second set of service cells, at least one CORESET is configured with or is associated with CORESETPoolIndex #1.

[0127] In some implementations, the second TAG includes or is associated with one or more TA values, wherein the one or more TA values: (i) are applied to or are associated with a second set of service cells, (ii) are applied to or are associated with a second TRP, (iii) are applied to or are associated with a UL channel / RS transmission associated with the second TRP or a second TRP identifier and / or identifier value, and / or (iv) are applied to or are associated with a third set of service cells.

[0128] In some cases, the base station indicates or configures the ID of the first TAG for the UE. In some cases, the UE obtains the ID of the first TAG. In some cases, the BS indicates or configures the ID of the second TAG for the UE. In some cases, the UE obtains the ID of the second TAG.

[0129] In some cases, the base station indicates or configures the third TAG for the UE. In some implementations, the third TAG is among one or more TA groups. In some implementations, the ID of the third TAG is indicated or configured to the UE, or the UE can derive the ID of the third TAG.

[0130] In some implementations, the third TAG is associated with the first TRP or the first TRP identifier and / or identifier value. In some implementations, the third TAG is associated with the second TRP or the second TRP identifier and / or identifier value. In some implementations, the third TAG includes or is associated with the third service cell set.

[0131] In some implementations, the third TAG includes or is associated with one or more TA values. In some implementations, the third TAG includes or is associated with one or more TA values, wherein the one or more TA values ​​include the first TA value and / or the second TA value.

[0132] In some implementations, if the base station indicates or configures a third TAG for the UE, the UE determines that at least one of the following is expected: (i) all service cells included in or associated with the third TAG are configured with a multi-TRP (M-TRP) mode by the base station (for example, the M-TRP mode is a single DCI (S-DCI) M-TRP mode or a multi-DCI (M-DCI) M-TRP mode), (ii) all service cells included in or associated with the third TAG are configured with a CORESETPoolIndex by the base station, and / or (iii) all service cells included in or associated with the third TAG are configured with a first TRP identifier and / or identifier value and a second TRP identifier and / or identifier value by the base station or are associated with a first TRP identifier and / or identifier value and a second TRP identifier and / or identifier value.

[0133] In some implementations, if the base station configures a third TAG for the UE, the base station performs one or some of the following: (i) configuring an M-TRP mode (for example, the M-TRP mode is an S-DCI M-TRP mode or an M-DCI M-TRP mode) for all service cells included in or associated with the third TAG, (ii) configuring CORESETPoolIndex for all service cells included in or associated with the third TAG, and / or (iii) configuring a first TRP identifier and / or identifier value and a second TRP identifier and / or value for all service cells included in or associated with the third TAG or associating all service cell configurations included in or associated with the third TAG with the first TRP identifier and / or identifier value and the second TRP identifier and / or value.

[0134] In some cases, the base station configures or indicates one or more primary TAGs (PTAGs) for the UE. In some implementations, the base station configures or indicates two PTAGs for the UE. In some cases, the base station configures or indicates one or more secondary TAGs (STAGs) for the UE.

[0135] In some cases, the first TAG is a PTAG. In some implementations, the first serving cell set includes a primary cell (PCell) or a primary secondary cell (PSCell). In some implementations, the first TAG is a STAG. In some implementations, the first serving cell set does not include a PCell or a PSCell.

[0136] In some cases, the second TAG is a PTAG. In some implementations, the second serving cell set includes a PCell or a PSCell. In some implementations, the second TAG is a STAG. In some implementations, the second serving cell set does not include a PCell or a PSCell.

[0137] In some cases, the third TAG is a PTAG. In some implementations, the third serving cell set includes a PCell or a PSCell. In some implementations, the third TAG is a STAG. In some implementations, the third serving cell set does not include a PCell or a PSCell.

[0138] In some cases, the base station configures or indicates one or more time alignment timers (TATs) for the UE. In some implementations, one or more TATs are configured for the active BWP or configured or indicated in the serving cell. In some implementations, the base station configures or indicates a first TAT in the active BWP or the serving cell for the UE. In some implementations, the base station configures or indicates a second TAT in the active BWP or the serving cell for the UE. In some implementations, the UE maintains the first TAT. In some implementations, the UE maintains the second TAT. In some implementations, the base station similarly maintains the first TAT and / or the second TAT.

[0139] In some implementations, the first TAT is associated with a first TAG. In further implementations, the first TAT is associated with or applied to a first serving cell set. In some implementations, the second TAT is associated with a second TAG. In further implementations, the second TAT is associated with or applied to a second serving cell set.

[0140] In some implementations, the base station indicates or configures the ID of the first TAT for the UE. In further implementations, the UE derives the ID of the first TAT. In some implementations, the base station configures or indicates the ID of the second TAT for the UE. In further implementations, the UE derives the ID of the second TAT.

[0141] In some cases, the base station configures or indicates a third TAT in an active BWP or serving cell for the UE. In some implementations, the third TAT is associated with or applied to a third serving cell set. In some implementations, the UE maintains the third TAT. In some implementations, the base station similarly maintains the third TAT. In some implementations, the base station configures or indicates an ID of the third TAT for the UE. In further implementations, the UE derives the ID of the third TAT.

[0142] In some cases, the first TA value and the second TA value belong to the same TAG (e.g., a third TAG) or are associated with the same TAG. In some implementations, the ID of the first TA value and the ID of the second TA value are included in the same TAG (e.g., a third TAG). In some cases, the first TA value and the second TA value belong to different TAGs (e.g., a first TAG and a second TAG) or are associated with the different TAGs. In some implementations, the ID of the first TA value and the ID of the second TA value are included in different TAGs (e.g., a first TAG and a second TAG).

[0143] In some cases, whether the first TA value expires and whether the second TA value expires are controlled by or associated with the same TAT (e.g., a third TAT). In further cases, whether the first TA value expires and whether the second TA value expires are controlled by or associated with different TATs (e.g., a first TAT and a second TAT).

[0144] In some cases, whether the first TAG is uplink time aligned and whether the second TAG is uplink time aligned are controlled by the same TAT (e.g., a third TAT) or are associated with the same TAT. In further cases, whether the first TAG is uplink time aligned and whether the second TAG is uplink time aligned are controlled by different TATs (e.g., a first TAT and a second TAT) or are associated with the different TATs.

[0145] In some cases, whether the first serving cell set is uplink time aligned and whether the second serving cell set is uplink time aligned are controlled by the same TAT (e.g., a third TAT) or are associated with the same TAT. In further cases, whether the first serving cell set is uplink time aligned and whether the second serving cell set is uplink time aligned are controlled by different TATs (e.g., a first TAT and a second TAT) or are associated with the different TATs.

[0146] In some cases, the base station configures or instructs the UE to send an UL transmission. In some implementations, the UL transmission is associated with a TA value and / or a TAG. In further implementations, the UL transmission is applied to or associated with a first TA value or a second TA value. In some implementations, the base station indicates to the UE which TA value is associated with or applied to the UL transmission. In some implementations, the UE derives which TA value is associated with or applied to the UL transmission.

[0147] In some implementations, the UL transmission is one of: (i) PUCCH resources; (ii) SRS resources, such as: (a) SRS resources for UL CB transmission, (b) SRS resources for UL NCB transmission, (c) SRS resources for BM, (d) SRS resources for antenna switching, (e) SRS resources for carrier switching, and / or (f) SRS resources for positioning; and / or (iii) PUSCH, such as: (a) configured UL grant and / or (b) dynamically scheduled PUSCH resources.

[0148] In some implementations, the time domain behavior of the UL transmission is one of: (i) periodic, (ii) semi-persistent, and / or (iii) aperiodic.

[0149] In some implementations, the base station configures a first TAG and a second TAG for the UE for UL transmission to the first TRP and the second TRP, respectively. In some implementations, the base station sends a first RRC message and a second RRC message to the UE including a first TAG configuration and a second TAG configuration for configuring the first TAG and the second TAG, respectively. In some implementations, the first TAG configuration and the second TAG configuration include a first TAG ID and a second TAG ID for identifying the first TAG and the second TAG, respectively. In some implementations, the first TAG configuration and the second TAG configuration include a timer value of / for the first TAT and a timer value of / for the second TAT for the first TAG and the second TAT, respectively. In some implementations, the first RRC message and the second RRC message are the same RRC message (e.g., the same instance) or different RRC messages (e.g., different instances or different types of RRC messages). In some implementations, the first RRC message and the second RRC message are RRC setup, RRC reconfiguration and / or RRC recovery messages. The UE associates the first TA value and the second TA value with the first TAG and the second TAG, respectively. In some implementations, the first TAG is associated with a first TRP or a first TRP identifier and / or an identifier value. In some implementations, the first TAG is associated with a specific service cell operated by the first TRP and configured for the UE. In some implementations, the first TAG is associated with an additional service cell operated by the first TRP and configured for the UE. In some implementations, the base station indicates or configures the association in the first RRC message. In some implementations, the second TAG is associated with a second TRP or a second TRP identifier and / or an identifier value. In some implementations, the second TAG is associated with a specific service cell or a non-service cell, and the base station indicates or configures the association in the second RRC message.

[0150] In other implementations, the base station configures a single TAG (e.g., a third TAG) for the UE for UL transmission to the first TRP and the second TRP. In some implementations, the base station sends a first RRC message (e.g., an RRC setup, an RRC reconfiguration, and / or an RRC recovery message) to the UE, the first RRC message including a single TAG configuration for configuring the TAG. In some implementations, the TAG configuration includes a single TAG ID for identifying the TAG. In some implementations, the TAG configuration includes a timer value for / for the first TAT and a timer value for / for the second TAT. In a further implementation, the TAG configuration includes a timer value for / for the first TAT, and the base station sends a second RRC message (e.g., an RRC setup, an RRC reconfiguration, and / or an RRC recovery message) including a timer value for the second TAT. The UE associates the first TA value and the second TA value with the TAG. In some implementations, the TAG is associated with (i) a first TRP or a first TRP identifier and / or an identifier value and (ii) a second TRP or a second TRP identifier. In some implementations, the TAG is associated with a specific service cell operated by the first TRP and configured for the UE. In some implementations, the TAG is associated with an additional service cell operated by the first TRP and configured for the UE. In some implementations, the base station indicates or configures the association in a first RRC message. In some implementations, the TAG is associated with a second TRP or a second TRP identifier and / or an identifier value. In some implementations, the TAG is associated with a specific service cell or a non-service cell, and the base station indicates or configures the association in a second RRC message.

[0151] In some implementations, the base station configures a specific service cell to be associated with a first TRP or a first TRP identifier and / or identifier value. In some implementations, the base station configures a first control resource set (CORESET) associated with a specific service cell or a first TRP. In a further implementation, the base station configures CORESETPoolIndex #0 to identify the first CORESET. In some implementations, the base station sends a third RRC message (e.g., an RRC setup message, an RRC reconfiguration message, or an RRC recovery message) to the UE, which configures the first CORESET and / or includes CORESETPoolIndex #0. Therefore, the UE monitors the PDCCH on the first CORESET to receive DCI from the base station, which means that the UE monitors the PDCCH or receives DCI from the base station (i.e., from the first TRP) via the first TRP. In some such cases, the UE determines that CORESETPoolIndex #0 indicates a specific TRP (i.e., the first TRP) of the base station.

[0152] In some implementations, the base station configures a specific serving cell to be associated with the second TRP or the second TRP identifier and / or identifier value. In other implementations, the second TAG is associated with a non-serving cell, and the base station indicates or configures the association in a second RRC message. In some implementations, the base station configures a non-serving cell associated with the second TRP or the second TRP identifier and / or identifier value. In some implementations, the base station configures a second CORESET to be associated with a specific serving cell, a non-serving cell, or a second TRP. In a further implementation, the base station configures CORESETPoolIndex#1 to identify the second CORESET. In some implementations, the base station sends a third RRC message (e.g., an RRC setup message, an RRC reconfiguration message, or an RRC recovery message) to the UE, which configures the second CORESET and / or includes CORESETPoolIndex #1. Therefore, the UE monitors the PDCCH on the second CORESET to receive DCI from the base station, which means that the UE monitors the PDCCH or receives DCI from the base station (i.e., from the second TRP) via the second TRP. In some such implementations, the UE determines that CORESETPoolIndex #1 indicates a specific TRP (i.e., the second TRP).

[0153] In some implementations, in addition to the TAG ID described above, the base station also configures a first ID for the UE to identify the first TA value. In some implementations, the base station includes the first ID in the RRC message described above. In a further implementation, the base station includes the first ID in the first TA command. In other implementations, the UE derives or determines the first ID and associates the first ID with the first TA value. Similarly, in addition to the TAG ID described above, the base station also configures a second ID for the UE to identify the second TA value. In some implementations, the base station includes the second ID in the RRC message described above. In a further implementation, the base station includes the second ID in the second TA command. In other implementations, the UE derives or determines the second ID and associates the second ID with the second TA value.

[0154] More generally, in some implementations, the base station configures or indicates to the UE a first index for or associated with the first TRP. In some implementations, the UE derives or determines the first index. In some implementations, the first index is one of: (i) a first TRP identifier and / or identifier value, (ii) an ID of a first TAG, (iii) an ID of a first TA value, and / or (iv) an ID of a first TAT.

[0155] More generally, in further implementations, the base station configures or indicates to the UE a second index for or associated with a second TRP. In some implementations, the UE derives the second index. In some implementations, the second index is one of: (i) a second TRP identifier and / or identifier value, (ii) an ID of a second TAG, (iii) an ID of a second TA value, and / or (iv) an ID of a second TAT.

[0156] First go to Figure 6 , a UE (eg, UE 102) implements the example method 600 to determine which TA value (eg, between a first TA value and a second TA value) to apply when sending an UL transmission.

[0157] Method 600 begins at block 602, where a UE performs DL and / or UL communications with a base station (e.g., events 504, 506, 508, 510, 512, 514, 516, 518, 590, 522, 524, 526, 528, 532, 534, 592, 536, 538, 540, 542, 544, 546, 594, 549, 551, 552, 554, 556, 562, 564). At block 604, the UE receives a configuration from the base station that enables two timing advance values ​​(e.g., events 548, 550, 596A, 578, 580, 596B, 579, 581, 596C). At block 606, the UE receives a first TA value and a second TA value from a base station (e.g., events 516, 518, 570, 571, 572, 573, 590, 598, 599). At block 608, the UE determines to send an UL transmission (e.g., a PUSCH transmission, a PUCCH transmission, or an SRS). At block 610, the UE determines whether the UL transmission is associated with the first TA value or the second TA value. If the UE determines that the UL transmission is associated with the first TA value, the flow proceeds to block 622. At block 622, the UE sends the UL transmission to the base station using the first TA value (e.g., events 520, 590). If the UE determines that the UL transmission is associated with the second TA value, the flow proceeds to block 626. At block 626, the UE sends the UL transmission to the base station using the second TA value (e.g., events 574, 598, 599).

[0158] A more detailed description of elements of method 600 is described herein, particularly with respect to the general description above. For example, in some implementations: (i) the first TA value and the second TA value shown at block 606 are described in the description of the first TA value and the second TA value described in the general description above and / or (ii) the UL transmission shown at block 608 is described in the description of the UL transmission described in the general description above.

[0159] Next go to Figure 7 , a UE (eg, UE 102) implements example method 700 to determine which TA value (eg, the first TA value or the second TA value) to apply when sending an UL transmission.

[0160] Method 700 starts at block 702. Blocks 702, 704, 706, 722, and 726 are similar to blocks 602, 604, 606, 622, and 626. At block 707, the UE receives a first index and a second index from a base station. At block 708, the UE receives a configuration of an UL transmission (e.g., a PUSCH transmission, a PUCCH transmission, or an SRS) from the base station (e.g., events 506, 518, 528, 538, 550, 551, 564, 580, 581). At block 709, the UE determines to send an UL transmission. At block 710, the UE determines whether the configuration of the UL transmission includes the first index or the second index. If the UE determines that the configuration of the UL transmission includes the first index, the process proceeds to block 720. At block 720, the UE determines or derives that the UL transmission is associated with a first TA value. If the UE determines that the configuration of the UL transmission includes the second index, the process proceeds to block 724. At block 724, the UE determines or derives that the UL transmission is associated with the second TA value.

[0161] Similar to method 600 , a more detailed description of the elements of method 700 are generally detailed above.

[0162] In some cases, the UE determines that (a) the UL transmission is sent by applying a first TA value, or (b) the UL transmission is associated with the first TA value based on one of: (i) the UL transmission or a configuration of the UL transmission includes or is associated with one of the first TA value, the first TAG, the first TAT, or the first TRP, and / or (ii) the UL transmission or the configuration of the UL transmission includes or is associated with the first index. In some such implementations, the UL transmission is one of: (i) a PUSCH with a configured UL grant, (ii) a P-SRS or SP-SRS, (iii) a P-CSI report or SP-CSI report, (iv) a P-CSI report or SP-CSI report carried or sent on a PUCCH or PUSCH resource, and / or (v) a scheduling request.

[0163] In a further case, the UE determines that (a) the UL transmission is sent by applying a second TA value, or (b) the UL transmission is associated with the second TA value based on one of: (i) the UL transmission or the configuration of the UL transmission includes or is associated with one of the second TA value, the second TAG, the second TAT, or the second TRP, and / or (ii) the UL transmission or the configuration of the UL transmission includes or is associated with the second index. In some such implementations, the UL transmission is one of: (i) a PUSCH with a configured UL grant, (ii) a P-SRS or SP-SRS, (iii) a P-CSI report or an SP-CSI report, (iv) a P-CSI report or an SP-CSI report carried or sent on a PUCCH or PUSCH resource, and / or (v) a scheduling request.

[0164] In a further case, the configuration of the UL transmission refers to at least one of the following: (i) if the UL transmission is a PUCCH resource, the configuration may refer to: (a) PUCCH-config, (b) resourceSetToAddModList or resourceSetToReleaseList, (c) resourceToAddModList or resourceToReleaseList, (d) schedulingRequestResourceToAddModList or schedulingRequestResourceToReleaseList, (e) resourceToAddModListExt-v1610, (f) schedulingRequestResourceToAddModListExt-v1610 or schedulingRequestResourceToAddModListExt-v1700, (g) PUCCH-ResourceSet, (h) resourceList, (i) PUCCH-Resource or PUCCH-ResourceExt-v1610, and / or (j) PUCCH-ConfigCommon;(ii) If the UL transmission is an SRS resource, the configuration may refer to: (a) SRS-Config, (b) srs-ResourceSetToAddModList or srs-ResourceSetToReleaseList, (c) srs-ResourceToAddModList or srs-ResourceToReleaseList, (d) srs-ResourceSetToAddModListDCI-0-2-r16 or srs-ResourceSetToReleaseListDCI-0-2-r16, (e) srs-PosResourceSetToAddModList-r16 or srs-PosResourceSetToReleaseList-r16, (f) srs-PosResourceToAddModList-r16 or srs-PosResourceToReleaseList-r16, (g) SRS-ResourceSet, (h) srs-ResourceIdList, (i) SRS-PosResourceSet-r16, (j) srs-PosResourceIdList-r16, (k) SRS-Resource, (l) SRS-PosResource-r16, and / or (m) SRS-CarrierSwitching; (iii) if the UL transmission is a dynamically scheduled PUSCH, the configuration may refer to: (a) PUSCH-Config, (b) pusch-TimeDomainAllocationList, (c) pusch-TimeDomainAllocationListDCI-0-1-r16 or pusch-TimeDomainAllocationListDCI-0-2-r16, (d) pusch-TimeDomainAllocationListForMultiPUSCH-r16 or pusch-TimeDomainAllocationListForMultiPUSCH-r17, (e) pusch-TimeDomainAllocationListDCI-0-1-r17 or pusch-TimeDomainAllocationListDCI-0-2-r17, (f) PUSCH-ConfigCommon, and / or (g) PUSCH-ServingCellConfig;and / or (iv) if the UL transmission is a configured UL grant, the configuration may refer to: (a) ConfiguredGrantConfig, (b) rrc-ConfiguredUplinkGrant, (c) timeDomainAllocation, and / or (d) cg-SDT-Configuration-r17. ;

[0165] Next go to Figure 8 , a UE (eg, UE 102) implements example method 800 to determine which TA value (eg, the first TA value or the second TA value) to apply when sending an UL transmission.

[0166] Method 800 starts at block 802. Blocks 802, 804, 806, 820, 822, 824, and 826 are similar to blocks 702, 704, 706, 720, 722, 724, and 726. At block 808, the UE receives a scheduling or triggering signal for UL transmission on a CORESET from a base station (e.g., event 550). At block 810, the UE determines whether the CORESET is associated with CORESETPoolIndex #0 or CORESETPoolIndex #1. If the UE determines that the CORESET is associated with CORESETPoolIndex #0, the flow proceeds to block 820. If the UE determines that the CORESET is associated with CORESETPoolIndex #1, the flow proceeds to block 824.

[0167] Similar to methods 600 and 700 , a more detailed description of the elements of method 800 is generally described herein.

[0168] In some cases, if or when a UL transmission is scheduled or triggered by a DL transmission configured with or associated with a first index, the UE determines that (i) the UL transmission is sent by applying a first TA value or (ii) the UL transmission is associated with the first TA value. In some implementations, the UE determines this at block 810. In some such implementations, the DL transmission is one of: (i) CORESET, (ii) DCI, (iii) search space, (iv) PDSCH, and / or (v) CSI-RS. In further such implementations, the UL transmission is one of: (i) dynamically scheduled PUSCH, (ii) AP-SRS, (iii) AP-CSI report, and / or (iv) AP-CSI report carried or sent on PUCCH or PUSCH resources.

[0169] In some cases, if or when the UL transmission is associated with or in response to a DL transmission configured with or associated with the first index, the UE determines that (i) the UL transmission is sent by applying a first TA value, or (ii) the UL transmission is associated with the first TA value. In some implementations, the UE determines this at block 810. In some such implementations, the DL transmission is one of: (i) a CORESET, (ii) a DCI, (iii) a search space, (iv) a PDSCH, and / or (v) a CSI-RS. In further such implementations, the UL transmission is a PUCCH resource indicated by a DCI that schedules a PDSCH. As an example, the UL transmission is a PUCCH resource associated with or in response to a PDSCH, where the PDSCH is scheduled by a DCI from a CORESET with CORESETPoolIndex #0. The PUCCH resource is indicated by the DCI. For some such examples, the PUCCH resource is sent by applying the first TA value.

[0170] In some cases, if or when a UL transmission is scheduled or triggered by a DL transmission configured with or associated with a second index, the UE determines that (i) the UL transmission is sent by applying a second TA value or (ii) the UL transmission is associated with the second TA value. In some implementations, the UE determines this at block 810. In some such implementations, the DL transmission is one of: (i) CORESET, (ii) DCI, (iii) search space, (iv) PDSCH, and / or (v) CSI-RS. In further such implementations, the UL transmission is one of: (i) dynamically scheduled PUSCH, (ii) AP-SRS, (iii) AP-CSI report, and / or (iv) AP-CSI report carried or sent on PUCCH or PUSCH resources.

[0171] In some cases, if or when the UL transmission is associated with or in response to a DL transmission configured with or associated with a second index, the UE determines that (i) the UL transmission is sent by applying a second TA value, or (ii) the UL transmission is associated with a second TA value. In some implementations, the UE determines this at block 810. In some such implementations, the DL transmission is one of: (i) a CORESET, (ii) a DCI, (iii) a search space, (iv) a PDSCH, and / or (v) a CSI-RS. In further such implementations, the UL transmission is a PUCCH resource indicated by a DCI that schedules a PDSCH. As an example, the UL transmission is a PUCCH resource associated with or in response to a PDSCH, where the PDSCH is scheduled by a DCI from a CORESET with CORESETPoolIndex #1. In further implementations, the PUCCH resource is indicated by the DCI. In some such examples, the PUCCH resource is sent by applying a second TA value.

[0172] Next go to Fig. 9A , a UE (eg, UE 102) implements example method 900A to determine which TA value (eg, a first TA value or a second TA value) to apply when sending an UL transmission.

[0173] Method 900A starts at block 902. Blocks 902, 904, 906, 920, 922, 924, and 926 are similar to blocks 702, 704, 706, 720, 722, 724, and 726. At block 907, the UE receives a first index and a second index from a base station. At block 908A, the UE receives a configuration to configure a spatial indication from the base station. At block 910A, the UE receives a configuration to configure the UE to send an UL transmission (e.g., a PUSCH transmission, a PUCCH transmission, or an SRS) by referencing the spatial indication or an indication (e.g., events 506, 518, 528, 538, 550, 551, 564, 580, 581) from the base station. At block 912, the UE determines to send an UL transmission. At block 914A, the UE determines whether the spatial indication is associated with the first index or the second index. If the UE determines that the spatial indication is associated with the first index, the flow proceeds to block 920. If the UE determines that the spatial indication is associated with the second index, the flow proceeds to block 924.

[0174] Fig. 9B Examples and Fig. 9AExample method 900B is similar to scenario 900A shown in FIG. 9, except that it is about blocks 908B, 910B, and 914B instead of 908A, 910A, and 914A. At block 908B, the UE receives a reference signal from a base station, or sends a reference signal to a base station. At block 910B, the UE receives from the base station a configuration that configures the UE to send an UL transmission (e.g., a PUSCH transmission, a PUCCH transmission, or an SRS) by referencing the reference signal or an indication (e.g., events 506, 518, 528, 538, 550, 551, 564, 580, 581) that instructs the UE to send the UL transmission by referencing the reference signal. At block 914B, the UE determines whether the reference signal is associated with the first index or the second index. If the UE determines that the reference signal is associated with the first index, the process proceeds to block 920. If the UE determines that the reference signal is associated with the second index, the process proceeds to block 924.

[0175] Similar to methods 600 , 700 , and 800 , a more detailed description of the elements of methods 900A and 900B are generally detailed above.

[0176] In some cases, the UE receives an indication or configuration of a spatial indication. In some implementations, the spatial indication is associated with or includes an ID of the spatial indication.

[0177] In some cases, the UE determines that (i) the UL transmission is sent by applying a first TA value, or (ii) the UL transmission is associated with the first TA value if or when at least one of the following occurs: (i) the base station configures or instructs the UE to send the UL transmission by applying a first TA value, or (ii) the UL transmission is associated with the first TA value: (i) the base station configures or instructs the UE to send the UL transmission by applying a spatial transmission filter / parameter derived from a spatial indication, wherein the spatial indication is associated with one of the first TA value, the first TAG, the first TAT, or the first TRP, (ii) the base station configures or instructs the UE to send the UL transmission by applying a spatial transmission filter / parameter derived from a spatial indication, wherein the spatial indication is associated with or includes the first index, (iii) the base station configures or instructs the UE to send the UL transmission by applying a spatial transmission filter / parameter derived from a reference signal, wherein the reference signal is associated with one of the first TA value, the first TAG, the first TAT, or the first TRP, and / or (iv) the base station configures or instructs the UE to send the UL transmission by applying a spatial transmission filter / parameter derived from a reference signal, wherein the reference signal is associated with or includes the first index.

[0178] In some cases, the UE determines that (i) the UL transmission is sent by applying a second TA value, or (ii) the UL transmission is associated with the second TA value if or when at least one of the following occurs: (i) the base station configures or instructs the UE to send the UL transmission by applying a second TA value, or (ii) the UL transmission is associated with the second TA value: (i) the base station configures or instructs the UE to send the UL transmission by applying a spatial transmission filter / parameter derived from a spatial indication, wherein the spatial indication is associated with one of the second TA value, the second TAG, the second TAT, or the second TRP, (ii) the base station configures or instructs the UE to send the UL transmission by applying a spatial transmission filter / parameter derived from a spatial indication, wherein the spatial indication is associated with or includes the second index, (iii) the base station configures or instructs the UE to send the UL transmission by applying a spatial transmission filter / parameter derived from a reference signal, wherein the reference signal is associated with one of the second TA value, the second TAG, the second TAT, or the second TRP, and / or (iv) the base station configures or instructs the UE to send the UL transmission by applying a spatial transmission filter / parameter derived from a reference signal, wherein the reference signal is associated with or includes the second index.

[0179] In some cases, the spatial indication is one of or includes one of: (i) spatial relationship or spatial relationship info or spatial relationship information; (ii) UL TCI; (iii) joint TCI; (iv) spatialRelationInfo or SpatialRelationInfo-PDC-r17; (v) spatialRelationInfoPos-r16, where in some implementations, UL transmission is related to positioning; (vi) PUCCH-SpatialRelationInfo or PUCCH-SpatialRelationInfoExt-r16; (vii) SRS-SpatialRelationInfo; (viii) SRS-SpatialRelationInfoPos-r16, where in some implementations, UL transmission is related to positioning; (ix) DLorJoint-TCIState-r17; and / or (x) UL-TCIState-r17.

[0180] In some cases, the reference signal is one of: (i) SSB, (ii) CSI-RS, (iii) SRS, (iv) SSB from a neighboring cell, and / or (v) DL PRS or DL ​​PRS for propagation delay compensation (PDC).

[0181] In some implementations, the spatial indication includes the first index or the second index means that the configuration of the spatial indication includes or contains the first index or the second index. In further implementations, the reference signal includes the first index or the second index means that the configuration of the reference signal includes or contains the first index or the second index.

[0182] In some cases, the base station configures the first list for the UE or indicates the first list to the UE. In some implementations, the first list includes one or more spatial indications. In some implementations, the first list includes one or more IDs of the spatial indications.

[0183] In some cases, the BS configures the second list for the UE or indicates the second list to the UE. In some implementations, the second list includes one or more spatial indications. In some implementations, the second list includes one or more IDs of the spatial indications.

[0184] In some implementations, the first list is associated with or includes a first TA value or an ID of a first TA value. In some implementations, the first list is associated with or includes a first TAG or an ID of a first TAG. In some implementations, the first list is associated with or includes a first TAT or an ID of a first TAT. In some implementations, the first list is associated with or includes a first TAT or an ID of a first TAT. In some implementations, the first list is associated with or includes a first TRP or a first TRP identifier and / or an identifier value.

[0185] In some implementations, the second list is associated with or includes a second TA value or an ID of a second TA value. In some implementations, the second list is associated with or includes a second TAG or an ID of a second TAG. In some implementations, the second list is associated with or includes a second TAG or an ID of a second TAG. In some implementations, the second list is associated with or includes a second TAT or an ID of a second TAT. In some implementations, the second list is associated with or includes a second TRP or a second TRP identifier and / or an identifier value.

[0186] In some cases, the base station configures the first resource list for the UE or indicates the first resource list to the UE. In some implementations, the first resource list includes one or more reference signals. In some implementations, the first list includes one or more IDs of the reference signals.

[0187] In some cases, the base station configures the second resource list for the UE or indicates the second resource list to the UE. In some implementations, the second resource list includes one or more reference signals. In some implementations, the second list includes one or more IDs of the reference signals.

[0188] In some implementations, the first resource list is associated with or includes a first TA value or an ID of a first TA value. In some implementations, the first resource list is associated with or includes a first TAG or an ID of a first TAG. In some implementations, the first resource list is associated with or includes a first TAG or an ID of a first TAG. In some implementations, the first resource list is associated with or includes a first TAT or an ID of a first TAT. In some implementations, the first resource list is associated with or includes a first TRP or a first TRP identifier and / or an identifier value.

[0189] In some implementations, the second resource list is associated with or includes a second TA value or an ID of a second TA value. In some implementations, the second resource list is associated with or includes a second TAG or an ID of a second TAG. In some implementations, the second resource list is associated with or includes a second TAG or an ID of a second TAG. In some implementations, the second resource list is associated with or includes a second TAT or an ID of a second TAT. In some implementations, the second resource list is associated with or includes a second TRP or a second TRP identifier and / or an identifier value.

[0190] In some cases, the UE determines that (i) the UL transmission is sent by applying the first TA value, or (ii) the UL transmission is associated with the first TA value if or when at least one of the following occurs: (i) the base station configures or instructs the UE to send the UL transmission through a spatial transmission filter / parameter derived from a spatial indication, where the spatial indication or its ID is associated with or included in the first list, and / or (ii) the base station configures or instructs the UE to send the UL transmission through a spatial transmission filter / parameter derived from a reference signal, where the reference signal or its ID is associated with or included in the first resource list.

[0191] In some cases, the UE determines that (i) the UL transmission is sent by applying the second TA value, or (ii) the UL transmission is associated with the second TA value if or when at least one of the following occurs: (i) the base station configures or instructs the UE to send the UL transmission through a spatial transmission filter / parameter derived from a spatial indication, where the spatial indication or its ID is associated with or included in the second list, and / or (ii) the base station configures or instructs the UE to send the UL transmission through a spatial transmission filter / parameter derived from a reference signal, where the reference signal or its ID is associated with or included in the second resource list.

[0192] In some implementations, the first list and / or the second list is one of the following or is modified from one of the following: (i) spatialRelationInfoToAddModList or spatialRelationInfoToAddModListExt-v1610; wherein the first list is spatialRelationInfoToAddModList or spatialRelationInfoToAddModList1-r18, the second list can be spatialRelationInfoToAddModList-r18 or spatialRelationInfoToAddModList2-r18, and / or the first list and / or the second list is configured in a configuration (e.g., PUCCH-Config); (ii) ul-TCIState-ToAddModList-r17, wherein the first list is ul-TCIState-ToAddModList-r17 or ul-TCIState-ToAddModList1-r18, and the second list is ul-TCIState-ToAddModList-r18 or ul-TCIState-ToAddModList2-r18, and / or the first list and / or the second list are configured in a configuration (e.g., BWP-UplinkDedicated); and / or (iii) dl-orJoint-TCIState-ToAddModList-r17, where the first list is dl-orJoint-TCIState-ToAddModList-r17 or dl-orJoint-TCIState-ToAddModList1-r18, the second list is dl-orJoint-TCIState-ToAddModList-r18 or dl-orJoint-TCIState-ToAddModList2-r18, and / or the first list and / or the second list are configured in the configuration (e.g., PDSCH-Config).

[0193] In some implementations, the first resource list and / or the second resource list is one of the following or is modified from one of the following: (i) srs-ResourceSetToAddModList, (ii) srs-ResourceToAddModList, (iii) srs-ResourceSetToAddModListDCI-0-2-r16, (iv) srs-PosResourceSetToAddModList-r16, (v) srs-PosResourceToAddModList-r16, (vi) SRS-ResourceSet, (vii) srs-ResourceIdList, (viii) SRS-PosResourceSet, (ix) srs-PosResourceIdList-r16, (x) nzp-CSI-RS-ResourceToAddModList, (xi) nzp-CSI-RS-ResourceSetToAddModList, (xii) csi-SSB-ResourceSetToAddModList, (xiii) csi-ResourceConfigToAddModList, (xiv) CSI-ResourceConfig, (xv) csi-RS-ResourceSetList, (xvi) nzp-CSI-RS-SSB, (xvii) nzp-CSI-RS-ResourceSetList, (xviii) csi-SSB-ResourceSetList, (xix) csi-SSB-ResourceSetListExt-r17, (xx)csi-RS-CellList-Mobility, (xxi) csi-rs-ResourceList-Mobility, (xxii) CSI-SSB-ResourceSet, (xxiii) NZP-CSI-RS-ResourceSet, (xxiv) nzp-CSI-RS-Resources, (xxv) a list or set of SSBs, and / or (xxvi) a list or set of SSBs sent from a neighboring cell.

[0194] In some implementations, the first list and / or the second list are included in or associated with a TAG or a TAG configuration. In some implementations, the first resource list and / or the second resource list are included in or associated with a TAG or a TAG configuration.

[0195] Next go to Fig.10 , a UE (eg, UE 102) implements example method 1000 to determine which TA value (eg, the first TA value or the second TA value) to apply when sending an UL transmission.

[0196] Method 1000 starts at block 1002. Blocks 1002, 1004, 1006, 1020, 1022, 1024, and 1026 are similar to blocks 702, 704, 706, 720, 722, 724, and 726. At block 1007, the UE receives a first index and a second index from a base station. At block 1008, the UE receives an indication from the base station that a path loss estimate for an UL transmission (e.g., a PUSCH transmission, a PUCCH transmission, or an SRS) is based on a path loss RS. At block 1010, the UE determines to send an UL transmission. At block 1012, the UE determines whether the path loss RS is associated with the first index or the second index. If the UE determines that the path loss RS is associated with the first index, the process proceeds to block 1020. If the UE determines that the path loss RS is associated with the second index, the process proceeds to block 1024.

[0197] Similar to methods 600 - 900B, a more detailed description of the elements of method 1000 is generally detailed above.

[0198] In some cases, the base station configures or indicates a path loss reference signal to the UE.In some implementations, the path loss reference signal is associated with or includes an ID of the path loss reference signal.

[0199] In some cases, the UE may determine that (i) the UL transmission is sent by applying a first TA value, or (ii) the UL transmission is associated with the first TA value if or when at least one of the following occurs: (i) the base station configures or instructs the UE to estimate or determine the path loss of the UL transmission by using a path loss reference signal, where the path loss reference signal is associated with one of the first TA value, the first TAG, the first TAT, or the first TRP, and / or (ii) the base station configures or instructs the UE to estimate or determine the path loss of the UL transmission by using a path loss reference signal, where the path loss reference signal is associated with or includes a first index.

[0200] In some cases, the UE determines that (i) the UL transmission is sent by applying a second TA value, or (ii) the UL transmission is associated with the second TA value if or when at least one of the following occurs: (i) the base station configures or instructs the UE to estimate or determine the path loss of the UL transmission by using a path loss reference signal, where the path loss reference signal is associated with one of the second TA value, the second TAG, the second TAT, or the second TRP, and / or (ii) the base station configures or instructs the UE to estimate or determine the path loss of the UL transmission by using a path loss reference signal, where the path loss reference signal is associated with or includes a second index.

[0201] In some implementations, the path loss reference signal including the first index or the second index means that the configuration of the reference signal includes or contains the first index or the second index.

[0202] In some implementations, the path loss RS or the configuration of the path loss RS is or includes one of the following: (i) PUSCH-PathlossReferenceRS or PUSCH-PathlossReferenceRS-r16, (ii) PUCCH-PathlossReferenceRS or PUCCH-PathlossReferenceRS-r16, (iii) PathlossReferenceRS-Config or PathlossReferenceRS-r16 or pathlossReferenceRS-Pos-r16, (iv) SSB or SSB index, (v) CSI-RS or CSI-RS resource index, (vi) SSB-InfoNcell-r16, (vii) DL PRS or DL ​​PRS for PDC or DL ​​PRS resource index, and / or (viii) DL-PRS-Info-r16.

[0203] In some cases, the base station configures the first path loss list for the UE or indicates the first path loss list to the UE. In some implementations, the first path loss list includes one or more reference signals. In some implementations, the first path loss list includes one or more IDs of path loss reference signals.

[0204] In some cases, the base station configures the second path loss list for the UE or indicates the second path loss list to the UE. In some implementations, the second path loss list includes one or more path loss reference signals. In some implementations, the second path loss list includes one or more IDs of the path loss reference signals.

[0205] In some implementations, the first path loss list is associated with or includes a first TA value or an ID of a first TA value. In some implementations, the first path loss list is associated with or includes a first TAG or an ID of a first TAG. In some implementations, the first path loss list is associated with or includes a first TAG or an ID of a first TAG. In some implementations, the first path loss list is associated with or includes a first TAT or an ID of a first TAT. In some implementations, the first path loss list is associated with or includes a first TRP or a first TRP identifier and / or an identifier value.

[0206] In some implementations, the second path loss list is associated with or includes a second TA value or an ID of a second TA value. In some implementations, the second path loss list is associated with or includes a second TAG or an ID of a second TAG. In some implementations, the second path loss list is associated with or includes a second TAG or an ID of a second TAG. In some implementations, the second path loss list is associated with or includes a second TAT or an ID of a second TAT. In some implementations, the second path loss list is associated with or includes a second TRP or a second TRP identifier and / or an identifier value.

[0207] In some cases, if or when the base station configures or instructs the UE to estimate or determine the path loss of the UL transmission by using a path loss reference signal, where the path loss reference signal is associated with or included in a first path loss list, the UE determines that (i) the UL transmission is sent by applying the first TA value, or (ii) the UL transmission is associated with the first TA value.

[0208] In some cases, if or when the base station configures or instructs the UE to estimate or determine the path loss of the UL transmission by using a path loss reference signal, where the path loss reference signal is associated with or included in the second path loss list, the UE determines that (i) the UL transmission is sent by applying the second TA value, or (ii) the UL transmission is associated with the second TA value.

[0209] In some implementations, the first path loss list and / or the second path loss list is one of the following or is modified from one of the following: (i) pathlossReferenceRSToAddModList or pathlossReferenceRSToAddModListSizeExt-v1610, where, for example, the first path loss list is pathlossReferenceRSToAddModList or pathlossReferenceRSToAddModList1-r18, the second path loss list is pathlossReferenceRSToAddModList-r18 or pathlossReferenceRSToAddModList2-r18, and / or the first path loss list and / or the second path loss list is configured in a configuration (e.g., PUSCH-config or PUSCH-PowerControl or PUSCH-PowerControl-v1610); (ii) pathlossReferenceRSs, where, for example, the first path loss list is pathlossReferenceRSToAddModList or pathlossReferenceRSToAddModList1-r18, the second path loss list is pathlossReferenceRSToAddModList-r18 or pathlossReferenceRSToAddModList2-r18, and / or the first path loss list and / or the second path loss list is configured in a configuration (e.g., PUSCH-config or PUSCH-PowerControl or PUSCH-PowerControl-v1610); enceRSs or pathlossReferenceRSs1-r18, the second path loss list is pathlossReferenceRSs-r18 or pathlossReferenceRSs2-r18, and / or the first path loss list and / or the second path loss list are configured in the configuration (e.g., PUCCH-config or PUCCH-PowerControl); and / or (iii) pathlossReferenceRSList-r16, wherein, for example, the first path loss list is pathlossReferenceRSList-r16 or pathlossReferenceRSList1-r18, the second path loss list is pathlossReferenceRSList-r18 or pathlossReferenceRSList2-r18, and / or the first path loss list and / or the second path loss list are configured in the configuration (e.g., SRS-ResourceSet).

[0210] Next go to Fig.11 , a UE (eg, UE 102) implements example method 1100 to determine which TA value (eg, the first TA value or the second TA value) to apply when sending an UL transmission.

[0211] Method 1100 starts at block 1102. Blocks 1102, 1104, 1106, 1120, 1122, 1124, and 1126 are similar to blocks 702, 704, 706, 720, 722, 724, and 726. At block 1108, the UE receives a configuration configuring a first group of UL transmissions and a second group of UL transmissions or an indication indicating a first group of UL transmissions and a second group of UL transmissions from a base station. At block 1110, the UE determines to send an UL transmission (e.g., a PUSCH transmission, a PUCCH transmission, or an SRS). At block 1112, the UE determines whether the UL transmission is included in the first group or the second group. If the UE determines that the UL transmission is included in the first group, the process proceeds to block 1120. If the UE determines that the UL transmission is included in the second group, the process proceeds to block 1124.

[0212] Similar to methods 600-1000, a more detailed description of the elements of method 1100 is generally detailed above.

[0213] In some cases, the base station configures the first group for the UE or indicates the first group to the UE. In some implementations, the first group includes one or more UL channels or UL RSs. In some implementations, the first group includes one or more IDs of the UL channels or UL RSs.

[0214] In some cases, the base station configures the second group for the UE or indicates the second group to the UE. In some implementations, the second group includes one or more UL channels or UL RSs. In some implementations, the second group includes one or more IDs of the UL channels or UL RSs.

[0215] In some implementations, the first group is associated with or includes a first TA value or an ID of a first TA value. In some implementations, the first group is associated with or includes a first TAG or an ID of a first TAG. In some implementations, the first group is associated with or includes a first TAT or an ID of a first TAT. In some implementations, the first group is associated with or includes a first TAT or an ID of a first TAT. In some implementations, the first group is associated with or includes a first TRP or a first TRP identifier and / or an identifier value.

[0216] In some implementations, the second group is associated with or includes a second TA value or an ID of a second TA value. In some implementations, the second group is associated with or includes a second TAG or an ID of a second TAG. In some implementations, the second group is associated with or includes a second TAG or an ID of a second TAG. In some implementations, the second group is associated with or includes a second TAT or an ID of a second TAT. In some implementations, the second group is associated with or includes a second TRP or a second TRP identifier and / or an identifier value.

[0217] In some cases, if or when the UE determines that the UL transmission is associated with or included in the first group, or the base station configures or indicates that the UL transmission is associated with or included in the first group, the UE determines that (i) the UL transmission is sent by applying the first TA value, or (ii) the UL transmission is associated with the first TA value.

[0218] In some cases, if or when the UE determines that the UL transmission is associated with or included in the second group, or the base station configures or indicates that the UL transmission is associated with or included in the second group, the UE determines that (i) the UL transmission is sent by applying the second TA value, or (ii) the UL transmission is associated with the second TA value.

[0219] In some implementations, where the UL transmission is a PUSCH (with a dynamically scheduled UL grant or a configured UL grant), the first group and / or the second group is a PUSCH resource group. For example, the first group is a PUSCH resource group and the second group is another PUSCH resource group.

[0220] In some implementations, the first group and / or the second group is a PUSCH group in the case where the UL transmission is a PUSCH with a configured UL grant. In some implementations, the first group and / or the second group is configuredGrantConfigToAddModList-r16 or is modified therefrom. For example, the first group is a PUSCH group configured from configuredGrantConfigToAddModList-r16 or configuredGrantConfigToAddModList-r18, and the second group is another PUSCH group configured from configuredGrantConfigToAddModList-r16 or configuredGrantConfigToAddModList-r18.

[0221] In some implementations, in the case where the UL transmission is a PUCCH, the first group and / or the second group is a PUCCH group. In some implementations, the first group and / or the second group is a PUCCH-ResourceGroup-r16 or is modified therefrom. For example, the first group is a PUCCH group configured from PUCCH-ResourceGroup-r16 or PUCCH-ResourceGroup-r18, and the second group is another PUCCH group configured from PUCCH-ResourceGroup-r16 or PUCCH-ResourceGroup-r18.

[0222] In some implementations, where the UL transmission is an SRS, the first group and / or the second group is an SRS group or an SRS resource set. In some implementations, the first group and / or the second group is one of the following or is modified from one of the following: (i) srs-ResourceToAddModList, (ii) srs-PosResourceToAddModList-r16, (iii) SRS-ResourceSet or srs-ResourceIdList, and / or (iv) SRS-PosResourceSet or srs-PosResourceIdList-r16. For example, the first group is an SRS resource set and the second group is another SRS resource set.

[0223] Next go to Fig.12 , a UE (eg, UE 102) implements example method 1200 to determine which TA value (eg, the first TA value or the second TA value) to apply when sending an UL transmission.

[0224] Method 1200 starts at block 1202. Blocks 1202, 1204, 1206, 1220, 1222, 1224, and 1226 are similar to blocks 702, 704, 706, 720, 722, 724, and 726. At block 1208, the UE receives a configuration or indication for a first HARQ process set and a second HARQ process set from a base station. At block 1210, the UE determines to use a HARQ process to send an UL transmission (e.g., a PUSCH transmission, a PUCCH transmission, or an SRS). At block 1212, the UE determines whether the HARQ process is included in the first HARQ process set or the second HARQ process set. If the UE determines that the HARQ process is included in the first HARQ process set, the process proceeds to block 1220. If the UE determines that the HARQ process is included in the second group, the process proceeds to block 1224.

[0225] Similar to methods 600 - 1100 , a more detailed description of the elements of method 1200 is generally described above.

[0226] In some cases, the base station configures the first HARQ process set for the UE or indicates the first HARQ process set to the UE. In some cases, the UE derives the first HARQ process set.

[0227] In some implementations, the first HARQ process set is associated with one of: (i) a first TA value or an ID of a first TA value, (ii) a first TAG or an ID of a first TAG, (iii) a first TAT or an ID of a first TAT, and / or (iv) a first TRP or a first TRP identifier and / or identifier value. In some implementations, the association of the first HARQ process set is performed via a DCI signal, a MAC-CE, or an RRC message.

[0228] In some cases, the base station configures the second HARQ process set for the UE or indicates the second HARQ process set to the UE. In some cases, the UE derives the second HARQ process set.

[0229] In some implementations, the second HARQ process set is associated with one of: (i) a second TA value or an ID of a second TA value, (ii) a second TAG or an ID of a second TAG, (iii) a second TAT or an ID of a second TAT, and / or (iv) a second TRP or a second TRP identifier and / or identifier value. In some implementations, the association of the second HARQ process set may be accomplished via a DCI signal, a MAC-CE, or an RRC message.

[0230] In some cases, if or when the UE determines that a UL transmission is associated with or sent via a HARQ process included in a first HARQ process set, or the base station configures or indicates that the UL transmission is associated with or sent via a HARQ process included in the first HARQ process set, the UE determines that (i) the UL transmission is sent by applying a first TA value, or (ii) the UL transmission is associated with the first TA value.

[0231] In some cases, if or when the UE determines that the UL transmission is associated with or sent via a HARQ process included in a second HARQ process set, or the base station configures or indicates that the UL transmission is associated with or sent via a HARQ process included in the second HARQ process set, the UE determines that (i) the UL transmission is sent by applying a second TA value, or (ii) the UL transmission is associated with the second TA value.

[0232] The following description can be applied to some situations (for example, FIG. 5A to FIG. 5E ) for more description.

[0233] In some cases, the UE sends a first capability report to the base station. In some implementations, the first capability report indicates at least one of: (i) whether the UE can support a serving cell belonging to more than one TAG or included in more than one TAG at the same time, (ii) whether the UE can support more than one TA value maintained or operated in one serving cell, and / or (iii) whether the UE can support multi-TA operation (e.g., two TA values) in an M-TRP scenario (e.g., M-DCI M-TRP or S-DCI M-TRP).

[0234] In some cases, the UE sends a second capability report to the base station. In some implementations, the second capability report indicates a maximum number of TAGs supported by the UE given that the TAG is configured for multi-TA operation. In some implementations, the second capability report is supportedNumberTAG.

[0235] In some cases, the UE sends a third capability report to the base station. In some implementations, given that all TAGs are configured for multi-TA operation (e.g., two TA values), the third capability report indicates at least one of the following: (i) a maximum number of TAGs supported by the UE, where (a) one serving cell with a multi-TA feature is associated with or included in two TAGs, where each of the two TAGs is associated with only one TA value or TAT, and / or (b) if the UE supports maintaining or operating more than one TA value in one serving cell (indicated in the first capability report), the number is at least two; and / or (ii) a maximum number of TAGs supported by the UE, where (a) one serving cell with a multi-TA feature is associated with or included in one TAG, where the TAG is associated with more than one TA value or TAT (e.g., two TA values ​​or two TATs), and / or (b) if the UE supports maintaining or operating more than one TA value in one serving cell (indicated in the first capability report), the number is at least one. In some implementations, the third capability report is a UE capability different from supportedNumberTAG. In some implementations, the fourth capability report is supportedNumberTAG-2TA. In some implementations, if the third capability report is not present or is not sent, the UE does not support maintaining or operating more than one TA value in one serving cell. In some such cases, the third capability report and the first capability report are the same.

[0236] In some cases, the UE sends a fourth capability report to the base station. In some implementations, the fourth capability report indicates a maximum number of TAGs supported by the UE or a maximum number of TAG pairs supported by the UE. In some implementations, a TAG pair includes two TAGs configured for multi-TA operation. In some implementations, given that at least one TAG is configured for multi-TA operation (e.g., two TA values), the fourth capability report indicates at least one of the following: (i) the maximum number of TAGs supported by the UE, where (a) a serving cell with multi-TA features is associated with or included in two TAGs, where each of the two TAGs is associated with only one TA value or TAT, (b) the number counts all TAGs configured for single-TA operation and multi-TA operation, (c) the number counts all TAGs configured only for multi-TA operation, and / or (d) if the UE supports maintaining or operating more than one TA value in a serving cell (indicated in the first capability report), the number is up to at least two; (ii) the maximum number of TAG pairs supported by the UE, where (a) one serving cell with multi-TA feature is associated with or included in two TAGs, where each of the two TAGs is associated with only one TA value or TAT, (b) the number counts TAGs configured only for multi-TA operation, and / or (c) if the UE supports maintaining or operating more than one TA value in one serving cell (indicated in the first capability report), the number is at least one; (iii) the maximum number of TAGs supported by the UE, where (a) one serving cell with multi-TA feature is associated with or included in one TAG, where each of the two TAGs is associated with only one TA value or TAT In some implementations, the fourth capability report is a UE capability different from supportedNumberTAG. In some implementations, the fourth capability report is a UE capability different from supportedNumberTAG. In some implementations, the fourth capability report is a UE capability different from supportedNumberTAG. In some implementations, the fourth capability report is a UE capability different from supportedNumberTAG. In some implementations, the fourth capability report is a UE capability different from supportedNumberTAG. In some implementations, the fourth capability report is a UE capability different from supportedNumberTAG. In some implementations, the fourth capability report is a UE capability different from supportedNumberTAG. In some implementations, the fourth capability report is a UE capability different from supportedNumberTAG.In some implementations, if the fourth capability report is not present or is not sent, the UE does not support maintaining or operating more than one TA value in one serving cell.In some such cases, the fourth capability report and the first capability report are the same.

[0237] In some cases, the maximum number of TAGs or TAG pairs indicated in the second, third, or fourth capability report is affected by at least one of: (i) whether the number is used for NR CA, NR-DC and / or (NG)EN-DC / NE-DC; (ii) whether the band combination includes more than one band entry (i.e., inter-band or intra-band non-contiguous band combination); and / or (iii) the number of band entries.

[0238] In some cases, the UE receives an indication or configuration of a signal from a base station. In some implementations, the signal is an RRC IE (e.g., featurePriorities or featurePriorities-r18). In some implementations, the signal indicates a priority value of a feature supported by the UE. In some implementations, the signal indicates a priority value of at least one of the following features: (i) multi-TA operation (or 2 TA operation), (ii) RedCap (i.e., reduced capability), (iii) slicing (or network slicing or slicing group), (iv) SDT (i.e., small data transmission), (v) MSG3 repetition, (vi) MSGB repetition, and / or (vii) CovEnh (i.e., coverage enhancement).

[0239] In some implementations, the base station indicates one or more preamble combinations to the UE. In some implementations, a preamble combination includes one or more RA preambles and / or RA resources. In some implementations, the preamble combination is used for, indicated for, or associated with one or more features supported by the UE. In some implementations, the preamble combination is indicated by the RRC IE FeatureCombinationPreambles. In some implementations, which features are mapped to the preamble combination or associated with the preamble combination is indicated by the RRC IE featureCombination configured in FeatureCombinationPreambles.

[0240] In some implementations, when a feature is mapped to more than one preamble combination or is associated with more than one preamble combination, the indicated priority value is used to determine which preamble combination the UE uses or applies for the feature. In some implementations, a lower value means a higher priority. In some implementations, the base station does not indicate the same priority value for more than one feature. In some implementations, the base station indicates priority values ​​for all features mapped to at least one preamble combination or FeatureCombinationPreambles.

[0241] In some cases, the UE performs an RA procedure for a feature using a preamble combination determined to be used or applied for the feature. In some implementations, the UE performs an RA procedure for the feature using an RA preamble and / or RA resources in a preamble combination determined to be used or applied for the feature. In some implementations, the UE does not perform an RA procedure for the feature using an RA preamble and / or RA resources that are not in a preamble combination determined to be used or applied for the feature.

[0242] Note that throughout this disclosure, “TA value expires” may refer to at least one of the following: (i) the TA value is not synchronized, (ii) the TA value is out of date, and / or (iii) the TA value is uplink time aligned.

[0243] Note that throughout this disclosure, a neighboring cell may refer to or be replaced by at least one of the following: (i) a non-serving cell, (ii) a cell having a PCI different from the PCI of the serving cell, and / or (iii) a TRP associated with a PCI different from the PCI of the serving cell.

[0244] Note that throughout this disclosure, a joint TCI state may refer to or be replaced by at least one of the following: (i) a beam applicable to both DL transmission and UL transmission (e.g., DL or UL channel, DL or UL RS, etc.), (ii) a spatial filter for transmission and / or reception, (iii) a spatial parameter for transmission and / or reception, (iv) a spatial relationship for transmission and / or reception, and / or (v) a spatial assumption for transmission and / or reception.

[0245] Note that throughout this disclosure, the joint TCI state may refer to or be replaced by a common TCI state or a unified TCI state.

[0246] Note that throughout this document, UL TCI state may refer to or be replaced by at least one of the following: (i) UL beam, (ii) spatial relationship, (iii) spatial transmit filter, (iv) transmit precoder, (v) spatial parameters, and / or (vi) spatial relationship.

[0247] Note that throughout this disclosure, DL TCI state may refer to or be replaced by at least one of the following: (i) TCI applicable to a DL channel or RS, (ii) TCI associated with quasi co-location (QCL) type D, (iii) QCL assumptions, (iv) DL beams, (v) spatial receive filters, (vi) spatial parameters, (vii) spatial relationships, and / or (viii) spatial assumptions.

[0248] It should be noted that throughout this disclosure, a TCI pool (e.g., a joint TCI pool, a UL TCI pool, a DL TCI pool) may refer to or represent a (RRC) configuration or list, which may include or contain one or more TCI (indexes). It should be noted that throughout this disclosure, "TCI" may refer to or be replaced by "TCI state". It should be noted that throughout this disclosure, "TCI pool" may refer to or be replaced by "TCI state pool".

[0249] Note that throughout this disclosure, a UE may have one or more of the following attributes or behaviors. The following attributes or behaviors of a UE may also imply associated attributes or behaviors of a base station: (i) The UE is configured with a base station in a serving cell and / or is served by a base station in the serving cell. (ii) The UE is configured to communicate with the base station in the serving cell. (iii) The UE is configured by the base station with one or more serving cells that may include the serving cell. (iv) The UE is activated or instructed by the base station to activate one or more serving cells that may include the serving cell. (v) The UE has been configured and / or instructed by the base station for one or more BWPs. The UE has been instructed and / or configured by the BS for a BWP in a serving cell. (a) In some implementations, the BWP is activated as an active BWP; (b) In some implementations, the BWP refers to an active BWP; (c) In some implementations, the BWP is an active DL BWP; (d) In some implementations, the BWP is an active UL BWP; (e) In some implementations, the BWP is an initial BWP; (f) In some implementations, the BWP is a default BWP; (g) In some implementations, the BWP is a dormant BWP. (vi) The UE is in one of the RRC_CONNECTED state, the RRC_INACTIVE state, or the RRC_IDLE state.

[0250] It should be noted that throughout this disclosure, the expression of “X / Y” may include the meaning of “X or Y”. It should be noted that throughout this disclosure, the expression of “X / Y” may include the meaning of “X and Y”. It should be noted that throughout this disclosure, the expression of “X / Y” may include the meaning of “X and / or Y”. It should be noted that throughout this disclosure, the expression of “(A) B” or “B (A)” may include the concept of “only B”. It should be noted that throughout this disclosure, the expression of “(A) B” or “B (A)” may include the concept of “A+B” or “B+A”.

[0251] Note that throughout this disclosure, a panel may refer to an antenna (port) group or an antenna (port) set. There may be more than one DL / UL beam associated with one panel. When a transmitting node (UE or BS) is performing a transmission via a panel, only one beam associated with the panel may be used to perform the transmission. For a transmitter comprising more than one panel (e.g., two panels), it may happen that both beams associated with two panels, respectively, are used to perform the transmission.

[0252] Note that throughout this disclosure, a TRP identifier may mean or be referred to as a (candidate) value of a TRP identifier. A first TRP identifier may be a first candidate value of a TRP identifier or a first TRP identifier value. A second TRP identifier may be a second candidate value of a TRP identifier or a second TRP identifier value.

[0253] Note that throughout this disclosure, a panel identifier may mean or be referred to as a (candidate) value of a panel identifier. A first panel identifier may be a first candidate value of a panel identifier or a first panel identifier value. A second panel identifier may be a second candidate value of a panel identifier or a second panel identifier value.

[0254] Note that throughout this disclosure, a TCI field may mean or be referred to as a field that is used or applied or reused to indicate one or more TCI states.

[0255] Note that throughout this disclosure, "joint mode" or "joint TCI state mode" may mean at least one of the following: (i) the TCI field in the DCI format or the indicated TCI state refers to / maps to one of the joint TCI state pool, the DL TCI state pool, or the UL TCI state pool; and / or (ii) the beam indication or the indicated TCI state is applied to both sending UL transmissions and / or receiving DL transmissions.

[0256] Note that throughout this disclosure, "separate mode" or "separate TCI state mode" may mean at least one of the following: (i) the TCI field in the DCI format or the indicated TCI state refers to / maps to one of the joint TCI state pool, the DL TCI state pool or the UL TCI state pool; and / or (ii) the beam indication or the indicated TCI state is applied to (only) sending UL transmissions or (only) receiving DL transmissions.

[0257] Note that throughout this disclosure, "UL mode" or "UL TCI state mode only" may mean at least one of the following: (i) the TCI field in the DCI format or the indicated TCI state refers to / mapped to the UL TCI state pool (joint TCI state pool); and / or (ii) the beam indication or the indicated TCI state is applied to (only) sending UL transmissions.

[0258] Note that throughout this disclosure, "DL mode" or "DL TCI state mode only" may mean at least one of the following: (i) the TCI field in the DCI format or the indicated TCI state refers to / mapped to a DL TCI state pool (joint TCI state pool); and / or (ii) the beam indication or the indicated TCI state is applied to (only) receiving DL transmissions.

[0259] Note that throughout this disclosure, when a process or description is related to a serving cell, it may mean that the process or description is related to an active (DL / UL) BWP in the serving cell.

[0260] It is noted that throughout this disclosure, “TA timer” or “TAT” may refer to or be replaced by “TA alignment timer”.

[0261] It should be noted that some or all of the foregoing or following embodiments may be combined or formed jointly into a new or another embodiment.

[0262] It should be noted that the aforementioned or following embodiments may be used to solve at least (but not limited to) the problems or scenarios mentioned in the present disclosure.

[0263] The following list of examples reflects the various embodiments that are expressly contemplated.

[0264] Example 1. A method in a UE includes: receiving a configuration including a first TA value and a second TA value for use in a serving cell from a RAN; receiving a spatial indication from the RAN for communicating signals between the UE and the RAN; selecting a TA value from among the first TA value and the second TA value based on the spatial indication; and communicating signals with the RAN using the selected TA value.

[0265] Example 2. The method of Example 1, further comprising: receiving an indication from the RAN to enable use of multiple TA values ​​in the serving cell.

[0266] Example 3. The method as described in Example 1 further includes, before receiving the spatial indication: receiving a configuration, the configuration including an indication that the first spatial indication corresponds to a first TA value and the second spatial indication corresponds to a second TA value; wherein the selection of the TA value includes determining whether the received spatial indication is the first spatial indication or the second spatial indication.

[0267] Example 4. The method as described in Example 1 further includes, before receiving the spatial indication: receiving a configuration, the configuration including an indication that the first spatial indication corresponds to the first TAT and the second spatial indication corresponds to the second TAT; wherein the selection of the TA value includes determining whether the received spatial indication is the first spatial indication or the second spatial indication.

[0268] Example 5. The method as described in Example 1 further includes, before receiving the spatial indication: receiving a configuration, the configuration including an indication that the first spatial indication corresponds to the first TRP and the second spatial indication corresponds to the second TRP; wherein the selection of the TA value includes determining whether the received spatial indication is the first spatial indication or the second spatial indication.

[0269] Example 6. A method in a RAN, the method comprising: sending a configuration including a first TA value and a second TA value for use in a serving cell to a UE; sending from the RAN a spatial indication for communicating signals between the UE and the RAN, the spatial indication being associated with one of the first TA value or the second TA value; and communicating signals with the UE according to the spatial indication.

[0270] Example 7. The method of Example 5, further comprising: sending an indication to the UE to enable use of multiple TA values ​​in the serving cell.

[0271] Example 8. The method of Example 5, further comprising, before sending the spatial indication: sending a configuration to the UE, the configuration comprising an indication that the first spatial indication corresponds to the first TA value and the second spatial indication corresponds to the second TA value.

[0272] Example 9. The method of Example 5, further comprising, before sending the spatial indication: sending a configuration to the UE, the configuration comprising an indication that the first spatial indication corresponds to a first TA timer (TAT) and the second spatial indication corresponds to a second TAT.

[0273] Example 10. The method as described in Example 5 further includes, before sending the spatial indication: sending a configuration to the UE, the configuration including an indication that the first spatial indication corresponds to the first TRP and the second spatial indication corresponds to the second TRP.

[0274] The following additional considerations may apply to the foregoing and following discussions.

[0275] It should be noted that any two or more of the preceding or following paragraphs, (sub)bullet points, key points, actions or claims described in each method / embodiment / implementation may be logically, reasonably and appropriately combined to form a specific method.

[0276] It should be noted that any sentence, paragraph, (sub) bullet point, key point, action or claim described in the above or following method / embodiment / implementation can be implemented independently and separately to form a specific method. Dependencies such as "based on", "more specifically", "wherein" in the following method / embodiment / implementation are only possible embodiments that do not restrict specific methods.

[0277] Note that some or all of the following terms and assumptions may be used below: (i) Base Station (BS): A network central unit or network node in NR that controls one or more TRPs associated with one or more cells. Communication between the base station and the TRP is via fronthaul. The base station may be referred to as a central unit (CU), eNB, gNB, or NodeB. (ii) Transmission and Reception Point (TRP): A transmission and reception point provides network coverage and communicates directly with the UE. The TRP may be referred to as a distributed unit (DU) or a network node. (iii) Cell: A cell consists of one or more associated TRPs (i.e., the coverage of a cell consists of the coverage of all associated TRPs). One cell is controlled by one base station. A cell may be referred to as a TRP group (TRPG). (iv) Serving Beam: A UE's serving beam is a beam generated by a network node (e.g., TRP) and configured to communicate with the UE (e.g., for transmission and / or reception). (v) Candidate Beam: A UE's candidate beam is a candidate for a serving beam. A serving beam may or may not be a candidate beam.

[0278] The user device (e.g., UE 102) in which the technology of the present disclosure can be implemented can be any suitable device capable of wireless communication, such as a smart phone, a tablet computer, a laptop computer, a mobile game console, a point of sale (POS) terminal, a health monitoring device, a drone, a camera, a media streaming dongle or another personal media device, a wearable device such as a smart watch, a wireless hotspot, a femtocell or a broadband router. Further, in some cases, the user device can be embedded in an electronic system such as a head unit of a vehicle or an advanced driver assistance system (ADAS). Further, the user device can be operated as an Internet of Things (IoT) device or a mobile Internet device (MID). Depending on the type, the user device may include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0279] Certain embodiments are described in the present disclosure as including logic or multiple components or modules. A module may be a software module (e.g., code stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit that is capable of performing certain operations and may be configured or arranged in a particular manner. A hardware module may include a dedicated circuit system or logic that is permanently configured (e.g., as a dedicated processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) to perform certain operations. A hardware module may also include programmable logic or circuit systems (e.g., as contained within a general-purpose processor or other programmable processor) that are temporarily configured by software to perform certain operations. The decision to implement a hardware module in a dedicated and permanently configured circuit system or in a temporarily configured circuit system (e.g., configured by software) may be driven by cost and time considerations.

[0280] When implemented in software, the techniques may be provided as part of an operating system, a library used by multiple applications, a specific software application, etc. The software may be executed by one or more general-purpose processors or one or more special-purpose processors.

Claims

1. A method in a user equipment UE, the method comprising: receiving (906) a configuration including a first timing advance TA value and a second TA value for use in a serving cell from a radio access network RAN; receiving (908) from the RAN a spatial indication for communicating signals between the UE and the RAN; selecting (914) a TA value from among the first TA value and the second TA value based on the spatial indication; as well as The signal is communicated (922, 926) with the RAN using the selected TA value.

2. The method of claim 1, wherein: The first TA value is associated with a first transmission reception point (TRP) of a node in the RAN; and The second TA value is associated with a second TRP of the node in the RAN.

3. The method according to claim 1 or 2, wherein: The spatial indication includes a transmission configuration indication TCI state.

4. The method of claim 3, wherein the TCI is an uplink (UL) TCI state.

5. The method of claim 3, wherein the TCI is a joint TCI state.

6. A method as claimed in any one of the preceding claims, wherein: The first TA value is associated with a first TA group TAG; and The second TA value is associated with a second TAG.

7. The method of claim 6, further comprising, before receiving the spatial indication: receiving a configuration, the configuration comprising an indication that a first spatial indication corresponds to the first TAG and a second spatial indication corresponds to the second TAG; The selecting of the TA value comprises determining whether the received spatial indication is the first spatial indication or the second spatial indication.

8. The method of claim 7, wherein the configuration is included in a Radio Resource Control (RRC) message.

9. A method in a radio access network RAN, the method comprising: Sending a configuration including a first timing advance TA value and a second TA value for use in a serving cell to a user equipment UE; sending (564) from the RAN a spatial indication for communicating signals between the UE and the RAN, the spatial indication being associated with one of the first TA value or the second TA value; as well as The signal is communicated (576) with the UE according to the spatial indication.

10. The method of claim 9, wherein: The first spatial indication includes a first TCI state corresponding to a first TAG, the first TA value being associated with the first TAG; The second spatial indication includes a second TCI state corresponding to a second TAG, the second TA value being associated with the second TAG; and The sent spatial indication is one of the first spatial indication or the second spatial indication.

11. The method of claim 10, further comprising, prior to said sending of said spatial indication: A first association between the first TCI state and the first TAG and a second association between the second TCI state and the second TAG are configured to the UE.

12. The method of claim 11, wherein the configuration of the UE comprises: including the first association in a first RRC message; as well as The second association is included in a second RRC message.

13. The method of claim 11, wherein the configuration of the UE comprises: The first association and the second association are included in a shared RRC message.

14. The method of any one of claims 9 to 11, wherein the communicating of the signal with the UE comprises: An uplink (UL) transmission is received from the UE.

15. A device comprising: a transceiver configured to communicate with a radio interface; as well as Processing hardware configured to implement a method as claimed in any one of the preceding claims.

Images