Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure is provided with: a reception unit that receives a candidate cell handover command; and controlling execution of a specific function for the candidate cell before receiving the handover command, the control unit executing the specific function on the basis of a parameter indicating whether execution of the specific function is possible.

Description

Technical Field Technical Field

[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system. Background Art

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been standardized to achieve even higher data rates and lower latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) has been standardized to further enhance the capacity and sophistication of LTE (Release (Rel.) 8 and 9) (Third Generation Partnership Project (3GPP (registered trademark))).

[0003] Successor systems to LTE (also known as, for example, fifth-generation mobile communication system (5G), 5G+ (plus), sixth-generation mobile communication system (6G), New Radio (NR), and 3GPP Rel. 15 and later) are also under study.

[0004] Prior art literature

[0005] Non-patent literature

[0006] Non-Patent Document 1: 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention

[0007] Problems to be solved by the invention

[0008] In future wireless communication systems (e.g., wireless communication systems after Rel.17 / 5G), it is envisioned to control communications using multiple transmission and reception points (e.g., Multi-TRP (MTRP)) in a serving cell, or to control communications based on inter-cell mobility including non-serving cells.

[0009] In this case, it is also envisioned that UL transmission control (e.g., execution of a random access procedure (or timing advance setting)) could be performed for each transmission / reception point, or for each serving cell and non-serving cell. However, the challenge is how a terminal (user terminal, User Equipment (UE)) can control UL transmission (e.g., timing advance control) for multiple transmission / reception points (or non-serving cells). If UL transmission for each transmission / reception point (or TRP for serving / non-serving cells) is not properly controlled, there is a concern that the quality of communications utilizing multiple transmission / reception points may deteriorate.

[0010] The present disclosure has been made in view of this point, and one of its objects is to provide a terminal, a wireless communication method, and a base station that can appropriately perform communication even when communication is performed using multiple transmission and reception points.

[0011] Means for solving problems

[0012] A terminal involved in one embodiment of the present invention is characterized in that it comprises: a receiving unit for receiving a switching command of a candidate cell; and a control unit for controlling the execution of a specific function for the candidate cell before receiving the switching command, wherein the control unit executes the specific function based on a parameter indicating whether the specific function can be executed.

[0013] Effects of the Invention

[0014] According to one aspect of the present disclosure, even when communication is performed using a plurality of transmission points, communication can be performed appropriately. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1A-1D This is a diagram showing an example of multi-TRP.

[0016] Figure 2A and Figure 2B This is a diagram showing an example of inter-cell mobility.

[0017] Figure 3A and Figure 3B This is a diagram showing an example of handover between a serving cell and an additional cell based on L1 / L2 signaling.

[0018] Figure 4 This is a diagram showing an example of setting example 1-3 for supporting candidate cells.

[0019] Figures 5A-5C This is a diagram showing an example of a case where switching of candidate cells / candidate cell groups based on L1 / L2 signaling is performed in setting example 1-3 in the case of supporting candidate cells.

[0020] Figure 6 This is a diagram showing an example of a timing advance group (TAG) to which cells included in a cell group belong.

[0021] Figure 7 This is a diagram showing an example of a MAC CE for a timing advance command.

[0022] Figure 8A and Figure 8B This is a diagram showing an example of the timing of PDCCH monitoring according to the first embodiment.

[0023] Figure 9 This is a diagram showing an example of a schematic configuration of a wireless communication system according to one embodiment.

[0024] Figure 10 This is a diagram showing an example of the configuration of a base station according to one embodiment.

[0025] Figure 11 This is a diagram showing an example of the configuration of a user terminal according to one embodiment.

[0026] Figure 12 This is a diagram showing an example of the hardware configuration of a base station and a user terminal according to one embodiment.

[0027] Figure 13 This is a diagram showing an example of a vehicle according to an embodiment. DETAILED DESCRIPTION

[0028] (TCI, spatial relation, QCL)

[0029] In NR, research is underway to control the reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, and coding) of at least one of a signal and a channel (expressed as signal / channel) in the UE based on the Transmission Configuration Indication state (TCI state).

[0030] The TCI state may also indicate the state of a signal / channel applied to a downlink. A state equivalent to the TCI state applied to a signal / channel applied to an uplink may also be expressed as a spatial relation.

[0031] The TCI status is information related to Quasi-Co-Location (QCL) of signals / channels and may also be referred to as spatial reception parameters, spatial relation information, etc. The TCI status may be set for each channel or each signal for the UE.

[0032] QCL is an indicator of the statistical properties of a signal / channel. For example, it can mean that when a signal / channel is in a QCL relationship with other signals / channels, it can be assumed that at least one of the Doppler shift, Doppler spread, average delay, delay spread, and spatial parameters (e.g., spatial Rx parameters) is the same among these different signals / channels (at least one of which is QCL).

[0033] In addition, the spatial reception parameter may also correspond to the UE's receive beam (eg, receive analog beam), and the beam may also be determined based on spatial QCL. The QCL (or at least one element of QCL) in this disclosure may also be rewritten as sQCL (spatial QCL).

[0034] Multiple QCL types (QCL types) can be specified. For example, four QCL types AD can be provided. The parameters (or parameter sets) that can be assumed to be the same in these four QCL types AD are different. These parameters (also referred to as QCL parameters) are expressed as follows:

[0035] QCL Type A (QCL-A): Doppler shift, Doppler spread, average delay, and delay spread;

[0036] QCL type B (QCL-B): Doppler shift and Doppler spread;

[0037] QCL Type C (QCL-C): Doppler shift and average delay;

[0038] QCL type D (QCL-D): spatial reception parameters.

[0039] The UE assumes that a certain Control Resource Set (CORESET), channel or reference signal is in a specific QCL relationship (e.g., QCL type D) with other CORESETs, channels or reference signals. This situation can also be called QCL assumption.

[0040] The UE may also determine at least one of a transmit beam (Tx beam) and a receive beam (Rx beam) of the signal / channel based on the TCI status or QCL assumption of the signal / channel.

[0041] The TCI status may also include, for example, information related to the QCL of the target channel (in other words, the reference signal (RS) used for that channel) and other signals (for example, other RSs). The TCI status may also be set (indicated) via higher-layer signaling, physical-layer signaling, or a combination thereof.

[0042] In addition, the channel / signal that becomes the application object of the TCI state can also be called the target channel / reference signal (target channel / RS), or simply referred to as the target, and the other signals mentioned above can also be called the reference reference signal (reference RS), source RS (source RS), or simply referred to as reference, etc.

[0043] The channel for which the TCI state or spatial relationship is set (specified) may also be, for example, at least one of a downlink shared channel (Physical Downlink Shared Channel (PDSCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), an uplink shared channel (Physical Uplink Shared Channel (PUSCH)), and an uplink control channel (Physical Uplink Control Channel (PUCCH)).

[0044] In addition, the RS that has a QCL relationship with the channel may be, for example, a synchronization signal block (SynchronizationSignal Block (SSB)), a channel state information reference signal (Channel State Information ReferenceSignal (CSI-RS)), a measurement reference signal (Sounding Reference Signal (SRS)), a tracking CSI-RS (also called a tracking reference signal (TRS))), a QCL detection reference signal (also called QRS), a demodulation reference signal (DeModulation Reference Signal (DMRS)), etc., at least one of the following.

[0045] The SSB is a signal block that includes at least one of a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a broadcast channel (physical broadcast channel (PBCH)). The SSB may also be referred to as an SS / PBCH block.

[0046] The RS of QCL type X in the TCI state may also mean an RS that is in a QCL type X relationship with a certain channel / signal (DMRS), and the RS may also be called a QCL source of QCL type X in the TCI state.

[0047] (Initial access process)

[0048] During the initial access procedure, the UE (RRC_IDLE mode) receives the SS / PBCH block (SSB), transmits Msg.1 (PRACH / random access preamble / preamble), receives Msg.2 (PDCCH, PDSCH containing the random access response (RAR)), transmits Msg.3 (PUSCH scheduled by the RAR UL grant), and receives Msg.4 (PDCCH, PDSCH containing the UE contention resolution identity). The UE then sends an ACK for Msg.4 to the base station (network), establishing an RRC connection (RRC_CONNECTED mode).

[0049] SSB reception includes PSS detection, SSS detection, PBCH-DMRS detection, and PBCH reception. PSS detection detects a portion of the physical cell ID (PCI), detects (synchronizes) OFDM symbol timing, and performs (coarse) frequency synchronization. SSS detection includes physical cell ID detection. PBCH-DMRS detection includes detecting (a portion of) the SSB index within a half radio frame (5ms). PBCH reception includes detecting the system frame number (SFN) and radio frame timing (SSB index), receiving configuration information for receiving the remaining minimum system information (RMSI, SIB1), and determining whether the UE can camp on the cell (carrier).

[0050] SSB has a 20-bit bandwidth and a 4-symbol time. The SSB transmission period can be set from {5, 10, 20, 40, 80, 160} ms. Within a half-frame, multiple SSB symbol positions are defined based on the frequency ranges (FR1 and FR2).

[0051] The PBCH has a 56-bit payload. N repetitions of the PBCH are sent in an 80ms period. N depends on the SSB transmission period.

[0052] System information consists of the MIB, RMSI (SIB1), and other system information (OSI) carried by the PBCH. The SIB1 includes RACH configuration and information used for RACH procedures. The time / frequency relationship between the SSB and the PDCCH monitoring resources used by the SIB1 is configured via the PBCH.

[0053] A base station using beam correspondence uses multiple beams to transmit multiple SSBs per SSB transmission period. Each SSB has multiple SSB indices. A UE that detects an SSB transmits a PRACH in the RACH opportunity associated with that SSB index and receives a RAR in the RAR window.

[0054] (Multiple TRPs)

[0055] In NR, one or more Transmission / Reception Points (TRPs) (multi-TRPs) are being studied for downlink transmissions to a UE using one or more panels (multi-panels). Furthermore, uplink transmissions from a UE to one or more TRPs are being studied.

[0056] In addition, multiple TRPs may correspond to the same cell identifier (cell identifier (ID)) or different cell IDs. The cell ID may be a physical cell ID (eg, PCI) or a virtual cell ID.

[0057] Figure 1A-Figure 1D The following are diagrams showing an example of a multi-TRP scenario. In these examples, it is assumed that each TRP can transmit four different beams, but the present invention is not limited to this.

[0058] Figure 1A This example shows a situation where only one TRP (TRP1 in this example) among multiple TRPs transmits to the UE (also referred to as single mode, single TRP, etc.). In this case, TRP1 transmits both control signals (PDCCH) and data signals (PDSCH) to the UE.

[0059] In the present disclosure, the single TRP mode may also mean a mode in the case where the multi-TRP (mode) is not set.

[0060] Figure 1B This example shows a situation (also called single-master mode) in which only one TRP (TRP1 in this example) among multiple TRPs sends control signals to the UE, and the multiple TRPs send data signals. The UE receives each PDSCH sent from the multiple TRPs based on a single downlink control information (Downlink Control Information (DCI)).

[0061] Figure 1C This example shows a scenario where each of multiple TRPs transmits a portion of a control signal to the UE, and the multiple TRPs transmit data signals (also known as master-slave mode). Alternatively, part 1 of the control signal (DCI) may be transmitted in TRP1, and part 2 of the control signal (DCI) may be transmitted in TRP2. Part 2 of the control signal may also depend on part 1. Based on these DCI portions, the UE receives each PDSCH transmitted from the multiple TRPs.

[0062] Figure 1D This example shows a scenario (also called multi-master mode) in which each of multiple TRPs transmits a different control signal to the UE, and these multiple TRPs transmit data signals. Alternatively, a first control signal (DCI) may be transmitted in TRP1, and a second control signal (DCI) may be transmitted in TRP2. Based on these DCIs, the UE receives the PDSCHs transmitted from these multiple TRPs.

[0063] exist Figure 1BIn the case where one DCI is used to schedule multiple PDSCHs from multiple TRPs (also called multiple PDSCHs), the DCI can also be called a single DCI (S-DCI, single PDCCH). Figure 1D When multiple DCIs are used to schedule multiple PDSCHs from multiple TRPs, these multiple DCIs can also be called multi-DCI (M-DCI, multiple PDCCH).

[0064] Each TRP in the multiple TRPs can send a different transport block (TB) / codeword (CW) / layer. Alternatively, each TRP in the multiple TRPs can send the same TB / CW / layer.

[0065] As a method for transmitting multiple TRPs, non-coherent joint transmission (NCJT) is under study. In NCJT, for example, TRP1 performs modulation mapping on a first codeword, performs layer mapping, and transmits a first PDSCH using a first precoding method for a first number of layers (e.g., two layers). Furthermore, TRP2 performs modulation mapping on a second codeword, performs layer mapping, and transmits a second PDSCH using a second precoding method for a second number of layers (e.g., two layers).

[0066] In addition, multiple PDSCHs (multi-PDSCHs) that are NCJTed can also be defined to partially or completely overlap with respect to at least one of the time domain and the frequency domain. That is, at least one of the time and frequency resources of the first PDSCH from the first TRP and the second PDSCH from the second TRP can also overlap.

[0067] It can also be assumed that the first PDSCH and the second PDSCH are not quasi-co-located. Reception of multiple PDSCHs can also be rewritten as simultaneous reception of PDSCHs of a non-QCL type (eg, QCL type D).

[0068] Support for PDSCH (transport block (TB) or codeword (CW)) repetition across multiple TRPs in URLLC for multiple TRPs is under study. Support for repetition across multiple TRPs in the frequency, layer (spatial), or time domains is under study (URLLC schemes, such as Schemes 1, 2a, 2b, 3, and 4). In Scheme 1, multiple PDSCHs from multiple TRPs are spatially multiplexed (SDM). In Schemes 2a and 2b, PDSCHs from multiple TRPs are frequency-division multiplexed (FDM). In Scheme 2a, the redundancy version (RV) is the same for multiple TRPs. In Scheme 2b, the RV can be the same or different for multiple TRPs. In Schemes 3 and 4, multiple PDSCHs from multiple TRPs are time-division multiplexed (TDM). In Scheme 3, multiple PDSCHs from multiple TRPs are transmitted within a single time slot. In scheme 4, multiple PDSCHs from multiple TRPs are sent in different time slots.

[0069] Based on such a multi-TRP scenario, more flexible transmission control can be performed by utilizing channels with good quality.

[0070] NCJT using multiple TRPs / panels may use high rank. In order to support ideal and non-ideal backhaul between multiple TRPs, single DCI (single PDCCH, for example, Figure 1B ) and multi-DCI (multi-PDCCH, e.g. Figure 1D ) Both for single DCI and multi-DCI, the maximum number of TRPs can also be 2.

[0071] For single-PDCCH designs (primarily for ideal backhaul), TCI extensions are under study. Each TCI code point within the DCI can also correspond to one or two TCI states. The TCI field size can also be the same as the Rel.15 TCI field size.

[0072] For PDCCH / CORESET specified in Rel. 15, a TCI state without a CORESET pool index (CORESETPoolIndex) (which may also be referred to as TRP information (TRP Info)) may also be set for a CORESET.

[0073] Regarding the enhancement of PDCCH / CORESET specified in Rel. 16, a CORESET pool index is set for each CORESET in a multi-TRP based on multi-DCI.

[0074] (Inter-cell mobility)

