Beam usage after cell handover command

By indicating the beam/TCI status in the cell handover signaling, the problem of beam selection mismatch during cell handover is solved, communication efficiency is improved and latency is reduced, and the operation of communication equipment is optimized.

CN123125952APending Publication Date: 2026-11-17PANASONIC INTELLECTUAL PROPERTY CORP OF AMERICA
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580026098.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-04-05
Filing Date
2025-03-27
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

During cell handover, communication equipment may experience beam mismatch when selecting beams, leading to low communication efficiency and increased latency.

Method used

By indicating the use of beam/TCI status in cell handover signaling, the beam communication between the communication equipment and the target cell is ensured to start at the appropriate time, reducing the risk of mismatch.

Benefits of technology

It improves communication efficiency during cell handover, reduces the risk of delays and mismatches, and optimizes the operation of communication equipment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125952A_ABST
    Figure CN123125952A_ABST
Patent Text Reader

Abstract

This disclosure relates to communication equipment, base stations, and corresponding methods for communication equipment and base stations. For example, the communication equipment is a user equipment (UE) including circuitry and a transceiver. The transceiver: (i) receives control signaling; (ii) transmits one or more transmissions of a random access (RA) procedure; (iii) receives one or more transmissions of the RA procedure; and (iv) transmits (a) a first physical uplink shared channel (PUSCH) transmission, wherein the first PUSCH transmission is the first transmission among PUSCH transmissions scheduled after the completion of the RA procedure and by uplink (UL) authorization addressed to the communication equipment's radio network temporary identifier (RNTI), or (b) a first physical uplink control channel (PUCCH) transmission acknowledging receipt of a downlink (DL) transmission, wherein the first PUCCH transmission is the first transmission among PUCCH transmissions carrying a receipt acknowledgment after the completion of the RA procedure. The circuit: (i) obtains from control signaling: (a) a cell handover command instructing the communication device to perform a cell handover from the source cell to the target cell, and (b) an indication of the Transmission Configuration Indication (TCI) status; (ii) performs a cell handover to the target cell according to the cell handover command; (iii) performs the RA procedure in the target cell; and (iv) determines that the indicated TCI status will be used when (a) the first PUSCH transmission or (b) the first PUCCH transmission begins or completes.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the transmission and reception of signals in communication systems, such as 3GPP communication systems. Specifically, this disclosure relates to methods and apparatus for such transmission and reception. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) works on the technical specifications for next-generation cellular technologies, also known as the fifth generation (5G) which includes “New Radio” (NR) Radio Access Technology (RAT) and operates in a frequency range up to 100 GHz. NR is a follower of technologies represented by Long Term Evolution (LTE) and LTE Advanced (LTE-A).

[0003] For systems like LTE and NR, further improvements and options can facilitate the effective operation of the communication system and the specific equipment associated with it. Summary of the Invention

[0004] A non-limiting and exemplary embodiment helps a communication device select the appropriate beam for communicating with the base station (BS) of the target cell after performing an RA-based cell handover to the target cell, while reducing the risk of mismatched beam usage (which occurs when the base station and the communication device assume they will use different beam / TCI states). Specifically, the use of the beam / TCI state indicated to the communication device along with the cell handover command can begin at an appropriate time.

[0005] In one embodiment, the technology disclosed herein is characterized by a communication device. The communication device includes a transceiver and circuitry. The transceiver: (i) receives cell handover signaling; (ii) transmits one or more transmissions of a random access (RA) procedure; (iii) receives one or more transmissions of the RA procedure; and (iv) transmits (a) a first physical uplink shared channel (PUSCH) transmission, wherein the first PUSCH transmission is the first transmission among PUSCH transmissions scheduled after the completion of the RA procedure and by uplink (UL) authorization addressed to the communication device via a radio network temporary identifier (RNTI), or (b) a first physical uplink control channel (PUCCH) transmission, wherein the first PUCCH transmission acknowledges the reception of a downlink (DL) transmission, wherein the first PUCCH transmission is the first transmission among PUCCH transmissions carrying a reception acknowledgment after the completion of the RA procedure. The circuit: (i) obtains from the cell handover signaling: (a) a cell handover command that instructs the communication equipment to perform a cell handover from the source cell to the target cell, and (b) an indication of the Transmission Configuration Indication (TCI) status; (ii) performs a cell handover to the target cell according to the cell handover command; (iii) performs the RA procedure in the target cell; and (iv) determines that the indicated TCI status will be used from the start of the operation or from the completion of the operation: (a) the first PUSCH transmission or (b) the first PUCCH transmission.

[0006] It should be noted that general or specific embodiments may be implemented as systems, methods, integrated circuits, computer programs, storage media or any alternative combination thereof.

[0007] Additional benefits and advantages of the disclosed embodiments will become apparent from the specification and accompanying drawings. Benefits and / or advantages may be obtained individually from the various embodiments and features in the specification and drawings, which need not all be provided to obtain one or more such benefits and / or advantages. Attached Figure Description

[0008] In the following description, exemplary embodiments are described in more detail with reference to the accompanying drawings.

[0009] Figure 1 An exemplary architecture of a 3GPP NR system to which exemplary embodiments of the present disclosure can be applied is shown;

[0010] Figure 2 Exemplary function splitting options in 5G O-RAN to which exemplary embodiments of the present disclosure can be applied are shown;

[0011] Figure 3A segmented gNB architecture is shown in which exemplary embodiments of the present disclosure can be applied, wherein the gNB is divided into a gNB central unit and one or more gNB distributed units.

[0012] Figure 4 A simplified signaling diagram of lower-level cell handover within a DU is shown;

[0013] Figure 5a A four-step type of competition-based RA (CBRA) process is shown;

[0014] Figure 5b A four-step competition-based RA (CFRA) process is shown;

[0015] Figure 5c A two-step type of non-competitive RA (CBRA) process is shown;

[0016] Figure 5d A two-step, non-competitive rescue (CFRA) process is shown;

[0017] Figure 6 The signaling diagram used for CSI measurement and reporting is shown;

[0018] Figure 7 An exemplary signaling procedure for L1 / L2 triggered mobility is shown;

[0019] Figure 8 It is a block diagram of a communication system including user equipment and base stations, and their respective exemplary functional structures;

[0020] Figure 9 This is a block diagram illustrating an exemplary functional structure of the processing circuitry on the user equipment side.

[0021] Figure 10 This is a block diagram illustrating an exemplary functional structure of the processing circuitry on the base station side.

[0022] Figure 11 This is a flowchart illustrating exemplary steps performed by a user equipment and exemplary steps performed by a base station; and

[0023] Figure 12a The TCI start time is shown according to an exemplary embodiment in the case of a 4-step CBRA process;

[0024] Figure 12b The TCI start time is shown according to another exemplary embodiment in the case of a 4-step type CBRA process;

[0025] Figure 13a The TCI start time is shown according to an exemplary embodiment in the case of a 4-step CFRA process;

[0026] Figure 13b The TCI start time is shown according to another exemplary embodiment in the case of a 4-step CFRA process;

[0027] Figure 14a The TCI start time is shown according to an exemplary embodiment in the case of a 2-step type CBRA process;

[0028] Figure 14b The TCI start time is shown according to an exemplary embodiment in the case of a 2-step CFRA process;

[0029] Figure 15a The TCI start time is shown according to another exemplary embodiment in the case of a 2-step type CBRA process;

[0030] Figure 15b The TCI start time is shown according to another exemplary embodiment in the case of a 2-step CFRA process;

[0031] Figure 16a The TCI start time is shown according to yet another exemplary embodiment in the case of a 2-step CBRA process;

[0032] Figure 16b The TCI start time is shown according to yet another exemplary embodiment in the case of a 2-step CFRA process;

[0033] Figure 17a The TCI start time is shown according to yet another exemplary embodiment in the case of a 2-step CBRA process; and

[0034] Figure 17b The TCI start time is shown according to yet another exemplary embodiment in the case of a 2-step CFRA process. Detailed Implementation

[0035] 5G NR System Architecture and Protocol Stack

[0036] The 5G NR system architecture employs NG-RAN (Next Generation Radio Access Network), which includes gNBs, user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocol terminations providing NG radio access to UEs. gNBs interconnect via the Xn interface. gNBs also connect to the NGC (Next Generation Core) via the Next Generation (NG) interface, and more specifically, to the AMF (Access and Mobility Management Functions) (e.g., specific core entities performing the AMF) via the NG-C interface, and to the UPF (User Plane Functions) (e.g., specific core entities performing the UPF) via the NG-U interface. The NG-RAN architecture in... Figure 1As shown in (see, for example, 3GPP TS 38.300 v15.6.0, Section 4).

[0037] RRC connection establishment and reconfiguration process

[0038] The interaction between the UE, gNB, and AMF (5GC entity) in the context of the UE's transition from RRC_IDLE to RRC_CONNECTED in the NAS section is described (see TS 38.300 v15.6.0).

[0039] RRC is a higher-level signaling (protocol) used for UE and gNB configuration. Specifically, this transition involves the AMF preparing UE context data (including, for example, PDU session context, security keys, UE radio capabilities, and UE security capabilities) and transmitting it to the gNB via an INITIALCONTEXT SETUP REQUEST. Then, the gNB activates AS security with the UE by sending a SecurityModeCommand message to the UE, which is executed by the UE responding with a SecurityModeComplete message. Afterward, the gNB performs reconfiguration by sending an RRCReconfiguration message to the UE to establish Signaling Radio Bearer 2 (SRB2) and (multiple) Data Radio Bearers (DRBs), and in response, the gNB receives an RRCReconfigurationComplete message from the UE. For signaling-only connections, the steps related to RRCReconfiguration are skipped because SRB2 and DRBs are not established. Finally, gNB notifies AMF that the configuration process is complete via the INITIALCONTEXT SETUP RESPONSE message.

[0040] Therefore, this disclosure provides entities for a fifth-generation core (5GC) (e.g., Access and Mobility Management Function (AMF), Session Management Function (SMF), etc.), including: a control circuit that establishes a next-generation (NG) connection with the gNodeB; and a transmitter that sends an initial context establishment message to the gNodeB via the NG connection to establish a signaling radio bearer between the gNodeB and the user equipment (UE). Specifically, the gNodeB sends Radio Resource Control (RRC) signaling containing resource allocation configuration information elements to the UE via the signaling radio bearer. The UE then performs uplink transmission or downlink reception based on the resource allocation configuration.

[0041] QoS control

[0042] The 5G QoS (Quality of Service) model is based on QoS flows and supports both QoS flows that require guaranteed flow bit rate (GBRQoS flows) and QoS flows that do not require guaranteed flow bit rate (non-GBR QoS flows). Therefore, at the NAS level, QoS flows represent the finest QoS granularity within a PDU session. QoS flows are identified within a PDU session by the QoS Flow ID (QFI) carried in the encapsulation header on the NG-U interface.

[0043] For each UE, the 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes at least one data radio bearer (DRB) along with the PDU session, and subsequently, multiple additional DRBs for the QoS flows of that PDU session can be configured (when to do so depends on the NG-RAN). The NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and 5GC associate UL and DL packets with QoS flows, while AS-level mapping rules in the UE and NG-RAN associate UL QoS flows and DL QoS flows with DRBs.

[0044] Open-RAN

[0045] The base station described in each exemplary embodiment (e.g., a 5G NR base station referred to as gNB) may consist of three functional modules: a centralized unit (CU), a distributed unit (DU), and a radio unit (RU).

[0046] A CU can be referred to as a centralized node, aggregation node, centralized station, aggregation station, or central unit. A DU can be referred to as an O-DU (O-RAN Distributed Unit), distributed node, distributed station, or distributed unit. A RU can be referred to as an O-RU (O-RAN Radio Unit), radio device, radio node, radio station, antenna unit, or radio unit.

[0047] The function split configuration (or function split point) between CU, DU, and RU defines several split options. The term "function split point" is sometimes also referred to as "split," "option," or "split option."

[0048] Examples of “segmentation options” are the following segmentation options 1 to 8. The functionality of the base station described in each exemplary embodiment can be segmented into CU, DU, RU by one of the following segmentation options 1 to 8. For example, each of CU, DU, and RU can undergo functional segmentation, or functional segmentation may be possible only between CU and DU or only between DU and RU.

[0049] (1) Split Option 1: Between RRC (Radio Resource Control) and PDCP

[0050] (2) Segmentation Option 2: Between PDCP and RLC (High-RLC)

[0051] (3) Segmentation Option 3: Between High-RLC and Low-RLC

[0052] (4) Segmentation Option 4: Between RLC (Low-RLC) and MAC (High-MAC)

[0053] (5) Splitting option 5: Between High-MAC and Low-MAC

[0054] (6) Segmentation Option 6: Between MAC (Low-MAC) and PHY (High-PHY)

[0055] (7) Splitting option 7: Between High-PHY and Low-PHY

[0056] (8) Splitting option 8: Between PHY (Low-PHY) and RF

[0057] The functional split point between the CU and O-DU can be split option 2. The link between the CU and O-DU is called midhaul, and the F1 interface is defined by 3GPP. Alternatively, the link between the O-DU and O-RU is called fronthaul, and its functional split point can be split option 7-2x, which is adopted as the O-RAN fronthaul specification.

[0058] Figure 2 An example is shown where the base station function of a gNB is functionally divided into CU, O-DU, and O-RU via Segmentation Option 2 and Segmentation Option 7-2x.

[0059] A CU may include, for example, RRC (Radio Resource Control) functions, SDAP (Service Data Adaptation Protocol) functions, and PDCP (Packet Data Convergence Protocol) functions.

[0060] O-DU may include, for example, RLC (Radio Link Control) functions, MAC functions, and high-level physical layer (HIGH-PHY) functions. Furthermore, HIGH-PHY functions may include coding, scrambling, modulation, layer mapping, precoding, and RE (Resource Element) mapping functions for downlink (DL) transmission. HIGH-PHY functions may also include decoding, descrambling, demodulation, layer demapping, and RE (Resource Element) demapping functions for uplink (UL) reception.

[0061] The O-RU may include, for example, LOW-PHY and RF functions. Furthermore, the LOW-PHY function may include beamforming, IFFT (Inverse Fast Fourier Transform) + CP (Cyclic Prefix) addition, and D / A (Digital to Analog) conversion for downlink transmission. Additionally, the LOW-PHY function may include A / D (Analog to Digital) conversion, CP removal + FFT (Fast Fourier Transform), and beamforming for uplink reception.

[0062] Note that if the O-DU does not include precoding functionality, the O-RU may include precoding functionality.

[0063] O-RU may include LBT (Listen Before You Speak) related functions.

[0064] eCPRI (Evolved Universal Public Radio Interface) is defined as the communication scheme between O-DU and O-RU in split option 7-2x.

[0065] In split option 7-2x, sampled sequences of in-phase (I) and quadrature (Q) components of OFDM signals in the frequency domain are transmitted and received via eCPRI, along with information for beamforming in the antenna, time synchronization signals, etc.

[0066] Information transmitted via the signals (PDCCH, PUCCH, PDSCH, PUSCH, MAC CE, RRC, etc.) described in each exemplary embodiment can be transmitted between the O-DU and O-RU via the user plane (U plane) or control plane (C plane) of eCPRI.

[0067] When the functions described in each exemplary embodiment are executed in the O-RU through function partitioning, the O-DU can control the O-RU by sending information for controlling the functions via control signals (e.g., eCPRI) between the O-DU and the O-RU.

[0068] In the case where the functions described in each exemplary embodiment are performed by means of a function segmentation in the O-DU, the O-RU can receive the results of the functions performed in the O-DU by means of a control signal (e.g., eCPRI) and can control the O-RU based on the received results.

[0069] CU, O-DU and O-RU can be deployed in physically different devices, with their respective functions connected by optical fibers, or some or all of their functions can be deployed in the same physical device.

[0070] CU and O-DU can be logical entities implemented as virtualized RAN (vRAN) software running on servers (such as the cloud). Furthermore, some or all of the functions of CU and O-DU can be provided as services for Network Functions Virtualization (NFV).

[0071] The transceiver does not have to be a radio transceiver; it can be, for example, a network transceiver, an optical transceiver, etc. The radio resources allocated by the O-DU can be resources used for radio communication between the O-RU and the UE.

[0072] Subband Non-overlapping Full-Duplex - SBFD

[0073] Operations on uplink, downlink, and sidelink symbols in an exemplary embodiment of this disclosure can be applied to symbols that perform SBFD operations or control (e.g., SBFD (Subband Non-overlapping Full-Duplex) symbols, subband full-duplex). For SBFD symbols, the frequency domain (or frequency resources or frequency bandwidth) is divided into multiple frequency domains (also referred to as, for example, subbands, RB sets, subbandwidths, or subBWPs (bandwidth portions)). The terminal performs transmission and reception in one direction (e.g., downlink or uplink direction) on a unit of subbands, which are the divided domains. For SBFD symbols, the terminal may perform transmission / reception in one of the uplink and downlink directions and may not perform transmission / reception in the other direction. On the other hand, the base station may be able to perform uplink and downlink transmission / reception simultaneously. SBFD symbols may have less frequency domain available for downlink compared to symbols that only perform downlink transmission / reception. Furthermore, SBFD symbols may have less frequency domain available for uplink compared to symbols that only perform uplink transmission / reception.

[0074] Furthermore, for SBFD symbols, the terminal can simultaneously perform uplink and downlink transmission / reception. In this case, the frequency domain transmitted by the terminal and the frequency domain received by the terminal do not need to be adjacent, and a frequency interval (also known as a frequency gap) can be provided between them.

[0075] In addition, sidelink transmission / reception may be included as a transmission / reception direction in units of subbands of the divided domain.

[0076] XDD: Cross Division Duplex

[0077] In one exemplary embodiment of this disclosure, the operation of uplink, downlink, and sidelink symbols can be applied to symbols that perform full-duplex operation or control (e.g., full-duplex symbols). For full-duplex symbols, both the terminal and the base station are capable of simultaneously performing uplink and downlink transmission / reception. For full-duplex symbols, the terminal and the base station can operate to simultaneously perform transmission / reception in an available frequency domain (or frequency resource or frequency bandwidth), or can operate to simultaneously perform transmission / reception in one or more frequency domains (i.e., can operate to perform transmission or reception in other frequency domains). In this case, the frequency domain transmitted by the base station or the terminal and the frequency domain received by the base station or the terminal may not be adjacent and a frequency interval (also called a frequency gap) may be provided between them. Furthermore, for example, for the purpose of reducing interference, one of the terminal and the base station can operate to simultaneously perform transmission / reception (i.e., the other can operate to perform transmission or reception).

[0078] Furthermore, full-duplex operation can be applied to situations where a terminal can simultaneously perform sidelink transmission / reception. Additionally, full-duplex operation can be applied to situations where a terminal can simultaneously perform sidelink transmission / reception and uplink or downlink transmission / reception.

[0079] Downlink control channel monitoring (PDCCH, DCI)

[0080] Many functions operated by the UE involve monitoring the downlink control channel (e.g., PDCCH, see 3GPP TS38.300V15.6.0, Section 5.2.3) to receive, for example, specific control information or data destined for the UE.

[0081] Below is a non-exhaustive list of these features:

[0082] -Paging message monitoring function

[0083] -System information retrieval function

[0084] - Signaling monitoring operations for discontinuous DRX reception function

[0085] - Inactive monitoring operation for discontinuous DRX function.

[0086] - Random access response reception for random access function

[0087] - Reordering function of the Packet Data Convergence Protocol (PDCP) layer.

[0088] PDCCH monitoring is performed by the UE in order to identify and receive information intended for the UE, such as control information and user services (e.g., DCI on the PDCCH and user data on the PDSCH indicated by the PDCCH).

[0089] Downlink control information (which may be referred to as downlink control information, DCI) serves the same purpose in 5G NR as DCI in LTE, namely, as a special set of control information, for example, scheduling downlink data channels (e.g., PDSCH) or uplink data channels (e.g., PUSCH). In 5G NR, many different DCI formats have been defined (see Section 7.3.1 of TS 38.212 v15.6.0).

[0090] The DCI format represents a predetermined format for forming and transmitting corresponding information. Specifically, DCI formats 0_1 and 1_1 are used to schedule the PUSCH and PDSCH in a cell, respectively.

