Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure is provided with: a receiving unit which receives a Medium Access Control Control Element (MAC CE) relating to a cell handover; and a control unit that controls the application of setting of at least one of radio link monitoring (RLM), beam failure detection (BFD), and uplink control channel (PUCCH) for a specific cell on the basis of information included in the MAC CE.

Description

Technical Field

[0001] This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems. Background Technology

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was standardized with the aim of achieving higher data rates and lower latency. Furthermore, LTE-Advanced (3GPP Rel. 10-14) was standardized with the aim of further increasing capacity and improving the height of LTE (3GPP Release (Rel.) 8, 9).

[0003] The development of successor systems to LTE is also underway (e.g., also known as the 5th generation mobile communication system (5G), 5G+, the 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.).

[0004] Existing technical documents

[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] The problem that the invention aims to solve

[0008] In future wireless communication systems (e.g., wireless communication systems after Rel.17 / 5G), it is envisioned that communication can be controlled using multiple transmit and receive points (e.g., multiple TRPs (MTRPs)) within the serving cell, or based on multiple inter-cell mobility / intra-cell mobility including non-serving cells.

[0009] However, in existing carrier aggregation (CA) scenarios, different settings may exist in SpCell and SCell. The question here is whether these settings need to be configured for each candidate cell. For example, it is unclear whether or how these settings should be applied when a cell handover command triggers a handover of the SpCell or a cell group. If these are unclear, it is impossible to properly control UE operations corresponding to cell handover, raising concerns about communication quality degradation.

[0010] This disclosure is made in view of the points involved, and one of its purposes is to provide a terminal, wireless communication method, and base station that can communicate appropriately even during cell handover.

[0011] Methods for solving problems

[0012] One aspect of the present disclosure relates to a terminal comprising: a receiving unit that receives a Medium Access Control Control Element (MAC CE) related to cell handover; and a control unit that, based on information contained in the MAC CE, controls the application of settings for at least one of Radio Link Monitoring (RLM), Beam Failure Detection (BFD), and Uplink Control Channel (PUCCH) for a specific cell.

[0013] Invention Effects

[0014] According to one method disclosed herein, communication can be properly maintained even during cell handover. Attached Figure Description

[0015] Figures 1A-1D This is a diagram illustrating an example of multiple TRPs.

[0016] Figure 2A as well as Figure 2B This is a diagram illustrating an example of inter-cell mobility.

[0017] Figure 3A as well as Figure 3BThis diagram illustrates an example of a handover between a serving cell and an additional cell based on L1 / L2 signaling.

[0018] Figure 4 This is a diagram illustrating one example of the setup in Example 1-3 where candidate cells are supported.

[0019] Figures 5A-5C This is a diagram illustrating an example of a candidate cell / candidate cell group handover based on L1 / L2 signaling in configuration examples 1-3 with candidate cell support.

[0020] Figure 6 This is a diagram illustrating the general outline of L1L2-triggered mobility (LTM).

[0021] Figure 7 This is a diagram illustrating a RACH (PDCCH ordered RACH) based on PDCCH indications for a serving cell, with random access response (RAR) monitoring.

[0022] Figure 8 This is a diagram illustrating a RACH (PDCCH ordered RACH) based on PDCCH indications for candidate cells, without Random Access Response (RAR) monitoring.

[0023] Figure 9 This shows a portion of the high-level parameters (e.g., IE RadioLinkMonitoringConfig) used by the UE to configure Radio Link Monitoring (RLM).

[0024] Figure 10 This is a diagram illustrating an example of an existing beam recovery process.

[0025] Figure 11 This shows a portion of the high-level parameters (e.g., IE BeamFailureRecoveryConfig) used by the UE to configure Beam Failure Recovery (BFR).

[0026] Figure 12 This shows a portion of the UE-specific UL BWP settings (such as IE PUCCH-Config) contained in the higher-level parameters (BWP-UplinkDedicated).

[0027] Figure 13This is a diagram illustrating an example of UE operation according to the first embodiment.

[0028] Figure 14 This is a diagram illustrating an example of UE operation according to the second embodiment.

[0029] Figure 15 This is a diagram illustrating an example of UE operation according to the third embodiment.

[0030] Figure 16 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment.

[0031] Figure 17 This is a diagram illustrating an example of the structure of a base station according to one embodiment.

[0032] Figure 18 This is a diagram illustrating an example of the structure of a user terminal according to one embodiment.

[0033] Figure 19 This is a diagram illustrating an example of the hardware structure of a base station and a user terminal according to one embodiment.

[0034] Figure 20 This is a diagram illustrating an example of a vehicle according to one embodiment. Detailed Implementation

[0035] (TCI, Spatial Relations, QCL)

[0036] In NR, research is being conducted on the reception processing (e.g., at least one of receiving, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmitting, mapping, precoding, modulation, and encoding) of at least one of control signals and channels (referred to as signal / channel) in the UE based on the Transmission Configuration Indication state (TCI state).

[0037] TCI states can also represent elements of signals / channels applied to the downlink. Elements equivalent to TCI states applied to signals / channels in the uplink can also be described as spatial relations.

[0038] The so-called TCI status is information related to the quasi-co-location (QCL) of a signal / channel, and can also be referred to as spatial reception parameters, spatial relation information, etc. The TCI status can also be set for the UE on a per-channel or per-signal basis.

[0039] QCL is an indicator that represents the statistical properties of a signal / channel. For example, it can also mean that, given a QCL relationship between a signal / channel and other signals / channels, it can be assumed that at least one of the following is the same (QCL): Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter).

[0040] Additionally, the spatial reception parameters may also correspond to the UE's receive beam (e.g., receive analog beam), and the beam may also be determined based on the spatial QCL. The QCL (or at least one element of the QCL) in this disclosure may also be rewritten as sQCL (spatial QCL).

[0041] A QCL can also be defined with multiple types (QCL types). For example, four QCL types, or types AD, can be set, where the parameters (or parameter sets) that can be assumed to be the same are different. These parameters (also called QCL parameters) are represented as follows:

[0042] • QCL Type A (QCL-A): Doppler shift, Doppler spread, average delay, and delay spread.

[0043] • QCL Type B (QCL-B): Doppler shift and Doppler extension,

[0044] • QCL Type C (QCL-C): Doppler shift and average delay,

[0045] • QCL Type D (QCL-D): Space reception parameters.

[0046] The assumption that a UE envisions a relationship between a Control Resource Set (CORESET), channel, or reference signal and other CORESETs, channels, or reference signals in a specific QCL (e.g., QCL type D) is called a QCL assumption.

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

[0048] The TCI state can also be, for example, information related to the QCL between the target channel (in other words, the reference signal (RS) used by the channel) and other signals (e.g., other RSs). The TCI state can also be set (indicated) by higher-layer signaling, physical-layer signaling, or a combination thereof.

[0049] In addition, the channel / signal that becomes the application object in the TCI state can also be called the target channel / reference signal (target channel / RS), or simply the target, etc. The other signals mentioned above can also be called reference RS, source RS, or simply reference, etc.

[0050] The channel that is set (specified) to TCI state or spatial relationship can be, for example, at least one of the following: downlink shared channel (Physical Downlink Shared Channel (PDSCH))), downlink control channel (Physical Downlink Control Channel (PDCCH))), uplink shared channel (Physical Uplink Shared Channel (PUSCH))), and uplink control channel (Physical Uplink Control Channel (PUCCH))).

[0051] Furthermore, the RS that is related to the channel as QCL can be at least one of the following: a Synchronization Signal Block (SSB), a Channel State Information Reference Signal (CSI-RS), a Measurement Reference Signal (Sounding Reference Signal (SRS)), a Tracking CSI-RS (also known as a Tracking Reference Signal (TRS)), a QCL Detection Reference Signal (also known as a QRS), or a DeModulation Reference Signal (DMRS).

[0052] An SSB is a block of signals that includes at least one Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a broadcast channel (Physical Broadcast Channel (PBCH)). An SSB can also be referred to as an SS / PBCH block.

[0053] The RS of QCL type X in TCI state can also refer to the RS that is in a relationship of QCL type X with a certain channel / signal (DMRS), and this RS can also be called the QCL source of QCL type X in TCI state.

[0054] (Multiple TRPs)

[0055] In NR, research is underway on one or more Transmission / Reception Points (TRPs) (multiple TRPs) using one or more panels (multiple panels) to perform DL transmissions to the UE. Additionally, research is underway on the UE performing UL transmissions to one or more TRPs.

[0056] Furthermore, multiple TRPs can correspond to the same cell identifier (cell Identifier(ID)) or different cell IDs. The cell ID can be either a physical cell ID (e.g., PCI) or a virtual cell ID.

[0057] Figures 1A-1D This is a diagram illustrating an example of a multi-TRP scenario. In these examples, it is assumed that each TRP can transmit four different beams, but it is not limited to this.

[0058] Figure 1A This illustrates an example of a scenario where only one TRP (TRP1 in this example) transmits data to the UE in a multi-TRP configuration (also known as single-mode, single TRP, etc.). In this case, TRP1 transmits both the control signal (PDCCH) and the data signal (PDSCH) to the UE.

[0059] In this disclosure, single TRP mode can also refer to the mode in which multiple TRP (modes) are not set.

[0060] Figure 1BThis illustrates an example of a scenario where only one TRP (TRP1 in this example) in a multi-TRP system sends control signals to the UE, while the multi-TRP system sends data signals (also known as single-master mode). The UE receives each PDSCH sent from the multi-TRP system based on a single downlink control information (DCI).

[0061] Figure 1C This illustrates an example of a multi-TRP (Multi-Terrain Protocol) model where each TRP sends a portion of its control signal to the UE, while the TRP also sends data signals (also known as master-slave mode). Alternatively, TRP1 may send part 1 of its control signal (DCI), and TRP2 may send part 2 of its control signal (DCI). Part 2 of the control signal can also depend on part 1. The UE receives each PDSCH sent from the multi-TRP based on these parts of the DCI.

[0062] Figure 1D This illustrates an example of a scenario where each of the multiple TRPs sends a different control signal to the UE, and the multiple TRPs also send data signals (also known as multi-master mode). Alternatively, a first control signal (DCI) can be sent in TRP1, and a second control signal (DCI) can be sent in TRP2. The UE uses these DCIs to receive the various PDSCHs sent from the multiple TRPs.

[0063] Using a DCI scheduler, such as Figure 1B In the case of multiple PDSCHs from multiple TRPs (also known as multiple PDSCHs), the DCI can also be called a single DCI (S-DCI, single PDCCH). Furthermore, when using multiple DCIs for separate scheduling... Figure 1D In the case of multiple PDSCHs from multiple TRPs, these multiple DCIs can also be referred to as multiple DCIs (M-DCI, multiple PDCCH).

[0064] Different Transport Blocks (TBs) / Code Words (CWs) / different layers can also be sent from different TRPs within a multi-TRP network. Alternatively, the same TB / CW / layer can be sent from different TRPs within a multi-TRP network.

[0065] As a method of multi-TRP transmission, non-coherent joint transmission (NCJT) is being investigated. In NCJT, for example, TRP1 performs modulation mapping on a first codeword and layer mapping, and transmits a first PDSCH using a first precoding on a first number of layers (e.g., 2 layers). Furthermore, TRP2 performs modulation mapping on a second codeword and layer mapping, and transmits a second PDSCH using a second precoding on a second number of layers (e.g., 2 layers).

[0066] Furthermore, multiple PDSCHs undergoing NCJT (multiple PDSCHs) can also be defined as partially or completely overlapping in terms of 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 the first TRP and the second PDSCH from the second TRP can also overlap.

[0067] These first and second PDSCHs can also be conceived as not being in a quasi-co-location (QCL) relationship (not quasi-co-located). The reception of multiple PDSCHs can also be rewritten as the simultaneous reception of PDSCHs that are not of a certain QCL type (e.g., QCL type D).

[0068] Investigating: Supporting PDSCH (Transport Block (TB) or Codeword (CW)) repetition across multiple TRPs in URLLC for multiple TRPs. Investigating: Supporting repetition across multiple TRPs in the frequency domain, layer (spatial) domain, or time domain (URLLC schemes, e.g., schemes 1, 2a, 2b, 3, 4). In scheme 1, multiple PDSCHs from multiple TRPs are space-division multiplexed (SDM). In schemes 2a and 2b, PDSCHs from multiple TRPs are frequency-division multiplexed (FDM). In scheme 2a, for multiple TRPs, the redundancy version (RV) is the same. In scheme 2b, for multiple TRPs, the RV can be the same or different. 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 this multi-TRP scenario, more flexible transmission control is possible when using high-quality channels.

[0070] NCJTs using multiple TRPs / panels may require high rank. To support both ideal and non-ideal backhaul between multiple TRPs, a single DCI (single PDCCH, e.g., ...) can also be supported. Figure 1B ) and multiple DCI (multiple PDCCH, for example, Figure 1D Both of these. For both single DCI and multiple DCI, the maximum number of TRPs can also be 2.

[0071] For single PDCCH designs (primarily for ideal backhaul), TCI extensions are being investigated. 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 in Rel.15.

[0072] Regarding PDCCH / CORESET as specified in Rel.15, a TCI state without a CORESET pool index (CORESETPoolIndex) (also known as TRP Info) is set to a CORESET.

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

[0074] (Inter-segment mobility)

[0075] In NR, research is underway on DL transmission to the UE via one or more Transmission / Reception Points (TRPs) (Multi-TRPs (MTRPs)). Additionally, research is underway on UL transmission to one or more TRPs via the UE.

[0076] Considering a UE receiving channels / signals from multiple cells / TRPs in inter-cell mobility (e.g., L1 / L2 inter-cell mobility) (see reference) Figure 2A B).

[0077] Figure 2AAn example of inter-cell mobility including non-serving cells (e.g., single-TRP inter-cell mobility) is shown. The UE can also be configured with a TRP (or a single TRP) in each cell. Here, a scenario is shown where the UE receives channels / signals from the base station / TRP of cell #1, which becomes the serving cell, and the base station / TRP of cell #3, which is not a serving cell (becoming a non-serving cell). This is equivalent to the UE switching from cell #1 to cell #3 (e.g., fast cell switch).

