Timing alignment management with multiple receivers in wireless communication systems

Abstract

The present invention provides a method or apparatus for managing the timing alignment of multiple receivers in a wireless communication system. [Solution] In order to manage synchronization, the user equipment receives a configuration from the radio access network (RAN) including a first timing advance (TA) value and a second TA value (606), operates a first TA timer (TAT) corresponding to the first TA value to manage the synchronization of a first uplink (UL) transmission with a first receiver in the RAN (608), operates a second TAT corresponding to the second TA value to manage the synchronization of a second UL transmission with a second UL receiver in the RAN (610), stops the first UL transmission in response to the expiration of the first TAT (612), and stops the second UL transmission in response to the expiration of the second TAT (614).

Description

Technical Field

[0001] Cross - reference to Related Applications This application claims priority to U.S. Provisional Patent Application No. 63 / 393,818, filed Jul. 29, 2022, entitled "MAINTAINING A TA VALUE IN A MULTIPLE - TRP SCENARIO IN A WIRELESS COMMUNICATION SYSTEM", and U.S. Provisional Patent Application No. 63 / 393,591, filed Jul. 29, 2022, entitled "MANAGING MULTIPLE TIMING ADVANCE VALUES FOR MULTIPLE TRANSMIT AND / OR RECEIVE POINTS". The entire contents of those provisional applications are hereby expressly incorporated by reference into this specification.

[0002] The present disclosure generally relates to wireless communication, and more specifically, to maintaining a TA value in a serving cell on the UE side or the NW / base station (BS) side, and / or supporting the update and expiration of a Time Alignment Timer (TAT). This technology can be applied to scenarios with multiple transmit and / or receive points (M - TRP).

Background Art

[0003] This description of the background art is provided for the purpose of generally indicating the background of the present disclosure. The work of the inventors specified in this specification is not admitted as prior art to the present disclosure, either expressly or implicitly, to the extent described in this background art section and in aspects of the description that may not qualify as prior art at the time of filing.

[0004] Generally speaking, base stations operating a cellular radio access network (RAN) communicate with user equipment (UEs) using multiple layers of specific radio access technologies (RATs) and protocol stacks. For example, the physical layer (PHY) of the RAT provides a transport channel to the Media Access Control (MAC) sublayer, which then provides a logical channel to the Radio Link Control (RLC) sublayer, which then provides data transfer services to the Packet Data Convergence Protocol (PDCP) sublayer. The Radio Resource Control (RRC) sublayer sits on top of the PDCP sublayer.

[0005] The RRC sublayer specifies the RRC_IDLE state, where the UE does not have an active radio connection with a base station; the RRC_CONNECTED state, where the UE has an active radio connection with a base station; and the RRC_INACTIVE state, which allows the UE to transition more quickly to and back to the RRC_CONNECTED state using Radio Access Network (RAN) level base station coordination and RAN level 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.

[0006] With respect to the PHY layer, different channel or reference signal (RS) configurations may, in some cases, correspond to different beam indication techniques. For most DL transmissions (e.g., physical downlink shared channel (PDSCH), physical downlink controlled channel (PDCCH), or channel state information (CSI) resource signal (CSI-RS)), the transmit configuration indication (TCI) framework and TCI states are applicable to and configured for such transmissions. However, in some cases, PDCCH transmissions require MAC-CE to further indicate TCI states within the configured TCI states, and PDSCH transmissions similarly require MAC-CE and downlink control information (DCI) for such transmissions. For physical uplink shared channels (PUSCH), UL beam indication depends on the index of a sounding reference signal (SRS) resource transmitted at least once by the UE. In some embodiments, for physical uplink controlled channels (PUCCH), MAC-CE indicates the spatial relationships for the UE to derive the UL beam. In further embodiments, spatial relationships are also configured in the SRS resource set, which represent the same UL beam applicable to all SRS resources within the SRS resource set. However, if many channels or RSs share the same beam, these messages may also require a significant amount of signaling overhead. [Overview of the Initiative]

[0007] An exemplary embodiment of the technology of the present disclosure is a method for managing synchronization, which is implemented in a user device (UE) and includes receiving a configuration from a radio access network (RAN) including a first timing advance (TA) value and a second TA value; operating a first TA timer (TAT) corresponding to the first TA value to manage the synchronization of a first uplink (UL) transmission with a first receiver in the RAN; operating a second TAT corresponding to the second TA value to manage the synchronization of a second UL transmission with a second receiver in the RAN; stopping the first UL transmission in response to the expiration of the first TAT; and stopping the second UL transmission in response to the expiration of the second TAT.

[0008] Another exemplary embodiment of these technologies is a user device (UE) comprising transceiver and processing hardware configured to implement the methods described above. [Brief explanation of the drawing]

[0009] [Figure 1A] This is a block diagram of an exemplary system in which distributed base stations and / or user equipment (UEs) can implement the technology of this disclosure. [Figure 1B] This is a block diagram of an exemplary base station, including a central unit (CU) and distributed units (DUs) of a distributed base station that can operate in the system shown in Figure 1A. [Figure 2A] Figures 1A and 1B are block diagrams of an exemplary protocol stack that allows the UE to communicate with the base station. [Figure 2B] Figures 1A and 1B show a block diagram of an exemplary protocol stack in which the UE can communicate with the DU and CU of the base station. [Figure 3A] This is a block diagram of the detailed structure of the various sublayers of the protocol stack shown in Figures 2A and / or 2B, including scheduling and / or priority handling functions. [Figure 3B]Similar to Figure 3A, this is a block diagram showing the detailed structure of the various sublayers of the protocol stack, including the logical channel prioritization function. [Figure 4A] This is a block diagram of a HARQ entity that includes multiple HARQ processes and communicates with transport channels to multiple TRPs. [Figure 4B] Similar to the block diagram in Figure 4A, this is a block diagram of HARQ entities, where the HARQ entities include multiple HARQ process groups associated with multiple transport channels to multiple TRPs. [Figure 4C] This block diagram is similar to the block diagram in Figure 4A, but it shows a HARQ entity communicating with a single TRP. [Figure 5A] This is a messaging diagram of an exemplary scenario in which the UE synchronizes with the first TRP and / or the second TRP in order to communicate with the base station. [Figure 5B] Similar to Figure 5A, this is a messaging diagram illustrating an exemplary scenario in which the UE receives UL and DL configuration parameters in separate wireless resource configuration messages. [Figure 5C] Similar to Figure 5A, this is a messaging diagram for an exemplary scenario in which the base station transmits UL configuration parameters to the UE via the second TRP instead of the first TRP. [Figure 5D] This is a messaging diagram for an exemplary scenario, similar to Figure 5A, but where the UE receives a response from the base station via the first TRP rather than via the second TRP while performing a random access procedure. [Figure 5E] Similar to Figure 5A, this is a messaging diagram for an exemplary scenario in which the UE receives the PDCCH order via the first TRP instead of the second TRP. [Figure 6]This is a flowchart illustrating an exemplary method in which the UE in Figure 1A and / or Figure 1B determines whether to stop sending the UL transmission associated with the first TA value or the second TA value, based on whether the UE detects that the first TAT or the second TAT has expired. [Figure 7A] Similar to Figure 6, this is an illustrative flowchart of a method in which, based on detection, the UE decides whether to flush the first or second set of HARQ buffers in the HARQ process. [Figure 7B] Similar to Figure 7A, this is a flowchart illustrating an exemplary method by which, based on detection, the UE decides whether to flush the HARQ buffers associated with the first and second TA values, or to refrain from flushing the HARQ buffers. [Figure 8A] Similar to Figure 6, this is a flowchart illustrating an exemplary method in which, based on detection, the UE determines whether to clear a configured UL grant associated with a first or second TA value. [Figure 8B] Similar to Figure 8A, this is a flowchart illustrating an exemplary method in which, based on detection, the UE decides whether to clear or refrain from clearing the configured UL grant associated with the first or second TA value. [Figure 9A] Similar to Figure 6, this is a flowchart illustrating an exemplary method by which, based on detection, the UE decides whether to release a PUCCH resource associated with the first or second TA value. [Figure 9B] Similar to Figure 9A, this is a flowchart illustrating an exemplary method by which, based on detection, the UE decides whether to release or refrain from releasing the PUCCH resources associated with the first and second TA values. [Figure 10A] Similar to Figure 6, this is a flowchart illustrating an exemplary method by which, based on detection, the UE decides whether to release the SRS resource associated with the first or second TA value. [Figure 10B] Similar to FIG. 10A, it is a flowchart of an exemplary method in which, based on detection, a UE determines whether to release an SRS resource associated with a first TA value and a second TA value, or whether to hold off on releasing the SRS resource. [Figure 11A] Similar to FIG. 6, it is a flowchart of an exemplary method in which, based on detection, a UE determines whether to clear a PUSCH resource for a CSI report associated with a first TA value or a second TA value. [Figure 11B] Similar to FIG. 11A, it is a flowchart of an exemplary method in which, based on detection, a UE determines whether to clear a PUSCH resource for a CSI report associated with a first TA value and a second TA value, or whether to hold off on clearing the PUSCH resource. [Figure 12A] Similar to FIG. 6, it is a flowchart of an exemplary method in which, based on detection, a UE determines whether to trigger a CBRA procedure associated with a first TA value or a second TA value. [Figure 12B] Similar to FIG. 12A, it is a flowchart of an exemplary method in which, based on detection, a UE determines whether to transmit a MAC CE indicating expiration of a first TA value or a second TA value. [Figure 12C] Similar to FIG. 12A, it is a flowchart of an exemplary method in which, based on detection, a UE determines whether to transmit an RRC message indicating expiration of a first TA value or a second TA value. [Figure 12D] Similar to FIG. 12A, it is a flowchart of an exemplary method in which, based on detection, a UE determines whether to transmit a PUCCH transmission indicating expiration of a first TA value or a second TA value. [Figure 12E] Based on whether the UE in FIG. 1A and / or FIG. 1B transmits one of the transmissions in FIGS. 12B to 12D indicating expiration of a first TA value or a second TA value, or whether the UE has detected expiration of a first TA value or a second TA value, it is a flowchart of an exemplary method for determining whether to trigger a CBRA procedure. [Figure 13] The flowchart of an exemplary method in which the UE in FIG. 1A and / or FIG. 1B receives a first TA value or a second TA value and starts or resumes a single TAT to maintain a first UL synchronization and a second UL synchronization with a base station. [Figure 14] The flowchart of an exemplary method in which the UE in FIG. 1A and / or FIG. 1B receives a first TA value and a delta value from a base station and subsequently determines a second TA value based on the first TA value and the delta value.

Mode for Carrying Out the Invention

[0010] The techniques described below can be applied to an M-TRP scenario that includes multiple timing advance (TA) values, and the UE maintains multiple TA values in at least one serving cell. The techniques described below enable the UE and / or the base station to maintain TA alignment in an M-TRP scenario. These techniques also enable the UE to indicate / update TA values for various TA operation frameworks (s). These techniques can be applied to LTE, NR, or any other suitable RAT.

[0011] Referring initially to FIG. 1A, an exemplary 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 can operate within a RAN 105 connected to a core network (CN) 110. The CN 110 can be implemented, for example, as an evolved packet core (EPC) 111 or a fifth generation (5G) core (5GC) 160. The CN 110 can also be implemented as a sixth generation (6G) core in another example.

[0012] Base station 104 can cover one or more cells (e.g., cells 124 and 125) at one or more transmit and / or receive points (TRPs), and base station 106 can similarly cover one or more cells (e.g., cell 126) at one or more TRPs. For example, base station 104 operates cell 124 at TRPs 107-1 and 107-2 and cell 125 at TRP 107-3, and base station 106 operates cell 126 at TRPs 108-1 and 108-2. Cells 124 and 125 operate at the same carrier frequency. Cell 126 may operate at the same carrier frequency as cells 124 and 125. Alternatively, cell 126 may operate at a different carrier frequency than cells 124 and 125. In some embodiments, base station 104 connects TRPs 107-1, 107-2, and 107-3, respectively, via fiber optic or Ethernet connections. 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 Evolutionary 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 can be in the same Radio Access Network Notice Area (RNA) or different RNAs. Generally, RAN 105 can contain any number of base stations, each of which can cover one, two, three, or any other appropriate number of cells. UE102 can support at least one 5G NR (or simply "NR") or E-UTRA air interface to communicate with base station 104 via TRP107-1, TRP107-2 and / or TRP-3. Similarly, UE102 can support at least one 5G NR (or simply "NR") or E-UTRA air interface to communicate with base station 106 via TRP108-1 and / or TRP108-2. Each of base stations 104 and 106 can connect to CN110 via an interface (e.g., S1 or NG interface).Base stations 104 and 106 can also be interconnected via an interface (e.g., an X2 or Xn interface) for interconnecting NG RAN nodes.

[0013] When a base station (e.g., base station 104 or 106) transmits DL data via a TRP (e.g., TRP107-1, TRP107-2, TRP107-3, TRP108-1, or TRP108-2), base station 104 can generate a packet containing the data and transmit the packet to TRP107-1. For example, the packet may be a fronthaul transport protocol data unit. The TRP extracts the data from the packet and transmits it. In some embodiments, 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 can transmit the data according to the control information. In some embodiments, the data includes in-phase and orthogonal (IQ) data, physical layer bit sequences, or MAC PDUs. When the TRP receives data from a UE (e.g., UE102), the TRP generates a packet containing the data and transmits the packet to base station 104. In some embodiments, the data includes IQ data, physical layer bit sequences, or MAC PDUs.

[0014] Among other components, the EPC111 may include a Serving Gateway (SGW)112, a Mobility Management Entity (MME)114, and a Packet Data Network Gateway (PGW)116. The SGW112 is typically configured to forward user plane packets related to voice calls, video calls, internet traffic, etc., and the MME114 is configured to manage authentication, registration, paging, and other related functions. The PGW116 provides connectivity from the UE102 to one or more external packet data networks (e.g., an internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network). The 5GC160 includes User Plane Functions (UPF)162, as well as Access and Mobility Management Functions (AMF)164, and / or Session Management Functions (SMF)166. Generally, UPF162 is configured to forward user plane packets related to voice calls, video calls, and internet traffic; AMF164 is configured to manage authentication, registration, paging, and other related functions; and SMF166 is configured to manage PDU sessions.

[0015] As shown in Figure 1A, base station 104 supports cells 124 and 125, and base station 106 supports cell 126. Cells 124, 125, and 126 can partially overlap, thereby allowing UE 102 to select, re-select, or pass between one of cells 124, 125, and 126. To directly exchange messages or information, base stations 104 and 106 can support X2 or Xn interfaces. In general, CN 110 can be connected to any appropriate number of base stations that support NR cells and / or EUTRA cells.

[0016] The base station 104 includes processing hardware 130, which may include one or more general-purpose processors (e.g., CPUs) and non-temporary computer-readable memory for storing instructions executed by the one or more general-purpose processors. Additionally or alternatively, the processing hardware 130 may include a special-purpose processing unit. The processing hardware 130 may include a PHY controller 132 configured to transmit data and control signals on a physical DL channel and DL reference signals via one or more TRPs (e.g., TRP107-1, TRP107-2 and / or TRP107-3) to one or more user devices (e.g., UE102). The PHY controller 132 is also configured to receive data and control signals on a physical UL channel and / or UL reference signals via one or more TRPs (e.g., TRP107-1, TRP107-2 and / or TRP107-3) to one or more user devices. In an exemplary embodiment, the processing hardware 130 includes a MAC controller 134 configured to perform random access (RA) procedures on one or more user devices, manage UL timing advances for one or more user devices, receive UL MAC PDUs from one or more user devices, and transmit 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 in 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.

[0017] UE102 includes processing hardware 150, which may include one or more general-purpose processors such as a CPU, non-temporary computer-readable memory for storing machine-readable instructions executable by one or more general-purpose processors, and / or a special-purpose processing unit. PHY controller 152 is also configured to receive data and control signals on the physical DL channel and / or DL ​​reference signals at base stations 104 or 106 via one or more TRPs (e.g., TRP107-1, TRP107-2, TRP107-3, TRP108-1 and / or TRP108-2). PHY controller 152 is also configured to transmit data and control signals on the physical UL channel and / or UL reference signals at base stations 104 or 106 via one or more TRPs (e.g., TRP107-1, TRP107-2, TRP107-3, TRP108-1 and / or TRP108-2). In an exemplary embodiment, the processing hardware 150 includes a MAC controller 154 configured to perform random access procedures at base stations 104 or 106, manage UL timing advances for one or more user devices, transmit UL MAC PDUs to base stations 104 or 106, and receive DL MAC PDUs from base stations 104 or 106. The processing hardware 150 may further include an RRC controller 156 to implement procedures and messaging in the RRC sublayer of the protocol communication stack.

[0018] Figure 1B shows exemplary distributed or centralized embodiments of one or both of the base stations 104 and 106. In this embodiment, each of the base stations 104 and / or 106 includes a central unit (CU) 172 and one or more distributed units (DUs) 174. The CU 172 includes processing hardware such as one or more general-purpose processors (e.g., CPUs), computer-readable memory for storing machine-readable instructions executable on the general-purpose processors, and / or special-purpose processing units. 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 embodiments, the CU 172 may include an RLC controller configured to manage or control one or more RLC operations or procedures. In other embodiments, the CU 172 does not include an RLC controller.