[0091] Each of these functions monitors the PDCCH for a specific purpose and thus from start to finish. PDCCH monitoring is typically controlled at least based on a timer operated by the UE. The timer serves to control PDCCH monitoring, for example, by limiting the maximum amount of time the UE should monitor the PDCCH. For instance, the UE may not need to monitor the PDCCH indefinitely but can stop monitoring after a certain period to conserve power.

[0092] As mentioned above, one of the purposes of DCI on PDCCH is the dynamic scheduling of resources in the downlink, uplink, or even sidelink. Specifically, DCIs in various formats are provided to carry indications of the resources (resource allocation, RA) allocated to a particular user's data channel. Resource allocation may include specifications of resources in the frequency domain and / or time domain.

[0093] Separate gNB architecture

[0094] In the 3GPP standard, a gNB can be divided into gNB-CU (centralized unit) and one or more gNB-DU (distributed unit). This is in Figure 3 As shown in the image.

[0095] The gNB-CU is a logical node that provides support for higher layers of the protocol stack, such as SDAP, PDCP, and RRC. Conversely, the gNB-DU is a logical node that provides support for lower layers of the protocol stack, such as RLC, MAC, and the physical layer. Furthermore, note that if the CU is connected to a 4G core network, the SDAP layer will not be present, as a 5G core network is required to support SDAP.

[0096] Therefore, the PHY and MAC layers terminate at gNB-DU, while layer 3 (RRC) terminates at gNB-CU.

[0097] Each gNB has a single CU; that is, one gNB-DU connects to only one gNB-CU. Alternatively, for flexibility, a gNB-DU can connect to multiple gNB-CUs. One gNB-CU can control multiple gNB-DUs; for example, more than 100 gNB-DUs can connect to one gNB-CU. Each gNB-DU can support one or more cells, so unlike 4G BTS, one gNB can control hundreds of cells. A cell is supported by only one gNB-DU.

[0098] Furthermore, note that the interface between the CU and DU is named F1, and according to 3GPP, it should be an open interface. For NG-RAN, the NG and Xn-C interfaces for a gNB including both gNB-CU and gNB-DU terminate at the gNB-CU. For EN-DC, the S1-U and X2-C interfaces for a gNB including both gNB-CU and gNB-DU terminate at the gNB-CU. The gNB-CU and the connected gNB-DU are only visible to other gNBs and the 5GC acting as a gNB.

[0099] The gNB-CU / DU architecture is specified in more detail, for example, in 3GPP TS 38.401 v17.3.0 (e.g., Section 6.1). The F1 interface is specified in more detail, for example, in 3GPP TS 38.473 v17.3.0.

[0100] Layer 1-Layer 2 Triggered Mobility (LTM)

[0101] When a UE moves from the coverage area of ​​one cell to another, a serving cell change needs to be performed at some point. One possibility is that the serving cell change is triggered by L3 measurements and completed via a synchronized reconfiguration triggered by RRC signaling, involving changes to the PCell and PSCell, and, where applicable, the release of the added SCell. Such a process may involve a full L2 (and L1) reset, resulting in longer latency, greater overhead, and longer downtime compared to beam switching mobility.

[0102] One of the topics in the ongoing 3GPP Rel.18 work on mobility enhancement is supporting Layer-1 to Layer-2 (also known as lower layers) triggered mobility (LTM). The UE is first configured with a set of candidate cells by the RRC (L3). Then, L1 or L2 signaling (e.g., MAC CE (and / or possibly DCI)) is used to trigger a handover of the UE's serving cell between candidate cells without requiring RRC reconfiguration. In other words, to facilitate sequential cell handover, the cell handover should be prepared in such a way that the UE does not require RRC reconfiguration after the handover, regardless of which candidate cell becomes the new serving cell. The goal is to reduce the latency, overhead, and downtime of serving cell changes. Intra-DU and intra-CU / inter-DU cell handovers are included in this scope. Figure 3 The diagram illustrates intra-DU handover between two cells of the same gNB-DU and inter-DU handover between two cells of different gNB-DUs.

[0103] Figure 4 This is a simplified and exemplary message exchange for intra-DU LTM cell handover based on the ongoing 3GPP Rel.18 work. Accordingly, it is exemplarily assumed that the gNB-DU controls multiple cells, including the UE's current serving cell. The gNB-DU is connected to the gNB-CU.

[0104] It is evident that cell handover decisions are based on lower-layer (e.g., Layer 1 RSRP) measurements performed at the UE and reported to the gNB-DU (see “Lower-Layer Measurement Reporting”). More specifically, the UE measures reference signals from one or more candidate cells from the gNB-DU and reports the results to the gNB-DU. The gNB-DU or gNB-CU can use the received measurement results to determine whether to perform LTM on a candidate target cell. A lower-layer cell handover trigger is sent to the UE, allowing the UE to perform a handover from the current cell to another cell of the gNB-DU.

[0105] The benefit achieved through performing measurements and being reported by Layer 1 is low latency.

[0106] In Rel-18, LTM is limited to within a CU, meaning that the serving cell and the candidate cells, including the target cell, belong to the same gNB. However, this should not be construed as a limitation of this disclosure. The disclosed concepts also apply to the case of inter-gNB LTM, meaning that the serving cell and the target cell belong to different gNBs (e.g., different gNB-CUs).

[0107] Random Access Procedure (RA)

[0108] Typically, an RA process can be, for example, a 4-step or a 2-step RA process. Specifically, an RA process may include, for example, 4 or 2 steps or consist of them. However, the term "RA process" should not generally be construed as any particular number of steps or a specific example of an RA procedure described herein.

[0109] In addition, generally speaking, the RA process can be a competition-based RA (CBRA) process or a non-competition RA (CFRA) process (for a high-level description, see, for example, Section 9.2.6 of TS 38.300 v18.0.0).

[0110] The details of the 5G NR RA procedure are described below. Similar to LTE, 5G NR provides the RACH (Random Access Channel (RACH procedure)) procedure (or simply the Random Access Procedure (RA procedure)). For example, the RACH procedure can be used by a UE to access a cell it has discovered. The RACH procedure can also be used in other contexts within NR, such as:

[0111] For handover, when synchronization with the new cell needs to be established;

[0112] If synchronization is lost due to a prolonged period without any uplink transmission from the device, then re-establish uplink synchronization with the current cell.

[0113] If no dedicated scheduling request resource is configured for the device, then request uplink scheduling.

[0114] Numerous events can trigger a UE to perform a random access procedure (see, for example, 3GPP TS 38.300V18.0.0, Section 9.2.6), including the following. The random access procedure is triggered by multiple events:

[0115] - Initial access starting from RRC_IDLE;

[0116] - RRC connection re-establishment process;

[0117] - During RRC_CONNECTED or RRC_INACTIVE, while the SDT process is in progress, DL or UL data arrives when the UL synchronization status is "out of sync".

[0118] - During RRC_CONNECTED or RRC_INACTIVE, while the SDT process is in progress, UL data arrives when there is no PUCCH resource available for SR;

[0119] - Handover;

[0120] - SR failed;

[0121] - Explicit request from RRC during synchronous reconfiguration;

[0122] - The RRC connection recovery process begins with RRC_IN ACTIVE;

[0123] - Establish time alignment for the main tag or secondary tag;

[0124] - Requests to other SIs;

[0125] - Beam fault recovery;

[0126] - Consistent UL LBT failure on SpCell;

[0127] - SDT under RRC_INACTIVE;

[0128] - Location purposes during RRC_CONNECTED, which requires a random access procedure, for example, when UE location needs to be timed in advance;

[0129] - Synchronize with the early UL of LTM candidate cells;

[0130] - LTM cell handover based on RACH.

[0131] If the uplink transmission of a mobile terminal is time-synchronized, the mobile terminal can be scheduled to perform uplink transmission. Therefore, the Random Access Channel (RACH) procedure acts as an interface between asynchronous mobile terminals and orthogonal transmissions of uplink radio access. For example, random access is used to achieve uplink time synchronization for a user equipment (UE) that has not yet acquired or has lost its uplink synchronization. Once the UE has achieved uplink synchronization, the base station can schedule uplink transmission resources for it. One scenario related to random access is when a UE in the RRC_CONNECTED state switches from its current serving cell to a new target cell, performing a random access procedure to achieve uplink time synchronization in the target cell.

[0132] PRACH consists of a preamble format, which comprises one or more preamble sequences transmitted in time-frequency resources. The UE transmits the PRACH preamble in a PRACH timing (RO), which is a time-frequency resource allocated by the network for preamble transmission. Each RO can be configured with 64 preambles. The higher-layer parameter prach-ConfigurationIndex determines the PRACH preamble format and time-domain resources for the PRACH timing by pointing to rows in the random access configuration table (Table 6.3.3.2-2 / 3Z4) of 3GPP TS 38.211.

[0133] There can be at least two types of random access procedures: contention-based random access (CBRA) and contention-free random access (CFRA). In a CBRA, multiple users randomly select a preamble from a preamble pool, and a contention resolution phase determines which user (if any) has their data successfully received by the network. Contention resolution is used to resolve contention between two or more users who select the same preamble. In a CFRA, the preamble is uniquely pre-assigned to users, so there is no possibility of preamble conflict between users, and no contention resolution is required. Exemplary definitions of random access procedures can be found in Section 5.1 of 3GPP TS 38.321, v18.0.0.

[0134] The following will refer to Figure 5a , Figure 5b , Figure 5c and Figure 5d A more detailed description of the different types of RA processes.

[0135] 4-step competition-based RA (CBRA) process

[0136] about Figure 5a The so-called 4-step CBRA process will be described in more detail. Specifically, this 4-step RA process may include or even consist of four "steps" (specifically, four transmissions).

[0137] like Figure 5a As shown, in the first step, the user equipment (UE) sends a random access preamble (i.e., message 1 of the RACH procedure, also known as Msg1) to the base station on the Physical Random Access Channel (PRACH). In other words, the first transmission of the RA procedure (i.e., the first message is time-preceded by all other transmissions in the RA procedure) is (i) sent by the UE to the base station and (ii) includes the random access preamble. When the UE sends the preamble to the gNB, it conveys the selected SS / PBCH block index to the gNB. The network configures the association between the SS / PBCH block index and the PRACH timing and preamble index via broadcast signaling.

[0138] In the second step, the gNB confirms the reception of the preamble by sending a Random Access Response (RAR) on the PDSCH channel, for example. This second transmission is also referred to as Msg2 or message 2 in the RACH procedure. In other words, the second transmission of the RA procedure (i.e., the second transmission in time during the RA procedure) is (i) sent from the base station to the UE, and (ii) includes the Random Access Response.

[0139] RAR can be scheduled by downlink control information (DCI) on the corresponding PDCCH, the CRC of which is scrambled by a random access radio network temporary identifier (RA-RNTI). The PDCCH for RAR can be transmitted in the type 1-PDCCH common search space (CSS). RA-RNTI is a function of time and frequency of the PRACH timing for detecting the preamble (see, for example, 38.321).

[0140] The UE attempts to receive RAR during the RAR window. In NR, the RAR window begins at the first symbol of the earliest CORESET (Control Resource Set) of type l-PDCCH CSS, which begins at least one symbol after the PRACH timing corresponding to the PRACH transmission. The RAR window size is configured by the number of time slots and is less than 10 ms. In the case of CBRA, the DMRS port of the PDSCH channel carrying RAR and the DMRS port of the corresponding PDCCH channel are quasi-co-located with the reference signal used for association and transmission of the corresponding preamble.

[0141] At the start of the random access procedure, the UE sets PREMBLE_TRANSMISSION_COUNTER (preamble transmission counter) to 1. If the UE does not receive a RAR with a RAPID (random access preamble identifier) ​​matching the transmitted preamble during the RAR window, it increments PREMBLE_TRANSMISSION_COUNTER by 1 and retransmits the PRACH preamble after the backoff period. After several PRACH preamble retransmission attempts, when PREMBLE_TRANSMISSION_COUNTER exceeds the higher-layer parameter preambleTransMax, the random access channel (RACH) procedure fails without receiving a RAR with a RAPID matching the transmitted preamble.

[0142] When the UE successfully decodes a RAR that has a RAPID that matches the transmitted preamble and includes the MAC RAR, the UE performs the following operations:

[0143] It processes the received TA commands.

[0144] It handles UL authorization in MAC RAR and, in response, sends PUSCH (also known as Msg3).

[0145] In the third step of the 4-step CBRA procedure, the UE transmits Msg3 on the uplink shared channel (UL-SCH) on the PUSCH in response to the uplink grant in the RAR. If the UE triggering the CBRA procedure is in connected mode and has a C-RNTI, then Msg3 contains the C-RNTI MAC CE, or it contains a CCCH SDU with a contention resolution identifier MAC CE. The triggering of the random access procedure determines the content of Msg3. For example:

[0146] During the initial access period, Msg3 contains an RRCSetupRequest.

[0147] During Radio Resource Control (RRC) re-establishment, Msg3 contains an RRCReestablishmentRequest.

[0148] To transition from the RRC_INACTIVE state to the RRC_CONNECTED state, Msg3 contains either RRCResumeRequest or RRCResumeRequest1.

[0149] To obtain system information, Msg3 contains RRCSystemInfoRequest.

[0150] During the competition-based BFR period, Msg3 includes C-RNTI MAC CE.

[0151] After the UE sends Msg3, it starts the ra-ContentionResolutionTimer and monitors the PDCCH channel. If the gNB fails to decode Msg3, the UE can receive a PDCCH with a CRC scrambled by TC-RNTI, which requests a retransmission of Msg3. When the UE retransmits Msg3, it restarts the ra-ContentionResolutionTimer after the Msg3 retransmission.

[0152] In the fourth step of the CBRA procedure, the gNB sends a message (also known as Msg4) to the UE.

[0153] If Msg3 contains a C-RNTI MAC CE, the gNB sends a PDCCH with a CRC scrambled by the C-RNTI. Upon receiving this PDCCH, the UE stops the ra-ContentionResolutionTimer and considers the CBRA procedure successful.

[0154] If Msg3 contains a CCCH SDU, the gNB sends a PDCCH with a PDSCH scrambled by a CRC scrambled by the TC-RNTI indicated to the UE in the RAR. The corresponding PDSCH echoes the contention resolution identifier received in Msg3. Upon receiving the scheduled PDSCH and the PDCCH with a CRC scrambled by the TC-RNTI, the UE decodes the corresponding PDSCH. If the contention resolution identifier received in the PDSCH matches the contention resolution identifier sent in Msg3, the UE stops the ra-ContentionResolutionTimer and considers the CBRA procedure successful, and sends an Uplink Hybrid Automatic Repeat Request (HARQ) acknowledgment to the gNB to stop any further retransmission of this message.

[0155] Otherwise, if the contention resolution identifier received in PDSCH does not match the contention resolution identifier sent in Msg3, the UE stops the ra-ContentionResolutionTimer and considers the contention resolution unsuccessful.

[0156] If the ra-ContentionResolutionTimer expires before the UE successfully receives the downlink message sent by the gNB, the UE considers the contention resolution unsuccessful. If contention resolution fails, the UE increments PREAMBLE_TRANSMISSION_COUNTER by 1 and restarts the random access procedure using a preamble after the backoff period. After several PRACH preamble retransmission attempts, if PREAMBLE_TRANSMISSION_COUNTER exceeds the higher-layer parameter preambleTransMax, the RACH procedure fails without successfully completing the random access procedure.

[0157] 4-step type of non-competitive RA (CFRA) process

[0158] Figure 5b It shows the relationship with Figure 5aThe 4-step CBRA procedure shown here is a comparison to the simplified CBFA procedure. In the first step, the base station provides the UE with a dedicated preamble for random access, eliminating the risk of collisions—that is, the risk of multiple UEs sending the same preamble. Therefore, the UE subsequently sends the preamble signaled by the base station in the uplink on the PRACH resource. Since CFRA avoids the situation where multiple UEs send the same preamble, the CFRA procedure is essentially completed after the UE has successfully received the random access response.

[0159] from Figure 5b As can be seen, a 4-step CFRA may not include 4 steps or may not consist of 4 steps. It can be called a 4-step CFRA because the transmission of the preamble does not include the PUSCH payload, which is similar to a 4-step CBRA process (and different from the 2-step type described below).

[0160] In more detail, the UE-specific preamble allocation is determined:

[0161] Preamble index.

[0162] A mask index is used to determine the PRACH timing(s) for preamble transmission within a set of PRACH timings associated with the SS / PBCH block or the Channel State Information Reference Signal (CSI-RS) for preamble transmission. The UE transmits on a pre-assigned preamble index and PRACH timing(s) associated with a reference signal (SS / PBCH block or CSI-RS) exceeding a threshold configured by a higher layer, rsrp-ThresholdSSB or rsrp-ThresholdCSI-RS.

[0163] Since the preamble is pre-allocated by the network, there is no contention resolution phase. Because the preamble is dedicated, it also identifies the UE to the gNB. The random access procedure is considered successful after receiving a RAR with a RAPID that matches the transmitted preamble.

[0164] The network configures a dedicated PRACH preamble via `rach-ConfigDedicated`. A dedicated PRACH preamble is also known as a contention-free preamble or a non-contention-based preamble. Dedicated PRACH configuration can be used for reconfigurations with synchronization procedures such as handover. The network can configure dedicated preambles associated with SS / PBCH blocks or CSI-RS resources. The UE identifies the SSB index / CSI-RS resource index of the candidate beam and finds the corresponding PRACH timing and preamble index within each PRACH timing to be used.

[0165] rach-ConfigDedicated includes:

[0166] PRACH timing for dedicated preambles

[0167] Dedicated (i.e., contention-free) PRACH resources. This is a list of preamble resources associated with SS / PBCH blocks or CSI-RS resources.

[0168] Parameters applied to prioritize the CFRA process.

[0169] 2-step CBRA and CFRA processes

[0170] Both RA processes (CBRA and CFRA) are also possible in the 2-step RA type. Specifically, such a 2-step RA process may include two "steps" or even consist of two "steps," and is therefore often referred to as, for example, a 2-step RACH process. Figure 5c The document illustrates a two-step CBRA process, and... Figure 5d The diagram illustrates a 2-step CFRA procedure. It can be seen that the difference between the 2-step RA procedure and the 4-step RA procedure is that the UE's first transmission includes a preamble and a (PUSCH) payload.