[0075] In NR, one or more Transmission / Reception Points (TRPs) (Multi-TRPs (MTRPs)) are being studied for DL transmissions to the UE. In addition, studies are underway for the UE to perform UL transmissions to one or more TRPs.

[0076] Consider that a UE receives channels / signals from multiple cells / TRPs in inter-cell mobility (e.g., L1 / L2 inter-cell mobility) (refer to Figure 2A , B).

[0077] Figure 2A This example shows inter-cell mobility (e.g., single-TRP inter-cell mobility) that includes non-serving cells. A UE can also be configured with a single TRP (or single TRP) in each cell. This example shows a situation where the UE receives channels / signals from both the base station / TRP of cell #1, which is the serving cell, and the base station / TRP of cell #3, which is not a serving cell (a non-serving cell). This corresponds to, for example, a UE switching from cell #1 to cell #3 (e.g., fast cell switch).

[0078] In this case, the port (e.g., antenna port) / TRP selection can also be performed dynamically. Port (e.g., antenna port) / TRP selection can also be performed based on the TCI status indicated or updated by the DCI / MAC CE. This indicates support for different physical cell IDs (e.g., PCIs) for cell #1 and cell #3.

[0079] Figure 2BThis example shows a multi-TRP scenario (e.g., inter-cell mobility using multiple TRPs). A UE can be configured with multiple (e.g., two) TRPs (or different CORESET pool indices) in each cell. This example shows a case where the UE receives channels / signals from TRP#1 and TRP2. Furthermore, this example shows a case where TRP#1 corresponds to Physical Cell ID (PCI) #1, and TRP#2 corresponds to PCI#2.

[0080] Multiple TRPs (TRP#1, #2) are connected via ideal / non-ideal backhaul, and information and data can be exchanged. The same or different code words (CW) and the same or different layers can also be sent from each TRP in the multiple TRPs. As one method of multiple TRP transmission, Figure 2B As shown, non-coherent joint transmission (NCJT) can also be used. Here, NCJT is performed between TRPs corresponding to different PCIs. In addition, the same serving cell setting can also be applied / set for TRP#1 and TRP#2.

[0081] Multiple PDSCHs (multi-PDSCHs) that are NCJTed can also be defined to partially or completely overlap in at least one of the time and frequency domains. That is, at least one of the time and frequency resources of the first PDSCH from TRP#1 and the second PDSCH from TRP#2 can also overlap. The first PDSCH and the second PDSCH can be used to transmit in the same TB or in different TBs.

[0082] It is also conceivable that the first PDSCH and the second PDSCH are not quasi-co-located. Reception of multiple PDSCHs can also be rewritten as simultaneous reception of PDSCHs that are not of a certain QCL type (eg, QCL type D).

[0083] Multiple PDSCHs from multiple TRPs (also called multiple PDSCHs) can also be scheduled using a single DCI (single DCI (S-DCI), single PDCCH) (single-master mode). A single DCI can also be sent from a single TRP in multiple TRPs. The structure of using a single DCI in multiple TRPs is also called multi-TRP (mTRP / MTRP) based on a single DCI.

[0084] Multiple PDSCHs from multiple TRPs can also be scheduled separately using multiple DCIs (multiple DCI (M-DCI), multiple PDCCHs (multiple PDCCHs)) (multi-master mode). Multiple DCIs can also be sent separately from multiple TRPs. The structure of using multiple DCIs in multiple TRPs is also called multi-TRP based on multiple DCIs (mTRP / MTRP).

[0085] The UE may also be configured to send separate CSI reports related to different TRPs. Such CSI feedback may also be referred to as separate feedback, separate CSI feedback, etc. In this disclosure, "separate" may be interchanged with "independent."

[0086] In inter-cell mobility, consider the following scenario 1 or scenario 2. In addition, in the present disclosure, the serving cell can also be rewritten as the TRP within the serving cell. Layer 1 / layer 2 (layer1 / layer2 (L1 / L2)), DCI / Medium Access Control Control Element (MAC CE)) can also be rewritten with each other. In the present disclosure, a PCI that is different from the Physical Cell Identity (PCI) of the current serving cell is sometimes referred to as a "different PCI". Non-serving cells, cells with different PCIs, and additional cells can also be rewritten with each other.

[0087] <Scenario 1>

[0088] Scenario 1 corresponds to, for example, inter-cell mobility with multiple TRPs. Scenario 1 may also be a scenario that does not correspond to inter-cell mobility with multiple TRPs. In Scenario 1, for example, the following process is performed.

[0089] (1) The UE receives from the serving cell the configuration of the SSB for beam measurement of the TRP corresponding to the PCI different from that of the serving cell, and the configuration necessary for using radio resources for data transmission and reception, including resources of the different PCI.

[0090] (2) The UE performs beam measurement of TRPs corresponding to different PCIs and reports the beam measurement results to the serving cell.

[0091] (3) Based on the above report, the Transmission Configuration Indication (TCI) status associated with the TRP corresponding to the different PCI is activated through L1 / L2 signaling from the serving cell.

[0092] (4) The UE uses the UE-dedicated channel on the TRP corresponding to different PCIs for transmission and reception.

[0093] (5) The UE must always be within the serving cell, including multiple TRPs. As in existing systems, the UE must use common channels from the serving cell (such as the Broadcast Control Channel (BCCH) and the Paging Channel (PCH)).

[0094] In Scenario 1, when the UE transmits or receives signals to or from the additional cell / TRP (the TRP corresponding to the additional cell's PCI), the serving cell (the UE's assumption of the serving cell) remains unchanged. In other words, L1 / L2-based serving cell handover is not supported. The UE is configured with higher-layer parameters associated with the PCI of the non-serving cell from the serving cell. Scenario 1 can also be applied, for example, in Rel. 17.

[0095] Figure 3A This figure illustrates an example of UE mobility in Rel. 17. Consider a scenario where a UE moves from a cell with PCI #1 (serving cell) to a cell with PCI #3 (additional cell) (overlapping with the serving cell). In this case, Rel. 17 does not support L1 / L2 serving cell handover.

[0096] Supplementary cells are cells with supplementary PCIs that differ from the serving cell's PCI. UEs can send and receive UE-specific channels from supplementary cells. To receive UE-common channels (e.g., system information, paging, and short messages), the UE must be within the coverage of the serving cell. If the UE moves outside the coverage of the serving cell, it must switch cells through handover (also known as L3 mobility).

[0097] <Scenario 2>

[0098] In Scenario 2, L1 / L2 inter-cell mobility is applied. L1 / L2 inter-cell mobility enables the serving cell to be changed without reconfiguring the RRC, using functions such as beam steering. In other words, transmission and reception with the added cell can be performed without handover (or without performing L3 mobility procedures). Because handover requires RRC reconnection and other procedures, which can result in periods where data communication is unavailable, the application of L1 / L2 inter-cell mobility, which does not require handover, allows data communication to continue even when the serving cell is changed. In Scenario 2, for example, the following steps are performed.

[0099] (1) The UE receives the SSB configuration of a cell (additional cell) having a different PCI from the serving cell for beam measurement / serving cell change.

[0100] (2) The UE performs beam measurement on cells using different PCIs and reports the measurement results to the serving cell.

[0101] (3) The UE may also receive the configuration of a cell with a different PCI (serving cell configuration) through higher layer signaling (e.g., RRC). In other words, it may be pre-configured for changing the serving cell. This configuration may be performed together with the configuration in (1) or separately.

[0102] (4) Based on the above report, the TCI status of cells with different PCIs can also be activated through L1 / L2 signaling according to the change of serving cell. The activation of TCI status and the change of serving cell can also be performed separately.

[0103] (5) The UE changes the serving cell (assuming the serving cell) and starts receiving / transmitting using the pre-set UE-specific channel and TCI state.

[0104] That is, in Scenario 2, the serving cell (the assumption of the serving cell in the UE) is updated through L1 / L2 signaling. Scenario 2 can also be applied in Rel. 18 and later.

[0105] Figure 3B This figure illustrates an example of UE mobility in Rel. 18. In Rel. 18, the serving cell is switched via L1 / L2. The UE can transmit and receive UE-specific channels and common channels with the new serving cell. The UE can also move out of the coverage of the previous serving cell.

[0106] (Setting of candidate cells)

[0107] In L1 / L2 inter-cell mobility, candidate cells may be configured in addition to the serving cell. In this disclosure, the term "candidate cell" may also be rewritten as a target cell, an additional cell, or an additional PCI. One or more candidate cells (or candidate cell groups) may be associated with each serving cell, or one or more candidate cells (or candidate cell groups) may be associated with multiple serving cells.

[0108] The configuration of candidate cells (or candidate cell groups) can also be configured using specific higher-layer parameters (e.g., ServingCellConfig) in the same manner as inter-cell beam management (BM) in existing systems (e.g., prior to Rel. 17). Alternatively, the configuration of candidate cells (or candidate cell groups) can reuse the framework for carrier aggregation configuration (e.g., CA configuration framework) or the framework for CHO (Conditional Handover) / CPC (Conditional PSCell Change) configuration.

[0109] Regarding the candidate cells (or candidate cell groups) configured by higher layer parameters, the activation / deactivation may be instructed to the UE via MAC CE / DCI.

[0110] For example, at least one of the following example settings 1 to 3 may be applied to the candidate cell configuration (or the association with the serving cell). Here, SpCell#0, SCell#1, and SCell#2 are configured as serving cells, and this illustrates an example of candidate cells / candidate cell groups configured separately from the serving cell. The following example settings 1 to 3 are merely examples; the number of serving cells / candidate cells / candidate cell groups, the association between serving cells and candidate cells, and the like are not limited thereto and can be modified as appropriate. Alternatively, other example settings may be supported / applied in addition to or in place of example settings 1 to 3.

[0111] [Setting Example 1]

