Terminals, wireless communication methods, base stations and systems

Abstract

A terminal according to one aspect of the present disclosure is characterized by comprising a reception unit that receives one or more serving cell settings for a serving cell and an additional cell and a control unit that controls the transmission to and reception from at least one of the serving cell and the additional cell on the basis of the one or more serving cell settings, and characterized in that each of the one or more serving cell settings includes settings relating to a plurality of bandwidth portions (BWP) and the setting relating to each BWP corresponds to at least one of the serving cell and the additional cell. According to one aspect of the present disclosure, cell-related settings can be appropriately performed.

Description

Technical Field

[0001] This disclosure relates to a terminal, a wireless communication method, 、 a base station and system in a next-generation mobile communication system.

Background Art

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was standardized for the purpose of further high data rates, low latency, etc. (Non-Patent Document 1). Also, for the purpose of further large capacity and sophistication of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9), LTE-Advanced (3GPP Rel. 10-14) was standardized.

[0003] Successor systems to LTE (for example, also referred to as 5th generation mobile communication system (5G), 5G+(plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later, etc.) are also being considered.

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

[0005] In wireless communication systems, it is being considered that one or more cells / transmission / reception points (TRPs) (multi-TRPs (MTRPs)) can perform downlink (DL) transmissions to terminals (user terminals, User Equipment (UEs)).

[0006] When multi-TRP is applied, a serving cell may be switched to a different PCI cell (additional cell) due to signaling at least one of Layer 1 and Layer 2 (Layer 1 / Layer 2 inter-cell mobility). However, if the cell (serving cell / additional cell) is not properly configured when a cell switch occurs, problems such as a decrease in communication throughput may occur.

[0007] Therefore, this disclosure relates to a terminal capable of appropriately configuring settings related to a cell, and a wireless communication method. 、 base station and system One of the objectives is to provide [this]. [Means for solving the problem]

[0008] A terminal relating to one aspect of this disclosure is Multiple candidates 1 for a cell Tsu Serving cell Regarding A receiving unit that receives the settings, and Recording Based on the above, Multiple candidates at least 1 to At least one of sending and receiving It has a control unit that controls the front The settings are , multiple bandwidth portions (BWP) index Includes each BWP index The above Multiple candidates It is characterized by corresponding to at least one cell.

Effect of the Invention

[0009] According to one aspect of the present disclosure, settings related to cells can be appropriately made.

Brief Description of the Drawings

[0010] [Figure 1] Figures 1A to 1D are diagrams showing configuration examples of multi-TRP. [Figure 2] Figure 2A is a diagram showing an example of UE movement in Rel. 17. Figure 2B is a diagram showing an example of UE movement in Rel. 18. [Figure 3] Figure 3 is a diagram showing an example of association between a serving cell and a candidate cell. [Figure 4] Figure 4A is a diagram showing a first example of ServingCellConfig for Option 1. Figure 4B is a diagram showing a second example of ServingCellConfig for Option 1. [Figure 5] Figure 5 is a diagram showing a first example of Option 2. [Figure 6] Figure 6A is a diagram showing a second example of Option 2. Figure 6B is a diagram showing a third example of Option 2. [Figure 7] Figure 7 is a diagram showing an example of a MAC entity / HARQ entity that reuses a CA / DC framework. [Figure 8] Figures 8A to 8C are diagrams showing examples of cell group settings corresponding to Figure 7. [Figure 9] Figure 9 is a diagram showing an example of serving cell change. [Figure 10] Figure 10A is a diagram showing Serving Cell Switch Example 1. Figure 10B is a diagram showing Serving Cell Switch Example 2. [Figure 11] Figure 11 is a diagram showing an example of association between a tag and a candidate cell. [Figure 12] Figure 12 is a diagram showing a setting example of ServingCellConfig for a cell (CC). [Figure 13] FIG. 13 is a diagram showing a setting example of ServingCellConfig in the first embodiment. [Figure 14] FIG. 14 is a diagram showing a setting example of ServingCellConfig in Embodiment 1-1. [Figure 15] FIG. 15 is a diagram showing a setting example of ServingCellConfig in Embodiment 1-2. [Figure 16] FIG. 16 is a diagram showing a serving cell setting in Example 1. [Figure 17] FIG. 17 is a diagram showing a cell group setting (CellGroupConfig) in Example 2. [Figure 18] FIG. 18 is a table showing PCI numbers and serving cell setting numbers in Example 2. [Figure 19] FIGS. 19A to 19C show modified examples of a table showing PCI numbers and serving cell settings set for each band / cell group. [Figure 20] [[ID=​​​​​​​​​​​​​​​​​​​​​​ [Figure 28] Figure 28 shows an example of the configuration of a base station according to one embodiment. [Figure 29] Figure 29 shows an example of the configuration of a user terminal according to one embodiment. [Figure 30] Figure 30 shows an example of the hardware configuration of a base station and a user terminal according to one embodiment. [Figure 31] Figure 31 shows an example of a vehicle according to one embodiment. [Modes for carrying out the invention]

[0011] (Multi-TRP) In NR, it is being considered that one or more transmission / reception points (TRPs) (multi-TRPs) will use one or more panels (multi-panels) to perform DL transmissions to the UE. Furthermore, it is being considered that the UE will perform UL transmissions to one or more TRPs.

[0012] Multiple TRPs may correspond to the same cell identifier (Cell Identifier (ID)) or to different cell IDs. This cell ID may be a physical cell ID or a virtual cell ID.

[0013] Figures 1A-1D show examples of multi-TRP scenarios. In these examples, it is assumed, but not limited to, that each TRP can transmit four different beams.

[0014] Figure 1A shows an example of a case where only one TRP (TRP1 in this example) among the multi-TRPs transmits to the UE (this may also be called single-mode or single-TRP). In this case, TRP1 transmits both control signals (PDCCH) and data signals (PDSCH) to the UE.

[0015] Figure 1B shows an example of a case where only one of the multi-TRPs (TRP1 in this example) transmits control signals to the UE, and that multi-TRP transmits data signals (this may also be called single-master mode). The UE receives each PDSCH transmitted from the multi-TRP based on a single Downlink Control Information (DCI).

[0016] Figure 1C shows an example of a case where each of the multi-TRPs transmits a portion of the control signal to the UE, and the multi-TRP transmits the data signal (this may be called master-slave mode). Part 1 of the control signal (DCI) may be transmitted by TRP1, and part 2 of the control signal (DCI) may be transmitted by TRP2. Part 2 of the control signal may depend on part 1. The UE receives each PDSCH transmitted from the multi-TRP based on these parts of the DCI.

[0017] Figure 1D shows an example of a multi-TRP where each of the multi-TRPs transmits a separate control signal to the UE, and the multi-TRP transmits data signals (this may also be called multi-master mode). TRP1 may transmit a first control signal (DCI), and TRP2 may transmit a second control signal (DCI). The UE receives each PDSCH transmitted from the multi-TRP based on these DCIs.

[0018] When scheduling multiple PDSCHs from a multi-TRP (which may also be called multiple PDSCHs) as shown in Figure 1B using a single DCI, that DCI may be called a single DCI (S-DCI, single PDCCH). Similarly, when scheduling multiple PDSCHs from a multi-TRP (as shown in Figure 1D) using multiple DCIs, these multiple DCIs may be called multiple DCIs (M-DCI, multi-PDCCH (multiple PDCCH)).

[0019] Each TRP in a multi-TRP system may transmit different transport blocks (TBs), code words (CWs), and layers. Alternatively, each TRP in a multi-TRP system may transmit the same TB, CW, and layer.

[0020] Non-Coherent Joint Transmission (NCJT) is being considered as one form of multi-TRP transmission. In NCJT, for example, TRP1 modulates and layers a first codeword and transmits a first PDSCH using a first precode with a first number of layers (e.g., 2 layers). TRP2 modulates and layers a second codeword and transmits a second PDSCH using a second precode with a second number of layers (e.g., 2 layers).

[0021] Furthermore, multiple PDSCHs (Multi-PDSCHs) that are NCJTed may be defined as partially or completely overlapping with respect to at least one of the time and frequency domains. In other words, a first PDSCH from a first TRP and a second PDSCH from a second TRP may overlap in at least one of the time and frequency resources.

[0022] These first and second PDSCHs may be assumed not to be quasi-co-located. Reception of multiple PDSCHs may be reinterpreted as simultaneous reception of PDSCHs that are not of a certain QCL type (e.g., QCL type D).

[0023] In URLLC for multiple TRPs, support for PDSCH (Transport Block (TB) or Codeword (CW)) repetition spanning multiple TRPs is being considered. Support for repetition schemes (URLLC schemes, e.g., schemes 1, 2a, 2b, 3, 4) spanning multiple TRPs on the frequency domain, layer (spatial) domain, or time domain is being considered. In scheme 1, multiple PDSCHs from multiple TRPs are performed using space division multiplexing (SDM). In schemes 2a and 2b, PDSCHs from multiple TRPs are performed using frequency division multiplexing (FDM). In scheme 2a, the redundant version (RV) is the same for multiple TRPs. In scheme 2b, the RV may be the same or different for multiple TRPs. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are performed using time division multiplexing (TDM). In Scheme 3, multi-PDSCH signals from multi-TRPs are transmitted within a single slot. In Scheme 4, multi-PDSCH signals from multi-TRPs are transmitted within different slots.

[0024] Such multi-TRP scenarios allow for more flexible transmission control using high-quality channels.

[0025] NCJT using multiple TRPs / panels may utilize high ranks. To support ideal and non-ideal backhauls between multiple TRPs, both single DCI (single PDCCH, e.g., Figure 1B) and multi-DCI (multi-PDCCH, e.g., Figure 1D) may be supported. For both single and multi-DCI, the maximum number of TRPs may be 2.

[0026] An extension of the TCI is being considered for single PDCCH designs (primarily for ideal backhaul). Each TCI code point within the DCI may correspond to one or two TCI states. The TCI field size may be the same as that of Rel. 15.

[0027] (L1 / L2 cell-to-cell mobility) As described above, it is being considered that a UE may send a UL to one or more cells / TRPs. In this case, the following Scenario 1 or Scenario 2 is possible. In this disclosure, a serving cell may be interpreted as a TRP within a serving cell. Layer 1 / layer 2 (L1 / L2) and DCI / Medium Access Control Control Element (MAC CE) may be interpreted as mutually exclusive. In this disclosure, a PCI different from the Physical Cell Identity (PCI) of the current serving cell may simply be referred to as a "different PCI". Non-serving cells, cells with different PCIs, and additional cells may be interpreted as mutually exclusive.

[0028] <Scenario 1> Scenario 1 may, for example, support inter-cell mobility in a multi-TRP (Trans-Traffic Relay Program), but it may also be a scenario that does not support inter-cell mobility in a multi-TRP.

[0029] (1) The UE receives from the serving cell the settings for the SSB for beam measurement of the TRP corresponding to a PCI different from that of the serving cell, and the settings necessary to use wireless resources for data transmission and reception, including resources for a different PCI. (2) The UE performs beam measurements of the TRP corresponding to the different PCIs and reports the beam measurement results to the serving cell. (3) Based on the above report, the Transmission Configuration Indication (TCI) status associated with the TRP corresponding to the different PCI is activated by L1 / L2 signaling from the serving cell. (4) UEs send and receive data using dedicated channels on the TRP that correspond to different PCIs. (5) The UE must always cover the serving cell, including in the case of multi-TRP. The UE must use common channels from the serving cell (such as the Broadcast Control Channel (BCCH) and the Paging Channel (PCH)), as in conventional systems.

[0030] 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 UE's assumption of the serving cell) remains unchanged. The UE sets higher-layer parameters related to the PCI of the non-serving cell from the serving cell. Scenario 1 may be applied, for example, in Rel. 17.

[0031] Figure 2A shows an example of UE movement in Rel.17. Suppose the UE moves from a PCI#1 cell (serving cell) to a PCI#3 cell (additional cell) (overlapping with the serving cell). In this case, Rel.17 does not allow switching of the serving cell via L1 / L2. The additional cell is a cell with a different additional PCI than the serving cell. The UE can receive / transmit UE-dedicated channels from the additional cell. The UE needs to be within the serving cell's coverage to receive UE-common channels (e.g., system information / paging / short messages).

[0032] <Scenario 2> In Scenario 2, L1 / L2 inter-cell mobility is applied. With L1 / L2 inter-cell mobility, serving cell changes can be made using functions such as beam control without RRC reconfiguration. In other words, transmission and reception with additional cells are possible without handover. Since handover requires RRC reconnection and other factors, resulting in a period of data communication interruption, applying L1 / L2 inter-cell mobility, which does not require handover, allows data communication to continue even when the serving cell is changed. Scenario 2 may be applied, for example, in Rel.18. In Scenario 2, for example, the following procedure is performed.

[0033] (1) The UE receives the SSB settings for a cell with a different PCI (additional cell) from the serving cell for beam measurement / serving cell changes. (2) The UE performs beam measurements of the cell using different PCIs and reports the measurement results to the serving cell. (3) The UE may receive the configuration of cells with different PCIs (serving cell configuration) through upper-layer signaling (e.g., RRC). In other words, pre-configuration regarding serving cell changes may be performed. This configuration may be performed together with the configuration in (1) or separately. (4) Based on the above report, the TCI status of cells with different PCIs may be activated by L1 / L2 signaling in accordance with the change in the serving cell. The activation of the TCI status and the change in the serving cell may be performed separately. (5) The UE changes the serving cell (assumed to be the serving cell) and starts receiving / transmitting using the pre-configured individual UE channel and TCI state.

[0034] In other words, in Scenario 2, the serving cell (the assumed serving cell in the UE) is updated by L1 / L2 signaling. Scenario 2 may also be applied in Rel. 18.

[0035] Figure 2B shows an example of UE migration in Rel.18. In Rel.18, serving cells are switched via L1 / L2. UEs can receive / transmit UE-dedicated / common channels to and from the new serving cell. UEs may be outside the coverage of the previous serving cell.

[0036] (Setting multiple candidate cells) Figure 3 shows an example of the association between serving cells and candidate cells. SpCell#0, SCell#1, or SCell#2 are assumed to be serving cells. SpCell means a special cell (including primary cells (PCell) and primary secondary cells (PSCell)). SCell means a secondary cell. SpCell#0 is associated with candidate cells #0-1, #0-2, and #0-3. SCell#1 is associated with candidate cell #1-1. SCell#2 is associated with candidate cells #2-1 and #2-2. Thus, a serving cell may be associated with one or more candidate cells (candidate serving cells).

[0037] Regarding the setting of candidate cells (candidate cells) when changing the serving cell, the following options 1 and 2 are possible, for example.

[0038] <Option 1> Similar to inter-cell mobility in Rel.17, the information in ServingCellConfig may include information about multiple candidate cells. In this case, the multiple candidate cells must share the same PDCCH / PDSCH / UL settings as the serving cell.

[0039] For example, in Rel.17's inter-cell mobility, it is being considered that "mimoParam-r17" will be added under ServingCellConfig to include PCI configuration information (Figures 4A and 4B). This framework applies when cells with different PCIs share the same PDCCH / PDSCH / UL settings.

[0040] For each candidate cell, more settings may be applied, such as LTE CRS patterns and RACH settings. Furthermore, by considering cell-specific CSI-RS settings (for CSI / TRS), different CSI-RS opportunities / resources can be configured for each cell, thereby reducing interference.

[0041] Figure 4A shows a first example of ServingCellConfig for Option 1. In Figure 4A, ServingCellConfig includes settings for additional cells (each candidate cell). Figure 4B shows a second example of ServingCellConfig for Option 1. In Figure 4B, ServingCellConfig includes settings for additional cells (each candidate cell) for L1 / L2 cell-to-cell mobility. Figure 4A corresponds to, for example, Scenario 1 above. Figure 4B corresponds to, for example, Scenario 2 above.

[0042] As shown in Figures 4A and 4B, candidate cells are pre-configured by RRC. Initially, candidate cells may be fixed to activated / deactivated in the specification, or they may be set to activated / deactivated by RRC. Furthermore, candidate cells for L1 / L2 cell switching may be activated / deactivated by MAC CE. L1 / L2 cell switching instructions may be sent only from cells that are active.

[0043] <Option 2> Multiple candidate cells may be associated with each serving cell by reusing the carrier aggregation (CA) configuration framework, with each cell having its own complete configuration (e.g., ServingCellConfig). The UE can communicate appropriately with the candidate cells because it is provided with the complete configuration for each candidate cell.

[0044] The CA configuration framework allows for configuring SpCells for each cell group and adding multiple SCells. By reusing the CA framework, a serving cell and multiple candidate cells may be configured for each cell group of L1 / L2 inter-cell mobility (Figure 5). Candidate cells may be activated / deactivated by MAC CE. This method is considered beneficial for reducing the complexity of UE operation. An example of CellGroupConfig for cell group ID 0 is shown.

[0045] Figure 6A shows a second example of Option 2. In the example in Figure 6A, a common candidate cell pool for cell switching in the MCG / SCG is applied to the candidate cells. In other words, the candidate cells are treated as a single pool (group) regardless of the frequency band.

[0046] Figure 6B shows a third example of Option 2. In the example in Figure 6B, multiple cell groups are configured, and cell group switching is possible via L1 / L2 signaling. Candidate cells are configured for each cell group, and the configuration for each group includes the corresponding SpCell and SCell indices. As an example, the CellGroupConfig for cell group ID 1 is shown.

[0047] (Reuse of the CA / DC framework) When reusing the CA / DC framework, the network (base station) may explicitly or implicitly issue new instructions to the UE for each cell group, setting up multiple candidate cells to associate with the serving cell.

[0048] Figure 7 shows an example of MAC entities / HARQ entities that reuse the CA / DC framework. The cells in the box shown in A of Figure 7 are cells of a cell group (MCG / SCG) for CA / DC operation. Each cell corresponds to a different frequency. The cells in the box shown in B of Figure 7 are cells of a cell group for L1 / L2 inter-cell mobility operation, an example where the serving cell is a SpCell. Each cell in B corresponds to the same frequency. The cells in the box shown in C of Figure 7 are cells of a cell group for L1 / L2 inter-cell mobility operation, an example where the serving cell is an SCell. Each cell in C corresponds to the same frequency.

[0049] In other words, in CA / DC, each cell corresponds to a different frequency (CC), but in L1 / L2 inter-cell mobility (multi-TRP), each cell (a cell with a different PCI) corresponds to the same frequency (CC). Candidate cell #X in C may be different from candidate cell #1 in B (they may have different PCI / frequency). X may be a re-created index at a certain frequency, for example, starting from 1. The re-created index may correspond to at least one part of the PCI and may be an index created for the candidate cell.

[0050] In another example, even in the case of L1 / L2 inter-cell mobility, each cell (SpCell / Scell, Candidate cell) may correspond to a different frequency. However, each cell may share the same HARQ entity corresponding to PDSCH scheduling.

[0051] Figures 8A to 8C show examples of cell group settings corresponding to Figure 7. Figures 8A to 8C correspond to the cells (cell groups) within frames A, B, and C in Figure 7, respectively. "cellGroupId", "new indicator for cell group purpose", "spCellConfig", and "sCellToAddModList" correspond to the cells (cell groups) within frames A, B, and C in Figure 7, respectively.

[0052] In this way, by reusing the CA / DC framework for L1 / L2 inter-cell mobility operations, cell group settings related to L1 / L2 inter-cell mobility can be configured without adding new RRC information elements.

[0053] (Signaling for serving cell change instructions) This section describes implicit and explicit signaling for serving cell change instructions.

[0054] [Aspect 1] Embodiment 1 describes implicit signaling for serving cell change instructions.

[0055] [[Option 1-1]] If a specific Control Resource Set (CORESET) (for example, CORESET#0, the CH5 Type0-CSS CORESET, or at least one of the CH6 / CH7 / CH8 CSS CORESETs) is indicated (activated) by MAC CE along with one or more TCI states associated with a cell having a different PCI than the serving cell (i.e., if one or more TCI states associated with a cell having a different PCI than the serving cell are indicated / activated by MAC CE for a specific CORESET), then the UE may decide to change the serving cell to another cell (cell x, a cell with a different PCI). In other words, this activation may implicitly indicate that the serving cell will be changed to another cell.

[0056] In this case, the UE may update the beams of other CORESET IDs, other CORESETs using CH6 / CH7 / CH8, or other CORESETs using CSS to the same TCI state as the activated TCI state described above.

[0057] [[Options 1-2]] When MAC CE activates / deactivates a TCI state of PDSCH, if all such TCI states activated by MAC CE are associated with the same cell x that has a different PCI than the serving cell, the UE may decide to change the serving cell to another cell (cell x). In other words, this association may implicitly indicate a change of the serving cell to another cell.

[0058] In cases where this option applies, if the NW (base station) does not change the serving cell, when MAC CE activates the TCI state of the PDSCH associated with a cell with a different PCI, it must also include the TCI state associated with another cell (for example, the current serving cell or a second cell with a different PCI).

[0059] [[Options 1-3]] If MAC CE activates / deactivates a Unified TCI state (e.g., corresponding to the Unified TCI Framework in Rel. 17), and all activated Unified TCI states are associated with the same cell x having different PCIs, then UE may decide to change the serving cell to another cell (cell x). In other words, this association may implicitly indicate a change in the serving cell to another cell.

[0060] [Aspect 2] Embodiment 2 describes explicit signaling for serving cell change instructions. Embodiment 2 applies, for example, to Scenario 2 described above.

[0061] [[Option 2-1]] The following is an example of a serving cell change instruction. Note that activating / deactivating a non-serving cell, changing a serving cell, and sending / receiving data to / from another cell (non-serving cell) with a different physical cell ID than the serving cell's physical cell ID may be interpreted interchangeably.

[0062] The UE may receive a new MAC CE containing at least one of the following fields (information) indicating the non-serving cell, which is used to activate / deactivate the non-serving cell. Upon receiving such a MAC CE, the UE may decide to change the serving cell to another cell (non-serving cell). The UE may also control the transmission and reception of DL / UL signals with the non-serving cell based on this information. There may be one or more non-serving cells. In the example below, a MAC CE containing multiple fields indicating multiple non-serving cell indices is applied.

[0063] (1) Serving cell ID. (2) BWP ID. (3) Non-serving cell ID to be used for activation. The non-serving cell ID may be replaced with any information that corresponds to the non-serving cell (that can identify the non-serving cell).

[0064] As an example of (3), any of (3-1) to (3-5) may be applied. (3-1) PCI (direct PCI). For example, 10 bits are used. (3-2) Re-indexing of non-serving cells (new ID). The new ID may be associated with a portion of the PCI and may be set only for serving cells and non-serving cells that the UE uses (is available for). The new ID may have fewer bits than the PCI. (3-3) CSI Report Configuration ID (CSI-ReportConfigId) (if CSI-ReportConfig corresponds to one or more non-serving cells). (3-4) CSI Resource Configuration ID (CSI-ResourceConfigId) (if CSI-ResourceConfigId corresponds to one or more non-serving cells). (3-5) A bitmap indicating the activation / deactivation status of each non-serving cell. The size (number of bits) of the bitmap may be the same as the number of non-serving cells set on this CC. For example, if the second of three non-serving cells is to be activated, "010" will be set.

[0065] At least one piece of information contained in the MAC CE may be included in the DCI. Alternatively, at least one of the serving cells activated by the MAC CE may be indicated by the DCI. The MAC CE / DCI may include a field indicating the TCI status / SSB / CSI-RS from cells with different PCIs so that the UE can recognize the DL beam being monitored on the target cell (the modified serving cell). The UE may use the TCI status / SSB / CSI-RS to create and transmit a beam report (CSI report).

[0066] [[Option 2-2]] The UE may receive a MAC CE with a new 1-bit field "C" added to the existing MAC CE. This field indicates whether to change the serving cell. The UE may receive the MAC CE and, based on this field, decide whether to change the serving cell to another cell.

[0067] [[Options 2-3]] In addition to the MAC CE in Option 2-2, the MAC CE may also include fields indicating the serving cell index / PCI / other IDs (such as the new ID in Option 2-1 above) and the TCI status / SSB / CSI-RS fields of the target cell (the serving cell after the change).

[0068] Thus, since the instruction for changing the serving cell is issued by MAC CE / DCI, the UE can appropriately change the serving cell.

[0069] FIG. 9 is a diagram showing an example of serving cell change. For example, in the serving cell SpCell#0 of MCG / SCG, when it is instructed to change the serving cell to candidate cell #0-2 by L1 / L2 signaling, candidate cell #0-2 becomes the new serving cell SpCell#0. Also, for example, in the serving cell SCell#2 of MCG / SCG, when it is instructed to change the serving cell to candidate cell #2-1 by L1 / L2 signaling, candidate cell #2-1 becomes the new serving cell SCell#2.

[0070] <L1 Beam Measurement / Report> When L1 / L2 inter-cell mobility is applied, L1-RSRP beam measurement / report from additional PCI cells in Rel.17 may be applied. L1 beam measurement / report by event trigger may be performed. L1 beam measurement / report and L3 measurement / report may correspond to each other.

[0071] <L1 Beam Indication and L1 / L2 Cell Switch Indication> In Rel.17, L1 beam indication to TCI states related to additional PCI is supported. As described above, a new L1 / L2 signal for indicating cell switch is required. For example, both implicit indication (e.g., when a certain CORESET is updated to a TCI state related to additional PCI by MAC CE) and explicit indication (e.g., indication using DCI / MAC CE) methods are considered.

[0072] [Example of Serving Cell Switch 1] RRC / MAC CE can set global candidate cell IDs (cell#0,...,5) for each cell group, band, FR, and UE. The UE may be instructed to switch the serving cell by the global candidate cell ID.

[0073] Figure 10A shows an example of serving cell switching 1. Similar to Figure 6A, a pool of multiple candidate cells is set up, and a serving cell can be switched to any (activated) candidate cell in the pool using L1 / L2 signaling. In this case, the set candidate cell can become either a SpCell or an SCell based on L1 / L2 signaling. This is a cell pool that serves as a candidate for cell switching for all serving cells.

[0074] The UE receives a command via MAC CE / DCI to change the serving cell (from cell #2 to cell #2-1). The commanded cell #2-1 then becomes the SpCell of the new cell group. For cells other than SpCells, Cell #1-0 becomes SCell #1, and Cell #2-0 becomes SCell #2.

[0075] [Serving cell switch example 2] The RRC / MAC CE can set global candidate cell IDs (cell#0-1, #0-1, ..., 2-2) for each cell group, band, FR, and UE. The UE may be instructed to switch serving cells by these global candidate cell IDs.

[0076] Figure 10B shows an example of a serving cell switch, 2. The UE receives a command via MAC CE / DCI to change the serving cell (from cell #2-0 to cell #2-1). The commanded cell #2-1 then becomes the SpCell of the new cell group. For cells other than SpCells, either option 1 or 2 below applies.

[0077] 《Option 1》 Based on the order of the global candidate cell IDs, cell#0-0 becomes Scell#1, and cell#1-0 becomes Scell#2 (example in Figure 10B).

[0078] 《Option 2》 Cell #1-0 becomes Scell ​​#1 (unchanged), and cell #0-0 (the previous SpCell) becomes Scell ​​#2. In other words, it is controlled to minimize changes.

[0079] (Tag management) Each candidate cell may be associated with a tag. Different serving cells and different candidate cells may be associated with the same tag. RACH to candidate cells may be supported to obtain the tag of a candidate cell. Tags may be set / instructed to the UE by upper-layer signaling / physical-layer signaling.

[0080] Figure 11 shows an example of the association between tags and candidate cells. In the example in Figure 11, SpCell#0 and SCell#1 have the same tag. Also, candidate cells #0-1 and candidate cells #1-1 have the same tag. Note that all serving cells may have different tags. Also, all candidate cells may have different tags.

[0081] (Example of ServingCellConfig settings) In Rel.18, in order to enable L1 / L2 serving cell switching, it is being considered that the UE may pre-configure some or all of the serving cell settings for non-serving cells (additional cells, additional PCIs, candidate cells) in the UE. The ServingCellConfig shown in the example of Option 1 (configuration of multiple candidate cells) in Figure 4 above may be applied to the additional cell to configure all or some of the parameters for the additional cell.

[0082] Alternatively, as described in Option 2 of the above (setting multiple candidate cells), all parameters in ServingCellConfig may be set for the additional cell. This allows for flexible configuration as different ServingCellConfigs can be set for different cells. However, ServingCellConfig is a very large RRC structure, which may result in significant RRC overhead.

[0083] Figure 12 shows an example of setting a ServingCellConfig for a cell (CC). The serving cell is #0-0, and the candidate cells are #0-1 to #0-7. #0-0 is a PScell, but the same applies if it's an SCell. In this example, a separate ServingCellConfig is set for each cell (serving cell and additional cells). This may increase the overhead of the RRC.

[0084] (analysis) As described above, when multi-TRP is applied, a serving cell may be switched to a PCI cell (additional cell) of a different layer due to signaling at least one of Layer 1 and Layer 2 (L1 / L2 inter-cell mobility). However, if the settings for the cell (serving cell / additional cell) are not properly configured when a cell switch occurs, problems such as a decrease in communication throughput may occur. For example, in the example in Figure 12, the RRC overhead may increase.

[0085] Therefore, the inventors conceived of a terminal, a wireless communication method, and a base station in which cell switching is performed appropriately.

[0086] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.

[0087] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0088] In this disclosure, terms such as notice, activate, deactivate, indicate, select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and operable may be interpreted interchangeably.

[0089] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Element (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0090] In this disclosure, the upper-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

[0091] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0092] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).

[0093] In this disclosure, terms such as index, identifier (ID), indicator, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, and subset may be interpreted interchangeably.

[0094] Applying an instructed TCI state, switching a TCI state, and switching a cell (serving cell) may be interpreted as being interchangeable. In this disclosure, cell switching may mean switching a serving cell.

[0095] In this disclosure, cell group, serving cell group, master cell group (MCG), and secondary cell group (SCG) may be interpreted interchangeably. L1 / L2, L1 / L2 signaling, and DCI / MAC CE may be interpreted interchangeably. A serving cell may be replaced with a cell that transmits a PDSCH. A candidate cell may mean a cell that is a candidate to become a serving cell through L1 / L2 inter-cell mobility.

[0096] In this disclosure, cell, PCI, serving cell, source serving cell, CC, BWP, BWP within CC, and band may be interpreted interchangeably. In this disclosure, additional cell, other cell, non-serving cell, cell with a different PCI, candidate cell, candidate serving cell, cell with a PCI different from the current serving cell's PCI, another serving cell, and target cell may be interpreted interchangeably. In this disclosure, switch, change, and update may be interpreted interchangeably. Serving cell may be interpreted as a serving cell before a switch or a serving cell after a switch.

[0097] (Wireless communication method) <First Embodiment> The UE may receive one or more ServingCellConfigs (settings / parameters of some or all of the ServingCellConfigs) for the serving cell and additional cells (candidate cells) by the method of option 1 or 2 described above (settings of multiple candidate cells). Based on the one or more ServingCellConfigs, the UE may control the sending and receiving of at least one of the serving cell and additional cells. Each of the one or more ServingCellConfigs is a setting for multiple additional cells (e.g., ServingCellConfig#1 or #2 below), or a setting for one serving cell and one or more additional cells (e.g., ServingCellConfig#0 below). The number of ServingCellConfigs set for additional cells may differ from the number of additional cells (PCIs of additional cells) (e.g., it may be less than the number of additional cells).

[0098] The configured ServingCellConfig is set along with a new cell index (ServingCellConfig#0,1,2, etc.), and each of the new cell indexes may be associated with a PCI (serving cell PCI or additional cell PCI).

[0099] If a UE is instructed to switch serving cells via L1 / L2 (DCI or MAC CE), it may use the ServingCellConfig associated with the new candidate cell (the cell in the instructed PCI). In other words, the UE may update the current serving configuration based on the ServingCellConfig associated with the new candidate cell.

[0100] Figure 13 shows an example of ServingCellConfig configuration in the first embodiment. In the notation #xy, x is the index of the component carrier (CC), and y is the new index corresponding to the additional PCI. As shown in Figure 13, ServingCellConfig#0 shows the configuration for serving cells #0-0 and additional cells #0-1. ServingCellConfig#1 shows the configuration for additional cells #0-2 to #0-4. ServingCellConfig#2 shows the configuration for additional cells #0-5 to #0-7. In other words, one ServingCellConfig shows the configuration for one or more serving cells / additional cells.

[0101] However, cells (serving cells / additional cells) to which the same ServingCellConfig is set do not necessarily have to have all the same settings; some (most) of the settings may be the same. For example, a ServingCellConfig like the one shown in Figure 4 may be applied. In other words, by sharing the same setting information (parameters) for multiple cells and explicitly setting only the different settings within a single ServingCellConfig, signaling overhead can be reduced.

[0102] As described above, signaling overhead can be suppressed by commonizing at least one part of the ServingCellConfig for multiple cells.

[0103] [Embodiment 1-1] The same serving cell configuration (the same set / combination of ServingCellConfig numbers) may be shared between different CCs (frequency bands) and different PCI cells. This embodiment may be combined, for example, with option 2 of the above-described configuration of multiple candidate cells.

[0104] Figure 14 shows an example of ServingCellConfig settings in Embodiment 1-1. In Figure 14, up to two ServingCellConfigs can be used for additional PCIs (candidate cells) between different (multiple) CCs. In the example in Figure 14, ServingCellConfig #0-#2 are shared between CC#0 and CC#1. Note that different ServingCellConfig numbers may be set for each CC, and the settings of each ServingCellConfig may be the same.

[0105] In Figure 14, the association settings between cell numbers and ServingCellConfig numbers may be the same across multiple CCs (CC#0 and CC#1) (a pair of cells corresponding to one ServingCellConfig). In this case, the UE may assume that the association settings are the same for different CCs. This simplifies the UE implementation. Alternatively, the UE may assume that the association settings are the same or different across multiple CCs. This improves the flexibility of the base station (gNB).

[0106] According to Embodiment 1-1, the overhead of RRC signaling can be suppressed by sharing ServingCellConfig among different (multiple) CCs.

[0107] [Embodiment 1-2] Separate serving cell configurations (different sets / combinations of ServingCellConfig numbers) may be set in different CCs. This embodiment may be combined, for example, with option 1 or 2 of the above-described (configuration of multiple candidate cells).

[0108] Figure 15 shows an example of ServingCellConfig configuration in Embodiment 1-2. In Figure 15, up to two ServingCellConfigs can be used for additional PCIs (candidate cells) between different (multiple) CCs. In the example in Figure 15, ServingCellConfig#0-0, #0-1, and #0-2 are used in CC#0. Also, ServingCellConfig#1-0, #1-1, and #1-2 are used in CC#0.

[0109] In Figure 15, the association settings between cell numbers and ServingCellConfig numbers may be the same across multiple CCs (CC#0 and CC#1) (i.e., the same set of cells corresponding to a single ServingCellConfig). In this case, the UE may assume that the association settings are the same for different CCs. This simplifies the implementation of the UE. Alternatively, the UE may assume that the association settings are the same or different across multiple CCs. This improves the flexibility of the base station (gNB).

[0110] According to Embodiment 1-2, flexible ServingCellConfig settings can be configured for each CC. For example, Embodiment 1-2 may be applied between PCell and SCell, while Embodiment 1-1 may be applied between SCells. This is because the ServingCellConfig between PCell and SCell is likely to be different, but the ServingCellConfig between different (multiple) SCells is likely to be the same (or nearly the same). This reduces the overhead of RRC signaling and allows for appropriate configuration of additional cells.

[0111] [Example 1] An example combining the first embodiment with option 1 (setting multiple candidate cells) described above will be explained. In other words, the ServingCellConfig of a serving cell may include settings for multiple candidate cells.

[0112] Figure 16 shows the serving cell settings for Example 1. The ServingCellConfig in Figure 16 corresponds to ServingCellConfig#0 in Figure 14. ServingCellConfig#1 corresponds to multiple additional cells (candidate cells) #2 to #4, as shown in Figure 14. ServingCellConfig#2 corresponds to multiple additional cells (candidate cells) #5 to #7. ServingCellConfig#1 and ServingCellConfig#2 may include some or all of the settings (parameters) of ServingCellConfig.

[0113] In the first example (example 1), the ServingCellConfig may include settings corresponding to ServingCellConfig#1 and ServingCellConfig#2 as "more configurations for each candidate cell" (apply the example in Figure 4A). In the second example (example 2), the ServingCellConfig may include settings corresponding to ServingCellConfig#1 and ServingCellConfig#2 as "additionalPCI and other configurations for each PCI" (apply the example in Figure 4B).

[0114] The additional PCI is the ID of the additional cell (candidate cell), and may also be the recreate index for the non-serving cell described above (additional PCI / new ID). Up to seven additional PCIs may be configured by RRC signaling (additionalPCI, ID for PCI in Figure 16). ID=0 may mean a serving cell PCI. A ServingCellConfig#ID may be set for each additional PCI. An existing ServingCellConfig may be used for the serving cell, and the ID of that ServingCellConfig may be #0.

[0115] [Example 2] An example combining the first embodiment with option 2 (configuration of multiple candidate cells) described above will be explained. In other words, multiple candidate cells may be associated with each serving cell by reusing the carrier aggregation (CA) configuration framework, with the complete configuration corresponding to each cell (e.g., ServingCellConfig) applied to each cell.

[0116] Figure 17 shows the cell group configuration (CellGroupConfig) for Example 2. When Example 1-1 is applied, ServingCellConfig#0, #1, and #2 are set separately. The cell group configuration includes the IDs of ServingCellConfig#0, #1, and #2. When Example 1-2 is applied, the cell group configuration includes the IDs of ServingCellConfig#0, #1, and #2 for each cell. Similar to Example 1, the recreated non-serving cell index (additional PCI / new ID) described above may be applied as the ID of the additional PCI (additional cell / candidate cell).

[0117] Figure 18 is a table showing the PCI numbers and serving cell configuration numbers for Example 2. As shown in Figure 18, the same PCI number and serving cell configuration are applied to each CC. PCI#0 and #1 correspond to ServingCellConfig#0. PCI#2 to #4 correspond to ServingCellConfig#1. PCI#5 to #7 correspond to ServingCellConfig#2.

[0118] The examples in Figures 16 to 18 show an example where Embodiment 1-1 is applied, but Embodiment 1-2 may be combined with option 1 or 2 of the above (setting multiple candidate cells). In this case, ServingCellConfig#0 is replaced with ServingCellConfig#0-0 or #1-0. Also, ServingCellConfig#1 and #2 are replaced with ServingCellConfig#0-1, #0-2 or ServingCellConfig#1-1, #1-2.

[0119] [Differentiation] A modified example of applying option 2 (setting multiple candidate cells) described above will be explained. Figures 19A to 19C and 20 show modified examples of tables that indicate PCI numbers and serving cell settings set for each band / cell group.

[0120] Figure 19A shows the first example of a table illustrating the relationship between PCI numbers and serving cell settings. Compared to Figure 18, Figure 19A omits the PCI number and only shows the serving cell settings.

[0121] Figure 19B shows a second example of a table illustrating the relationship between PCI numbers and serving cell settings. In Figure 19B, PCI numbers are omitted, and only serving cell settings are shown. In Figure 19B, different serving cell setting numbers are assigned to CC#0 and CC#1.

[0122] Figure 19C shows a third example of a table illustrating the relationship between PCI numbers and serving cell settings. In Figure 19C, PCI numbers are omitted, and only serving cell settings are shown. Also, in Figure 19C, a common serving cell setting number is assigned to each CC, resulting in a table with only one column per band / cell group. This example may also be applied to Embodiment 1-1.

[0123] Figure 20 shows a fourth example of a table illustrating the relationship between PCI numbers and serving cell configurations. Figure 20 assumes a case where a candidate cell pool is applied, as in Figures 6A and 10A. In the example in Figure 20, for example, candidate cell PCI#0, CC#0 serving cell, and CC#1 serving cell share a ServingCellConfig number. This means that serving cells and candidate cells can share serving cell configurations regardless of the frequency band.

[0124] <Second Embodiment> The UE may receive one or more ServingCellConfigs for the serving cell and the additional cell, and control the sending and receiving of data with at least one of the serving cell and the additional cell based on those one or more ServingCellConfigs.

[0125] [Embodiment 2-1] Each of the one or more ServingCellConfigs may include settings for multiple Bandwidth Parts (BWPs) (Figure 21). Each BWP setting corresponds to at least one of the Serving Cell and / or additional cells. Some of the RRC parameters of a ServingCellConfig are related to the BWPs of the ServingCellConfig. Hereafter, settings related to BWPs may be referred to as BWP settings.

[0126] Not all parameters in ServingCellConfig need to be set for each additional cell (additional PCI). If the base station (gNB) sets different BWPs for each cell / PCI in ServingCellConfig, the BWP may be switched by the existing BWP switching mechanism after the L1 / L2 serving cell switch.

[0127] For additional cells / PCIs, only a limited number of parameters can be set, and other parameters can be taken from the ServingCellConfig of the serving cell. For example, if a serving cell PCI and additional PCIs #1-7 exist, ServingCellConfig's BWP#0 will be used for the serving cell PCI and additional PCI #1, ServingCellConfig's BWP#1 will be used for additional PCIs #2-4, and ServingCellConfig's BWP#3 will be used for additional PCIs #5-7.

[0128] [Embodiment 2-2] For additional cells / PCIs, the BWP settings in ServingCellConfig to be used may be determined by upper-layer signaling or by the specification.

[0129] The BWP ID may be set / specified for each additional cell / PCI. If no BWP ID is set / specified for an additional cell / PCI, the same ID as the serving cell's BWP ID will be used for that additional cell / PCI.

[0130] In this disclosure, “ServingCellConfig” may be replaced with “BWP setting in ServingCellConfig (BWPConfig)”. According to Embodiment 2-1, the base station (gNB) does not need to trigger the BWP switch after the L1 / L2 serving cell switch.

[0131] Figure 22 shows an overview of Embodiment 2-2. ServingCellConfig's BWP#0 is used for the cell of Additional PCI #1, ServingCellConfig's BWP#1 is used for Additional PCIs #2-4, and ServingCellConfig's BWP#3 is used for Additional PCIs #5-6. ServingCellConfig may also include BWPConfig. This allows for setting different parameters in BWPConfig for Additional PCIs using a particular BWP (e.g., Additional PCIs #5-6) compared to Additional PCIs using other BWPs (see more configurations for each candidate cell in Figure 22). Furthermore, different parameters can be set for each Additional PCI.

[0132] In the example shown in Figure 22, different settings for each ServingCellConfig, each BWP (BWPConfig), and each additional PCI are sent to the UE via RRC signaling. This allows common parameters to be shared, thereby reducing the overhead of RRC signaling.

[0133] However, since the operation of the base station (gNB) becomes more complex as the number of BWP configurations (BWPConfig) increases, the number of BWP configurations for a single serving cell configuration (ServingCellConfig) may be limited to a predetermined number. For example, option 1 or 2 below may be applied.

[0134] 《Option 1》 A single ServingCellConfig may contain three BWP configurations. For example, a single ServingCellConfig may have BWP#1 for FR1's MCG, BWP#2 for FR1's SCG, and BWP#3 for FR2's SCG. The reason for distinguishing between FR1 and FR2 is that FR2 may have a narrower BWP configured for battery saving. Otherwise, two BWPConfigs, one for MCG and one for SCG, may be applied, as in Option 2.

[0135] 《Option 2》 A single ServingCellConfig may have two BWP configurations (BWPConfig). For example, a single ServingCellConfig may have BWP#1 for MCG and BWP#2 for SCG.

[0136] Options 1 and 2 may also be applied to ServingCellConfig. That is, as a variation of Option 1, only three ServingCellConfigs may be set. For example, ServingCellConfig#1 for FR1's MCG, ServingCellConfig#2 for FR1's SCG, and ServingCellConfig#3 for FR2's SCG may be set. As a variation of Option 2, only two ServingCellConfigs may be set. For example, ServingCellConfig#1 for MCG and ServingCellConfig#2 for SCG may be set.

[0137] <Third Embodiment> If no specific RRC parameters are set in the ServingCellConfig (or BWPConfig within ServingCellConfig) for the additional cell, the UE may (and may expect) use the same RRC parameters for the additional cell / PCI as the serving cell (ServingCellConfig#0) for those specific parameters. In this disclosure, ServingCellConfig#0 may mean the serving cell configuration used for the serving cell before the switch.

[0138] For example, if no PDCCH-Config exists in ServingCellConfig#1 / #2, the UE may assume that the PDCCH-Config of ServingCellConfig#0 is applied to ServingCellConfig#1 / #2. This can reduce RRC overhead. The third embodiment may be applied in combination with options 1 and 2 (configuration of multiple candidate cells) and the first / second embodiments.

[0139] Figure 23 shows an example of a ServingCellConfig in a third embodiment. ServingCellConfig#0-#2 may correspond, for example, to the example in Figure 13. ServingCellConfig#1 does not include PDCCH-Config, PDSCH-Config, or PUSCH-Config, and the UE assumes that the PDCCH-Config, PDSCH-Config, or PUSCH-Config of ServingCellConfig#0 will be applied to the additional cells corresponding to ServingCellConfig#1. ServingCellConfig#2 does not include PDCCH-Config, PUCCH-Config, PUSCH-Config, or SRS-Config, and the UE assumes that the PDCCH-Config, PUCCH-Config, PUSCH-Config, or SRS-Config of ServingCellConfig#0 will be applied to the additional cells corresponding to ServingCellConfig#2.

[0140] <Fourth Embodiment> The UE may receive and set different parameters (e.g., Cell Radio Network Temporary Identifier (C-RNTI)) for each additional cell (additional PCI, candidate cell) via MAC CE.

[0141] [Embodiment 4-1] 《Option 1》 Since there is no MAC entity reset for L1 / L2 inter-cell mobility, C-RNTI does not need to be changed.

[0142] 《Option 2》 The UE may receive the C-RNTI associated with each additional PCI (related to SpCell) via the MAC CE. When a SpCell is switched, the UE applies the new C-RNTI associated with the new SpCell from the C-RNTIs in the MAC CE and performs transmission / reception.

[0143] Similarly, if a SpCell is switched, the UE may receive and apply new CSI-RS settings associated with the new SpCell (e.g., periodic CSI-RS settings in the case of TRS). In other words, CSI-RS settings may also differ for each candidate cell. L1 beam measurement / reporting settings or CSI measurement / reporting settings may differ for each additional cell (candidate cell), or they may be pre-configured for each candidate cell.

[0144] Figure 24A shows the C-RNTI MAC CE of Rel.16. As shown in Figure 24A, the MAC CE contains one 16-bit C-RNTI.

[0145] Figure 24B shows a C-RNTI MAC CE of the fourth embodiment. As shown in Figure 24B, the MAC CE includes one C-RNTI (16 bits) per cell / PCI. Note that the number of C-RNTIs to be set is not limited to the example in Figure 24B.

[0146] [Differentiation] Figure 25 shows a modified C-RNTI MAC CE of the fourth embodiment. Similar to Figure 24B, the MAC CE contains one 16-bit C-RNTI per cell / PCI. x (C1~C7) indicates whether a C-RNTI is specified for each cell / PCI. For example, C x If it is 0, the C-RNTI of the corresponding cell / PCI is indicated, C x If it is 1, it means that the C-RNTI for the corresponding cell / PCI is not specified (the octet for the corresponding cell / PCI does not exist). For example, if C (8 bits from C1 to C7) is 00000101, the C-RNTI for cells / PCI#0 and #2 is specified.

[0147] Even if different (multiple) additional cells / PCIs share the same ServingCellConfig, some (a limited number of) parameters may be set per additional cell / PCI.

[0148] [Embodiment 4-2] The UE may have multiple C-RNTI values ​​set by higher-layer signaling (e.g., RRC / MAC CE). When a switch to an additional cell / PCI of the SpCell is instructed or completed, the UE may update the new C-RNTI associated with the additional cell / PCI to receive DL signals and transmit UL signals.

[0149] For example, (1) or (2) below may apply. (1) Setting / instructing multiple C-RNTI values ​​via upper-layer signaling also applies to cell#0 (the serving cell before the switch). (2) Setting / instructing multiple C-RNTI values ​​by upper-layer signaling is applicable only to Cell #1, 2, 3... (additional / candidate cells). The UE may obtain the setting / instruction of the C-RNTI value for Cell #0 using an existing C-RNTI MAC CE.

[0150] Figure 26 shows an example of C-RNTI settings in Embodiment 4-2. Figure 26 corresponds to (2) above. As shown in Figure 26, C-RNTI may be set for each of the Cell#1, 2, 3...7 (additional / candidate cells) by upper layer signaling. When applying (1) above, C-RNTI may also be set for cell#0 (serving cell before switch).

[0151] If there is no PRACH procedure for the new serving cell after a serving cell switch by L1 / L2, the UE may obtain a new C-RNTI using the method of this embodiment. If a PRACH procedure occurs, the UE may obtain the C-RNTI using the C-RNTI MAC CE, similar to existing specifications (e.g., Rel. 16).

[0152] Alternatively, the UE may apply the C-RNTI set / instructed by this embodiment, regardless of whether or not a RACH procedure (receiving a C-RNTI MAC CE for the new serving cell) has been performed.

[0153] <Supplement> [Notification of information to UE] In the embodiments described above, notification of any information from a Network (NW) (e.g., a Base Station (BS)) to a UE (in other words, reception of any information from a BS at the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0154] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader.

[0155] If the above notification is made by a DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble the Cyclic Redundancy Check (CRC) bits assigned to the DCI, or the format of the DCI.

[0156] Furthermore, the notification of any information to the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0157] [Notification of information from UE] In the embodiments described above, notification of any information from the UE (to the NW) (in other words, transmission / reporting of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0158] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID, not specified in existing standards, in the MAC subheader.

[0159] If the above notice is issued by the UCI, the notice may be sent using PUCCH or PUSCH.

[0160] Furthermore, the notification of any information from the UE in the above-described embodiments may be periodic, semi-persistent, or aperiodic.

[0161] [Regarding the application of each embodiment] At least one of the embodiments described above may be applied if certain conditions are met. These conditions may be specified in a standard or notified to the UE / BS using upper-layer signaling / physical layer signaling.

[0162] At least one of the embodiments described above may apply only to a UE that has reported or supports a particular UE capability.

[0163] The specific UE capability may represent at least one of the following: • To support specific processing / operation / control / information for at least one of the above embodiments. • Support for simultaneous switching of multiple serving cells. • The maximum number of serving cells that can be switched at one time. • Whether to limit multiple serving cells to Scell. • The number of ServingCellConfigs configured for each CC or across CCs (first embodiment). • Support for one-to-many associations between ServingCellConfig and PCI (first embodiment). Which of the following embodiments is supported: Embodiment 1-1 (applying a common ServingCellConfig to different CCs) or Embodiment 1-2 (applying separate ServingCellConfigs to different CCs)? • Support for setting different BWPs for different cells / PCIs (Embodiment 2-2). • To support the processing / operation / control / information of the third embodiment (additional cell / PCI).

[0164] Furthermore, the above-mentioned specific UE capabilities may be capabilities that apply across all frequencies (commonly regardless of frequency), capabilities per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), capabilities per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities per subcarrier spacing (SCS), or capabilities per feature set (FS) or feature set per component-carrier (FSPC).

[0165] Furthermore, the specific UE capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).

[0166] Furthermore, at least one of the embodiments described above may be applied when the UE is configured / activated / triggered by upper layer signaling / physical layer signaling to perform certain information (or the actions of the embodiments described above) related to the embodiments described above.

[0167] If the UE does not support at least one of the above-mentioned specific UE capabilities or does not have the above-mentioned specific information configured, the behavior of, for example, Rel.15 / 16 may be applied.

[0168] (Note) With respect to one embodiment of this disclosure, the following invention is added. [Note 1] A receiving unit that receives one or more serving cell settings for serving cells and additional cells, The system includes a control unit that controls transmission and reception with at least one of the serving cell and additional cells based on the one or more serving cell settings described above, Each of the one or more serving cell settings includes settings for multiple bandwidth portions (BWPs), and the settings for each BWP correspond to at least one of the serving cell and the additional cell. Terminal. [Note 2] The receiving unit receives, via upper-layer signaling, an instruction indicating which of the multiple BWP settings to use for the additional cell. The terminals listed in Appendix 1. [Note 3] If no specific parameters are set in the serving cell settings for the additional cell, the control unit will use the same parameters for the additional cell as for the serving cell. The terminals listed in Appendix 1 or Appendix 2. [Note 4] The receiving unit receives a different Cell Radio Network Temporary Identifier (C-RNTI) setting for each additional cell via a Media Access Control element (MAC CE). The terminals listed in any of the appendices 1 through 3.

[0169] (Wireless communication system) The configuration of a wireless communication system according to one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any or a combination thereof of the wireless communication methods according to the above embodiments of this disclosure.

[0170] Figure 27 shows an example of a schematic configuration of a wireless communication system according to one embodiment. Wireless communication system 1 (which may also be simply called system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

[0171] Furthermore, the wireless communication system 1 may support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and so on.

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

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

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

[0175] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).

[0176] Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may fall in a frequency band higher than FR2.

[0177] Furthermore, the user terminal 20 may communicate using at least one of the following methods at each CC: Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

[0178] Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, if NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node.

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

[0180] The core network 30 may include network functions (NF) such as User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Multiple functions may be provided by a single network node. Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.

[0181] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0182] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc., may be used in at least one of the downlink (DL) and uplink (UL).

[0183] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

[0184] In the wireless communication system 1, a Physical Downlink Shared Channel (PDSCH), a Broadcast Channel (PBCH), or a Physical Downlink Control Channel (PDCCH) may be used as the downlink channel, shared by each user terminal 20.

[0185] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0186] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

[0187] Lower-layer control information may be transmitted by PDCCH. The lower-layer control information may include, for example, Downlink Control Information (DCI) which includes scheduling information for at least one of PDSCH and PUSCH.

[0188] Furthermore, the DCI that schedules PDSCH may be called a DL assignment or DL ​​DCI, and the DCI that schedules PUSCH may be called a UL grant or UL DCI. Furthermore, PDSCH may be interpreted as DL data, and PUSCH may be interpreted as UL data.

[0189] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with a particular search space based on the search space configuration.

[0190] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

[0191] PUCCH may transmit uplink control information (UCI) which includes at least one of the following: channel state information (CSI), delivery acknowledgment (e.g., Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell.

[0192] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted when describing various channels.

[0193] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc., may be transmitted. In the wireless communication system 1, as DL-RS, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc., may be transmitted.

[0194] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. SS, SSB, etc., may also be called reference signals.

[0195] Furthermore, in the wireless communication system 1, the Uplink Reference Signal (UL-RS) may transmit the Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. The DMRS may also be called the User-Specific Reference Signal (UE-specific Reference Signal).

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

[0197] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0198] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

[0200] The transmitting / receiving unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0201] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.

[0202] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

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

[0204] The transmitting / receiving unit 120 may form at least one of the transmitting beam and the receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

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

[0207] The transmitting / receiving unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 130.

[0208] On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 130.

[0209] The transmitting / receiving unit 120 (receiving processing unit 1212) may apply reception processing to the acquired baseband signal, such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to acquire user data, etc.

[0210] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc., based on the received signal. The measurement unit 123 may also measure received power (e.g., Reference Signal Received Power (RSRP)), reception 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 may be output to the control unit 110.

[0211] The transmission path interface 140 may send and receive signals (backhaul signaling) with devices included in the core network 30 (e.g., network nodes providing NF), other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0212] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0213] The transmitting / receiving unit 120 may transmit one or more serving cell settings for the serving cell and additional cells. The control unit 110 may control transmission and reception with at least one of the serving cell and additional cells based on the one or more serving cell settings.

[0214] Each of the one or more serving cell settings described above may be a setting for multiple additional cells, or a setting for one serving cell and one or more additional cells.

[0215] Each of the one or more serving cell settings includes settings for multiple bandwidth portions (BWPs), and the settings for each BWP may correspond to at least one of the serving cell and the additional cell.

[0216] (User terminal) Figure 29 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0217] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0218] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

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