[0171] For example (see Figure 5c and Figure 5d 3GPP also defines a two-step process for 5G NR, in which message 1 corresponding to messages 1 and 3 of the corresponding four-step LTE / NR RA process is first sent (for a two-step type called MsgA) (i.e., Msg1 and Msg3 of the four-step CBRA in the two-step CBRA combination MsgA / corresponding to Msg1 and Msg3 of the four-step CBRA in MsgA; and Msg1 and Msg3 of the four-step CFRA in the two-step CFRA combination MsgA / corresponding to Msg1 and Msg3 of the four-step CFRA in MsgA). The MsgA of the two-step RACH type includes a preamble on the Physical Random Access Channel (PRACH) and a payload on the Physical Uplink Shared Channel (PUSCH).

[0172] After MsgA transmission, the UE monitors for responses from the gNB within the configured time window. The gNB then responds with message 2 (referred to as MsgB) corresponding to message 2 of the corresponding 4-step LTE / NR RA procedure and message 4 (for CBRA) (i.e., Msg2 and Msg4 of the 4-step CBRA in the 2-step CBRA combination MsgA / Msg2 and Msg4 of the 4-step CBRA in MsgA; and Msg2 of the 4-step CFRA in the 2-step CFRA combination MsgA / Msg2 of the 4-step CFRA in MsgA).

[0173] The MsgB may include, for example, a Successful Random Access Response (RAR), a Fallback RAR, and an optional backoff indication. If contention is resolved successfully upon receiving a successful RAR, the UE terminates the RA procedure; if a Fallback RAR is received in the MsgB, the UE performs Message 3 transmission (as in a 4-step RACH procedure) and monitors for contention resolution. Further exemplary assumptions are made for a 2-step RACH procedure, such that after determining the RACH type (e.g., 2-step RACH), the UE continues to retry the same RACH type until failure. However, it is also possible that the UE may switch to a 4-step RACH procedure after some retries of the MsgA.

[0174] Another difference in RRC is the large amount of RRC configuration required for 2-step RACH, especially the PUSCH physical resources used to send MsgA (see below).

[0175] The PRACH preamble and PUSCH in MsgA are transmitted in TDM (Time Division Multiplexing) mode. The PUSCH is transmitted at least N symbols after the PRACH transmission, where the value of N depends on the SCS (Subcarrier Spacing) of the active UL BWP.

[0176] Furthermore, the network can semi-statically determine the radio resources to be used for executing mutually exclusive 2-step and 4-step RACH processes. The radio resources used to transmit the first message during the RACH process include at least the RACH timing and the preamble. For example, in a 2-step RACH process, the first message MsgA uses not only the PRACH resources (e.g., the RACH timing and preamble) but also the associated PUSCH resources.

[0177] More specifically, in the 2-step RA type, the PUSCH can be sent without waiting for a response from the network; therefore, the UE needs to know the PUSCH configuration beforehand. The PUSCH configuration is given in the IE msgA-PUSCH-Config:

[0178] - This IE is used to specify the PUSCH allocation for MsgA in the 2-step RA type. It provides the UE with all the configurations required for PUSCH transmission, such as time-domain / frequency-domain resources, DMRS type, MCS, PUSCH Tx power-related parameters, etc.

[0179] - This IE is configured separately for CFRA and CBRA, where for CBRA, the IE msgA-PUSCH-Config is configured as part of the BWP-UplinkCommon IE. For CFRA, the IE msgA-PUSCH-Config is configured as part of the IE CFRA-TwoStep (discussed later) within RACH-ConfigDedicated.

[0180] Furthermore, there is no closed-loop uplink timing control during message-A PUSCH transmission. Therefore, message-A PUSCH transmissions may arrive with relatively large timing misalignment compared to other uplink transmissions.

[0181] Typically, for RACH preambles, see, for example, 3GPP TS 38.211 V18.1.0, “Table 6.3.3.2-2: Random access configurations for FR1 and paired spectrum / supplementary uplink” and Section 6.3.3.2, “Mapping to physical resources”.

[0182] The UE selects either a 2-step or 4-step RA type when initiating the RA procedure based on network configuration. For the CBRA case:

[0183] When the network configures both 4-step RA type and 2-step RA type, the UE uses an RSRP threshold to select between the two types. The RSRP threshold is configured by the msgA-RSRP-Threshold field.

[0184] - If RSRP is higher than the threshold, the UE selects the 2-step RA type; otherwise, it selects the 4-step RA type.

[0185] For CFRA cases:

[0186] - When CFRA resources are configured for 4-step RA type, the UE performs random access of 4-step RA type.

[0187] - When CFRA resources are configured for 2-step RA type, the UE performs random access of 2-step RA type.

[0188] - The network is not configured with CFRA resources for both 4-step and 2-step RA types.

[0189] Compared to a 4-step RACH, the advantages of a 2-step RACH are:

[0190] Reduce control signal overhead

[0191] Reduce latency

[0192] PUSCH transmission is allowed at the first step.

[0193] Beam Management (BM) & Transmission Configuration Indication (TCI) Signaling Framework

[0194] Beam management (BM) in 5G NR has adopted a so-called Transport Configuration Indication (TCI) signaling framework. The beam used for a target channel / signal (e.g., PDSCH, PDCCH, CSI-RS) can be indicated by a TCI state. The TCI state contains parameters used to configure the quasi-co-location (QCL) relationship between the source reference signal (RS) and the target channel / signal. By measuring the source RS, the UE can set the receive coefficients (e.g., spatial filters) for receiving the target channel / signal. In Rel-17, a unified TCI framework has been introduced, allowing TCI states to be applied to multiple channels / signals. The same TCI state can be applied to both DL and UL transmissions (such as PUSCH, PUCCH, SRS), referred to as a "joint TCI state." In other words, a "joint TCI state" is the TCI state to be applied to / used for both UL and DL transmissions.

[0195] Alternatively, UL and DL transmissions can each have separate "DL TCI states" and "UL TCI states". The UL TCI state is then applied to / for the UE's UL transmissions, and the DL TCI state is applied to / for the UE's DL transmissions. Typically, multiple UL and / or DL ​​TCI states can exist (e.g., one UL TCI state for PUCH transmissions and one TCI state for PSUCH transmissions).

[0196] The following describes further details of the BM and TCI signaling framework in 5G NR.

[0197] Beam management

[0198] Beam management is a collection of Layer 1 (PHY) and Layer 2 (MAC) processes used to establish and retain optimal beam pairs for good connectivity. A beam pair consists, for example, of a transmit beam and a corresponding receive beam in one link direction.

[0199] Before a UE can communicate with the network, it must perform a cell search and selection process and obtain initial cell synchronization and system information. The first step in this process is to obtain frame synchronization, identify the cell identifier, and decode the MIB and SIB1.

[0200] In the case of a multi-antenna system that transmits multiple beams, detecting the beam from the gNB is also part of the initial process (e.g., where the UE typically detects all beams in the search space).

[0201] Beam management can be divided into the following three main processes:

[0202] Initial beam establishment,

[0203] Beam adjustment (also known as beam tracking and refinement), and

[0204] Beam fault recovery.

[0205] In short, the network can be configured with periodic or semi-persistent beam reporting or trigger aperiodic beam reporting to promptly acquire the best / preferred beam for data / control transmissions. The UE performs measurements on reference signals (SSB and / or CSI-RS) configured by the gNB to determine the best receive (Rx) beam (and, in the case of beam correspondence, possibly the transmit Tx beam). In one example, to determine the UE's Tx beam, the UE is configured by the gNB to transmit SRS (Sound Reference Signal) to the gNB in ​​different directions, and the gNB then determines and indicates the best / preferred UL beam to the UE using an SRI (SRS Resource Indicator).

[0206] When the gNB scans the beams by using different DL beams for each SSB, multiple beam management procedures can occur during the RACH (Random Access Channel) procedure, and the UE informs the gNB of the best / preferred Rx beam by using specific PRACH resources mapped to the selected DL beam. The beam management procedure can be, for example, part of or using the CSI framework. CSI reports can be configured by the network to occur periodically (e.g., RRC-configured), semi-persistently (e.g., triggered by MAC-CE and / or DCI), or aperiodically (e.g., triggered by DCI). For beam management, when used as part of the CSI framework, the UE can be configured using the information element IE CSI-ReportConfig, where the high-level parameter reportQuantity is set to one or more of “cri-RSRP”, “cri-SINR”, “ssb-Index-RSRP”, “ssb-Index-SINR”, “cri-RSRP-Index”, “ssb-Index-RSRP-Index”, “cri-SINR-Index”, and “ssb-Index-SINR-Index”.

[0207] Initial beam establishment

[0208] Initial beamforming includes, for example, the process and functionality of initially establishing beam pairs in the downlink (DL) and uplink (UL) transmission directions during connection establishment. In the current 5G NR standard, this can be accomplished via beam scanning, where different SSBs associated with different transmission Tx beams are transmitted in different OFDM symbols.

[0209] During beam scanning, the gNB transmits beams in all directions in bursts at regularly defined intervals. Whenever the UE synchronizes with the network, it reads the synchronization signal block SSB and extracts the primary synchronization signal PSS, secondary synchronization signal SSS, physical broadcast channel PBCH, and demodulation reference signal DMRS of PBCH.

[0210] A single SS block spans four OFDM symbols in time and 240 subcarriers (20 resource blocks) in frequency. Each SS block corresponds to a specific beamformation in a different direction. A set of SS blocks forms an SS burst set spanning a 5ms window. SS bursts repeat periodically with a period of 20ms, where the maximum number of SS blocks in an SS burst set depends on the operating frequency range.

[0211] The UE can then search for the strongest DL Tx beam, for example, by also adjusting the corresponding DL receive Rx beam on the UE side, and then report the selection to the gNB via the corresponding RACH timing and preamble. In this way, an initial beam pair is established, which remains valid after the connection is established until the UE receives a new beam indication.

[0212] Beam Adjustment

[0213] After the initial beam pair has been established, it can be continuously adjusted to account for UE movement and / or changes in the environment. This can be referred to as beam tuning. Furthermore, beam management can also include refining the beam shape, for example, using a narrower CSI-RS beam compared to the relatively wide SSB beam used for initial beam establishment.

[0214] The UE measures beam strength by measuring the received signal power. In idle mode, beam measurement can be based on the synchronization signal, and in connected mode, beam measurement can be based on the Channel State Information Reference Signal (CSI-RS) in the DL and the Sounding Reference Signal (SRS) in the UL. The UE periodically searches for the optimal beam using predefined threshold criteria defined by the gNB and identifies the beam with the highest received reference signal power (RSRP). The UE can then perform a beam reporting procedure.

[0215] Since beamforming does not occur simultaneously at the gNB and UE, one beam (identified by its index) from each process is the result that can be used for UL or DL ​​communication. The gNB can use information and recommendations from the UE to enhance beamforming. The transmission of control signaling and data can benefit from the beams selected in this process, as beamforming is designed to improve link quality based on constantly changing radio channel conditions. The gNB is responsible for deciding which UL Rx and DL Tx beams it will use and instructing the UE on them. Knowing the beams that the gNB is using, the UE is able to select its own UL Tx and DL Rx beams.

[0216] Beam fault recovery

[0217] If the beam cannot be tracked through the beam adjustment process described above, a beam failure may occur. This could be, for example, when the current beam pair is suddenly and unexpectedly blocked, and the beam tracking function cannot react quickly enough. Once a beam failure occurs, beam recovery typically requires the following steps:

[0218] Beam fault detection

[0219] Candidate beam identification,

[0220] Resume request transmission, and

[0221] Network response to beam recovery request.

[0222] For example, in the event of a beam failure due to poor channel conditions, a beam recovery procedure is triggered to restore a new beam. The UE monitors multiple reference signals and identifies a beam failure once the failure triggering conditions are met. When a beam failure occurs, the UE selects the next best beam to transmit in the Random Access (RA) preamble. If the first attempt at RA fails, it scans for another beam to perform another RA procedure. The RA preamble is transmitted in the PRACH. Finally, the UE receives downlink resource allocation and uplink grant on the Physical Downlink Control Channel (PDCCH).

[0223] Beam measurement and reporting

[0224] The general operations performed during one or more of the above-mentioned main processes may involve one or more of the following:

[0225] Beam scanning, also known as beam scanning, involves covering a spatial area with a set of beams that are transmitted and received according to pre-specified intervals and directions.

[0226] Beam measurement, i.e., the evaluation of the quality of the (beam) signal received at the gNB or UE,

[0227] Beam determination, that is, selecting one or more suitable beams at the gNB or UE based on measurements obtained using the beam measurement process, and

[0228] Beam reporting is the process by which the UE sends beam quality and beam decision information to the gNB.

[0229] In short, beam measurement and reporting involves the UE measuring a set of reference signals (e.g., SSB or CSI-RS) corresponding to different downlink Tx beams. The UE then reports these measurements to the network (e.g., the serving gNB). Based on the received measurements, the network can then, for example, determine the appropriate downlink Tx beam for the UE. Measurement and reporting can be based, for example, on a CSI framework (see the following sections).

[0230] Channel State Information Measurement and Reporting Framework

[0231] The network can configure the UE to perform measurements and report the results according to configuration parameters. The measurements and reports performed by the UE can be, for example, based on a 5G NR-based CSI reporting framework, which can generally be considered to involve two parts: one for configuration and the other for triggering CSI reporting.

[0232] CSI-MeasConfig IE is the highest level IE for CSI configuration, and it configures not only L1-RSRP related measurements / reports for beam management, but also general CSI related measurements / reports (such as CQI) to determine appropriate MIMO precoding, modulation, and coding, etc.

[0233] CSI-MeasConfig IE primarily configures three types of lists:

[0234] 1) List of RS resource sets

[0235] Each RS resource set in the list contains one or more RS resources. For example, multiple CSI-RS resources can be configured by the NZP-CSI-RS-Resource IE and then grouped into RS resource sets by the NZP-CSI-RS-ResourceSet IE. Other possible RS resources are defined by the IEs CSI-IM-Resource and SSB-Index.

[0236] 2) List of CSI-ResourceConfig IEs

[0237] The different CSI-ResourceConfigs in the list may contain one or more different RS resource sets selected from list element 1). This may include NZP-CSI-RS-ResourceSet, CSI-IM-ResourceSet, and / or CSI-SSB-ResourceSet, each identified by a suitable ID (see, for example, NZP-CSI-RS-ResourceSetId, CSI-IM-ResourceSetId, and / or CSI-SSB-ResourceSetId).

[0238] 3) List of CSI-ReportConfig IEs.

[0239] Different CSI-ReportConfig configurations in the list represent different CSI reporting instances. This is an information element that links the reporting configuration of that CSI-ReportConfig (such as via PUCCH or PUSCH) to the measurement resource set (i.e., one of the CSI-ResourceConfigs in element 2 of the list above). The CSI-ResourceConfigId included in the CSI-ReportConfig IE identifies the CSI-ResourceConfig IE to be used.

[0240] Measurements and reporting can be performed in the time domain on a periodic, semi-periodic, or aperiodic basis. Measurement results are reported by the UE to the gNB, for example, as uplink control information on the PUCCH or PUSCH. In a 5G-compliant example, CSI reporting is performed by the UE based on the definitions given in Section 6.3 of 3GPP TS 38.212 v18.1.0.

[0241] There are at least two types of reference signals that can be used for measurement: SSB (see SSB-Index mentioned above) and CSI-RS (Channel State Information-Reference Signal; see NZP-CSI-RS-Resource IE and CSI-IM-Resource IE above). SSB is always transmitted by the network and is not UE-specific, thus it is inflexible. For example, SSB can be used in conjunction with a relatively wide beam. On the other hand, CSI-RS can be specifically configured for the UE and is very flexible regarding the time and frequency (how often) of its transmission (time domain) and regarding frequency domain resources. CSI-RS can be used in conjunction with a relatively narrow beam because it can be configured for only one or a few UEs.

[0242] For example, based on 3GPP TS 38.214—section 5.2.1 of which there are several reporting components of CSI in 5G NR (i.e., several different types of CSI):

[0243] CQI (Channel Quality Information)

[0244] PMI (Precoding Matrix Indicator)

[0245] CRI (CSI-RS Resource Indicator)

[0246] SSBRI (SS / PBCH resource block indicator).

[0247] LI (Layer Indicator)

[0248] Rl (rank indicator)

[0249] L1-RSRP, and / or

[0250] Capability Index.

[0251] A UE can report one or more metrics, or a combination of different metrics. Typically, metrics can be grouped into two types:

[0252] - Quantities related to L1-RSRP (e.g., cri-RSRP and ssb-index-RSRP, see IE later) CSI-Report Config )

[0253] - CSI-related quantities (e.g., from IE) CSI-Report Config The rest of the text)

[0254] L1-RSRP-related quantities are new quantities introduced for the first time in NR (Rel-15), and one purpose is to facilitate beam management. In contrast, CSI-related quantities (such as CQI) are conventional quantities that already exist in LTE. Base stations use those conventional CSI-related quantities to select, for example, appropriate MIMO precoding, modulation, and coding sizes to match channel conditions.

[0255] Exemplary implementations follow the current definitions of 5G 3GPP standards, such as those defined in 3GPP TS 38.331, and may involve, for example, the following information elements (IEs):

[0256] CellGroupConfig, CSI-MeasConfig, CSI-ReportConfig, CSI-ResourceConfig, NZP-CSI-RS-Resource and NZP-CSI-RS-ResourceSet.

[0257] In short, LTM measurements and reporting can be based on the 5G CSI reporting framework. Specifically, the information element (IE) CSI-MeasConfig and the information element CSI-ReportConfig indicate the parameters of the CSI reporting framework that the UE can use to measure and then report the measurement results.

[0258] A possible and exemplary sequence of IEs used to define measurement and reporting according to the CSI framework is shown below:

[0259] - CellGroupConfig IE

[0260] o SpCellConfig or ScellConfig's ServingCellConfig IE

[0261] CSI-MeasConfig IE

[0262] CSI-ResourceConfig IE

[0263] o NZP-CSI-RS-ResourceSet

[0264] NZP-CSI-RS-Resource

[0265] o CSI-SSB-ResourceSet

[0266] SSB-Index

[0267] o CSI-IM-ResourceSet

[0268] CSI-IM-Resource

[0269] CSI-ReportConfig IE

[0270] Figure 6 An exemplary and simplified signaling handover for measurement reporting is illustrated, assuming periodic transmission of a reference signal and a report. It is evident from this that the gNB configures the UE for measurement and reporting (e.g., as described above). The UE follows this configuration for measurement and reporting processing. The gNB transmits a reference signal, and the UE performs the configured measurement on the received reference signal and generates a CSI report, which it then sends to the gNB. This can be repeated, for example, periodically as configured.

[0271] Transport Configuration Indicator (TCI) Status

[0272] The gNB and UE can use a so-called Transmission Configuration Indication (TCI) signaling framework. This means that the gNB can indicate to the UE, via a specific TCI state, the beam for a target channel (such as PDSCH, PDCCH) or a target reference signal (such as Channel State Information Reference Signal, CSI-RS). The TCI state can be used by the UE to receive the target channel or target signal. The TCI state defines parameters used to define the quasi-co-located (QCL) relationship between the source reference signal (RS) and the target channel or target signal. In short, when the source signal and the target signal are quasi-co-located (QCLed), the two signals may have experienced (very) similar channel conditions, such as the same location and the same antenna, using the same spatial filter, etc. Therefore, by measuring the source reference signal, the UE can appropriately set the receive coefficients (e.g., spatial filter) and / or tune the receive antenna based on the source reference signal to receive the target channel / signal.

[0273] More specifically, the similarity of the channel conditions of QCLs can be affected by different parameters that the two signals may share, including one or more of the following:

[0274] Doppler shift

[0275] Doppler extension

[0276] Average delay

[0277] Delay spread

[0278] Spatial Rx parameters

[0279] Accordingly, different types of QCLs can be defined in the 5G NR system, such as:

[0280] Type Description

[0281] QCL Type A: Doppler frequency shift, Doppler spread, average delay, delay spread

[0282] QCL type B Doppler frequency shift, Doppler spread

[0283] QCL type C Doppler shift, average delay

[0284] QCL type D space Rx parameter

[0285] In frequency range 1 (FR1, below 7.125 GHz), QCL type AC is applicable, and in frequency range 2 (FR2, above 24.250 GHz), QCL type AD is applicable. For example, QCL type D for FR2 indicates that the target signal (such as PDCCH / PDSCH / CSI-RS) is transmitted using the same spatial filter as the source reference signal associated with that TCI state.

[0286] For example, the TCI state can be similar to a spatial filter used for sending from a transmitting point or TRP (transmitter-receiver point) and receiving to a transmitting point or TRP (transmitter-receiver point).

[0287] Version 17 introduces a unified TCI framework that allows TCI states to be applied jointly to DL and UL channels / signals, including not only downlink but also target uplink channels (such as PUSCH or PUCCH) or target uplink reference signals (such as sounding reference signals (SRS)); such TCI states can be referred to as "joint TCI states". Alternatively, Version 17 supports the possibility that UL transmissions can have separate "TCI UL states".

[0288] An example TCI state operation involves the following:

[0289] Step 1: The UE is configured with a TCI status list, for example, via higher-layer signaling from the gNB (such as RRC signaling), and may depend on the UE's capabilities.

[0290] Step 2: Then, activate a subset of the TCI states from all configured TCI states. For example, the UE receives a Medium Access Control (MAC) Control Element (CE) message from the gNB to activate, for example, a subset of up to eight pre-configured TCI states. Each activated TCI state is mapped by the UE to a code point (e.g., 3 bits) that can be indicated by the DCI field “Transmission Configuration Indication”.

[0291] Step 3: Then, the UE actually uses one of the eight active TCI states to receive the target channel / signal. For example, the UE receives a DCI signal that indicates one of the code points in the DCI field "Transmission Configuration Indication". The UE applies the indicated code point to (multiple) target channels or (multiple) target signals.

[0292] TCI status configuration (TCI configuration)

[0293] According to an exemplary implementation (see, for example, 3GPP TS 38.214, v18.1.0), the UE can be configured with a list of up to M TCI states via higher-layer signaling (e.g., RRC signaling). The number M of configured TCI states depends on the UE's capabilities, and, for example, up to 128 TCI states for PDSCH and up to 64 TCI states for PDCCH.