[0078] In this case, port (e.g., antenna port) / TRP selection can also be performed dynamically. Port (e.g., antenna port) / TRP selection can also be based on the TCI status indicated or updated via DCI / MAC CE. The following illustrates a scenario where different physical cell IDs (e.g., PCIs) are supported for cell #1 and cell #3.

[0079] Figure 2B An example of a multi-TRP scenario (e.g., inter-cell mobility utilizing multiple TRPs) is shown. The UE can also have multiple (e.g., two) TRPs (or different CORESET pool indices) configured in each cell. The UE receiving channels / signals from TRP#1 and TRP#2 is shown here. Furthermore, the case where TRP#1 corresponds to Physical Cell ID (PCI)#1 and TRP#2 corresponds to PCI#2 is shown here.

[0080] Multiple TRPs (TRP #1, #2) can also be connected via ideal / non-ideal backhaul to exchange information, data, etc. It is also possible to send the same or different codewords (CWs) and the same or different layers from each TRP within a multi-TRP network. As one method of multi-TRP transmission, such as... Figure 2B As shown, Non-Coherent Joint Transmission (NCJT) can also be used. This illustrates the case of NCJT being performed between TPRs corresponding to different PCIs. Alternatively, the same serving cell settings can be applied / configured for TRP#1 and TRP#2.

[0081] Multiple PDSCHs undergoing NCJT (multiple PDSCHs) can also be defined as partially or completely overlapping in terms of 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 overlap. The first PDSCH and the second PDSCH can be used for transmission within the same TB or for transmission within different TBs.

[0082] It can also be envisioned that these first PDSCHs and second PDSCHs are not in a quasi-co-location (QCL) relationship (not quasi-co-located). The reception of multiple PDSCHs can also be rewritten as the simultaneous reception of PDSCHs that are not of a certain QCL type (e.g., QCL type D).

[0083] Multiple PDSCHs from multiple TRPs (also known as multiple PDSCHs) can 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 within a multiple TRP. A structure utilizing a single DCI in a multiple TRP can also be called a multiple TRP based on a single DCI (mTRP / MTRP).

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

[0085] Alternatively, it can be envisioned that the UE sends separate CSI reports (CSI reports) related to each different TRP. Such CSI feedback can also be referred to as separate feedback, independent CSI feedback, etc. In this disclosure, "separate" and "independent" can be rewritten interchangeably.

[0086] In inter-cell mobility, consider scenario 1 or scenario 2 below. Additionally, in this disclosure, the serving cell can also be rewritten as the TRP within the serving cell. Layer 1 / Layer 2 (L1 / L2) and the DCI / Medium Access Control Element (MAC CE) can also be rewritten interchangeably. In this disclosure, a PCI that differs from the physical cell ID (Physical Cell Identity (PCI)) of the current serving cell is sometimes abbreviated as "different PCI". Non-serving cells, cells with different PCIs, candidate cells, and additional cells can also be rewritten interchangeably.

[0087] <Scenario 1>

[0088] Scenario 1 corresponds, for example, to inter-cell mobility with multiple TRPs. Alternatively, Scenario 1 can 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) UE receives from the serving cell: the setting of the SSB for beam measurement of the TRP corresponding to a different PCI from the serving cell, and the settings required for using radio resources for data transmission and reception, including resources of different PCIs.

[0090] (2) The UE performs beam measurement for the TRP 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 different PCIs is activated by L1 / L2 signaling from the serving cell.

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

[0093] (5) The UE needs to always cover the serving cell, including in the case of multiple TRPs. Similar to previous systems, the UE needs to use common channels from the serving cell (Broadcast Control Channel (BCCH), Paging Channel (PCH)), etc.

[0094] In Scenario 1, when the UE sends and receives signals with the additional cell / TRP (the TRP corresponding to the PCI of the additional cell), the serving cell (the intended serving cell in the UE) is not changed. That is, handover of the serving cell based on L1 / L2 is not supported. The UE can also have higher-layer parameters associated with the PCI of a non-serving cell set from the serving cell. Scenario 1 can also be applied in Rel. 17, for example.

[0095] Figure 3A This diagram illustrates an example of UE movement in Rel.17. Imagine the UE moving from PCI#1 cell (serving cell) to PCI#3 cell (additional cell) (overlapping with the serving cell). In this case, L1 / L2-based handover of the serving cell is not supported in Rel.17.

[0096] An additional cell is a cell with an additional PCI that differs from the serving cell. The UE can receive / transmit UE-dedicated channels from the additional cell. The UE needs to be within the coverage area of ​​the serving cell to receive UE-shared channels (e.g., system information / paging / short messages). When the UE moves outside the coverage area of ​​the serving cell, a handover (also known as L3 mobility) is required.

[0097] <Scenario 2>

[0098] In Scenario 2, L1 / L2 inter-cell mobility is applied. With L1 / L2 inter-cell mobility, serving cell changes can be performed using functions such as beam control without RRC resetting. In other words, transmission and reception with the additional cell can be performed without handover (or without L3 mobility procedures). Since periods of data communication disruption occur due to the need for RRC reconnection for handover, data communication can continue even during serving cell changes by applying L1 / L2 inter-cell mobility that does not require handover. In Scenario 2, the following process is performed, for example.

[0099] (1) In order to change the beam measurement / serving cell, the UE receives the SSB settings of the cell (additional cell) with different PCI from the serving cell.

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

[0101] (3) The UE can also receive the settings (serving cell settings) of cells with different PCIs through higher-layer signaling (e.g., RRC). That is, it can also make advance settings related to serving cell changes. This setting can be made together with the setting in (1) or separately.

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

[0103] (5) The UE changes its serving cell (the concept of the serving cell) and uses a pre-set UE-specific channel and TCI state to start receiving / transmitting.

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

[0105] Figure 3B This diagram illustrates an example of UE movement in Rel.18. In Rel.18, the serving cell is handed over via L1 / L2. The UE can receive / transmit UE-dedicated channels / common channels between the new serving cell and the new serving cell. The UE can also leave the coverage area of ​​its previous serving cell.

[0106] (Setting up candidate cells)

[0107] In L1 / L2 inter-cell mobility, candidate cells can be set in addition to serving cells. In this disclosure, candidate cells can also be rewritten as target cells, additional cells, or additional PCIs. More than one candidate cell (or candidate cell group) can also be associated separately with each serving cell, and more than one candidate cell (or candidate cell group) can also be associated with multiple serving cells in a common area.

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

[0109] Candidate cells (or candidate cell groups) set by higher-layer parameters can also be activated / deactivated to the UE via MAC CE / DCI.

[0110] As a setting for candidate cells (or their association with serving cells), at least one of the following setting examples 1 to 3 can be applied, for example. Here, an example is shown where SpCell#0, SCell#1, and SCell#2 are set as serving cells, and candidate cells / candidate cell groups are set separately from serving cells. The following setting examples 1 to 3 are examples, and the number of serving cells / candidate cells / candidate cell groups, the association between serving cells and candidate cells, etc., are not limited to these and can be appropriately changed. Alternatively, in addition to setting examples 1 to 3, or in place of setting examples 1 to 3, other setting examples can be supported / applied.

[0111] [Setting Example 1]

[0112] Example 1 specifies that for each serving cell (or, respectively, corresponding to the frequency domain of each serving cell), one or more candidate cells are associated / assigned (refer to...). Figure 4 This section illustrates the association of candidate cells #0-1, #0-2, and #0-3 with SpCell#0 (or the frequency domain corresponding to SpCell#0), candidate cell #1-1 with SCell#1 (or the frequency domain corresponding to SCell#1), and candidate cells #2-1 and #2-2 with SCell#2 (or the frequency domain corresponding to SpCell#2). Information related to this association can also be set / indicated to the UE from the base station via RRC / MAC CE / DCI.

[0113] [Setting Example 2]

[0114] Example 2 describes the association / configuration of candidate cells for MAC entities / MCGs / SCGs (refer to...). Figure 4 Here, the case of candidate cells #3-#8 associated with MAC entities / MCG / SCG is shown. In this case, candidate cells are not associated with each serving cell, but with MAC entities or cell groups (e.g., MCG / SCG). Information related to the candidate cells assigned to each cell can also be set / indicated to the UE from the base station via RRC / MAC CE / DCI.

[0115] [Example 3]

[0116] In Example 3, more than one candidate cell group is set (see Example 3). Figure 4A candidate cell group has more than one candidate cell. Here, the following are examples: candidate cell group #1 with candidate cells #0-#2, candidate cell group #2 with candidate cells #0 and #1, and candidate cell group #3 with candidate cell #0. At least one of the information related to the configured candidate cell group and the information related to the candidate cells contained in each candidate cell group can also be configured / indicated to the UE from the base station via RRC / MACCE / DCI.

[0117] [Service Cell Switching]

[0118] In existing systems (e.g., Rel.17), L1 beam indication (e.g., DCI-based indication of TCI status field) is supported in relation to the TCI status of the additional PCI (or, additional cell).

[0119] Following Rel.18, it is also envisionable to support new L1 / L2 signals (e.g., DCI / MAC CE) for indicating serving cell handover (e.g., serving cell switch). As such an indication, it is envisioned to support at least one of implicit and explicit indications. An implicit indication, for example, could mean that a CORESET is updated to a TCI state associated with an additional PCI via MAC CE. An explicit indication could also mean directly indicating cell handover via DCI / MAC CE.

[0120] For example, in candidate cell configuration example 1, a specific candidate cell can be designated as the serving cell (or, an indication of handover to the serving cell) via L1 / L2 signaling. Figure 5A The diagram illustrates the scenario where candidate cell #0-2 becomes the SpCell of the MCG / SCG (handover between SpCell #0 and candidate cell #0-2) via L1 / L2 signaling. Additionally, it illustrates the scenario where candidate cell #2-1 becomes the SCell of the MCG / SCG (handover between SCell #2 and candidate cell #2-1) via L1 / L2 signaling.

[0121] Alternatively, in Example 2 of the candidate cell configuration, a specific candidate cell can be designated as the serving cell (or, an indication of handover to the serving cell) via L1 / L2 signaling. Figure 5B The diagram illustrates the scenario where candidate cell #4 becomes the SpCell of MCG / SCG (switching between SpCell #0 and candidate cell #4) via L1 / L2 signaling.

[0122] Alternatively, in Example 3 of the candidate cell configuration, a specific candidate cell group (or more than one candidate cell contained in that specific candidate cell group) can be changed / updated to a serving cell group via L1 / L2 signaling. Figure 5C The diagram illustrates a scenario where candidate cell group #1 (or candidate cells #0-#2 within candidate cell group #1) becomes the serving cell group (a handover between the serving cell group and candidate cell group #1) via L1 / L2 signaling. Among the candidate cells (here, candidate cells #0-#2) contained in candidate cell group #1, candidate cells associated with SpCell #0 or candidate cells set to the same frequency domain as SpCell #0 (here, candidate cell #0) can also be designated as the new SpCell. Alternatively, candidate cells that become SpCells can be indicated via L1 / L2 signaling.

[0123] (An overview of L1L2-triggered mobility (LTM))

[0124] After Rel.18, it is envisioned that support will be provided for mobility based on L1 / L2 triggering (L1L2-triggered mobility (LTM)).

[0125] Figure 6 This diagram illustrates an overview of L1L2-triggered mobility (LTM). LTM and L1 / L2 inter-cell mobility can also be overridden. During UE reconfiguration, the UE receives candidate cell configurations from the NW. The candidate cell information may include information related to the target serving cell, or information related to both the target and current serving cells.

[0126] UE reconstruction includes T RRC T proccesing1 / Tproccesing2 T RRC (For example, a maximum of 10ms) is the processing time for RRC reconfiguration (RRC Reconfiguration) to carry candidate cell settings (candidate configurations). proccesing1 / Tproccesing2(For example, the maximum usage time is 20ms for the same FR and 40ms for different FRs) This refers to the time allocated for UE processing before and after the cell handover command. This sometimes includes L2 / 3 reconfiguration, RF retuning, baseband retuning, and security updates if necessary.

[0127] DL synchronization includes T search T Δ T margin T search (For example, 0ms when the cell is known, and a maximum of 60ms when the cell is unknown) is the time required to search for the target cell. Δ This is the time used for fine-grained tracking and acquisition of all timing information. T margin (For example, a maximum of 2ms) is the time used for post-processing of SSB and CSI-RS.

[0128] L1 measurement includes T meas (SMTC cycle (e.g., 20ms)). T meas It is the measurement delay from the appearance of the target to the cell handover command.

[0129] UL synchronization includes T IU T RAR T cmd T IU (For example, a maximum of 15ms) is the indeterminate interruption time when an initial PRACH opportunity (occasion) is obtained in a new cell. T RAR (For example, a maximum of 4ms) is the RAR latency. T cmd (For example, a maximum of 5ms) is the processing time for L1 / L2 commands (HARQ and paging).

[0130] T cmd The T after that first-data It is the time when the UE performs its initial DL reception / UL transmission on the indicator beam of the target cell after RAR.

[0131] Figure 7 This is a diagram representing a RACH (PDCCH ordered RACH) based on PDCCH instructions used for serving cells, with Random Access Response (RAR) monitoring. Additionally, in this disclosure, source cell and source cell group can be interchanged. Furthermore, candidate cell and candidate cell group can also be interchanged.

[0132] The source cell sends candidate cell settings to the UE. Then, the source cell sends a RACH indication (PDCCH order) based on PDCCH (e.g., including DCI format 1_0) to the UE. Additionally, a candidate cell is indicated in this indication because parallel RAR is more complex. Then, for TAG / TA acquisition, the UE sends the PRACH during the RACH process to the candidate cell.

[0133] Next, the source cell sends a RAR (TA Instruction) to the UE. In this case, since only one Common Search Space (CSS) is set, the RAR is monitored on the SpCell (only within the Distributed Unit (DU)). Furthermore, the UE can also transmit and receive within its current serving cell. Then, TA adjustment is performed in the source cell.

[0134] Next, the source cell sends a cell handover command to the UE. At this point, the TA information can be moved from the source cell to the target cell. In this case, after the initial cell handover, it is possible that not all candidate cells have completed UL synchronization. The UE uses the initial TA to perform the initial UL transmission.