[0220] The transmitting / receiving unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

[0222] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

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

[0224] The transmitting / receiving unit 220 may form at least one of the transmitting beam and the receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

[0226] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion, and output a baseband signal.

[0227] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.

[0228] The transmitting / receiving unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 230.

[0229] On the other hand, the transmitting / receiving unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 230.

[0230] The transmission / reception unit 220 (reception processing unit 2212) may apply reception processing such as analog-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and may acquire user data and the like.

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

[0232] Note that the transmission unit and reception unit of the user terminal 20 in the present disclosure may be constituted by at least one of the transmission / reception unit 220 and the transmission / reception antenna 230.

[0233] Note that the transmission / reception unit 220 may receive one or more serving cell settings for the serving cell and additional cells. The control unit 210 may control the transmission / reception with at least one of the serving cell and the additional cells based on the one or more serving cell settings.

[0234] Each of the one or more serving cell settings may be a setting related to a plurality of additional cells, or a setting related to one serving cell and one or more additional cells.

[0235] The same serving cell setting may be shared in different component carriers. Different serving settings may be set in different component carriers.

[0236] Each of the above one or more serving cell configurations includes configurations related to a plurality of bandwidth parts (BWPs), and the configuration related to each BWP may correspond to at least one of the serving cell and the additional cell.