[0294] As described in 3GPP TS 38.331, v18.0.0, Section 6.3.2, the IE TCI-State associates one or two DL reference signals (here, SSB and / or CSI-RS) with the corresponding quasi-co-address (QCL) type (for DL ​​or joint DL / UL operation), as follows:

[0295] TCI-State Information elements

[0296] -- ASN1START

[0297] -- TAG-TCI-STATE-START

[0298] TCI-State ::= SEQUENCE {

[0299] tci-StateId TCI-StateId,

[0300] qcl-Type1 QCL-Info,

[0301] qcl-Type2 QCL-Info OPTIONAL,--Need R

[0302] ..., [[

[0304] additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL, -- Need R

[0305] pathlossReferenceRS-Id-r17 PUSCH-PathlossReferenceRS-Id-r17OPTIONAL, -- Cond JointTCI

[0306] ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL -- CondJointTCI ]]

[0308] }

[0309] QCL-Info ::= SEQUENCE {

[0310] cell ServCellIndex OPTIONAL, -- Need R

[0311] bwp-Id BWP-Id OPTIONAL, -- Cond CSI-RS-Indicated

[0312] referenceSignal CHOICE {

[0313] csi-rs NZP-CSI-RS-ResourceId,

[0314] ssb SSB-Index

[0315] },

[0316] qcl-Type ENUMERATED {typeA, typeB, typeC, typeD}, ...

[0318] }

[0319] -- TAG-TCI-STATE-STOP

[0320] -- ASN1STOP

[0321]

[0322]

[0323]

[0324] For the uplink, information elements TCI-UL-State Defined in Section 6.3.2 of 3GPP TS 38.331.

[0325] Further improvements

[0326] Version 18 introduced lower-level mobility, also known as L1 L2 triggered mobility (LTM). This has been specifically referenced above. Figures 3 to 4 Some aspects of it are described. Further details of the LTM signaling process can be found in 38.300_CR0833 (R2-2401610), and... Figure 7 The image shows (corresponding to 38.300_CR0833 (R2-2401610)) Figure 9 .2.3.5.2-1).

[0327] Specifically, in step 6, the gNB decides to perform a cell handover to the target cell and sends an LTM cell handover command MAC CE to trigger the handover. This LTM cell handover command may include:

[0328] The target configuration ID is an index indicating the candidate configuration index of the target cell.

[0329] Beams indicated by TCI status or by DL and UL TCI status, and

[0330] Pre-time command for the target cell (if available).

[0331] The UE switches to the target cell and applies the candidate configuration indicated by the candidate target configuration index ID. In step 7, if the UE does not have a valid TA in the target cell, the UE can perform the RA procedure in the target cell.

[0332] If not executed Figure 7If early synchronization with the target cell is not performed in optional step 4b, the UE may specifically lack a valid TA for the target cell. Therefore, if early synchronization with the target cell is not performed, the RA procedure is typically performed (and vice versa).

[0333] The beam and / or TCI state indicated in the cell handover command are intended for use by the UE for transmission and / or reception on the target cell. However, according to the traditional random access procedure, it is the UE that selects a beam (which may be different from the indicated beam) to transmit PRACH and monitor RAR (Random Access Response) on the target cell. Therefore, it is unclear when the UE should apply the beam indicated in the cell handover command. Consequently, mismatched beam usage between the base station and the UE may occur. Regarding this, the following consensus was reached at the RAN2#124 meeting (November 2023):

[0334] For CFRA configured with RRC, the UE selects from the beams used in the RRC configuration for CFRA (if the beams are above the RSRP threshold, as is the case in the traditional configuration); and

[0335] For CBRA, the UE selects a beam based on RSRP and ignores the beam indicated in CBRA.

[0336] Furthermore, at the RAN1#116 meeting (February 2024), it was agreed that for RA-based LTM procedures (i.e., LTM procedures with RA procedures), the UE will use the TCI state indicated in the LTM cell handover command after completing the RA procedure. However, the stage / time at which the UE should apply the beam indicated in the cell handover command remains unclear.

[0337] The inventors have recognized the aforementioned problems with beam usage after cell handover in the case of RACH procedures. Therefore, the inventors have identified the possibility of providing an improved procedure to allow avoidance of one or more of the aforementioned disadvantages. The present invention relates to different solutions and variations for such improved procedures. While problems have been described with respect to L1 / L2 triggered mobility in NR version 18, these solutions and improved procedures are generally applicable to scenarios where communication devices perform the following:

[0338] Receive cell handover signaling, which indicates (i) cell handover to the target cell and (ii) the TCI state (or beam) to be used by the UE.

[0339] (Based on the cell handover signaling) Handover to the target cell; and

[0340] The RA procedure is performed in the target cell (specifically, the first transmission of the UE in the target cell may be a transmission of the RA procedure (i.e., Msg1 or MsgA in LTE / NR)).

[0341] Note that this disclosure refers to this type of cell handover as "RA-based cell handover".

[0342] This disclosure provides a method to allow a UE (and the base station of the target cell) to obtain a suitable beam for communicating with the base station of the target cell after performing an RA-based cell handover to the target cell, while reducing the risk of beam usage mismatch (which occurs when the base station and the UE assume they will use different beam / TCI states). Specifically, the use of the beam / TCI state indicated to the UE along with the cell handover command can begin at an appropriate time.

[0343] Example

[0344] This disclosure specifically provides scheduling equipment, corresponding methods for base stations (or scheduling equipment), communication equipment (or UE), corresponding methods for base stations and communication equipment, communication systems including such base stations and communication equipment, and integrated circuits for controlling the base station / communication equipment to perform the corresponding methods.

[0345] As described above, this disclosure provides a scheduling device (e.g., a base station) and a communication device (e.g., a scheduled device or user equipment). This disclosure also provides a system including a scheduled device and a scheduling device, as well as corresponding methods, integrated circuits, and programs. Figure 8 An example of such a communication system is shown. Communication system 800 can be a wireless communication system according to the technical specifications of 5G, particularly an NR communication system. However, this disclosure is not limited to 3GPP NR terrestrial networks (TN), and can also be applied to NTN or other wireless or cellular systems.

[0346] Figure 8 A general, simplified, and exemplary block diagram of a communication device 810 (exemplarily assumed to be a UE herein) and a scheduling device 860 (exemplarily assumed to be located in a base station, such as in an LTE eNB (which may alternatively be referred to as an ng-eNB) or a gNB in ​​5G NR) is shown. However, typically, in the case of a sidelink connection between two terminals, the scheduling device can also be a terminal. Furthermore, particularly with regard to URLLC use cases; the communication device 810 can also be a sensor device, a wearable device, or a controller for a connected vehicle, or an automated machine in an industrial plant. Additionally, the communication device 810 can be used as a relay between a base station and another communication device (e.g., this disclosure is not limited to a communication "terminal" or a user "terminal").

[0347] like Figure 8 As shown, communication device 810 and base station 860 (eNB / gNB) can communicate with each other via (wireless) physical channel 850 using their transceivers 820 (UE side) and 870 (base station side), respectively. Base station 860 and terminal 810 together form communication system 800. Communication system 800 may also include other entities, such as... Figure 1 The entities shown.

[0348] transceiver

[0349] like Figure 8 As shown (on the left), a communication device may include a transceiver and circuitry (or processing circuitry), and a base station may include a transceiver and (processing) circuitry. A transceiver may further include and / or function as a receiver and / or transmitter. In this disclosure, in other words, the term "transceiver" is used for the hardware and software components that allow a communication device or, consequently, a base station to transmit and / or receive radio signals via a wireless channel. Thus, a transceiver corresponds to a receiver, a transmitter, or a combination of a receiver and a transmitter. Generally, it is assumed that base stations and communication devices are capable of both transmitting and receiving radio signals. However, particularly for some applications of eMBB, mMTC, and URLLC (smart home, smart city, industrial automation, etc.), it is conceivable that devices (such as sensors) may only receive signals. Furthermore, the term "circuitry" includes processing circuitry formed by one or more processors or processing units.

[0350] The transmitter can be responsible for performing the transmission process and other related processes. The receiver can be responsible for performing the reception process and other related processes, such as monitoring the channel.

[0351] circuit

[0352] The circuitry or processing circuitry can be one or more pieces of hardware, such as one or more processors or any LSI. Input / output points (or nodes) may exist between the transceiver and the processing circuitry, through which the processing circuitry can control the transceiver, i.e., control the receiver and / or transmitter and switch between receiving and transmitting data. The transceiver, acting as both a transmitter and receiver, may include an RF (radio frequency) front end, comprising one or more antennas, amplifiers, RF modulators / demodulators, etc. The processing circuitry can perform control tasks, such as controlling the transceiver to transmit user data and control data provided by the processing circuitry and / or receive user data and control data further processed by the processing circuitry. The processing circuitry can also be responsible for performing other processing, such as determination, decision-making, calculation, measurement, etc.

[0353] Communication equipment (e.g., UE) and corresponding methods

[0354] According to an exemplary embodiment, a communication device 810 is provided, for example, such as... Figure 8 The UE is shown on the left. The communication device 810 includes a transceiver 820 and a circuit 830.

[0355] Transceiver 820:

[0356] For example, in the source cell, control signaling (referred to in this disclosure as "cell handover signaling") is received. Typically, cell handover can be received when the UE is in the RRC_CONNECTED state and / or the source cell is the UE's current serving cell;

[0357] Send one or more transmissions of the RA process in the target cell;

[0358] Receive one or more transmissions of the RA process in the target cell; and

[0359] Send the first PUSCH transmission or the first PUCCH transmission (whether to send the first PUSCH or the first PUCCH depends on the details of the determination of the "TCI start time", which will be explained further below; for example, if the start time is based on the completion of the first PUCCH, then there is a first PUCCH to send).

[0360] (Processing) Circuit 830:

[0361] Obtain cell handover command and indication of TCI status from cell handover signaling (in this disclosure, the indication is referred to as "TCI status indication", and the TCI status is referred to as "indicated TCI status")

[0362] According to the cell handover command, a cell handover to the target cell is performed (note that this disclosure is not limited to any specific details of cell handover).

[0363] Perform the RA procedure in the target cell (note that this disclosure is not limited to any specific details of the RA procedure); and

[0364] Determine the TCI start time, from which the indicated TCI status will be used (the details of this determination will be explained further below).

[0365] For example, the communication device 810 can obtain the cell handover command and TCI status indication from the cell handover signaling by parsing the cell handover signaling and / or extracting the cell handover command and TCI status indication from the cell handover signaling.

[0366] Note that circuit 830 can implement more than the functions described above. For example, circuit 830 can also control transceiver 820 to receive cell handover signaling and / or receive or transmit other data / control information (in particular, control the transceiver to perform any other transmission / reception disclosed herein). Therefore, circuit 830 is exemplarily considered to include cell handover circuit 835, which is configured to perform the aforementioned processes of cell handover signaling, cell handover, and determination of the TCI start time after cell handover (and RA procedure). This configuration can be provided through hardware adaptation and / or software.

[0367] Figure 9 An exemplary functional structure of a cell handover circuit 835 is shown. Specifically, the cell handover circuit 835 may include:

[0368] Cell handover signaling processing circuit 910 obtains cell handover command and TCI status indication from cell handover signaling.

[0369] Cell handover execution circuit 920, which performs cell handover to the target cell according to the cell handover command; and

[0370] TCI start time determination circuit 930 determines the TCI start time, from which the indicated TCI state will be used.

[0371] Note that the cell handover circuit 835 can also implement more functions, as it can also be responsible for performing the aforementioned RA process, for example.

[0372] Corresponding to the aforementioned communication equipment, a method executed by the communication equipment is provided. For example... Figure 11 As shown, the method includes the following steps:

[0373] Receive S1100 cell handover signaling;

[0374] Obtain the S1110 cell handover command and TCI status indication from the cell handover signaling;

[0375] According to the cell handover command, execute S1120 to handover to the target cell;

[0376] Performing the S1130 RA procedure in the target cell includes sending one or more transmissions of the RA procedure and receiving one or more transmissions of the RA procedure.

[0377] The S1140TCI start time is determined, and from this TCI start time, the indicated TCI state will be used (details of this determination are further explained below); and

[0378] Send the first PUSCH transmission or send the first PUCCH transmission on S1150.

[0379] Base Station (BS) and Corresponding Methods

[0380] For example Figure 8 As shown on the right-hand side, according to another exemplary embodiment, a base station 860 is provided. The base station 860 includes a transceiver 870 and circuitry 880.

[0381] (Processing) Circuit 880:

[0382] It is determined that the communication equipment will perform a cell handover from the source cell to the target cell according to the cell handover signaling, which includes an indication of the TCI status sent to the communication equipment in the source cell, and the target cell is operated by the base station;

[0383] (In the target cell) Perform the RA procedure with the communication equipment; and

[0384] The TCI start time is determined, from which the TCI indicated by the cell handover signaling will be used by the communication equipment (the details of this determination will be further explained below).

[0385] Transceiver 870:

[0386] (In the target cell) send one or more transmissions of the RA process to the communication equipment.

[0387] (In the target cell) receiving one or more transmissions of the RA process of the communication equipment, and

[0388] (In the target cell) Receive the first PUSCH transmission or the first PUCCH from the communication equipment.

[0389] Circuit 880 can implement more than the functions described above. For example, circuit 880 can determine the TCI state that the communication device will use at the TCI start time, and / or control transceiver 870 to send cell handover signaling and / or receive or send data / control information (in particular, control the transceiver to perform any other sending / receiving disclosed herein).

[0390] Therefore, circuit 880 is exemplarily considered to include cell handover circuit 885, which can be configured to perform (i) determining that the communication device will perform cell handover, (ii) determining the TCI state that the communication device will use at the TCI start time, (iii) generating cell handover signaling, (iv) performing the RA procedure with the communication device, and (v) determining the TCI start time. This configuration can be provided by hardware adaptation and / or by software.

[0391] Figure 10 An exemplary functional structure of a cell handover circuit 885 is illustrated. Specifically, the cell handover circuit 885 may include:

[0392] The cell handover determination circuit 1010 can determine whether the communication equipment needs to perform a cell handover; and

[0393] TCI start time determination circuit 1020, which can determine the TCI start time.

[0394] Note that the cell handover circuit 885 can also perform more functions, as it can, for example, also be responsible for performing the aforementioned RA process.

[0395] Note that, typically, the source and destination cells in a cell handover performed by communication equipment can be operated by the same BS, or by different BSs. In other words, BS 860 can operate the destination cell without operating the source cell, or BS 860 can operate both the destination and source cells.

[0396] Typically, the BS operating the source cell can be responsible for (i) determining whether / when the communication equipment should perform a cell handover, (ii) determining the TCI state to be indicated in the cell handover signaling, and (iii) generating and / or sending the cell handover signaling to the communication equipment. Therefore, in the case where the BS 860 also operates the source cell, circuit 880 can also:

[0397] Determine the TCI state that the communication device will use at the TCI start time (this can also be accomplished, for example, by the TCI start time determination circuit 1020); and

[0398] Generate cell handover signaling, which includes (a) a cell handover command indicating that a cell handover should be performed and (b) an indication of the TCI status.

[0399] Therefore, for the case where BS 860 also operates the source cell:

[0400] The cell handover circuit 885 may further include a cell handover signaling generation circuit 1030, which can be configured to generate cell handover signaling, and

[0401] The TCI start time determination circuit 1020 can also, for example, determine the indicated TCI state.

[0402] In addition, when the BS 860 also operates the source cell, the BS transceiver 870 can send cell handover signaling to the communication equipment from the source cell.

[0403] Note that if the BS 860 does not operate the source cell, notification can be received from the source cell (e.g., by receiving an instruction via an interface between network nodes):

[0404] The communication equipment needs to perform a cell handover to the target cell, and

[0405] The TCI status indicated in the corresponding cell handover signaling sent to or to be sent to the communication equipment.

[0406] When BS 860 does not operate the source cell, circuit 880 can therefore:

[0407] Receive instructions / signals

[0408] Based on the indication / signaling, determine the indicated TCI status, and

[0409] Based on the aforementioned indication / signaling, the communication device will perform the previously mentioned determination of cell handover based on cell handover signaling including indications of TCI status.

[0410] Note that in this case, the target cell BS does not make a decision in the determination, but rather derives / obtains the result of a decision already performed by the source cell BS (whether to perform cell handover / target cell / indicate which TCI state).

[0411] In addition, corresponding to the aforementioned base station, a method executed by the base station is provided. For example... Figure 11 As shown, the method includes the following steps:

[0412] It is determined that the S1105 communication device needs to perform a cell handover from the source cell to the target cell based on the control signaling sent to the communication device in the source cell. The target cell is operated by the base station.

[0413] (In the target cell) Perform the S1145 RA procedure with the communication equipment, including: (a) (in the target cell) sending one or more transmissions of the RA procedure to the communication equipment, and (b) (in the target cell) receiving one or more transmissions of the RA procedure from the communication equipment;

[0414] Determine the start time of S1155 TCI (details of which will be provided below); and

[0415] (In the target cell) Receive S1165 (a) first PUSCH transmission or (b) first PUCCH transmission from the communication equipment.

[0416] like Figure 11 As shown, the method may further include the step of determining the TCI state that the S1115 communication device will begin to use or complete when (a) the first PUSCH transmission or (b) the first PUCCH transmission.

[0417] like Figure 11 As further indicated in the text, if the source cell is operating on BS 860, the method may therefore include the following steps:

[0418] Generate S1125 cell handover signaling, which includes (a) a cell handover command indicating that a cell handover from the source cell to the target cell is to be performed, and (b) an indication of the TCI status; and / or

[0419] Send S1135 cell handover signaling to the communication equipment in the source cell.

[0420] As described above, if BS 860 operates the source cell, then BS 860 (i) can make a decision to perform a cell handover in S1105, and (ii) can make a decision in step S1115 to indicate which TCI state to indicate in the cell handover signaling. On the other hand, if BS 860 does not operate the source cell, then BS 860 (i) can determine the result of a cell handover decision made by another entity based on the obtained indication in S1105, and (ii) can determine the result of a decision to indicate which TCI state to indicate in the cell handover signaling based on the obtained indication in step S1115.

[0421] Note that this disclosure relates to two entities, the UE (typically a communication device / transceiver device) and the base station (typically a network node). Therefore, in the further description, details and embodiments apply to (and can be implemented by) each of the communication device, the base station (or scheduling node), and the corresponding methods / circuitets, unless explicitly stated or indicated by the context otherwise. Both the base station side and the UE side can determine the TCI start time in the same manner and obtain the TCI start time described herein. Furthermore, the base station can be configured to generate and transmit control signals as described below, and the communication device / UE can be configured to receive such signaling and obtain corresponding instructions from it. Specifically, any steps / operations described below can be performed or controlled by circuit 830 (on the UE side) and / or circuit 880 (on the base station side). Furthermore, any receive and transmit steps can be performed by transceiver 820 (on the UE side) and / or transceiver 870 (on the base station side) (e.g., by control of the corresponding circuitry).

[0422] TCI start time

[0423] Typically, the term "TCI start time" refers to a point in time from which the (multiple) TCI states indicated by cell handover signaling will be used by the communication equipment (and usually also by the base station for transmitting / receiving with said communication equipment). Specifically, the TCI start time is the common start time of the UL and DL TCI states. In other words:

[0424] If the TCI status indicator indicates a TCI status pair, then the TCI start time can refer to a point in time from which the UL and DL TCI states in the TCI status pair will be used for UL and DL transmissions, respectively.

[0425] If the TCI status indicator indicates a combined TCI status, then the TCI start time can refer to a point in time from which the indicated TCI status will be used for UL and DL transmissions.

[0426] Typically, the UE and BS apply the indicated beam in cell handover signaling to transmit or receive on the target candidate cell after the RA procedure is completed. For example, the first / earliest transmit or receive using the indicated beam could be the first PUSCH or the first PUCCH. The first / earliest transmit or receive using the indicated beam could also be (directly) a transmit or receive following the first PUSCH or the first PUCCH.

[0427] More specifically, the TCI start time can typically be the start or end (or completion) of the first PUSCH transmission or the first PUCCH transmission. More specifically, the TCI start time can be:

[0428] Situation / Solution A): Start of the first PUSCH transmission (the first PUSCH transmission is sent using the indicated TCI state).

[0429] Situation / Solution B): Start of the first PUCCH transmission (the first PUCCH transmission is sent using the indicated TCI state).