[0135] Figure 8 This is a diagram representing a RACH (PDCCH ordered RACH) based on PDCCH indications used for candidate cells, without Random Access Response (RAR) monitoring. For Figure 8 This is only to explain the relationship with Figure 7 The differences. Figure 8 In the example, multiple candidate cells can be indicated in the PDCCH-based RACH indication (PDCCH order). The UE can also send the PRACH during the RACH process to the candidate cells for multiple TAG / TA acquisitions. Furthermore, the source cell does not send the RAR, but sends the TA indication in the cell handover command.

[0136] In this disclosure, a RACH without RAR can also be rewritten with a RACH without RAR monitoring (e.g., RACH without RAR monitoring). A RACH can also be rewritten with a PRACH transmission triggered by a PDCCH command. A RACH / PRACH transmission without RAR monitoring can also be rewritten with a RACH / PRACH transmission that does not require RAR monitoring, or a RACH / PRACH transmission that does not require RAR monitoring.

[0137] Regarding LTM, each candidate cell setting can at least include the high-level parameter CellGroupConfig and the setting ID.

[0138] In LTM, candidate cell settings support delta settings based on baseline settings. Here, regarding delta settings, the UE stores the baseline settings as separate settings. That is, baseline settings can be managed separately. For example, other baseline settings can also be provided for the delta settings of candidate cells.

[0139] A MAC CE containing LTM-related information for cell handover can be used as a trigger for LTM cell handover. LTM cell handover can be monitored by a timer. A MAC CE for cell handover commands can also be used to indicate a connection to a target cell.

[0140] In LTM, the target cell (PCell / SCell) can also be the current SCell / PCell. That is, the current SCell / PCell (serving cell) can also be set as a candidate cell.

[0141] In Rel.18 LTM, SSB-based measurements (e.g., L1-RSRP measurements) are also supported. In this case, it is envisioned that specific configuration parameters are applied / set for candidate cells.

[0142] For example, for intra-frequency measurements (e.g., intra-F measurement), a Physical Cell ID (PCI) or Logical ID, or a time domain (e.g., time domain) can also be set. The PCI or Logical ID can also be the ID defined in Rel. 17 Inter-cell Beam Management (ICBM). The time domain can also be, for example, the SMTC or the periodic and burst-in SSB position (e.g., periodicity and SSB position inburst).

[0143] For inter-frequency measurements (e.g., inter-F measurement), a Physical Cell ID (PCI) or Logical ID, a time domain (e.g., time domain), a frequency domain location (e.g., frequency domain location), and a Subcarrier Spacing (SCS) can also be set. The PCI or Logical ID can also be the ID defined in Rel. 17 Inter-cell Beam Management (ICBM). The time domain can also be, for example, the SMTC or the periodic and burst SSB position (e.g., periodicity and SSB position in burst). The frequency domain position can also be the center frequency (e.g., center frequency).

[0144] In LTM versions after Rel.18, the configuration of each candidate cell can also be provided by specific higher-level parameters. These specific higher-level parameters can be, for example, higher-level parameters related to the cell group configuration (e.g., CellGroupConfig IE).

[0145] (Radio Link Monitoring (RLM))

[0146] In NR, Radio Link Monitoring (RLM) is used.

[0147] In NR, the base station can also use higher-layer signaling to configure the Radio Link Monitoring Reference Signal (RLM-RS) for the UE on a per-BWP basis. The UE can also receive configuration information for the RLM (e.g., the "RadioLinkMonitoringConfig" information element of the RRC) (see reference). Figure 9 ).

[0148] The configuration information used by this RLM can also include failure detection resource configuration information (e.g., the higher-level parameter "failureDetectionResourcesToAddModList"). The failure detection resource configuration information can also include parameters related to RLM-RS (e.g., the higher-level parameter "RadioLinkMonitoringRS").

[0149] Parameters related to RLM-RS may also include: information corresponding to the purpose of the RLM, and indexes corresponding to the resources of the RLM-RS (e.g., the indexes contained in the higher-layer parameter "failureDetectionResources" (RadioLinkMonitoringRS within failureDetectionResourcesToAddModList)). This index can be, for example, an index of the CSI-RS resource settings (e.g., a non-zero power CSI-RS resource ID) or an SS / PBCH block index (SSB index). The purpose information may also indicate beam failure, (cell-level) radio link failure (Radio LinkFailure (RLF)), or both.

[0150] Here, the purpose may, for example, mean determining whether the UE should monitor reference signals associated with beam failure detection in the cell. For example, the network may also set values ​​(parameters) specifically for beam failure in the SCell. Furthermore, in the higher-layer signaling used to configure RLM-RS, in addition to the RLM-RS settings, the BFD-RS settings (described later) may also be included. Moreover, as described later, RLM-RS and BFD-RS can be interchanged.

[0151] The UE can also determine the RLM-RS resource based on the index corresponding to the RLM-RS resource and use the RLM-RS resource to implement RLM.

[0152] In the RLM of Rel.16, the UE follows the procedure below.

[0153] [process]

[0154] If the UE is not provided with RLM-RS (e.g., RadioLinkMonitoringRS for higher-layer parameters) and the UE is provided with a TCI state containing more than one CSI-RS for PDCCH reception, the UE follows procedures 1 to 4 below.

[0155] [[Process 1]]

[0156] If the active TCI state for PDCCH reception contains only one RS, the UE will use the RS provided for the active TCI state for PDCCH reception for RLM.

[0157] [[Process 2]]

[0158] When the active TCI state for PDCCH reception includes two RSs, the UE assumes that one RS has QCL type D, and the UE will use this RS with QCL type D for RLM. The UE does not assume that both RSs have QCL type D.

[0159] [[Process 3]]

[0160] The UE is not requested to use aperiodic or semi-persistent RS for RLM.

[0161] [[Process 4]]

[0162] For L max =4, starting from the minimum monitoring period, the UE sequentially selects the N provided for the active TCI state used for PDCCH reception from multiple CORESETs associated with multiple search space sets. RLM There are 1 RS. When more than 1 CORESET is associated with multiple search space sets with the same monitoring period, the UE determines the order of CORESETs starting from the highest CORESET.

[0163] Here, L max This is the maximum number of SS / PBCH block indices within the cell. The maximum number of SS / PBCH blocks transmitted within a half-frame is L. max .

[0164] In this way, when the UE is not provided with RLM-RS, the UE performs an implicit RLM-RS decision, using the active TCI state for PDCCH reception for RLM. In L max When N=4, the UE first selects N in ascending order of the monitoring period of the search space set, and then in descending order of the CORESET index. RLM RS.

[0165] For the link recovery process and RLM, the UE can be configured with a maximum of N. LR-RLM RLM-RS. From N LR-RLM In each RLM-RS, depending on L max At most N RLM One RLM-RS is used for RLM. In Rel.16, as shown in Figure 1, in L max When N = 4, RLM =2, in L max When N = 8, RLM =4, in L max When N = 64, RLM =8. Additionally, Lmax N RLM and N LR-RLM The correspondence is not limited to this.

[0166] (Beam Failure Detection (BFD) / Beam Failure Recovery (BFR))

[0167] In NR, beamforming is used for communication. For example, the UE and the base station (e.g., gNB (gNodeB)) can use beams used in signal transmission (also known as transmit beams, Tx beams, etc.) and beams used in signal reception (also known as receive beams, Rx beams, etc.).

[0168] Imagine using beamforming; due to susceptibility to interference (hindrance) caused by obstacles, radio link quality may deteriorate. There is a concern that this deterioration in radio link quality could lead to frequent radio link failures (RLFs). If an RLF occurs, the cell needs to be reconnected; therefore, frequent RLFs result in a decrease in system throughput.

[0169] In NR, to suppress RLF (Rapid Regression Failure), a switch to other beams is implemented when the quality of a specific beam deteriorates (also known as Beam Recovery (BR), Beam Failure Recovery (BFR), L1 / L2 (Layer 1 / Layer 2) beam recovery, etc.). Additionally, the BFR process can also be simply referred to as BFR.

[0170] In addition, beam failure (BF) in this disclosure can also be referred to as link failure.

[0171] Figure 10 This is a diagram illustrating an example of an existing (e.g., Rel.15) beam recovery process. The number of beams is an example, and is not limited thereto. In the initial state (step S101), the UE performs a measurement based on the reference signal (RS) resources transmitted using two beams.

[0172] The RS can also be at least one of a Synchronization Signal Block (SSB) and a Channel State Information RS (CSI-RS). Additionally, the SSB can also be referred to as an SS / PBCH (Physical Broadcast Channel) block, etc.

[0173] The RS can also be at least one of the following: Primary SS (PSS), Secondary SS (SSS), Mobility Reference Signal (MRS), a signal contained in the SSB, the SSB, CSI-RS, DeModulation Reference Signal (DMRS), beam-specific signal, etc., or a signal formed by extending or modifying them. The RS measured in step S101 can also be referred to as the RS for beam failure detection (Beam Failure Detection RS (BFD-RS) or the RS used in the beam recovery process (BFR-RS), etc.

[0174] In step S102, the UE cannot detect BFD-RS (or the reception quality of RS is degraded) because the radio waves from the base station are interfered with. Such interference can occur, for example, due to obstacles, fading, or other factors between the UE and the base station.

[0175] The UE detects a beam failure if certain conditions are met. For example, if the BLER (Block Error Rate) is less than a threshold for all configured BFD-RS (BFD-RS resource settings), the UE can also detect a beam failure. If a beam failure is detected, the lower layer (PHY layer) of the UE can also notify (indicate) the higher layer (MAC layer) of the beam failure instance.

[0176] Furthermore, the benchmark (standard) for judgment is not limited to BLER; it can also be the reference signal received power in the physical layer (Layer 1 Reference Signal Received Power (L1-RSRP)). Additionally, beam failure detection can be implemented based on the downlink control channel (Physical Downlink Control Channel (PDCCH)) or on the basis of RS measurement, either in place of RS measurement. It is also expected that BFD-RS and the DMRS of the PDCCH monitored by the UE will be quasi-co-located (QCL).

[0177] Here, QCL refers to an indicator of the statistical properties of a channel. For example, when a signal / channel has a QCL relationship with other signals / channels, it can also mean that among these different signals / channels, it can be assumed that at least one of the following is the same (at least one of them is QCL): Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial RxParameter).

[0178] Additionally, the spatial reception parameters may also correspond to the UE's receive beam (e.g., receive analog beam), and the beam may also be determined based on the spatial QCL. The QCL (or at least one element of the QCL) in this disclosure may also be replaced with sQCL (spatial QCL).

[0179] Information related to BFD-RS (e.g., RS index, resources, quantity, number of ports, precoding, etc.) and information related to beam failure detection (BFD) (e.g., the aforementioned thresholds) can also be set (notified) to the UE using higher-layer signaling. Information related to BFD-RS can also be referred to as information related to BFR resources, etc.

[0180] Upon receiving a beam failure instance notification from the UE's PHY layer, the UE's higher layers (e.g., the MAC layer) may also start a specific timer (also referred to as a beam failure detection timer). After receiving a certain number of beam failure instance notifications (e.g., beamFailureInstanceMaxCount set via RRC) before the timer expires, the UE's MAC layer may also trigger a BFR (e.g., start any of the random access procedures described later).

[0181] Even without notification from the UE or if the base station receives a specific signal from the UE (beam recovery request in step S104), it can still determine that the UE has detected a beam failure.

[0182] In step S103, for beam recovery, the UE begins searching for a new candidate beam for the new communication. The UE can also select a new candidate beam corresponding to a specific RS by measuring that RS. The RS measured in step S103 can also be referred to as a new candidate RS, an RS used for new candidate beam identification (New Candidate Beam Identification RS (NCBI-RS)), a CBI-RS, a CB-RS (Candidate Beam RS), etc. The NCBI-RS can be the same as or different from the BFD-RS. Additionally, the new candidate beam can also be simply referred to as a candidate beam or candidate RS.

[0183] The UE can also select the beam corresponding to an RS that meets specific conditions as a new candidate beam. For example, the UE can also select a new candidate beam based on RSs whose L1-RSRP in the set NCBI-RS exceeds a threshold. Furthermore, the criterion for judgment is not limited to L1-RSRP. L1-RSRP related to SSB can also be called SS-RSRP. L1-RSRP related to CSI-RS can also be called CSI-RSRP.

[0184] Information related to NCBI-RS (e.g., RS resources, quantity, number of ports, precoding, etc.) and information related to New Candidate Beam Identification (NCBI) (e.g., the aforementioned thresholds) can also be set (notified) to the UE using higher-layer signaling. Information related to New Candidate RS (or NCBI-RS) can also be obtained based on information related to BFD-RS. Information related to NCBI-RS can also be referred to as information related to NCBI resources, etc.

[0185] In addition, BFD-RS, NCBI-RS, etc. can also be rewritten as Radio Link Monitoring Reference Signal (RLM-RS).

[0186] In step S104, the UE that has determined the new candidate beam sends a beam recovery request (Beam Failure Recovery reQuest (BFRQ)). The beam recovery request can also be referred to as a beam recovery request signal, beam failure recovery request signal, etc.

[0187] BFRQ can also be transmitted using at least one of the following: the Physical Uplink Control Channel (PUCCH), the Physical Random Access Channel (PRACH), the Physical Uplink Shared Channel (PUSCH), and the configured grant (CG) PUSCH.

[0188] The BFRQ may also include information about the new candidate beam / new candidate RS determined in step S103. Resources used for the BFRQ may also be associated with the new candidate beam. Beam information may also be provided using a beam index (BI), a port index of a specific reference signal, an RS index, a resource index (e.g., a CSI-RS resource indicator (CSI-RS Resource Indicator (CRI)) or an SSB resource indicator (SSBRI)).

[0189] In Rel.15 NR, research is underway on BFR based on the Random Access (RA) procedure, namely CB-BFR (Contention-Based BFR), and BFR based on the Non-Contention-Based BFR procedure, namely CF-BFR (Contention-Free BFR). In CB-BFR and CF-BFR, the UE can also use PRACH resources to transmit preambles (RA preamble, random access channel (also known as Physical Random Access Channel (PRACH)), RACH preamble, etc.) as BFRQs.