[0112] Setting example 1 is: for each serving cell (or the frequency domain corresponding to each serving cell), one or more candidate cells are associated / set (refer to Figure 4 Here, the following situation is shown: candidate cells #0-1, #0-2, and #0-3 are associated with SpCell#0 (or the frequency domain corresponding to SpCell#0), candidate cell #1-1 is associated with SCell#1 (or the frequency domain corresponding to SCell#1), and candidate cells #2-1 and #2- are associated with SCell#2 (or the frequency domain corresponding to SpCell#2). Information related to this association can also be set / indicated by the base station to the UE via RRC / MAC CE / DCI.

[0113] [Setting Example 2]

[0114] Setting example 2 is: for MAC entity / MCG / SCG, associate / set candidate cells (refer to Figure 4). Here, the case where candidate cells #3-#8 are associated with the MAC entity / MCG / SCG is shown. In this case, the candidate cells are not associated with each serving cell, but rather the candidate cells are set to the MAC entity or cell group (for example, MCG / SCG). Information related to the candidate cells set to each cell can also be set / indicated to the UE from the base station via RRC / MAC CE / DCI.

[0115] [Setting Example 3]

[0116] In setting example 3, one or more candidate cell groups are set (refer to Figure 4 A candidate cell group includes one or more candidate cells. Here, a case is shown where candidate cell group #1 including candidate cells #0-#2, candidate cell group #2 including candidate cells #0 and #1, and candidate cell group #3 including candidate cell #0 are configured. At least one of information related to the configured candidate cell groups and information related to the candidate cells included in each candidate cell group may also be configured / indicated to the UE by the base station via RRC / MACCE / DCI.

[0117] [Serving cell switching]

[0118] In an existing system (eg, Rel. 17), L1 beam indication related to the TCI status of an additional PCI (or an additional cell) is supported (eg, indication based on the TCI status field of the DCI).

[0119] In Rel. 18 and later, support for new L1 / L2 signals (e.g., DCI / MAC CE) for indicating a serving cell switch (e.g., a serving cell switch) is envisioned. This indication may include at least one of implicit and explicit indications. Implicit indication may mean, for example, that a CORESET is updated to a TCI state associated with an additional PCI via a MAC CE. Explicit indication may also mean that a cell switch is directly indicated via a DCI / MAC CE.

[0120] For example, in the candidate cell setting example 1, a specific candidate cell may be designated as a serving cell (or instructed to switch to a serving cell) via L1 / L2 signaling. Figure 5A , candidate cell #0-2 becomes the SpCell of the MCG / SCG through L1 / L2 signaling (SpCell #0 and candidate cell #0-2 are switched). Furthermore, candidate cell #2-1 becomes the SCell of the MCG / SCG through L1 / L2 signaling (SCell #2 and candidate cell #2-1 are switched).

[0121] Alternatively, in the example 2 of setting the candidate cell, a specific candidate cell may be designated as a serving cell (or instructed to switch to a serving cell) via L1 / L2 signaling. Figure 5B , a case is shown where the candidate cell #4 becomes the SpCell of the MCG / SCG (SpCell #0 and the candidate cell #4 are switched) through L1 / L2 signaling.

[0122] Alternatively, in the candidate cell setting example 3, a specific candidate cell group (or one or more candidate cells included in the specific candidate cell group) may also be changed / updated to a serving cell group via L1 / L2 signaling. Figure 5C Figure 2 shows how candidate cell group #1 (or candidate cells #0-#2 included in candidate cell group #1) becomes the serving cell group (the serving cell group and candidate cell group #1 are switched) through L1 / L2 signaling. Among the candidate cells included in candidate cell group #1 (here, candidate cells #0-#2), a candidate cell associated with SpCell #0 or a candidate cell configured in the same frequency domain as SpCell #0 (here, candidate cell #0) can also be configured as a new SpCell. Alternatively, the candidate cell to become the SpCell can be indicated through L1 / L2 signaling.

[0123] (Timing advance group)

[0124] When using multiple TRPs, the distance between the UE and each TRP may be different. Multiple TRPs may also be included in the same cell (e.g., serving cell). Alternatively, one of the multiple TRPs may be equivalent to the serving cell, while the other TRPs may be equivalent to non-serving cells. In this case, it is also assumed that the distance between each TRP and the UE is different.

[0125] In existing systems, the transmission timing of UL (Uplink) channels and / or UL signals (UL channels / signals) is adjusted using Timing Advance (TA). The reception timing of UL channels / signals from different user terminals (UEs) is also adjusted at the radio base station (also known as a Transmission and Reception Point (TRP), gNB (gNodeB), etc.).

[0126] The UE may also apply the timing advance (multiple timing advance) for each preset timing advance group (TAG) to perform timing control of UL transmission.

[0127] When multiple timing advances are used, support is provided for timing advance groups (TAGs), which are categorized by transmission timing. The UE is expected to apply the same TA offset (or TA value) to each TAG to control the UL transmission timing in each TAG. In other words, the TA offset can be independently set for each TAG.

[0128] When multiple timing advances are applied, the UE independently adjusts the transmission timing of cells belonging to each TAG. This allows the radio base station to align the timing of receiving uplink signals from the UE even when multiple cells are used.

[0129] TAGs (e.g., serving cells belonging to the same TAG) can also be configured using higher-layer parameters. The same timing advance value can also be applied to serving cells belonging to the same TAG. Alternatively, the timing advance group for the SpCell containing the MAC entity is called the primary timing advance group (PTAG), and all other TAGs are called secondary timing advance groups (STAGs).

[0130] In existing systems (e.g., Rel.16 NR), each cell group (e.g., MCG / SCG) supports a maximum of 4 TAGs (see Figure 6 ).exist Figure 6 Figure 3 shows a case where three tags are configured for a cell group consisting of SpCell and SCells #1 to #4. Here, the SpCell and SCell #1 belong to the first TAG (PTAG or TAG #0), SCell #2 and SCell #3 belong to the second TAG (TAG #1), and SCell #4 belongs to the third TAG (TAG #2).

[0131] A timing advance command (TA command) can also be sent to the UE using a MAC control element (e.g., a MAC CE). The TA command specifies the transmission timing value for the uplink channel and is included in the MAC control element. The TA command is signaled from the radio base station to the UE at the MAC layer. The UE controls a specific timer (e.g., the TA timer) based on receipt of the TA command.

[0132] The MAC CE for timing advance command (TAC MAC CE) may also be a structure including a field for timing advance group index (eg, TAGID) and a field for timing advance command (see Figure 7 ).

[0133] On the other hand, it is envisioned that in future wireless communication systems, different TAGs (or TAG-IDs) may be configured for more than one TRP corresponding to a certain cell (or CC). For example, regarding multi-TRP operation using multiple DCIs, it is envisioned that two TAs (or TAGs) may be supported in UL transmission.

[0134] Alternatively, it is also envisioned that different TRPs corresponding to a certain cell share a common TAG. Alternatively, it is also envisioned that the MAC CE for TA command is applied to only one TRP, or that the MAC CE for TA command is applied to multiple TRPs.

[0135] Alternatively, it is also envisioned that the TRPs corresponding to different cells use different TAGs / share a common TAG. For example, in inter-cell mobility, it is also envisioned that the UL transmission is controlled based on a common / different timing advance for the serving cell (or the TRP of the serving cell) and the non-serving cell (or the TRP of the non-serving cell).

[0136] As described above, in MIMO after Rel. 18, in multi-TRP operation using multiple DCIs, it is also assumed that two timing advances (TAs) for two TRPs are supported.

[0137] When TAGs are configured / controlled in units of TRPs, a time alignment timer (e.g., timeAlignmentTimer) can also be set for each TRP. The time alignment timer can also control the time at which the MAC entity considers the serving cell to which the associated TAG belongs to be uplink time aligned (e.g., uplink time aligned). For example, the time alignment timer can also be set via RRC to maintain (e.g., maintain) UL time alignment.

[0138] A time alignment timer (e.g., timeAlignementTimer) can also be maintained for UL time alignment. In Rel. 17, a time alignment timer (e.g., timeAlignementTimer) is associated with each tag. Upon receiving a MAC CE for a timing advance command (e.g., TAC MAC CE), the UE starts or restarts the time alignment timer associated with each indicated timing advance group (e.g., tag).

[0139] The MAC entity receives the TAC MAC CE and maintains a specific value (N TA), apply the timing advance command for the indicated TAG, or start or restart the time alignment timer associated with the indicated TAG. TA ) can also be the timing advance between DL and UL.

[0140] The operation when the time alignment timer expires can also be defined separately in the PTAG and STAG. In addition, the timing advance group (TAG) of the SpCell including the MAC entity can be called the primary timing advance group (PTAG), and the other TAGs can be called secondary timing advance groups (STAG).

[0141] For example, Rel. 17 may also support the following: when the timing advance timer corresponding to PTAG expires, a specific PTAG operation may be applied; and when the timing advance timer corresponding to STAG expires, a specific STAG operation may be applied.

[0142] For example, when the time alignment timer expires, the following operations (eg, operations for a specific PTAG / operations for a specific STAG) may be performed.

[0143] [Specific PTAG operation]

[0144] In case the time alignment timer is associated with PTAG,

[0145] • Flush (discard) all HARQ buffers of all serving cells.

[0146] When set, the RRC is notified to release the PUCCH to all serving cells.

[0147] If set, notify RRC to release SRS.

[0148] Clear all configured DL allocations and UL allocations.

[0149] Clear PUSCH resources used for semi-persistent CSI reporting.

[0150] · Expire all running time alignment timers.

[0151] Maintain N for all tags TA .

[0152] [Specific STAG operation]

[0153] When the time alignment timer is associated with a STAG, for all serving cells belonging to the TAG,

[0154] • Flush (discard) all HARQ buffers.

[0155] If set, notify RRC to release the PUCCH.

[0156] If set, notify RRC to release SRS.

[0157] Clear all configured DL and UL allocations.

[0158] Clear PUSCH resources used for semi-persistent CSI reporting.

[0159] Maintain the N of the TAG TA .

[0160] (TA control in TRP / panel)

[0161] As described above, when communication is performed using a plurality of transmission and reception points (eg, TRPs) / panels, it is also assumed that the timing advance (TA) is controlled for each TRP / each panel.

[0162] In NRs after Rel.18, for RACH triggered by PDCCH order and RACH triggered by UE, contention based random access (CBRA) and non-contention free random access (CFRA) are considered / determined in TRP units or TRP TA (TA per TRP) units.

[0163] In the case of supporting the application / setting of timing advance per TRP (or in TRP units), the UE controls the UL transmission (e.g., RACH transmission, etc.) in each TRP based on the timing advance corresponding to each TRP (or the timing advance group to which each TRP belongs).

[0164] Information related to the TRP corresponding to each serving cell (e.g., TRP index / TRP ID) can also be set / indicated from the base station to the UE using RRC / MAC CE / downlink control information. The UE can also receive information related to the timing advance corresponding to each TRP (e.g., information related to the TA value / timing advance command / time alignment timer, etc.) from the base station.

[0165] Each embodiment of the present disclosure may also be applied to / supported in at least one of intra-cell multi-TRP (Intra-cell M-TRP) and inter-cell multi-TRP (Inter-cell M-TRP).

[0166] In intra-cell multi-TRPs, multiple TRPs (or activated TCI states of multiple TRPs) can also be associated with the same cell ID. The cell ID can also be a physical cell ID (PCI).

[0167] In inter-cell multi-TRPs, multiple TRPs (or activated TCI states of multiple TRPs) can also be associated with different cell IDs (e.g., PCIs). For example, in inter-cell multi-TRPs, two TRPs can also be rewritten as two TRPs associated with two PCIs, respectively.

[0168] When supporting the application / configuration of timing advance per TRP (or per TRP), each TRP may belong to a different TAG. Multiple TRPs (e.g., two TRPs) in a serving cell may each belong to two separate TAGs. A TAG may also contain multiple TRPs from multiple serving cells. All TRPs / serving cells within a TAG apply / maintain the same timing advance (TA) / time alignment timer.

[0169] In the present disclosure, a TAG may contain more than one sub-TAG. For example, two TRPs of a serving cell may belong to two sub-TAGs and one TAG respectively. A sub-TAG may also contain multiple TRPs from multiple serving cells. All TRPs / serving cells within a sub-TAG apply / maintain the same timing advance (TA) / time alignment timer.

[0170] For example, TA may be applied to each TRP (or may be instructed in TRP / TA units). For example, at least one of the following options may be applied.

[0171] [Option 1]

[0172] A different TAG-ID may be set for each TRP, and a different MAC CE for TA command may be set for each TRP. Each TAG may also maintain a time alignment timer for UL time alignment.

[0173] [Option 2]

[0174] Different TRPs can also share a TAG. The MAC CE for the TA command can also be applied to only one TRP. The UE can also apply different TAs to other TRPs. For example, the UE can adjust the TA value for other TRPs (e.g., TRP#1) using a TA offset (TA_TRP_offset) based on the TA for TRP#0 (TA_TRP#0).

[0175] In this case, there may be only one time alignment timer for UL time alignment of multiple TRPs. This means that UL time alignment of multiple TRPs can be maintained or lost at the same time.

[0176] [Option 3]

[0177] The TAG may also be set to one. The TA command MAC CE may also be applied to multiple service TRPs for the UE.

[0178] [Option 4]

[0179] Alternatively, a single TAG can be used. A MAC CE for a TA command received via a TRP / CW / PDSCH / DMRS port group can be applied to the same TRP / CW / PDSCH / DMRS port group in the TAG. Each TRP / CW / PDSCH / DMRS port group in the TAG can also maintain a time alignment timer for UL time alignment.

[0180] Thus, support for multiple timing advances in multiple TRPs (e.g., multiple TRPs utilizing multiple DCIs) is also envisioned in Rel. 18 and later versions. For example, multiple (e.g., two) timing advances can be supported for multiple TRPs utilizing multiple DCIs. Furthermore, the use of multiple timing advances for multiple TRPs can be supported in both intra-cell and inter-cell multi-DCI multi-TRP scenarios, as well as in multiple frequency ranges (e.g., FR1 and FR2).

[0181] (PDCCH order)

[0182] DCI format 1_0 includes a DCI format identifier field, a bit field that is always set to 1, and a frequency domain resource assignment field. If the cyclic redundancy check (CRC) of DCI format 1_0 is scrambled by the C-RNTI and the frequency domain resource assignment field is all 1, DCI format 1_0 is used for random access procedures initiated by a PDCCH order. The remaining fields are the random access preamble, UL / supplementary uplink (SUL) indicator, SS / PBCH index (SSB index), PRACH mask index, and reserved bits (12 bits).

[0183] In the case of PRACH transmission triggered by a PDCCH command, the PRACH mask index field indicates that, when the value of the random access preamble index field is not zero, the PRACH opportunity is a PRACH transmission associated with the SS / PBCH block index indicated by the SS / PBCH block index field of the PDCCH command.

[0184] (RACH process triggered by PDCCH command)

[0185] In existing systems (e.g., prior to Rel. 17), regarding RACH procedures for specific cells (e.g., SpCells), the UE performs the RACH procedure based on the assumption that the PDCCH command and the RAR PDCCH have the same QCL characteristics. The RAR PDCCH can also be a PDCCH transmitted by the base station in response to a PRACH triggered to the UE (or transmitted from the UE) by a PDCCH command. The PDSCH scheduled by this RAR PDCCH can also include the RAR. The QCL characteristics can also be rewritten as DMRS QCL characteristics.

[0186] Specifically, when the UE detects DCI format 1_0 scrambled by CRC via the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH command for triggering a CFRA process for the SpCell, the UE may also assume that the PDCCH containing DCI format 1_0 and the PDCCH command have the same DMRS antenna port quasi-co-location characteristics.

[0187] In addition, in RAR monitoring that is not triggered by PDCCH commands, the QCL of the CORESET that transmits the RAR may be the same as the SSB / CSI-RS used in the PRACH.

[0188] In existing systems (e.g., prior to Rel. 17), RACH procedures for other cells (e.g., SCells) are not restricted to specific cells, and support the UE's reception of the PDCCH for RAR using the QCL of a specific CORESET. The specific CORESET may also be a CORESET associated with a Type 1 CSS set (e.g., Type 1-PDCCH CSS set).

[0189] Specifically, when the UE detects DCI format 1_0 scrambled by CRC via the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDDCCH command for triggering a CFRA process for the SCell, the UE may also envision the quasi-co-location characteristics of the DMRS antenna ports of the CORESET associated with the type 1-PDCCH CSS set for receiving the PDCCH containing DCI format 1_0.

[0190] In this way, in RAR monitoring of the RACH ordered by the PDCCH for the SCell, the QCL of the RAR CORESET may also be associated with the Type 1-PDCCH CSS set.

[0191] However, to obtain the TA for each TRP (or the TA for the serving cell and non-serving cell), a RACH can be triggered for each TRP (or for each serving cell / non-serving cell). Regarding the PDCCH command that triggers the RACH procedure to a TRP (or serving cell / non-serving cell), it is also possible to consider the case where the PDCCH command and the RAR PDCCH are sent from different TRPs. In such a case, the restriction that the PDCCH command and the RAR PDCCH have the same DMRS QCL characteristics needs to be relaxed or modified.

[0192] For example, it is also possible to support: the PDCCH command from TRP#1 triggers the RACH to TRP#2, and the RAR is sent from TRP#2. In this case, the RACH to any TRP can be triggered via the PDCCH command from any TRP, which can improve the flexibility of the RACH process.

[0193] As another example, a PDCCH command from TRP#2 triggers a RACH to TRP#2, and a RAR is sent from TRP#1. This example may occur in an inter-cell multi-TRP (e.g., inter-cell M-TRP) scenario when the UE cannot receive a Type 1 CSS set from a TRP in a non-serving cell.

[0194] (Random access procedure in MAC entity)

[0195] The random access procedure is initiated via a PDCCH command, the MAC entity itself, or an RRC event according to the specification. Within the MAC entity, only one random access procedure is in progress at any given time. The random access procedure for an SCell is initiated only via a PDCCH command with an ra-PreambleIndex different from 0b000000.

[0196] When the random access procedure is started on the serving cell, the MAC entity performs the following operations.

[0197] When the random access procedure is started by a PDCCH command and the ra-PreambleIndex explicitly provided by the PDCCH is not 0b000000, or when the random access procedure is started to accompany synchronization reconfiguration and contention-free random access resources of the 4-step RA type are explicitly provided by rach-ConfigDedicated to the BWP selected for the random access procedure, RA_TYPE is set to 4-step RA.

[0198] When the selected RA_TYPE is set to 4-step RA, the MAC entity performs the following operations.

[0199] When ra-PreambleIndex is explicitly provided from the PDCCH and ra-PreambleIndex is not 0b000000, PREAMBLE_INDEX is set to the notified ra-PreambleIndex, and the SSB notified by the PDCCH is selected.

[0200] ·When the SSB is selected as above, the next available PRACH opportunity is determined based on the PRACH opportunities corresponding to the selected SSB that are permitted according to the restrictions given by ra-ssb-OccasionMaskIndex (the MAC entity randomly selects a PRACH opportunity with medium probability from consecutive PRACH opportunities corresponding to the selected SSB in accordance with the specifications. When determining the next available PRACH opportunity corresponding to the selected SSB, the MAC entity may also consider the possibility of generating a measurement gap).

[0201] For example, when a new random access procedure is started while another random access procedure is already in progress within the MAC entity, whether to continue the ongoing procedure or start a new procedure (SI request, etc.) depends on the actual installation of the UE.

[0202] When the UE receives other PDCCH commands indicating the same random access preamble, PRACH mask index and UL carrier, if there is already an ongoing random access procedure triggered by a certain PDCCH command, the procedure is regarded as the same random access procedure as the ongoing procedure and is not reinitialized.

[0203] (Contention Resolution)

[0204] If Msg3 is sent, the MAC entity follows operations 1 to 4 below.

[0205] [Operation 1] When Msg3 is sent on a non-terrestrial network, the MAC entity starts the ra-ContentionResolutionTimer and restarts the ra-ContentionResolutionTimer in each HARQ retransmission within the first codeword after the end of Msg3 plus the UE estimate of the UE-gNB RTT.

[0206] [Operation 2] Otherwise, when the Msg3 transmission (initial transmission or HARQ retransmission) is scheduled with the Type A PUSCH repetition, the MAC entity starts or restarts the ra-ContentionResolutionTimer in the first codeword after all the repetitions of the Msg3 transmission are completed.

[0207] [Operation 3] Otherwise, the MAC entity starts or restarts the ra-ContentionResolutionTimer within the first codeword after the end of sending the Msg3.

[0208] [Operation 4] The MAC entity monitors the PDCCH regardless of the possibility of a measurement gap occurring while the ra-ContentionResolutionTimer is operating.

[0209] Step 4 (Msg4) of the RA process of Rel.16 NR follows the following Step 4 operations.

[0210] [Step 4 Operation]

[0211] When the UE is not provided with a C-RNTI, based on a PUSCH transmission scheduled by an RAR UL grant, the UE attempts to detect DCI format 1_0 scheduling a PDSCH containing the UE's contention resolution identity, accompanied by a CRC scrambled with the corresponding TCI-RNTI. Upon reception of the PDSCH containing the UE's contention resolution identity, the UE transmits HARQ-ACK information within the PUCCH. The PUCCH transmission occurs within the same active UL BWP as the PUSCH transmission. The minimum time between the last symbol received on the PDSCH and the first symbol transmitted on the corresponding PUCCH containing HARQ-ACK information is equal to N_T,1 [msec]. N_T,1 is the duration of N_T,1 symbols, equivalent to the PDSCH processing time of UE processing capability 1 when additional PDSCH DM-RS is configured. For μ = 0, the UE assumes N_T,1 = 14.

[0212] In case of detecting the DCI format based on a PUSCH transmission scheduled by an RAR UL grant or a corresponding PUSCH retransmission scheduled by DCI format 0_0 with a CRC scrambled by the TC-RNTI provided by the corresponding RAR message, the UE may also assume that the PDCCH carrying the DCI format is the same DM-RS antenna port quasi co-location (QCL) properties as those for the SS / PBCH blocks used in the PRACH association by the UE, regardless of whether the TCI state of the CORESET for the PDCCH accompanied by the DCI format received by the UE is provided to the UE.

[0213] When CA is configured, the first three steps of CBRA can always occur in the PCell during the 4-step RA random access procedure. In this case, contention resolution (step 4) can also be cross-scheduled across the PCell. The three steps of CFRA initiated in the PCell remain in the PCell. To establish the timing advance of the STAG, CFRA in the SCell can also be initiated solely by the gNB. This procedure can also be initiated by the gNB using a PDCCH command (step 0) sent in the scheduling cell of the activated SCell in the STAG. Preamble transmission (step 1) can also be performed in the indicated SCell. RAR (step 2) can also be performed in the PCell. Thus, in existing systems, during the RACH procedure in the Scell, the PDCCH command is sent in the activated Scell.

[0214] (SCell activation / deactivation)

[0215] When one or more SCells are configured in the MAC entity, the network (NW) can activate / deactivate the configured SCells. After the SCell is configured, it remains deactivated as long as the parameter (sCellState) is not set to active by higher layers.

[0216] The configured one or more SCells may be activated / deactivated based on at least one of the following conditions:

[0217] Receive SCell Activation / Deactivation MAC CE.

[0218] Receive the extended SCell Activation / Deactivation MAC CE (SCell Activation / Deactivation MAC CE).

[0219] A timer (sCellDeactivationTimer) is set for each SCell (except for the SCell for which the PUCCH is being configured). If the timer expires, the associated SCell is deactivated.

[0220] sCellState is set for each configured SCell. In this case, the associated SCell is activated based on the SCell configuration.

[0221] When the SCell is deactivated, the UE may also implement / envision the following operations:

[0222] The SRS of the SCell is not sent.

[0223] Do not report the CSI of the SCell.

[0224] UL-SCH is not transmitted in the SCell.

[0225] · RACH is not sent in SCell.

[0226] • PDCCH is not monitored in SCell.

[0227] • The PDCCH for the SCell is not monitored.

[0228] PUCCH is not transmitted in SCell.

[0229] HARQ feedback for MAC Protocol Data Units (PDUs) containing SCell Activation / Deactivation MAC CEs or Enhanced SCell Activation / Deactivation MAC CEs is not affected by the interruption of the PCell / PSCell / PUCCH-SCell caused by SCell activation / deactivation. On the other hand, if an SCell is deactivated, any ongoing random access procedure in the SCell is interrupted.

[0230] (Time between PDCCH command reception and PRACH transmission)

[0231] When the random access procedure is initiated via a PDCCH command, the UE, if requested by higher layers, shall transmit PRACH within the selected PRACH opportunity, as specified in the specification, provided that the time between the last symbol received in the PDCCH command and the first symbol transmitted in the PRACH is greater than or equal to N_(T,2) + Δ_BWPSwitching + Δ_Delay + T_switch [msec] (time condition). Here, N_(T,2) is the duration of N_2 symbols corresponding to the PUSCH preparation time of UE processing capability 1. M corresponds to the SCS setting used for PRACH transmission. For example, μ corresponds to the minimum SCS setting between the subcarrier spacing (SCS) setting in the PDCCH command and the corresponding SCS setting in the PRACH transmission. If the active UL BWP remains unchanged, Δ_BWPSwitching = 0; otherwise, Δ_BWPSwitching is defined in the specification. In FR1, Δ_delay = 0.5 msec, and in FR2, Δ_delay = 0.25 msec. T_switch is the switching gap duration defined by the specification.

[0232] K is provided in UE through CellSpecific_Koffset cell，offset In the case of PRACH opportunity, the PRACH opportunity is in time slot n+2 μ ·K cell，offset Here, n is the same as T TA = 0, the reception of the PDCCH command ends the time slot of the UL BWP of the overlapping PRACH transmission. M corresponds to the SCS setting used for PRACH transmission. When the PDCCH reception for the PDCCH command includes two PDCCH candidates from two search space sets linked based on searchSpaceLinkingId, the final symbol of the PDCCH reception is the final symbol of the subsequent PDCCH candidate. Even if the UE does not need to monitor either of the two PDCCH candidates, the PDCCH reception includes both PDCCH candidates.

[0233] In the case where the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission started by a PDCCH order triggering the CFRA procedure for the SpCell, the UE may also assume that the PDCCH containing DCI format 1_0 and the PDCCH order have the same DM-RS antenna port QCL characteristics.

[0234] When the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission started by a PDDCCH order triggering the CFRA procedure for the SCell, the UE may also assume the DMRS antenna port QCL characteristics of the CORESET associated with the type 1-PDCCH CSS set configured for reception of the PDCCH containing DCI format 1_0.

[0235] Thus, the timing of the PRACH opportunity is related to μ and CellSpecific_Koffset.

[0236] (RACH procedure for non-serving cells used for L1 / L2-centric inter-cell mobility)

[0237] When RRC constructs one or more non-serving cell information for a UE, it may also include RACH configurations for the non-serving cell(s). As examples of supporting RACH for candidate cells triggered by PDCCH orders, the following options 1-3 can be used.

[0238] <Option 1>

[0239] The UE may also determine the cell to which the PDCCH command (or the PRACH transmitted in accordance with the PDCCH command) corresponds based on a specific parameter used in the PDCCH of the PDCCH command. The specific parameter may be, for example, the TCI state.

[0240] For example, if the base station sends a PDCCH command for PRACH, and the PDCCH (or DCI / CORESET) is associated with the TCI state from a non-serving cell, the PRACH requested by the PDCCH command may also correspond to the non-serving cell. In this case, the UE can also control PRACH transmission based on the PRACH configuration of the non-serving cell. The UE can then determine the TA of the non-serving cell based on the DL transmission feedback (e.g., RAR) for the PRACH transmission.

[0241] When the PDCCH (or DCI / CORESET) is associated with the TCI status from the serving cell, the PRACH requested by the PDCCH command may also correspond to the serving cell. In this case, the UE can also control PRACH transmission based on the PRACH configuration of the serving cell. The UE can then determine the TA of the serving cell based on the DL transmission (e.g., RAR) fed back in response to the PRACH transmission.

[0242] <Option 2>

[0243] The UE may also determine the cell corresponding to the PDCCH command (or the PRACH sent according to the PDCCH command) based on the DCI (or CORESET) used in the PDCCH command.

[0244] For example, the DCI used in the PDCCH order may include identification information of the cell to which the PRACH corresponds (e.g., cell index / cell type (e.g., serving cell / non-serving cell)) and notify the UE. In a specific DCI format (e.g., DCI format 1_0) used in the PDCCH order, X reserved bits of the DCI may be used in the cell notification to explicitly indicate the serving cell / non-serving cell to which the PRACH corresponds. The reserved bits may also be the reserved bits included in DCI format 1_0 in existing systems (e.g., Rel. 15 / 16).

[0245] The bit size of X can also be set, determined, or determined based on the number of non-serving cells configured. For example, if one non-serving cell is configured, X can be 1 bit. In this case, '0' can represent a serving cell, and '1' can represent a non-serving cell. The fields used in notification of cell identification information can also use the most significant bit (MSB) or least significant bit (LSB) of the reserved bits.

[0246] Furthermore, when three non-serving cells are configured, X can be 2 bits. To indicate non-serving cells, a multiplied re-indexed non-serving cell index can be applied. The association between cell indices and bit values (or codepoints) can be defined in the specification or configured by higher-layer signaling. For example, codepoint '0' or '00' can represent a serving cell, and the remaining bits can be associated with the order of the configured non-serving cell indices (e.g., ascending / descending order).

[0247] Alternatively, the size of X may be fixed, and the number of bits may not be changed regardless of the number of configured non-serving cells. In this case, unused bits / fields may be configured as reserved bits.

[0248] <Option 3>

[0249] When the preamble index (eg, ra-PreambleIndex) of random access is a specific value (eg, 0-63), a portion of the preamble may be configured / activated through RRC / MAC CE to be associated with a non-serving cell.

[0250] In this case, serving / non-serving cell information can be indicated using a specific field in a specific DCI format (e.g., DCI format 1_0). For example, the specific field can be the random access preamble index field (e.g., the Random Access Preamble Index field). Furthermore, the preamble configuration associated with non-serving cells can be configured to be applied only to PRACH transmissions based on PDCCH commands (or not to be applied to contention-based PRACH transmissions).

[0251] In the case where a preamble associated with a non-serving cell is indicated through DCI, the UE may also perform control according to the RACH configuration of the non-serving cell to perform PRACH transmission with the indicated preamble.

[0252] The UE may also adjust the TA of one or more indicated cells after the PRACH is sent based on the PDCCH command. Information related to the TA may also be received through an acknowledgement signal (eg, RAR) sent in response to the PRACH.

[0253] (RACH process for each TRP in multiple TRPs)

[0254] However, in the RACH process of each TRP (or TRP TA) in multiple TRPs as described above, how to perform the RACH process has not been fully studied.

[0255] For example, it is not clear in which cell the PDCCH command of a candidate cell is sent during the RACH process for the candidate cell triggered by the PDCCH command. Candidate cells are not limited to SpCells / PCells; SCells can also be candidate cells.

[0256] For example, it is unclear how to transmit a PDCCH command in the case of an inactive (deactivated) cell / deactivated candidate cell. In addition, in existing systems, a UE does not monitor the PDCCH in a deactivated cell.

[0257] Furthermore, when a PDCCH command is transmitted in each cell, the UE needs to monitor the PDCCHs of multiple candidate cells (at least regarding the PDCCH command). Consequently, the UE may not know which candidate cell's PDCCH command to monitor.

[0258] The NW can send two PDCCH commands for PRACH to two cells, but the preamble / mask (PRACH mask index) / UL carrier indication is the same (common), so the existing rules are not appropriate (cannot be applied). For example, if a UE has an ongoing random access procedure triggered by a certain PDCCH command, even if it receives another PDCCH command indicating the same random access preamble / PRACH mask index / UL carrier, it will treat the procedure as the same random access procedure as the ongoing procedure and will not reinitialize.

[0259] <Option 1>

[0260] The PDCCH command sent to the UE in a cell #A may also trigger the PRACH in the cell #A. For example, if the NW wants to trigger the RACH in the candidate cell #A, the NW needs to send the PDCCH command in the candidate cell #A.

[0261] In the present disclosure, cells #A and #B are candidate cells, and unless otherwise specified, they can also be any of SpCell / PCell / SCell.

[0262] [Option 1-1]

[0263] The NW may also support PDCCH command transmission / PDCCH monitoring / PRACH transmission in an inactive (deactivated) cell / deactivated candidate cell. In this case, the NW does not need to indicate the candidate cell ID to the UE in order to trigger RACH.

[0264] [Option 1-2]

[0265] The UE may also determine whether it is necessary to monitor the PDCCH / the candidate cells to be monitored based on at least one of the following options.

[0266] [Option 1-2-1]

[0267] The NW can also use RRC / MAC CE to set the candidate cells for each candidate cell / TAG / reference CC / TAG of each TAG that the UE needs to monitor for PDCCH (including at least PDCCH command / DCI format 1_0). The UE can also determine the candidate cells for each candidate cell / TAG / reference CC / TAG of each TAG that it needs to monitor based on RRC / MAC CE. Candidate cells can also include deactivated SCells.

[0268] The UE may monitor PDCCH commands for each candidate cell (including deactivated SCells) / TAG / TAG's reference CC indicated by the NW. The UE may not monitor PDCCH commands for other candidate cells. Here, the reference CC for each TAG may also mean that the NW / UE only needs to obtain the TA based on this reference CC for all cells within the TAG.

[0269] [Option 1-2-2]

[0270] The PDCCH command transmitted to the UE in a certain cell #A may also trigger the PRACH of a cell #B different from the cell #A (details will be described later in the second embodiment).

[0271] [Option 1-2-3]

[0272] The UE may also determine the candidate cells for PDCCH monitoring based on a certain (specific) rule. The specific rule may also be at least one of the following:

[0273] Candidate cells for which L1 beam measurement / reporting is configured,

[0274] Candidate cells that are set to activate TCI state / TRS / CSI measurement / reporting,

[0275] The candidate cell (for each TAG) with the smallest cell ID among the above candidate cells.

[0276] In this case, the UE may determine only one candidate cell for PDCCH monitoring per TAG.

[0277] [change]

[0278] In options 1-1 and 1-2, the UE monitors DCI format 1_0 with a specific DCI format (e.g., a CRC scrambled by the corresponding RA-RNTI / C-RNTI) in the candidate cell (deactivated cell / configured cell). This reduces the number of BDs and the UE load. However, this is not limiting. For example, the UE may monitor any DCI format scrambled by any RNTI.

[0279] Figure 8A and Figure 8B This is a diagram showing an example of the timing of PDCCH monitoring involved in Option 1. The UE can also Figure 8A and Figure 8B The PDCCH command sent in cell #A is received at any timing shown in .

[0280] For example, Figure 8AAs shown, the UE can also receive PDCCH commands at any timing. In this case, even if the SCell is deactivated, the UE always needs to monitor the PDCCH.

[0281] In addition, if Figure 8B As shown, the UE can also receive PDCCH commands at a specific timing. In this case, the UE only needs to monitor the PDCCH for a specific time duration. The monitoring period / non-monitoring period can be predetermined in the specification or set / indicated by RRC / MAC CE / DCI. The specific period can also be any of the following: the same as the DRX period (On duration of DRX), several parts of the DRX period, or a period that includes the DRX period.

[0282] According to option 1, the UE can properly determine in which cell the PDCCH command of the candidate cell is sent during the RACH process.

[0283] <Option 2>

[0284] Option 2 involves the following scenario: a PDCCH command sent to a UE in a cell #A triggers a PRACH in another cell #B that is different from the cell #A. Cells #A and #B may belong to the same MCG / SCG or the same TAG.

[0285] [Option 2-0]

[0286] In this option, the UE triggers RACH based on at least one of the following options.

[0287] [Option 2-0-1]

[0288] Any activated serving cell (cell #A) may also trigger RACH for a candidate cell (cell #B (or other serving cells)).

[0289] [Option 2-0-2]

[0290] Alternatively, only a certain cell #A may trigger RACH to a candidate cell (cell #B) in the SPCell.

[0291] [Option 2-0-3]

[0292] Alternatively, only the (activated) scheduled cell (cell #A) may trigger RACH for the scheduled cell (cell #B) associated with cell #A. The association between cells #A and #B (e.g., based on cross-carrier scheduling) may be configured / indicated by RRC.

[0293] The maximum number of scheduled cells may also be defined for the scheduled cell (cell #A).

[0294] If a new carrier indicator field (CIF) in the PDCCH command is used to indicate the scheduling cell ID, the CIF value used in the PDCCH command for a single scheduled cell (cell #B) can be explicitly set via RRC. Alternatively, the multiple CIF values used in the PDCCH command for multiple scheduled cells can be implicitly determined based on the order of the cell indices / PCIs of the multiple scheduled cells. In the implicit case, for example, a smaller cell index / PCI can be mapped to a smaller CIF value.

[0295] [Option 2-0-4]

[0296] The cell #A capable of triggering RACH (per TAG) can be explicitly or implicitly set via RRC / MAC CE, or predefined in the specification. For example, the cell with the smallest cell ID per TAG / CG (cell group), or the activated cell with the smallest cell ID per TAG / CG (cell group), can be the cell #A (the cell capable of triggering RACH).

[0297] According to embodiment 2-0, the UE does not need to monitor the PDCCH command in the deactivated cell / most cells. In this case, PRACH transmission in the deactivated cell / deactivated candidate cell may also be supported.

[0298] In order to indicate the target cell of the PRACH, the target cell ID / BWP ID / frequency may also be indicated by DCI including the PDCCH command.

[0299] The NW can indicate multiple target cells in the DCI containing the PDCCH command. The UE can also select one cell to trigger the RACH based on the DCI.

[0300] In the present disclosure, the PDCCH command is not limited to DCI format 1_0, and other DCI formats such as DCI formats 1_1, 1_2, and 2_X may also include (apply).

[0301] [Option 2-1]

[0302] When there is an ongoing random access procedure triggered by a certain PDCCH command, even if the UE receives another PDCCH command indicating the same target cell ID / BWP ID / center frequency / random access preamble code / PRACH mask index / UL carrier, it will regard the procedure as the same random access procedure as the ongoing procedure and will not reinitialize.

[0303] According to Option 2, the UE can appropriately determine the triggering of the RACH based on the PDCCH command of the candidate cell based on the new rule.

[0304] (Topic)

[0305] As mentioned above, how to perform the RACH process for each TRP (or TRP TA) in multiple TRPs has not been fully studied. Specifically, the following multiple topics are envisioned.

[0306] <Topic 1>

[0307] For example, when the RACH is triggered for a candidate cell and the PRACH is sent to the candidate cell, it is unclear in which cell the UE monitors the RAR. Furthermore, it is unclear how the QCL concept for the CORESET used to monitor the RAR is implemented. In this case, activated SCells and deactivated (deactivated) SCells can also be used as candidate cells to be monitored.

[0308] <Topic 2>

[0309] For example, it is agreed that, to reduce handover delay / interruption, the UE performs the following process in the candidate cell before receiving the L1 / L2 cell handover command:

[0310] For DL synchronization of candidate cells,

[0311] For TRS tracking of candidate cells,

[0312] · For the CSI acquisition of candidate cells,

[0313] Activation / selection of the TCI status of candidate cells.

[0314] In addition, research is underway to determine whether the above process can be performed even when the candidate cell is a deactivated SCell.

[0315] However, considering scenarios between distributed nodes (Distribution Units: DUs), it's assumed that certain procedures cannot be executed by the UE in a candidate cell before receiving a cell handover command. For example, it's assumed that certain procedures will only be executed by the UE after receiving a cell handover command. In this case, how to notify and control the UE's operations regarding these functions / procedures in the candidate cell is a challenge.

[0316] Therefore, the inventors of the present invention focused on the situation where RACH is triggered, studied the RACH procedure in such a situation, and came up with one aspect of the present embodiment.

[0317] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The wireless communication methods according to the respective embodiments may be applied individually or in combination.

[0318] In the present disclosure, "A / B" and "at least one of A and B" may be replaced with each other. In addition, in the present disclosure, "A / B / C" may also mean "at least one of A, B, and C."

[0319] In the present disclosure, the words “notify,” “activate,” “deactivate,” “indicate,” “select,” “configure,” “update,” and “determine” may be used interchangeably. In the present disclosure, the words “support,” “control,” “controllable,” “operate,” and “operable” may also be used interchangeably.

[0320] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IEs), and settings may also be overwritten. In this disclosure, Medium Access Control (MAC) Control Elements (CEs), update commands, and activation / deactivation commands may also be overwritten.

[0321] In the present disclosure, the higher layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or any one or a combination thereof.

[0322] In the present disclosure, MAC signaling may include, for example, a MAC Control Element (MACCE) and a MAC Protocol Data Unit (PDU). Broadcast information may include, for example, a Master Information Block (MIB), a System Information Block (SIB), minimum system information (Remaining Minimum System Information (RMSI)), and other system information (Other System Information (OSI)).

[0323] In the present disclosure, the physical layer signaling may also be, for example, downlink control information (Downlink Control Information (DCI)), uplink control information (Uplink Control Information (UCI)), etc.

[0324] In the present disclosure, an index, an identifier (ID), an indicator, a resource ID, etc. may also be overwritten with each other. In the present disclosure, a sequence, a list, a set, a group, a group, a cluster, a subset, etc. may also be overwritten with each other.

[0325] In the present disclosure, panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP)), base station, Spatial Relation Information (SRI)), spatial relationship, SRS Resource Indicator (SRI)), Control Resource Set (CORESET)), Physical Downlink Shared Channel (PDSCH)), Codeword (CW), Transport Block (TB), Reference Signal (RS), Antenna Port (e.g., Demodulation Reference Signal (DMRS) port), Antenna Port Group (e.g., DMRS Port Group), Group (e.g., Spatial Relation Group, Code Division Multiplexing (CDM) Group), Reference Signal Group, CORESET Group, Physical Uplink Control Channel (PDSCH) Channel (PUCCH)) group, PUCCH resource group), resources (e.g., reference signal resources, SRS resources), resource sets (e.g., reference signal resource sets), CORESET pool, downlink transmission configuration indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state (unified TCI state), common TCI state (common TCI state), Quasi-Co-Location (QCL)), QCL assumptions, etc. can also be rewritten with each other.