[0430] Situation / Solution C): End / Completion of the first PUSCH transmission (the first PUSCH transmission may not be sent using the indicated TCI status), or

[0431] Situation / Solution D): End / Completion of the first PUCCH transmission (the first PUCCH transmission may not be sent using the indicated TCI status).

[0432] When the UE / BS (e.g., circuit 835 / 885) determines the start time, the UE / BS can determine that the indicated TCI state will be used at the start or end of the start time. More specifically:

[0433] In scenario A) above, the UE / BS can determine that the indicated TCI state will be used starting from the first PUSCH transmission;

[0434] In scenario B) above, the UE / BS can determine that the indicated TCI state will be used starting from the first PUCCH transmission;

[0435] In scenario C) above, the UE / BS can determine that the indicated TCI state will be used from the time the first PUSCH transmission is completed (in other words, immediately after the first PUSCH transmission is completed); and

[0436] In case D above, the UE / BS can determine that the indicated TCI state is used from the time the first PUCCH transmission is completed (in other words, it starts immediately after the first PUCCH transmission is completed).

[0437] For example, in solution A), the indicated TCI state can be used starting from the slot of the first / earliest symbol of the first PUSCH. In solution B), the indicated TCI state can be used starting from the slot of the first / earliest symbol of the first PUSCH. In solution C), the indicated TCI state can be used starting from the first / earliest symbol of the first slot after the last symbol of the first PUSCH. In solution D), the indicated TCI state can be used starting from the first / earliest symbol of the first slot after the last symbol of the first PUSCH.

[0438] By applying one of the solutions A) to D) above, beam usage alignment can be achieved between the UE and BS without affecting the traditional UE-initiated beam selection during RA.

[0439] Typically, in order to implement one of the solutions A) to D) above in a standard specification (e.g., 3GPP), a channel can also be specified for the UE / BS to begin applying the indicated beam.

[0440] For example, the indicated beam / TCI state can be specified to begin at the start of the first PUSCH / PUCH channel transmission or at the completion of the first PUSCH / PUCH channel transmission. One of the solutions A) through D) above can also be implemented in the standard specification by a precise interpretation of the phrase "random access procedure complete." For example, "random access procedure complete" can be interpreted as beginning at the start of the first PUSCH / PUCCH transmission or at the completion of the first PUSCH / PUCCH transmission.

[0441] For example, solution A) can be implemented in the standard specification by defining the completion of a stochastic process for a RACH-based LTM as follows:

[0442] The 4-step CBRA procedure is completed when the UE successfully decodes the PDCCH of the UE's C-RNTI after Msg3 (which contains the UL authorization for the new transmission) / when the UE successfully decodes the PDCCH of the UE's C-RNTI after Msg3.

[0443] After the UE successfully receives the RAR message, or when the UE successfully receives the RAR message, the 4-step CFRA process is completed.

[0444] In the case of MSGA including C-RNTI, the 2-step CBRA / CFRA procedure is completed after / when the following conditions are met:

[0445] o The PDCCH and corresponding scheduling transport block addressed to the UE's C-RNTI are successfully decoded by the UE, or

[0446] The PDCCH addressing the UE's C-RNTI (which contains the UL authorization for the new transmission) was successfully decoded by the UE.

[0447] The difference between case A) and case C) is that the indicated TCI state is also used for the first PUSCH transmission. After the first PUSCH transmission (in cases A) and C), the indicated TCI state is used for any / every transmission (and reception (in the case of a combined TCI state)) until the BS determines a new TCI state and indicates it to the UE. In case C), the indicated TCI state will therefore be used for any / every transmission (and reception (if applicable)) after the first PUSCH transmission.

[0448] The difference between case C) and case D) is that the indicated TCI state is also used for the first PUCCH transmission. After the first PUCCH transmission (in cases B) and D), the indicated TCI state is used for any / every transmission (and reception (in the case of a combined TCI state)) until the BS determines a new TCI state and indicates it to the UE. In case C), the indicated TCI state will therefore be used for any / every transmission (and reception (if applicable)) after the first PUCCH transmission.

[0449] Note that the above process does not preclude the possibility that in some cases, transmissions prior to the TCI start time (e.g., transmissions in the RA process) may use the same TCI state as indicated. However, this can be considered a coincidence that occurs only in certain circumstances, as the TCI state used for the RA process is determined based on criteria such as the quality of a specific reference signal and not on the TCI state indication. Furthermore, even in such cases, the TCI start time of the indicated TCI state is still the TCI start time determined according to this disclosure, and not, for example, the start of the RACH process.

[0450] Note that the different solutions A) through D) can be combined, for example, by using different solutions for different types of RA procedures (4-step CBRA, 4-step CFRA, 2-step CBRA, and 2-step CFRA). In other words, the UE / base station can be configured to operate according to any of the 4-step CBRA embodiments described below when performing a 4-step CBRA, and according to any of the 2-step CBRA embodiments when performing a 2-step CBRA. Further details regarding solutions A) through D) are described below for different types of RA procedures.

[0451] Cell handover signaling

[0452] Typically, cell handover signaling is transmitted from the base station to the UE, including:

[0453] A cell handover command is an instruction (issued by the communication equipment receiving the command) to perform a cell handover from the source cell to the target cell.

[0454] Indication indicating the TCI status (i.e., the TCI status indication).

[0455] Typically, a cell handover command can be an indication of the target cell or an indication that includes the target cell. For example, it can be an index of the target configuration ID that indicates the candidate configuration index of the target cell. Note that cell handover signaling can also be, or referred to as, a “cell handover command” (e.g., in TS 38.321v18.0.0 6.1.3.75), and / or a TCI status indication can be included within the cell handover command.

[0456] The TCI status indicator can indicate:

[0457] TCI status (e.g., "joint TCI status" for UL and DL transmissions), or

[0458] UL TCI states to be used for UL transmission and DL TCI states to be used for DL ​​transmission (also referred to in this disclosure as "TCI state pairs").

[0459] The indication of TCI status can be considered as the indication of the beam, and the indication of TCI status can be considered as the indication of the beam pair (i.e., the UL beam and the DL beam).

[0460] Details of cell handover signaling and / or cell handover commands may be specified, for example, as in Section 6.1.3.75 of TS 38.321 v18.0.0. Note that, typically, cell handover signaling may also include a timing advance command for the target cell (if available).

[0461] First PUSCH / PUCCH transmission

[0462] The term "first PUSCH transmission" refers to the first / earliest PUSCH transmission among PUSCH transmissions that meets the following conditions (i.e., when arranged chronologically, the PUSCH transmission is "first").

[0463] UL authorized scheduling from addressing to the RNTI of the communication device; and

[0464] After completing the RA process.

[0465] Therefore, the first PUSCH transmission (i) is scheduled by the UL authorization of the RNTI addressing the communication device, and (ii) after the RA process is completed.

[0466] The term "first PUCCH transmission" refers to the first / earliest PUCCH transmission among PUCCH transmissions that meets the following conditions (i.e., when arranged in chronological order, the PUCCH transmissions are "first" in chronological order):

[0467] Carrying receipt confirmation; and

[0468] After completing the RA process.

[0469] Therefore, the first PUCCH transmission (i) acknowledges the receipt of the DL transmission, and (ii) after the RA process is completed.

[0470] 4-step CBRA

[0471] Typically (e.g., in the case of a 4-step CBRA), as part of the RA procedure, the UE can send (and the BS receives):

[0472] The first transmission (e.g., Msg1) includes a random access preamble (e.g., a sequence code / Zadoff-Chu sequence), and

[0473] The second RA transmission (e.g., Msg3) is scheduled by the target cell BS and includes an indication of the RNTI of the communication equipment (e.g., an indication of the cell RNTI (C-RNTI of the communication equipment)).

[0474] Note that the BS can schedule this second RA transmission using a transmission commonly referred to as a "random access response" (e.g., Msg2). The random access response is the transmission addressing the RA-RNTI to the UE. (See above for reference.) Figure 5a The details of this RA process are described.

[0475] Typically, in this RA procedure, the UE / BS (i) begins using the indicated TCI state from the first PUSCH or (ii) after the completion of the first PUSCH (i.e., from the first Tx / Rx following the first PUSCH). Therefore, the UE and BS begin applying the beam indicated in the cell handover signaling from the following:

[0476] The first PUSCH scheduled by the UL grant for the new transmission (i.e., the "new transmission" is not part of the RA procedure). This UL grant can be included in the PDCCH addressed to the C-RNTI, which is received by the UE after the UE's second RA transmission (Msg3). This PDCCH can be included in the "contention resolution step" (i.e., Msg4), i.e., in the last transmission of the BS in the RA procedure (corresponding to solution a)), or...

[0477] The first transmission or reception following this first PUSCH (corresponding to solution C) scheduled by the UL authorization for the new transmission.

[0478] It should be noted that if the first PDCCH includes a DL allocation, the UE may wait for a UL-authorized PDCCH for a new PUSCH transmission to complete the RA procedure. In other words, if the first PDCCH includes a DL allocation, the UE can use its current beam / TCI state (i.e., without applying the indicated TCI state) to perform reception of a DL transmission scheduled by the first PDCCH. Therefore, the UE waits for a UL-authorized PDCCH addressed to the C-RNTI and switches to the indicated TCI state at the start or completion of a PUSCH scheduled by the UL authorization. However, this disclosure is not limited to this. Typically, the UE may also determine that the indicated TCI state is applied from the start (or completion) of the first transmission scheduled by either: (i) a PDCCH containing a DL allocation, or (ii) a PDCCH containing a UL authorization, whichever is received first.

[0479] Typically, the UE and BS can continue using the indicated beam until a new beam is indicated. References will now be made. Figure 12a and Figure 12b The details of determining the TCI start time in the case of 4-step CBRA (in steps S1140 and S1155 respectively) are described, corresponding to solutions A and C respectively.

[0480] like Figure 12b and Figure 12b As shown, after the second transmission in the RA process (step 3 "Scheduled Transmission" in the figure), the UE can receive DL control signaling from the BS. Figure 12b and Figure 12b As further shown, the DL control signaling includes:

[0481] Includes a new UL authorization for the UE (this transmission is referred to herein as the first PUCCH);

[0482] The C-RNTI addressed to the UE;

[0483] It is received after the second UE transmission in the RA process (e.g., after Msg3); and

[0484] It can be included in PDCCH.

[0485] like Figure 12a As shown, the UE / BS (e.g., circuit 835 / 885) can then determine that the TCI start time is the start of the first PUSCH transmission scheduled by the DL control signaling. In other words, the indicated TCI state will be used from the start of the first PUSCH transmission. Therefore, the UE / BS will use the indicated beam for the first PUSCH transmission (in Figure 12a The term "PUSCH" is used for subsequent transmissions (until another beam switch is performed).

[0486] Once the first PDCCH, which addresses the UE's C-RNTI and contains the UL authorization for the new transmission, is successfully decoded by the UE, the UE can assume that random access is complete / successful. Therefore, in the case of 4-step CBRA, applying the indicated beam from the start of the PUSCH transmission scheduled by the first PDCCH can provide the earliest possibility of applying the indicated beam after completion.

[0487] However, when the BS grants authorization, it may need to account for beam handover delay between PDCCH scheduling permission and PUSCH transmission. If the UE misses the PDCCH, it will continue to use the old beam. However, the BS can apply (i.e., as indicated in the cell handover signaling) a new beam to schedule PUSCH retransmission. In this case, misalignment may occur for a period of time. After the timer (e.g., ra-ContentionResolutionTimer) expires, the misalignment will be resolved, and the UE can then restart Msg1.

[0488] like Figure 12b As shown, in other embodiments, the UE / BS (e.g., circuit 835 / 885) determines the TCI start time as the start of the completion of the first PUSCH transmission. In other words, the indicated TCI state will be used from the start of the completion of the first PUSCH transmission. Therefore, the UE / BS does not use the indicated beam for the first PUSCH transmission, but instead uses the indicated beam for subsequent (e.g., all / each) transmit / receive (until another beam switch is performed).

[0489] Applying the indicated beam early upon completion of the first PUSCH transmission avoids beam switching between UL authorization and the corresponding PUSCH (some UEs may not be able to handle such rapid beam switching). In this case, if the BS misses the PUSCH, the BS will not apply the indicated beam. However, the UE will apply the indicated beam after transmitting the PUSCH. In this situation, misalignment may occur. To address this issue, in some embodiments, the BS determines which indicated beam to use:

[0490] From the completion of the first PUSCH transmission, and

[0491] Send (multiple) PDCCHs for (re)scheduling the retransmission of the first PUSCH.

[0492] In other words, the BS can determine that the indicated beam will be used from the time the scheduling of the first PUSCH transmission is completed (i.e., the time when the scheduling is completed is the point in time when the first PUSCH transmission should be completed according to the DL control signaling / UL authorization that scheduled the first PUSCH transmission).

[0493] 4-step CFRA

[0494] Typically (e.g., in the case of a 4-step CFRA), as part of the RA process (see also...) Figure 5b , Figure 13a and Figure 13b ):

[0495] The UE can transmit (and the BS receives) a first RA transmission (e.g., Msg1) including a random access preamble (e.g., a sequence code / Zadoff-Chu sequence), and

[0496] The BS can send (and the UE receives) a second RA transmission, typically referred to as a "Random Access Response (RAR)" (e.g., Msg2). This RAR includes (i) a random access response addressing the UE's RA-RNTI, and (ii) a UL grant for the first PUSCH transmission. This second RA transmission is sent / received after the aforementioned first RA transmission.

[0497] Note that when a RAR is received in the case of CFRA and it is confirmed that the RAR corresponds to the random access preamble sent by the UE in Msg1, the UE can assume that the RA procedure is complete (since there are no other UEs that have completed the procedure, it is not necessary to assume that the RA procedure is complete). Figure 5a Steps 3 and 4 in the above (as already referenced). Figure 5bThe details of this RA process are described.

[0498] Typically, in this RA procedure, the UE / BS (i) begins using the indicated TCI state from the first PUSCH or (ii) upon completion of the first PUSCH (i.e., from the first Tx / Rx after the first PUSCH). Therefore, the UE and BS begin applying the beam indicated in the cell handover signaling from the following:

[0499] The PUSCH scheduled by the UL authorization included in the random access response (corresponding to Solution A), or

[0500] The first transmission or reception following such a PUSCH scheduled by the UL authorization included in the random access response (corresponding to solution C).

[0501] Typically, the UE and BS can continue using the indicated beam until a new beam is indicated. References will now be made. Figure 13a and Figure 13b The details of determining the TCI start time in the case of 4-step CFRA (in steps S1140 and S1155 respectively) are described, corresponding to solutions A and C respectively.

[0502] like Figure 13a and Figure 13b As shown, after the first transmission of the RA procedure (step 1 "Random Access Preamble" in the figure), the UE receives the RAR from the BS. The RAR includes the UL authorization for the (first) PUSCH transmission to the UE after the completion of the RA procedure.

[0503] like Figure 13a As shown, the UE / BS (e.g., circuit 835 / 885) can then determine that the TCI start time is the start of the first PUSCH transmission scheduled by the UL authorization in the RAR. In other words, the indicated TCI state will be used from the start of the first PUSCH transmission. Therefore, the UE / BS will use the indicated beam for the first PUSCH transmission (in Figure 13a The term "PUSCH" is used for subsequent transmissions (until another beam switch is performed).

[0504] For a 4-step CFRA, once the UE successfully receives the RAR, the UE can assume that random access is complete / successful. Therefore, in the case of a 4-step CFRA, applying the indicated beam starting from the first PUSCH transmission scheduled using the RAR can provide the earliest possibility of applying the indicated beam after completion.

[0505] However, when the BS provides authorization, it may be necessary to account for beam handover delay between the scheduling authorization in the RAR and the PUSCH transmission. If the UE misses the RAR, the UE will continue to use the old beam. However, the BS will apply (i.e., as indicated in the cell handover command) the new beam to schedule the PUSCH retransmission. In this case, misalignment may occur for a period of time. After the timer (e.g., ra-ReactionWindow) expires, the misalignment will be resolved, and the UE can restart Msg1.

[0506] like Figure 13b As shown, in other embodiments, the UE / BS (e.g., circuit 835 / 885) determines the TCI start time as the start of the completion of the first PUSCH transmission. In other words, the indicated TCI state will be used from the time the first PUSCH transmission is completed. Therefore, the UE / BS does not use the indicated beam for the first PUSCH transmission, but instead uses the indicated beam for subsequent (e.g., all / each) transmit / receive (until another beam switch is performed).

[0507] Applying the indicated beam early, starting when the first PUSCH transmission is complete, avoids beam switching between UL authorization and the corresponding PUSCH (some UEs may not be able to handle such rapid beam switching). If the BS misses a PUSCH, it will not apply the indicated beam. However, the UE will apply the indicated beam after transmitting the PUSCH. In this case, misalignment may occur. To address this issue, in some embodiments, the BS determines which indicated beam to use:

[0508] Starting from the completion of the first PUSCH transmission, and

[0509] Send (multiple) PDCCHs for (re)scheduling the retransmission of the first PUSCH.

[0510] In other words, the BS can determine that the indicated beam will be used from the time the scheduling of the first PUSCH transmission is completed (i.e., the time when the scheduling is completed is the point in time when the first PUSCH transmission should be completed according to the DL control signaling / UL authorization that scheduled the first PUSCH transmission).

[0511] CBRA / CFRA with C-RNTI in MsgA (2-step type)

[0512] Typically (e.g., in the case of a 2-step (type) CFRA or a 2-step (type) CBRA), as part of the RA procedure, the UE may send (and the BS may receive) a first RA transmission (e.g., MsgA), which includes (see...) Figure 5c and Figure 5d ):

[0513] Random access preamble (e.g., sequence code / Zadoff-Chu sequence), and

[0514] The UE's C-RNTI indication.

[0515] The above has been referenced Figure 5c and Figure 5d The details of this RA process are described.

[0516] Typically, according to solutions A) through D) above, when C-RNTI is included in MsgA (e.g., included in the first and only transmission of the RA procedure performed by the UE), the UE can receive DL control signaling (e.g., PDCCH) from the BS, the DL control signaling being:

[0517] Addressing to the UE's C-RNTI, and

[0518] Schedule DL or UL transmissions.

[0519] Note that this DL signaling may be the first transmission received by the UE from the BS after the aforementioned first (and possibly only) transmission during its RA transmission process.

[0520] Typically, after MsgA, the first PDCCH received by the UE can be a PDCCH for scheduling the following: 1) DL, 2) UL for a new transmission, or 3) UL for a retransmission of MsgA. In cases 1) or 2), the RA process can be considered complete. However, in case 3), the UE needs to wait for either 1) or 2). Therefore, in case 1), the UE can apply one of solutions B) and D); in case 2), the UE can apply one of solutions A) and C); and in case 3), the UE can use its current TCI state to retransmit MsgA (PUSCH payload) and wait to receive a PDCCH for a retransmission that does not schedule MsgA. If such a PDCCH is received, it includes either a DL allocation or a UL grant. If such a PDCCH includes a DL allocation, the UE applies solution B) or D), and if such a PDCCH includes a UL grant, the UE applies solution A) or C).

[0521] Following the random access preamble sent by the UE, DL control signaling is transmitted. The UE / BS (e.g., circuit 835 / 885) can then determine (e.g., in S1140 and S1155 respectively) that the first transmission to apply the indicated TCI state is:

[0522] First PUSCH transmission (corresponding to solution A)

[0523] First PUCCH transmission (corresponding to Solution B)

[0524] The first Tx / Rx after the first PUSCH transmission (corresponding to solution C) or

[0525] The first Tx / Rx after the first PUCCH (corresponding to solution D)).

[0526] More specifically (regarding C) and D), if the next / first transmission after the first PUCCH / PUSCH is a UL transmission sent by the UE, then the UL transmission is the first transmission of the TCI state indicated by the application; if the next / first transmission after the first PUCCH / PUSCH is a DL transmission received by the UE, then the DL transmission is the first transmission of the TCI state indicated by the application (if the TCI state indicates a pair of TCI states, then the DL TCI state is applied).

[0527] Typically, especially for 2-step CBRA and 2-step CFRA, any of the PUSCH-based options A) and C) can be combined with any of the PUCCH solutions B) and D). For example:

[0528] If the next PDCCH after MsgA schedules a UL transmission, then solution A) or solution C) can be applied.

[0529] If the next PDCCH after MsgA schedules a DL transmission, then solution B) or solution D can be applied.

[0530] In other words, whether the first PUCCH or the first PUSCH is related to determining the TCI start time can depend on whether the next DL signaling is a scheduled UL transmission or a DL transmission.

[0531] The following describes the details of solutions A) to D) in the case of 2-step CBRA / CFRA when MsgA includes C-RNTI.

[0532] CBRA / CFRA with two-step type of C-RNTI in MsgA and PDCCH indicating DL transmission

[0533] As described above, for example, in the case of a 2-step CBRA / CFRA, when the UE's first (and possibly only) RA transmission (MsgA) includes a C-RNTI, the UE can receive (and the BS can send) DL control signaling (e.g., PDCCH) after the MsgA. This DL control signaling is:

[0534] Addressing to the UE's C-RNTI, and

[0535] Schedule DL transmission.

[0536] DL transmissions can carry TA information (e.g., Absolute Timing Advance Command MAC CE). The UE can then receive DL transmissions (e.g., PDSCH) scheduled by DL control signaling. Note that this should be interpreted as the PDCCH and PDSCH being included in... Figure 5c and Figure 5d In step B shown. In other words, the scheduled DL transfer and / or DL ​​transfer may or may not be part of the RA process.

[0537] Then, in response to the reception of the DL transmission, the UE sends a transmission acknowledging the reception of the DL transmission. In other words, the UE's first PUCCH transmission can carry an acknowledgment of the DL transmission reception. Then, the UE and BS can begin applying the beam indicated in the cell handover signaling as follows:

[0538] The first PUCCH (corresponding to Solution B) carries a receive acknowledgment (e.g., HARQ-ACK) in response to a DL transmission scheduled by the PDCCH, or

[0539] The first transmission or reception following the first PUCCH in response to the DL transmission (corresponding to solution D).

[0540] Typically, the UE and BS can continue using the indicated beam until a new beam is indicated. References will now be made. Figure 14a , Figure 14b , Figure 15a and Figure 15b The details of determining the TCI start time based on PUCCH transmission in the case of 2-step CBRA / CFRA are described (in steps S1140 and S1155 respectively). More specifically, Figure 14a and Figure 14bThe determination of the TCI start time as the start of the first PUCCH transmission for CBRA and CFRA is shown separately. Figure 15a and Figure 15b The TCI start time is shown as the determination of the first PUCCH transmission (completion / end) of CBRA and CFRA, respectively.

[0541] like Figure 14a and Figure 14b As shown (all corresponding to Solution B), the first transmission of the RA procedure of the UE (e.g., MsgA) may include a random access preamble and a PUSCH payload. Figure 14a and Figure 14b Step A in the process. After this transmission, the UE may receive (i) downlink control (DL) signaling that schedules the DL transmission (e.g., as shown in step A). Figure 14a and Figure 14b The “PDCCH” shown, and (ii) the scheduled transmission ( Figure 14a and Figure 14b (The "corresponding DL data" in the text). Note that, compared to... Figure 14a and Figure 14b Conversely, as illustrated in the diagram, DL signaling and the corresponding DL transport can be different / separate transports. This is in response to a scheduled transport being received.

[0542] Then, the UE sends a transmission carrying a receive / receive acknowledgment to the BS using the indicated TCI state / beam. More specifically, the receive acknowledgment confirms to the BS that the UE has received the transmission via DL signaling (e.g., as...). Figure 14a and Figure 14b The DL transmission is scheduled by the PUSCH carrying HARQ-ACK. Since the DL signaling can be the first transmission received by the UE from the BS after the first transmission of its RA procedure, this transmission of the UE is usually the first (i.e., the earliest) PUCCH transmission after the RA procedure.

[0543] Therefore, the TCI start time is the first PUCCH transmission. In other words, the UE / BS determines that the TCI state indicated in the cell handover signaling will be applied starting from the first PUCCH transmission.

[0544] After the UE successfully decodes the PDCCH and the scheduled transport block, the UE can assume that RA is complete / successful. Applying the indicated beam starting from the first PUCCH carrying HARQ-ACK can be the earliest possible time after the RA process is complete. However, UE beam switching may occur between receiving the PDCCH / PDSCH and sending the PUCCH. If the UE misses a PDCCH or PDSCH, it will still use the old beam. However, the BS can apply the indicated beam to reschedule the PDSCH. This misalignment can be resolved once a timer (such as msgB-ResponseWindow) expires.

[0545] like Figure 15a and Figure 15b As shown (all corresponding to Solution D), the first transmission of the UE's RA procedure (e.g., MsgA) may include a random access preamble and a PUSCH payload (as shown). Figure 15a and Figure 15b Step A in the process). After this transmission, the UE may receive (i) DL signaling that schedules the DL transmission (e.g., such as...). Figure 15a and Figure 15b The “PDCCH” shown, and (ii) the scheduled transmission ( Figure 15a and Figure 15b (The "corresponding DL data" in the text). Note that, compared to... Figure 15a In contrast to the diagram, DL signaling and the corresponding DL transmission can be different / separate transmissions.

[0546] In response to receiving the scheduled transmission, the UE then sends a transmission carrying a receive / receive acknowledgment to the BS. More specifically, the receive acknowledgment confirms to the BS that the UE has received the DL transmission scheduled by the DL signaling (e.g., such as...). Figure 15a and Figure 15b The PUSCH carrying HARQ-ACK in the transmission. The UE does not apply the indicated beam to this transmission (but uses, for example, the current beam / the beam used for the RA procedure / the beam used during the RA procedure). Since DL signaling can be the first transmission received by the UE from the BS after it sends the first transmission of the RA procedure, this transmission of the UE is usually the first (i.e., the earliest) PUCCH transmission after the RA procedure.

[0547] The UE applies the indicated beam immediately after the ACK transmission is completed. In other words, the TCI start time is therefore the completion of the first PUCCH transmission. In other words, the UE / BS determines that the TCI state indicated in the cell handover signaling will begin to apply upon the completion of the first PUCCH transmission.

[0548] The application of the indicated beam begins as soon as the first PUCCH transmission carrying HARQ-ACK is completed. This early application of the indicated beam avoids beam switching between DL data reception and the corresponding HARQ-ACK transmission (some UEs may not be able to handle such rapid beam switching). The PUCCH with HARQ-ACK serves as an acknowledgment of the application of the indicated beam. Since the chance of missing a HARQ-ACK is very low, if the BS does not receive it, the BS can assume that the UE missed a previous PDCCH / PDSCH. The BS will then not switch to the indicated beam. Therefore, beam misalignment during MsgB retry can be avoided.

[0549] CBRA / CFRA with two-step type, featuring C-RNTI in Msg A and PDCCH indicating UL transmission.

[0550] As described above, for example, in the case of a 2-step CBRA / CFRA, when the UE's first (and possibly only) RA transmission (MsgA) includes a C-RNTI, the UE can receive (and the BS can send) DL control signaling (e.g., PDCCH) after the MsgA. This DL control signaling is:

[0551] Addressing to the UE's C-RNTI, and

[0552] Schedule new UL transmissions (i.e., UL authorization).

[0553] Note that this should be interpreted as the PDCCH being included. Figure 5c and Figure 5d In step B shown. In other words, the transmission scheduled for UL transmission may or may not be part of the RA process.

[0554] Then, the UE can begin applying the beam indicated in the cell handover signaling from the following:

[0555] The (first) PUSCH (corresponding to Solution A) scheduled by UL authorization, or

[0556] The first transmission or reception following this (first) PUSCH scheduled by UL authorization (corresponding to solution C).

[0557] Typically, the UE and BS can continue using the indicated beam until a new beam is indicated. References will now be made. Figure 16a , Figure 16b , Figure 17a and Figure 17bThe details of determining the TCI start time in the case of a two-step CBRA / CFRA based on PUSCH transmission are described (in steps S1140 and S1155 respectively). More specifically, Figure 16a and Figure 16b The determination of the TCI start time as the start of the first PUSCH transmission for CBRA and CFRA is shown separately. Figure 17a and Figure 17b The TCI start time is shown as the determination of the first PUSCH transmission (completion / end) of CBRA and CFRA, respectively.

[0558] like Figure 16a and Figure 16b As shown (all corresponding to solution a)), the first transmission of the UE's RA procedure (e.g., MsgA) may include a random access preamble and a PUSCH payload (as shown). Figure 16a and Figure 16b Step A in the process. After this transmission, the UE may receive scheduling of new UL transmissions and / or DL ​​signaling including UL authorization (e.g., as shown in step A). Figure 16a and Figure 16b (as shown in the diagram "PDCCH"). This DL signaling can be the first transmission received by the UE from the BS after the first transmission during its RA procedure. Specifically, the DL signaling schedules the first PUSCH transmission.

[0559] Then, the UE transmits the first PUSCH transmission using the indicated TCI state / beam. Therefore, the TCI start time is the first PUSCH transmission. In other words, the UE / BS determines that the TCI state indicated in the cell handover signaling will be applied starting from the first PUSCH transmission.

[0560] After the UE successfully decodes the PDCCH containing the UL authorization for the new transmission, the RA procedure can be assumed to have been completed (successfully). Applying the indicated beam starting from the first PUSCH can be the earliest possible time after the RA procedure is completed. However, a UE beam switching may occur between receiving the PDCCH and transmitting the PUSCH. If the UE misses the PDCCH, it will still use the old beam. However, the BS can apply the indicated beam to reschedule the PUSCH. This misalignment can be resolved once a timer (such as msgB-ResponseWindow) expires.

[0561] like Figure 17a and Figure 17b As shown (all corresponding to Solution C), the first transmission of the UE's RA procedure (e.g., MsgA) may include a random access preamble and a PUSCH payload. Figure 17a and Figure 17bStep A in the process. After this transmission, the UE may receive scheduling UL transmissions and / or DL ​​signaling including UL authorization (e.g., as shown in step A). Figure 17a and Figure 17b (See “PDCCH”). This DL signaling can be the first transmission received by the UE from the BS after the first transmission of its RA procedure. Specifically, the DL signaling schedules the first PUSCH transmission.

[0562] Then, the UE transmits the first PUSCH transmission. The UE does not apply the indicated beam to this transmission (but uses, for example, the current beam / the beam used for the RA procedure / the beam used during the RA procedure).

[0563] The UE applies the indicated beam immediately after the PUSCH transmission is completed. In other words, the TCI start time is the completion of the first PUSCH transmission. In other words, the UE / BS determines that the TCI state indicated in the cell handover signaling will begin to be applied upon the completion of the first PUSCH transmission.

[0564] Applying the indicated beam early, starting from the completion of the first PUSCH, avoids beam switching between UL authorization and PUSCH (some UEs may not be able to handle such rapid beam switching). If the BS misses the PUSCH, the BS will not apply the indicated beam. However, RA is completed from the UE side. Therefore, the UE will apply the indicated beam after sending the PUSCH. In this case, misalignment may occur. To address this issue, in some embodiments, the BS determines which indicated beam to use:

[0565] From the completion of the first PUSCH transmission, and

[0566] Send (multiple) PDCCHs for (re)scheduling the retransmission of the first PUSCH.

[0567] In other words, the BS can determine that the indicated beam will be used from the start of the scheduling completion of the first PUSCH transmission (i.e., the scheduling completion refers to the time point at which the first PUSCH transmission should be completed according to the DL control signaling / UL authorization that schedules the first PUSCH transmission).

[0568] MSGA-No C-RNTI

[0569] Typically, in the case of a 2-step CBRA, when the C-RNTI is not included in the first UE transmission (e.g., MsgA) of the RA procedure:

[0570] A 2-step CBRA can be reverted to a 4-step CBRA. In this case, the solution described above for a 4-step CBRA can be applied / used.

[0571] A 2-step CFRA can revert to a 4-step CFRA. In this case, the solution described above for a 4-step CBFA can be applied / used.

[0572] More specifically, as described above, when MsgA does not include C-RNTI, the BS's RAR will be addressed to MsgB-RNTI, and within the RAR (which is a fallback RAR), the UE will obtain UL authorization, as in the corresponding 4-step case. Therefore, the UE can monitor the PDCCH addressed to MsgB-RNTI (in... Figure 5c and Figure 5d In step B), and / or the UE may receive a fallback RAR as MsgB to instruct the UE to fall back to the corresponding 4-step RA procedure.

[0573] Combination of solutions

[0574] A processing time, referred to herein as "Tproc," can be defined for beam switching. Tproc can be defined differently for beam switching between grant and PUSCH, and between DL PDSCH reception and the corresponding HARQ-ACK transmission. Tproc is predetermined and can be (pre)defined in a standard, or it can depend on UE capabilities (i.e., it can be determined based on, for example, the capabilities of the corresponding UE in the source cell). Tproc specifies or corresponds to a predetermined time period / duration, i.e., the length of time. Tproc can, for example, be a value specifying the duration in milliseconds, number of symbols, or number of time slots. Essentially, Tproc is an estimate of the time required for the UE to perform the switching of the TCI(s) state(s) used.

[0575] In the event of a cell handover where the source cell is operated by a different BS than the target cell, the BS of the source cell can notify the BS of the target cell of the Tproc value of the UE undergoing the cell handover.

[0576] Using processing time Tproc, solution A) can be combined with solution C) as follows:

[0577] If the time interval (length) between (i) the UL grant (reception) of the first PUSCH and (ii) the transmission of the first PUSCH is shorter than or equal to Tproc, the UE will not apply the indicated TCI state / beam to the transmission of the first PUSCH (i.e., Solution C applies). In other words, if the indicated TCI state is different from the TCI state / beam used by the UE for MSG1 or MSGA, the indicated beam will be applied to the next channel / signal that follows in time.

[0578] If the time interval is longer than Tproc, the UE applies the indicated TCI state / beam to the transmission of the first PUSCH (i.e., Solution A applies).

[0579] The length of the time interval between the UL grant for scheduling the first PUSCH and the first PUSCH can be measured, for example, from the last symbol of the UL grant to the first slot of the first PUSCH. It should also be noted that if Tproc equals the time interval, then in some embodiments, solution A) is applied instead of solution C).

[0580] Using the processing time Tproc, solution B) can be combined with solution D) as follows:

[0581] If the time interval (length) between the DL reception mentioned in (i) and the corresponding HARQ-ACK transmission is shorter than or equal to Tproc, then the UE will not apply the indicated TCI state / beam to the transmission of the first PUCCH carrying the HARQ-ACK transmission (i.e., Solution D applies). In other words, if the indicated TCI state / beam is different from the TCI state / beam used by the UE for MSG1 or MSGA, then the indicated TCI state / beam will be applied to the next channel / signal that follows in time.

[0582] If the time interval is longer than Tproc, the UE applies the indicated TCI state / beam to the transmission of the first PUCCH carrying the HARQ-ACK transmission (i.e., Solution B applies).

[0583] The length of the time interval between the UL grant for scheduling the first PUSCH and the first PUSCH can be measured, for example, from the last symbol of the UL grant to the first slot of the first PUSCH. It should also be noted that if Tproc equals the time interval, then in some embodiments, solution A) is applied instead of solution C).

[0584] Other variations and / or details of the hardware and software implementations of this disclosure.

[0585] Variations and / or details of this disclosure are described below.

[0586] control signals

[0587] In this disclosure, the downlink control signals (information) related to this disclosure can be signals (information) transmitted through the physical layer PDCCH, or signals (information) transmitted through a higher-layer MAC control element (CE) or RRC. Downlink control signals can be predefined signals (information).

[0588] The uplink control signals (information) related to this disclosure may be signals (information) transmitted via the physical layer PUCCH, or signals (information) transmitted via a higher-layer MAC CE or RRC. Furthermore, the uplink control signals may be predefined signals (information). Uplink control signals may be replaced by uplink control information (UCI), phase one sidelink control information (SCI), or phase two SCI.

[0589] the term

[0590] The following describes the UE, base station, and corresponding processes for meeting these requirements with respect to new radio access technologies envisioned for 5G mobile communication systems; however, these technologies can also be used in previous LTE-based mobile communication systems or future (e.g., 6G) mobile communication systems. Different implementation methods and variations will also be explained. The following disclosure is facilitated by the discussion and findings described above and may be based, for example, at least in part.

[0591] Generally, it should be noted that many assumptions have been made herein in order to explain the basic principles of this disclosure in a clear, concise, and understandable manner. However, these assumptions are to be understood merely as examples made herein for illustrative purposes, and these examples are not necessarily necessary for the invention and therefore should not limit the scope of this disclosure. Those skilled in the art will recognize that the principles disclosed below, as well as those set forth in the claims, can be applied to different scenarios and in ways not explicitly described herein.

[0592] Furthermore, some terms used below, such as processes, entities, and layers, are closely related to those used in LTE / LTE-A systems or current 3GPP 5G standards, even though specific terms used in the context of new radio access technologies for next-generation communication systems have not been fully determined or may ultimately change. Therefore, terminology may be changed in the future without affecting the functionality of the corresponding features and technical solutions. Thus, those skilled in the art will recognize that the technical solutions and their scope of protection should not be limited to the specific terms exemplarily used herein due to the lack of updated or ultimately agreed-upon terminology, but should be understood more broadly in terms of the functions and concepts that form the basis of the technical solutions explained in this disclosure. Specifically:

[0593] User equipment

[0594] In LTE and NR, a terminal, user terminal, user equipment, mobile station, mobile node, or mobile device is referred to as a User Equipment (UE). This can be a mobile device or communication device / equipment, such as a wireless phone, smartphone, tablet computer, or USB (Universal Serial Bus) stick with UE functionality. However, the term mobile device is not limited to this; typically, a repeater can also have the functionality of such a mobile device, and a mobile device can also be used as a repeater. For example, a terminal is a physical entity (physical node) within a communication network. Furthermore, a communication device can be any type of machine communication device, such as an IoT device. A node can have several functional entities. A functional entity refers to a software or hardware module that implements and / or provides a predetermined set of functions to the same or another node or other functional entities in the network. A node can have one or more interfaces that allow the node to be attached to a communication facility or medium through which it can communicate. Similarly, a network entity can have a logical interface that allows functional entities to be attached to a communication facility or medium, through which it can communicate with other functional entities or communication nodes. Therefore, unless the context otherwise indicates, the terms “(user) terminal”, “user equipment”, “user equipment (UE)”, “mobile station / node / device”, “enB”, etc. are used interchangeably.

[0595] base station

[0596] In this disclosure, a base station can be, for example, a Transmitter Receiver Point (TRP), cluster head, access point, Remote Radio Header (RRH), eNodeB (eNB), gNodeB (gNB), base station (BS), base transceiver unit (BTS), base station unit, or gateway. Furthermore, in sidelink communication, a terminal can be used instead of a base station. A base station can be a relay device for communication between a higher relay node and a terminal. A base station can also be a roadside unit.

[0597] A base station can be a scheduling node or a network node, for example, forming part of a network used to provide services to terminals. Specifically, a base station can provide radio access to terminals. Communication between communication equipment (e.g., a UE or terminal) and scheduling equipment (e.g., a base station) is typically standardized and can be defined by different layers such as PHY, MAC, RRC, etc. (see also the discussion above). In LTE and NR, the radio interface protocol stack includes the physical layer, the media access layer (MAC), and higher layers. In the control plane, a higher-layer protocol, the Radio Resource Control Protocol, is provided. Via RRC, the base station can control the configuration of the terminal, and the terminal can communicate with the base station to perform control tasks such as connection and bearer establishment, modification, measurement, and other functions. The term used in LTE is eNB (or eNodeB), while the term currently used for 5G NR is gNB. The term "base station" or "radio base station" here refers to a physical entity within a communication network. Like a mobile station, a base station can have several functional entities. A functional entity is a software or hardware module that implements and / or provides a predetermined set of functions to other functional entities in the same or another node or network. Physical entities perform control tasks related to communication equipment, including one or more of scheduling and configuration. Note that base station functions and communication equipment functions can also be integrated within a single device. For example, a mobile terminal can also implement base station functions for other terminals. The term used in LTE is eNB (or eNodeB), while the current term used for 5G NR is gNB. Specifically, a base station can also be a gNB in ​​a non-terrestrial network (NTN) NR system. Therefore, unless the context otherwise indicates, the terms "base station," "scheduling node," "network node," "gnB," "enB," "scheduling equipment," etc., are used interchangeably.