[0190] In CB-BFR, the UE can also transmit a preamble randomly selected from one or more preambles. Conversely, in CF-BFR, the UE can also transmit a preamble assigned to it by the base station. In CB-BFR, the base station can also assign the same preamble to multiple UEs. In CF-BFR, the base station can also assign a preamble specifically for each UE.

[0191] Additionally, CB-BFR and CF-BFR can also be referred to as CB PRACH-based BFR (contention-based PRACH-based BFR (CBRA-BFR)) and CF PRACH-based BFR (contention-free PRACH-based BFR (CFRA-BFR)), respectively. CBRA-BFR can also be referred to as BFR using CBRA. CFRA-BFR can also be referred to as BFR using CFRA.

[0192] Regardless of whether it's CB-BFR or CF-BFR, information related to PRACH resources (RA preamble) can be communicated via higher-level signaling (RRC signaling, etc.). For example, this information can include correspondences between detected DL-RS (beams) and PRACH resources, or it can be associated with PRACH resources that differ for each DL-RS.

[0193] In step S105, the base station that detected the BFRQ sends a response signal (also known as a gNB response, etc.) to the BFRQ from the UE. This response signal may also contain reconstruction information for one or more beams (e.g., structural information of DL-RS resources).

[0194] The response signal can also be transmitted, for example, in the UE common search space of the PDCCH. The response signal can also be notified using a PDCCH (DCI) scrambled with a UE identifier (e.g., Cell-Radio RNTI (C-RNTI)). The UE can also determine the transmitted beam and received beam used based on beam reconstruction information.

[0195] The UE can also monitor the response signal based on at least one of the control resource set (CORESET) used by the BFR and the search space set used by the BFR.

[0196] Regarding CB-BFR, if the UE receives a PDCCH corresponding to its own C-RNTI, it can be determined that the contention resolution was successful.

[0197] The processing in step S105 can also be configured to allow the UE to monitor the period during which it receives responses (responses) to the BFRQ from the base station (e.g., gNB). This period can also be referred to as the gNB response window, gNB window, beam recovery request response window, etc. If no gNB response is detected during this window period, the UE can also retransmit the BFRQ.

[0198] In step S106, the UE may also send a message to the base station indicating that beam reconfiguration is complete. This message can be sent via either PUCCH or PUSCH.

[0199] A beam recovery success (BR success) could also indicate that the process has reached step S106. On the other hand, a beam recovery failure (BR failure) could also be equivalent to the BFRQ transmission reaching a certain number of times or the beam-failure-recovery-Timer expiring.

[0200] In Rel.15, the use of random access procedures is supported for beam recovery procedures (e.g., BFRQ notification) for beam failures detected via SpCell (PCell / PSCell). On the other hand, in Rel.16, the use of at least one of the following for beam recovery procedures (e.g., BFRQ notification) for beam failures detected via SCell is supported: PUCCH (e.g., Scheduling Request (SR)) transmission for BFR and MAC CE (e.g., UL-SCH) transmission for BFR.

[0201] For example, the UE can also use two steps based on MAC CE to send information related to beam failure. The information related to beam failure can also include information related to the cell where the beam failure was detected, and information related to new candidate beams (or new candidate RS indexes).

[0202] [Step 1]

[0203] If a beam failure is detected, a PUCCH-BFR (Schedule Request (SR)) can be sent from the UE to the PCell / PSCell. Then, a UL clearance (DCI) for step 2 below can be sent from the PCell / PSCell to the UE. If a beam failure is detected, and a MAC CE (or UL-SCH) for sending information related to a new candidate beam is available, step 1 (e.g., PUCCH transmission) can be omitted, and step 2 (e.g., MAC CE transmission) can be performed instead.

[0204] [Step 2]

[0205] Next, the UE can also use MAC CE to send information related to the cell where the beam failure was detected (e.g., cell index) and information related to the new candidate beam to the base station (PCell / PSCell) via the uplink channel (e.g., PUSCH). Subsequently, after the BFR process, a specific period (e.g., 28 symbols) from receiving the acknowledgment signal from the base station, the QCL of the PDCCH / PUCCH / PDSCH / PUSCH can be updated to the new beam.

[0206] Furthermore, the numbering of these steps is merely for illustrative purposes; multiple steps can be summarized or their order rearranged. Additionally, whether or not BFR is implemented can be configured to the UE using higher-layer signaling.

[0207] Figure 11 This diagram illustrates an example of the BeamFailureRecoveryConfig settings assigned to the UE's BFR. For instance, the aforementioned BFD / BFR can be configured in both SpCell and SCell. In this case, additional settings can be included for SpCell. For example... Figure 11 As shown, the higher-layer signaling used for BFR configuration can include spCell-BFR-CBRA-r16 as a configuration for SpCell. This parameter can instruct the UE to be configured to send BFR MAC CE for SpCell. That is, the BFD / BFR configuration for SpCell can be different from the BFD / BFR configuration for SCell (they can be configured separately).

[0208] (BFD-RS)

[0209] In Rel.16, for each BWP of a serving cell, the UE can be provided with a set q0 of periodic (P)-CSI-RS resource setting index through failure detection resources (failureDetectionResources, failureDetectionResourcesToAddModList, RadioLinkMonitoringConfig), and can be provided with at least one set q1 of P-CSI-RS resource setting index and SS / PBCH block index through candidate beam RS list (candidateBeamRSList), extended candidate beam RS list (candidateBeamRSListExt-r16), or SCell candidate beam RS list (candidateBeamRSSCellList-r16).

[0210] Here, "q0bar" is an overlined representation of "q0". From now on, "q0bar" will be simply referred to as "q0". "q1bar" is an overlined representation of "q1". From now on, "q1bar" will be simply referred to as "q1".

[0211] The set q0 of P-CSI-RS resources provided by failure detection resources can also be called explicit BFD-RS.

[0212] The UE can also use RS resources corresponding to the indexes contained in at least one set of set q0 and set q1 to perform L1-RSRP measurements, etc., to detect beam failure.

[0213] Furthermore, in this disclosure, the aforementioned high-level parameters, which provide information representing the index corresponding to the BFD resource, can also be interchanged with the configured BFD resource, configured BFD-RS, etc. In this disclosure, the set q0 of the BFD resource, the periodic CSI-RS resource setting index, or the SSB index, the BFD-RS, the BFD-RS set, and the RS set can also be interchanged.

[0214] If a UE does not have a failure detection resource (q0) provided for a BWP of its serving cell, it decides to include a P-CSI-RS resource setting index in set q0. This P-CSI-RS resource setting index has the same value as the RS index within the RS set indicated by the TCI state, where the TCI state is the TCI state corresponding to the CORESET used by the UE for PDCCH monitoring. If two RS indices exist within a TCI state, set q0 includes the RS index with QCL type D setting for the corresponding TCI state. The UE assumes that set q0 contains at most two RS indices. The UE assumes a single-port RS within set q0.

[0215] The set q0 can also be called implicit BFD-RS (e.g., implicit BFD-RS).

[0216] In this way, the UE uses the TCI state via the PDCCH to determine the reference signal (BFD-RS (RS set)) used for the beam failure detection / beam recovery process. The UE assumes that the RS set contains a maximum of 2 RSs.

[0217] (PUCCH settings for SpCell and SCell)

[0218] The UE can also be configured with parameters for PUCCH transmission (PUCCH configuration information, i.e., PUCCH-Config). Figure 12 This shows a portion of the UE-specific UL BWP settings (such as IE PUCCH-Config) contained in the higher-level parameters (BWP-UplinkDedicated).

[0219] This parameter indicates the PUCCH setting corresponding to one BWP of the serving cell's normal UL (normal UL) / Supplemental UL (SUL). If the UE is configured with SUL, the network can set the PUCCH only on one of the BWPs of the UL (normal UL / SUL).

[0220] The network can configure PUCCH-Config in at least the non-initial BWP of the SpCell and all BPWs of the PUCCH SCell. With UE support, the network can also configure a maximum of one additional SCell (i.e., PUCCHSCell) as the cell group accompanying the PUCCH-Config. That is, an SpCell can be configured along with (via) PUCCH-Config, and the maximum number of SCells (PUCCH SCells) that can be configured along with (via) PUCCH-Config is one.

[0221] (analyze)

[0222] As mentioned above, the necessity of IE CellGroupConfig is being studied in the candidate cell configuration of LTM. Furthermore, in the future, it will be necessary to support continuous L1 / L2 cell handover (changes) between candidate cells without accompanying RRC reconfiguration.

[0223] In L1 / L2 inter-cell mobility, the PCell / SCell targeted for handover can be the current SCell / PCell. That is, the current SCell / PCell can be set as a candidate.

[0224] Furthermore, in order to form a complete candidate configuration, the candidate delta configuration can be applied on top of the reference configuration. Additionally, the timing of the application can be, for example, during or before cell handover.

[0225] The complete candidate settings can also be applied to replace the current UE settings (during resetting / cell handover). This application can also be performed via the RRC resetting procedure, in which the settings are replaced, but the RLC / PDCP is not necessarily reset.

[0226] However, in existing carrier aggregation (CA) scenarios, different settings may exist in SpCell and SCell. For example, the following settings are given.

[0227] • SpCell's RLM / RLF settings only

[0228] • BFD / BFR settings for SpCell only and BFD / BFR settings for SCell only (i.e., the BFD / BFR settings are different in SpCell and SCell).

[0229] • Setting of PUCCH SCell (SCell set along with PUCCH via PUCCH-Config).

[0230] The issue here is whether the aforementioned settings need to be applied to each candidate cell. For example, it is unclear whether or how to apply these settings when a cell handover command triggers a handover of the SpCell or a cell group. If these are unclear, it is impossible to properly control the UE operations corresponding to cell handover, raising concerns about communication quality degradation.

[0231] Therefore, the inventors of this invention, considering various settings (related to RLM / BFR / PUCCH) corresponding to the type of candidate cell during cell handover, conceived of one embodiment of this invention.

[0232] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The wireless communication methods involved in each embodiment can be applied individually or in combination.

[0233] (Various rewrites, etc.)

[0234] In this disclosure, "A / B" and "at least one of A and B" may be rewritten as each other. In addition, in this disclosure, "A / B / C" may also mean "at least one of A, B and C".

[0235] In this disclosure, the terms "activate," "deactivate," "indicate," "select," "configure," "update," and "determine" can be overridden. Similarly, the terms "support," "control," "capable of control," "operate," and "capable of operation" can also be overridden.

[0236] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-level parameters, information elements (IEs), settings, etc., can also be modified interchangeably. In this disclosure, Medium Access Control (MAC) control elements (MAC control elements (CEs), update commands, activation / deactivation commands, etc., can also be modified interchangeably.

[0237] Higher-layer signaling can also be any one or a combination of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., positioning protocol messages from the core network, such as NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP) messages), etc.

[0238] In this disclosure, MAC signaling may also use, for example, a MAC Control Element (MACCE) or a MAC Protocol Data Unit (PDU). Broadcast information may also be, for example, a Master Information Block (MIB), a System Information Block (SIB), a Minimum System Information (Remaining Minimum System Information (RMSI)), or Other System Information (OSI).

[0239] In this disclosure, physical layer signaling may also be, for example, downlink control information (DCI), uplink control information (UCI), etc.

[0240] In the following implementations, "multiple" and "2" can be interchanged. Furthermore, "TAG" and "TAG ID" can also be interchanged. Additionally, "cell," "CC," and "carrier" can also be interchanged. In the following implementations, "calculate," "derive," and "obtain" can also be interchanged.

[0241] In this disclosure, indexes, identifiers (IDs), indicators, resource IDs, etc., can also be overridden with each other. In this disclosure, sequences, lists, sets, groups, clusters, subsets, etc., can also be overridden with each other.

[0242] In this disclosure, the following terms are used: panel, UE panel, panel group, beam, beam group, precoder, uplink (UL) transmitting entity, transmission / reception point (TRP), base station, spatial relation information (SRI), spatial relation, 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). Channel (PUCCH) groups, PUCCH resource groups, resources (e.g., reference signal resources, SRS resources), resource sets (e.g., reference signal resource sets), CORESET pools, downlink transmission configuration indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, quasi-co-location (QCL) and QCL concept can also be rewritten.

[0243] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) can be interchanged. "Spatial relationship information" can also be interchanged with "a set of spatial relationship information," "one or more spatial relationship information," etc. The TCI state and TCI can also be interchanged.

[0244] Furthermore, panel identifiers (IDs) and panels can be interchanged. That is, TRP IDs and TRPs, CORESET group IDs and CORESET groups, etc., can also be interchanged.

[0245] In this disclosure, the TRP, the transmitting point, the panel, the DMRS port group, the CORESET pool, and one of the two TCI states associated with a code point in the TCI field can also be overwritten.

[0246] In this disclosure, the transmission / reception of a channel / signal using a single TRP can also be rewritten as follows: the TCI states (joint / independent / indicating TCI states) are equal in the transmission / reception of the channel / signal (e.g., NCJT / CJT / repeated), or the number of TCI states (joint / independent / indicating TCI states) in the transmission / reception of the channel / signal (e.g., NCJT / CJT / repeated) is 1.

[0247] The transmission / reception of a channel / signal using a single TRP can also be rewritten as follows: the TCI states (joint / independent / indicator TCI states) are different in the transmission / reception of the channel / signal (e.g., NCJT / CJT / repeated), or the number of different TCI states (joint / independent / indicator TCI states) in the transmission / reception of the channel / signal (e.g., NCJT / CJT / repeated) is multiple (e.g., 2).

[0248] In this disclosure, a single TRP, a single TRP system, a single TRP transmission, and a single PDSCH can also be rewritten. In this disclosure, multiple TRPs, multiple TRP systems, multiple TRP transmissions, and multiple PDSCHs can also be rewritten.

[0249] In this disclosure, a single DCI, a single PDCCH, multiple TRPs based on a single DCI, two TCI states activated on at least one TCI code point, at least one code point of a TCI field mapped to two TCI states, and specific indexes set for a specific channel / CORESET (e.g., TRP index, CORESET pool index, or index corresponding to a TRP) can also be overridden.