[0237] The transceiver 220 may receive, by upper layer signaling, an instruction indicating which BWP configuration among the configurations related to the plurality of BWPs is to be used for the additional cell.

[0238] When a specific parameter is not set in the serving cell configuration for the additional cell, the control unit 210 may use the same parameter as that of the serving cell for the additional cell for the specific parameter.

[0239] The transceiver 220 may receive, by a media access control control element (MAC CE), a setting of a different Cell Radio Network Temporary Identifier (C-RNTI) for each additional cell.

[0240] (Hardware Configuration) Note that the block diagrams used in the description of the above embodiments show functional unit blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Also, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically combined device, or may be realized using two or more physically or logically separated devices directly or indirectly (for example, using wired, wireless, etc.) connected, and these multiple devices. The functional block may be realized by combining software with the above one device or the above multiple devices.

[0241] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0242] For example, a base station, user terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 30 is a diagram showing an example of the hardware configuration of a base station and user terminal according to one embodiment. The base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0243] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

[0244] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, processing may be performed by one processor, or by two or more processors simultaneously, sequentially, or by other means. Note that processor 1001 may be implemented using one or more chips.

[0245] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication via the communication device 1004, or to control at least one of the reading and writing of data in the memory 1002 and storage 1003.

[0246] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