[0326] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and spatial relationship information (TCI state) can also be overwritten. "Spatial relationship information" can also be overwritten with "a set of spatial relationship information," "one or more spatial relationship information," and so on. TCI state and TCI can also be overwritten with each other.

[0327] In the present disclosure, TRP, CORESET pool index (CORESETPoolIndex), TRP ID, ID related to TRP, TAG ID, TCI state group, spatial relationship group, QCL source RS group, DL RS group, path loss RS group, PCI (for multiple TRPs between cells) can also be rewritten with each other.

[0328] In the present disclosure, associations with different TRPs, associations with different CORESET pool indexes (CORESETPoolIndex), associations with different TRP IDs, associations with IDs related to different TRPs, associations with different TAG IDs, associations with groups of different TCI states, associations with groups of different spatial relationships, associations with groups of different QCL source RSs, associations with groups of different DLRSs, associations with groups of different path loss RSs, and associations with different PCIs (for multiple TRPs between cells) can also be rewritten with each other.

[0329] Each embodiment of the present disclosure may also be applied to at least one of intra-cell multi-TRP and inter-cell multi-TRP.

[0330] In the present disclosure, intra-cell multi-TRP may also mean that activated TCI states of multiple (eg, two) TRPs are associated with the same PCI.

[0331] In the present disclosure, inter-cell multi-TRP may also mean that activated TCI states of multiple (eg, two) TRPs are associated with different PCIs.