[0019] Each DU174 also includes processing hardware that may include one or more general-purpose processors (e.g., CPUs), computer-readable memory for storing machine-readable instructions executable on one or more general-purpose processors, and / or special-purpose processing units. For example, the processing hardware may include MAC controllers (e.g., MAC controllers 132, 142) configured to manage or control one or more MAC operations or procedures (e.g., random access procedures), and / or RLC controllers configured to manage or control one or more RLC operations or procedures. The processing hardware may also include physical layer controllers configured to manage or control one or more physical layer operations or procedures.

[0020] In some embodiments, RAN105 supports Integrated Access Backhaul (IAB) functionality. In some embodiments, DU174 acts as an IAB node and CU172 acts as an IAB donor.

[0021] In some embodiments, CU172 may include a logical node CU-CP172A that hosts the control plane portion of the PDCP protocol of CU172. CU172 may also include a logical node(s) CU-UP172B that hosts the user plane portion of the PDCP protocol and / or SDAP protocol of CU172. CU-CP172A can transmit control information (e.g., RRC messages, F1 application protocol messages), and CU-UP172B can transmit data packets (e.g., SDAP PDU or IP packets).

[0022] A CU-CP172A can connect to multiple CU-UP172Bs via the E1 interface. The CU-CP172A selects the appropriate CU-UP172B for the service requested by the UE102. In some embodiments, a single CU-UP172B can connect to multiple CU-CP172As via the E1 interface. If the CU-CP172A and DU(multiple)174 belong to a gNB, the CU-CP172A can connect to one or more DU(multiple)174s via the F1-C interface and / or the F1-U interface. If the CU-CP172A and DU(multiple)174 belong to an ng-eNB, the CU-CP172A can connect to DU(multiple)174s via the W1-C interface and / or the W1-U interface. In some embodiments, a single DU(174) can connect to multiple CU-UP172Bs under the control of the same CU-CP172A. In such an embodiment, connectivity between CU-UP172B and DU174 is established by CU-CP172A using bearer context management functionality.

[0023] Figure 2A shows a simplified exemplary protocol stack 200, which allows UE102 to communicate with an eNB / ng-eNB or gNB (e.g., one or both of base stations 104 and 106).

[0024] In an exemplary stack 200, the EUTRA physical layer (PHY) 202A provides a transport channel to the EUTRA MAC sublayer 204A, which then provides a logical channel to the EUTRA RLC sublayer 206A. The EUTRA RLC sublayer 206A then provides an RLC channel to the EUTRA PDCP sublayer 208, and possibly to the NR PDCP sublayer 210. Similarly, the NR PHY 202B provides a transport channel to the NR MAC sublayer 204B, which then provides a logical channel to the NR RLC sublayer 206B. The NR RLC sublayer 206B then provides data transfer services to the NR PDCP sublayer 210. The NR PDCP sublayer 210 can then provide data transfer services to the SDAP sublayer 212 or the RRC sublayer (not shown in Figure 2A). In some embodiments, the UE102 supports both EUTRA and NR stacks, as shown in Figure 2A, supports handover between EUTRA base stations and NR base stations, and / or supports dual connectivity (DC) via EUTRA and NR interfaces. Furthermore, as shown in Figure 2A, the UE102 can support layering of NR PDCP210 on EUTRA RLC206A and SDAP sublayer 212 on NR PDCP sublayer 210.

[0025] EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 receive packets that may be called SDUs (e.g., from the IP layer layered directly or indirectly on PDCP layer 208 or 210) and output packets that may be called PDUSs (e.g., to RLC layer 206A or 206B). For simplicity, in this disclosure, both SDUs and PDUs are referred to as “packets” unless the difference between SDUs and PDUs is relevant.

[0026] In the control plane, the EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 provide a signal-transmitting radio bearer (SRB) to the RRC sublayer (not shown in Figure 2A) to exchange, for example, RRC messages or NAS messages. In the user plane, the EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 provide a data radio bearer (DRB) to support data exchange. The data exchanged in the NR PDCP sublayer 210 may be SDAP PDUs, IP packets, or Ethernet packets.

[0027] Therefore, the radio protocol stack can be functionally divided as shown by the radio protocol stack 250 in Figure 2B. A CU located in one or both of base stations 104, 106 can hold all control and higher-layer functions (e.g., RRC214, SDAP212, NR PDCP210), while lower-layer operations (e.g., NR RLC206B, NR MAC204B, and NR PHY202B) are delegated to the DU. To support connection to 5GC, NR PDCP210 provides SRB to RRC214, NR PDCP210 provides DRB to SDAP212, and NR PDCP210 provides SRB to RRC214.

[0028] Figure 3A shows a detailed structure of the NR Layer 2 protocol stack 200 or 250A of base station 104 or 106. PHY 202 (not shown in Figure 3A) provides a transport channel to MAC sublayer 204. MAC sublayer 204 includes scheduling and / or priority handling functions for scheduling and / or prioritizing DL and UL transmissions with one or more user devices. MAC sublayer 204 also includes multiplexing functions for DL ​​transmissions with specific user devices and / or demultiplexing functions for UL transmissions. MAC sublayer 204 further includes hybrid automatic retransmission request (HARQ) entities for DL ​​transmissions and / or UL transmissions, respectively, with specific DL component carriers (CCs) and / or specific UL CCs with specific user devices. RLC sublayer 206 includes segmentation and automatic retransmission request (ARQ) functions for DL ​​and UL data communicating with one or more UEs. The PDCP sublayer 210 provides a wireless bearer to the SDAP sublayer 212, including (i) integrity protection and / or encryption / description, and (ii) security and (ii) robust header compression (ROHC) functions for header compression / decompression, respectively. The SDAP sublayer 212 provides 5GC QoS flow to the upper layer(s).

[0029] Figure 3B, similar to structure 300A, shows a detailed structure 300B of the NR Layer 2 protocol stack 200 or 250 for UE102. PHY202 (not shown in Figure 3B) provides the MAC sublayer 204 with transport channels for DL ​​and UL transmissions with base station(s) 104 or 106. MAC sublayer 204 includes one or more HARQ entities for DL ​​and / or UL transmissions with base station(s) 104 or 106 at specific DL CCs and / or specific UL CCs, respectively. MAC sublayer 204 also includes logical channel prioritization and multiplexing functions for UL transmissions to base station(s) 104 or 106, and demultiplexing functions for DL ​​transmissions from base station(s) 104 or 106. RLC sublayer 206 includes segmentation and automatic retransmission request (ARQ) functions for DL ​​and UL data communicating with base station(s) 104 and / or 106. The PDCP sublayer 210 provides a wireless bearer to the SDAP sublayer 212, including (i) integrity protection and / or encryption / description, and (ii) security and (ii) robust header compression (ROHC) functions for header compression / decompression, respectively. The SDAP sublayer 212 provides 5GC QoS flow to the upper layer(s).

[0030] Figures 4A to 4C illustrate different embodiments of the HARQ entity for multiple TRP (mTRP) operations on a specific CCy (e.g., UL CC or DL ​​CC), which may be implemented in UE102, base station 104 or 106, or DU174 on base station 104 or 106.

[0031] First, refer to Figure 4A, which shows the HARQ entity 400A. In some embodiments, the HARQ entity 400A includes HARQ processes 1, ..., N for communicating with TPRs 1, ..., m. N is an integer greater than zero, and m is an integer greater than zero. For example, N may be 8, 16, 32, etc., and m may be 2, 3, 4, etc.

[0032] Next, Figure 4B shows a further embodiment of HARQ entity 400B, similar to HARQ entity 400A. The difference between embodiments HARQ entity 400B and 400A is that HARQ entity 400B divides HARQ processes 1, ..., N into m groups, each used for communication with a specific TRP.

[0033] Next, Figure 4C shows an embodiment of HARQ entity 400C (e.g., HARQ entity k) similar to HARQ entity 400A. The difference between embodiments of HARQ entity 400C and 400A is that HARQ entity 400C is a specific TRP (e.g., TRP) on a specific CC (e.g., CCk, where 1 ≤ k ≤ m). k The purpose is to be used for communication with the RAN nodes (e.g., base stations 104 or 106, or DU174) via TRP1, ..., m on each ULCC, respectively. Similarly, the RAN nodes communicate with the UE102 via TRP1, ..., m on each RAN node (e.g., base stations 104 or 106, or DU174) via TRP1, ..., m on each DL CC, respectively.

[0034] Next, several exemplary scenarios related to mTRP operation, including the various components in Figure 1A, are described with reference to Figures 5A to 5E. In general, events in Figures 5A to 5E that may be the same are labeled with the same reference number.

[0035] Referring first to 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 one or more synchronization signal blocks (SSBs) 508, 510 and system information (504, 506) via TRP 107-1 (e.g., periodically). In some embodiments, the system information includes a Master Information Block (MIB) and / or System Information Block (SIB). In some examples, the SIB includes SIB1, and further includes SIB2, SIB3, SIB4, and / or SIB5. UE 102 initially operates in an idle state (e.g., RRC_IDLE state) (502). In the idle state, UE 102 receives SSBs from base station 104 via TRP 107-1 (504, 506) and system information (508, 510). In some embodiments, UE102 detects that base station 104 transmits an SSB via TRP107-1. In some embodiments, UE102 then uses one of the SSBs to perform downlink synchronization with base station 104 on cell 124 via TRP107-1 and receives system information via TRP107-1 based on the SSB (508, 510).

[0036] Subsequently, UE102 decides to perform the random access procedure (590) and the RRC connection establishment procedure (592). In response to this decision, UE102 transmits a first random access preamble 512 for time / frequency resources and / or random access channel (RACH) occasions to TRP107-1. TRP107-1 then forwards the first random access preamble to base station 104 (514). In some embodiments, UE102 selects an SSB from among SSBs whose RSRP obtained by UE102 exceeds a first threshold (e.g., rsrp-ThresholdSSB) for the random access procedure. In other embodiments, if the RSRP of any SSB within the SSBs does not exceed the first threshold, UE102 selects an SSB from among SSBs and uses that SSB to determine the first random access preamble. In some such cases, UE102 randomly selects an SSB from among SSBs or selects one based on the UE implementation. UE102 then determines a first random access preamble, a time / frequency resource, and / or a RACH occasion based on the selected SSB and random access configuration parameters included in the system information (e.g., SIB1). In some embodiments, the random access configuration parameters indicate (i) one or more associations between the SSB and (ii) a random access preamble, a RACH occasion, and / or a time / frequency resource. Based on the selected SSB and associations, UE102 determines the first random access preamble, a RACH occasion, and / or a time / frequency resource to which the first random access preamble is transmitted.

[0037] In response to the first random access preamble, base station 104 transmits a first random access response to TRP 107-1 (516). TRP 107-1 then forwards the first random access response to UE 102 (518). In some embodiments, base station 104 or TRP 107-1 identifies the SSB associated with the first random access preamble, RACH occasion, and / or time / frequency resource. In the case where a single SSB is associated with the first random access preamble, RACH occasion, and / or time / frequency resource, the identified SSB is the SSB selected by UE 102. If multiple SSBs are associated with the first random access preamble, RACH occasion, and / or time / frequency resource, the identified SSB is either identical to or different from the SSB selected by UE 102. In such an embodiment, base station 104 transmits a first random access response to UE 102 via TRP 107-1 based on the identified SSB. Base station 104 includes a first preamble ID and a 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, after applying the first TA value (e.g., in response thereto), determines or maintains an uplink synchronized with TRP 107-1 (e.g., time-matched) (520). UE 102 applies the first TA value to transmit UL transmissions (e.g., PUCCH transmissions, PUSCH transmissions, and / or sounding reference signal transmissions) until it receives a new or different TA value from base station 104 that updates the first TA value. In some embodiments, UE102 initiates a first time alignment timer (TAT) to maintain UL synchronization status with TRP107-1 or base station 104 after or when it receives a first TA command. In some embodiments, base station 104 includes a UL grant (i.e., a RAR grant) in its random access response.

[0038] In some embodiments, after the base station 104 sends a random access response or a first TA command to the UE 102, it initiates a first TAT to maintain a first UL synchronization for UL and / or DL ​​communication with the UE 102 via the TRP 107-1. In some embodiments, the TRP 107-1 generates timing information of the first random access preamble received from the UE 102, or timing information based on the first random access preamble received from the UE 102, and transmits the timing information to the base station 104. In some embodiments, the timing information indicates a propagation delay or propagation delay shift. Based on the timing information received from the TRP 107-1, the base station 104 determines a first TA value.

[0039] Blocks 512, 514, 516, 518, and 520 are collectively referred to as random access procedure 590 in Figure 5A.

[0040] During or after the random access procedure 590, UE 102 sends an RRC setup request message (e.g., an RRCSetupRequest message) to the base station via TRP 107-1 (522, 524). In some embodiments, 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, base station 104 sends an RRC setup message (e.g., an RRCSetup message) to UE 102 via TRP 107-1 (526, 528). In some embodiments, base station 104 resolves the random access procedure conflict by sending a MAC PDU containing conflict resolution (e.g., MAC control element (CE)) to UE 102. In some embodiments, base station 104 includes the RRC setup message in the MAC PDU. In further embodiments, after sending the MAC PDU, base station 104 sends another MAC PDU containing the RRC setup message to UE 102. In response to the RRC setup message, UE102 transitions to a connected state (e.g., RRC_CONNECTED) (530) and sends an RRC setup complete message (e.g., an RRCSetupcomplete message) to base station 104 via TRP107-1 (532, 534). In some embodiments, after performing the RRC connection establishment procedure with UE102, base station 104 performs a security activation procedure on UE102 to activate security protection (e.g., integrity protection / integrity check and encryption / decryption) for UL data and DL data communicated between UE102 and base station 104. In further embodiments, after performing the RRC connection establishment procedure or security activation procedure, base station 104 performs a radio bearer configuration procedure with UE102 to configure SRB2 and / or DRB on UE102.

[0041] After performing the RRC connection establishment procedure, security activation procedure, or radio bearer configuration procedure, base station 104 sends an RRC reconfiguration message (e.g., an RRCReconfiguration message) to UE 102 via TRP 107-1, which includes the channel state information (CSI) resource configuration and the CSI reporting configuration (536, 538). In response, UE 102 sends an RRC reconfiguration complete message (e.g., an RRCReconfigurationComplete message) to base station 104 via TRP 107-1 (540, 542). In some embodiments, the CSI resource configuration includes configuration parameters that constitute the channel state information reference signal (CSI-RS) that UE 102 measures. Base station 104 transmits the CSI-RS via TRP 107-2 according to the CSI resource configuration. UE 102 performs the measurement on the CSI-RS according to the CSI resource configuration. In some embodiments, the CSI resource configuration includes configuration parameters that constitute the SSB for UE 102 to measure. Base station 104 transmits the SSB via TRP107-2. UE102 performs measurements on the SSB according to the CSI resource configuration. In other embodiments, the RRC reconfiguration message or CSI resource configuration does not include the configuration parameters that make up the SSB. In some such cases, base station 104 still transmits the SSB via TRP107-2, and UE102 performs measurements on the SSB. Based on the CSI reporting configuration, UE102 generates a CSI report from the CSI-RS or SSB measurements and transmits the CSI report to base station 104 via TRP107-1 (544, 546). In some embodiments, UE102 transmits the CSI report on PUCCH to base station 104 via TRP107-1. In some embodiments, the CSI reporting configuration constitutes periodic or semi-persistent reporting, or the CSI reporting configuration constitutes semi-persistent or aperiodic reporting triggered by DCI. CSI reporting includes periodic CSI reporting, semi-persistent CSI reporting, and / or aperiodic CSI reporting.

[0042] In some embodiments, base station 104 includes a CSI resource configuration and / or CSI report configuration in the CSI measurement configuration (e.g., CSI-MeasConfigIE). Base station 104 then includes the CSI measurement configuration in the RRC reconfiguration message for events 536, 538. In other embodiments, the CSI resource configuration includes NZP-CSI-RS-ResourceIE, NZP-CSI-RS-ResourceSetIE, CSI-SSB-ResourceSetIE, CSI-ResourceConfigIE, and / or CSI-ReportConfigIE.

[0043] Blocks 536, 538, 540, 542, 544, and 546 are collectively referred to as CSI Resource Configuration and CSI Reporting Procedure 594 in Figure 5A.

[0044] After receiving the CSI report in event 546, base station 104 decides to communicate with UE 102 via TRP 107-2 based on the CSI report, while maintaining the link with UE 102 via TRP 107-1. In some embodiments, base station 104 makes the decision based on the capabilities of one or more UE 102. In response to the decision, base station 104 sends an RRC reconfiguration message to UE 102 via TRP 107-1, which includes DL and UL configuration parameters for DL ​​and UL communication with base station 104 via TRP 107-2, respectively (548, 550). In some embodiments, base station 104 includes the DL and UL configuration parameters in CellGroupConfigIE and includes CellGroupConfigIE in the RRC reconfiguration message. In some embodiments, base station 104 includes DL configuration parameters such as BWP-DownlinkDedicatedIE in Bandwidth Part (BW)IE and includes BWP-DownlinkDedicatedIE in the RRC reconfiguration message. In some embodiments, base station 104 includes UL configuration parameters in the BWP-UplinkDedicatedIE and includes the BWP-UplinkDedicatedIE in the RRC reconfiguration message.