[0247] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.

[0248] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. Memory 1002 may also be called a register, cache, or main memory. Memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of this disclosure.

[0249] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM)), a digital multipurpose disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be called an auxiliary storage device.

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

[0251] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0252] Furthermore, each device, such as the processor 1001 and memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0253] Furthermore, the base station 10 and the user terminal 20 may 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), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0254] (modified version) In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

[0255] A wireless frame may consist of one or more periods (frames) in the time domain. Each of these periods (frames) constituting a wireless frame may be called a subframe. Furthermore, a subframe may consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0256] Here, the new numerology may be a communication parameter applied to at least one of the transmission and reception of a certain signal or channel. The new numerology may indicate, for example, at least one of subcarrier spacing (SubCarrier Spacing (SCS)), bandwidth, symbol length, cyclic prefix length, transmission time interval (Transmission Time Interval (TTI)), number of symbols per TTI, radio frame configuration, specific filtering process performed by the transceiver in the frequency domain, specific windowing process performed by the transceiver in the time domain, etc.

[0257] A slot may be composed of one or more symbols (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC - FDMA) symbols, etc.) in the time domain. Also, a slot may be a time unit based on the new numerology.

[0258] A slot may include a plurality of mini - slots. Each mini - slot may be composed of one or more symbols in the time domain. Also, a mini - slot may be called a sub - slot. A mini - slot may be composed of a smaller number of symbols than a slot. The PDSCH (or PUSCH) transmitted in a time unit larger than a mini - slot may be called PDSCH (PUSCH) mapping type A. The PDSCH (or PUSCH) transmitted using a mini - slot may be called PDSCH (PUSCH) mapping type B.