[0332] In the present disclosure, in the case of inter-cell multi-TRPs, multiple (eg, two) TRPs may also mean multiple (eg, two) TRPs associated with multiple (eg, two) PCIs.

[0333] In the present disclosure, non-serving cell, additional cell, candidate cell, and target cell may be replaced with each other.

[0334] The following embodiments may also be applied to the case where a RACH procedure is configured / supported for each TRP (or each serving cell / supplemented cell / non-serving cell). Alternatively, the following embodiments may also be applied to the case where a timing advance / timing advance group is configured / supported for each TRP (or each serving cell / supplemented cell / non-serving cell).

[0335] (Wireless Communication Method)

[0336] <First embodiment>

[0337] This embodiment relates to Problem 1. This embodiment can also apply at least one of the following aspects. Each aspect can also be applied alone or in combination.

[0338] [Method 1-1]

[0339] The UE may also perform the RACH procedure using existing rules defined for the RACH ordered by the PDCCH in the SCell. As described later, the QCL of the RAR in the SpCell may also be associated with the Type 1-PDCCH CSS set.

[0340] Specifically, when the UE responds to the PRACH transmission started by the PDDCCH command that triggers the CFRA process for the SCell or candidate cell, and performs DCI format 1_0 that is CRC-scrambled by the corresponding RA-RNTI, the UE can also imagine the quasi-co-location characteristics of the DMRS antenna port of the CORESET associated with the type 1-PDCCH CSS set for receiving the PDCCH containing DCI format 1_0.

[0341] This procedure may also be applied only to the RACH ordered by the PDCCH in the candidate cell.

[0342] [Method 1-2]

[0343] The UE may also monitor the RAR in the candidate cell that triggers the RACH and transmits the PRACH. To support this operation, the RRC-based candidate cell configuration may also include a Type 1-PDCCH CSS set configuration for each candidate cell.

[0344] The UE may also assume that the quasi-co-location characteristics of the DMRS antenna ports of the CORESET associated with the Type 1-PDCCH CSS set in the candidate cell are the same as the SSB / CSI-RS resources used by the UE in association with the PRACH in the candidate cell.

[0345] This process can also be applied to the CBRA process for candidate cells, for example, when the UE triggers the CBRA process for the candidate cell. This process can also be applied only to activated / deactivated candidate cells.

[0346] [Methods 1-3]

[0347] The UE may also monitor the RAR in the cell that sends the PDCCH command. In this case, the QCL of the RAR may also be correlated with the QCL of the PDCCH command.

[0348] [Methods 1-4]

[0349] The UE may monitor the RAR in several cells pre-configured for monitoring the RAR. Type 1-PDCCH CSS sets may also be configured for these cells.

[0350] [Methods 1-5]

[0351] The UE may not monitor the RAR.

[0352] For example, after sending a PRACH triggered by a PDCCH order, it is unclear whether the UE knows when (or for which candidate cell) it needs to monitor the RAR, or when it does not need to monitor the RAR (Topic 1-1).

[0353] <Method 1-5-1>

[0354] Whether it is necessary to monitor the RAR for the candidate cell may also be explicitly indicated in the PDCCH command.

[0355] The PDCCH command may also include 1-bit information indicating whether the UE needs to monitor the RAR.

[0356] For example, when RACH for multiple candidate cells is triggered by one PDCCH command, information represented by one bit or separate bits may be used to indicate whether RAR monitoring needs to be performed on the indicated candidate cells.

[0357] The above-mentioned indication for RAR monitoring may be set / indicated for each candidate cell / cell group / TAG via RRC / MAC CE.

[0358] <Method 1-5-2>

[0359] Whether or not to perform RAR monitoring on candidate cells can be predefined in the specification or set through higher layer signaling.

[0360] When the candidate cell is an activated SCell, RAR monitoring may also be required in the candidate cell.

[0361] When the SCell is deactivated, RAR monitoring may be required in the candidate cell. When the SCell is activated, RAR monitoring may not be required in the candidate cell.

[0362] When the candidate cell is not an SCell, RAR monitoring may not be necessary in the candidate cell. When the candidate cell is an SCell, RAR monitoring may be necessary in the candidate cell.

[0363] [Methods 1-6]

[0364] The operation of the UE when the RACH procedure is triggered in a candidate cell and it is indicated / predefined that RAR monitoring is not required in the candidate cell may also be defined as follows.

[0365] The PRACH preamble transmission (PRACH opportunity (RO) and preamble selection) may follow the existing operation or may have the following differences.

[0366] For PREAMBLE_POWER_RAMPING_COUNTER:

[0367] Opt1: Increase by 1 (same as when RAR monitoring is required),

[0368] Opt2: No change.

[0369] Opt3: Set to 0.

[0370] For PREAMBLE_RECEIVED_TARGET_POWER:

[0371] Opt1: Set PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP + POWER_OFFSET_2STEP_RA (same as when RAR monitoring is required),

[0372] Opt2: No power ramp-up.

[0373] Do not launch the RAR window.

[0374] [Methods 1-7]

[0375] PRACH transmission without RAR monitoring may be performed in a manner different from the conventional random access procedure. Conventional specifications (1) and (2) shown below may not be used for PRACH transmission without RAR monitoring.

[0376] Existing specifications in TS38.321

[0377] (1) When a new random access procedure is triggered while another random access procedure is already in progress within the MAC entity, whether to continue the ongoing procedure or start a new procedure (such as SI request) may also depend on the actual installation of the UE.

[0378] (2) If a random access procedure is in progress triggered by a PDCCH command while the UE is receiving another PDCCH command indicating the same random access preamble, PRACH mask index, and UL carrier, the UE shall treat the random access procedure as the same random access procedure as the ongoing procedure and shall not initiate the procedure again.

[0379] In the case where there is an ongoing random access procedure in the MAC entity, if the random access without RAR monitoring is triggered by a PDCCH command, for example, the UE may continue the ongoing procedure and perform PRACH transmission without RAR monitoring.

[0380] When the UE receives a new PDCCH command for sending PRACH immediately after receiving the old PDCCH command for sending PRACH (even before the UE sends PRACH for the old PDCCH command, even if these two PDCCH commands represent the same preamble code, mask index, and UL carrier), the UE can also follow the two PDCCH commands and send two PRACHs based on them.

[0381] According to the first embodiment described above, the UE can appropriately perform the RACH procedure based on the PDCCH command of the candidate cell.

[0382] <Second embodiment>

[0383] This embodiment relates to Problem 2. This embodiment can also apply at least one of the following aspects. Each aspect can also be applied alone or in combination.

[0384] Before receiving the cell handover command, the UE may also be imported with new parameters related to the execution of a specific function / process.

[0385] The new parameter may be a parameter indicating whether a specific function or process can be executed. When the configuration for multiple candidate cells is provided to the UE in RRC signaling, the new parameter may be configured for each candidate cell.

[0386] [Method 2-1]

[0387] For example, a new parameter may indicate whether a specific function or procedure can be executed using a single bit of information (0 or 1) (Option 1). If the new parameter field indicates a "1," the UE may execute the set of predefined or configured functions or procedures before receiving a cell handover command (this may also be considered as executable). Alternatively, if the new parameter field indicates a "0," the UE may not execute the set of predefined or configured functions or procedures before receiving a cell handover command (this may also be considered as incapable of executing the set).

[0388] In addition, in order to represent different sets of functions / processes, other new parameters may also be defined (option 2). In order to define other new parameters (in order to represent different functions / processes), different bits of information are required.