[0045] In response to the RRC reconfiguration complete message, UE102 transmits the RRC reconfiguration complete message to base station 104 via TRP107-1 (552, 554). In some embodiments, upon receiving the RRC reconfiguration message in event 554, UE102 applies DL configuration parameters. In such embodiments, UE102 performs DL and UL communication with base station 104 via TRP107-2 according to the DL configuration parameters while performing DL and UL communication with base station 104 via TRP107-1 (556). In some embodiments, UE102 refrains from performing UL communication according to the UL configuration parameters until after performing a random access procedure with base station 104 via TRP107-2 in event 598. In further embodiments, UE102 refrains from performing DL communication with base station 104 via TRP107-2 until after performing a random access procedure with base station 104 via TRP107-2 in event 598. In some embodiments, base station 104 refrains from performing UL communication and / or configuring UL configuration parameters until after completing a random access procedure with base station 104 via TRP 107-2 in event 598. In some embodiments, base station 104 refrains from performing DL communication and / or configuring DL configuration parameters until after completing a random access procedure with base station 104 via TRP 107-2 in event 598.

[0046] In some embodiments, base station 104 and UE 102 perform DL communication with base station 104 via TRP 107-1 and TRP 107-2 in event 556, using the HARQ entities in Figure 4A, Figure 4B, or Figure 4C. In the case of HARQ entity 400B in Figure 4B, for example, the DL configuration parameters in events 548 and 550 include HARQ configuration parameters. The HARQ configuration parameters constitute a first set of HARQ process IDs and a second set of HARQ process IDs. In some cases, the first set of HARQ process IDs and the second set of HARQ process IDs are for TRP 107-1 and TRP 107-2, respectively. The first set of HARQ process IDs and the second set of HARQ process IDs identify a first set of HARQ processes and a second set of HARQ processes for the HARQ entity, respectively. In some embodiments, the first set of HARQ process IDs and the second set of HARQ process IDs are not identical. In other embodiments, some parts of the first set of HARQ process IDs and the second set of HARQ process IDs are identical, while others are different.

[0047] In some embodiments, base station 104 transmits one or more MAC control elements (CEs) or DCIs to UE 102 to modify or update one or more HARQ process IDs in a first set of HARQ process IDs. In some embodiments, base station 104 transmits one or more MAC CEs or DCIs to UE 102 to modify or update one or more HARQ process IDs in a second set of HARQ process IDs. In some alternative embodiments, base station 104 does not configure a first set of HARQ process IDs and a second set of HARQ process IDs in the DL configuration parameters. In some embodiments, base station 104 determines a first set of HARQ process IDs and a second set of HARQ process IDs for mTRP operation based on preconfiguration. In further embodiments, the first set of HARQ process IDs and the second set of HARQ process IDs are unique predetermined IDs (for example, as defined in a 3GPP® specification). In a further embodiment, the base station 104 determines a first set of HARQ process IDs and a second set of HARQ process IDs based on a rule.

[0048] In some embodiments, when base station 104 decides to schedule UE 102 to receive a DL transmission to TRP 107-1, base station 104 selects a HARQ process ID from a first set of HARQ process IDs and sends a DCI including the DL allocation, along with the selected HARQ process ID, to UE 102. UE 102 uses the HARQ process identified by the selected HARQ process ID and receives the DL transmission from base station 104 using the HARQ process and the UL grant. Similarly, when base station 104 decides to schedule UE 102 to send a UL transmission to TRP 107-2, base station 104 selects a HARQ process ID from a second set of HARQ process IDs and sends a DCI including the UL grant, along with the selected HARQ process ID, to UE 102. UE 102 uses the HARQ process identified by the selected HARQ process ID and receives the DL transmission from base station 104 using the HARQ process and the DL grant.

[0049] In some embodiments, one or more capabilities include at least one capability indicating that UE102 supports mTRP operation (e.g., Release 16 capability fields / IE and / or Release 17 capability fields / IE in 3GPP specification 38.306 or 38.331 v17.1.0 or later versions for mTRP operation). In some embodiments, base station 104 decides to configure DL configuration parameters for DL ​​communication with base station 104 via TRP107-2 based on at least one first capability. In some embodiments, base station 104 decides UL configuration parameters for UL communication with base station 104 via TRP107-2 based on at least one first capability. In cases where base station 104 includes DU174 and CU172, DU174 makes the decision.

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

[0051] In some embodiments, the base station 104 receives one or more capabilities from the UE 102 after receiving an RRC setup complete message or after performing a security activation procedure with the UE 102. In some embodiments, the base station 104 sends a UE capability inquiry message (e.g., a UECapabilityEnquiry message) to the UE 102 and, in response, receives a UE capability information message (e.g., a UECapabilityinfo message) from the UE containing one or more capabilities.

[0052] In other embodiments, base station 104 receives a CN-to-BS message from CN110 containing one or more capabilities (for example, after receiving an RRC setup complete message). In some embodiments, base station 104 sends a BS-to-CN message to CN110 after receiving an RRC setup complete message, and CN110 sends a CN-to-BS message after receiving a BS-to-CN message (for example, in response to the reception). In some embodiments, UE 102 sends a NAS message (for example, a Registration Request message or a Registration Complete message) to CN110 containing capability IDs that identify one or more capabilities, and CN110 retrieves one or more capabilities from the capability IDs. In other embodiments, UE 102 performs a registration procedure with CN110 via a base station (for example, base station 104 or 106) before event 502 which registers with CN110. During the registration procedure, UE102 receives a UE capability inquiry message (e.g., a UECapabilityEnquiry message) from the base station and sends a UE capability information message (e.g., a UECapabilityinfo message) containing one or more capabilities to the base station. The base station sends a BS-to-CN message containing one or more capabilities to CN110, which stores one or more capabilities. In some embodiments, the CP-to-BS message and the BS-to-CN message are NG Application Protocol (NGAP) messages. In the case where base station 104 includes DU174 and CU172, CU172 sends a CU-to-DU message containing one or more capabilities to DU174. In some embodiments, the CU-to-DU message is an F1 Application Protocol (F1AP) message.

[0053] In some embodiments, base station 104 may include random access configuration parameters in the RRC reconfiguration message for UE 102 to perform a random access procedure (598). In some embodiments, the random access configuration parameters are specific to UE 102. For example, base station 104 generates a RACH configuration (e.g., RACH-ConfigDedicated, RACH-ConfigDedicated-r18, or RACH-ConfigDedicated-v1800IE) that includes random access configuration parameters specific to UE 102. In some embodiments, the format of the RRCReconfiguration message includes a ReconfigurationWithSync IE, which includes a RACH-ConfigDedicatedIE (e.g., a RACH configuration or random access configuration parameters) (as specified in, for example, 3GPP specification 38.331v17.0.0 or later). In cases where the RRC reconfiguration message is an RRCReconfiguration message, base station 104 includes RACH configuration or random access configuration parameters for the RRCReconfiguration message in the RRCReconfiguration message, and these parameters do not include a ReconfigurationWithSync IE, and the ReconfigurationWithSync IE does not wrap the RACH configuration or random access configuration parameters. If base station 104 includes random access configuration parameters using a ReconfigurationWithSync IE, the ReconfigurationWithSync IE causes UE 102 to perform a handover, which interrupts communication between UE 102 and base station 104. In other embodiments, base station 104 refrains from including random access configuration parameters in the RRC reconfiguration message.

[0054] In some embodiments, base station 104 indicates in the RRC reconfiguration message that UL synchronization is required (i.e., for communication with base station 104 via a second TRP). That is, base station 104 configures UE 102 to acquire (second) UL synchronization for communication between UE 102 and TRP 107-1 while maintaining a first UL synchronization for communication between UE 102 and TRP 107-2. In other words, base station 104 configures the UE to maintain 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). In further embodiments, base station 104 includes a configuration (e.g., a field or IE (e.g., RRC release 18 field or IE)) in the RRC reconfiguration message indicating that UL synchronization is required for communication between UE 102 and TRP 107-2. In other words, this configuration allows for the manipulation of two TA values ​​for communication between UE102 and base station 104 (for example, between UE102 and TRP107-1, and between UE102 and TRP107-2, respectively).

[0055] In some embodiments, UE102 initiates a random access procedure in response to receiving a field or IE, before sending a UL transmission (e.g., a Channel Status Information (CSI) report, a Sounding Reference Signal (SRS), a PUCCH transmission, and / or a PUSCH transmission) to the base station via TRP107-2 (598). In some such embodiments, if the RRC reconfiguration message does not contain a field or IE, UE102 does not initiate a random access procedure and sends a UL transmission to the base station via TRP107-2. In further embodiments, UE102 refrains from sending a UL transmission to the base station via TRP107-2 in response to receiving a field or IE. In some such cases, UE102 does not send a random access preamble to base station 104 via TRP107-2 until it receives a PDCCH order (e.g., events 558, 560, 559, 561) from the base station.

[0056] Blocks 548, 550, 552, 554, and 556 are collectively referred to as TRP configuration procedure 596A in Figure 5A.

[0057] In some embodiments, after receiving the RRC reconfiguration message in event 538, after performing the CSI resource configuration and CSI reporting procedure 594, or after performing the TRP configuration procedure 596A with base station 104, UE 102 receives RS from base station 104 via TRP 107-2 (562, 564). Depending on the embodiment, the RS consists of the CSI resource configuration in event 538, and events 562, 564 occur after receiving the RRC reconfiguration message in event 538, during or after the CSI resource configuration and CSI reporting procedure 594, or during or after the TRP configuration procedure 596A. After performing the TRP configuration procedure 596A with base station 104, UE 102 initiates the random access procedure (598). In response to initiating a random access procedure, UE102 transmits a second random access preamble to base station 104 via TRP107-2, specifying the time / frequency resources and random access channel (RACH) occasion (566, 568). In response to the second random access preamble, base station 104 transmits a second random access response to UE102 via TRP107-2 (570, 572). In the second random access response, base station 104 includes a second preamble ID and a second TA command. 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, after applying the second TA value (for example, in response thereto), determines or maintains an uplink synchronized with TRP107-2 (574). UE102 applies the second TA value and sends UL transmissions (e.g., PUCCH transmissions, PUSCH transmissions, and / or SRS transmissions) until UE102 receives a new or different TA value from base station 104 that updates the second TA value. In some embodiments, UE102 initiates a second TAT to maintain or manage the UL synchronization status with TRP107-2 or base station 104 after receiving or when receiving the second TA command.In some embodiments, base station 104 includes a UL grant (e.g., a RAR grant) in the second random access response, and UE 102 transmits a UL MAC PDU to base station 104 via TRP 107-2 according to the UL grant. In the case where the random access procedure is a competition-based random access procedure, UE 102 includes UE 102's C-RNTI in the UL MAC PDU. Base station 104 identifies UE 102 based on the C-RNTI. In response to this identification, base station 104 generates a DCI and a CRC of the DCI, scrambles the CRC with the C-RNTI, and transmits the DCI and the scrambled CRC to UE 102 via PDCCH. In some embodiments, the DCI includes an nUL grant. Upon receiving the DCI and the scrambled CRC via PDCCH, UE 102 determines that the content-based random access procedure 598 has been successfully executed. In the case where random access procedure 598 is a random access procedure without conflicts, UE102 determines that the content-based random access procedure 598 has executed successfully in response to receiving a second random access response message.

[0058] In some embodiments, the base station 104 initiates a second TAT and, after sending a second TA command to the UE 102 (for example, in response thereto), maintains a second UL synchronization for UL and / or DL ​​communication with the UE 102 via the TRP 107-2. In some embodiments, the TRP 107-1 generates timing information for the second random access preamble received from the UE 102 and transmits the timing information to the base station 104. As an example, the timing information indicates a propagation delay or propagation delay shift. Based on the timing information received from the TRP 107-1, the base station 104 determines a second TA value.

[0059] Blocks 566, 568, 570, 572, and 574 are collectively referred to as random access procedure 598 in Figure 5A.

[0060] In some embodiments, UE102 pauses communication with base station 104 via TRP107-1 (e.g., receiving DL channel / RS or transmitting UL channel / RS) while executing random access procedure 598. Depending on the embodiment, UE102 pauses communication if it is unable to simultaneously execute random access procedures based on a UL beam or RS (i.e., toward a TRP) and is unable to communicate UL and DL transmissions (i.e., unrelated to the random access procedure) based on another UL beam or RS (i.e., toward another TRP). In other embodiments, UE102 continues communication with base station 104 via TRP107-2 while executing random access procedure 598. After successfully completing the random access procedure (598), UE performs DL and UL communication with base station 104 via TRP107-1 and TRP107-2 according to a first TA value and a second TA value, respectively (576).

[0061] In some embodiments, base station 104 and UE 102 perform UL communication with base station 104 via TRP 107-1 and TRP 107-2 in event 576 using HARQ entities (for example, as shown in Figures 4A, 4B, or 4C). In some cases (for example, in the case of the exemplary HARQ entities in Figure 4B), the UL configuration parameters for events 548 and 550 include HARQ configuration parameters. The HARQ configuration parameters constitute a first set of HARQ process IDs and a second set of HARQ process IDs. In some cases, the first set of HARQ process IDs and the second set of HARQ process IDs are for TRP 107-1 and TRP 107-2, respectively. The first set of HARQ process IDs and the second set of HARQ process IDs identify a first set of HARQ processes for the HARQ entity and a second set of HARQ processes for the HARQ entity, respectively. In some embodiments, neither the first set of HARQ process IDs nor the second set of HARQ process IDs are identical. In other embodiments, some parts of the first set of HARQ process IDs and the second set of HARQ process IDs are identical, while others are different.

[0062] In some embodiments, base station 104 transmits one or more MAC CEs or DCIs to UE 102 to modify or update one or more HARQ process IDs in a first set of HARQ process IDs. In some further embodiments, base station 104 transmits one or more MAC CEs or DCIs to UE 102 to modify or update one or more HARQ process IDs in a second set of HARQ process IDs. In some alternative embodiments, base station 104 does not configure a first set of HARQ process IDs and a second set of HARQ process IDs in the UL configuration parameters. In some embodiments, base station 104 determines a first set of HARQ process IDs and a second set of HARQ process IDs for mTRP operation based on preconfiguration. In further embodiments, the first set of HARQ process IDs and the second set of HARQ process IDs are defined sets (e.g., as defined in the 3GPP specification). Furthermore, in a further embodiment, the base station 104 determines a first set of HARQ process IDs and a second set of HARQ process IDs based on rules.

[0063] In some embodiments, when base station 104 decides to schedule UE 102 to receive a UL transmission to TRP 107-1, base station 104 selects a HARQ process ID from a first set of HARQ process IDs and transmits the DCI containing the UL grant and the selected HARQ process ID to UE 102. UE 102 uses the HARQ process identified by the selected HARQ process ID and transmits the UL transmission to base station 104 using the HARQ process and the UL grant. Similarly, when base station 104 decides to schedule UE 102 to transmit a UL transmission to TRP 107-2, base station 104 selects a HARQ process ID from a second set of HARQ process IDs and transmits the DCI containing the UL grant and the selected HARQ process ID to UE 102. UE 102 uses the HARQ process identified by the selected HARQ process ID and transmits the UL transmission to base station 104 using the HARQ process and the UL grant.

[0064] In some embodiments, after receiving the RRC reconfiguration complete message in event 554, base station 104 sends a PDCCH order to UE 102 via TRP 107-2 (558, 560) to cause UE 102 to initiate the random access procedure 598 together with base station 104 via TRP 107-2. In some embodiments, the PDCCH order includes the RS index and the random access preamble index. Alternatively, base station 104 sends the PDCCH order to UE 102 via TRP 107-1. In response to the PDCCH order, UE 102 sends the random access preamble to base station 104 via TRP 107-2 in event 566. In some embodiments, the random access preamble index includes the value of a second preamble ID that identifies a second random access preamble. Thus, UE 102 determines the second random access preamble according to the random access preamble index. In other embodiments, the random access preamble index includes a value that indicates or instructs UE102 to determine a random access preamble. Thus, UE102 determines a second random access preamble by (randomly) selecting a second random access preamble from the random access preamble configured in the system information.

[0065] In some embodiments, the PDCCH order is DCI. Base station 104 generates DCI and the CRC of DCI, scrambles the CRC with C-RNTI, and transmits DCI and the scrambled CRC to TRP 107-2 (e.g., over a fiber connection). TRP 107-2 then transmits DCI and the scrambled CRC to UE 102 in PDCCH. In some embodiments, base station 104 transmits a first packet containing DCI and the scrambled CRC to TRP 107-2. In some embodiments, base station 104 transmits control information to TRP 107-2 that constitutes or indicates the time resources and / or frequency resources of the PDCCH. In some embodiments, the time resources and / or frequency resources include subcarriers, resource elements, or physical resource blocks. TRP 107-2 transmits DCI and the scrambled CRC in the time resources and / or frequency resources according to the control information. In some embodiments, base station 104 includes control information in the first packet. In other embodiments, base station 104 transmits a second packet containing control information to TRP 107-2 instead of the first packet. In other embodiments, base station 104 does not transmit DCI and scrambled CRC control information to TRP 107-2. In such embodiments, TRP 107-2 determines the time and / or frequency resources of the PDCCH and transmits DCI and scrambled CRC over the time and / or frequency resources.

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