[0250] In this disclosure, a single TRP, a channel / signal using a single TRP, a channel using one TCI state / spatial relationship, multiple TRPs not activated by RRC / DCI, multiple TCI states / spatial relationships not activated by RRC / DCI, and a CORESET pool index (CORESETPoolIndex) value not set to 1 for any CORESET and no code point in the TCI field being mapped to two TCI states can also be mutually rewritten.

[0251] In this disclosure, multiple TRPs, channels / signals using multiple TRPs, channels using multiple TCI state / spatial relationships, multiple TRPs activated by RRC / DCI, multiple TCI state / spatial relationships activated by RRC / DCI, and at least one of multiple TRPs based on a single DCI and multiple TRPs based on multiple DCIs can also be rewritten to each other.

[0252] In this disclosure, multiple TRPs based on multiple DCIs, a CORESET pool index (CORESETPoolIndex) value set to 1 for a CORESET, and multiple specific indices (e.g., TRP index, CORESET pool index, or index corresponding to a TRP) set for a specific channel / CORESET can also be rewritten to each other.

[0253] In this disclosure, TRP#1 (first TRP) can correspond to either CORESET pool index = 0 or the first TCI state out of two TCI states corresponding to one code point of the TCI field. TRP#2 (second TRP) can correspond to either CORESET pool index = 1 or the second TCI state out of two TCI states corresponding to one code point of the TCI field.

[0254] In this disclosure, a single DCI (sDCI), a single PDCCH, a multi-TRP system based on a single DCI, an MTRP based on sDCI, and two TCI states on a TCI code point that are activated can also be rewritten to each other.

[0255] In this disclosure, multiple DCI (mDCI), multiple PDCCH, multiple TRP systems based on multiple DCI, MTRP based on mDCI, and systems with two CORESET pool indices or CORESET pool index = 1 (or a value greater than 1) can also be overridden with each other.

[0256] In this disclosure, the terms "channel," "signal," and "channel / signal" can be interchanged. Similarly, the terms "DL channel," "DL signal," "DL signal / channel," "DL signal / channel transmission / reception," "DL reception," and "DL transmission" can also be interchanged. Furthermore, the terms "UL channel," "UL signal," "UL signal / channel," "UL signal / channel transmission / reception," "UL reception," and "UL transmission" can also be interchanged.

[0257] In this disclosure, applying the TCI state / QCL concept to each channel / signal / resource can also mean applying the TCI state / QCL concept to the transmission and reception of each channel / signal / resource.

[0258] In this disclosure, the first TCI state (the first indicated TCI state) may also correspond to the first TRP. In this disclosure, the second TCI state (the second indicated TCI state) may also correspond to the second TRP. In this disclosure, the nth TCI state (the nth indicated TCI state) may also correspond to the nth TRP.

[0259] In this disclosure, the value of the first CORESET pool index (e.g., 0), the value of the first TRP index (e.g., 1), and the first TCI state (first DL / UL (joint / independent) TCI state) may also correspond to each other. In this disclosure, the value of the second CORESET pool index (e.g., 1), the value of the second TRP index (e.g., 2), and the second TCI state (second DL / UL (joint / independent) TCI state) may also correspond to each other.

[0260] Furthermore, in the various embodiments of this disclosure described below, the application of multiple TCI states in the transmission and reception of multiple TRPs is mainly described in the case of two TRPs (i.e., at least one of N and M is 2). However, the number of TRPs can be three or more, and the various embodiments can be applied in a manner corresponding to the number of TRPs. In other words, at least one of N and M can also be a number greater than 2.

[0261] In this disclosure, the combined TCI status, DL / UL TCI status, independent TCI status, and independent DL / UL TCI status can be overridden with each other. Furthermore, the indication of the combined TCI status, the indication of the DL / UL TCI status, and the indication of the TCI status can also be overridden with each other.

[0262] In this disclosure, multiple TCI states set via RRC IE, multiple TCI states activated via MAC CE, information related to one or more TCI states, TCI state settings, TCI state pools, activated TCI state pools, common TCI state pools, unified TCI state pools, TCI state lists, unified TCI state lists, joint TCI state pools, independent TCI state pools, independent DL / UL TCI state pools, DL TCI state pools, UL TCI state pools, and independent DL TCI state pools and independent UL TCI state pools can also be overwritten with each other.

[0263] In this disclosure, TRP, CORESET Pool Index, TRP ID, ID associated with TRP, TAG ID, TCI status group, spatial relationship group, QCL source RS group, DL RS group, path loss RS group, and PCI (used for multiple TRPs in inter-cell intervals) can also be rewritten.

[0264] In this disclosure, associations with different TRPs, different CORESET PoolIndex, different TRP IDs, different TRP-related IDs, different TAG IDs, different TCI state groups, different spatial relationship groups, different QCL source RS groups, different DL RS groups, different path loss RS groups, and different PCIs (used for multiple TRPs in inter-cell communication) can also be rewritten.

[0265] The embodiments disclosed herein can also be applied to at least one of intra-cell multi-TRP and inter-cell multi-TRP.

[0266] In this disclosure, intra-cell multiple TRPs may also mean that multiple (e.g., 2) TRPs have activated TCI states (activated TCI states) associated with the same PCI.

[0267] In this disclosure, inter-cell multiple TRPs may also refer to multiple (e.g., 2) TRPs whose activated TCI states are associated with different PCIs.

[0268] In this disclosure, in the case of multiple TRPs in an inter-cell, multiple (e.g., 2) TRPs can also refer to multiple (e.g., 2) TRPs associated with multiple (e.g., 2) PCIs.

[0269] In this disclosure, non-serving cells, additional cells, candidate cells, and target cells can be interchanged.

[0270] In this disclosure, the reference cell can also be rewritten as a reference cell, a specific cell, or a reference cell. The reference cell can be, for example, a specific cell or a cell that indicates / has obtained a TA value. The reference cell can be defined in the specification or set / indicated to the UE from the base station via RRC / MAC CE / DCI.

[0271] In this disclosure, the baseline TRP may also be rewritten as a reference TRP, a specific TRP, or a reference TRP.

[0272] In this disclosure, the RLM settings, BFD settings, PUCCH settings, and reference settings can also be overwritten.

[0273] In this disclosure, cell handover commands (L1 / L2 signals (e.g., DCI / MAC CE)), cell handover indication information, and information related to cell handover can also be rewritten.

[0274] The following implementation methods can also be applied to situations where RACH procedures are configured / supported for each TRP (or each serving cell / additional cell / non-serving cell). Alternatively, the following implementation methods can also be applied to situations where timing advance / timing advance groups are configured / supported for each TRP (or each serving cell / additional cell / non-serving cell).

[0275] The following description can be applied to inter-cell mobility (e.g., L1 / L2 inter-cell mobility) as well as to communication control outside of inter-cell mobility (e.g., intra-cell mobility). L1 / L2 inter-cell mobility can also be rewritten as at least one of cell handover, cell switch, and cell change.

[0276] (Wireless communication method)

[0277] <First Implementation>

[0278] The first implementation involves RLM settings. Figure 13 This is a diagram illustrating an example of UE operation according to the first embodiment.

[0279] <Option 1>

[0280] Each candidate cell can be configured along with (via) RLM settings. That is, RLM settings can also be configured for each candidate cell. RLM settings can also be included in the higher-layer parameters (IECellGroupConfig) used for configuring each LTM candidate cell.

[0281] When a cell handover command (MAC CE) is sent for a SpCell handover (e.g., when indicating the SpCell as a target candidate cell), the target candidate cell becomes the new SpCell, and the UE applies its RLM settings. That is, upon receiving a cell handover command (MAC CE) for an SpCell, the UE can apply the RLM settings corresponding to that SpCell as the target candidate cell (see [reference]). Figure 13 ).

[0282] When a MAC CE (Mobile Cell Handover Command) is sent for cell group handover (e.g., indicating SpCell and SCell as target candidates), the UE can apply the new RLM settings for SpCell and ignore the new RLM settings for SCell. That is, upon receiving a MAC CE for cell group handover, the UE can also apply only the RLM settings for SpCell (see [reference]). Figure 13 ).

[0283] If the candidate cell is the current SCell, RLM settings can also be provided to that SCell. In this case, the UE will not apply the corresponding RLM settings until the above conditions are met (e.g., receiving a cell handover command (MAC CE) for a specific cell). Additionally, under existing rules, RLM settings are not provided to the SCell.

[0284] <Option 2>

[0285] RLM settings can also be configured in the reference configuration. That is, the RLM setting can be applied to any candidate cell. For example, when a cell handover command (MAC CE) is sent for a handover of a SpCell or cell group, the UE applies the RLM setting to the new SpCell. In other words, when a cell handover command (MAC CE) is received for a handover of a SpCell or cell group, the UE can also apply the RLM setting corresponding to the SpCell (reference configuration). Figure 13 ).

[0286] <Option 3>

[0287] It is also possible to allow the RRC not to provide RLM settings for LTM candidate cells. In this case, the UE can also implicitly derive the RLM-RS. As methods for deriving the RLM-RS, the following options 3-1 to 3-2 are given.

[0288] (Option 3-1)

[0289] When a cell handover command is sent via MAC CE for the handover of a SpCell or cell group, the beam / TCI status of the target SpCell is transmitted through this cell handover command. That is, the cell handover command (MAC CE) may contain information indicating the beam / TCI status of the target SpCell (the new SpCell).

[0290] Upon receiving a cell handover command, the UE implicitly derives, for the new SpCell, the RS associated with the indicated TCI state as the RLM-RS (refer to...). Figure 13 The UE can execute the implicit export method of the RLM-RS until the RLM-RS is explicitly set / updated by higher-layer signaling (RRC / MAC CE).

[0291] (Option 3-2)

[0292] After a cell handover is performed using MAC CE via a cell handover command, the UE derives RLM-RS for the new SpCell based on existing rules.

[0293] According to the first implementation described above, the UE can appropriately control the RLM for the candidate cell / serving cell (the new cell to which the handover destination is located) based on the cell handover command.

[0294] <Second Implementation>

[0295] The second implementation involves BFD settings. Figure 14 This diagram illustrates an example of UE operation according to the second embodiment. The second embodiment can rewrite the RLM of the first embodiment as BFD for application.

[0296] <Option 1>

[0297] Each candidate cell can be configured along with (via) BFD settings. That is, BFD settings can also be configured for each candidate cell. BFD settings can be included in the higher-layer parameters (IE CellGroupConfig) used for configuring each LTM candidate cell. Parameters associated with this BFD setting can include, for example, spCell-BFR-CBRA-r16 mentioned above.

[0298] When a cell handover command (MAC CE) is sent for SpCell handover (e.g., when indicating SpCell as a target candidate cell), the target candidate cell becomes the new SpCell, and the UE applies its BFD settings. That is, when the UE receives a cell handover command (MAC CE) for SpCell, it can apply the BFD settings corresponding to that SpCell as the target candidate cell (see [reference]). Figure 14 ).

[0299] When a cell handover command (MAC CE) is sent for cell group handover (e.g., indicating SpCell and SCell as target candidates), the UE can apply the new BFD setting for SpCell and ignore the new BFD setting for SCell. That is, upon receiving a cell handover command (MAC CE) for cell group handover, the UE can also apply only the BFD setting for SpCell (see [reference]). Figure 14 ).

[0300] If the candidate cell is the current SCell, BFD settings can also be provided to that SCell. In this case, the UE will not apply the corresponding BFD settings until the above conditions are met (e.g., receiving a cell handover command (MAC CE) for a specific cell). Additionally, under existing rules, RLM settings are not provided to the SCell.

[0301] <Option 2>

[0302] BFD settings can also be configured in the reference configuration. That is, the BFD setting can be applied to any candidate cell. For example, when a cell handover command (MAC CE) is sent for the handover of a SpCell or cell group, the UE applies the BFD setting to both the new SpCell and the new SCell. In other words, upon receiving a cell handover command (MAC CE) for the handover of a SpCell or cell group, the UE can also apply the BFD settings corresponding to the SpCell and SCell respectively (reference configuration). Figure 14 Additionally, it can be assumed that the parameters of SpCell BFR are only applied to new SpCells.

[0303] (Changes to Option 2)

[0304] In addition to the parameters of SpCell BFR, BFD settings can also be set for each candidate cell. On the other hand, the parameters of SpCell BFR can be set in the reference settings. That is, the BFR parameters of a specific cell can also be set separately from other parameters (BFD settings).

[0305] <Option 3>

[0306] Even without BFD settings for LTM candidate cells, the UE can implicitly derive BFD-RS. Examples of methods for deriving BFD-RS include options 3-1 to 3-2.

[0307] (Option 3-1)

[0308] When a cell handover command is sent via MAC CE for the handover of a SpCell or cell group, the beam / TCI status of the target SpCell is transmitted through this cell handover command. That is, the cell handover command (MAC CE) may contain information indicating the beam / TCI status of the target SpCell (the new SpCell).

[0309] Upon receiving a cell handover command, the UE implicitly derives the RS associated with the indicated TCI state as the BFD-RS (refer to...). Figure 14 The UE can execute the implicit export method of the BFD-RS until the BFD-RS is explicitly set / updated by higher-layer signaling (RRC / MAC CE).

[0310] (Option 3-2)

[0311] After a cell handover is performed using MAC CE via a cell handover command, the UE derives BFD-RS for each new SCell based on existing rules.

[0312] According to the second implementation described above, the UE can appropriately control BFD / BFR for the candidate cell / serving cell (the new cell to which the handover destination is located) based on the cell handover command.

[0313] <Third Implementation Method>

[0314] The first implementation involves PUCCH configuration. Figure 15 This diagram illustrates an example of UE operation according to the third embodiment. The third embodiment can rewrite the RLM of the first embodiment / BFD of the second embodiment into a PUCCH for application. The PUCCH settings, PUCCH-Config settings, and PUCCH-Config can be mutually overwritten.

[0315] <Option 1>

[0316] Each candidate cell can be configured along with (through) the PUCCH-Config settings (PUCCH settings). That is, the PUCCH-Config settings can also be configured for each candidate cell. The PUCCH-Config settings can be included in the higher-layer parameters (IE CellGroupConfig) used for configuring each LTM candidate cell.