[0389] This new parameter (also referred to as a parameter) can also indicate whether each candidate cell and the current serving cell are located in (or belong to) a distributed node (e.g., a distributed unit (DU)) or a central unit (CU), or in different DUs / CUs. This parameter can indicate to the UE whether or not to perform specific procedures before receiving a cell handover command.

[0390] For example, when the parameter field is set to "0" for the candidate cell, the UE may not assume that the signaling from the NW triggers unexpected functions / processes for the candidate cell, or the UE may ignore triggering these functions / processes even if it receives signaling from the NW.

[0391] For example, the parameter field "0" may indicate (mean) "Do not permit CSI acquisition for candidate cells before receiving a cell handover command." In this case, if the RRC-based CSI measurement configuration includes a candidate cell indicated by the parameter field "0," the UE may ignore CSI measurement / CSI reporting for that candidate cell.

[0392] The predefined / preconfigured functions / processes in each set may also include at least one of the following:

[0393] For DL synchronization of candidate cells,

[0394] For TRS tracking of candidate cells,

[0395] Acquisition of the L1 beam of the candidate cell, or CSI acquisition (measurement results of periodic, semi-persistent, or aperiodic CSI-RS in the candidate cell),

[0396] Activation / selection of the TCI status of candidate cells,

[0397] PRACH transmission in candidate cells,

[0398] SRS transmission in candidate cells,

[0399] Monitoring of PDCCH (corresponding to a specific format or CORESET / SS) in candidate cells.

[0400] As a variation, the RRC / MAC CE may also select at least one of predefined / preconfigured functions / procedures. Furthermore, the DCI / MAC CE may also indicate / initiate whether the selected set of functions / procedures should be applied to each candidate cell. For example, DCI containing a PDCCH command may be used for such indication. Whether the candidate cell is explicitly indicated may be indicated via the RRC / MAC CE / DCI, or may be implicitly associated with the candidate cell for the triggered PRACH.

[0401] [Method 2-2]

[0402] When the UE receives a cell handover command using DCI / MAC CE, a set of predefined / preconfigured functions / procedures / RSs may be triggered or activated for the indicated target cell, which may also be a candidate cell.

[0403] For example, if the cell handover command is for the target cell, the UE may also assume that the function / procedure / RS indicated by field "0" of the new parameter (however, these structures are provided by RRC) is triggered / activated for the target cell. In this case, the function / procedure / RS structure indicated by field "0" of the new parameter may also be provided by RRC.

[0404] When a cell handover command is sent from the NW to the UE, explicit indication of triggering / activating a set of several functions / procedures / RSs may also be included in the cell handover command.

[0405] For example, the latency of data transmission in the target cell after the UE receives the cell handover command is shortened, so the functions / processes required for data transmission need to be executed as early as possible if they were not executed before the cell handover command.

[0406] In order to trigger several functions / processes, the content of the existing MAC CE may also include at least one of the following as a new cell handover command:

[0407] Activation / deactivation of SCell / candidate cells,

[0408] For the non-periodic CSI triggering state of the target cell,

[0409] Activation of the aperiodic CSI-RS / Channel State Information-Interference Measurement (CSI-IM) resource set for the target cell,

[0410] · For the activation of the PDCCH / PDSCH of the target cell using the TCI state,

[0411] Timing Advance Command (TA command) for the target cell.

[0412] In order to trigger several functions / processes, several existing DCI indications may also include at least one of the following as a new cell handover command.

[0413] PDCCH command for triggering RACH for the target cell,

[0414] An indication for triggering aperiodic CSI reporting for the target cell.

[0415] As other new instructions, at least one of the following may also be included:

[0416] In case the CFRA / CBRA PRACH structure is valid, the RACH is triggered by the upper layer,

[0417] Activation of settings related to measurement / reporting of L1 / CSI.

[0418] According to the second embodiment described above, the UE can appropriately control a specific function / procedure in the RACH procedure based on new parameters and the like.

[0419] <Supplement>

[0420] [Notification of information to UE]

[0421] In the above-mentioned embodiment, notification of arbitrary information from the network (NW) (e.g., from a base station (BS)) to the UE (in other words, reception of arbitrary information from the BS in the UE) may also be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signals), or a combination thereof.

[0422] When the notification is performed through a MAC CE, the MAC CE may be identified by including a new logical channel ID (LCID) not specified in existing specifications in the MAC subheader.

[0423] When the above notification is performed through DCI, the above notification may be performed through a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used in scrambling cyclic redundancy check (CRC) bits assigned to the DCI, the format of the DCI, and the like.

[0424] In addition, notification of any information in the above-mentioned embodiments to the UE may be performed periodically, semi-continuously, or aperiodically.

[0425] [Notification of information from UE]

[0426] The notification of arbitrary information from the UE (to the NW) in the above-mentioned embodiment (in other words, the sending / reporting of arbitrary information from the UE to the BS) can also be performed using physical layer signaling (e.g., UCI), high-layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0427] When the above notification is performed through MAC CE, the MAC CE can also be identified by including a new LCID that is not specified in the existing specifications in the MAC subheader.

[0428] When the notification is performed through UCI, the notification may be transmitted using PUCCH or PUSCH.

[0429] Furthermore, the notification of arbitrary information from the UE in the above-mentioned embodiments may be performed periodically, semi-continuously, or aperiodically.

[0430] [Regarding the application of each embodiment]

[0431] At least one of the above embodiments may also be applied when a specific condition is met, which may be specified in the specification or notified to the UE / BS using higher layer signaling / physical layer signaling.

[0432] At least one of the above-mentioned embodiments may also be applied only to a UE that reports a specific UE capability (UE capability) or supports the specific UE capability.

[0433] The specific UE capability may also indicate at least one of the following:

[0434] Supporting specific processing / operation / control / information related to at least one of the above embodiments,

[0435] Supports two TAs for multiple TRPs,

[0436] Support for two TAs for intra-cell multiple TRPs (e.g., intra-cell M-TRP),

[0437] Support for two TAs for inter-cell multi-TRP (e.g., inter-cell M-TRP),

[0438] Support L1 / L2 inter-cell mobility (e.g., L1 / L2 inter-cell mobility),

[0439] Support PDCCH monitoring of candidate cells / deactivated candidate cells / deactivated SCells,

[0440] The maximum number of cells / TAGs / reference CCs supported as targets for PDCCH monitoring,

[0441] Support cross-carrier (cross-CC) PDCCH commands,

[0442] Support monitoring of RAR for candidate cells in candidate cells / SpCell / SCell,

[0443] The maximum number of candidate cells / SpCells / SCells supported as targets for PDCCH monitoring,

[0444] • Before receiving an L1 / L2 cell handover command, support the execution of a specific set of functions / procedures in candidate cells (or deactivated cells), supporting a maximum number of such cells.

[0445] In addition, the above-mentioned specific UE capabilities can be capabilities that are applied across all frequencies (commonly regardless of frequency), or capabilities for each frequency (for example, one or a combination of cells, bands, band combinations, BWPs, component carriers, etc.), or capabilities for each frequency range (for example, Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or capabilities for each subcarrier spacing (SubCarrier Spacing (SCS)), or capabilities for each feature set (Feature Set (FS)) or each feature set (Feature Set Per Component-carrier (FSPC)) of each component carrier.

[0446] Furthermore, the specific UE capability may be a capability applied across all full-duplex modes (commonly regardless of the duplex mode) or a capability for each duplex mode (eg, time division duplex (TDD) or frequency division duplex (FDD)).

[0447] Furthermore, at least one of the aforementioned embodiments may also be applied when specific information associated with the aforementioned embodiment is configured / activated / triggered by the UE through higher layer signaling / physical layer signaling (or operations of the aforementioned embodiment are performed). For example, the specific information may be information indicating activation of 8TX UL transmission, arbitrary RRC parameters for a specific release (e.g., Rel. 18 / 19), etc.

[0448] Even if the UE does not support at least one of the above-mentioned specific UE capabilities or is not configured with the above-mentioned specific information, the UE may apply operations such as Rel.15 / 16.

[0449] (Note)

[0450] The following inventions are added to one embodiment of the present disclosure.

[0451] [Note 1]

[0452] A terminal having:

[0453] a receiving unit, receiving a downlink control channel (PDCCH) command used in triggering a random access procedure from a candidate cell; and

[0454] The control unit determines a cell that sends a random access channel (PRACH) based on the PDCCH command.

[0455] [Note 2]

[0456] The terminal as described in Supplement 1, wherein:

[0457] The receiving unit monitors a random access response in a candidate cell that transmits the random access channel or a cell that transmits the PDCCH command.

[0458] [Note 3]

[0459] The terminal as described in Supplement 1 or Supplement 2, wherein:

[0460] The control unit assumes that the quasi co-location specific reference signal resources associated with the Type 1-PDCCH CSS set in the candidate cell are the same as the reference signal resources used in association with the PRACH.

[0461] [Note 4]

[0462] The terminal according to any one of Supplement 1 to Supplement 3, wherein:

[0463] The PDCCH order includes information on whether monitoring of random access responses to a certain cell is necessary.

[0464] (Note)

[0465] The following inventions are added to one embodiment of the present disclosure.

[0466] [Note 1]

[0467] A terminal having:

[0468] a receiving unit, receiving a handover command of a candidate cell; and

[0469] a control unit, which controls execution of a specific function for the candidate cell before receiving the handover command,

[0470] The control unit executes the specific function based on a parameter indicating whether or not the specific function can be executed.

[0471] [Note 2]

[0472] The terminal as described in Supplement 1, wherein:

[0473] The parameters are set or indicated through higher layer signaling or MAC control elements.

[0474] [Note 3]

[0475] The terminal as described in Supplement 1 or Supplement 2, wherein:

[0476] The specific functions include specific operations pre-defined for the candidate cells.

[0477] [Note 4]

[0478] The terminal according to any one of Supplement 1 to Supplement 3, wherein:

[0479] The handover command of the candidate cell includes information for triggering a specific function for the target cell.

[0480] The control unit performs the specific function based on the information.

[0481] (Wireless Communication System)

[0482] The following describes a configuration of a wireless communication system according to an embodiment of the present disclosure. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above-described embodiments of the present disclosure or a combination thereof.

[0483] Figure 9 This figure shows an example of a schematic configuration of a wireless communication system according to one embodiment. Wireless communication system 1 (may also be simply referred to as system 1) may be a system that implements communication using Long Term Evolution (LTE) standardized by the Third Generation Partnership Project (3GPP) or the fifth-generation mobile communication system New Radio (5G NR).

[0484] In addition, the wireless communication system 1 may also support dual connectivity between multiple radio access technologies (Radio Access Technologies (RATs)) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may also include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and the like.

[0485] In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the Secondary Node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

[0486] The wireless communication system 1 may also support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC)) in which both the MN and the SN are NR base stations (gNB)).

[0487] The wireless communication system 1 may also include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) that are deployed within the macrocell C1 and form small cells C2 that are narrower than the macrocell C1. User terminals 20 may also be located within at least one of the cells. The arrangement and number of cells and user terminals 20 are not limited to those shown in the figure. Hereinafter, when not distinguishing between base stations 11 and 12, they are collectively referred to as base stations 10.

[0488] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CCs) and dual connectivity (DC).

[0489] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). Macrocell C1 may be included in FR1, and small cell C2 may be included in FR2. For example, FR1 may be a frequency band below 6 GHz (sub-6 GHz), and FR2 may be a frequency band higher than 24 GHz (above-24 GHz). The frequency bands and definitions of FR1 and FR2 are not limited to these. For example, FR1 may correspond to a frequency band higher than FR2.

[0490] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

[0491] Multiple base stations 10 may be connected via wired (e.g., optical fiber based on the Common Public Radio Interface (CPRI), an X2 interface, etc.) or wireless (e.g., NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, base station 11, which functions as a host station, may be referred to as an Integrated Access Backhaul (IAB) donor, and base station 12, which functions as a relay station (relay), may be referred to as an IAB node.

[0492] The base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0493] The core network 30 may also include network functions (NFs), such as the User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration, and Maintenance (Management) (OAM). Furthermore, a single network node may provide multiple functions. Furthermore, communication with external networks (e.g., the Internet) may also be conducted via the DN.

[0494] The user terminal 20 may also be a terminal that supports at least one of communication methods such as LTE, LTE-A, and 5G.

[0495] In the wireless communication system 1 , a radio access scheme based on orthogonal frequency division multiplexing (OFDM) may be used. For example, in at least one of the downlink (DL) and uplink (UL), cyclic prefix OFDM (CP-OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), orthogonal frequency division multiple access (OFDMA), or single carrier frequency division multiple access (SC-FDMA) may be used.

[0496] The radio access scheme may also be referred to as a waveform. In addition, in the wireless communication system 1 , other radio access schemes (eg, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

[0497] As downlink channels, the wireless communication system 1 may use a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20 , a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc.

[0498] In addition, as uplink channels, the wireless communication system 1 can also use an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), etc.

[0499] User data, higher-layer control information, and system information blocks (SIBs) are transmitted via the PDSCH. User data and higher-layer control information can also be transmitted via the PUSCH. Furthermore, the Master Information Block (MIB) can also be transmitted via the PBCH.

[0500] Lower layer control information may also be transmitted via the PDCCH. The lower layer control information may include, for example, downlink control information (Downlink Control Information (DCI)) including scheduling information for at least one of the PDSCH and the PUSCH.

[0501] In addition, the DCI that schedules the PDSCH may also be referred to as DL allocation, DL DCI, etc., and the DCI that schedules the PUSCH may also be referred to as UL grant, UL DCI, etc. In addition, the PDSCH may also be rewritten as DL data, and the PUSCH may also be rewritten as UL data.

[0502] PDCCH detection also utilizes control resource sets (CORESETs) and search spaces. A CORESET corresponds to the resources used to search for DCI. A search space corresponds to the search area and search method for PDCCH candidates. A CORESET can be associated with one or more search spaces. Based on the search space configuration, the UE can monitor the CORESETs associated with a particular search space.

[0503] A search space may also correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may also be referred to as a search space set. Furthermore, the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" in this disclosure may be interchangeable.

[0504] The PUCCH can also transmit uplink control information (uplink control information (UCI)) including at least one of channel state information (CSI), delivery confirmation information (e.g., also known as hybrid automatic repeat request ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH can also transmit the random access preamble used to establish a connection with a cell.

[0505] In the present disclosure, downlink, uplink, etc. may be expressed without the word “link.” Furthermore, various channels may be expressed without the word “physical” at the beginning.

[0506] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), and the like may also be transmitted. As DL-RSs, in the wireless communication system 1, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), and a phase tracking reference signal (PTRS) may also be transmitted.

[0507] For example, a synchronization signal may be at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block containing SSs (PSS, SSS) and PBCHs (and DMRS for the PBCH) may also be referred to as an SS / PBCH block or an SS block (SSB). Furthermore, SSs and SSBs may also be referred to as reference signals.

[0508] In addition, wireless communication system 1 may also transmit a sounding reference signal (SRS) or a demodulation reference signal (DMRS) as an uplink reference signal (UL-RS). DMRS is also called a user terminal-specific reference signal (UE-specific Reference Signal).

[0509] (Base Station)

[0510] Figure 10 This figure shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission path interface (transmission line interface) 140. Furthermore, one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140 may be provided.

[0511] In addition, in this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it is also conceivable that the base station 10 also has other functional blocks required for wireless communication. Part of the processing of each unit described below may also be omitted.