[0067] In other embodiments, the RS index (e.g., the CSI-RS index) identifies one of the CSI-RSs. In some embodiments, base station 104 determines or decodes the CSI-RS index shown in the CSI report. In further embodiments, base station 104 determines or decodes the CSI-RS index based on the radio resource (e.g., the PUCCH resource) from which base station 104 receives CSI reports about the CSI-RS. In some such embodiments, base station 104 configures different radio resources for UE 102 and transmits a CSI report for each of the CSI-SSBs. In some examples, base station 104 includes configuring different radio resources (e.g., the PUCCH resource) for UE 102 so as to transmit a CSI report for each of the CSI-SSBs in the RRC reconfiguration message of event 536. In some embodiments, UE102 determines the time resource / frequency resource and / or RACH occasion based on the CSI-RS (e.g., indicated by the RS index) and random access configuration parameters in the RRC reconfiguration message received by UE102 in event 550. UE102 sends a second random access preamble to the time resource / frequency resource and / or RCH occasion. In some embodiments, the random access configuration parameters indicate one or more associations between the CSI-RS, RACH occasion and / or time resource / frequency resource.

[0068] In some embodiments, UE102 determines transmit characteristics (e.g., spatial transmit filter / parameters) based on or by reference to the RS index in PDCCH order, and transmits a second random access preamble to TRP107-2 using the determined transmit characteristics. In some examples, UE102 derives transmit characteristics using receive characteristics for receiving (564) RS identified by the RS index. In some embodiments, transmit characteristics include phase, power, and / or transmit precoder. In some embodiments, UE102 further uses DL and / or UL configuration parameters of event 550 to determine transmit characteristics. In further embodiments, UE102 uses configuration parameters in system information of event 510 to determine transmit characteristics. In some embodiments, UE102 determines transmit characteristics (e.g., spatial transmit filter / parameters) without relying on or referencing the RS index in PDCCH order, and transmits a second random access preamble to TRP107-2 using the determined transmit characteristics.

[0069] In some embodiments, UE102 initiates the random access procedure (598) after receiving RS in event 564, in response to the random access configuration parameters received in event 550. In such embodiments, base station 104 does not send a PDCCH order, allowing UE102 to perform the random access procedure 598.

[0070] In some embodiments, 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 UE102 to receive DL transmissions from TRP107-2. In some embodiments, UE102 receives a second random access response according to the configuration parameters. In other embodiments, the system information of event 510 includes configuration parameters for UE102 to receive a random access response from TRP107-2. In such embodiments, UE102 receives a second random access response according to the configuration parameters. In some embodiments, UE102 receives a second random access response from TRP107-2 using a receive characteristic for receiving RS (564).

[0071] Although TRP107-2 is used in Scenario 500A, the above description can be applied to scenarios in which TRP107-3 is used instead of TRP107-2. In such a scenario, after successfully completing the random access procedure with the base station via TRP107-3 and cell 125, the UE performs DL and UL communications with the base station via TRP107-1 and TRP107-3 according to the first TA value and the second TA value, respectively, as in Procedure 598.

[0072] In some scenarios or embodiments, base station 104 transmits a third TA command to UE 102 via TRP 107-1 or TRP 107-2, which includes a first new TA value to update the first TA value. In some embodiments, the third TA command is a MAC control element (CE). UE 102 applies the first new TA value to the first UL synchronization and restarts the first TAT of UE 102 in response to receiving the third TA command. Base station 104 restarts the first TAT of base station 104 in response to transmitting the third TA command. In some scenarios or embodiments, base station 104 transmits a fourth TA command to UE 102 via TRP 107-1 or TRP 107-2, which includes a second new TA value to update the second TA value. In some embodiments, the fourth TA command is a MAC CE. UE102 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 embodiments, base station 104 sends a single TA command containing the first new TA value and the second new TA value to UE102 via TRP107-1 or TRP107-2 to update the first and second TA values, respectively. In some embodiments, the single TA command is a new or existing MAC control element (CE) (as defined, for example, in 3GPP specification 38.321 V17.1.0).

[0073] In some embodiments, TRP107-1 generates timing information based on UL transmissions received from UE102 and transmits the timing information to base station 104. In some embodiments, the timing information indicates propagation delay or propagation delay shift. Based on the timing information received from TRP107-1, base station 104 decides whether to update the first TA value. In some embodiments, if the propagation delay or propagation delay shift is greater than or equal to a first threshold, base station 104 decides to update the first TA value. Otherwise, if the propagation delay or propagation delay shift is less than a second threshold, base station 104 decides not to update the first TA value. In some embodiments, if base station 104 decides to update the first TA value, base station 104 generates a first new TA value. In some embodiments, TRP107-2 generates timing information based on UL transmissions received from UE102 and transmits the timing information to base station 104. In some embodiments, the timing information indicates propagation delay or propagation delay shift. Based on the timing information received from TRP107-2, base station 104 decides whether to update the second TA value. In some embodiments, if the propagation delay or propagation delay shift is greater than or equal to a third threshold, base station 104 decides to update the second TA value. Otherwise, if the propagation delay or propagation delay shift is less than a fourth threshold, base station 104 decides not to update the first TA value. In some embodiments, if base station 104 decides to update the second TA value, base station 104 generates a second new TA value. Depending on the embodiment, the first, second, third, and fourth thresholds may be the same or different.

[0074] Referring to Figure 5B, Scenario 500B is similar to Scenario 500A, but with differences which are described below. In Scenario 500B, base station 104 sends an RRC reconfiguration message to UE 102 via TRP 107-1 that includes DL configuration parameters for DL ​​communication with base station 104 via TRP 107-2 (549, 551). In some embodiments, base station 104 includes UL configuration parameters for UL communication with base station 104 via TRP 107-1 in the RRC reconfiguration message (for example, to configure or enable DL communication with base station 104 via TRP 107-2). In some embodiments, base station 104 includes DL configuration parameters in CellGroupConfigIE and includes CellGroupConfigIE in the RRC reconfiguration message. In some embodiments, base station 104 includes DL configuration parameters in BWP-UplinkDedicatedIE and includes BWP-UplinkDedicatedIE in the RRC reconfiguration message. The RRC reconfiguration messages for events 549 and 551 are similar to the RRC reconfiguration messages for events 548 and 550, except that base station 104 excludes or refrains from including UL configuration parameters in the RRC reconfiguration messages for events 549 and 551 for UL communication with base station 104 via TRP 107-2. Instead, base station 104 sends another RRC reconfiguration message to UE 102 via TRP 107-1 that includes UL configuration parameters for UL communication with base station 104 via TRP 107-2 (578, 580). In response, UE 102 sends an RRC reconfiguration complete message to base station 104 via TRP 107-1 (582, 584). In some embodiments, base station 104 includes UL configuration parameters in CellGroupConfigIE and includes CellGroupConfigIE in the RRC reconfiguration messages for events 578 and 580. In some embodiments, base station 104 includes UL configuration parameters in the BWP-UplinkDedicatedIE and includes the BWP-UplinkDedicatedIE in the RRC reconfiguration message.

[0075] Blocks 549, 551, 552, 554, 556, 578, 580, 582, and 584 are collectively referred to as TRP configuration procedure 596B in Figure 5B. After receiving the RRC reconfiguration message in event 538, after performing CSI resource configuration and CSI reporting procedure 594, or after performing TRP configuration procedure 596B with base station 104, UE 102 receives RS from base station 104 via TRP 107-2 (562, 564). After performing TRP configuration procedure 596A with base station 104, UE 102 performs a random access procedure with base station 104 via TRP 107-2 (598).

[0076] Next, referring to Figure 5C, Scenario 500C is similar to Scenarios 500A and 500B, with the differences described below.

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

[0078] Blocks 549, 551, 552, 554, 556, 579, 581, 582, and 584 are collectively referred to as TRP configuration procedure 596C in Figure 5C.

[0079] Next, referring to Figure 5D, Scenario 500D is similar to Scenarios 500A, 500B, and 500C, with the differences described below.

[0080] After UE102 has performed TRP configuration procedures 596A, 596B, or 596C with base station 104, UE102 initiates the random access procedure (599). In response to the initiation, UE102 sends a second random access preamble to base station 104 via TRP107-2 (566, 568). In response, base station 104 sends a second random access response to UE102 via TRP107-1 instead of TRP107-2 (571, 573).

[0081] Next, referring to Figure 5E, Scenario 500E is similar to Scenarios 500A, 500B, 500C, and 500D, with the differences described below.

[0082] In some embodiments, after receiving the RRC reconfiguration complete message in event 554, base station 104 sends a PDCCH order to UE 102 via TRP 107-1 (559, 560) to cause UE 102 to initiate a random access procedure 598 or 599 with base station 104 via TRP 107-2, as in events 558, 560.

[0083] Figures 6 to 14 are flowcharts illustrating exemplary methods that a UE (e.g., UE102) can implement to enable the operation of multiple TA values ​​under multiple TRP scenarios. Figures 6 to 14 illustrate several ways in which the UE determines an action when one of multiple TATs is fulfilled and maintains multiple TA values. In some embodiments, the first and second TRPs described below are, for example, TRP107-1 and TRP107-2. In another example, the first and second TRPs described below are TRP107-1 and TRP107-3.

[0084] Some general descriptions are given below, which can be applied to the following flowcharts and / or embodiments.

[0085] In some embodiments, the UE performs DL reception from a first TRP (e.g., one of TRP107-1, TRP107-2, TRP107-3, TRP108-1, and / or TRP108-2) and / or UL transmission to the first TRP. In some such embodiments, the UE performs DL reception from a second TRP (e.g., one of TRP107-1, TRP107-2, TRP107-3, TRP108-1, and / or TRP108-2) and / or UL transmission to the second TRP. In some embodiments, the first TRP is located within a serving cell. In further embodiments, the second TRP is located within a serving cell. Alternatively, the second TRP is located in an adjacent cell. In some embodiments, the second TRP is located in an adjacent cell or a non-serving cell, where the adjacent cell or non-serving cell is a cell with a different PCI than the serving cell.

[0086] In some embodiments, each TRP (e.g., TRP107-1, TRP107-2, TRP107-3, TRP108-1, and / or TRP108-2) is associated with or identified by a TRP identifier. In some embodiments, a base station (e.g., base station 104 or 106) includes a TRP identifier in the UL configuration, which the base station transmits to a UE (e.g., UE102) for UL transmission via the TRP identified by the TRP identifier. In some embodiments, the UL configuration includes a DCI transmitted in PDCCH, and / or a PUSCH configuration, a PUCCH configuration, and / or an SRS configuration, which are included in the RRC message (e.g., an RRC reconfiguration message or an RRC restart message) that the base station transmits to the UE. In some embodiments, the UL transmission includes a PUSCH transmission, a PUCCH transmission, and / or an SRS transmission. In some embodiments, the base station includes a TRP identifier in the DL configuration, and the DL configuration is transmitted by the base station to the UE102 for DL ​​transmission via the TRP identified by the TRP identifier. In some embodiments, the DL configuration includes a DCI transmitted to the PDCCH, and / or a CSI resource configuration, PDSCH configuration, and / or PDCCH configuration included in an RRC message (e.g., an RRC reconfiguration message or an RRC restart message) transmitted by the base station to the UE. In some embodiments, the DL transmission includes a CSI-RS transmission, an SSB transmission, a PDSCH transmission, and / or a PDCCH transmission.

[0087] In other embodiments, the base station does not send the TRP identifier to the UE, but instead uses implicit indication to show the TRP to the UE. In some embodiments, the implicit indication is one of the following configuration parameters: CORESETPoolIndex, the value or candidate value of CORESETPoolIndex, dataScrambleIdentityPDSCH, dataScrambleIdentityPDSCH2-r16, or PUCCH-ResourceGroup-r16. In such embodiments, the UE derives the TRP (identifier) ​​from the implicit indication. In some embodiments, the base station sends an RRC message (e.g., an RRC reconfiguration message or RRC restart message) to the UE that includes the configuration parameters.

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

[0089] In some cases, the UE maintains multiple TA values. In some such embodiments, the UE maintains multiple TA values, and all of the multiple TA values ​​are shown to or signaled to the UE. In further such embodiments, the UE maintains multiple TA values, and all of the multiple TA values ​​are derived by the UE. In some embodiments, the UE maintains multiple TA values, and at least one of several TA values ​​is shown to or signaled to the UE, and at least one of the remaining TA values ​​is derived by the UE. In further embodiments, the UE maintains or operates multiple TA values ​​in a serving cell. In some embodiments, the base station shows or configures the ID of each of the multiple TA values ​​to the UE. In some embodiments, the UE derives the ID of each of the multiple TA values. In some such embodiments, each of the multiple TA values ​​has a separate ID. In some such embodiments, the UE maintains multiple TA values ​​for or within a serving cell.

[0090] In some cases, the base station configures or activates a first set of serving cells for the UE. In some cases, the base station configures or activates a second set of serving cells for the UE. In some embodiments, the first set of serving cells has the same serving cell elements as the second set of serving cells. In some embodiments, the first set of serving cells has different serving cell elements than the second set of serving cells.

[0091] In some cases, the base station configures or activates a third set of serving cells for the UE. In some embodiments, the third set of serving cells includes at least a first set of serving cells. In further embodiments, the third set of serving cells includes at least a second set of serving cells. In some embodiments, the third set of serving cells includes at least a first set of serving cells and a second set of serving cells. In some embodiments, the third set of serving cells is a union of the first set of serving cells and the second set of serving cells. In some embodiments, the third set of serving cells is an intersection of the first set of serving cells and the second set of serving cells.

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

[0093] Depending on the embodiment, the first TA value is applied to or associated with (i) a first set of serving cells, (ii) applied to or associated with a first TRP, (iii) applied to or associated with UL channel / RS transmissions sent to the first TRP, and / or (iv) applied to or associated with UL channel / RS transmissions associated with a first TRP identifier and / or identifier value.

[0094] Depending on the embodiment, the second TA value is applied to or associated with (i) a second set of serving cells, (ii) applied to or associated with a second TRP, (iii) applied to or associated with UL channel / RS transmissions sent to the second TRP, and / or (iv) applied to or associated with UL channel / RS transmissions associated with a second TRP identifier and / or identifier value.

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

[0096] In some cases, a base station configures or indicates one or more TA groups for the UE. In some embodiments, a TA group (TAG) contains or is associated with one or more serving cells and / or indices. In some embodiments, each serving cell contained in or associated with the same TAG uses or operates with one or more TA values. In some embodiments, a TAG contains or is associated with one or more TA values. In some embodiments, the UE is indicated or configured with the ID of each of the one or more TA groups, or the UE derives the ID of each of the one or more TA groups. In some such embodiments, each TAG has a separate ID.

[0097] In some cases, the base station configures or indicates a first TAG for the UE. In some embodiments, the first TAG is within one or more groups of TAs. In some embodiments, the first TA value or the ID of the first TA value is associated with or included in the first TAG.

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

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

[0100] In some embodiments, the first TAG is associated with a first TRP or a first TRP identifier and / or identifier value. In some embodiments, the first TAG includes or is associated with a first set of serving cells. In some embodiments, the first set of serving cells consists of or is associated with a first TRP or a first TRP identifier and / or identifier value. In some embodiments, in each serving cell of the first set of serving cells, at least one CORESET consists of or is associated with CORESETPoolIndex#0.

[0101] In some embodiments, the first TAG includes or is associated with one or more TA values, the one or more TA values ​​being (i) applied to or associated with a first set of serving cells, (ii) applied to or associated with a first TRP, (iii) applied to or associated with a UL channel / RS transmission associated with a first TRP or a first TRP identifier and / or identifier value, and / or (iv) applied to or associated with a third set of serving cells.

[0102] In some embodiments, the second TAG is associated with a second TRP or a second TRP identifier and / or identifier value. In some embodiments, the second TAG includes or is associated with a second set of serving cells. In some embodiments, the second set of serving cells consists of or is associated with a second TRP or a second TRP identifier and / or identifier value. In some embodiments, in each serving cell of the second set of serving cells, at least one CORESET consists of or is associated with CORESETPoolIndex#1.

[0103] In some embodiments, the second TAG includes or is associated with one or more TA values, the one or more TA values ​​being (i) applied to or associated with a second set of serving cells, (ii) applied to or associated with a second TRP, (iii) applied to or associated with a UL channel / RS transmission associated with a second TRP or a second TRP identifier and / or identifier value, and / or (iv) applied to or associated with a third set of serving cells.

[0104] In some cases, the base station provides or configures the ID of the first TAG for the UE. In some cases, the UE derives the ID of the first TAG. In some cases, the base station provides or configures the ID of the second TAG for the UE. In some cases, the UE derives the ID of the second TAG.

[0105] In some cases, the base station indicates or configures a third TAG for the UE. In some embodiments, the third TAG is within one or more groups of TAs. In some embodiments, the UE may indicate or configure the ID of the third TAG, or the UE may derive the ID of the third TAG.

[0106] In some embodiments, the third TAG is associated with a first TRP or a first TRP identifier and / or identifier value. In some embodiments, the third TAG is associated with a second TRP or a second TRP identifier and / or identifier value. In some embodiments, the third TAG includes or is associated with a third set of serving cells.