[0317] When a cell handover command (MAC CE) is sent for SpCell handover (e.g., when the SpCell is indicated as the target candidate cell), the target candidate cell becomes the new SpCell, and the UE applies its PUCCH-Config settings. That is, when the UE receives a cell handover command (MAC CE) for an SpCell, it can apply the PUCCH-Config settings corresponding to that SpCell as the target candidate cell (see [reference]). Figure 15 ).

[0318] Given the existing PUCCH SCell settings, one of the following options 1-2 can also be considered.

[0319] (Choose 1)

[0320] The existing PUCCH SCell is no longer a PUCCH SCell. After cell handover, the PUCCH SCell does not exist until the NW sets / indicates a new PUCCH SCell. That is, the UE can also assume that the PUCCH SCell does not exist until it receives the setting / indication corresponding to the new PUCCH SCell from the NW.

[0321] (Option 2)

[0322] The existing PUCCH SCell will not be changed. That is, the UE can also apply it directly without changing the settings related to the PUCCH SCell.

[0323] When a cell handover command (MAC CE) is sent for cell group handover (e.g., when both SpCell and SCell are indicated as target candidates), the UE can also apply the new PUCCH-Config settings for the SpCell. That is, upon receiving a cell handover command (MAC CE) for cell group handover, the UE can also apply the PUCCH-Config settings corresponding to the SpCell (see [reference]). Figure 15 On the other hand, the UE can apply the following options 1-1 to 1-3 to the new SCel.

[0324] (Option 1-1)

[0325] The UE can also ignore the PUCCH-Config settings for each new SCell.

[0326] (Options 1-2)

[0327] Before the NW sets / indicates the largest SCell as the new PUCCH SCell via higher-layer / physical-layer signaling (unless otherwise set / indicated), the UE can also ignore the PUCCH-Config settings for each new SCell. In this case, it is possible to append an indication of a candidate cell index as the PUCCH SCell via a cell handover command (MAC CE).

[0328] (Options 1-3)

[0329] The UE can also select a SCell as the PUCCHSCell based on predefined rules (specified in the specification). For example, as a selection rule, the selectable SCell could be the new SCell with the smallest cell ID. Whether to apply such a selection rule can also be set by new parameters (e.g., reference settings described later).

[0330] In Option 1, if the candidate cell is the current SCell, the PUCCH-Config settings can also be provided to that SCell. In this case, the UE will not apply the corresponding PUCCH-Config settings until the above conditions are met (e.g., receiving a cell handover command (MAC CE) for a specific cell) or unless a new parameter for the applied settings is indicated. Additionally, under existing rules, this parameter (e.g., PUCCH-Config) can only be provided to the largest SCell.

[0331] <Option 2>

[0332] The PUCCH-Config settings can also be configured in the reference configuration. That is, the PUCCH-Config settings can be applied to candidate cells. For example, when a cell handover command (MAC CE) is sent for a handover of a SpCell or cell group, the UE applies the PUCCH-Config settings to the new SpCell. In other words, when a cell handover command (MAC CE) is received for a handover of a SpCell or cell group, the UE can also apply the PUCCH-Config settings corresponding to the SpCell (reference configuration). Figure 15 ).

[0333] (Changes to Option 2)

[0334] When a cell handover command (MAC CE) is sent for a SpCell handover (e.g., when the SpCell is indicated as a target candidate cell), the target candidate cell becomes the new SpCell, and the UE applies its PUCCH-Config settings. That is, upon receiving a cell handover command (MAC CE) for a SpCell, the UE can apply the PUCCH-Config settings corresponding to that SpCell as the target candidate cell (see [reference]). Figure 15 ).

[0335] Given the existing PUCCH SCell settings, one of the following options 1-2 can also be considered.

[0336] (Choose 1)

[0337] The existing PUCCH Scell ​​is no longer a PUCCH SCell. After cell handover, the PUCCH SCell does not exist until the NW sets / indicates a new PUCCH SCell. That is, the UE can also be assumed to be a PUCCH SCell until it receives the setting / indication corresponding to the new PUCCH SCell from the NW.

[0338] (Option 2)

[0339] The existing PUCCH SCell will not be changed. That is, the UE can also apply it directly without changing the settings related to the PUCCH SCell.

[0340] When a cell handover command (MAC CE) is sent for cell group handover (e.g., when both SpCell and SCell are indicated as target candidates), the UE can also apply the new PUCCH-Config settings for the SpCell. That is, upon receiving a cell handover command (MAC CE) for cell group handover, the UE can also apply the PUCCH-Config settings corresponding to the SpCell (see [reference]). Figure 15 On the other hand, the UE can apply the following options 2-1 to 2-3 to the new SCel.

[0341] (Option 2-1)

[0342] The UE can also ignore the PUCCH-Config settings for each new SCell.

[0343] (Option 2-2)

[0344] Before the NW sets / indicates the largest SCell as the new PUCCH SCell via higher-layer / physical-layer signaling (unless otherwise set / indicated), the UE can also ignore the PUCCH-Config settings for each new SCell. In this case, it is possible to append an indication of a candidate cell index as the PUCCH SCell via a cell handover command (MAC CE).

[0345] (Options 2-3)

[0346] The UE can also select a specific SCell as the PUCCHSCell based on predefined rules (specified in the specification). For example, the selectable SCell could be the new SCell with the smallest cell ID, for instance. Whether to apply such a selection rule can also be set by new parameters (e.g., reference settings).

[0347] According to the third implementation described above, the UE can appropriately control the application of PUCCH-Config settings for the candidate cell / serving cell (the new cell to which the handover destination is located) based on the cell handover command.

[0348] <Supplement>

[0349] [Information notification to UE]

[0350] In the above embodiments, any information (notification from the Network (NW) (e.g., Base Station (BS)) to the UE) (in other words, the reception of any information from the BS in the UE) can also be delivered 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 combinations thereof.

[0351] In the case where the above notification is made via MAC CE, the MAC CE can also be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not specified in the existing standard.

[0352] When the above notification is made through a DCI, the notification may also be made through specific fields of the DCI, the Radio Network Temporary Identifier (RNTI) used in the scrambling of the Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0353] Furthermore, the notification of any information to the UE in the above embodiments can also be performed periodically, semi-persistently, or non-periodically.

[0354] [Notification from UE]

[0355] The notification of any information from the UE (to the NW) in the above embodiments (in other words, the transmission / reporting of any information in the UE to the BS) can also be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MACCE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals) or combinations thereof.

[0356] In the case where the above notification is made via MAC CE, the MAC CE can also be identified by a new LCID included in the MAC subheader that is not specified in the existing standard.

[0357] In cases where the above notification is sent via UCI, the above notification may also be sent using PUCCH or PUSCH.

[0358] Furthermore, the notification of any information from the UE in the above embodiments can also be performed periodically, semi-persistently, or non-periodically.

[0359] [Regarding the application of each implementation method]

[0360] At least one of the above embodiments can also be applied to situations where specific conditions are met. These specific conditions can be specified in the standard or notified to the UE / BS using higher-layer signaling / physical layer signaling.

[0361] At least one of the above embodiments may also be applied only to UEs that have reported a specific UE capability or support that specific UE capability.

[0362] This specific UE capability can also represent at least one of the following:

[0363] • Supports specific processing / operation / control / information for at least one of the above embodiments.

[0364] • Supports intra-cell mobility in L1 / L2 cells and inter-cell mobility in L1 / L2 cells.

[0365] • Supports TA for each TRP in multiple TRPs within / between cells.

[0366] • Supports setting multiple TRPs within a serving cell / multiple TRPs between cells for both serving and non-serving cells.

[0367] • Supports RLM-RS settings for candidate cells (RLM settings).

[0368] • Supports setting RFD-RS for candidate cells (RFD settings).

[0369] • Supports setting PUCCH-Config for candidate cells (PUCCH settings).

[0370] Furthermore, the aforementioned specific UE capabilities can be applied across the entire frequency range (commonly independent of frequency), or per frequency (e.g., one or a combination of cells, bands, band combinations, BWPs, component carriers, etc.), or per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or per subcarrier spacing (SCS), or per feature set (FS) or per component carrier feature set (FSPC).

[0371] Furthermore, the aforementioned specific UE capabilities can be either capabilities that are applied across all duplex modes (common regardless of the duplex mode) or capabilities that are specific to each duplex mode (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).

[0372] Furthermore, at least one of the above embodiments can also be applied to situations where the UE is set / activated / triggered by higher-layer signaling / physical layer signaling to specific information associated with the above embodiments (or to perform actions of the above embodiments). For example, the specific information may be information indicating activation of a random access procedure / PRACH transmission without RAR monitoring, arbitrary RRC parameters for a specific version (e.g., Rel. 18 / 19), etc.

[0373] The UE may also apply operations such as Rel.15 / 16 if it does not support at least one of the specific UE capabilities mentioned above or if the specific information mentioned above is not set.

[0374] (Postscript)

[0375] With respect to one embodiment of this disclosure, the following invention is noted.

[0376] [Postscript 1]

[0377] A terminal having:

[0378] The receiving unit receives the Medium Access Control Element (MAC CE) related to cell handover; and

[0379] The control unit, based on the information contained in the MAC CE, controls the application of settings for at least one of Radio Link Monitoring (RLM), Beam Failure Detection (BFD), and Uplink Control Channel (PUCCH) for a specific cell.

[0380] [Postscript 2]

[0381] The terminal as described in Appendix 1, wherein,

[0382] The control unit determines the settings to be applied based on the category of the candidate cells.

[0383] [Postscript 3]

[0384] The terminal as described in Appendix 1 or Appendix 2, wherein,

[0385] The control unit applies the settings to a portion of the specific cells, and ignores the settings or does not apply the settings until certain conditions are met for another portion of the specific cells.

[0386] [Postscript 4]

[0387] The terminal as described in any one of Annexes 1 to 3, wherein,

[0388] If the settings are not provided by higher-layer signaling, or if the settings for candidate cells do not exist, the control unit outputs a reference signal (RS) corresponding to the settings.

[0389] (Wireless communication system)

[0390] The structure of a wireless communication system according to one embodiment of this disclosure will now be described. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above embodiments of this disclosure.

[0391] Figure 16This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment. The wireless communication system 1 (also referred to simply as System 1) may also be a system that uses Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5GNR) as standardized by the Third Generation Partnership Project (3GPP).

[0392] Furthermore, the wireless communication system 1 can also support dual connectivity between multiple radio access technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC can 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)), etc.

[0393] 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.

[0394] Wireless communication system 1 can also support dual connectivity between multiple base stations within the same RAT (e.g., MN and SN are dual connectivity between NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0395] The wireless communication system 1 may also include a base station 11 forming a macro cell C1 with a relatively wide coverage area, and a base station 12 (12a-12c) configured within the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. The user terminal 20 may also be located within at least one cell. The configuration and number of each cell and the user terminal 20 are not limited to the arrangement shown in the figure. Hereinafter, without distinguishing between base stations 11 and 12, they will be collectively referred to as base station 10.

[0396] User terminal 20 may also connect to at least one of multiple base stations 10. User terminal 20 may also utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0397] Each CC can also be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). Macro cell C1 can also be included in FR1, and small cell C2 can also be included in FR2. For example, FR1 can also be a frequency band below 6 GHz (sub-6 GHz), and FR2 can also be a frequency band above 24 GHz (above-24 GHz). In addition, the frequency bands, definitions, etc. of FR1 and FR2 are not limited to these; for example, FR1 can also correspond to a frequency band higher than FR2.

[0398] In addition, user terminal 20 can also use at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) to communicate in each CC.

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

[0400] Base station 10 may also be connected to core network 30 via other base stations 10 or directly. Core network 30 may include, for example, at least one of Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0401] The core network 30 may also include, for example, user plane functions (UPF), access and mobility management functions (AMF), session management functions (SMF), unified data management (UDM), application functions (AF), data network (DN), location management functions (LMF), and network functions (NF) such as operation, administration and maintenance (OAM). Alternatively, multiple functions can be provided through a single network node. Furthermore, communication with external networks (e.g., the Internet) can also be achieved via the DN.

[0402] User terminal 20 can also be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0403] In wireless communication system 1, wireless access methods based on Orthogonal Frequency Division Multiplexing (OFDM) can also be used. For example, in at least one of the downlink (DL) and uplink (UL) links, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA) can also be used.

[0404] The wireless access method can also be referred to as a waveform. In addition, in the wireless communication system 1, other wireless access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) can also be used in the wireless access methods of UL and DL.

[0405] In the wireless communication system 1, the downlink channel can also be a shared downlink channel (Physical Downlink Shared Channel (PDSCH)), a broadcast channel (Physical Broadcast Channel (PBCH)), or a downlink control channel (Physical Downlink Control Channel (PDCCH)) shared by each user terminal 20.

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

[0407] User data, high-level control information, and System Information Blocks (SIBs) are transmitted via the PDSCH. User data and high-level control information can also be transmitted via the PUSCH. In addition, Master Information Blocks (MIBs) can also be transmitted via the PBCH.

[0408] Lower-layer control information can also be transmitted via PDCCH. This lower-layer control information may include, for example, downlink control information (DCI), which includes scheduling information for at least one of PDSCH and PUSCH.

[0409] Additionally, the DCI that schedules PDSCH can also be called DL allocation, DL DCI, etc., and the DCI that schedules PUSCH can also be called UL authorization, UL DCI, etc. Furthermore, PDSCH can be rewritten as DL data, and PUSCH can be rewritten as UL data.

[0410] In PDCCH detection, a Control Resource Set (CORESET) and a search space can also be utilized. A CORESET corresponds to the resources used to search for DCIs. The search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor CORESETs associated with a specific search space based on search space settings.

[0411] A search space can also correspond to a PDCCH candidate corresponding to one or more aggregation levels. One or more search spaces can also be referred to as a search space set. In addition, the terms "search space", "search space set", "search space setting", "search space set setting", "CORESET", and "CORESET setting" in this disclosure can be rewritten interchangeably.

[0412] The PUCCH can also transmit uplink control information (uplink control information (UCI)) that includes at least one of the following: Channel State Information (CSI), delivery confirmation information (e.g., also known as Hybrid Automatic Repeat Request ACK Knowledge (HARQ-ACK), ACK / NACK, etc.), and Scheduling Request (SR). The PRACH can also transmit random access preambles used for establishing connections with the cell.