[0598] Uplink / Downlink / Sidelink

[0599] This disclosure can be applied to any of the uplink, downlink, and sidelink.

[0600] This disclosure can be applied to, for example, uplink channels (such as PUSCH, PUCCH and PRACH), downlink channels (such as PDSCH, PDCCH and PBCH), and sidelink channels (such as Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH) and Physical Sidelink Broadcast Channel (PSBCH)).

[0601] PDCCH, PDSCH, PUSCH, and PUCCH are examples of downlink control channel, downlink data channel, uplink data channel, and uplink control channel, respectively. PSCCH and PSSCH are examples of sidelink control channel and sidelink data channel, respectively. PBCH and PSBCH are examples of broadcast channels, and PRACH is an example of a random access channel.

[0602] Data channel / control channel

[0603] This disclosure can be applied to any data channel and control channel. The channels in this disclosure can be replaced with data channels including PDSCH, PUSCH, and PSSCH, and / or control channels including PDCCH, PUCCH, PBCH, PSCCH, and PSBCH.

[0604] Reference signal

[0605] In this disclosure, the reference signal is a signal known to both the base station and the mobile station, and each reference signal may be referred to as a reference signal (RS) or sometimes as a pilot signal. The reference signal may be any one of DMRS, Channel State Information Reference Signal (CSI-RS), Tracking Reference Signal (TRS), Phase Tracking Reference Signal (PTRS), Cell Specific Reference Signal (CRS), and Sounding Reference Signal (SRS).

[0606] Time interval

[0607] In this disclosure, the time resource unit is not limited to one or a combination of time slots and symbols, and can be a time resource unit such as a frame, superframe, subframe, time slot, time slot sub-time slot, micro-time slot, or a time resource unit such as a symbol, orthogonal frequency division multiplexing (OFDM) symbol, single-carrier frequency division multiple access (SC-FDMA) symbol, or other time resource units. The number of symbols contained in a time slot is not limited to the number of symbols exemplified in the above embodiments, and can also be other numbers of symbols.

[0608] Parameter set (Numerology)

[0609] Typically (as in new radio systems like 5G-NR), for each parameter set and carrier, resource grids for subcarriers and OFDM symbols can be defined separately for the uplink and downlink. Each element in the resource grid is called a resource element (RE) and is identified based on its frequency index in the frequency domain and its symbol position in the time domain (see, for example, 3GPP TS 38.211 v15.6.0 or, for example, v16.2.0, Section 4). In other words, the term "resource element" can be used to represent the smallest resource unit consisting of one subcarrier for the length of an OFDM / SC-FDMA symbol.

[0610] For example, downlink and uplink transmissions can be organized into frames with a duration of 10 ms, each frame consisting of ten subframes, each with a duration of 1 ms. In a 5g NR implementation, the number of consecutive OFDM symbols in each subframe depends on the subcarrier spacing configuration. For example, for a 15 kHz subcarrier spacing, the subframe has 14 OFDM symbols (similar to an LTE-compliant implementation, assuming a normal cyclic prefix). On the other hand, for a 30 kHz subcarrier spacing, the subframe has two slots, each containing 14 OFDM symbols.

[0611] Compared to the LTE parameter set (subcarrier spacing and symbol length), NR supports several different types of subcarrier spacing marked by the parameter μ (in LTE, only a 15 kHz subcarrier spacing exists, corresponding to μ=0 in NR). The types of NR parameter sets are outlined in 3GPP TS38.211, v 15.7.0.

[0612] A set of OFDM parameters suitable for one use case (e.g., subcarrier spacing, OFDM symbol duration, cyclic prefix (CP) duration, number of symbols per scheduling interval) may not be suitable for another use case. For example, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, etc., could be considered.

[0613] frequency band

[0614] This disclosure can be applied to either licensed or unlicensed frequency bands.

[0615] communication

[0616] This disclosure can be applied to communication between base stations and terminals (Uu link communication), communication between terminals (side link communication), and vehicle-to-everything (V2X) communication. The channels in this disclosure can be replaced by PSCCH, PSSCH, Physical Side Link Feedback Channel (PSFCH), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, and PBCH.

[0617] Furthermore, this disclosure can be applied to any terrestrial network or other networks (NTN: non-terrestrial networks) that use satellites or high-altitude pseudo-satellites (HAPS). Additionally, this disclosure can be applied to networks with large cell sizes, and to terrestrial networks with significant delays compared to symbol lengths or time slot lengths, such as ultra-wideband transmission networks.

[0618] Antenna port

[0619] An antenna port refers to a logical antenna (antenna group) consisting of one or more physical antennas. That is, an antenna port does not necessarily refer to a single physical antenna, and sometimes it refers to an array antenna consisting of multiple antennas. For example, there is no definition of how many physical antennas constitute an antenna port; instead, an antenna port is defined as the smallest unit through which a terminal is allowed to transmit a reference signal. An antenna port can also be defined as the smallest multiplication unit used for precoding vector weighting.

[0620] Hardware and software implementations of this disclosure

[0621] This disclosure can be implemented through software, hardware, or a combination of software and hardware. Each functional block used in each of the above embodiments can be implemented partially or entirely by an LSI, such as an integrated circuit, and each process described in each embodiment can be partially or completely controlled by the same LSI or a combination of LSIs. An LSI can be formed as a single chip, or a chip can be formed to include some or all of the functional blocks. An LSI can include data inputs and outputs coupled thereto. The LSI mentioned herein may be referred to as an IC, system LSI, super LSI, or ultra-large LSI, depending on the degree of integration. However, the technology for implementing integrated circuits is not limited to LSIs; it can also be implemented using dedicated circuits, general-purpose processors, or special-purpose processors. Furthermore, FPGAs (Field-Programmable Gate Arrays) that can be programmed after the LSI is manufactured can be used, or reconfigurable processors can be used, where the connections and settings of the internal circuitry units of the LSI can be reconfigured. This disclosure can be implemented as digital or analog processing. If future integrated circuit technologies replace LSIs due to advancements in semiconductor technology or other derivative technologies, future integrated circuit technologies can be used to integrate functional blocks. Biotechnology can also be applied.

[0622] This disclosure can be implemented by any kind of communication-enabled device, apparatus or system, collectively referred to as communication apparatus.

[0623] Communication devices may include transceivers and processing / control circuitry. A transceiver may include and / or act as both a receiver and a transmitter. A transceiver acting as both a transmitter and a receiver may include an RF (radio frequency) module, which includes amplifiers, RF modulators / demodulators, etc., and one or more antennas.

[0624] Non-limiting examples of such communication devices include telephones (e.g., cellular phones, smartphones), tablet computers, personal computers (PCs) (e.g., laptops, desktop computers, netbooks), cameras (e.g., digital cameras / camcorders), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, e-book readers, remote health / telemedicine (e.g., remote health and medical) devices, and vehicles that provide communication capabilities (e.g., cars, airplanes, ships), as well as various combinations thereof.

[0625] The communication device is not limited to portable or mobile devices, but may also include any type of non-portable or fixed device, equipment or system, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, and any other “thing” in an “Internet of Things (IoT)” network.

[0626] Communication may include the exchange of data through, for example, cellular systems, wireless LAN systems, satellite systems, and various combinations thereof.

[0627] The communication device may include devices such as controllers or sensors coupled to a communication device that performs the communication functions described herein. For example, the communication device may include a controller or sensor that generates control signals or data signals that are used by the communication device performing the communication functions of the communication device.

[0628] Communication devices may also include infrastructure such as base stations, access points, and any other devices, equipment, or systems that communicate with or control devices such as those in the non-limiting examples above.

[0629] Furthermore, various embodiments can also be implemented using software modules, which are executed by a processor or directly in the hardware. Combinations of software modules and hardware implementations are also possible. The software modules can be stored on any type of computer-readable storage medium. In particular, according to another embodiment, a non-transitory computer-readable recording medium is provided. The recording medium stores a program that, when executed by one or more processors, causes one or more processors to perform the steps of the method according to this disclosure.

[0630] By way of example and not limitation, such computer-readable storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and is accessible by a computer. Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if instructions are transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of medium. However, it should be understood that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transient media, but are specifically addressed to non-transient tangible storage media. As used herein, disks and optical discs include compact optical discs (CDs), laser discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, where disks typically magnetically copy data, while optical discs optically copy data using lasers. The above combinations should also be included within the scope of computer-readable media.

[0631] It should also be noted that various features of different embodiments may individually or in any combination form the subject of another embodiment. Those skilled in the art will understand that various changes and / or modifications can be made to this disclosure as illustrated in the specific embodiments. Therefore, this embodiment is to be considered illustrative rather than restrictive in all respects.

[0632] Other aspects

[0633] According to a first aspect, a communication device is provided. The communication device includes a transceiver and circuitry. The transceiver: (i) receives control signaling; (ii) transmits one or more transmissions of a random access (RA) procedure; (iii) receives one or more transmissions of the RA procedure; and (iv) transmits (a) a first physical uplink shared channel (PUSCH) transmission, or (b) a first physical uplink control channel (PUCCH) transmission. The first PUSCH transmission is the first of PUSCH transmissions scheduled after the completion of the RA procedure and by uplink (UL) authorization addressed to the communication device via a Radio Network Temporary Identifier (RNTI). The first PUCCH transmission acknowledges the reception of a downlink (DL) transmission, wherein the first PUCCH transmission is the first of PUCCH transmissions carrying a reception acknowledgment after the completion of the RA procedure. The circuit: (i) obtains from control signaling: (a) a cell handover command indicating that a cell handover from the source cell to the target cell will be performed by the communication equipment, and (b) an indication of the Transmission Configuration Indication (TCI) status; (ii) performs a cell handover to the target cell according to the cell handover command; (iii) performs the RA procedure in the target cell; and (iv) determines that the indicated TCI status will be used from the start of the operation or from the completion of the operation: (a) the first PUSCH transmission or (b) the first PUCCH transmission.

[0634] According to the second aspect provided in addition to the first aspect, the circuit determines at the time that: (i) if the indicated TCI state is a UL TCI state to be used for UL transmission, and the indication indicating the TCI state also indicates a DL TCI state to be used for DL ​​transmission, then the indicated UL TCI state and DL TCI state will be used for UL transmission and DL transmission respectively from the following operations or from the completion of the following operations: (a) a first PUSCH transmission, or (b) a first PUCCH transmission; or (ii) if the indicated TCI state is a TCI state to be used for both UL transmission and DL transmission, then the indicated TCI state will be used for UL transmission and DL transmission from the following operations or from the completion of the following operations: (a) a first PUSCH transmission or (b) a first PUCCH transmission.

[0635] According to a third aspect provided in addition to the first or second aspect: (i) the circuit: (a) determines that the indicated TCI state will be used from the start of the first PUSCH transmission if the predetermined time period is shorter than or equal to the time period between the UL authorization and the first PUSCH transmission, and (b) determines that the indicated TCI state will be used from the completion of the first PUSCH transmission if the predetermined time period is longer than the time period between the UL authorization and the first PUSCH transmission; or (ii) the circuit determines that: (a) the indicated TCI state will be used from the start of the first PUSCH transmission if the predetermined time period is shorter than or equal to the time period between the reception of the DL transmission and the first PUSCH transmission, and (b) the indicated TCI state will be used from the completion of the first PUSCH transmission if the predetermined time period is longer than the time period between the reception of the DL transmission and the first PUSCH transmission.

[0636] According to the fourth aspect provided in addition to any of the first to third aspects, one or more transmissions transmitted in the RA process include (i) a first RA transmission including a random access preamble, and (ii) a second RA transmission, which is a scheduling transmission including an indication of an RNTI, wherein the RNTI is a cell RNTI (C-RNTI). The transceiver: (i) transmits the first RA transmission and the second RA transmission, (ii) after transmitting the second RA transmission, receives DL control signaling addressing to the RNTI and scheduling the first PUSCH transmission, and (iii) transmits the first PUSCH transmission. The circuitry: (i) determines that the indicated TCI state will be used from the start of the first PUSCH transmission, or (ii) determines that the indicated TCI state will be used from the completion of the first PUSCH transmission.

[0637] According to the fifth aspect provided in addition to any of the first to third aspects, one or more transmitted transmissions in the RA process include a first RA transmission, which includes a random access preamble. One or more received transmissions in the RA process include a second RA transmission, which includes (a) a random access response addressed to an RNTI and (b) a UL authorization for the first PUSCH transmission, wherein the RNTI is an RA-RNTI. The transceiver: (i) transmits the first RA transmission, (ii) receives the second RA transmission after transmitting the first RA transmission, and (iii) transmits the first PUSCH transmission. The circuitry obtains the UL authorization for the first PUSCH transmission from the second RA transmission. Furthermore, the circuitry: (i) determines that an indicated TCI state will be used for transmission from the start of the first PUSCH transmission, or (ii) determines that an indicated TCI state will be used for transmission from the completion of the first PUSCH transmission.

[0638] According to the sixth aspect provided in addition to any of the first to third aspects, one or more transmissions sent in the RA process include an RA transmission, which includes (a) a random access preamble and (b) an indication of an RNTI, wherein the RNTI is a cell RNTI (C-RNTI); and the transceiver sends the RA transmission.

[0639] According to the seventh aspect provided in addition to the sixth aspect, the transceiver: (i) after transmitting the RA transmission, receives DL control signaling, which (a) addresses to the RNTI, where the RNTI is the cell RNTI (C-RNTI), (b) schedules the first PUSCH transmission, and (ii) transmits the first PUSCH transmission. The circuitry: (i) determines that the indicated TCI state will be used from the start of the first PUSCH transmission, or (ii) determines that the indicated TCI state will be used from the completion of the first PUSCH transmission.

[0640] According to the eighth aspect provided in addition to the sixth or seventh aspect, the transceiver: (i) after transmitting an RA transmission, receives (a) DL control signaling addressing to an RNTI and (b) scheduling a DL transmission, wherein the RNTI is a cell RNTI (C-RNTI); (ii) receives the DL transmission scheduled by the DL control signaling; and (iii) transmits a first PUCCH transmission, wherein the first PUCCH transmission carries an acknowledgment of receipt of the DL transmission. The circuitry: (i) determines that the indicated TCI state will be used from the start of the first PUCCH transmission, or (ii) determines that the indicated TCI state will be used from the completion of the first PUCCH transmission.

[0641] According to a ninth aspect, a method for a communication device is provided. The method includes the steps of: (i) receiving control signaling; (ii) obtaining from the control signaling: (a) a cell handover command indicating that a cell handover from a source cell to a target cell will be performed by the communication device; and (b) an indication of a Transmission Configuration Indication (TCI) state; (iii) performing a cell handover to the target cell according to the cell handover command; (iv) performing a random access (RA) procedure in the target cell, including: (a) transmitting one or more transmissions of the RA procedure; and (b) receiving one or more transmissions of the RA procedure; and (v) determining that the indicated TCI state will be used from the start of an operation or from the completion of an operation: (a) a first physical uplink. The first physical uplink shared channel (PUSCH) transmission, wherein the first PUSCH transmission is the first transmission among the PUSCH transmissions scheduled after the completion of the RA procedure and by the uplink UL authorization addressed to the radio network temporary identifier RNTI of the communication device, or (b) the first physical uplink control channel (PUCCH) transmission, wherein the first PUCCH transmission acknowledges the reception of the downlink DL transmission, wherein the first PUCCH transmission is the first transmission among the PUCCH transmissions carrying the reception acknowledgment after the completion of the RA procedure; and (vi) transmission: (a) the first PUSCH transmission, or (b) the first PUCCH transmission.

[0642] A further (dependent) aspect is provided for the method according to the ninth aspect, corresponding to the steps performed by the communication device provided in any of the second to eighth aspects.

[0643] According to the tenth aspect, a base station for operating a target cell is provided. The base station includes circuitry and a transceiver. The circuit: (i) determines that the communication device will perform a cell handover from the source cell to the target cell according to control signaling sent to the communication device in the source cell, wherein the control signaling includes (a) a cell handover command indicating that the communication device will perform a cell handover from the source cell to the target cell, and (b) an indication of a Transmission Configuration Indication (TCI) state; (ii) performs a random access (RA) procedure with the communication device in the target cell; and (iii) determines that the indicated TCI state will be used from the start of or upon completion of the following operations: (a) a first Physical Uplink Shared Channel (PUSCH) transmission, wherein the first PUSCH transmission is the first transmission of the communication device scheduled by the uplink UL authorization of the Radio Network Temporary Identifier (RNTI) addressed to the communication device after the completion of the RA procedure performed in the target cell, or (b) a first Physical Uplink Control Channel (PUCCH) transmission, wherein the first PUCCH transmission is the first transmission of the communication device carrying a reception acknowledgment after the completion of the RA procedure. The transceiver: (i) sends one or more transmissions of the RA process to the communication device; (ii) receives one or more transmissions of the RA process from the communication device; and (iii) receives from the communication device: (a) a first PUSCH transmission, or (b) a first PUCCH transmission.

[0644] According to the eleventh aspect provided in addition to the tenth aspect, the circuit determines at the time of determination: (i) if the indicated TCI state is a UL TCI state to be used for UL transmission, and the indication of the TCI state also indicates a DL TCI state to be used for DL ​​transmission, then the indicated UL TCI state and DL TCI state will be used for UL transmission and DL transmission respectively from the following operation or from the completion of the following operation: (a) a first PUSCH transmission, or (b) a first PUCCH transmission; or (ii) if the indicated TCI state is a TCI state to be used for both UL transmission and DL transmission, then the indicated TCI state will be used for UL transmission and DL transmission from the following operation or from the completion of the following operation: (a) a first PUSCH transmission or (b) a first PUCCH transmission.

[0645] According to a twelfth aspect provided in addition to the tenth or eleventh aspect: (i) the circuit: (a) determines that the indicated TCI state will be used from the start of the first PUSCH transmission if the predetermined time period is shorter than or equal to the time period between the UL authorization and the first PUSCH transmission, and (b) determines that the indicated TCI state will be used from the completion of the first PUSCH transmission if the predetermined time period is longer than the time period between the UL authorization and the first PUSCH transmission; or (ii) the circuit determines that: (a) the indicated TCI state will be used from the start of the first PUSCH transmission if the predetermined time period is shorter than or equal to the time period between the reception of the DL transmission and the first PUSCH transmission, and (b) the indicated TCI state will be used from the completion of the first PUSCH transmission if the predetermined time period is longer than the time period between the reception of the DL transmission and the first PUSCH transmission.

[0646] According to the thirteenth aspect provided in addition to any of the tenth to twelfth aspects, one or more received transmissions in the RA process include (i) a first RA transmission including a random access preamble, and (ii) a second RA transmission, which is a scheduling transmission including an indication of an RNTI, wherein the RNTI is a cell RNTI (C-RNTI). The transceiver: (i) receives the first RA transmission and the second RA transmission, (ii) after receiving the second RA transmission, sends DL control signaling addressing to the RNTI and scheduling the first PUSCH transmission, and (iii) receives the first PUSCH transmission. The circuit: (i) determines that the indicated TCI state will be used from the start of the first PUSCH transmission, or (ii) determines that the indicated TCI state will be used from the completion of the first PUSCH transmission.

[0647] According to the fourteenth aspect provided in addition to any of the tenth to twelfth aspects, one or more received transmissions in the RA process include a first RA transmission, which includes a random access preamble. One or more transmitted transmissions in the RA process include a second RA transmission, which includes (a) a random access response addressed to an RNTI and (b) a UL authorization for the first PUSCH transmission, wherein the RNTI is an RA-RNTI. The transceiver: (i) receives the first RA transmission, (ii) transmits the second RA transmission after receiving the first RA transmission, and (iii) receives the first PUSCH transmission. The circuitry generates the second RA transmission including the UL authorization for the first PUSCH transmission. Furthermore, the circuitry: (i) determines that an indicated TCI state will be used for transmission from the start of the first PUSCH transmission, or (ii) determines that an indicated TCI state will be used for transmission from the start of the completion of the first PUSCH transmission.

[0648] According to the fifteenth aspect provided in addition to any one of the tenth to twelfth aspects, one or more received transmissions in the RA process include an RA transmission, which includes (a) a random access preamble and (b) an indication of an RNTI, wherein the RNTI is a cell RNTI (C-RNTI); and the transceiver receives the RA transmission.