[0107] In some embodiments, the third TAG includes or is associated with one or more TA values. In some embodiments, the third TAG includes or is associated with one or more TA values, where one or more TA values ​​include a first TA value and / or a second TA value.

[0108] In some embodiments, if a base station indicates or configures a third TAG for a UE, the UE decides to expect at least one of the following: (i) all serving cells included in or associated with the third TAG are configured by the base station in multiple TRP (M-TRP) modes (e.g., an M-TRP mode is a single DCI (S-DCI) M-TRP mode or multiple DCI (M-DCI) M-TRP modes); (ii) all serving cells included in or associated with the third TAG are configured by the base station in CORESETPoolIndex; and / or (iii) all serving cells included in or associated with the third TAG are configured by the base station in a first TRP identifier and / or identifier value, and a second TRP identifier and / or identifier value, and associated with them.

[0109] In some embodiments, if a base station configures a third TAG for a UE, the base station performs one or more of the following: (i) configure all serving cells included in or associated with the third TAG in M-TRP mode (e.g., M-TRP mode is S-DCI M-TRP mode or M-DCI M-TRP mode); (ii) configure all serving cells included in or associated with the third TAG in CORESETPoolIndex; and / or (iii) configure or associate all serving cells included in or associated with the third TAG with a first TRP identifier and / or identifier value, and a second TRP identifier and / or value.

[0110] In some cases, the base station configures or indicates one or more primary TAGs (PTAGs) for the UE. In some embodiments, 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.

[0111] In some cases, the first TAG is PTAG. In some embodiments, the first set of serving cells includes primary cells (PCells) or primary secondary cells (PSCells). In some embodiments, the first TAG is STAG. In some embodiments, the first set of serving cells does not include PCells or PSCells.

[0112] In some cases, the second TAG is PTAG. In some embodiments, the second set of serving cells includes PCell or PSCell. In some embodiments, the second TAG is STAG. In some embodiments, the second set of serving cells does not include PCell or PSCell.

[0113] In some cases, the third TAG is PTAG. In some embodiments, the third set of serving cells includes PCell or PSCell. In some embodiments, the third TAG is STAG. In some embodiments, the third set of serving cells does not include PCell or PSCell.

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

[0115] In some embodiments, a first TAT is associated with a first TAG. In further embodiments, a first TAT is associated with or applied to a first set of serving cells. In some embodiments, a second TAT is associated with a second TAG. In further embodiments, a second TAT is associated with or applied to a second set of serving cells.

[0116] In some embodiments, the base station configures or indicates a first TAT ID for the UE. In further embodiments, the UE derives a first TAT ID. In some embodiments, the base station configures or indicates a second TAT ID for the UE. In further embodiments, the UE derives a second TAT ID.

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

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

[0119] In some cases, whether the first TA value has expired and whether the second TA value has expired are controlled or associated with the same TAT (e.g., a third TAT). Furthermore, in some cases, whether the first TA value has expired and whether the second TA value has expired are controlled or associated with different TATs (e.g., a first TAT and a second TAT).

[0120] In some cases, whether the first TAG is uplink time-matched and whether the second TAG is uplink time-matched are controlled or associated by the same TAT (e.g., a third TAT). Furthermore, in some cases, whether the first TAG is uplink time-matched and whether the second TAG is uplink time-matched are controlled or associated by different TATs (e.g., a first TAT and a second TAT).

[0121] In some cases, whether a first set of serving cells is uplink time-matched and whether a second set of serving cells is uplink time-matched are controlled or associated by the same TAT (e.g., a third TAT). Furthermore, in some cases, whether a first set of serving cells is uplink time-matched and whether a second set of serving cells is uplink time-matched are controlled or associated by different TATs (e.g., a first TAT and a second TAT).

[0122] In some embodiments, the base station configures a first TAG and a second TAG, respectively, for UL transmission to a first TRP and a second TRP for the UE. In some embodiments, the base station transmits a first RRC message and a second RRC message to the UE, which include a first TAG configuration and a second TAG configuration, respectively, that constitute the first TAG and the second TAG. In some embodiments, the first TAG configuration and the second TAG configuration include a first TAG ID and a second TAG ID, respectively, to identify the first TAG and the second TAG. In some embodiments, the first TAG configuration and the second TAG configuration include a timer value for the first TAT and a timer value for the second TAT, respectively, for the first TAG and the second TAG. In some embodiments, 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 embodiments, the first RRC message and the second RRC message are an RRC setup message, an RRC reconfiguration message, and / or an RRC restart message. The UE associates the first TA value and the second TA value with the first TAG and the second TAG, respectively. In some embodiments, the first TAG is associated with a first TRP or a first TRP identifier and / or identifier value. In some embodiments, the first TAG is associated with a specific serving cell operated by the first TRP and configured for the UE. In some embodiments, the first TAG is associated with an additional serving cell operated by the first TRP and configured for the UE. In some embodiments, the base station indicates or configures the association within the first RRC message. In some embodiments, the second TAG is associated with a second TRP or a second TRP identifier and / or identifier value. In some embodiments, the second TAG is associated with a specific serving cell or non-serving cell, and the base station indicates or configures the association in the second RRC message.

[0123] In other embodiments, the base station configures a single TAG (e.g., a third TAG) for UL transmission to the first TRP and the second TRP for the UE. In some embodiments, the base station sends a first RRC message (e.g., RRC setup, RRC reconfiguration, and / or RRC restart message) to the UE that includes a single TAG configuration for configuring the TAG. In some embodiments, the TAG configuration includes a single TAG ID to identify the TAG. In some embodiments, the TAG configuration includes a timer value for the first TAT and a timer value for the second TAT. In further embodiments, the TAG configuration includes a timer value for the first TAT and a timer value for the second TAT, and the base station sends a second RRC message (e.g., RRC setup, RRC reconfiguration, and / or RRC restart message) that includes a timer value for the second TAT. The UE associates the first and second TAT values ​​with the TAG. In some embodiments, the TAG is associated with (i) a first TRP or a first TRP identifier and / or identifier value, and (ii) a second TRP or a second TRP identifier. In some embodiments, the TAG is associated with a specific serving cell operated by the first TRP and configured for the UE. In some embodiments, the TAG is associated with an additional serving cell operated by the first TRP and configured for the UE. In some embodiments, the base station indicates or configures the association in a first RRC message. In some embodiments, the TAG is associated with a second TRP or a second TRP identifier and / or identifier value. In some embodiments, the TAG is associated with a specific serving cell or non-serving cell, and the base station indicates or configures the association in a second RRC message.

[0124] In some embodiments, the base station is configured such that a particular serving cell is associated with a first TRP or a first TRP identifier and / or identifier value. In some embodiments, the base station configures a first control resource set (CORESET) associated with a particular serving cell or the first TRP. In further embodiments, the base station configures CORESETPoolIndex#0 to identify the first CORESET. In some embodiments, the base station configures the first CORESET and / or sends a third RRC message (e.g., an RRC setup message, an RRC reconfiguration message, or an RRC restart message) to the UE that includes CORESETPoolIndex#0. Thus, the UE monitors the PDCCH on the first CORESET to receive DCI from the base station, which means the UE monitors the PDCCH or receives DCI from the base station via the first TRP (i.e., from the first TRP). In such cases, the UE determines that CORESETPoolIndex#0 indicates a particular TRP of the base station (i.e., the first TRP).

[0125] In some embodiments, the base station configures a particular serving cell to be associated with a second TRP or a second TRP identifier and / or identifier value. In other embodiments, a 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 embodiments, the base station configures a non-serving cell associated with a second TRP or a second TRP identifier and / or identifier value. In some embodiments, the base station configures a second CORESET to be associated with a particular serving cell, non-serving cell, or second TRP. In further embodiments, the base station configures CORESETPoolIndex#1 to identify the second CORESET. In some embodiments, the base station configures the second CORESET and / or sends a third RRC message (e.g., RRC setup, RRC reconfiguration, and / or RRC restart message) to the UE that includes CORESETPoolIndex#1. Therefore, the UE monitors the PDCCH in the second CORESET and receives the DCI from the base station, which means the UE monitors the PDCCH or receives the DCI from the base station via the second TRP (i.e., from the second TRP). In some such embodiments, the UE determines that CORESETPoolIndex#1 indicates a particular TRP (i.e., the second TRP).

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

[0127] More generally, in some embodiments, the base station configures or indicates to the UE a first index for or related to a first TRP. In some embodiments, the UE derives or determines the first index. In some embodiments, 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.

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

[0129] In some cases, the first TAT is initiated or restarted by the UE or base station in response to at least one of the following: (i) the UE receives a timing advance command MAC CE, which indicates or updates timing adjustment-related information about a first TA value or a first TAG or a first TAT; (ii) the UE receives the timing advance command in a RAR response or in a MAC payload for a RAR response, where (a) in some embodiments, the RAR response or timing advance command is transmitted or associated with a first TRP; (b) in some embodiments, the RAR response or timing advance command is associated with a first index; and / or (c) in some embodiments, the RAR response and / or timing advance command indicates that the RAR response or timing advance command is for a first TRP. and / or (iii) the UE receives an absolute timing advance command in response to an MSGA transmission including a C-RNTI MAC CE, wherein (a) in some embodiments, the response to the MSGA or absolute timing advance command is transmitted or associated with a first TRP, (b) in some embodiments, the response to the MSGA or absolute timing advance command is associated with a first index, and / or (c) in some embodiments, the response to the MSGA or absolute timing advance command indicates that this response is for a first TRP.

[0130] In some cases, the second TAT is started or restarted in response to at least one of the following: (i) the UE receives a timing advance command MAC CE, where in some embodiments, the timing advance command MAC CE indicates or updates timing adjustment-related information about a second TA value or a second TAG or a second TAT; (ii) the UE receives the timing advance command in a RAR response or in a MAC payload for a RAR response, where (a) in some embodiments, the RAR response or timing advance command is transmitted or associated with a second TRP; (b) in some embodiments, the RAR response or timing advance command is associated with a second index; and / or (c) in some embodiments, the RAR response and / or timing advance command indicates that the RAR response or timing advance command is for a second TRP. and / or (iii) the UE receives an absolute timing advance command in response to an MSGA transmission including a C-RNTI MAC CE, wherein (a) in some embodiments, the response to the MSGA or absolute timing advance command is transmitted or associated with a second TRP, (b) in some embodiments, the response to the MSGA or absolute timing advance command is associated with a second index, and / or (c) in some embodiments, the response to the MSGA or absolute timing advance command indicates that this response is for a second TRP.

[0131] In some cases, the third TAT is started or restarted in response to at least one of the following: (i) the UE receives a timing advance command MAC CE, where, in some embodiments, the timing advance command MAC CE indicates or updates timing adjustment-related information for at least one of the following: (a) a first TA value, first TAG, or first TAT; (b) a second TA value, second TAG, or second TAT; and / or (c) a third TA value, third TAG, or third TAT. (ii) The UE receives a timing advance command in a RAR response or in a MAC payload for a RAR response, where (a) in some embodiments, the RAR response or timing advance command is transmitted or associated with a first TRP and / or a second TRP, (b) in some embodiments, the RAR response or timing advance command is associated with a first index and / or a second index, and / or (c) in some embodiments, the RAR response and / or timing advance command indicates that the RAR response or timing advance command is for a first TRP and / or a second TRP. and / or (iii) the UE receives an absolute timing advance command in response to an MSGA transmission including a C-RNTI MAC CE, wherein (a) in some embodiments, the response to the MSGA or absolute timing advance command is transmitted or associated with a first TRP and / or a second TRP, (b) in some embodiments, the response to the MSGA or absolute timing advance command is associated with a first index and / or a second index, and / or (c) in some embodiments, the response to the MSGA or absolute timing advance command indicates that this response is for a first TRP and / or a second TRP.

[0132] Referring first to Figure 6, the UE (e.g., UE102) implements an exemplary method 600 that performs operations on multiple TA values ​​under multiple TRP scenarios.

[0133] Method 600 begins in block 602, where the UE performs DL and / or UL communication with the 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). In block 604, the UE receives a configuration from the base station that enables the manipulation of two TA values ​​(e.g., events 548, 550, 596A, 578, 580, 596B, 579, 581, 596C). In block 606, the UE receives a first TA value and a second TA value from the base station (e.g., events 516, 518, 570, 571, 572, 573, 590, 598, 599). In block 608, upon receiving the first TA value (e.g., upon, after, or in response to the reception), the UE initiates or restarts the first TAT to maintain the first UL synchronization with the base station. In block 610, upon receiving the second TA value, the UE initiates or restarts the second TAT to maintain the second UL synchronization with the base station. In block 611, the UE detects whether the first or second TAT has expired. If the UE detects that the first TAT has expired, the flow proceeds to block 612. In block 612, the UE stops transmitting the UL transmission associated with the first TA value to the base station. If the UE detects that the second TAT has expired, the flow proceeds to block 614. In block 614, the UE stops transmitting the UL transmission associated with the second TA value to the base station.

[0134] When the first TAT expires and the UE stops transmitting to the first TRP, the UE can continue UL transmissions associated with the second TAT to the second TRP. Conversely, when the second TAT expires and the UE stops transmitting to the second TRP, the UE can continue UL transmissions associated with the second TAT to the first TRP. For example, in some embodiments, the UE reports to the base station that it has lost synchronization with the first TRP (e.g., TAT expiration), and the base station stops scheduling transmissions to the first TRP but continues scheduling transmissions to the second TRP.

[0135] In some embodiments, the UE maintains first and second UL synchronization with the base station based on a first and second TA value, respectively. In some embodiments, the UE applies the first and second TA values ​​to first and second UL transmissions with the base station on the serving cell, respectively. In other embodiments, the UE applies the first and second TA values ​​to transmit first and second UL transmissions with the base station in the serving cell and non-serving cell, respectively.

[0136] In some embodiments, the UE receives a first TA value from the base station in a first random access response, a first MAC CE, or a first MAC PDU. In some embodiments, the UE receives a second TA value from the base station in a second random access response, a second MAC CE, or a second MAC PDU. In some embodiments, the first MAC CE and the second MAC CE are the same MAC CE. In further embodiments, the first MAC CE and the second MAC CE are different MAC CEs having the same MAC CE format or different MAC CE formats. In some embodiments, the first MAC PDU and the second MAC PDU are the same MAC PDU. In further embodiments, the first MAC PDU and the second MAC PDU are different MAC PDUs.

[0137] A more detailed description of the elements of Method 600 is provided herein, particularly in relation to the general description above. For example, in some embodiments, (i) the first and second TA values ​​shown in block 606 are described in relation to the description of the first and second TA values ​​described in relation to the general description above, and (ii) the first and second TATs shown in blocks 608 and 610 are described in relation to the description of the first and second TATs described in relation to the general description above.

[0138] Next, referring to Figure 7A, the UE (e.g., UE102) implements exemplary method 700A, which performs operations on multiple TA values ​​under multiple TRP scenarios.

[0139] Method 700A begins in block 702. Blocks 702, 704, 706, 708, 710, and 711A are similar to blocks 602, 604, 606, 608, 610, and 611. If the UE detects that the first TAT has expired, the flow proceeds to block 712A. In block 712A, the UE flushes the HARQ buffer for the first set of HARQ processes, and the first set of HARQ processes is associated with a PUSCH transmission to which the UE has applied the first TA value. If the UE detects that the second TAT has expired, the flow proceeds to block 714A. In block 714A, the UE flushes the HARQ buffer for the second set of HARQ processes, and the second set of HARQ processes is associated with a PUSCH transmission to which the UE has applied the second TA value.

[0140] Figure 7B shows an exemplary method 700B that is similar to scenario 700A shown in Figure 7A, except that method 700B includes blocks 711B, 712B, and 714B, which are described below.

[0141] In block 711B, the UE detects whether both the first TAT and the second TAT have expired. If the UE detects that both the first and second TATs have expired, the flow proceeds to block 712B. In block 712B, the UE flushes the HARQ buffers of the HARQ processes associated with the first and second PUSCH transmissions to which the UE applied the first and second TA values, respectively. If the UE does not detect that both the first and second TATs have expired, the flow proceeds to block 714B. In block 714B, the UE refrains from flushing the HARQ buffers.

[0142] Similar to Method 600, a more detailed explanation of the elements of Method 700 is generally provided above.

[0143] In some cases, the UE is signaled by or composed of one or more HARQ processes in a serving cell. In some embodiments, the UE is signaled by or composed of one or more HARQ processes within each of one or more serving cells. For example, the UE is signaled by or composed of up to 16 HARQ processes within a serving cell. In another embodiment, the UE is signaled by or composed of up to 16 HARQ processes in each of one or more serving cells, and each serving cell is signaled by or composed of up to 16 HARQ processes.

[0144] In some cases, the UE is signaled or configured by a first set of HARQ processes. In some cases, the UE derives a first set of HARQ processes. In some embodiments, the UE is signaled or configured by a first set of HARQ processes in each of the first sets of serving cells. In some embodiments, the UE derives a first set of HARQ processes in each of the first sets of serving cells. In some embodiments, some elements or ID numbers in each of the first sets of HARQ processes are different in each of the first sets of serving cells. In further embodiments, some elements or ID numbers in each of the first sets of HARQ processes are the same in each of the first sets of serving cells. For example, when the first set of serving cells includes serving cell #0 and serving cell #1, the first set of HARQ processes in serving cell #0 for some such examples are HARQ processes #1, #2, and #5. However, the first set of HARQ processes in serving cell #1 are HARQ processes #1, #5, and #9.