[0512] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, a control circuit, and the like that are described based on common knowledge in the technical field to which this disclosure relates.

[0513] The control unit 110 may also control signal generation, scheduling (e.g., resource allocation, mapping), etc. It may also control transmission, reception, and measurement using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140. The control unit 110 may also generate data, control information, sequences, etc. to be transmitted as signals and forward them to the transceiver unit 120. The control unit 110 may also perform call processing (e.g., setup and release) of communication channels, manage the status of the base station 10, and manage radio resources.

[0514] Transmitter / receiver unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. Baseband unit 121 may also include a transmit processing unit 1211 and a receive processing unit 1212. Transmitter / receiver unit 120 may include a transmitter / receiver, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmit / receive circuits, and the like, as described based on common knowledge in the technical fields involved in this disclosure.

[0515] The transmitting and receiving unit 120 may be configured as an integrated transmitting and receiving unit or may be configured as a transmitting unit and a receiving unit. The transmitting unit may also be configured as a transmitting processing unit 1211 and an RF unit 122. The receiving unit may also be configured as a receiving processing unit 1212, an RF unit 122, and a measuring unit 123.

[0516] The transmitting and receiving antenna 130 can be formed of an antenna described based on common knowledge in the technical field to which this disclosure relates, such as an array antenna.

[0517] The transmitting and receiving unit 120 may also transmit the aforementioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 120 may also receive the aforementioned uplink channel, uplink reference signal, etc.

[0518] The transmitting and receiving unit 120 may also use digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), etc. to form at least one of a transmitting beam and a receiving beam.

[0519] The transmitting and receiving unit 120 (transmitting processing unit 1211) may perform processing at the Packet Data Convergence Protocol (PDCP) layer, processing at the Radio Link Control (RLC) layer (e.g., RLC retransmission control), processing at the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), etc. on the data and control information obtained from the control unit 110, to generate a bit string to be transmitted.

[0520] The transmitting and receiving unit 120 (transmitting processing unit 1211) may also perform transmission processing such as channel coding (which may also include error correction coding), modulation, mapping, filter processing (filtering processing), discrete Fourier transform (DFT) processing (as needed), inverse fast Fourier transform (IFFT) processing), precoding, digital-to-analog conversion, etc. on the bit sequence to be transmitted, and output a baseband signal.

[0521] The transmitting and receiving unit 120 (RF unit 122 ) may also perform modulation, filter processing, amplification, etc. on the baseband signal to a radio frequency band, and transmit the signal in the radio frequency band via the transmitting and receiving antenna 130 .

[0522] Meanwhile, the transmitting and receiving unit 120 (RF unit 122 ) may also perform amplification, filter processing (filtering), and demodulation into baseband signals on the radio frequency band signals received via the transmitting and receiving antenna 130 .

[0523] The transmitting and receiving unit 120 (receiving processing unit 1212) may also apply receiving processing such as analog-to-digital conversion, fast Fourier transform (FFT) processing, inverse discrete Fourier transform (IDFT) processing (as needed), filter processing (filtering processing), demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the obtained baseband signal to obtain user data, etc.

[0524] The transmitting / receiving unit 120 (measuring unit 123) may also perform measurements related to received signals. For example, the measuring unit 123 may also perform radio resource management (RRM) measurements and channel state information (CSI) measurements based on the received signals. The measuring unit 123 may also measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), and propagation path information (e.g., CSI). The measurement results may also be output to the control unit 110.

[0525] The transmission path interface 140 can also send and receive signals (return signaling) between the devices included in the core network 30 (for example, the network node providing NF), other base stations 10, etc., and obtain and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0526] In addition, the transmitting unit and the receiving unit of the base station 10 in the present disclosure may also be composed of at least one of the transmitting and receiving unit 120 , the transmitting and receiving antenna 130 , and the transmission path interface 140 .

[0527] In addition, the transmitting and receiving unit 120 may also transmit a downlink control channel (PDCCH) command used to trigger a random access procedure from the candidate cell to the terminal. The transmitting and receiving unit 120 may also transmit a handover command of the candidate cell to the terminal.

[0528] The control unit 110 may determine the cell to which the terminal transmits a random access channel (PRACH) based on the PDCCH command. The control unit 110 may also control the setting of a parameter indicating whether a specific function can be executed in the candidate cell before receiving the handover command.

[0529] (User Terminal)

[0530] Figure 11This figure shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Furthermore, the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may each be provided in one or more units.

[0531] In addition, in this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it is also assumed that the user terminal 20 also has other functional blocks required for wireless communication. Part of the processing of each unit described below may also be omitted.

[0532] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, a control circuit, and the like that are described based on common knowledge in the technical field to which this disclosure relates.

[0533] The control unit 210 may also control signal generation, mapping, etc. The control unit 210 may also control transmission, reception, measurement, etc. using the transmission and reception unit 220 and the transmission and reception antenna 230. The control unit 210 may also generate data, control information, sequences, etc. to be transmitted as signals and forward them to the transmission and reception unit 220.

[0534] The transceiver unit 220 may also include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may also include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may include a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, and the like, which are described based on common knowledge in the technical fields involved in this disclosure.

[0535] The transmitting and receiving unit 220 may be configured as an integrated transmitting and receiving unit or may be composed of a transmitting unit and a receiving unit. The transmitting unit may also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may also be composed of a receiving processing unit 2212, an RF unit 222, and a measuring unit 223.

[0536] The transmitting and receiving antenna 230 can be formed of an antenna described based on common knowledge in the technical field involved in the present disclosure, such as an array antenna.

[0537] The transmitting and receiving unit 220 may also receive the aforementioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 220 may also transmit the aforementioned uplink channel, uplink reference signal, etc.

[0538] The transmitting and receiving unit 220 may also use digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), etc. to form at least one of a transmit beam and a receive beam.

[0539] The transmitting and receiving unit 220 (transmitting processing unit 2211) may also perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on the data and control information obtained from the control unit 210, and generate a bit string to be transmitted.

[0540] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may also include error correction coding), modulation, mapping, filter processing (filtering processing), DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be transmitted, and output a baseband signal.

[0541] Furthermore, whether DFT processing is applied may also be determined based on the transform precoding configuration. For a particular channel (e.g., PUSCH), if transform precoding is enabled, the transceiver unit 220 (transmit processing unit 2211) may perform DFT processing as part of the aforementioned transmit processing in order to transmit the channel using a DFT-s-OFDM waveform. Otherwise, the transceiver unit 220 (transmit processing unit 2211) may perform DFT processing as part of the aforementioned transmit processing.

[0542] The transmitting and receiving unit 220 (RF unit 222 ) may also perform modulation, filter processing (filtering), amplification, etc. on the baseband signal to a radio frequency band, and transmit the signal in the radio frequency band via the transmitting and receiving antenna 230 .

[0543] Meanwhile, the transmitting and receiving unit 220 (RF unit 222 ) may also perform amplification, filter processing (filtering processing), and demodulation into a baseband signal on the radio frequency band signal received via the transmitting and receiving antenna 230 .

[0544] The transmitting and receiving unit 220 (receiving processing unit 2212) may also apply receiving processing such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing (filtering processing), demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the obtained baseband signal, and obtain user data, etc.

[0545] The transmitting / receiving unit 220 (measuring unit 223) may also perform measurements related to received signals. For example, the measuring unit 223 may also perform RRM measurements and CSI measurements based on the received signals. The measuring unit 223 may also measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may also be output to the control unit 210.

[0546] In addition, the transmitting unit and the receiving unit of the user terminal 20 in the present disclosure may also be composed of at least one of the transmitting and receiving unit 220 and the transmitting and receiving antenna 230 .

[0547] Furthermore, the transceiver unit 220 may also receive a downlink control channel (PDCCH) command from a candidate cell, used to trigger a random access procedure. The transceiver unit 220 may also monitor for random access responses in the candidate cell that transmitted the random access channel or the cell that transmitted the PDCCH command. The PDCCH command may also include information regarding the need to monitor random access responses from a particular cell.

[0548] The control unit 210 may also determine the cell that transmits the random access channel (PRACH) based on the PDCCH command. The control unit 210 may also assume that the quasi-co-location specific reference signal resources associated with the type 1-PDCCH CSS set in the candidate cell and the reference signal resources used in the association of the PRACH are the same. The control unit 210 may also control the execution of a specific function for the candidate cell before receiving the handover command. The control unit 210 may also control the execution of the specific function based on a parameter indicating whether the specific function can be executed. The parameter may also be set or indicated by higher-layer signaling or a MAC control element. The specific function may also include a specific operation pre-defined for the candidate cell. The handover command for the candidate cell may also include information for triggering the specific function for the target cell. The control unit 210 may also execute the specific function based on the information for triggering the specific function for the target cell.

[0549] (Hardware structure)

[0550] Furthermore, the block diagrams used in the description of the above embodiments illustrate blocks of functional units. These functional blocks (structural units) are implemented by any combination of at least one of hardware and software. Furthermore, the implementation method of each functional block is not particularly limited. Specifically, each functional block can be implemented using a single device that is physically or logically combined, or by connecting two or more physically or logically separate devices directly or indirectly (e.g., by wired or wireless connections) to implement these multiple devices. A functional block can also be implemented by combining one or more of these devices with software.

[0551] Functions include, but are not limited to, judging, determining, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, regarding, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. For example, a functional block (structural unit) that implements a transmitting function may also be referred to as a transmitting unit, a transmitter, or the like. Any of these functions are as described above, and their implementation methods are not particularly limited.

[0552] For example, a base station, a user terminal, etc. in one embodiment of the present disclosure may also function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 12 This figure shows an example of the hardware configuration of a base station and a user terminal according to one embodiment. The base station 10 and the user terminal 20 described above can also be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

[0553] In this disclosure, the terms "device," "circuit," "equipment," "section," and "unit" are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figures, or may exclude some of the devices.

[0554] For example, although only one processor 1001 is shown, multiple processors may be provided. Furthermore, processing may be performed by a single processor, or by two or more processors simultaneously, sequentially, or using other methods. Furthermore, processor 1001 may be implemented using more than one chip.

[0555] The functions of the base station 10 and the user terminal 20 are realized, for example, by reading specific software (program) into hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations and controls communication via the communication device 1004, or controls at least one of reading and writing data in the memory 1002 and the storage 1003.

[0556] Processor 1001 controls the entire computer by, for example, operating an operating system. Processor 1001 may also be comprised of a central processing unit (CPU) including interfaces with peripheral devices, a control device, a computing device, registers, and the like. For example, at least a portion of the aforementioned control unit 110 (210) and transceiver unit 120 (220) may also be implemented by processor 1001.

[0557] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes based on them. As a program, a program that causes a computer to execute at least a portion of the operations described in the above-described embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and executed by the processor 1001, and the other functional blocks can also be implemented similarly.

[0558] Memory 1002 may also be a computer-readable recording medium, such as at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), or other suitable storage medium. Memory 1002 may also be referred to as a register, a cache, a main memory (main storage device), or the like. Memory 1002 can store executable programs (program code), software modules, and the like for implementing the wireless communication method according to an embodiment of the present disclosure.

[0559] Storage 1003 may also be a computer-readable recording medium, such as at least one of a flexible disk, a floppy disk, an optical disk (such as a compact disk (Compact Disc Read-Only Memory (CD-ROM)), a digital versatile disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (such as a card, a stick, or a key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

[0560] The communication device 1004 is hardware (a transmitting and receiving device) for communicating between computers via at least one of a wired network and a wireless network. For example, it is also referred to as a network device, a network controller, a network card, a communication module, etc. In order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD), the communication device 1004 may also be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the aforementioned transmitting and receiving unit 120 (220) and the transmitting and receiving antenna 130 (230) may also be implemented by the communication device 1004. The transmitting and receiving unit 120 (220) may also be physically or logically separated by a transmitting unit 120a (220a) and a receiving unit 120b (220b).

[0561] The input device 1005 is an input device that receives input from the outside (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to the outside (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). Alternatively, the input device 1005 and output device 1006 may be integrated (e.g., a touch panel).

[0562] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 may be configured as a single bus or may be configured as different buses between the devices.

[0563] Furthermore, the base station 10 and user terminal 20 may also be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and may use this hardware to implement part or all of each functional block. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0564] (Variation)

[0565] In addition, the terms described in this disclosure and the terms required for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be replaced with each other. In addition, a signal may also be a message. A reference signal may also be referred to as RS, or as a pilot, pilot signal, etc. depending on the applied standard. In addition, a component carrier (CC) may also be referred to as a cell, frequency carrier, carrier frequency, etc.

[0566] A radio frame can also be composed of one or more time periods (frames) in the time domain. Each of these one or more time periods (frames) that make up a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (for example, 1ms) that is independent of the numerology.

[0567] Here, a parameter set may also refer to communication parameters applied to at least one of the transmission and reception of a signal or channel. For example, the parameter set may also represent at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), the number of symbols per TTI, radio frame structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, and specific windowing processing performed by the transmitter and receiver in the time domain.

[0568] In the time domain, a slot can also be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) Furthermore, a slot can also be a time unit based on a parameter set.

[0569] A time slot may also contain multiple mini-slots. Each mini-slot may also consist of one or more symbols in the time domain. Furthermore, a mini-slot may also be referred to as a sub-slot. A mini-slot may also consist of fewer symbols than a time slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may also be referred to as PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using mini-slots may also be referred to as PDSCH (PUSCH) mapping type B.

[0570] Radio frames, subframes, time slots, mini-slots, and symbols all represent time units used for signal transmission. Radio frames, subframes, time slots, mini-slots, and symbols may also be referred to by their respective equivalents. Furthermore, the time units of frame, subframe, time slot, mini-slot, and symbol in this disclosure may be interchangeable.

[0571] For example, a subframe can be called a TTI, multiple consecutive subframes can be called a TTI, and a slot or a mini-slot can be called a TTI. That is, at least one of a subframe and a TTI can be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Furthermore, the unit representing a TTI can be called a slot, a mini-slot, or the like, rather than a subframe.

[0572] Here, TTI refers to, for example, the minimum time unit used for scheduling in wireless communications. For example, in the LTE system, a base station schedules each user terminal by allocating radio resources (such as the frequency bandwidth and transmit power available to each user terminal) in TTI units. The definition of TTI is not limited to this.

[0573] A TTI can also be a unit of time for transmitting channel-coded data packets (transport blocks), code blocks, code words, etc., and can also be a unit of processing for scheduling, link adaptation, etc. Furthermore, when a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, code block, code word, etc. is actually mapped can be shorter than the TTI.

[0574] Furthermore, while a time slot or mini-slot is referred to as a TTI, one or more TTIs (i.e., one or more time slots or one or more mini-slots) can also be the minimum time unit for scheduling. Furthermore, the number of time slots (mini-slots) that constitute this minimum time unit for scheduling can also be controlled.