[0649] According to the sixteenth aspect provided in addition to the fifteenth aspect, the transceiver: (i) after receiving the RA transmission, sends DL control signaling, which (a) addresses to the RNTI, wherein the RNTI is the cell RNTI (C-RNTI), (b) schedules the first PUSCH transmission, and (ii) receives the first PUSCH transmission. The circuitry: (i) determines that the indicated TCI state will be used from the start of the first PUSCH transmission, or (ii) determines that the indicated TCI state will be used from the completion of the first PUSCH transmission.

[0650] According to the seventeenth aspect provided in addition to the fifteenth or sixteenth aspect, the transceiver: (i) after receiving the RA transmission, sends DL control signaling, which (a) addresses to the RNTI and (b) schedules the DL transmission, wherein the RNTI is the cell RNTI (C-RNTI); (ii) sends the DL transmission scheduled by the DL control signaling; and (iii) receives a first PUCCH transmission, wherein the first PUCCH transmission carries an acknowledgment of receipt of the DL transmission. The circuitry: (i) determines that the indicated TCI state begins to be used from the start of the first PUCCH transmission, or (ii) determines that the indicated TCI state begins to be used when the first PUCCH transmission is completed.

[0651] According to the eighteenth aspect, a method for operating a base station of a target cell is provided. The method includes the steps of: (i) determining that a communication device will perform a cell handover from a source cell to the target cell according to control signaling sent to the communication device in a source cell, wherein the control signaling includes (a) a cell handover command indicating that a cell handover from the source cell to the target cell will be performed by the communication device, and (b) an indication of a Transmission Configuration Indication (TCI) state; (ii) performing a random access (RA) procedure with the communication device in the target cell, including: (a) sending one or more transmissions of the RA procedure to the communication device in the target cell, and (b) receiving one or more transmissions of the RA procedure from the communication device in the target cell; (iii) determining that the indicated TCI state will be used for the following operations. The use of (a) a first Physical Uplink Shared Channel (PUSCH) transmission is initiated or commences upon completion of the following operations: (a) a first Physical Uplink Shared Channel (PUSCH) transmission, wherein the first PUSCH transmission is the first transmission among the PUSCH transmissions of the communication device scheduled by the uplink UL authorization of the Radio Network Temporary Identifier (RNTI) addressed to the communication device after the completion of the RA procedure performed in the target cell; or (b) a first Physical Uplink Control Channel (PUCCH) transmission, wherein the first PUCCH transmission is the first transmission among the PUCCH transmissions of the communication device carrying a reception acknowledgment after the completion of the RA procedure; and (iv) receiving (a) the first PUSCH transmission or (b) the first PUCCH transmission from the communication device.

[0652] Further (dependent) aspects are provided for the method according to aspect eighteen, which correspond to the steps performed by the base station provided by any one of aspects eleven to seventeen.

[0653] According to the nineteenth aspect, an integrated circuit (which can be deployed in a communication device, particularly a user equipment) is provided. The integrated circuit controls the processing of the communication device, the processing comprising the steps of: (i) receiving control signaling; (ii) obtaining from the control signaling: (a) a cell handover command indicating that a cell handover from a source cell to a target cell will be performed by the communication device; and (b) an indication of a Transmission Configuration Indication (TCI) state; (iii) performing a cell handover to the target cell according to the cell handover command; (iv) performing a random access (RA) procedure in the target cell, including: (a) transmitting one or more transmissions of the RA procedure; and (b) receiving one or more transmissions of the RA procedure; and (v) determining whether the indicated TCI state will be used from or after the following operations. The following are to be used: (a) a first Physical Uplink Shared Channel (PUSCH) transmission, wherein the first PUSCH transmission is the first of the PUSCH transmissions scheduled after the completion of the RA procedure and by the uplink UL authorization addressed to the radio network temporary identifier RNTI of the communication device, or (b) a first Physical Uplink Control Channel (PUCCH) transmission, wherein the first PUCCH transmission acknowledges the reception of the downlink DL transmission, wherein the first PUCCH transmission is the first of the PUCCH transmissions carrying the reception acknowledgment after the completion of the RA procedure; and (vi) transmission: (a) the first PUSCH transmission, or (b) the first PUCCH transmission.

[0654] For example, the integrated circuit according to the nineteenth aspect may include: an interface to a transceiver capable of receiving and transmitting signals; and circuitry (by hardware or software) configured to perform:

[0655] (i) Configure (or control) the transceiver via the interface to receive control signaling;

[0656] (ii) Obtained from control signaling (e.g., after receiving control signaling from the transceiver through the interface): (a) a cell handover command that instructs the communication device to perform a cell handover from the source cell to the target cell, and (b) an indication of the TCI status;

[0657] (iii) Perform a cell handover to the target cell according to the cell handover command;

[0658] (iv) Performing the RA procedure in the target cell, including configuring (or controlling) the transceiver via the interface to: (a) transmit one or more transmissions of the RA procedure, and (b) receive one or more transmissions of the RA procedure;

[0659] (v) Determines whether the indicated TCI state is used at the start or completion of the first PUCCH transmission that acknowledges the receipt of the first PUSCH transmission or DL ​​transmission; and

[0660] (vi) Configure (or control) the transceiver via the interface to send a first PUSCH transmission or a first PUCCH transmission.

[0661] The integrated circuit of aspect nineteen can also implement the corresponding features of any of aspects two through eight.

[0662] According to the twentieth aspect, an integrated circuit (which can be deployed in a base station, particularly a gNB) is provided. The integrated circuit controls the processing of a base station operating a target cell, the processing comprising the following steps: (i) determining that a communication device will perform a cell handover from a source cell to a target cell according to control signaling sent to the communication device in a source cell, wherein the control signaling includes (a) a cell handover command indicating that the communication device will perform a cell handover from the source cell to the target cell, and (b) an indication of a Transmission Configuration Indication (TCI) status; (ii) performing a random access (RA) procedure with the communication device in the target cell, comprising: (a) sending one or more transmissions of the RA procedure to the communication device in the target cell, and (b) receiving one or more transmissions of the RA procedure from the communication device in the target cell; (iii) determining the indicated... The TCI state will be used from the following operations or upon completion of the following operations: (a) a first physical uplink shared channel (PUSCH) transmission, wherein the first PUSCH transmission is the first transmission among the PUSCH transmissions of the communication device scheduled by the uplink UL authorization of the radio network temporary identifier (RNTI) addressed to the communication device after the completion of the RA procedure performed in the target cell; or (b) a first physical uplink control channel (PUCCH) transmission, wherein the first PUCCH transmission is the first transmission among the PUCCH transmissions of the communication device carrying a reception acknowledgment after the completion of the RA procedure; and (iv) receiving (a) the first PUSCH transmission or (b) the first PUCCH transmission from the communication device.

[0663] For example, the integrated circuit according to aspect 20 may include: an interface to a transceiver capable of receiving and transmitting signals; and circuitry (by hardware or software) configured to perform:

[0664] (i) Determine that the communication equipment will perform a cell handover from the source cell to the target cell according to control signaling;

[0665] (ii) Performing the RA procedure with the communication device in the target cell, including configuring (or controlling) the transceiver via the interface to: (a) send one or more transmissions of the RA procedure to the communication device in the target cell, and (b) receive one or more transmissions of the RA procedure from the communication device in the target cell;

[0666] (iii) Determine whether the indicated TCI state will be used at the start or completion of the first PUSCH transmission or the first PUCCH transmission; and

[0667] (iv) Configure (or control) the transceiver to receive a first PUSCH transmission or a first PUCCH transmission from the communication device via the interface.

[0668] The integrated circuit of aspect 20 can also implement the corresponding features of any of aspects 11 to 17.

[0669] According to the twenty-first aspect, a program is provided that is stored on a (non-transitory) storage medium and includes code instructions that, when executed on one or more processors of a communication device (particularly a user equipment or base station), cause the one or more processors to perform the steps of any one of the methods described above (the ninth and eighteenth aspects and their respective further aspects).

[0670] In summary, this disclosure relates to communication equipment, base stations, and corresponding methods for communication equipment and base stations. For example, the communication equipment is a user equipment (UE) including circuitry and a transceiver. The transceiver: (i) receives control signaling; (ii) transmits one or more transmissions of a random access (RA) procedure; (iii) receives one or more transmissions of the RA procedure; and (iv) transmits (a) a first physical uplink shared channel (PUSCH) transmission, wherein the first PUSCH transmission is the first transmission among PUSCH transmissions scheduled after the completion of the RA procedure and by uplink (UL) authorization addressed to the communication equipment via a radio network temporary identifier (RNTI), or (b) a first physical uplink control channel (PUCCH) transmission, wherein the first PUCCH transmission acknowledges the reception of a downlink (DL) transmission, wherein the first PUCCH transmission is the first transmission among PUCCH transmissions carrying a reception acknowledgment after the completion of the RA procedure. The circuit: (i) obtains from control signaling: (a) a cell handover command indicating that a cell handover from the source cell to the target cell will be performed by the communication equipment, and (b) an indication of the Transmission Configuration Indication (TCI) status; (ii) performs a cell handover to the target cell according to the cell handover command; (iii) performs the RA procedure in the target cell; and (iv) determines that the indicated TCI status will be used from the start of the operation or from the completion of the operation: (a) a first PUSCH transmission or (b) a first PUCCH transmission.

Claims

1. A communication device, comprising: Transceiver: - Receive control signaling, - Send one or more transmissions for the Random Access RA procedure. - Receive one or more transmissions of the RA process, and - send: o First Physical Uplink Shared Channel (PUSCH) transmission, wherein the first PUSCH transmission is the first of the PUSCH transmissions scheduled after the completion of the RA process and by the uplink UL grant addressed to the radio network temporary identifier (RNTI) of the communication device, or o First Physical Uplink Control Channel (PUCCH) transmission, the first PUCCH transmission acknowledging the reception of the downlink DL transmission, wherein the first PUCCH transmission is the first transmission among the PUCCH transmissions carrying reception acknowledgment after the completion of the RA procedure; and Circuit: - Obtained from the control signaling: o A cell handover command, the cell handover command indicating that the communication equipment will perform a cell handover from the source cell to the target cell, and o Indicates the transmission configuration and the TCI status; - Based on the cell handover command, perform a cell handover to the target cell; - Perform the RA procedure in the target cell; and - Determine whether the indicated TCI status will be used starting from the following operation or upon completion of the following operation: o The first PUSCH transmission, or o The first PUCCH transmission.

2. The communication device according to claim 1, wherein, The circuit is determined at the specified time: - If the indicated TCI state is a UL TCI state to be used for UL transmission, and the indication indicating the TCI state also indicates a DL TCI state to be used for DL ​​transmission, then the indicated UL TCI state and DL TCI state will be used for UL transmission and DL transmission respectively from the following operations or from the completion of the following operations: o The first PUSCH transmission, or o The first PUCCH transmission; or - If the indicated TCI state is the TCI state to be used for both UL and DL transmissions, the indicated TCI state will begin to be used for UL and DL transmissions from the following operation or from the completion of the following operation: o The first PUSCH transmission, or o The first PUCCH transmission.

3. The communication device according to claim 1 or 2, wherein, The circuit: - If the predetermined time period is shorter than or equal to the time period between the UL authorization and the first PUSCH transmission, then it is determined that the indicated TCI status will be used from the start of the first PUSCH transmission, and - If the predetermined time period is greater than the time period between the UL authorization and the first PUSCH transmission, then it is determined that the indicated TCI status will be used from the time the first PUSCH transmission is completed; or The circuit: - If the predetermined time period is shorter than or equal to the time period between the reception of the DL transmission and the first PUCCH transmission, then it is determined that the indicated TCI state will be used from the start of the first PUCCH transmission, and - If the predetermined time period is greater than the time period between the reception of the DL transmission and the first PUCCH transmission, it is determined that the indicated TCI state will be used from the time the first PUCCH transmission is completed.

4. The communication device according to any one of claims 1 to 3, wherein, One or more transmissions sent in the RA process include: - First RA transmission, the first RA transmission including random access preamble, and - Second RA transmission, the second RA transmission is a scheduling transmission that includes an indication of the RNTI, wherein the RNTI is a cell RNTI, i.e., C-RNTI; The transceiver: - Send the first RA transmission and the second RA transmission. - After sending the second RA transmission, receive DL control signaling addressed to the RNTI and scheduling the first PUSCH transmission. - Send the first PUSCH transmission; The circuit: - Determine that the indicated TCI state will be used starting from the first PUSCH transmission, or - Determine that the indicated TCI state will be used from the time the first PUSCH transmission is completed.

5. The communication device according to any one of claims 1 to 3, wherein, One or more transmissions sent during the RA process include a first RA transmission, the first RA transmission including a random access preamble. One or more received transmissions in the RA process include a second RA transmission, the second RA transmission including a random access response addressed to the RNTI and a UL authorization for the first PUSCH transmission, wherein the RNTI is an RA-RNTI; The transceiver: - Send the first RA transmission, - After sending the first RA transmission, receive the second RA transmission; - Send the first PUSCH transmission; The circuit obtains the UL authorization for the first PUSCH transmission from the second RA transmission, and The circuit: - Determine that the indicated TCI state will be used for transmission starting from the first PUSCH transmission, or - Determine that the indicated TCI state will be used for transmission starting when the first PUSCH transmission is completed.

6. The communication device according to any one of claims 1 to 3, wherein, One or more transmissions sent during the RA process include an RA transmission, which includes a random access preamble and an indication of an RNTI, wherein the RNTI is a cell RNTI, i.e., a C-RNTI; and The transceiver sends the RA transmission.

7. The communication device according to claim 6, wherein, The transceiver: - After sending the RA transmission, receive DL control signaling addressed to the RNTI and schedule the first PUSCH transmission, wherein the RNTI is the cell RNTI, i.e., C-RNTI; - Send the first PUSCH transmission; and The circuit: - Determine that the indicated TCI state will be used starting from the first PUSCH transmission, or - Determine that the indicated TCI state will be used from the time the first PUSCH transmission is completed.

8. The communication device according to claim 6 or 7, wherein, The transceiver: - After sending the RA transmission, receive DL control signaling addressed to the RNTI and schedule DL transmission, wherein the RNTI is the cell RNTI, i.e., C-RNTI. - Receive DL transmissions scheduled by the DL control signaling, and - Send the first PUCCH transmission, wherein the first PUCCH transmission carries an acknowledgment of receipt of the DL transmission; and The circuit: - Determine that the indicated TCI state will be used starting from the first PUCCH transmission, or - Determine that the indicated TCI state will be used from the time the first PUCCH transmission is completed.

9. A method for a communication device, the method comprising the following steps: Receive control signaling, Obtained from the control signaling: - A cell handover command, which indicates that the communication device will perform a cell handover from the source cell to the target cell, and - Indication of the transmission configuration and TCI status; According to the cell handover command, perform a cell handover to the target cell; Performing a random access (RA) procedure in the target cell includes: - Sending one or more transmissions of the RA process, and - Receive one or more transmissions from the RA process; The indicated TCI status will be used starting from the following operation or upon completion of the following operation: - First Physical Uplink Shared Channel (PUSCH) transmission, wherein the first PUSCH transmission is the first of the PUSCH transmissions scheduled after the completion of the RA process and by the uplink UL grant addressed to the radio network temporary identifier (RNTI) of the communication device, or - First Physical Uplink Control Channel (PUCCH) transmission, the first PUCCH transmission acknowledging the reception of the downlink DL transmission, wherein the first PUCCH transmission is the first transmission among the PUCCH transmissions carrying reception acknowledgment after the completion of the RA procedure; and send: - The first PUSCH transmission, or - The first PUCCH transmission.

10. A base station for operating a target cell, comprising: Circuit: - Determine that the communication device will perform a cell handover from the source cell to the target cell based on control signaling sent to the communication device in the source cell, wherein the control signaling includes: o A cell handover command, the cell handover command indicating that the communication equipment will perform a cell handover from the source cell to the target cell, and o Indicates the transmission configuration and the TCI status; - Perform a random access (RA) procedure with the communication device in the target cell; - Determine whether the indicated TCI status will be used starting from the following operation or upon completion of the following operation: o First Physical Uplink Shared Channel (PUSCH) transmission, wherein the first PUSCH transmission is the first transmission among the PUSCH transmissions of the communication device scheduled by the uplink UL grant addressed to the radio network temporary identifier (RNTI) of the communication device after the completion of the RA procedure performed in the target cell, or o First Physical Uplink Control Channel (PUCCH) transmission, the first PUCCH transmission being the first transmission among the PUCCH transmissions of the communication device after the completion of the RA process and carrying a reception acknowledgment; and Transceiver: - Send one or more transmissions of the RA process to the communication device. - Receive one or more transmissions from the communication device during the RA process, and - Received from the communication device: o The first PUSCH transmission, or o The first PUCCH.

11. A method for operating a base station of a target cell, the method comprising the following steps: It is determined that the communication device will perform a cell handover from the source cell to the target cell based on control signaling sent to the communication device in the source cell, wherein the control signaling includes: - A cell handover command, which indicates that the communication device will perform a cell handover from the source cell to the target cell, and - Indication of the transmission configuration and TCI status; Performing a random access (RA) procedure with the communication device in the target cell includes: - Sending one or more transmissions of the RA procedure to the communication device in the target cell. - Receive one or more transmissions of the RA process from the communication device in the target cell; The indicated TCI status will be used starting from the following operation or upon completion of the following operation: - First Physical Uplink Shared Channel (PUSCH) transmission, wherein the first PUSCH transmission is the first transmission among the PUSCH transmissions of the communication device scheduled by the uplink UL authorization addressed to the radio network temporary identifier (RNTI) of the communication device after the completion of the RA procedure performed in the target cell, or - First Physical Uplink Control Channel (PUCCH) transmission, the first PUCCH transmission being the first transmission among the PUCCH transmissions of the communication device after the completion of the RA process and carrying a reception acknowledgment; and Received from the communication device: - The first PUSCH transmission, or - The first PUCCH transmission.

12. An integrated circuit that controls the processing of a communication device, the processing comprising the following steps: Receive control signaling, Obtained from the control signaling: - A cell handover command, which indicates that the communication device will perform a cell handover from the source cell to the target cell, and - Indication of the transmission configuration and TCI status; According to the cell handover command, perform a cell handover to the target cell; Performing a random access (RA) procedure in the target cell includes: - Sending one or more transmissions of the RA process, and - Receive one or more transmissions from the RA process; The indicated TCI status will be used starting from the following operation or upon completion of the following operation: - First Physical Uplink Shared Channel (PUSCH) transmission, wherein the first PUSCH transmission is the first of the PUSCH transmissions scheduled after the completion of the RA process and by the uplink UL grant addressed to the radio network temporary identifier (RNTI) of the communication device, or - First Physical Uplink Control Channel (PUCCH) transmission, the first PUCCH transmission acknowledging the reception of the downlink DL transmission, wherein the first PUCCH transmission is the first transmission among the PUCCH transmissions carrying reception acknowledgment after the completion of the RA procedure; and send: - The first PUSCH transmission, or - The first PUCCH transmission.

13. An integrated circuit that controls the processing of a base station operating a target cell, the processing comprising the following steps: It is determined that the communication device will perform a cell handover from the source cell to the target cell based on control signaling sent to the communication device in the source cell, wherein the control signaling includes: - A cell handover command, which indicates that the communication device will perform a cell handover from the source cell to the target cell, and - Indication of the transmission configuration and TCI status; Performing a random access (RA) procedure with the communication device in the target cell includes: - Sending one or more transmissions of the RA procedure to the communication device in the target cell. - Receive one or more transmissions of the RA process from the communication device in the target cell; The indicated TCI status will be used starting from the following operation or upon completion of the following operation: - First Physical Uplink Shared Channel (PUSCH) transmission, wherein the first PUSCH transmission is the first transmission among the PUSCH transmissions of the communication device scheduled by the uplink UL authorization addressed to the radio network temporary identifier (RNTI) of the communication device after the completion of the RA procedure performed in the target cell, or - First Physical Uplink Control Channel (PUCCH) transmission, the first PUCCH transmission being the first transmission among the PUCCH transmissions of the communication device after the completion of the RA process and carrying a reception acknowledgment; and Received from the communication device: - The first PUSCH transmission, or - The first PUCCH transmission.