[0145] In some cases, the UE is signaled or configured by a second set of HARQ processes. In some cases, the UE may derive a second set of HARQ processes. In some embodiments, the UE is signaled or configured by a second set of HARQ processes in each of the second sets of serving cells. In some embodiments, the UE derives a second set of HARQ processes in each of the second sets of serving cells. In some embodiments, some elements or ID numbers in each of the second sets of HARQ processes are different in each of the second sets of serving cells. In some embodiments, some elements or ID numbers in each of the second sets of HARQ processes are the same in each of the first sets of serving cells. For example, if the second set of serving cells includes serving cell #0 and serving cell #1, then the second set of HARQ processes in serving cell #0 are HARQ processes #3, #6, and #11. However, the second set of HARQ processes for serving cell #1 is HARQ processes #2, #4, and #8.

[0146] In some embodiments, in at least one serving cell, the elements in the first set of HARQ processes are orthogonal to the elements in the second set of HARQ processes. In some embodiments, in at least one serving cell, each value of the HARQ process ID in the first set of HARQ processes is different from the value in the second set of HARQ processes. In some embodiments, in at least one serving cell, none of the values ​​of the HARQ process IDs in the first set of HARQ processes are the same as the values ​​in the first set of HARQ processes. For example, if both the first set of serving cells and the second set of serving cells contain serving cell #0 and serving cell #1, then the first set of HARQ processes in serving cell #0 are HARQ processes #1, #2, and #5. However, the first set of HARQ processes in serving cell #1 are HARQ processes #1, #5, and #9. The second set of HARQ processes in serving cell #0 are HARQ processes #3, #6, and #11. However, the second set of HARQ processes in serving cell #1 is HARQ processes #2, #4, and #8.

[0147] In some cases, the first set of HARQ processes is associated with one of the candidate values ​​for the TRP identifier. In some embodiments, the first set of HARQ processes is associated with one of the candidate values ​​for the CORESETPoolIndex. In some embodiments, the first set of HARQ processes is associated with CORESETPoolIndex#0. In further embodiments, the first set of HARQ processes is associated with CORESETPoolIndex#1.

[0148] In some cases, the second set of HARQ processes is associated with one of the candidate values ​​for the TRP identifier. In some embodiments, the second set of HARQ processes is associated with one of the candidate values ​​for the CORESETPoolIndex. In some embodiments, the second set of HARQ processes is associated with CORESETPoolIndex#1. In further embodiments, the second set of HARQ processes is associated with CORESETPoolIndex#0.

[0149] In some cases, the first set of HARQ processes is associated with the first index. In further cases, the second set of HARQ processes is associated with the second index.

[0150] In some cases, for a HARQ process in a first set of HARQ processes, the HARQ process includes at least one of the following attributes: (i) In some embodiments, the HARQ process is used to send a UL transmit, where the UL transmit is transmitted by a spatial relationship, UL / joint TCI state, or spatial transmit filter / parameter derived from a source RS, which is associated with or includes a first TA value; (ii) In some embodiments, the HARQ process is used to send a UL transmit, where the UL transmit is transmitted using a first TA value; and / or, (iii) In some embodiments, the HARQ process is used to send a UL transmit, where the UL transmit is associated with or includes a first TA value.

[0151] In some cases, for a HARQ process in a second set of HARQ processes, the HARQ process includes at least one of the following attributes: (i) the HARQ process is used to send a UL transmit, where the UL transmit is transmitted by a spatial relation, UL / joint TCI state, or spatial transmit filter / parameter derived from a source RS, which is associated with or includes a second TA value; (ii) the HARQ process is used to send a UL transmit, where the UL transmit is transmitted using a second TA value; and / or (iii) the HARQ process is used to send a UL transmit, where the transmit is associated with or includes a second TA value.

[0152] In some cases, the base station signals or configures one HARQ entity in a serving cell for the UE. In some embodiments, the base station signals or configures only one HARQ entity in a serving cell for the UE. In some embodiments, the base station signals or configures one HARQ entity in each of a first set of serving cells for the UE. In some embodiments, the base station signals or configures one HARQ entity in each of a second set of serving cells for the UE. In some embodiments, the base station signals or configures one HARQ entity in at least one serving cell in the first set of serving cells for the UE. In some embodiments, the base station signals or configures one HARQ entity in at least one serving cell in a second set of serving cells for the UE. In some embodiments, one or more of each of the first set of serving cells are signaled or configured by the base station with a single HARQ entity. In some embodiments, one or more of each of the second set of serving cells are signaled or configured by the base station with a single HARQ entity.

[0153] In some embodiments, a first set of HARQ processes may be included in or belong to the HARQ entity of the first serving cell. In some embodiments, a second set of HARQ processes may be included in or belong to the HARQ entity of the first serving cell.

[0154] In some embodiments, the first serving cell is associated with or included in a first set of serving cells. In some embodiments, the first serving cell is associated with or included in a second set of serving cells. In some embodiments, the first TAG is associated with or included in a third set of serving cells.

[0155] In some cases, the base station signals or configures multiple HARQ entities within a serving cell for the UE. In some embodiments, the base station signals or configures multiple HARQ entities in each of a first set of serving cells for the UE. In some embodiments, the base station signals or configures multiple HARQ entities in each of a second set of serving cells for the UE. In some embodiments, the base station signals or configures multiple HARQ entities in at least one serving cell in the first set of serving cells for the UE. In some embodiments, the base station signals or configures multiple HARQ entities in at least one serving cell in the second set of serving cells for the UE. In some embodiments, one or more of each of the first set of serving cells are signaled or configured by multiple HARQ entities. In some embodiments, one or more of each of the second set of serving cells are signaled or configured by multiple HARQ entities.

[0156] In some embodiments, the base station signals or configures a first HARQ entity in a second serving cell for the UE. In some embodiments, the base station signals or configures a second HARQ entity in a second serving cell for the UE.

[0157] In some embodiments, a second serving cell is associated with or included in a first set of serving cells. In some embodiments, a second serving cell is associated with or included in a second set of serving cells. In some embodiments, a second serving cell is associated with or included in a third set of serving cells.

[0158] In some embodiments, the first HARQ entity is associated with a first TRP or a first TRP identifier and / or identifier value. In some embodiments, the first HARQ entity includes a first TRP identifier and / or identifier value. For example, the first HARQ entity is associated with or includes CORESETPoolIndex#0. In some embodiments, the first HARQ entity includes or is associated with a first set of HARQ processes.

[0159] In some embodiments, the second HARQ is associated with a second TRP or a second TRP identifier and / or identifier value. In some embodiments, the second HARQ entity includes the second TRP identifier and / or identifier value. For example, the second HARQ entity is associated with or includes CORESETPoolIndex#1. In some embodiments, the second HARQ entity includes or is associated with a second set of HARQ processes.

[0160] In some embodiments, the base station indicates or signals elements or HARQ process IDs that are part of a first set of HARQ processes. In some embodiments, the base station indicates or signals elements or HARQ process IDs that are part of a first set of HARQ processes by at least one of DCI signaling, MAC-CE, or RRC signaling. In some embodiments, the base station indicates or signals elements or HARQ process IDs that are part of a first set of HARQ processes via a bitmap. In some embodiments, the base station indicates or signals elements or HARQ process IDs that are part of a first set of HARQ processes. In some embodiments, the base station indicates or signals elements or HARQ process IDs that are part of a first set of HARQ processes by at least one of DCI signaling, MAC-CE, or RRC signaling. In some embodiments, the base station indicates or signals elements included in a first set of HARQ processes or HARQ process IDs by bitmap.

[0161] In some embodiments, the base station indicates or signals elements or HARQ process IDs included in a second set of HARQ processes. In some embodiments, the base station indicates or signals elements or HARQ process IDs included in a second set of HARQ processes by at least one of DCI signaling, MAC-CE, or RRC signaling. In some embodiments, the base station indicates or signals elements or HARQ process IDs included in a second set of HARQ processes by a bitmap. In some embodiments, the base station updates or changes elements or HARQ process IDs included in a second set of HARQ processes. In some embodiments, the base station updates or changes elements or HARQ process IDs included in a second set of HARQ processes by at least one of DCI signaling, MAC-CE, or RRC signaling. In some embodiments, the base station updates or changes elements or HARQ process IDs included in a second set of HARQ processes by a bitmap.

[0162] In some cases, if a UL transmission (e.g., UL data) is associated with a first TRP or a first TRP identifier and / or identifier value, the UL transmission is associated with or uses a HARQ process in a first set of HARQ processes.

[0163] In some cases, if a UL transmission (e.g., UL data) is associated with a second TRP or a second TRP identifier and / or identifier value, the UL transmission will be associated with or use a HARQ process in a second set of HARQ processes.

[0164] In some cases, upon the expiration of the first TAT, the UE may perform at least one of the following actions: (i) flush or clear any HARQ buffers belonging to or associated with a first set of HARQ processes, where (a) in some embodiments, the UE performs the action when it does not support retransmissions scheduled by PDCCHs received at a different CORESETPoolIndex compared to the CORESETPoolIndex of the initial transmission (for example, when the UE does not expect to receive DCIs from different CORESETPoolIndexes that schedule retransmissions for the same HARQ process ID); (b) in some embodiments, the UE performs the action when it reports supportRetx-Diff-CoresetPool-Multi-DCI-TRP-r16; and / or (c) in some embodiments, the action may refer to flushing or clearing any HARQ buffers belonging to or associated with each of the first set of HARQ processes in the first set of service cells. (ii) Do not flush or clear any HARQ buffers that belong to or are associated with a second set of HARQ processes. (iii) Do not flush or clear any HARQ buffers that belong to or are associated with each of the second sets of HARQ processes for the serving cell. (iv) Do not flush or clear any HARQ buffers that belong to or are associated with any HARQ processes that are not the first set of HARQ processes for the first and / or second serving cell. and / or (v) Do not flush or clear any HARQ buffers that belong to or are associated with any HARQ processes that are not the first set of HARQ processes for the first and / or second set of serving cell. In such cases, the first TAG is STAG. In such cases, the first TA value belongs to or is associated with STAG. In such cases, the first TAT is associated with STAG.

[0165] Alternatively, in response to the expiration of the first TAT, the UE may perform at least one of the following actions: (i) flush or clear any HARQ buffers belonging to or associated with a second set of HARQ processes; (ii) flush or clear any HARQ buffers belonging to or associated with each of the second sets of HARQ processes in the second set of serving cells; (iii) flush or clear any HARQ buffers belonging to or associated with any HARQ processes that are not in the first set of HARQ processes in the first and / or second serving cells; (iv) flush or clear any HARQ buffers belonging to or associated with any HARQ processes that are not in the first set of HARQ processes in the first and / or second set of serving cells; (v) flush or clear all HARQ buffers in the first and / or second serving cells; (vi) flush or clear all HARQ buffers in the first and / or second set of serving cells. (vii) Flushe or clear all HARQ buffers belonging to or associated with the HARQ process of data related to the first index of all serving cells. and / or (viii) Flushe or clear all HARQ buffers of all serving cells. In such cases, the first TAG is PTAG. In such cases, the first TA value belongs to or is associated with PTAG. In such cases, the first TAT is associated with PTAG.

[0166] In some cases, the UE may, in response to the expiration of the second TAT, perform at least one of the following actions: (i) flush or clear any HARQ buffers belonging to or associated with a second set of HARQ processes, where (a) in some embodiments, the UE performs the action when it does not support retransmissions scheduled by PDCCHs received at a different CORESETPoolIndex compared to the CORESETPoolIndex of the initial transmission (for example, when the UE does not expect to receive DCIs from different CORESETPoolIndexes that schedule retransmissions for the same HARQ process ID); (b) in some embodiments, the UE performs the action when it reports supportRetx-Diff-CoresetPool-Multi-DCI-TRP-r16; and / or (c) in some embodiments, the action refers to flushing or clearing any HARQ buffers belonging to or associated with each of the second set of HARQ processes in the second set of service cells. (ii) Do not flush or clear any HARQ buffers that belong to or are associated with the first set of HARQ processes. (iii) Do not flush or clear any HARQ buffers that belong to or are associated with each of the first sets of HARQ processes for the first set of serving cells. (iv) Do not flush or clear any HARQ buffers that belong to or are associated with any HARQ processes that are not the second set of HARQ processes for the first and / or second serving cells. and / or, (v) Do not flush or clear any HARQ buffers that belong to or are associated with any HARQ processes that are not the second set of HARQ processes for the first set and / or second set of serving cells. In such cases, the second TAG is STAG. In such cases, the second TA value may belong to or be associated with STAG. In such cases, the second TAT is associated with STAG.

[0167] Alternatively, in response to the expiration of the second TAT, the UE may perform at least one of the following actions: (i) flush or clear any HARQ buffers belonging to or associated with the first set of HARQ processes; (ii) flush or clear any HARQ buffers belonging to or associated with each of the first sets of HARQ processes in the first set of serving cells; (iii) flush or clear any HARQ buffers belonging to or associated with any HARQ processes that are not in the second set of HARQ processes in the first and / or second serving cells; (iv) flush or clear any HARQ buffers belonging to or associated with any HARQ processes that are not in the second set of HARQ processes in the first and / or second set of serving cells; (v) flush or clear any HARQ buffers in the first and / or second serving cells; (vi) flush or clear any HARQ buffers in the first and / or second set of serving cells. (vii) Flushe or clear all HARQ buffers belonging to or associated with the data of the second TRP, or the second TRP identifier and / or identifier value, for all serving cells. and / or, (viii) Flushe or clear all HARQ buffers for all serving cells. In such cases, the second TAG is PTAG. In such cases, the second TA value belongs to or is associated with PTAG. In such cases, the second TAT is associated with PTAG.

[0168] Next, referring to Figure 8A, the UE (e.g., UE102) implements exemplary method 800A, which performs operations on multiple TA values ​​under multiple TRP scenarios.

[0169] Method 800A begins in block 802. Blocks 802, 804, 806, 808, 810, and 811A are similar to blocks 602, 604, 606, 608, 610, and 611. If the UE detects that the first TAT has expired, the flow proceeds to block 812. In block 812, the UE clears the configured UL grants that were and / or associated with the first TA value. If the UE detects that the second TAT has expired, the flow proceeds to block 814. In block 814, the UE clears the configured UL grants that were and / or associated with the second TA value.

[0170] Figure 8B shows an exemplary method 800B which is similar to scenario 800A shown in Figure 8A, except that method 800B includes blocks 811B, 813, and 815.

[0171] In block 811B, the UE detects whether the first TAT and the second TAT have expired. If the UE detects that the first TAT and the second TAT have expired, the flow proceeds to block 813. In block 813, the UE performs the clear action described in blocks 812 and / or 814. If the UE does not detect that the first TAT and the second TAT have expired, the flow proceeds to block 815. In block 815, the UE refrains from performing the clear action described in blocks 812 and / or 814.

[0172] Next, referring to Figure 9A, the UE (e.g., UE102) implements exemplary method 900A, which performs operations on multiple TA values ​​under multiple TRP scenarios.

[0173] Method 900A begins in block 902. Blocks 902, 904, 906, 908, 910, and 911A are similar to blocks 602, 604, 606, 608, 610, and 611. If the UE detects that the first TAT has expired, the flow proceeds to block 912. In block 912, the UE releases the PUCCH resource and / or scheduling request resource configuration instance configured with and / or associated with the first TA value. If the UE detects that the second TAT has expired, the flow proceeds to block 914. In block 914, the UE releases the PUCCH resource and / or scheduling request resource configuration instance configured with and / or associated with the second TA value.

[0174] Figure 9B shows an exemplary method 900B which is similar to scenario 900A shown in Figure 9A, except that method 900B includes blocks 911B, 913, and 915.

[0175] In block 911B, the UE detects whether the first TAT and the second TAT have expired. If the UE detects that the first TAT and the second TAT have expired, the flow proceeds to block 913. In block 913, the UE performs the release actions described in blocks 912 and / or 914. If the UE does not detect that the first TAT and the second TAT have expired, the flow proceeds to block 915. In block 915, the UE refrains from performing the release actions described in blocks 912 and / or 914.

[0176] Next, referring to Figure 10A, the UE (e.g., UE102) implements exemplary method 1000A, which performs operations on multiple TA values ​​under multiple TRP scenarios.

[0177] Method 1000A begins in block 1002. Blocks 1002, 1004, 1006, 1008, 1010, and 1011A are similar to blocks 602, 604, 606, 608, 610, and 611. If the UE detects that the first TAT has expired, the flow proceeds to block 1012. In block 1012, the UE releases the SRS resource configuration instance configured with and / or associated with the first TA value. If the UE detects that the second TAT has expired, the flow proceeds to block 1014. In block 1014, the UE releases the SRS resource configuration instance configured with and / or associated with the second TA value.

[0178] Figure 10B shows an exemplary method 1000B which is similar to scenario 1000A shown in Figure 10A, except that method 1000B includes blocks 1011B, 1013, and 1015.