[0259] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

[0260] For example, one subframe may be called TTI, multiple consecutive subframes may be called TTI, or one slot or one mini-slot may be called TTI. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Note that the unit representing TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0261] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0262] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0263] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0264] A TTI with a time length of 1 ms may also be called a normal TTI (TTI in 3GPP Rel.8-12), a long TTI, a normal subframe, a long subframe, or a slot. A TTI shorter than a normal TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, or a slot.

[0265] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0266] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0267] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. Each TTI, subframe, etc., may consist of one or more resource blocks.

[0268] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0269] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0270] A Bandwidth Part (BWP) (also called a partial bandwidth) may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.

[0271] A BWP may include UL BWPs (BWPs for UL) and DL BWPs (BWPs for DL). One or more BWPs may be configured within a single carrier for a UE.

[0272] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0273] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative examples. For instance, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots within a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0274] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or corresponding other information. For example, wireless resources may be indicated by a predetermined index.

[0275] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements that use these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0276] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0277] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

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

[0279] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof).

[0280] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Element (CE).

[0281] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information).

[0282] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

[0283] Software should be broadly interpreted to mean 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, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

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

[0285] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0286] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "quasi-co-location (QCL)," "transmission configuration indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," and "panel" may be used interchangeably.

[0287] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "panel", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0288] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0289] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information.