[0413] In addition, in this disclosure, downlink, uplink, etc., may be described without the word "link". Furthermore, various channels may be described without the word "physical".

[0414] In wireless communication system 1, synchronization signals (SS) and downlink reference signals (DL-RS) can also be transmitted. In wireless communication system 1, DL-RS can also transmit cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), positioning reference signals (PRS), and phase tracking reference signals (PTRS).

[0415] Synchronization signals can be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block containing SS (PSS, SSS) and PBCH (and DMRS for PBCH) can also be called an SS / PBCH block, SS block (SSB), etc. In addition, SS, SSB, etc. can also be called reference signals.

[0416] Furthermore, in wireless communication system 1, the uplink reference signal (UL-RS) can also transmit measurement reference signals (sounding reference signals (SRS)) and demodulation reference signals (DMRS). Additionally, DMRS can also be referred to as user terminal-specific reference signals (UE-specific reference signals).

[0417] (Base station)

[0418] Figure 17 This diagram illustrates an example of the structure of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmit / receive unit 120, a transmit / receive antenna 130, and a transmission path interface (transmission line interface) 140. Alternatively, the control unit 110, the transmit / receive unit 120, the transmit / receive antenna 130, and the transmission path interface 140 may each be provided in more than one manner.

[0419] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it can also be envisioned that the base station 10 also possesses other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0420] The control unit 110 performs overall control of the base station 10. The control unit 110 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the art to which this disclosure pertains.

[0421] The control unit 110 can also control signal generation and scheduling (e.g., resource allocation, mapping). The control unit 110 can also control transmission, reception, and measurement using the transmit / receive unit 120, transmit / receive antenna 130, and transmission path interface 140. The control unit 110 can also generate data, control information, sequences, etc., to be transmitted as signals and forward them to the transmit / receive unit 120. The control unit 110 can also perform call processing (setting, releasing, etc.) of the communication channel, status management of the base station 10, and management of wireless resources.

[0422] The transmitting / receiving unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting / receiving unit 120 may be composed of transmitters / receivers, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmitting / receiving circuits, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0423] The transmitting and receiving unit 120 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 1211 and an RF unit 122. The receiving unit can also be composed of a receiving processing unit 1212, an RF unit 122, and a measurement unit 123.

[0424] The transmitting and receiving antenna 130 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0425] The transmitting / receiving unit 120 can also transmit the aforementioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 can also receive the aforementioned uplink channel, uplink reference signal, etc.

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

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

[0428] The transmitting and receiving unit 120 (transmitting processing unit 1211) can 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, and digital-to-analog conversion on the bit string to be transmitted, and output the baseband signal.

[0429] The transmitting and receiving unit 120 (RF unit 122) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 130.

[0430] On the other hand, the transmitting and receiving unit 120 (RF unit 122) can also amplify, filter, and demodulate the signals of the wireless frequency band received through the transmitting and receiving antenna 130 into the baseband signal.

[0431] The transmitting and receiving unit 120 (receiving and processing unit 1212) can also perform receiving and processing on the acquired baseband signal, including analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to acquire user data, etc.

[0432] The transmitting / receiving unit 120 (measurement unit 123) can also perform measurements related to the received signal. For example, the measurement unit 123 can also perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc., based on the received signal. The measurement unit 123 can 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)), propagation path information (e.g., CSI), etc. The measurement results can also be output to the control unit 110.

[0433] The transmission path interface 140 can also transmit and receive signals (backhaul signaling) between the device included in the core network 30 (e.g., the network node providing the NF), other base stations 10, etc., and can also acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

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

[0435] The transmitting unit 120 can also transmit the Medium Access Control Element (MAC CE) related to cell handover.

[0436] The control unit 110 may also generate information based on the information contained in the MAC CE, which is used by the control terminal to determine the application settings of at least one of Radio Link Monitoring (RLM), Beam Failure Detection (BFD), and Uplink Control Channel (PUCCH) for a specific cell.

[0437] (User terminal)

[0438] Figure 18This diagram illustrates an example of the structure 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. Alternatively, the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may each be provided as one or more.

[0439] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the user terminal 20 may also have other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0440] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the technical field to which this disclosure pertains.

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

[0442] The transmitting / receiving 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 transmitting processing unit 2211 and a receiving processing unit 2212. The transmitting / receiving unit 220 may be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0443] The transmitting and receiving unit 220 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit can also be composed of a receiving processing unit 2212, an RF unit 222, and a measurement unit 223.

[0444] The transmitting and receiving antenna 230 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0445] The transmitting / receiving unit 220 can also receive the downlink channel, synchronization signal, downlink reference signal, etc., mentioned above. The transmitting / receiving unit 220 can also transmit the uplink channel, uplink reference signal, etc., mentioned above.

[0446] The transmitting and receiving unit 220 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc., to form at least one of the transmitting beam and the receiving beam.

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

[0448] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may include error correction coding), modulation, mapping, filter 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 the baseband signal.

[0449] Furthermore, whether or not to apply DFT processing can be based on the settings of transform precoding. For a certain channel (e.g., PUSCH), if transform precoding is enabled, the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as described above in order to transmit the channel using the DFT-s-OFDM waveform. If not, the transmit / receive unit 220 (transmit processing unit 2211) can perform the above transmission processing without performing DFT processing.

[0450] The transmitting and receiving unit 220 (RF unit 222) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 230.

[0451] On the other hand, the transmitting and receiving unit 220 (RF unit 222) can also amplify, filter, demodulate, etc., the signals of the wireless frequency band received by the transmitting and receiving antenna 230.

[0452] The transmitting and receiving unit 220 (receiving and processing unit 2212) can also perform receiving and processing on the acquired baseband signal, such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to acquire user data.

[0453] The transmitting / receiving unit 220 (measurement unit 223) can also perform measurements related to the received signal. For example, the measurement unit 223 can also perform RRM measurements, CSI measurements, etc., based on the received signal. The measurement unit 223 can 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 can also be output to the control unit 210.

[0454] Additionally, the measurement unit 223 can also derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources can be, for example, non-zero power (NZP) CSI-RS resources. Furthermore, the measurement unit 223 can also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources can be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. Additionally, CSI-IM can also be referred to as CSI-Interference Management (IM), and can be interchanged with zero power (ZP) CSI-RS. Furthermore, in this disclosure, CSI-RS, NZPCSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., can also be interchanged.

[0455] Alternatively, the transmitting and receiving units of the user terminal 20 in this disclosure may also be composed of at least one transmitting / receiving unit 220 and transmitting / receiving antenna 230.

[0456] The transmitting / receiving unit 220 can also receive a Medium Access Control (MAC CE) element related to cell handover. The MAC CE may also contain information related to the TCI state pool of the serving cell or candidate cell. The TCI state pool may be associated with at least one of a unified TCI state, a component carrier (CC) specific TCI pool, and a CC common pool.

[0457] The control unit 210 can also control the application of settings for at least one of Radio Link Surveillance (RLM), Beam Failure Detection (BFD), and Uplink Control Channel (PUCCH) for a specific cell based on the information contained in the MAC CE. The control unit 210 can also determine the settings to apply based on the category of candidate cells. The control unit 210 can also apply the settings to a subset of cells in a specific set of cells, ignoring the settings or not applying them until certain conditions are met for another subset of cells in the specific set. In the absence of settings provided by higher-layer signaling, or in the absence of settings for candidate cells, the control unit 210 can also derive a reference signal (RS) corresponding to the settings.

[0458] (Hardware structure)

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

[0460] Here, the functions include judgment, decision, determination, calculation, calculation, processing, export, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, regard as, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, a functional block (structural unit) that implements the sending function can also be called a transmitting unit, transmitter, etc. Each of these, as described above, is not particularly limited in its implementation method.

[0461] For example, in one embodiment of this disclosure, the base station, user terminal, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 19This diagram illustrates an example of the hardware structure 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 device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0462] Furthermore, in this disclosure, terms such as apparatus, circuit, device, section, and unit can be interchanged. The hardware structure of base station 10 and user terminal 20 can be configured to include one or more of the apparatuses shown in the figures, or it can be configured not to include any of the apparatuses.

[0463] For example, only one processor 1001 is shown, but there can be multiple processors. Furthermore, processing can be performed by one processor, or simultaneously, sequentially, or by two or more processors using other methods. Additionally, processor 1001 can be implemented using more than one chip.

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

[0465] The processor 1001 enables the operating system to operate and control the computer as a whole. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic devices, registers, etc. For example, at least a portion of the control unit 110 (210), the transmit / receive unit 120 (220), etc., described above may also be implemented by the processor 1001.

[0466] 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 performs various processes accordingly. As a program, a program that causes the computer to perform at least a portion of the operations described in the above 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 operated in the processor 1001; similar implementations can be made for other functional blocks.

[0467] The memory 1002 may also be a computer-readable recording medium, such as being composed of at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage media. The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 is capable of storing executable programs (program code), software modules, etc., for implementing the wireless communication method according to an embodiment of this disclosure.

[0468] Storage device 1003 may also be a computer-readable recording medium, such as a flexible disc, floppy disk, optical disk (e.g., a compact disc ROM), digital multifunction disk, Blu-ray disc, removable disk, hard disk drive, smart card, flash memory device (e.g., a card, stick, key drive), magnetic stripe, database, server, or at least one other suitable storage medium. Storage device 1003 may also be referred to as an auxiliary storage device.

[0469] The communication device 1004 is hardware (transmitting and receiving device) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. To implement at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD), the communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the aforementioned transmit / receive unit 120 (220) and transmit / receive antenna 130 (230) may also be implemented by the communication device 1004. The transmit / receive unit 120 (220) may also be implemented by physically or logically separating the transmit unit 120a (220a) and the receive unit 120b (220b).

[0470] Input device 1005 is an input device that receives input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, light-emitting diode (LED) lamp, etc.). Alternatively, input device 1005 and output device 1006 can also be an integrated structure (e.g., a touch panel).

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

[0472] Furthermore, the base station 10 and the user terminal 20 can 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 can also use this hardware to implement part or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0473] (Variation example)

[0474] Furthermore, the terms described in this disclosure, as well as those necessary for understanding this disclosure, may be replaced with terms that have the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be interchanged. Additionally, a signal may also be a message. A reference signal can also be abbreviated as RS, and may be referred to as pilot, pilot signal, etc., depending on the applied standard. Furthermore, a component carrier (CC) may also be referred to as cell, frequency carrier, carrier frequency, etc.

[0475] A radio frame can also be composed of one or more periods (frames) in the time domain. Each of these periods (frames) that constitute 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 (e.g., 1 ms) independent of the parameter set (numerology).

[0476] Here, the parameter set can also be communication parameters applied in at least one of the transmission and reception of a signal or channel. For example, the parameter set can also represent at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), 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.

[0477] In the time domain, a time 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.). In addition, a time slot can also be a time unit based on a set of parameters.

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

[0479] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can also use their respective other names. Furthermore, the time units such as frames, subframes, time slots, mini-time slots, and symbols in this disclosure can be interchanged.

[0480] For example, a subframe can also be called a TTI, multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is, at least one of a subframe and a TTI can be a subframe in existing LTE (1ms), a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but rather a time slot, mini-time slot, etc.

[0481] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules radio resources (frequency bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0482] TTI can also be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., and can also be a unit of processing such as scheduling and link adaptation. In addition, when a TTI is given, the actual time interval (e.g., the number of symbols) mapped to transmission blocks, code blocks, codewords, etc. can be shorter than the TTI.

[0483] Additionally, where a time slot or a mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can also serve as the minimum time unit for scheduling. Furthermore, the number of time slots (mini-time slots) constituting the minimum time unit of the schedule can also be controlled.

[0484] A TTI with a duration of 1ms can also be referred to as a normal TTI (TTI in 3GPPRel.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 can 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 mini time slot, a sub-time slot, a time slot, etc.

[0485] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) can also be rewritten as a TTI with a duration of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) can also be rewritten as a TTI with a duration of less than a long TTI but more than 1 ms.

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

[0487] Furthermore, an RB can contain one or more symbols in the time domain, and can also be a time slot, a mini-time slot, a subframe, or the length of a TTI. A TTI, a subframe, etc., can also be composed of one or more resource blocks.

[0488] In addition, one or more RBs can also be referred to as Physical Resource Blocks (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0489] In addition, a resource block can also consist of one or more resource elements (REs). For example, an RE can also be a radio resource area consisting of a subcarrier and a symbol.

[0490] The Bandwidth Part (BWP) (also referred to as partial bandwidth, etc.) can also represent a subset of consecutive common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can also be determined by the index of RBs based on the common reference point of the carrier. PRBs can also be defined in a BWP and appended with numbers within that BWP.

[0491] A BWP can also include a UL BWP (the BWP used by UL) and a DL BWP (the BWP used by DL). For a UE, one or more BWPs can also be set within a single carrier.

[0492] At least one of the configured BWPs can be active, and the UE may not intend to transmit or receive specific signals / channels outside of the active BWPs. Additionally, terms such as "cell" and "carrier" in this disclosure may be replaced with "BWP".

[0493] Furthermore, the structures described above, such as radio frames, subframes, time slots, mini-time slots, and symbols, are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

[0494] Furthermore, the information, parameters, etc., described in this disclosure can be represented by absolute values, relative values ​​with respect to a specific value, or other corresponding information. For example, wireless resources can also be indicated by a specific index.

[0495] In this disclosure, the names used for parameters, etc., are not limiting names in any respect. Furthermore, the mathematical expressions, etc., using 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 name; therefore, the various names assigned to these various channels and information elements are not limiting names in any respect.

[0496] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be mentioned throughout the above description, can also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

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

[0498] 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.

[0499] The notification of information is not limited to the methods / implementations described in this disclosure, and may also be carried out by other methods. For example, the notification of information in this disclosure may also be implemented by physical layer signaling (e.g., downlink control information (DCI), uplink control information (UCI), etc.), 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 combinations thereof.

[0500] In addition, physical layer signaling can also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. Furthermore, RRC signaling can also be referred to as RRC messages, such as RRC connection setup messages, RRC connection reconfiguration messages, etc. Additionally, MAC signaling can also be notified using, for example, the MAC control element (CE).