[0179] In block 1011B, the UE detects whether the first TAT and the second TAT have expired. If the UE detects that the first TAT and the second TAT have expired, the flow proceeds to block 1013. In block 1013, the UE performs the release action described in blocks 1012 and / or 1014. If the UE does not detect that the first TAT and the second TAT have expired, the flow proceeds to block 1015. In block 1015, the UE refrains from performing the release action described in blocks 1012 and / or 1014.

[0180] Next, referring to Figure 11A, the UE (e.g., UE102) implements exemplary method 1100A, which performs operations on multiple TA values ​​under multiple TRP scenarios.

[0181] Method 1100A begins in block 1102. Blocks 1102, 1104, 1106, 1108, 1110, and 1111A are similar to blocks 602, 604, 606, 608, 610, and 611. If the UE detects that the first TAT has expired, the flow proceeds to block 1112. In block 1112, the UE clears the PUSCH resources for semi-persistent CSI reporting, which consist of and / or are associated with the first TA value. If the UE detects that the second TAT has expired, the flow proceeds to block 1114. In block 1114, the UE clears the PUSCH resources for semi-persistent CSI reporting, which consist of and / or are associated with the second TA value.

[0182] Figure 11B shows an exemplary method 1100B that is similar to scenario 1100A shown in Figure 11A, but differs in that method 1100B includes blocks 1111B, 1113, and 1115, which are described below.

[0183] In block 1111B, the UE detects whether the first TAT and the second TAT have expired. If the UE detects that the first TAT and the second TAT have expired, the flow proceeds to block 1113. In block 1113, the UE performs the clear action described in blocks 1112 and / or 1114. If the UE does not detect that the first TAT and the second TAT have expired, the flow proceeds to block 1115. In block 1115, the UE refrains from performing the clear action described in blocks 1112 and / or 1114.

[0184] Similar to Method 600, a more detailed explanation of the elements of Methods 800A–1100B is generally provided above.

[0185] In some cases, the UE may, in response to the expiration of the first TAT, release, clear, or suspend the configured resources, or send an RRC notification to release the configured resources in the first set of serving cells, where the configured resources are associated with the first TA value or the first index. In such cases, the first TAG is STAG. In such cases, the first TA value belongs to or is associated with STAG. In such cases, the first TAT is associated with STAG.

[0186] In some cases, the UE releases, clears, or suspends the configured resources in response to the expiration of the second TAT, or sends an RRC notice to release the configured resources in a second set of serving cells, where, in some embodiments, the configured resources are associated with a second TA value or a second index. In such cases, the second TAG is STAG. In such cases, the second TA value belongs to or is associated with STAG. In such cases, the second TAT is associated with STAG.

[0187] In some cases, the configured resources are one of the following: (i) a PUCCH resource, (ii) an SRS resource, (iii) a configured downlink allocation (e.g., DL SPS), (iv) a configured uplink grant, and / or (v) a PUSCH resource, where the PUSCH resource is for semi-persistent CSI reporting.

[0188] In some cases, if a configured resource is associated with a first TA value, the configured resource will be subject to at least one of the following: (i) the configured resource is transmitted via the first TA value; (ii) the configured resource, or the configuration for the configured resource, includes the first TA value; (iii) the configuration of the configured resource includes the first index; (iv) the configured resource is transmitted by a spatial transmit filter / parameter derived from a spatial relationship (or UL / joint TCI state or reference signal) associated with or including the first TA value; and / or (v) the configured resource is received by a spatial receive filter / parameter derived from a joint TCI state (or TCI state, QCL assumption, or reference signal) associated with or including the first TA value.

[0189] In some cases, if a configured resource is associated with a second TA value, the configured resource will be subject to at least one of the following: (i) the configured resource is transmitted via the second TA value; (ii) the configured resource, or the configuration for the configured resource, includes the second TA value; (iii) the configuration for the configured resource includes the second index; (iv) the configured resource is transmitted by a spatial transmit filter / parameter derived from a spatial relationship (or UL / joint TCI state or reference signal) associated with or including the second TA value; and / or (v) the configured resource is received by a spatial receive filter / parameter derived from a joint TCI state (or TCI state, QCL assumption, or reference signal) associated with or including the second TA value.

[0190] In some cases, the UE may, in response to the expiration of the first TAT, perform at least one of the following actions: (i) release, clear, or suspend the configured resources or send an RRC notice to release, clear, or suspend the configured resources associated with the first TRP / TAG / TAT / TA value or the first index in all serving cells, and / or (ii) release, clear, or suspend the configured resources or send an RRC notice to release, clear, or suspend the configured resources in all serving cells. In such cases, the first TAG is the PTAG. In such cases, the first TA value belongs to or is associated with the PTAG. In such cases, the first TAT is associated with the PTAG.

[0191] In some cases, the UE may, in response to the expiration of the second TAT, perform at least one of the following actions: (i) release, clear, or suspend the configured resources or send an RRC notice to release, clear, or suspend the configured resources associated with the second TRP / TAG / TAT / TA value or the second index in all serving cells, and / or (ii) release, clear, or suspend the configured resources or send an RRC notice to release, clear, or suspend the configured resources in all serving cells. In such cases, the second TAG is the PTAG. In such cases, the second TA value belongs to or is associated with the PTAG. In such cases, the second TAT is associated with the PTAG.

[0192] In some cases, the UE maintains, retains, or otherwise stores the first TA value in response to the expiration of the first TAT. In such cases, the first TAG is STAG. In such cases, the first TA value belongs to or is associated with STAG. In such cases, the first TAT is associated with STAG.

[0193] Alternatively, in response to the expiration of the first TAT, the UE may perform at least one of the following actions: (i) maintain, retain, or otherwise store all indicated or derived TA values ​​associated with the first TRP / TAG / TAT / TA value or the first index across all TAGs; (ii) maintain, retain, or otherwise store the second TA value; and / or (iii) maintain, retain, or otherwise store all indicated or derived TA values ​​across all TAGs. In such cases, the first TAG is a PTAG. In such cases, the first TA value belongs to or is associated with a PTAG. In such cases, the first TAT is associated with a PTAG.

[0194] In some cases, the UE maintains, retains, or stores the second TA value in response to the expiration of the second TAT. In such cases, the second TAG is STAG. In such cases, the second TA value belongs to or is associated with STAG. In such cases, the second TAT is associated with STAG.

[0195] Alternatively, in response to the expiration of the second TAT, the UE may perform at least one of the following actions: (i) maintain, retain, or store all indicated or derived TA values ​​associated with the second TRP / TAG / TAT / TA values ​​or the second index across all TAGs; (ii) maintain, retain, or store the first TA values; and / or (iii) maintain, retain, or store all indicated or derived TA values ​​across all TAGs. In such cases, the second TAG may be a PTAG. In such cases, the second TA values ​​may belong to or be associated with a PTAG. In such cases, the second TAT may be associated with a PTAG.

[0196] Next, referring to Figure 12A, the UE (e.g., UE102) implements exemplary method 1200A, which performs operations on multiple TA values ​​under multiple TRP scenarios.

[0197] Method 1200A begins in block 1202. Blocks 1202, 1204, 1206, 1208, 1210, and 1211 are similar to blocks 602, 604, 606, 608, 610, and 611. If the UE detects that the first TAT has expired, the flow proceeds to block 1212A. In block 1212A, the UE triggers a CBRA procedure with the base station associated with the first TA value. If the UE detects that the second TAT has expired, the flow proceeds to block 1214A. In block 1214A, the UE triggers a CBRA procedure with the base station associated with the second TA value.

[0198] Figure 12B shows an exemplary method 1200B that is similar to scenario 1200A shown in Figure 12A, except that method 1200B includes blocks 1212B and 1214B.

[0199] If the UE detects that the first TAT has expired, the flow proceeds to block 1212B. In block 1212B, the UE sends a first MAC CE to the base station indicating the expiration of the first TA value. If the UE detects that the second TAT has expired, the flow proceeds to block 1214B. In block 1214B, the UE sends a second MAC CE to the base station indicating the expiration of the second TA value.

[0200] In some embodiments, the first MAC CE and the second MAC CE have the same MAC CE format. In some embodiments, in block 1212B, the UE transmits a MAC PDU containing the subheader of the first MAC CE and the first MAC CE to the base station. In some embodiments, in block 1214B, the UE transmits a MAC PDU containing the subheader of the second MAC CE and the second MAC CE to the base station.

[0201] In some embodiments, the UE includes in the first MAC CE the ID of the first TA value, or the ID of the first TAG associated with the first TA value. In some embodiments, the UE includes in the second MAC CE the ID of the second TA value, or the ID of the second TAG associated with the second TA value.

[0202] Figure 12C shows an exemplary method 1200C, which is similar to scenario 1200A shown in Figure 12A, except that method 1200C includes blocks 1212C and 1214C.

[0203] If the UE detects that the first TAT has expired, the flow proceeds to block 1212C. In block 1212C, the UE sends a first RRC message to the base station indicating the expiration of the first TA value. If the UE detects that the second TAT has expired, the flow proceeds to block 1214C. In block 1214C, the UE sends a second RRC message to the base station indicating the expiration of the second TA value.

[0204] In some embodiments, the first RRC message and the second RRC message have the same RRC message format. For example, the first RRC message and the second RRC message are UE assistance information messages (e.g., UEAssistanceInformation messages).

[0205] In some embodiments, the UE includes in the first RRC message the ID of a first TA value, or the ID of a first TAG associated with the first TA value. In some embodiments, the UE includes in the second RRC message the ID of a second TA value, or the ID of a second TAG associated with the second TA value.

[0206] Figure 12D shows an exemplary method 1200D which is similar to scenario 1200A shown in Figure 12A, except that method 1200D includes blocks 1212D and 1214D.

[0207] If the UE detects that the first TAT has expired, the flow proceeds to block 1212D. In block 1212D, the UE sends a first PUCCH transmission to the base station indicating the expiration of the first TA value. If the UE detects that the second TAT has expired, the flow proceeds to block 1214D. In block 1214D, the UE sends a second PUCCH transmission to the base station indicating the expiration of the second TA value.

[0208] In some embodiments, the UE includes in the first PUCCH transmission the ID of a first TA value, or the ID of a first TAG associated with the first TA value. In some embodiments, the UE includes in the second PUCCH transmission the ID of a second TA value, or the ID of a second TAG associated with the second TA value.

[0209] Figure 12E shows an exemplary method 1200E that is similar to scenario 1200A shown in Figure 12A, except that method 1200E includes blocks 1211E and 1216.

[0210] In block 1211E, the UE detects whether the first TAT has expired, whether the second TAT has expired, or whether both the first and second TATs have expired. If the UE detects that the first TAT has expired, the UE performs the actions described in blocks 1212B, 1212C, or 1212D. If the UE detects that the second TAT has expired, the UE performs the actions described in blocks 1214B, 1214C, or 1214D. If the UE detects that both the first and second TATs have expired, the flow proceeds to block 1216. In block 1216, the UE triggers a CBRA procedure with the base station.

[0211] Similar to Method 600, a more detailed explanation of the elements of Methods 1200A to 1200E is generally provided above.

[0212] In some cases, the UE takes action when at least one of the following is met or achieved: (i) the first TAT expires; (ii) the UE has UL data or UL channel / RS associated with the first index; (iii) the UE has UL data or UL channel / RS intended for or associated with the first TRP to transmit; and / or (iv) the UE has UL data or UL channel / RS to transmit via the first TA value. In some such embodiments, the next action the UE takes is at least one of the following: (i) trigger or execute a competition-based or non-compete RA procedure associated with the first index; (ii) trigger or execute a competition-based or non-compete RA procedure intended for the first TRP, first TAG, first TAT, or first TA value; and / or (iii) send the first MAC-CE to the NW, where the second TAT has not expired.

[0213] In some cases, the UE takes action when at least one of the following is met or achieved: (i) the second TAT expires; (ii) the UE has UL data or UL channel / RS associated with the second index; (iii) the UE has UL data or UL channel / RS intended for or associated with a second TRP to transmit; and / or (iv) the UE has UL data or UL channel / RS to transmit via a second TA value. In some such embodiments, the next action the UE takes is at least one of the following: (i) trigger or execute a competition-based or non-compete RA procedure associated with the second index; (ii) trigger or execute a competition-based or non-compete RA procedure intended for a second TRP, second TAG, second TAT, or second TA value; and / or (iii) send a second MAC-CE to the NW, where the first TAT has not expired.

[0214] In some cases, when an RA procedure is associated with, or intended to be associated with, (a) a first index and / or (b) a first TRP / TAG / TA value / TAT, at least one of the following is true: (i) MSG 0 or PDCCH order (e.g., received by the UE from the base station) for the RA procedure indicates or is associated with a first index, where in some embodiments the RA procedure is a non-conflicting RA procedure; (ii) MSG 1 or MSG A (e.g., transmitted by the UE to the base station) for the RA procedure indicates or is associated with a first index; (iii) MSG 2 or MSG B (e.g., received by the UE from the base station) for the RA procedure indicates or is associated with a first index; and / or (iv) MSG 3 or MSG 4 (e.g., transmitted by the UE to the base station) for the RA procedure indicates or is associated with a first index.

[0215] In some cases, when an RA procedure is associated with, or intended to be associated with, (a) a second index and / or (b) a second TRP / TAG / TA value / TAT, at least one of the following is true: (i) MSG 0 or PDCCH order (e.g., received by the UE from the base station) for the RA procedure indicates or is associated with a second index, where in some embodiments the RA procedure is a non-conflicting RA procedure; (ii) MSG 2 or MSG B (e.g., transmitted to the base station by the UE) for the RA procedure indicates or is associated with a second index; (iii) MSG 2 or MSG B (e.g., received from the base station by the UE) for the RA procedure indicates or is associated with a second index, and / or (iv) MSG 3 (e.g., transmitted to the base station by the UE) or MSG 4 (e.g., received from the base station by the UE) for the RA procedure indicates or is associated with a second index.

[0216] In some embodiments, the first and / or second MAC-CE represents at least one of the following, which are (i) the first or second index, (ii) which TA value or TAG has expired, and / or (iii) the estimated TA offset or difference.

[0217] In some cases, when a base station receives a first MAC-CE, the base station transmits an MSG 0 or PDCCH order to the UE. In a further embodiment, when a network receives a first MAC-CE, the network transmits an MSG 0 or PDCCH order to the UE, where (i) the MSG 0 or PDCCH order indicates or is associated with a first index, and / or (ii) the MSG 0 or PDCCH order indicates or is associated with a first index, if the first MAC-CE indicates a first index.

[0218] In some cases, when a base station receives a second MAC-CE, the base station transmits an MSG 0 or PDCCH order to the UE. In a further embodiment, when a network receives a first MAC-CE, the network transmits an MSG 0 or PDCCH order to the UE, where (i) the MSG 0 or PDCCH order indicates or is associated with a second index, and / or (ii) the MSG 0 or PDCCH order indicates or is associated with a second index, if the first MAC-CE indicates a first index.

[0219] In some embodiments, the MAC-CE of the first MAC-CE and / or the second MAC-CE refers to or replaces the TA Expiration Indicator MAC-CE or the TA Expiration Report MAC-CE. In some embodiments, the first MAC-CE and the second MAC-CE are the same MAC-CE. Alternatively, the first MAC-CE and the second MAC-CE are different MAC-CEs.

[0220] Next, referring to Figure 13, the UE (e.g., UE102) implements an exemplary method 1300 that performs operations on multiple TA values ​​under multiple TRP scenarios.

[0221] Method 1300 begins with block 1302. Blocks 1302, 1304, and 1306 are similar to blocks 602, 604, and 606. In block 1308, the UE starts or restarts a single TAT to maintain first and second UL synchronization with the base station. In some embodiments, the single TAT is the third TAT described above. In block 1310, the UE detects or determines whether the single TAT has expired. In block 1312, the UE performs the actions described in 612 / 614, 712B, 812 / 814, 912 / 914, 1012 / 1014, 1112 / 1114, 1212A / 1214A, 1212B / 1214B, 1212C / 1212C, 1212D / 1214D, and / or 1216 in response to the expiration of a single TAT.

[0222] In some embodiments, the UE initiates or restarts a single TAT and maintains first UL synchronization and second UL synchronization with the UE upon receiving a first TA value, a second TA value, or both the first and second TA values ​​(e.g., upon reception, in response to reception, or after reception).

[0223] Similar to Method 600, a more detailed explanation of the elements of Method 1300 is generally provided above.

[0224] In some cases (including method 1300), the UE maintains one TAT (e.g., a third TAT) for the first TA value and the second TA value. In some embodiments, the UE maintains one TAT (e.g., a third TAT) for the first TA value and the second TA value, and the third TAT is used to determine whether the first TA value and / or the second TA value have expired.

[0225] In some cases, the UE receives a third MAC-CE, which simultaneously indicates or updates the first TA value and the second TA value. In some embodiments, when the UE receives the third MAC-CE, the UE expects the third MAC-CE to simultaneously indicate or update the first TA value and the second TA value. In some embodiments, if the UE maintains one TAT (e.g., a third TAT) for the first and second TA values, the UE expects the third MAC-CE, upon receipt, to simultaneously update the first TA value and the second TAT value.

[0226] In some embodiments, if the UE receives a third MAC-CE and the third MAC-CE does not simultaneously indicate or update the first TA value and the second TA value, the UE ignores, discards, or otherwise uses the third MAC-CE. In some embodiments, if the UE maintains one TAT (e.g., a third TAT) for the first TA value and the second TA value, then if the UE receives a third MAC-CE and the third MAC-CE does not simultaneously indicate or update the first TA value and the second TA value, the UE ignores, discards, or otherwise uses the third MAC-CE.