[0290] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0291] A mobile station may also be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term.

[0292] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.

[0293] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.

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

[0295] Figure 31 shows 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 rotation speed sensor 51, a pneumatic 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.

[0296] The drive unit 41 consists of, for example, at least one of an engine, a motor, or an engine-motor hybrid. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by the user.

[0297] The electronic control unit 49 consists of a microprocessor 61, memory (ROM, RAM) 62, and communication ports (e.g., input / output (IO) ports) 63. Signals from various sensors 50-58 installed in the vehicle are input to the electronic control unit 49. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0298] Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression signal of accelerator pedal 43 acquired by accelerator pedal sensor 55, brake pedal depression signal of brake pedal 44 acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals for detecting obstacles, vehicles, pedestrians, etc., acquired by object detection sensor 58.

[0299] The information service unit 59 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, displays, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

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

[0301] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver assistance functions or autonomous driving functions.

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

[0303] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

[0304] The communication module 60 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 50-58 input to the electronic control unit 49, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 59. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above input.

[0305] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 59 installed in the vehicle. The information service unit 59 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 60).

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

[0307] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, uplink channel and downlink channel may be interpreted as sidelink channel.

[0308] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.

[0309] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes with base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0310] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements in an exemplary order and are not limited to that specific order.

[0311] Each aspect / embodiment described in this disclosure includes 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 decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), and IEEE This may apply to systems utilizing 802.20, Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, as well as next-generation systems that are extended, modified, created, or defined based on these. It may also apply to combinations of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