[0501] Furthermore, notification of specific information (e.g., a notification of “is X”) is not limited to explicit notification, but can also be implicit (e.g., by not providing that specific information, or by providing other information).

[0502] The determination can be made by a value represented by a single bit (0 or 1), by a true or false value (boolean), or by a numerical comparison (e.g., a comparison with a specific value).

[0503] Whether software is called software, firmware, middleware, microcode, hardware description language, or any other name, it should be broadly interpreted to refer to instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

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

[0505] The terms “system” and “network” as used in this disclosure are interchangeable. “Network” may also mean devices included in a network (e.g., base stations).

[0506] In this disclosure, the terms “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”, “layer”, “number of layers”, “rank”, “resource”, “resource set”, “beam”, “beamwidth”, “beam angle”, “antenna”, “antenna element”, “panel”, “UE panel”, “transmitting entity”, and “receiving entity” are used interchangeably.

[0507] Furthermore, in this disclosure, the antenna port can also be rewritten with an antenna port used for any signal / channel (e.g., a DeModulation Reference Signal (DMRS) port). In this disclosure, resources can also be rewritten with resources used for any signal / channel (e.g., reference signal resources, SRS resources, etc.). Additionally, resources can also include time / frequency / code / space / power resources. Moreover, the spatial domain transmission filter can also include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0508] The aforementioned groups may include, for example, at least one of the following: spatial relation group, code division multiplexing (CDM) group, reference signal (RS) group, control resource set (CORESET) group, PUCCH group, antenna port group (e.g., DMRS port group), layer group, resource group, beam group, antenna group, panel group, etc.

[0509] Furthermore, in this disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), RS, etc., can also be rewritten to each other.

[0510] Furthermore, in this disclosure, the TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, and joint TCI state can also be rewritten to each other.

[0511] Furthermore, in this disclosure, terms such as "QCL", "QCL concept", "QCL relationship", "QCL type information", "QCL property (QCLproperty / properties)", "specific QCL type (e.g., type A, type D) property", and "specific QCL type (e.g., type A, type D)" can be rewritten interchangeably.

[0512] In this disclosure, indexes, identifiers (IDs), indicators, indications, resource IDs, etc., can be interchanged. Sequences, lists, sets, groups, clusters, subsets, etc., can also be interchanged.

[0513] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) can be interchanged. "Spatial relationship information (TCI state)" can also be interchanged with "a set of spatial relationship information (TCI states)," "one or more spatial relationship information," etc. TCI state and TCI can also be interchanged. Spatial relationship information and spatial relationships can also be interchanged.

[0514] In this disclosure, the terms "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. There are also instances where the terms macro cell, small cell, femtocell, and picocell are used to refer to a base station.

[0515] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, its overall coverage area can be divided into several smaller areas, each of which can also provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0516] In this disclosure, the act of a base station sending information to a terminal can also be rewritten in relation to the act of the base station instructing the terminal to perform control / operation based on that information.

[0517] In this disclosure, the terms “Mobile Station (MS)”, “user terminal”, “user equipment (UE)”, and “terminal” are used interchangeably.

[0518] There are also instances where mobile stations are referred to as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or several other appropriate terms.

[0519] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Additionally, at least one of the base station and the mobile station can also be a device mounted on a moving object, the moving object itself, etc.

[0520] The term "mobile body" refers to a movable object whose speed is arbitrary, including when the object is stationary. Examples of such mobile bodies include vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships (ships and other watercraft), airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, hot air balloons, and objects carried on them, but are not limited to these. Furthermore, the mobile body can also be a mobile body that moves autonomously based on operational commands.

[0521] The mobile entity can be a means of transportation (e.g., a vehicle, an airplane, etc.), a mobile entity moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Additionally, at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station can also be an Internet of Things (IoT) device such as a sensor.

[0522] Figure 20 This is a diagram illustrating an example of a vehicle according to one embodiment. The 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 speed sensor 51, a 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.

[0523] The drive unit 41 is comprised of 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 called a steering handle) that steers at least one of the front wheels 46 and the rear wheels 47 based on operation of the steering wheel by the user.

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

[0525] The signals from various sensors 50-58 include the following: current signal from current sensor 50 sensing the current of the motor; rotational speed signal of front wheel 46 / rear wheel 47 obtained by speed sensor 51; air pressure signal of front wheel 46 / rear wheel 47 obtained by air pressure sensor 52; vehicle speed signal obtained by vehicle speed sensor 53; acceleration signal obtained by acceleration sensor 54; accelerator pedal 43 depress amount signal obtained by accelerator pedal sensor 55; brake pedal 44 depress amount signal obtained by brake pedal sensor 56; shift lever 45 operation signal obtained by shift lever sensor 57; and detection signal obtained by object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc.

[0526] The information service unit 59 comprises various devices such as a navigation system, audio system, speakers, display, television, and radio, used to provide (output) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 59 uses information obtained from external devices via the communication module 60, etc., to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0527] The information service unit 59 may include input devices (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) that accept input from the outside, and output devices (e.g., display, speaker, LED light, touch panel, etc.) that implement output to the outside.

[0528] The driver assistance system unit 64 comprises various devices used to provide functions for preventing accidents or reducing the driver's workload, such as millimeter-wave radar, light detection and ranging (LiDAR), cameras, positioning detectors (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 Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, and one or more ECUs that control these devices. Furthermore, the driver assistance system unit 64 sends and receives various information via communication module 60 to realize driver assistance functions or autonomous driving functions.

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

[0530] The communication module 60 can be controlled by the microprocessor 61 of the electronic control unit 49 and is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information with external devices via wireless communication. The communication module 60 can be located both inside and outside the electronic control unit 49. The external device can be, for example, the aforementioned base station 10, user terminal 20, etc. Furthermore, the communication module 60 can be, for example, at least one of the aforementioned base station 10 and user terminal 20 (or it can function as at least one of the base station 10 and user terminal 20).

[0531] The communication module 60 can also wirelessly transmit at least one of the signals input to the electronic control unit 49 from the various sensors 50-58 described above, the information obtained based on these signals, and the information based on input from an external (user) source obtained via the information service unit 59 to an external device. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., can also be referred to as input units that receive input. For example, the PUSCH transmitted via the communication module 60 can also contain information based on the aforementioned inputs.

[0532] The communication module 60 receives various information (traffic information, signal information, workshop information, etc.) sent 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, outputs information to devices such as displays and speakers based on the PDSCH received by the communication module 60 (or the data / information decoded from the PDSCH).

[0533] Furthermore, the communication module 60 stores various types of information received from external devices into a memory 62 that can be utilized 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, gear shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, and various sensors 50-58, etc., of the vehicle 40.

[0534] Furthermore, the base station in this disclosure can also be rewritten as a user terminal. For example, various methods / implementations of this disclosure can be applied to structures where communication between the base station and the user terminal is replaced by communication between multiple user terminals (e.g., also referred to as device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, it can also be configured such that the user terminal 20 has the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be rewritten as terms corresponding to inter-terminal communication (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can also be rewritten as sidelink channel.

[0535] Similarly, the user terminal in this disclosure can also be rewritten as a base station. In this case, it can also be configured such that the base station 10 has the functions of the user terminal 20 described above.

[0536] In this disclosure, operations are assumed to be performed by the base station, and sometimes, depending on the circumstances, by its upper node. In a network containing one or more network nodes having a base station, the various operations performed for communication with a terminal can obviously be performed by the base station, one or more network nodes other than the base station (e.g., considering a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc., but not limited to these), or combinations thereof.

[0537] The various methods / implementations described in this disclosure can be used individually or in combination, and can be switched as needed during execution. Furthermore, the processing procedures, timing sequences, flowcharts, etc., of the various methods / implementations described in this disclosure can be rearranged as long as they do not contradict each other. For example, for the method described in this disclosure, the illustrated order is used to indicate various steps, but the order in which they are indicated is not limited.

[0538] The various methods / implementations described in this disclosure can 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, where 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), Futuregeneration Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE This includes 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-Wideband (UWB)), Bluetooth (registered trademark), systems utilizing other suitable wireless communication methods, and next-generation systems derived from, modified, generated, or specified based on these methods. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A, combinations with 5G, etc.) for application.

[0539] As used in this disclosure, the term "based on" does not mean "based on only" unless otherwise specified. In other words, the term "based on" means both "based on only" and "based on at least".

[0540] Any reference to an element using the designations "first," "second," etc., as used in this disclosure does not comprehensively limit 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 the first and second elements does not imply that only two elements may be used, or that the first element must take precedence over the second element in some form.

[0541] The term "determining" as used in this disclosure can encompass a wide variety of operations. For example, "determining" can also refer to judging, calculating, computing, processing, deriving, investigating, looking up (search, inquiry) (e.g., searching in a table, database or other data structure), and ascertaining.

[0542] In addition, "judgment (decision)" can also refer to receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, accessing (e.g., accessing data in memory), etc., as situations where "judgment (decision)" is performed.

[0543] Furthermore, "judgment (decision)" can also refer to situations where resolving, selecting, choosing, establishing, or comparing are considered as making a "judgment (decision)". That is, "judgment (decision)" can also refer to certain operations as making a "judgment (decision)". In this disclosure, "judgment (decision)" can also be rewritten in relation to the operations described above.

[0544] Furthermore, in this disclosure, "determine / determining" can also be interchanged with "assume / assuming," "expect / expecting," "consider / considering," etc. Additionally, in this disclosure, "not assuming to proceed..." can also be interchanged with "assuming not to proceed..."

[0545] In this disclosure, "expect" can also be interchanged with "be expected." For example, "expect(s) ..." (where "..." can also be expressed using a that clause, to infinitive, etc.) can also be interchanged with "be expected ...." "Does not expect..." can also be interchanged with "be not expected...". Furthermore, "An apparatus A is not expected..." can also be interchanged with "Apparatus B other than apparatus A does not expect..." (for example, if apparatus A is a UE, apparatus B can also be a base station).

[0546] The term "maximum transmit power" as used in this disclosure may refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated UE maximum transmit power).

[0547] As used in this disclosure, the terms “connected,” “coupled,” or all variations thereof, refer to all direct or indirect connections or combinations between two or more elements, and can include cases where there is one or more intermediate elements between two mutually “connected” or “coupled” elements. The connections or combinations between elements can be physical, logical, or a combination thereof. For example, “connection” can also be rewritten as “access.”

[0548] In this disclosure, when two elements are connected, it is possible to consider using more than one wire, cable, printed electrical connection, etc. to be "connected" or "combined" with each other, and as several non-limiting and non-exclusive examples, to use electromagnetic energy with wavelengths having wireless frequency domain, microwave region, light (both visible and invisible) region to be "connected" or "combined" with each other.

[0549] In this disclosure, the term "A is different from B" can also mean "A and B are different from each other." Additionally, the term can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0550] When the terms "include," "including," and variations thereof are used in this disclosure, these terms, like the term "comprising," mean inclusive. Furthermore, the term "or" as used in this disclosure does not mean XOR.

[0551] In this disclosure, for example, in cases where articles are added through translation, such as a, an, and the in English, the disclosure may also include cases where the noun following these articles is in a plural form.

[0552] In this disclosure, words such as "below," "less than," "above," "more than," and "equal to" can be interchanged. Furthermore, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "early," "slow," "wide," and "narrow," etc., are not limited to the positive, comparative, and superlative degrees, and can be interchanged. Additionally, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "early," "slow," "wide," and "narrow," etc., as expressions with "i" appended (i being any integer), are not limited to the positive, comparative, and superlative degrees, and can be interchanged (for example, "highest" can also be interchanged with "i-th highest").

[0553] In this disclosure, "of", "for", "regarding", "related to", "associated with", etc., can also be rewritten interchangeably.

[0554] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "based on A", "B during / while A", "before A", "at the same time as / on A", "after A", "since A", and "until A" can be rewritten interchangeably. Furthermore, A and B can be replaced with nouns, gerunds, or ordinary sentences, depending on the context. Additionally, the time difference between A and B can be approximately 0 (immediately following or immediately preceding). Moreover, a time offset can be applied to the time A occurs. For example, "A" can be rewritten interchangeably with "before / after the time offset of A". This time offset (e.g., more than one symbol / slot) can be predetermined or determined by the UE based on the information it is notified of.

[0555] In this disclosure, timing, moment, time, time instance, arbitrary time unit (e.g., time slot, sub-time slot, symbol, subframe), period, opportunity, resource, etc., can also be overridden.

[0556] The inventions disclosed herein have been described in detail above. However, it will be apparent to those skilled in the art that the inventions disclosed herein are not limited to the embodiments described herein. The description herein is for illustrative purposes only and is not intended to limit the inventions disclosed herein in any way.

[0557] This vow is based on Special Vow 2023-70548, made on April 24, 2023. Its entire contents are contained herein.

Claims

1.A terminal, comprising: a reception unit that receives a medium access control control element (MAC CE) related to cell switching; and a control unit that controls application of a setting for at least one of radio link monitoring (RLM), beam failure detection (BFD), and a physical uplink control channel (PUCCH) for a specific cell based on information included in the MAC CE. 2.The terminal according to claim 1, wherein the control unit determines the setting to be applied based on a category of a candidate cell. 3.The terminal according to claim 1, wherein the control unit applies the setting to a part of cells in a specific cell, and ignores the setting or does not apply the setting until a specific condition is satisfied for another part of cells in the specific cell. 4.The terminal according to claim 1, wherein in a case where the setting is not provided by higher layer signaling, or in a case where the setting for a candidate cell is not present, the control unit derives a reference signal (RS) corresponding to the setting. 5.A wireless communication method of a terminal, comprising: a step of receiving a medium access control control element (MAC CE) related to cell switching; and a step of controlling application of a setting for at least one of radio link monitoring (RLM), beam failure detection (BFD), and a physical uplink control channel (PUCCH) for a specific cell based on information included in the MAC CE. 6.A base station, comprising: a transmission unit that transmits a medium access control control element (MAC CE) related to cell switching; and a control unit that controls generation of information for a terminal to determine application of a setting for at least one of radio link monitoring (RLM), beam failure detection (BFD), and a physical uplink control channel (PUCCH) for a specific cell based on information included in the MAC CE.

Images