[0575] A TTI with a time length of 1 ms may also be referred to as a normal TTI (TTI in 3GPP Rel. 8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI may also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a minislot, a subslot, a time slot, etc.

[0576] In addition, a long TTI (e.g., normal TTI, subframe, etc.) can also be rewritten as a TTI with a time length exceeding 1ms, and a short TTI (e.g., shortened TTI, etc.) can also be rewritten as a TTI with a TTI length shorter than the long TTI and longer than 1ms.

[0577] A resource block (RB) is a unit of resource allocation in the time and frequency domains. In the frequency domain, it may also include one or more consecutive subcarriers (subcarriers). The number of subcarriers contained in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers contained in an RB can also be determined based on the parameter set.

[0578] In addition, an RB may also include one or more symbols in the time domain, and may also be the length of a slot, a mini-slot, a subframe, or a TTI. A TTI, a subframe, etc. may also be composed of one or more resource blocks.

[0579] In addition, one or more RBs may also be referred to as a physical resource block (Physical RB (PRB)), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0580] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0581] A Bandwidth Part (BWP) (also known as a fractional bandwidth) can also represent a subset of contiguous common resource blocks (RBs) used for a particular parameter set within a carrier. Common RBs can also be identified by their index relative to the common reference point for that carrier. PRBs can also be defined within a BWP and numbered within that BWP.

[0582] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). For a UE, one or more BWPs may be configured within one carrier.

[0583] At least one of the configured BWPs may be activated, and the UE may not assume that it will transmit or receive specific signals / channels other than the activated BWP.

[0584] The above-mentioned structures of radio frames, subframes, slots, mini-slots, and symbols are merely examples. For example, the number of subframes in a radio frame, the number of slots per subframe or radio frame, the number of mini-slots within a slot, the number of symbols and RBs within a slot or mini-slot, the number of subcarriers within an RB, the number of symbols within a TTI, the symbol length, and the cyclic prefix (CP) length can be modified in various ways.

[0585] Furthermore, the information and parameters described in this disclosure may be expressed as absolute values, relative values relative to a specific value, or other corresponding information. For example, wireless resources may be indicated by specific indexes.

[0586] The names used for parameters, etc. in this disclosure are not intended to be limiting in any respect. Furthermore, the mathematical formulas used for these parameters may differ from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any respect.

[0587] Information, signals, and the like described in this disclosure may also be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, and the like that may be referred to throughout the foregoing description may also be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or photons, or any combination thereof.

[0588] Furthermore, information, signals, etc. can be output in at least one of the following directions: from a higher layer (upper layer) to a lower layer (lower layer), and from a lower layer to a higher layer. Information, signals, etc. can also be input and output via multiple network nodes.

[0589] Input and output information, signals, etc. can be stored in a specific location (e.g., memory) or managed using a management table. Input and output information, signals, etc. can be overwritten, updated, or appended. Output information, signals, etc. can also be deleted. Input information, signals, etc. can also be sent to other devices.

[0590] The notification of information is not limited to the methods / implementations described in this disclosure and may also be performed using other methods. For example, the notification of information in this disclosure may also be implemented through physical layer signaling (e.g., downlink control information (Downlink Control Information (DCI)), uplink control information (Uplink Control Information (UCI))), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB)), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0591] Physical layer signaling may also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), Layer 1 control information (L1 control signal), etc. Furthermore, RRC signaling may also be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, MAC signaling may also be notified using, for example, a MAC Control Element (CE).

[0592] Furthermore, notification of specific information (eg, notification of “it is X”) is not limited to explicit notification, but may be performed implicitly (eg, by not notifying the specific information or by notifying other information).

[0593] The determination can be made using a value represented by a bit (0 or 1), a true or false value (Boolean value) represented by true or false, or a numerical comparison (eg, comparison with a specific value).

[0594] The term “software” or “firmware” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, sub-programs, software modules, applications, software applications, software packages, routines, sub-routines, objects, executable files, execution threads, procedures, functions, etc.

[0595] Furthermore, software, instructions, information, and the like may also be transmitted and received via a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using at least one of a wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and a wireless technology (infrared, microwave, etc.), at least one of the wired technology and the wireless technology is included within the definition of a transmission medium.

[0596] The terms "system" and "network" used in this disclosure are interchangeable. "Network" may also refer to devices included in the network (eg, base stations).

[0597] In the present disclosure, terms such as "precoding", "precoder", "weight (precoding weight)", "Quasi-Co-Location (QCL))", "Transmission Configuration Indication state (TCI state)", "spatial relation", "spatial domain filter", "transmit power", "phase rotation", "antenna port", "antenna port group", "layer", "number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angle", "antenna", "antenna element", and "panel" can be used interchangeably.

[0598] In this disclosure, terms such as "base station (BS)", "wireless base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP))", "panel", "cell", "sector", "cell group", "carrier", and "component carrier" are used interchangeably. In some cases, a base station may be referred to as a macrocell, small cell, femtocell, or picocell.

[0599] A base station can accommodate one or more (for example, three) cells. When a base station accommodates multiple cells, the base station's overall coverage area can be divided into multiple smaller areas, each of which can be provided with communications services by a base station subsystem (for example, a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or the entire coverage area of at least one of a base station and a base station subsystem providing communications services within that coverage area.

[0600] In the present disclosure, the base station sends information to the terminal, and this situation can also be rewritten as the base station instructing the terminal to control / operate based on the information.

[0601] In the present disclosure, terms such as “mobile station (MS)”, “user terminal”, “user device (UE)”, and “terminal” can be used interchangeably.

[0602] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, hand set, user agent, mobile client, client, or several other appropriate terms.

[0603] At least one of the base station and the mobile station may also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. In addition, at least one of the base station and the mobile station may also be a device mounted on a moving object, a moving object body, etc.

[0604] The mobile body refers to a movable object, and the moving speed is arbitrary, including the case where the mobile body is stopped. The mobile body includes, for example, vehicles, transport vehicles, cars, automatic two-wheeled vehicles (motorcycles), bicycles, connected cars, loading shovels, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, trolleys, rickshaws, ships (ships and other watercraft), airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, hot air balloons, and objects carried on them, but is not limited to these. In addition, the mobile body can also be a mobile body that moves autonomously based on operating instructions.

[0605] The mobile object may be a vehicle (e.g., a car, an aircraft, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0606] Figure 13 This diagram shows an example of a vehicle according to one embodiment. Vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0607] The drive unit 41 is composed of, for example, at least one of an engine, a motor, or a combination of an engine and a motor. The steering unit 42 is configured to include at least a steering wheel (also referred to as a handle), and steers at least one of the front wheels 46 and the rear wheels 47 based on the user's operation of the steering wheel.

[0608] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and communication ports (e.g., input / output (IO) ports) 63. Signals from various sensors 50-58 included in the vehicle are input to the electronic control unit 49. The electronic control unit 49 may also be referred to as an electronic control unit (ECU).

[0609] As signals from various sensors 50-58, there are current signals from the current sensor 50 that senses the current of the motor, speed signals of the front wheels 46 / rear wheels 47 obtained by the speed sensor 51, air pressure signals of the front wheels 46 / rear wheels 47 obtained by the air pressure sensor 52, vehicle speed signals obtained by the vehicle speed sensor 53, acceleration signals obtained by the acceleration sensor 54, depression amount signals of the accelerator pedal 43 obtained by the accelerator pedal sensor 55, depression amount signals of the brake pedal 44 obtained by the brake pedal sensor 56, operation signals of the shift lever 45 obtained by the shift lever sensor 57, detection signals for detecting obstacles, vehicles, pedestrians, etc. obtained by the object detection sensor 58, etc.

[0610] Information service unit 59 is comprised of various devices, such as a navigation system, audio system, speakers, display, television, and radio, that provide (output) various types of information, including driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. Information service unit 59 uses information acquired from external devices via communication module 60 and the like to provide various information and services (e.g., multimedia information and multimedia services) to vehicle 40 occupants.

[0611] The information service unit 59 may include an input device for accepting input from the outside (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.), or an output device for outputting to the outside (e.g., a display, a speaker, an LED light, a touch panel, etc.).

[0612] The driving assistance system unit 64 is composed of various devices that provide functions for preventing accidents or reducing the driver's driving burden, such as millimeter-wave radar, light detection and ranging (LiDAR), cameras, positioners (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyroscope systems (e.g., inertial measurement units (IMUs)), inertial navigation systems (INS), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. Furthermore, the driving assistance system unit 64 transmits and receives various information via the communication module 60 to implement driving assistance functions or autonomous driving functions.

[0613] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 transmits and receives data (information) via the communication port 63 with the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, the microprocessor 61 in the electronic control unit 49, the memory (ROM, RAM) 62, and various sensors 50-58 included in the vehicle 40.

[0614] The communication module 60 is controlled by the microprocessor 61 of the electronic control unit 49 and is a communication device capable of communicating with external devices. For example, various information can be transmitted and received with the external device via wireless communication. The communication module 60 can be located either inside or outside the electronic control unit 49. Examples of external devices include the aforementioned base station 10 and user terminal 20. Furthermore, the communication module 60 can also be, for example, at least one of the aforementioned base station 10 and user terminal 20 (or function as at least one of the base station 10 and user terminal 20).

[0615] The communication module 60 may also transmit at least one of the following to an external device via wireless communication: signals input to the electronic control unit 49 from the various sensors 50-58, information obtained based on these signals, and information based on external (user) input received via the information service unit 59. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may also be referred to as input units that receive input. For example, the PUSCH transmitted via the communication module 60 may also include information based on these inputs.

[0616] The communication module 60 receives various information (such as traffic information, traffic light information, and vehicle information) transmitted from external devices and displays it on the vehicle's information service unit 59. The information service unit 59 can also be referred to as an output unit that outputs information (for example, information output to a display, speaker, or other device based on the PDSCH received by the communication module 60 (or data / information decoded from the PDSCH)).

[0617] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 can also control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, various sensors 50-58, and the like included in the vehicle 40.

[0618] Furthermore, the base station in this disclosure can also be rewritten as a user terminal. For example, the various methods / implementations of this disclosure can also be applied to a structure in which communication between a base station and a user terminal is replaced by communication between multiple user terminals (e.g., device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, the user terminal 20 can also have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" can also be rewritten with terms corresponding to inter-terminal communication (e.g., "sidelink"). For example, uplink channels, downlink channels, etc. can also be rewritten as sidelink channels.

[0619] Likewise, the user terminal in the present disclosure may be rewritten as a base station. In this case, the base station 10 may have the functions of the user terminal 20 described above.

[0620] In this disclosure, actions performed by a base station may also be performed by its upper node depending on the situation. Obviously, in a network including one or more network nodes including a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (for example, but not limited to, a Mobility Management Entity (MME) and a Serving-Gateway (S-GW)), or a combination thereof.

[0621] The various methods / implementations described in this disclosure may be used individually or in combination, and may be switched between them during execution. Furthermore, the processing procedures, timings, flow charts, and the like of the various methods / implementations described in this disclosure may be reversed as long as they do not conflict. For example, the methods described in this disclosure use an illustrative order to present elements of various steps, but are not limited to the specific order presented.

[0622] The various modes and embodiments described in the present disclosure may also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or a decimal)), Future Radio Access (FRA), New Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), systems utilizing other appropriate wireless communication methods, and next-generation systems based on these that are extended, modified, generated, or specified. Furthermore, multiple systems may be combined for application (for example, LTE or LTE-A combined with 5G).

[0623] The phrase “based on” used in this disclosure does not mean “based only on” unless otherwise specified. In other words, the phrase “based on” means both “based only on” and “based at least on.”

[0624] Any reference to an element using the designations "first," "second," etc., as used in this disclosure, does not necessarily define the quantity or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to a first and a second element does not imply that only two elements may be used or that the first element must in some way take precedence over the second element.

[0625] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may also encompass situations where judging, calculating, computing, processing, deriving, investigating, looking up (e.g., searching a table, database, or other data structure), ascertaining, and the like are considered "determining."

[0626] In addition, “judgment (decision)” may also refer to situations where receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), etc. are regarded as “judgment (decision)”.

[0627] Furthermore, "judgment (decision)" can also refer to situations where resolving, selecting, choosing, establishing, comparing, etc. can be considered "judgment (decision)". In other words, "judgment (decision)" can also refer to situations where certain actions can be considered "judgment (decision)".

[0628] In addition, "judge (decide)" can also be rewritten as "assuming (assuming)", "expecting (expecting)", "considering (considering)" and so on.

[0629] The “maximum transmit power” described in the present disclosure may refer to the maximum value of the transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0630] As used in this disclosure, the terms "connected," "coupled," or all variations thereof, refer to any direct or indirect connection or coupling between two or more elements, including the presence of one or more intermediate elements between the two elements being "connected" or "coupled." The coupling or connection between elements can be physical, logical, or a combination thereof. For example, "connected" can also be rephrased as "accessed."

[0631] In the present disclosure, when two elements are connected, it is possible to consider being "connected" or "combined" to each other using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, light (both visible and invisible) region, etc. as several non-limiting and non-inclusive examples to be "connected" or "combined" to each other.

[0632] In the present disclosure, the term "A is different from B" may also mean "A and B are different from each other." Alternatively, the term may also mean "A and B are each different from C." Terms such as "separate" and "bound" may also be interpreted in the same manner as "different."

[0633] When used in this disclosure, "include," "including," and variations thereof have the same inclusive meaning as the term "comprising." Furthermore, the term "or" used in this disclosure does not mean an exclusive OR.

[0634] In the present disclosure, when an article is added by translation, such as a, an, and the in English, the present disclosure may also include a case where the noun following the article is in a plural form.

[0635] In the present disclosure, "below," "less than," "above," "more than," "equal to," and the like may be replaced with one another. Furthermore, in the present disclosure, expressions meaning "good," "bad," "big," "small," "high," "low," "early," "late," "wide," and "narrow," etc., are not limited to the positive, comparative, and superlative forms, but may be replaced with one another. Furthermore, in the present disclosure, expressions meaning "good," "bad," "big," "small," "high," "low," "early," "late," "wide," and "narrow," etc., with "i" (where i is an arbitrary integer) are not limited to the positive, comparative, and superlative forms, but may be replaced with one another (for example, "highest" and "i-th highest" may be replaced with one another).

[0636] In the present disclosure, “of,” “for,” “regarding,” “related to,” “associated with,” etc. may also be replaced with each other.

[0637] While the invention disclosed herein has been described in detail above, it will be apparent to those skilled in the art that the invention disclosed herein is not limited to the embodiments described herein. The invention disclosed herein can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the claims. Therefore, the description herein is for illustrative purposes only and is not intended to limit the invention disclosed herein in any way.

[0638] This application is based on Japanese Patent Application No. 2022-181916, filed on November 14, 2022, the entire contents of which are incorporated herein by reference.

Claims

1. A terminal comprising: a receiving unit, receiving a handover command of a candidate cell; and a control unit, which controls execution of a specific function for the candidate cell before receiving the handover command, The control unit executes the specific function based on a parameter indicating whether the specific function can be executed.

2. The terminal according to claim 1, wherein: The parameters are set or indicated through higher layer signaling or MAC control elements.

3. The terminal according to claim 1, wherein: The specific functions include specific operations pre-defined for the candidate cells. The terminal according to claim 1 , wherein: The handover command of the candidate cell includes information for triggering a specific function for the target cell. The control unit performs the specific function based on the information.

5. A wireless communication method, which is a wireless communication method of a terminal, comprising: The step of receiving a handover command of a candidate cell; and The step of controlling the execution of a specific function on the candidate cell before receiving the handover command.

6. A base station comprising: a sending unit, sending a handover command of a candidate cell to the terminal; and The control unit controls the setting of a parameter indicating whether a specific function can be executed in the candidate cell before receiving the handover command.

Images