[0312] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0313] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0314] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to include judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0315] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0316] Furthermore, "judgment (decision)" can be considered as "judging (deciding)" something like resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" can be considered as "judging (deciding)" something about an action.

[0317] Furthermore, "judgment (decision)" can be replaced with "assuming," "expecting," or "considering."

[0318] The term "maximum transmit power" as used in this disclosure may mean the maximum transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0319] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0320] In this disclosure, when two elements are connected, they can be considered to be “connected” or “coupled” to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, or optical domain (both visible and invisible).

[0321] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0322] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0323] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0324] In this disclosure, terms such as "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. Furthermore, in this disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").

[0325] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.

[0326] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The invention described herein can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined in the claims. Therefore, the descriptions herein are for illustrative purposes only and do not imply any limitation on the invention described herein.

Claims

1. A receiving unit that receives settings for one serving cell for a plurality of candidate cells, The system includes a control unit that controls at least one transmission and reception with at least one of the plurality of candidate cells based on the above setting, The above configuration includes a plurality of bandwidth portion (BWP) indices, each BWP index corresponding to at least one of the plurality of candidate cells. Terminal.

2. When the control unit is instructed to switch cells by the Medium Access Control Control Element (MAC CE), it uses the settings corresponding to the instructed cell. The terminal according to claim 1.