[0227] In some cases, the base station maintains one TAT (e.g., a third TAT) for the first TA value and the second TA value. In some embodiments, the base station maintains one TAT (e.g., a third TAT) for the first TA value and the second TA value, where the third TAT is used to determine whether the first TA value and / or the second TA value have expired.

[0228] In some cases, the base station transmits a third MAC-CE, which simultaneously indicates or updates the first and second TA values. In some embodiments, when the base station transmits the third MAC-CE, it may be necessary to simultaneously indicate or update the first and second TA values. In some such embodiments, the base station may not be able to use the third MAC-CE and may only indicate or update one of the first or second TA values. In some embodiments, when the base station maintains one TAT (e.g., a third TAT) for the first and second TA values, the base station may be required to simultaneously indicate or update the first and second TAT values. In some embodiments, when a base station maintains a single TAT (e.g., a third TAT) for a first TA value and a second TA value, and the base station transmits a third MAC-CE, the base station may be required to simultaneously indicate or update the first TA value and the second TA value in the third MAC-CE.

[0229] In some embodiments, when the UE maintains one TAT (e.g., a third TAT) for a first TA value and a second TA value, the first TA value and the second TA value belong to or are associated with a TAG (e.g., a third TAG). In some embodiments, when the UE maintains one TAT (e.g., a third TAT) for a first TA value and a second TA value, the first TA value and the second TA value belong to or are associated with different TAGs (e.g., a first TAG and a second TAG).

[0230] In some embodiments, the third MAC-CE is one of the following, which are: (i) an (advanced) timing advance command MAC CE, (ii) an (advanced) timing advance command in or in the MAC payload for a RAR response, or (iii) an (advanced) absolute timing advance command in response to an MSGA transmission including a C-RNTI MAC CE.

[0231] In some embodiments, a third MAC-CE is also used when the UE is configured to maintain and / or maintain two TATs (e.g., a first TAT and a second TAT) in at least one serving cell. In some embodiments, the third MAC-CE is used to indicate or update the first TA value and / or the second TA value, where (i) the first TA value and the second TA value are shown or updated simultaneously in some embodiments, (ii) the first TA value and the second TA value are shown or updated separately (e.g., at different times) in some embodiments, and / or (iii) the first TAT and the second TAT value belong to or are associated with different TATs (e.g., a first TAT and a second TAT).

[0232] Next, referring to Figure 14, the UE (e.g., UE102) implements an exemplary method 1400 for performing operations on multiple TA values ​​under multiple TRP scenarios.

[0233] Method 1400 begins with block 1402. Blocks 1402 and 1404 are similar to blocks 602 and 604. In block 1406, the UE receives a first TA value from the base station. In block 1408, the UE sends a UL transmission to the base station using the first TA value. In block 1410, upon receiving the first TA value, the UE initiates or restarts a first TAT to maintain a first UL synchronization with the base station. In block 1412, the UE receives a MAC CE from the base station containing a delta value. In block 1414, the UE derives a second TA value using the first TA value and the delta value. In block 1416, in some embodiments, upon receiving the delta value or deriving the second TA value, the UE initiates or restarts a second TAT to maintain a second UL synchronization with the base station. In block 1418, the UE sends a UL transmission to the base station using the second TA value. In block 1420, when the first TAT expires, the UE considers or determines whether the second TAT will expire.

[0234] Similar to Method 600, a more detailed explanation of the elements of Method 1400 is generally provided above.

[0235] In some cases, the UE derives a second TA value. In some embodiments, the exact value of the second TA value is not explicitly indicated or signaled to the UE (e.g., MAC-CE or DCI) by the base station. In some embodiments, the exact value of the first TA value is explicitly indicated or signaled by the base station (e.g., MAC-CE or DCI).

[0236] In some embodiments, if the UE derives a second TA value, there is no TAT (e.g., a dedicated TAT) for or associated with the second TA value. In some embodiments, if the UE derives a second TA value, there is no TAG (e.g., a dedicated TAG) for or associated with the second TA value.

[0237] In some embodiments, the UE receives the delta value. In some embodiments, the second TA value is derived by using the delta value. In some embodiments, the second TA value is derived using the first TA value and the delta value. In some embodiments, the second TA value is the sum of the first TA value and the delta value. In some embodiments, the possible range of values ​​for the value obtained by adding the first TA value to the delta value is the same as or a subset of that of the first TA value. In some embodiments, the NW indicates or signals the delta value. In some such embodiments, the NW indicates or signals the delta value via one of RRC, MAC-CE, or DCI.

[0238] In some embodiments, the delta value is indicated or updated by a fourth MAC-CE. In some embodiments, the fourth MAC-CE is the MAC-CE described in Method 1400. In some embodiments, the fourth MAC-CE can indicate or update the first TA value. In some embodiments, or alternatively, the fourth MAC-CE cannot indicate or update the first TA value.

[0239] In some embodiments, if the UE receives a fourth MAC-CE and the fourth MAC-CE does not indicate or update a delta value, the currently applied delta value is used or not changed. In some embodiments, if (i) the fourth MAC-CE can indicate or update a delta value and a first TA value, and (ii) the UE receives a fourth MAC-CE that does not indicate or update a delta value, the currently applied delta value is used.

[0240] In some embodiments, the fourth MAC-CE includes a bit or field indicating whether the delta value is indicated by or updated by the fourth MAC-CE. In some embodiments, the fourth MAC-CE includes a bit or field indicating whether the delta value is present in or included in the fourth MAC-CE.

[0241] In some embodiments, the UE determines that if the first TAT has expired, the second TA value has also expired. In some embodiments, the UE determines that if the first TAT has expired, the delta value has also expired. In further embodiments, the base station configures or indicates a special timer for the UE to determine whether the delta value is expired / expired or valid. In some embodiments, the UE has a special timer to determine whether the delta value is expired / expired or valid. In some embodiments, the UE determines that if the special timer has expired, the second TA value has also expired.

[0242] Throughout this disclosure, note that “TA value expires” can mean at least one of the following: (i) the TA value is not synchronized, (ii) the TA value has expired, and / or (iii) the TA value is uplink time-matched.

[0243] Throughout this disclosure, note that "adjacent 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 that of a serving cell, and / or (iii) a TRP associated with a PCI different from that of a serving cell.

[0244] Throughout this disclosure, it should be noted that the joint TCI state refers to or may be replaced by at least one of the following: (i) a beam applicable to both DL 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] Throughout this disclosure, please note that the term "joint TCI state" refers to or may be replaced by a common TCI state or a unified TCI state.

[0246] Throughout this specification, it should be noted that the UL TCI state refers to or may be replaced by at least one of the following: (i) UL beam, (ii) spatial relation, (iii) spatial transmit filter, (iv) transmit precoder, (v) spatial parameter, and / or (vi) spatial relation.

[0247] Throughout this disclosure, it should be noted that the DL TCI state refers to or may be replaced by at least one of the following: (i) a TCI applicable to the DL channel or RS, (ii) a TCI associated with a pseudo-collocation (QCL) type D, (iii) a QCL assumption, (iv) a DL beam, (v) a spatial receive filter, (vi) a spatial parameter, (vii) a spatial relationship, and / or (viii) a spatial assumption.

[0248] Throughout this disclosure, note that 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 TCIs (indices). Throughout this disclosure, note that "TCI" may also be referred to as and may be replaced by "TCI state". Throughout this disclosure, note that "TCI pool" may also be referred to as and may be replaced by "TCI state pool".

[0249] Throughout this disclosure, it should be noted that a UE may have one or more of the following attributes or behaviors. The following attributes or behaviors of a UE may also mean the relevant attributes or behaviors of a base station. (i) A UE is composed of and / or serviced by a base station in a serving cell. (ii) A UE is configured to communicate with a base station in a serving cell. (iii) A UE is composed of one or more serving cells by a base station, and the base station may include serving cells. (iv) A UE is activated or indicated by a base station, and activates one or more serving cells, and the base station may include serving cells. (v) A UE has configured and / or indicated one or more BWPs by a base station. A UE has indicated and / or configured a BWP in a serving cell by a base station. (a) In some embodiments, a BWP is activated as an active BWP. (b) In some embodiments, a BWP refers to an active BWP. (c) In some embodiments, a BWP is an active DL BWP. (d) In some embodiments, BWP is an active UL BWP. (e) In some embodiments, BWP is an initial BWP. (f) In some embodiments, BWP is a default BWP. (g) In some embodiments, BWP is a dormant BWP. (vi) UE is in one of the following states: RRC_CONNECTED, RRC_INACTIVE, or RRC_IDLE.

[0250] Throughout this disclosure, note that the expression "X / Y" may mean "X or Y". Throughout this disclosure, note that the expression "X / Y" may mean "X and Y". Throughout this disclosure, note that the expression "X / Y" may mean "X and / or Y". Throughout this disclosure, note that the expression "(A)B" or "B(A)" may mean "B only". Throughout this disclosure, note that the expression "(A)B" or "B(A)" may mean "A+B" or "B+A".

[0251] Throughout this disclosure, note that "panel" may mean an antenna (port) group or a set of antenna (ports). Multiple DL / UL beams can be associated with a single panel. When a transmitting node (UE or base station) performs a transmission through a panel, it may perform the transmission using only one beam associated with the panel. For a transmitter with multiple panels, such as two panels, it may occur that the transmission is performed using two beams, each associated with a different panel.

[0252] Throughout this disclosure, it should be noted that a TRP identifier may mean or be referred to as a (candidate) value of a TRP identifier. The first TRP identifier may be the first candidate value of a TRP identifier or the first TRP identifier value. The second TRP identifier may be the second candidate value of a TRP identifier or the second TRP identifier value.

[0253] Throughout this disclosure, note that a panel identifier may mean or be referred to as a (candidate) value of a panel identifier. The first panel identifier may be a first candidate value of a panel identifier or the first panel identifier value. The second panel identifier may be a second candidate value of a panel identifier or the second panel identifier value.

[0254] Throughout this disclosure, note that the term TCI field means, or may mean, a field that is used to indicate, applied to, or adapted to indicate one or more TCI conditions.

[0255] Throughout this disclosure, it should be noted that “Joint Mode” or “Joint TCI State Mode” may mean at least one of the following: (i) a TCI field or a TCI state shown in DCI format refers to / maps to one of the Joint TCI State Pool, DL TCI State Pool, or UL TCI State Pool; and / or (ii) a beam display or shown TCI state applies to both the transmission of a UL transmission and / or the reception of a DL transmission.

[0256] Throughout this disclosure, note that “separate mode” or “separate TCI state mode” may mean at least one of the following: (i) a TCI field or a TCI state shown in DCI format refers to / maps to one of the joint TCI state pool, DL TCI state pool, or UL TCI state pool; and / or (ii) a beam display or a shown TCI state applies to either a UL transmit (only) or a DL transmit (only).

[0257] Throughout this disclosure, note that “UL mode” or “UL-only TCI state mode” may mean at least one of the following: (i) a TCI field or a TCI state shown in DCI format refers to / maps to a UL TCI state pool (joint TCI state pool); and / or (ii) a beam display or a shown TCI state applies to UL transmissions (only).

[0258] Throughout this disclosure, note that “DL mode” or “DL-only TCI state mode” may mean at least one of the following: (i) a TCI field or a TCI state shown in DCI format refers to / maps to a DL TCI state pool (joint TCI state pool); and / or (ii) a beam display or shown TCI state applies to DL transmission reception (only).

[0259] Throughout this disclosure, whenever a procedure or description relates to a serving cell, it may mean that the procedure or description relates to the serving cell's active (DL / UL)BWP.

[0260] Throughout this disclosure, please note that “TA Timer” or “TAT” may also be referred to as “TA Alignment Timer” or may be replaced by it.

[0261] It should be noted that some or all of the aforementioned or subsequent embodiments may be combined or formed as new or alternative embodiments.

[0262] It should be noted that the aforementioned and subsequent embodiments (but not limited to them) can be used to solve at least the problems or scenarios mentioned in this disclosure.

[0263] The following additional considerations may apply to the preceding or subsequent explanations.

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

[0265] It should be noted that any sentence, paragraph, (sub)item, point, action, or claim described in each of the preceding or following methods / embodiments / embodiments may be implemented independently and separately to form a specific method. Dependencies in the following methods / embodiments / embodiments, such as "based on," "more specifically," and "here," are merely one possible embodiment and do not limit the particular method.

[0266] Please 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 within an NR, which is used to control one or more TRPs associated with one or more cells. Communication between the base station and the TRP(s) takes place via fronthaul. A base station may be called a central unit (CU), eNB, gNB, or NodeB. (ii) Transmit / receive point (TRP): A transmit / receive point provides network coverage and communicates directly with the UE. A TRP may be called a distributed unit (DU) or 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 TRP(s)). One cell is controlled by one base station. A cell may be called a TRP group (TRPG). (iv) Serving beam: A serving beam for a UE is a beam generated by a network node (e.g., a TRP), which is configured to be used to communicate with the UE (e.g., for transmission and / or reception). (v) Candidate beams: Candidate beams for UE are candidates for serving beams. A serving beam may or may not be a candidate beam.

[0267] User devices (e.g., UE102) that can implement the technology of this disclosure may be any suitable wirelessly communicating device, such as a smartphone, tablet computer, laptop computer, mobile game console, point-of-sale (POS) terminal, health management device, drone, camera, media streaming dongle or other personal media device, wearable device such as a smartwatch, wireless hotspot, femtocell, or broadband router. Furthermore, the user device may be embedded in an electronic system such as a vehicle head unit or advanced driver-assistance system (ADAS). Moreover, the user device may operate 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, computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0268] Certain embodiments described in this disclosure include logic, or several components or modules. A module may be a software module (e.g., code stored in a non-temporary machine-readable medium) or a hardware module. A hardware module is a tangible unit capable of performing a particular operation and may be configured or arranged in a particular manner. A hardware module may include dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC)) to perform a particular operation. A hardware module may also include programmable logic or circuitry that is temporarily configured by software (e.g., contained within a general-purpose processor or other programmable processor) to perform a particular operation. The decision to implement a hardware module in dedicated and permanently configured circuitry or in temporarily configured circuitry (e.g., configured by software) may depend on cost and time considerations.

[0269] When implemented in software, the technology may be provided as part of an operating system, a library used by multiple applications, or a specific software application. The software can run on one or more general-purpose processors or one or more special-purpose processors.

Claims

1. A method for managing synchronization, the method being implemented in a user device (UE), The configuration, including a first timing advance (TA) value and a second TA value, is received from a wireless access network (RAN). To manage the synchronization between the first uplink (UL) transmission and the first receiver in the RAN, a first TA timer (TAT) corresponding to the first TA value is operated, In order to manage the synchronization between the second UL transmission and the second receiver in the RAN, a second TAT corresponding to the second TA value is operated, In response to the expiration of the first TAT, the first UL transmission is stopped, In response to the expiration of the second TAT, the second UL transmission is stopped, The method, including the method described above.

2. The first receiver is the first transmit / receive point (TRP) of a node in the RAN, The second receiver is the second TRP of the node, The method according to claim 1, wherein the UE is configured to communicate with the first TRP and the second TRP in multiple TRP (M-TRP) modes.

3. The method according to claim 2, further comprising continuing the second UL transmission to the second TRP after the first TAT has expired and before the second TAT has expired.

4. The method according to claim 3, wherein continuing the second UL transmission includes continuing to receive the scheduling of the second UL transmission from the RAN.

5. The first TRP is associated with the first TA group (TAG), The method according to any one of claims 2 to 4, wherein the second TRP is associated with the second TAG.

6. The first TA value is associated with the first TCI state, The method according to claim 5, wherein the second TA value is associated with a second TCI state.

7. The first receiver operates in the serving cell, The method according to claim 1, wherein the second receiver operates in a non-serving cell.

8. Operating the first TAT includes starting or restarting the first TAT in response to receiving the first TA value. The method according to any one of claims 1 to 7, wherein operating the second TAT includes starting or restarting the second TAT in response to receiving the second TA value.

9. The method according to any one of claims 1 to 8, further comprising receiving an indication from the RAN that the use of multiple TA values ​​in the serving cell is effective.

10. Receiving the first TA value means Transmitting a random access preamble to the first receiver, The first TA value is received from the first receiver in response to the random access preamble, The method according to any one of claims 1 to 9, including the method described in any one of claims 1 to 9.

11. Receiving the first TA value means The method according to any one of claims 1 to 9, comprising receiving a media access control (MAC) control element (CE) including the first TA value.

12. Receiving the first TA value means The method according to any one of claims 1 to 11, comprising receiving a MAC protocol data unit (PDU) containing the first TA value.

13. In response to the expiration of the first TAT, a first expiration indication that the first TAT has expired is transmitted to the RAN, In response to the expiration of the second TAT, a second expiration indication that the second TAT has expired is transmitted to the RAN, The method according to any one of claims 1 to 12, further comprising:

14. The method according to claim 13, wherein each of the first expiration indication and the second expiration indication is included in their respective MAC CE.

15. Transceiver and, Processing hardware configured to implement the method described in any one of claims 1 to 14, User equipment (UE), including user devices.

Images