3. The setting includes a setting common to the plurality of candidate cells and a setting that is different for each of the plurality of candidate cells. The terminal according to claim 1.

4. The settings are shared between different Physical Cell Identities (PCIs). The terminal according to claim 1.

5. A step of receiving settings for one serving cell for a plurality of candidate cells, The process includes controlling at least one transmission and reception with at least one of the plurality of candidate cells based on the above setting, The above configuration includes a plurality of bandwidth portion (BWP) indices, each BWP index corresponding to at least one of the plurality of candidate cells. The wireless communication method used by the terminal.

6. A transmission unit that transmits settings for one serving cell for a plurality of candidate cells, The system includes a control unit that controls at least one transmission and reception with at least one of the plurality of candidate cells based on the above setting, The above configuration includes a plurality of bandwidth portion (BWP) indices, each BWP index corresponding to at least one of the plurality of candidate cells. Base station.

7. A system including a terminal and a base station, The aforementioned base station is It has a transmission unit that transmits settings for one serving cell for multiple candidate cells, The aforementioned terminal is A receiving unit that receives the aforementioned settings, The system includes a control unit that controls at least one transmission and reception with at least one of the plurality of candidate cells based on the above setting, The above configuration includes a plurality of bandwidth portion (BWP) indices, each BWP index corresponding to at least one of the plurality of candidate cells. system.

Images