Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit which receives a cell group configuration for a cell group including a special cell and one or more secondary cells; and a control unit which controls, on the basis of the cell group configuration, communication that uses said cell group. A cell configuration for one cell in the cell group configuration includes one or more information elements for a plurality of cells in the cell group.

Description

Terminal, wireless communication method and base station

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

[0002] Long Term Evolution (LTE) has been specified for the Universal Mobile Telecommunications System (UMTS) network with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) has been specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

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

[0004] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010

[0005] In future wireless communication systems (e.g., NR), it is being considered to communicate by bundling multiple cells.

[0006] However, the structure of the information required for setting up communication across multiple cells has not been fully considered, which could lead to an increase in the signaling load on terminals.

[0007] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that use settings to reduce the load on the base station / terminal.

[0008] A terminal according to one aspect of the present disclosure includes a receiving unit that receives a cell group configuration for a cell group including a special cell and one or more secondary cells, and a control unit that controls communication using the cell group based on the cell group configuration, wherein the cell configuration for one cell in the cell group configuration includes one or more information elements for multiple cells in the cell group.

[0009] According to one aspect of the present disclosure, the load on the base station / terminal can be reduced.

[0010] 1A and 1B show an example of slot configuration. FIG. 2 shows an example of an XDD configuration. FIG. 3A and 3B show an example of time domain and frequency domain resource configuration for XDD operation. FIG. 4 shows an example of cell group configuration. FIG. 5 shows an example of cell group configuration using an SCell. FIGs. 6A to 6C show an example of existing multiple carriers in one serving cell. FIGs. 7A to 7C show an example of multiple carriers in one serving cell according to embodiment A1. FIGs. 8A to 8C show an example of initial access using multiple carriers in one serving cell according to embodiment A2. FIG. 9 shows an example of a combination of Option A and Option 1 according to embodiment B1. FIG. 10 shows an example of a combination of Option A and Option 2 according to embodiment B1. FIG. 11 shows an example of a combination of Option B and Option 1 according to embodiment B1. FIG. 12 shows an example of sCellToAddModList in the combination of Option B and Option 1 according to embodiment B1. FIG. 13 shows an example of a combination of Option C and Option 1 according to embodiment B1. FIG. 14 shows an example of a combination of Option D and Option 1 of embodiment B1. FIG. 15 shows an example of a modified example of a combination of Option C and Option 1 of embodiment B1. FIG. 16 shows an example of sCellToAddModList in a modified example of a combination of Option C and Option 1 of embodiment B1. FIG. 17 shows an example of a modified example of a combination of Option D and Option 1 of embodiment B1. FIG. 18 shows an example of an existing cell configuration. FIG. 19 shows an example of a first stage of embodiment B2-1. FIG. 20 shows an example of option 1 of the second stage of embodiment B2-1. FIG. 21 shows an example of option 2 of the second stage of embodiment B2-1. FIG. 22 shows an example of a third stage after option 1 of the second stage of embodiment B2-1. FIG. 23 shows an example of a third stage after option 3 of the second stage of embodiment B2-1. FIG. 24 shows an example of a state in which option 1 of the second stage of embodiment B2-1 is applied to option B and option 2 of embodiment B1. FIG. 25 shows an example of a state in which option 1 of the second stage of embodiment B2-1 and embodiment B2-2 are applied once to option B and option 2 of embodiment B1.FIG. 26 shows an example of a state in which option 1 of the second stage of embodiment B2-1 and embodiment B2-2 are applied twice to option B and option 2 of embodiment B1. FIG. 27 shows an example of a state in which option 1 of the second stage of embodiment B2-1 and embodiment B2-2 are applied three times to option B and option 2 of embodiment B1. FIG. 28 shows an example of a state in which option 1 of the second stage of embodiment B2-1 and embodiment B2-2 are applied four times to option B and option 2 of embodiment B1. FIG. 29 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 30 is a diagram showing an example of a configuration of a base station according to an embodiment. FIG. 31 is a diagram showing an example of a configuration of a user terminal according to an embodiment. FIG. 32 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment. FIG. 33 is a diagram showing an example of a vehicle according to an embodiment.

[0011] (Improving Spectral Utilization Efficiency) Improvements in spectral efficiency (e.g., increasing the efficiency of existing frequency bands) are being considered for future wireless communication systems (e.g., Beyond 5G and 6G). Specifically, elastic (elastic, stretchable, flexible, adaptive) cells, which treat multiple frequency bands as a single virtual cell, and intra-carrier / inter-carrier cross-division duplex (XDD), in which base stations simultaneously transmit and receive, are being considered.

[0012] In LTE up to Rel. 14, Frequency Division Duplex (FDD) was mainly used, and Time Division Duplex (TDD) was also supported.

[0013] On the other hand, in NR from Rel. 15 onwards, TDD was mainly considered, and FDD was also supported at the same time (for example, migration of LTE bands).

[0014] In FDD, DL reception and UL transmission can be performed simultaneously, which is preferable from the viewpoint of delay reduction. On the other hand, in FDD, the resource ratio between DL and UL is fixed (for example, 1:1).

[0015] In TDD, it is possible to change the ratio of DL and UL resources. For example, in a typical environment where DL traffic is relatively heavy, it is possible to increase the amount of DL resources and improve DL throughput.

[0016] On the other hand, when considering the time ratio of transmission and reception using Time Division Duplex (TDD) up to Rel. 16, there may be cases where the number of transmission opportunities for UL signals / channels is fewer than the number of reception opportunities for DL ​​signals / channels. In such cases, the UE cannot transmit UL signals / channels frequently, which raises concerns about delays in the transmission of important UL signals / channels. Furthermore, since there are fewer UL transmission opportunities compared to DL reception opportunities, there is also concern about signal / channel congestion during UL transmission opportunities. Furthermore, since TDD limits the time resources available for transmitting UL signals / channels, the application of UL coverage extension techniques, such as repetition transmission, is also limited.

[0017] In future wireless communication systems (for example, Rel. 17 / 18 and later), it is being considered to introduce a frequency division duplexing method that combines TDD and frequency division duplex (FDD) for UL and DL.

[0018] This division duplexing method may be called XDD (Cross Division Duplex). XDD may refer to a duplexing method in which DL and UL are frequency-division multiplexed (DL and UL can be used simultaneously) within one component carrier (CC) of a TDD band or across multiple CCs. When this duplexing method is applied to multiple CCs, it may mean that in a time resource in which DL is available on one CC, UL is available on another CC. The multiple CCs may be CCs in the same band.

[0019] 1A is a diagram showing an example of TDD configuration defined up to Rel. 16. In this example, TDD slots / symbols are configured for a UE within the bandwidth of one component carrier (CC) (which may also be called a cell or serving cell).

[0020] In the example shown in Figure 1A, the time ratio of DL slots to UL slots is 4: 1. In such a conventional TDD slot / symbol setting, sufficient UL time resources cannot be secured, which may result in UL transmission delays and degradation of coverage performance.

[0021] 1B is a diagram showing an example of the configuration of XDD. In this example, within one component carrier (CC), resources used for DL ​​reception and resources used for UL transmission overlap in time. With this resource configuration, UL resources can be secured and resource utilization efficiency can be improved.

[0022] For example, as shown in the example of Figure 1B, by configuring both ends of the frequency domain in one CC as DL and sandwiching UL resources between the DL resources, it is possible to avoid and mitigate the occurrence of cross link interference (CLI) with neighboring carriers. Also, a guard area may be set at the boundary between the DL resource and the UL resource.

[0023] Considering the complexity of handling self-interference, it is possible that only the base station uses DL and UL resources simultaneously, i.e., in the case of DL and UL resources that overlap in time, one UE may use the DL resources and another UE may use the UL resources.

[0024] 2 is a diagram showing an example of the XDD configuration, in which part of the DL resources of the TDD band is used as UL resources, and the DL and UL are configured to overlap in time.

[0025] In this example, during the DL-only period, each of the multiple UEs (in this example, UE #1 and UE #2) receives the DL channel / signal.

[0026] Furthermore, during the period when the DL and UL channels overlap in time, one UE (UE #1 in this example) receives the DL channel / signal, and another UE (UE #2 in this example) transmits the UL channel / signal. During this period, the base station simultaneously transmits and receives the DL and UL channels.

[0027] Additionally, during the UL-only period, each of the multiple UEs transmits an UL channel / signal.

[0028] In the existing NR (for example, as defined by Rel. 15 / 16), the DL frequency resource and the UL frequency resource in the UE carrier are configured as a DL Bandwidth Part (BWP) and a UL BWP, respectively. In order to switch the DL / UL frequency resource to another DL / UL frequency resource, multiple BWP configurations and a BWP adaptation mechanism are required.

[0029] In addition, in the existing NR, the time resources in the TDD carrier for the UE are configured as at least one of DL, UL, and flexible (FL) in the TDD configuration.

[0030] The time and frequency domain resource configuration for XDD operation is being considered. For example, for UE #1 in Figure 2, it is possible to configure XDD resources (duration of DL and UL overlap) while avoiding the use of portions of the UL resources used by other UEs (e.g., UE #2) (see Figure 3A).

[0031] Also, for example, for UE #2 in Figure 2, it is possible to configure XDD resources while avoiding the use of portions of the DL resources used by other UEs (e.g., UE #1) (see Figure 3B).

[0032] (Virtual Cell) Toward 6G, consideration is being given to improving frequency utilization efficiency and reducing scheduling overhead by regarding multiple frequency bands as one virtual cell. In elastic cell and inter-carrier XDD, multiple carriers are aggregated and considered as one virtual cell, and control and UL are performed only on specific carriers among the multiple carriers, allowing the remaining carriers to be used for data communication. This allows low overhead to be achieved. A UE that supports carrier aggregation (CA) can perform control / UL only on specific carriers by cross-carrier scheduling during RRC connection.

[0033] Scheduling is being considered in which all frequency resources included in one CC or a carrier set (virtual CC) is defined by bundling multiple CCs, and resources with a larger granularity than a CC are used.

[0034] (Cell group setting / cell setting) In NR / 5G, for dual connectivity (DC), multiple cells are set within a cell group, and the settings of multiple cells are managed in a unified manner.

[0035] By using the cell group setting (Figure 4), when adding a cell, the gNB can simply add the cell to the cell group without changing the information set for each cell (Figure 5). This setting allows the gNB to easily add cells even if the settings for each cell are different.

[0036] The cell group configuration (CellGroupConfig structure) has the following structure:

[0037] ◆The CellGroupConfig structure includes spCellConfig (SpCellConfig structure, SpCell configuration), sCellToAddModList (one or more SCellConfig structures, one or more SCell configurations). -◆The spCellConfig includes servCellIndex (ServCellIndex structure, serving cell index), reconfigWithSync (ReconfigWithSync structure), and spCellConfigDedicated (individual SpCell configuration, ServingCellConfig structure). -◆The ReconfigWithSync structure includes spCellConfigCommon (common SpCell configuration, ServingCellConfigCommon structure). -◆The SCellConfig structure includes sCellIndex (SCellIndex structure, SCell index), sCellConfigCommon (common SCell configuration, ServingCellConfigCommon structure), and sCellConfigDedicated (individual SCell configuration, ServingCellConfig structure).

[0038] ◆The ServingCellConfigCommon structure includes physCellId (PhysCellId structure, physical cell index), downlinkConfigCommon (DownlinkConfigCommon structure, common DL setting), and uplinkConfigCommon (common UL setting). -◆The DownlinkConfigCommon structure includes initialDownlinkBWP (BWP-DownlinkCommon structure, initial DL BWP setting).

[0039] ◆The ServingCellConfig structure includes the initialDownlinkBWP (BWP-DownlinkDedicated structure), firstActiveDownlinkBWP-Id, bwp-InactivityTimer, defaultDownlinkBWP-Id, downlinkBWP-ToAddModList (one or more BWP-Downlink structures), uplinkConfig (UplinkConfig structure, UL settings). -◆The UplinkConfig structure includes the initialUplinkBWP (BWP-UplinkDedicated structure, initial UL BWP settings), uplinkBWP-ToAddModList (one or more BWP-Uplink structures), firstActiveUplinkBWP-Id.

[0040] ◆The BWP-Downlink structure includes bwp-Id, bwp-Common (BWP-DownlinkCommon structure, common DL BWP setting), and bwp-Dedicated (BWP-DownlinkDedicated structure, individual DL BWP setting).

[0041] ◆The BWP-DownlinkCommon structure contains genericParameters (BWP structure, generic parameters).

[0042] ◆The BWP-UplinkCommon structure includes genericParameters (BWP structure, generic parameters).

[0043] ◆The BWP structure includes locationAndBandwidth (location and bandwidth in the frequency domain), subcarrierSpacing (subcarrier spacing setting), and cyclicPrefix (cyclic prefix).

[0044] When an SCell is added, the sCellToAddModList contains several sCellConfigs (sCellConfig1, sCellConfig2, ...) The sCellConfigs include sCellConfigCommon and sCellConfigDedicated.

[0045] When DC is not configured (for example, when carrier aggregation (CA) is configured), a cell group is not configured, and multiple cells are configured for each cell.

[0046] In operation, there may be no difference in parameters and their values ​​between multiple cell configurations, resulting in redundant parameters.

[0047] When reducing the bandwidth of CA for power saving or the like, CA needs to change the bandwidth of each of the following multiple cells. It also needs to change the bandwidth of the BWP in each cell. Changing the nested structure is complicated when the SCS of a cell is changed, for example.

[0048] The complexity of the configuration structure increases the processing load of the base station / terminal, and the existence of redundant parameters increases signaling overhead, which may reduce communication throughput.

[0049] Therefore, the inventors have conceived a method for integrating the configuration structure for one or more cells.

[0050] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0051] (Various Reinterpretations) In the present disclosure, a word enclosed in "( )" in a sentence may indicate an explanation of the word immediately preceding it (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Furthermore, in the present disclosure, a word enclosed in "[ ]" in a sentence may be interpreted including the word in the meaning of the entire sentence, or may be interpreted excluding (ignoring) the word in the meaning of the entire sentence. Note that "( )" and "[ ]" may also be used for purposes / meanings other than those mentioned above.

[0052] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0053] In the present disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be read interchangeably. In the present disclosure, terms such as support, control, controllable, operate, and operate may be read interchangeably.

[0054] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.

[0055] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., messages from the core network such as positioning protocol (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages), or a combination thereof.

[0056] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. Broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0057] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.

[0058] In the present disclosure, ceil(x), ceiling function, and ceiling function may be interchangeable. In the present disclosure, floor(x), floor function, and floor function may be interchangeable. In the present disclosure, sqrt(x), square root of x, and root x may be interchangeable. In the present disclosure, x mod y, mod(x, y), mod function, and modulo operation may be interchangeable. In the present disclosure, Σ i=M M＋N－1 f(i), Σ i=M M+N-1 f i , f(i) or f for i = M, M+1, ..., M+N-1 i Summation of f(M) + f(M+1) + ... + f(M+N-1), f M +f M＋1 +...+f M＋N－1 , may be read interchangeably. C(n, k) is the number of combinations of k values ​​selected from n values ​​(combinatorial coefficient), binomial coefficients, n Ck , C n k In the present disclosure, x / y and floor(x / y) may be read as interchangeable.

[0059] In this disclosure, A b , A_b, Ab, and A with b added to the bottom right may be read interchangeably. c , A^c, and the notation of A with c added to the upper right may be read interchangeably. b c , A_b^c, and the notation in which b is added to the bottom right of A and c is added to the top right of A may be read interchangeably. ～ may be expressed by adding 〜 to the x, or may be referred to as x tilde. － may be represented by placing a minus sign (-) on top of the x, or may be referred to as an x-bar. ＾ may be represented by placing a ^ above the x, and may be called an x-hat.

[0060] In the present disclosure, FR may be, for example, at least one of FR1, FR2, FR2-1, FR2-2, FR3, sub-terahertz, and terahertz. In the present disclosure, the frequency range corresponding to FR1 may be 410-7125 MHz. In the present disclosure, FR2 may include FR2-1 and FR2-2, and the frequency range corresponding to FR2-1 may be 24250-52600 MHz, and the frequency range corresponding to FR2-1 may be 52600-71000 MHz.

[0061] In this disclosure, the following abbreviations may be used: FDM: frequency division multiplexing TDM: time division multiplexing

[0062] In the present disclosure, the terms structure, class, and type may be read interchangeably.

[0063] In the present disclosure, the terms RRC IE, information element, variable, constant, parameter, and higher layer parameter may be interchangeable.

[0064] In the present disclosure, the terms representative cell, specific cell, special cell (SpCell), and integrated cell may be read interchangeably.

[0065] In the present disclosure, the terms "integrate," "combine," "summarize," and "simplify" may be read as interchangeable. In the present disclosure, the terms "integrate," "combine," and "simplify" may be read as interchangeable.

[0066] In the present disclosure, the terms block, setting group, part, location, range, and structure may be read interchangeably.

[0067] In the present disclosure, management and configuration may be read interchangeably.

[0068] In the present disclosure, the cell index, CC index, serving cell index, SCell index, and physical cell index may be read as interchangeable.

[0069] In the present disclosure, the terms list, add / modify list (ToAddModList), and release list (ToReleaseList) may be read interchangeably.

[0070] In the present disclosure, common configuration, common cell configuration, intra-cell UE common configuration, multiple UE common configuration, cell common configuration, cell configuration, ConfigCommon, reconfigWithSync, spCellConfigCommon, sCellConfigCommon, xCellConfigCommon, and CellConfigCommon may be interchangeable. In the present disclosure, dedicated configuration, dedicated cell configuration, UE dedicated configuration, cell configuration, spCellConfigDedicated, sCellConfigDedicated, xCellConfigDedicated, and CellConfigDedicated may be interchangeable. In the present disclosure, xCell, spCell (SpCell), sCell (SCell), cell, serving cell, and CC may be interchangeable.

[0071] In the present disclosure, in a list (XToAddModList / XToReleaseList) including one or more information elements X, the information element X including an index / ID (e.g., X-Id / XIndex) = i and the information element X being represented as Xi may be read interchangeably.

[0072] In the present disclosure, a specific wireless communication system, an existing wireless communication system, and 5G / NR may be interchangeable. In the present disclosure, an existing information element, an information element of a specific wireless communication system, and a setting of a specific wireless communication system may be interchangeable.

[0073] (Wireless Communication Method) ((Embodiment A)) <Embodiment A1> <UE Capability> A capability indicating support for using different carriers as DL / UL of one serving cell (new UE capability, new UE capability information) may be defined. The new UE capability may be defined as a capability separate from support for CA.

[0074] The new UE capabilities may be defined for at least one of the following cases: the multiple carriers include a DL carrier and a UL carrier; the multiple carriers include multiple DL carriers; and the multiple carriers include multiple UL carriers.

[0075] While a UE processes HARQ-ACK separately for multiple serving cells in CA, it may process HARQ-ACK collectively for multiple carriers in one serving cell, which can reduce the load on the UE.

[0076] The multiple carriers do not have to be pairs of DL and UL carriers in one FDD band. The multiple carriers may include DL / UL carriers with different center frequencies in one TDD band. The multiple carriers may include one of a DL and an UL carrier in one TDD band and a carrier in another band.

[0077] The multiple carriers may span multiple bands, which may or may not include an SUL band, and may include multiple FDD bands, one or more TDD bands, or bands with different duplex modes (e.g., one or more FDD bands and one or more TDD bands).

[0078] Figures 6A to 6C show examples of multiple carriers within one existing serving cell. In the example of Figure 6A, one serving cell includes an UL carrier and a DL carrier within one FDD band. In the example of Figure 6B, one serving cell includes an UL carrier and a DL carrier with the same center frequency within one TDD band. In the example of Figure 6C, one serving cell includes a NUL carrier and a DL carrier with the same center frequency within one TDD band, and an SUL carrier within one SUL band.

[0079] 7A to 7C illustrate an example of multiple carriers in one serving cell according to embodiment A1. As in the example of FIG. 7A, one serving cell may include UL / DL carriers in multiple FDD bands. As in this example, one serving cell may include UL and DL carriers in a first FDD band and UL and DL carriers in a second FDD band. As in the example of FIG. 7B, one serving cell includes UL and DL carriers having different center frequencies in one or more TDD bands. Here, the number of UL / DL carriers in one TDD band does not have to be one. As in this example, one serving cell may include two DL carriers and one UL carrier in one TDD band. As in the example of FIG. 7C, one serving cell may include UL / DL carriers in multiple bands, or the multiple bands may include a TDD band that includes only one of the UL and DL carriers. As in this example, one serving cell may include one UL carrier in one TDD band and a DL carrier in another band (e.g., the TDD band or the FDD band).

[0080] Different DL BWPs and UL BWPs of multiple carriers may be configured within a serving cell. For UEs with the new UE capabilities described above, different DL BWPs and UL BWPs of multiple carriers may be configured within a serving cell. The DL / UL BWPs may be configured using an offset (e.g., resource block (RB) offset) from NR—Absolute Radio Frequency Channel Number (ARFCN, a number on the global frequency raster) / pointA (a common reference point for the RB grid) and a bandwidth (e.g., the number of RBs).

[0081] The UE may report, as a capability (information in the new UE capability information), a combination of multiple DL / UL bands (e.g., a combination of band numbers) that can be used as one serving cell. The UE may also report, as a capability (information in the new UE capability information), whether or not it supports simultaneous transmission and reception of DL and UL.

[0082] The specifications may specify / limit multiple DL / UL band combinations that can be used as one serving cell. For example, the combinations may be limited to only TDD bands, only FDD bands, only multiple carriers within the same band (intra-band), or only FR1 (combination of bands within FR1). When multiple carriers within the same TDD band are used for DL ​​and UL, simultaneous transmission and reception on the multiple carriers may be impossible, or whether simultaneous transmission and reception using multiple carriers within the same TDD band is possible may be determined based on whether intra-carrier / intra-band XDD is supported.

[0083] A UE having the above-mentioned new UE capability or another new UE capability may support (or be configured with) one or more DL BWPs on different carriers in one serving cell. At least one of the following may be reported as a capability (information in the new UE capability information): the number (maximum number) of the one or more DL BWPs, the number (maximum number) of the multiple carriers, the total bandwidth (maximum bandwidth) of the one or more DL / BWPs, the total bandwidth (maximum bandwidth) of the multiple carriers, the bandwidth (maximum bandwidth) from the lower limit frequency to the upper limit frequency of the one or more DL / BWPs, and the bandwidth (maximum bandwidth) from the lower limit frequency to the upper limit frequency of the multiple carriers.

[0084] At any given time in a serving cell, one DL BWP may be active, or multiple DL BWPs may be active.

[0085] The UL BWP may be configured in the same manner as the DL BWP. A UE having the new UE capability described above or another new UE capability may support (configure) one or more UL BWPs on different carriers within one serving cell, or may support (configure) one UL BWP on different carriers within one serving cell. A UE having the new UE capability described above or another new UE capability may support (configure) one or more DL BWPs and one UL BWP on different carriers within one serving cell.

[0086] At any given time in a serving cell, one UL BWP may be active, or multiple UL BWPs may be active.

[0087] <<Combination of DL Carriers and UL Carriers>> When different carriers in one serving cell are used for DL ​​and UL (when the carriers in one serving cell include DL and UL carriers with different center frequencies, or when one serving cell includes multiple carriers for TDD), the UE may follow at least one of the following time resource determination methods 1 and 2. [Time Resource Determination Method 1] When simultaneous transmission and reception is not possible (the UE does not support simultaneous transmission and reception), the UE may determine the available time resources for each carrier according to a single TDD UL / DL configuration (or a TDD UL / DL configuration common to multiple carriers). [Time Resource Determination Method 2] When simultaneous transmission and reception is possible (the UE supports simultaneous transmission and reception), the UE may determine the available time resources for each carrier according to the TDD UL / DL configuration of each carrier. The TDD UL / DL configurations (link directions) of the multiple carriers at a given time may be the same or different. Alternatively, even if simultaneous transmission and reception are possible, the UE may follow a single TDD UL / DL configuration, and whether simultaneous transmission and reception are possible in each time resource may follow a different configuration (for example, a configuration for XDD).

[0088] <<Combination of Multiple DL Carriers>> When different carriers in one serving cell are used for DL ​​(the carriers in one serving cell include multiple DL carriers), the UE may follow at least one of the following DL BWP usage methods 1 and 2.

[0089] [DL BWP Usage Method 1] A UE may treat a combination of multiple DL BWPs (e.g., multiple DL BWPs spanning multiple carriers) as a single DL BWP. Within the single DL BWP, resources / channels / signals spanning multiple carriers may be configured / scheduled. The resources / channels / RS may be CORESET / PDSCH / CSI-RS, etc. The single DL BWP may be considered as a DL BWP consisting of pseudo-contiguous frequency resources. A frequency index (e.g., RB index) used for scheduling within the single DL BWP may be assigned to the frequency resources within the single DL BWP in a contiguous manner. The subcarrier spacing (SCS) may be the same among the multiple DL BWPs (within the single DL BWP).

[0090] [DL BWP Usage Method 2] Multiple DL BWPs (a set of multiple DL BWPs) may be active simultaneously. Resources / channels / signals across the multiple DL BWPs (multiple carriers) may be configured / scheduled. The UE may be specified not to assume that resources / channels / signals across the multiple DL BWPs (multiple carriers) are configured / scheduled. The resources / channels / RS may be only within one DL BWP (closed). The resources / channels / RS may be CORESET / PDSCH / CSI-RS, etc. The SCS may be the same among the multiple DL BWPs. The cases where the SCSs are different among the multiple DL BWPs may be allowed. A BWP switch may be an operation to simultaneously switch the multiple DL BWPs to other multiple DL BWPs. The multiple DL BWPs may be capable of being activated / deactivated (turned on / off) individually one by one, or may be switched to another DL BWP one by one.

[0091] According to embodiment A1, the UE can improve frequency utilization efficiency by using multiple carriers (e.g., not a pair of FDD carriers (paired spectrum) and not including SUL) as DL carriers and UL carriers within one serving cell.

[0092] <Embodiment A2> The UE may be able to use (or support) different carriers during initial access. The carriers may be included in one serving cell. The UE may receive SSBs (synchronization signals and / or PBCH) on at least one of the carriers.

[0093] 8A to 8C show an example of initial access using multiple carriers in one serving cell according to embodiment A2.

[0094] As shown in the example of Figure 8A, one serving cell includes UL and DL carriers with different center frequencies within one TDD band. Here, the number of UL carriers / DL carriers within one TDD band may not be one. As shown in this example, one serving cell may include a first DL carrier, a UL carrier, and a second DL carrier within one TDD band. The UE may receive an SSB on the second DL carrier, receive SIB1 PDSCH on the first DL carrier, and be instructed by SIB1 about the initial UL BWP within the UL carrier.

[0095] As shown in the example of Figure 8B, one serving cell includes UL carriers and DL carriers with different center frequencies in multiple TDD bands. Here, the number of UL carriers / DL carriers in one TDD band may not be one. As in this example, one serving cell may include an UL carrier in a first TDD band and a DL carrier in a second TDD band. The UE may receive the SSB and SIB1 PDSCH on the DL carrier and be instructed by SIB1 about the initial UL BWP in the UL carrier.

[0096] As shown in the example of Figure 8C, one serving cell may include UL / DL carriers in multiple FDD bands. As shown in this example, one serving cell may include a first UL carrier and a second DL carrier in a first FDD band and a first UL carrier and a second DL carrier in a second FDD band. The UE may receive the SSB on the first DL carrier, receive the SIB1 PDSCH on the second DL carrier, and be instructed by SIB1 about the initial UL BWP in the first UL carrier.

[0097] <<Different UL Carriers During Initial Access>> UL carriers of bands other than those defined for SUL (e.g., bands defined for TDD / FDD / XDD) may be configured / indicated by system information (e.g., SIB1).

[0098] An UL carrier (initial UL BWP) of a carrier (center frequency) different from SIB1 may be signaled / broadcast by SIB1. SIB1 may signal / broadcast the parameters of the initial UL BWP and the NR-ARFCN / point A of the UL carrier. Only UEs that support the signaling of the initial UL BWP may recognize the signaling (initial UL BWP). The signaling of the initial UL BWP may be a mandatory function for a specific frequency range (FR) / band / release. The UE may perform UL transmission (e.g., random access procedure) at the initial UL BWP signaled by SIB1.

[0099] <<Multiple DL Carriers During Initial Access>> The UE may be instructed / configured to receive SIB1 PDCCH / SIB1 PDSCH on a carrier different from the carrier on which the SSB is received. The UE may follow at least one of the following carrier determination methods 1 to 3. [Carrier Determination Method 1] Multiple candidates for bands / carriers may be specified in the specifications. An information element / field in the MIB (PBCH) may indicate one of the multiple candidates. The UE may monitor the SIB1 PDCCH (Type 0-PDCCH) on the indicated candidate carrier. [Carrier Determination Method 2] Multiple candidates for bands / carriers may be specified in the specifications. A field in the SIB1 PDCCH may indicate one of the multiple candidates. The UE may receive SIB1 PDSCH on the indicated candidate carrier. [Carrier Determination Method 3] The band / carrier for receiving the SIB1 PDCCH / SIB1 PDSCH may be specified in the specifications. The association between the band / carrier of the detected SSB and the band / carrier for receiving the SIB1 PDCCH / SIB1 PDSCH may be specified in the specifications. A derivation rule (calculation formula) for the band / carrier for receiving the SIB1 PDCCH / SIB1 PDSCH from the band / carrier of the detected SSB may be specified in the specifications. The UE may determine a carrier different from the carrier for receiving the SSB as the carrier for receiving the SIB1 PDCCH / SIB1 PDSCH in accordance with the specifications. The UE may receive the SIB1 PDCCH / SIB1 PDSCH on the determined carrier.

[0100] Random Access Procedure on a Different Carrier During Initial Access A UE in IDLE mode may be instructed / configured to perform a random access procedure (e.g., transmit a random access preamble) on a carrier different from the one it is camped on.

[0101] Information about the carrier / BWP used for the random access procedure may be announced / broadcast by SIB1, which may include the parameters of the BWP and the NR ARFCN / point A of the carrier / BWP.

[0102] According to embodiment A2, the UE can improve frequency utilization efficiency by using multiple carriers (for example, not one pair of FDD carriers (paired spectrum) and not including the SUL) for initial access.

[0103] ((Embodiment B)) <Embodiment B1> Embodiment B1 relates to changing the structure of setting information between multiple cells.

[0104] Not only in DC but also in CA etc., by setting a cell group, it is possible to easily set / manage / change parameters for each cell. Multiple cells may be managed / set as a cell group. Information elements for each cell can be changed to common information elements in a cell group / multiple cells.

[0105] By sharing redundant existing information elements among multiple cells or within a cell, the structure can be simplified and the processing load of the UE can be reduced. Furthermore, by setting the values ​​of redundant existing information elements in common, the signaling overhead can be reduced.

[0106] Within the cell group / cell configuration, there are information elements that are managed by specific units (blocks).

[0107] The inter-cell information integration method is a regulation / rule / principle for integrating / combining / summarizing / simplifying information between multiple cells. The inter-cell information integration method may, for example, indicate a unit (block) to be integrated between multiple cells.

[0108] The inter-cell information management method is a regulation / rule / principle for managing information when integrating information between multiple cells, and may indicate, for example, whether information is shared between multiple cells or whether multiple cells are managed together as a single cell.

[0109] The inter-cell information integration method and the inter-cell information management method may be set in combination.

[0110] <<Inter-cell information integration method>> The existing configuration of each cell includes multiple blocks. Each block includes one or more information elements (RRC IEs). For example, some of the blocks are common configurations (xCellConfigCommon, reconfigWithSync, spCellConfigCommon, sCellConfigCommon) and dedicated configurations (xCellConfigDedicated, spCellConfigDedicated, sCellConfigDedicated). One or more information elements in a specific block may be integrated between multiple cells. The inter-cell information integration method may be based on at least one of the following options:

[0111] ◆ Option A: SpCell configuration information elements and SCell configuration information elements are managed separately. All or part of multiple SCell configuration information elements may be integrated.

[0112] ◆ Option B: All or part of the information elements of the SpCell configuration and the SCell configuration may be integrated.

[0113] ◆ Option C: All or part of the individual settings of the SpCell and the SCell (spCellConfigDedicated / sCellConfigDedicated) may be integrated. The common settings of the SpCell (reconfigWithSync / spCellConfigCommon) and the common settings of the SCell (sCellConfigCommon) may be separated.

[0114] ◆ Option D: All or part of the common settings of the SpCell and the SCell may be integrated. The individual settings of the SpCell and the individual settings of the SCell may be separated.

[0115] The integrated information elements maintain information elements of common configuration blocks (spCellConfigCommon / sCellConfigCommon), and a list (xToAddModList) for managing one or more blocks may be introduced, or a list for managing information elements within the common configuration may be introduced.

[0116] The inter-cell information integration method may be based on at least one of the following examples.

[0117] ◆ Example 1A (Option A) - ◆ All or part (one or more information elements) of multiple sCellConfigCommons included in multiple sCellConfigs in sCellToAddModList in CellGroupConfig may be integrated between multiple cells. - ◆ All or part (one or more information elements) of multiple sCellConfigDedicated included in multiple sCellConfigs in sCellToAddModList in CellGroupConfig may be integrated between multiple cells.

[0118] ◆ Example 1B (Option B) - ◆ Within a CellGroupConfig, all or part (one or more information elements) of spCellConfigCommon in reconfigWithSync and multiple sCellConfigCommons included in multiple sCellConfigs in sCellToAddModList may be integrated between multiple cells. - ◆ Within a CellGroupConfig, all or part (one or more information elements) of spCellConfigDedicated and multiple sCellConfigDedicated included in multiple sCellConfigs in sCellToAddModList may be integrated between multiple cells.

[0119] ◆ Example 1C (Option C) - ◆ Within a CellGroupConfig, all or part (one or more information elements) of multiple sCellConfigCommons included in each of multiple sCellConfigs in sCellToAddModList may be integrated between multiple cells. - ◆ Within a CellGroupConfig, all or part (one or more information elements) of spCellConfigDedicated and multiple sCellConfigDedicated included in each of multiple sCellConfigs in sCellToAddModList may be integrated between multiple cells.

[0120] ◆ Example 1D (Option D) - ◆ Within a CellGroupConfig, all or part (one or more information elements) of spCellConfigCommon in reconfigWithSync and multiple sCellConfigCommons included in multiple sCellConfigs in sCellToAddModList may be integrated between multiple cells. - ◆ All or part (one or more information elements) of multiple sCellConfigDedicated included in multiple sCellConfigs in sCellToAddModList in CellGroupConfig may be integrated between multiple cells.

[0121] <<Inter-Cell Information Management Method>> The one or more information elements integrated by the inter-cell information integration method may be based on at least one of several options:

[0122] ◆ Option 1: The configuration of one or more representative cells (specific cells) among the multiple cells may include one or more information elements among the configuration of the multiple cells. For cells other than the representative cell among the multiple cells, the configuration of the representative cell may be referenced.

[0123] ◆ Option 2: Multiple cells may be integrated into one or more integrated cells (specific cells). The settings of the integrated cell may include the settings of the multiple cells.

[0124] <<Example of Combination of Option A and Option 1 / 2>> The inter-cell information integration method and the inter-cell information management method may be based on at least one of the following examples.

[0125] ◆ Example 1A1 (Combination of Option A and Option 1, Figure 9) - ◆ One of multiple SCells may be a representative cell. The representative cell may be, for example, the SCell with the lowest index (e.g., SCellIndex = 1). -- ◆ The SCellConfig for the representative cell may include a list (e.g., sCellConfigCommonToAddModList) including multiple sCellConfigCommons corresponding to the multiple SCells, respectively. The SCellConfig for each SCell other than the representative cell may not include sCellConfigCommon. The SCellConfig for each SCell other than the representative cell may include an index (e.g., serving cell index / SCell index) for referencing the sCellConfigCommon of the representative cell. The UE may obtain sCellConfigCommon corresponding to each SCell other than the representative cell from the SCellConfigCommonToAddModList for the representative cell. --◆ The SCellConfig for the representative cell may include a list (e.g., sCellConfigDedicatedToAddModList) including multiple sCellConfigDedicated corresponding to multiple SCells, respectively. The SCellConfig for each SCell other than the representative cell may not include sCellConfigDedicated. The SCellConfig for each SCell other than the representative cell may include an index (e.g., serving cell index / SCell index) for referencing the sCellConfigDedicated of the representative cell. The UE may obtain sCellConfigDedicated corresponding to each SCell other than the representative cell from the SCellConfigDedicatedToAddModList for the representative cell. --◆ All or part of the value of sCellConfigCommon may be common to multiple SCells. The SCellConfig for the representative cell may include one sCellConfigCommon.The SCellConfig for each SCell other than the representative cell may not include all or part of sCellConfigCommon. The SCellConfig for each SCell other than the representative cell may include an index (e.g., serving cell index / SCell index) for referencing the sCellConfigCommon of the representative cell. UEs of multiple SCells may obtain sCellConfigCommon corresponding to each SCell other than the representative cell by referencing sCellConfigCommon in the SCellConfig for the representative cell. All or part of the values ​​of sCellConfigDedicated for multiple SCells may be common to multiple SCells. The SCellConfig for the representative cell may include one sCellConfigDedicated. The SCellConfig for each SCell other than the representative cell may not include all or part of sCellConfigDedicated. The SCellConfig for each SCell other than the representative cell may include an index (e.g., serving cell index / SCell index) for referencing the sCellConfigDedicated of the representative cell. The UE may obtain sCellConfigDedicated corresponding to each SCell other than the representative cell by referring to sCellConfigDedicated in the SCellConfig for the representative cell.

[0126] ◆ Example 1A2 (Combination of Option A and Option 2, Figure 10) - ◆ Multiple SCells may be integrated into one integrated cell. - ◆ CellGroupConfig may not include sCellToAddModList and may include one sCellConfig for the integrated cell. -- ◆ SCellConfig for the integrated cell may include a list (e.g., sCellConfigCommonToAddModList) including multiple sCellConfigCommons corresponding to the multiple SCells. The UE may obtain sCellConfigCommon corresponding to each SCell from the SCellConfigCommonToAddModList for the integrated cell. -- ◆ SCellConfig for the integrated cell may include a list (e.g., sCellConfigDedicatedToAddModList) including multiple sCellConfigDedicateds corresponding to the multiple SCells. The SCellConfig for each SCell other than the representative cell does not need to include sCellConfigDedicated. The UE may obtain sCellConfigDedicated corresponding to each SCell other than the representative cell from SCellConfigDedicatedToAddModList for the representative cell. ---◆ All or part of the values ​​of sCellConfigCommon for multiple SCells may be common to multiple SCells. SCellConfig for an integrated cell may include sCellConfigCommon for one cell and may not include all or part of sCellConfigCommon for other cells. ---◆ All or part of the values ​​of sCellConfigDedicated for multiple SCells may be common to multiple SCells. SCellConfig for an integrated cell may include sCellConfigDedicated for one cell and may not include all or part of sCellConfigDedicated for other cells.

[0127] ◆ Example 1V (Variation) - ◆ SCellConfig for each SCell may include a list (e.g., sCellConfigCommonToAddModList) including multiple sCellConfigCommons corresponding to multiple SCells, respectively. SCellConfigCommonToAddModList may have the same information among multiple sCellConfigs corresponding to multiple SCells, respectively. - ◆ SCellConfig for each SCell may include a list (e.g., sCellConfigDedicatedToAddModList) including multiple sCellConfigDedicateds corresponding to multiple SCells, respectively. SCellConfigDedicatedToAddModList may have the same information among multiple sCellConfigs corresponding to multiple SCells, respectively.

[0128] <<Details of Option 1>> As described above, in the cell configuration, at least one first information element among spCellConfigCommon in reconfigurationWithSync in spCellConfig, sCellConfigCommon in sCellConfig, sCellConfigDedicated in sCellConfig, and all information elements in sCellConfig may be integrated among multiple cells. In the cell configuration, second information elements other than the first information element may be collected into a group, and the group may be integrated among multiple cells, or each information element may be integrated among multiple cells.

[0129] The second information element may be an information element of sCellConfig for the SCell other than sCellConfigCommon / sCellConfigDedicated. The group may be an information element such as sCellConfigRest. The second information element may be at least one of the following information elements: sCellState-r16 secondaryDRX-GroupConfig-r16 preConfGapStatus-r17 goodServingCellEvaluationBFD-r17 plmn-IdentityInfoList-r17 npn-IdentityInfoList-r17 smtcs

[0130] The second information element may be an information element other than spCellConfigCommon in reconfigWithSync for SpCell. The group may be an information element such as spCellConfigRest. The second information element may be at least one of the following information elements: smtcs rach-ConfigDedicated daps-UplinkPowerConfig-r16 sl-PathSwitchConfig-r17

[0131] In a cell group, the representative cell or the aggregated cell may be one cell or multiple cells. If at least one of spCellConfigCommon and spCellConfigDedicated in reconfigWithSync for the SpCell is integrated with the information of the SCell, the index for the SpCell may be a special value (e.g., 0).

[0132] The sCellConfig for each SCell other than the representative cell may not include all or part of sCellConfigCommon / sCellConfigDedicated, but may include an index for the representative cell (serving cell index / CC index / physical cell index / SCell index). The UE may acquire the configuration of the SCell from the configuration of the representative cell based on the index for the representative cell.

[0133] Whether a cell group configuration / cell configuration based on the inter-cell information integration method / inter-cell information management method of embodiment B1 or a cell group configuration / cell configuration based on existing specifications is applied / configured for a certain cell group / certain cell may be notified / configured / indicated by an RRC IE / MAC CE / DCI, or may be notified / configured based on the value / existence / validity of an information element in a cell group configuration / common cell configuration / individual cell configuration, or may depend on the implementation of a base station or may be based on UE capabilities reported by a UE. For example, if a serving cell index / CC index exists in the common cell configuration / individual cell configuration, the cell group configuration / cell configuration based on the inter-cell information integration method / inter-cell information management method of embodiment B1 may be applied / configured, and if a serving cell index / CC index does not exist in the common cell configuration / individual cell configuration, the cell group configuration / cell configuration based on existing specifications may be applied / configured.

[0134] Embodiment B2 may be further applied to the inter-cell information integration method / inter-cell information management method of embodiment B1. For example, when sCellConfigCommon / sCellConfigDedicated are integrated, sCellConfig for one SCell may include a list of sCellConfigCommon / sCellConfigDedicated (sCellConfigCommonToAddModList / sCellConfigDedicatedToAddModList), and the list may include sCellConfigCommon / sCellConfigDedicated corresponding to multiple cells, respectively. For example, when sCellConfigCommon / sCellConfigDedicated are integrated, sCellConfig for one SCell may include a list for each information element in sCellConfigCommon / sCellConfigDedicated, and the list may include values ​​corresponding to multiple cells, respectively.

[0135] <<Details of the Combination of Option A and Option 2>> sCellConfigCommonToAddModList / sCellConfigDedicatedToAddModList may exist in the sCellConfig of the integrated cell (see FIG. 10 above) or in the CellGroupConfig.

[0136] When a new SCell is added, the SCell may be added to a cell group based on Rule 1 below. ◆ Rule 1: In the list sCellConfigCommonToAddModList / sCellConfigDedicatedToAddModList, the index of the SCell to be added may be the index of the first, last, or middle cell in the list. If the index of the SCell to be added is the first or middle index in the list and a cell corresponding to that index already exists, that index and any larger index may be incremented by 1.

[0137] <<Examples of Combinations of Options B / C / D and Options 1 / 2>> The inter-cell information integration method and the inter-cell information management method may be based on at least one of the following examples.

[0138] ◆ Example 1-B1 (Combination of Option B and Option 1, Figures 11 and 12) - ◆ The representative cell may be an SpCell. - ◆ CellGroupConfig may include SpCellConfig and sCellToAddModList. -- ◆ reconfigWithSync in spCellConfig may include a list (e.g., CellConfigCommonToAddModList) containing multiple common cell configurations (e.g., CellConfigCommon) corresponding to multiple cells (including SpCell and SCell) in the cell group. SCellConfig for each SCell may not include sCellConfigCommon. SCellConfig for each SCell may include an index indicating the SpCell. The UE may obtain CellConfigCommon corresponding to each SCell from CellConfigCommonToAddModList for the SpCell. --◆ spCellConfigDedicated in spCellConfig may include a list (e.g., CellConfigDedicatedToAddModList) containing multiple individual cell configurations (e.g., CellConfigDedicated) corresponding to multiple cells (including SpCell and SCell) in a cell group. SCellConfig for each SCell may not include sCellConfigDedicated. SCellConfig for each SCell may include an index indicating the SpCell. The UE may obtain CellConfigDedicated corresponding to each SCell from CellConfigDedicatedToAddModList for the SpCell. --◆ Each sCellConfig in sCellToAddModList may include CellConfigCommonToAddModList / CellConfigDedicatedToAddModList / CellConfigCommon / CellConfigDedicated.CellConfigCommonToAddModList / CellConfigCommon may include an index indicating the corresponding cell. The UE may obtain CellConfigCommon corresponding to each SCell from CellConfigCommonToAddModList in SpCellConfig based on the index. CellConfigDedicatedToAddModList / CellConfigDedicated may include an index indicating the corresponding cell. The UE may obtain CellConfigDedicated corresponding to each cell from CellConfigDedicatedToAddModList in SpCellConfig based on the index. - All or part of the value of CellConfigCommon may be common to multiple cells or multiple SCells. CellGroupConfig may include CellConfigCommon for the representative cell and may not include all or part of the values ​​of CellConfigDedicated for cells other than the representative cell. - All or part of the value of CellConfigDedicated may be common to multiple cells or multiple SCells. CellGroupConfig includes CellConfigDedicated for the representative cell, and may not include all or part of the values ​​of CellConfigDedicated for cells other than the representative cell.

[0139] ◆ Example 1-B2 (Combination of Option B and Option 2, Figure 11 above) - ◆ Multiple cells (including SpCell and SCell) in a cell group may be integrated into a single integrated cell. - ◆ CellGroupConfig may not include sCellToAddModList. - ◆ CellGroupConfig may include spCellConfig. -- ◆ spCellConfig / reconfigWithSync may include a list (e.g., CellConfigCommonToAddModList) containing multiple common cell configurations (e.g., CellConfigCommon) corresponding to multiple cells in the cell group. The UE may obtain CellConfigCommon corresponding to each cell from CellConfigCommonToAddModList. -- ◆ CellConfigCommon may include an index indicating the corresponding cell. The index may be an integer greater than or equal to 0, or may be an integer greater than or equal to 1. -- ◆ CellGroupConfig may include spCellConfigDedicated. --◆spCellConfig may include a list (e.g., CellConfigDedicatedToAddModList) containing multiple individual cell configurations (e.g., CellConfigDedicated) corresponding to multiple cells in a cell group. The UE may obtain CellConfigDedicated corresponding to each cell from CellConfigDedicatedToAddModList. --◆CellConfigDedicated may include an index indicating the corresponding cell. The index may be an integer equal to or greater than 0, or may be an integer equal to or greater than 1. --◆All or part of the value of CellConfigCommon may be common to multiple cells or multiple SCells. CellGroupConfig may include CellConfigCommon for one cell / SCell and not include all or part of CellConfigCommon for other cells.--All or part of the value of CellConfigDedicated may be common to multiple cells or multiple SCells. CellGroupConfig may include CellConfigDedicated for one cell / SCell and not include all or part of CellConfigDedicated for other cells.

[0140] ◆ Example 1-C1 (Combination of Option C and Option 1, Figure 13 and the above-mentioned Figure 12) - ◆ The representative cell may be an SpCell. - ◆ CellGroupConfig may include SpCellConfig and sCellToAddModList. -- ◆ spCellConfig may include reconfigWithSync / spCellConfigCommon, and a list (e.g., CellConfigCommonToAddModList) containing multiple common cell configurations (e.g., CellConfigCommon) corresponding to multiple SCells. Each CellConfigCommon may include an index indicating the corresponding cell. -- ◆ The UE may obtain spCellConfigCommon corresponding to the SpCell from reconfigWithSync in SpCellConfig. -- ◆ spCellConfig may include a list (e.g., CellConfigDedicatedToAddModList) containing multiple individual cell configurations (CellConfigDedicated) corresponding to multiple cells in the cell group. Each CellConfigDedicated may include an index indicating the corresponding cell. --◆The UE may obtain CellConfigDedicated corresponding to the SpCell from CellConfigDedicatedToAddModList in SpCellConfig. --◆Each sCellConfig in sCellToAddModList may include CellConfigCommonToAddModList / CellConfigDedicatedToAddModList / CellConfigCommon / CellConfigDedicated. CellConfigCommonToAddModList / CellConfigCommon may include an index indicating the corresponding cell. The UE may obtain CellConfigCommon corresponding to each SCell from CellConfigCommonToAddModList in SpCellConfig based on the index.CellConfigDedicatedToAddModList / CellConfigDedicated may include an index indicating the corresponding cell. The UE may obtain CellConfigDedicated corresponding to each cell from CellConfigDedicatedToAddModList in SpCellConfig based on the index. - All or part of the value of CellConfigCommon may be common to multiple cells or multiple SCells. CellGroupConfig may include CellConfigCommon for the representative cell and may not include all or part of the values ​​of CellConfigDedicated for cells other than the representative cell. - All or part of the values ​​of CellConfigDedicated may be common to multiple cells or multiple SCells. CellGroupConfig may include CellConfigDedicated for the representative cell and may not include all or part of the values ​​of CellConfigDedicated for cells other than the representative cell.

[0141] ◆ Example 1-C2 (Combination of Option C and Option 2, as shown in Figure 13 above) - ◆ Multiple cells in a cell group may be integrated into a single integrated cell. - ◆ CellGroupConfig may not include sCellToAddModList. - ◆ CellGroupConfig may include SpCellConfig. -- ◆ spCellConfig may include reconfigWithSync / spCellConfigCommon and a list (e.g., CellConfigCommonToAddModList) containing multiple common cell configurations (e.g., CellConfigCommon) corresponding to multiple SCells, respectively. The UE may obtain spCellConfigCommon corresponding to the SpCell from SpCellConfig / reconfigWithSync. The UE may obtain CellConfigCommon corresponding to each SCell from CellConfigCommonToAddModList in SpCellConfig. --◆ spCellConfig may include a list (e.g., CellConfigDedicatedToAddModList) containing multiple individual cell configurations (e.g., CellConfigDedicated) corresponding to multiple cells in a cell group. The UE may obtain CellConfigDedicated corresponding to each cell from CellConfigDedicatedToAddModList in SpCellConfig. --◆ All or part of the value of CellConfigCommon may be common to multiple cells or multiple SCells. CellGroupConfig may include CellConfigCommon for one cell / SCell and not include all or part of CellConfigCommon for other cells. --◆ All or part of the value of CellConfigDedicated may be common to multiple cells or multiple SCells. CellGroupConfig may include CellConfigDedicated for one cell / SCell and not include all or part of CellConfigDedicated for other cells.

[0142] ◆ Example 1-D1 (Combination of Option D and Option 1, Figure 14 and Figure 12 described above) - ◆ The representative cell may be an SpCell. - ◆ CellGroupConfig may include SpCellConfig and sCellToAddModList. -- ◆ spCellConfig / reconfigWithSync may include a list (e.g., CellConfigCommonToAddModList) containing multiple common cell configurations (e.g., CellConfigCommon) corresponding to multiple cells in the cell group. Each CellConfigCommon may include an index indicating the corresponding cell. -- ◆ The UE may obtain CellConfigCommon corresponding to the SpCell from CellConfigCommonToAddModList in SpCellConfig. -- ◆ spCellConfig may include spCellConfigDedicated. -- ◆ The UE may obtain spCellConfigDedicated corresponding to the SpCell from SpCellConfig. --◆spCellConfig may include a list (e.g., CellConfigDedicatedToAddModList) containing multiple individual cell configurations (e.g., CellConfigDedicated) corresponding to multiple SCells in a cell group. Each CellConfigDedicated may include an index indicating the corresponding cell. --◆Each sCellConfig in sCellToAddModList may include CellConfigCommonToAddModList / CellConfigDedicatedToAddModList / CellConfigCommon / CellConfigDedicated. CellConfigCommonToAddModList / CellConfigCommon may include an index indicating the corresponding cell. The UE may obtain CellConfigCommon corresponding to each SCell from CellConfigCommonToAddModList in SpCellConfig based on the index.CellConfigDedicatedToAddModList / CellConfigDedicated may include an index indicating the corresponding cell. The UE may obtain CellConfigDedicated corresponding to each cell from CellConfigDedicatedToAddModList in SpCellConfig based on the index. - All or part of the value of CellConfigCommon may be common to multiple cells or multiple SCells. CellGroupConfig may include CellConfigCommon for the representative cell and may not include all or part of the values ​​of CellConfigDedicated for cells other than the representative cell. - All or part of the values ​​of CellConfigDedicated may be common to multiple cells or multiple SCells. CellGroupConfig may include CellConfigDedicated for the representative cell and may not include all or part of the values ​​of CellConfigDedicated for cells other than the representative cell.

[0143] ◆ Example 1-D2 (Combination of Option D and Option 2, as shown in Figure 14 above) - ◆ Multiple cells in a cell group may be integrated into a single integrated cell. - ◆ CellGroupConfig may not include sCellToAddModList. - ◆ CellGroupConfig may include SpCellConfig. -- ◆ spCellConfig / reconfigWithSync may include a list (e.g., CellConfigCommonToAddModList) containing multiple common cell configurations (e.g., CellConfigCommon) corresponding to each of the multiple cells in the cell group. The UE may obtain spCellConfigCommon corresponding to the SpCell from reconfigWithSync in SpCellConfig. The UE may obtain sCellConfigCommon corresponding to each SCell from SCellConfigCommonToAddModList in SpCellConfig. -- ◆ spCellConfig may include spCellConfigDedicated. The UE may obtain spCellConfigDedicated corresponding to the SpCell from SpCellConfig. --◆spCellConfig may include a list (e.g., CellConfigDedicatedToAddModList) containing multiple individual cell configurations (e.g., CellConfigDedicated) corresponding to multiple SCells in a cell group. The UE may obtain CellConfigDedicated corresponding to each SCell from CellConfigDedicatedToAddModList in SpCellConfig. --◆All or some values ​​of CellConfigCommon may be common to multiple cells or multiple SCells. CellGroupConfig may include CellConfigCommon for one cell / SCell and not include all or some of CellConfigCommon for other cells. --◆All or some values ​​of CellConfigDedicated may be common to multiple cells or multiple SCells.The CellGroupConfig may include CellConfigDedicated for one cell / SCell and may not include all or part of CellConfigDedicated for other cells. - When an SCell is added to a cell group, Rule 1 above may be applied.

[0144] ◆ Example 1-C1-2 (Variation of the combination of Option C and Option 1, Figures 15 and 16) - ◆ The representative cell may be an SpCell. - ◆ CellGroupConfig may include SpCellConfig. - ◆ CellGroupConfig may include sCellToAddModList. - ◆ CellGroupConfig may include a list (e.g., CellConfigCommonToAddModList) containing multiple common cell configurations (e.g., CellConfigCommon) corresponding to multiple SCells, respectively. Each CellConfigCommon may include an index indicating the corresponding cell. - ◆ CellGroupConfig may include a list (e.g., CellConfigDedicatedToAddModList) containing multiple individual cell configurations (CellConfigDedicated) corresponding to multiple cells in the cell group, respectively. Each CellConfigDedicated may include an index indicating the corresponding cell. - ◆ spCellConfig may include reconfigWithSync / spCellConfigCommon. Each sCellConfig in sCellToAddModList may include CellConfigCommonToAddModList / CellConfigDedicatedToAddModList / CellConfigCommon / CellConfigDedicated. CellConfigCommonToAddModList / CellConfigCommon may include an index indicating the corresponding cell. The UE may obtain CellConfigCommon corresponding to each SCell from CellConfigCommonToAddModList in SpCellConfig based on the index. CellConfigDedicatedToAddModList / CellConfigDedicated may include an index indicating the corresponding cell.The UE may obtain the CellConfigDedicated corresponding to each cell from the CellConfigDedicatedToAddModList in the SpCellConfig based on the index. - The UE may obtain the spCellConfigCommon corresponding to the SpCell from the SpCellConfig / reconfigWithSync.

[0145] ◆ Example (variant example of the combination of Option C and Option 2, as shown in Figure 15 above) - ◆ Multiple cells in a cell group may be integrated into a single integrated cell. - ◆ CellGroupConfig may include SpCellConfig. The UE may obtain spCellConfigCommon corresponding to the SpCell from SpCellConfig / reconfigWithSync. - ◆ CellGroupConfig may not include sCellToAddModList. - ◆ CellGroupConfig may include a list (e.g., CellConfigCommonToAddModList) containing multiple common cell configurations (e.g., CellConfigCommon) corresponding to multiple SCells, respectively. The UE may obtain CellConfigCommon corresponding to each SCell from CellConfigCommonToAddModList. - ◆ CellGroupConfig may include a list (e.g., CellConfigDedicatedToAddModList) containing multiple individual cell configurations (e.g., CellConfigDedicated) corresponding to multiple cells in the cell group, respectively. The UE may obtain CellConfigCommon corresponding to each cell from CellConfigCommonToAddModList.

[0146] ◆ Example 1-D1-2 (Variation of the combination of Option D and Option 1, FIG. 17 and the above-mentioned FIG. 16) -◆ The representative cell may be an SpCell. -◆ CellGroupConfig may include sCellToAddModList. -◆ CellGroupConfig may include a list (e.g., CellConfigCommonToAddModList) containing multiple common cell configurations (e.g., CellConfigCommon) corresponding to multiple cells in the cell group. Each CellConfigCommon may include an index indicating the corresponding cell. -◆ CellGroupConfig may include spCellConfigDedicated. The UE may obtain spCellConfigDedicated corresponding to the SpCell from CellGroupConfig. -◆ CellGroupConfig may include a list (e.g., CellConfigDedicatedToAddModList) containing multiple individual cell configurations (e.g., CellConfigDedicated) corresponding to multiple SCells in the cell group. Each sCellConfigDedicated may include an index indicating the corresponding cell. Each sCellConfig in sCellToAddModList may include CellConfigCommonToAddModList / CellConfigDedicatedToAddModList / CellConfigCommon / CellConfigDedicated. CellConfigCommonToAddModList / CellConfigCommon may include an index indicating the corresponding cell. The UE may obtain CellConfigCommon corresponding to each SCell from CellConfigCommonToAddModList in SpCellConfig based on the index. CellConfigDedicatedToAddModList / CellConfigDedicated may include an index indicating the corresponding cell.The UE may obtain the CellConfigDedicated corresponding to each cell from the CellConfigDedicatedToAddModList in the SpCellConfig based on the index.

[0147] ◆ Example 1-D2-2 (Variation of the combination of Option D and Option 2, FIG. 17 described above) -◆ Multiple cells in a cell group may be integrated into a single integrated cell. -◆ CellGroupConfig may not include sCellToAddModList. -◆ CellGroupConfig may include a list (e.g., CellConfigCommonToAddModList) containing multiple common cell configurations (e.g., CellConfigCommon) corresponding to multiple cells in a cell group. The UE may obtain CellConfigCommon corresponding to each cell from CellConfigCommonToAddModList. -◆ CellGroupConfig may include spCellConfigDedicated. The UE may obtain spCellConfigDedicated corresponding to SpCell from CellGroupConfig. -◆ CellGroupConfig may include a list (e.g., CellConfigDedicatedToAddModList) containing multiple individual cell configurations (e.g., CellConfigDedicated) corresponding to multiple SCells in a cell group. The UE may obtain the CellConfigDedicated corresponding to each SCell from CellConfigDedicatedToAddModList.

[0148] Although some of the above examples include combinations of Options B / C / D with Option 3, Options B / C / D may also be combined with Options 1 / 2.

[0149] <<Integration Operation>> In each configuration of multiple cells in the existing specifications, at least one existing information element from several options below may be integrated into one cell configuration. ◆ Option 1: The existing information element does not have a list structure. The existing information element may be, for example, downlinkConfigCommon in spCellconfigCommon / sCellConfigCommon. ◆ Option 2: The existing information element has a list structure. The existing information element may be, for example, downlinkBWP-ToAddModList in spCellConfigDedicated / sCellConfigDedicated.

[0150] The integration of existing information elements in option 1 / 2 may be based on several methods:

[0151] ◆ Option 1: Existing information elements (which do not have a list structure) are integrated among multiple cells and defined as one list. An add / modify list having the name of the existing information element + "ToAddModList" and a release list having the name of the existing information element + "ToReleaseList" may be defined. The names of information elements in the list may be represented by the name of the existing information element + index. Each list may be a list of existing information elements (or the index of that information element). The list may be based on at least one of the following options:

[0152] ◆ Option 1: The existing information element corresponding to the SpCell is placed first in the list, and the existing information elements corresponding to the SCells are placed in the list in ascending order of SCell index. The order / index of one or more existing information elements in the list may be based on at least one of the following options 1x / 1y: ◆ Option 1x: The index of the information element corresponding to the SpCell may be 0, and the index of the information element corresponding to the SCell may be the index of the existing information element corresponding to the SCell. For example, when downlinkConfigCommon in spCellconfigCommon and two downlinkConfigCommon in sCellConfigCommon are integrated, if the indices of the existing information elements corresponding to the two SCells are 1 and 2, in the integrated list downlinkConfigCommonToAddModList, indices 0, 1, and 2 of downlinkConfigCommon may be defined. A downlinkConfigCommon with index 0 may correspond to one SpCell (downlinkConfigCommon in spCellConfigCommon), and downlinkConfigCommon with indexes 1 and 2 may correspond to two SCells (downlinkConfigCommon in two sCellConfigCommon). --Option 1y: The index of an information element corresponding to an SpCell may be 1, and the index of an information element corresponding to an SCell may be a value obtained by adding 1 to the index of an existing information element corresponding to the SCell. For example, when a downlinkConfigCommon in spCellconfigCommon and two downlinkConfigCommon in sCellConfigCommon are integrated, if the indices of the existing information elements corresponding to the two SCells are 1 and 2, indices 1, 2, and 3 of downlinkConfigCommon may be defined in the integrated list downlinkConfigCommonToAddModList.The downlinkConfigCommon with index 1 may correspond to one SpCell (downlinkConfigCommon in spCellConfigCommon), and the downlinkConfigCommon with indexes 2 and 3 may correspond to two SCells (downlinkConfigCommon in two sCellConfigCommon).

[0153] - Option 2: Existing information elements corresponding to SCells are arranged in the list in ascending order of SCell index. Existing information elements corresponding to SpCells may be arranged at the end of the list. The index of the existing information element corresponding to the SpCell may be the last index of the existing information element corresponding to the SCell plus 1, or may be a special value for the SpCell (e.g., 0).

[0154] - Option 3: One or more existing information elements are placed in the list according to the order in which they are notified by configuration / indication. The configuration / indication may be an RRC IE / MAC CE / DCI / SIB.

[0155] - Option 4: There is no restriction on the order of one or more existing information elements in the list.

[0156] Option 2: Existing information elements (having a list structure) are aggregated across multiple cells and defined as one list. The aggregated list may be based on at least one of the following options:

[0157] - Option 1: The consolidated list has a nested structure. The consolidated list may be named using the same rules as option 1. For example, the name of the consolidated add / modify list may be the name of the existing information element plus the name of "ToAddModList" ("...ToAddModListToAddModList").

[0158] ◆ Option 2: The consolidated list does not have a nested structure. The consolidated list may be a list of one or more elements in one or more existing information elements (lists before consolidation). The order / index of one or more elements in the consolidated list may be based on at least one of the following options 1a / 1b. ◆ Option 1a: The index of an element in the consolidated list may be represented by x, y. x may be based on the rules of option 1x / 1y in alternative 1. y may be an index corresponding to an existing information element of the corresponding cell. For example, if the existing information element "downlinkBWP-ToAddModList" corresponding to SpCell includes three BWP-Downlinks, each with indexes 1, 2, and 3, respectively, then by applying option 1a (and option 1x), the three BWP-Downlinks in the consolidated list "downlinkBWP-ToAddModList" may have indexes 0-1, 0-2, and 0-3. The name of an element in the integrated list may be the element name in the existing information element + "xy", the element name in the existing information element + "xy", the element name in the existing information element + "x,y", etc. --◆Option 1b: The index of an element in the integrated list may be represented by z. The maximum number of elements in the existing information element may be MAX. In the integrated list, the index z of an element corresponding to an SpCell may be the index of an element in the existing information element corresponding to the SpCell. In the integrated list, the index z of an element corresponding to an SCell may be i×MAX+j, where i is the index corresponding to the SCell and j is the index of an element in the existing information element corresponding to the SCell.For example, if downlinkBWP-ToAddModList in the existing information element spCellConfigCommon corresponding to SpCell includes two BWP-Downlinks, with the two BWP-Downlinks having indices 1 and 2, respectively, and downlinkBWP-ToAddModList in the existing information element sCellConfigCommon corresponding to SCell index 1 includes two BWP-Downlinks, with the two BWP-Downlinks having indices 1 and 2, respectively, and MAX is 4, the indices of the elements in the integrated list may be 1, 2, 5, and 6. Here, the indices 1 and 2 of the elements in the integrated list correspond to the two BWP-Downlinks in downlinkBWP-ToAddModList in the existing information element spCellConfigCommon, respectively, and the indices 5 and 6 of the elements in the integrated list correspond to the two BWP-Downlinks in downlinkBWP-ToAddModList in the existing information element sCellConfigCommon corresponding to SCell index 1, respectively. The name of the element in the consolidated list may be the name of the element in the existing information element + "z", etc.

[0159] Option 3: One or more elements in one or more existing information elements are arranged in the consolidated list according to the order / index signaled by the configuration / indication. The configuration / indication may be an RRC IE / MAC CE / DCI / SIB. At least one of the name of the consolidated list and the names of the elements in the list may be based on Option 1 or 2.

[0160] According to embodiment B1, by integrating existing information elements in multiple settings corresponding to multiple cells, the processing load of the gNB / UE can be reduced. Furthermore, if the values ​​of the existing information elements may be common between multiple cells, by integrating the existing information elements between multiple cells, the signaling overhead can be reduced.

[0161] <Embodiment B2> Embodiment B2 relates to changing the structure of setting information within a cell.

[0162] A combination of Embodiment B1 and Embodiment B2 may be applied. One or both of the following Embodiments B2-1 and B2-2 may be applied.

[0163] <<Embodiment B2-1>> An existing information element that groups together multiple existing information elements (having a nested structure) within one cell setting may be deleted, thereby reducing the nested structure.

[0164] By eliminating the nested structure of the existing information elements, the functions of the existing information elements may disappear or may not be supported. The existing information elements having a nested structure may be at least one of BWP, pdcch-config, pdcch-ConfigCommon, pdsch-Config, and pdsch-ConfigCommon.

[0165] For example, a method for eliminating the nested structure of settings related to BWP (BWP-DownlinkCommon / BWP-DownlinkDedicated) may include the following three steps.

[0166] ◆ Phase 1: The nested structure of the existing information element genericParameters (BWP structure) may be eliminated. - ◆ At least one of locationAndBandwidth, subcarrierSpacing, and cyclicPrefix included in the existing information element genericParameters may be placed / expanded outside / in parallel with genericParameters, or may be deleted from genericParameters. This procedure may be applied to all existing information elements including genericParameters, or to some existing information elements including genericParameters. Existing information elements including genericParameters include BWP-DownlinkCommon and bwp-Common in BWP-Downlink. This procedure may affect DownlinkConfigCommonSIB, DownlinkConfigCommon, downlinkBWP-ToAddModList in ServingCellConfig, etc.

[0167] ◆ Phase 2: The nested structure of the existing information elements BWP-DownlinkCommon / BWP-DownlinkDedicated may be eliminated. This phase may be based on at least one of the following options: ◆ Option 1: The existing information elements pdcch-Config, pdcch-ConfigCommon, pdsch-Config, pdsch-ConfigCommon, genericParameters, bwp-id, sps-Config, radioLinkMonitoringConfig, etc. included in the existing information elements BWP-DownlinkCommon / BWP-DownlinkDedicated may be placed / deployed outside / in parallel with BWP-DownlinkCommon / BWP-DownlinkDedicated, or may be deleted from BWP-DownlinkCommon / BWP-DownlinkDedicated. In the first stage, if the nested structure of genericParameters is expanded, existing information elements (at least one of locationAndBandwidth, subcarrierSpacing, and cyclicPrefix) expanded from genericParameters may also be placed / expanded outside / in parallel with DownlinkCommon / BWP-DownlinkDedicated. - ◆ Option 2: The nested structure within at least one of the existing information element spCellConfigDedicated and the initialDownlinkBWP within the existing information element sCellConfigDedicated may be maintained.

[0168] ◆ Phase 3: The complexity of the configuration may be reduced by deleting all or part of the BWP-related configuration. This may result in the loss of BWP functionality. - ◆ If option 1 in Phase 2 is applied, existing information elements in initialDownlinkBWP and existing information elements in bwp-Dedicated in downlinkBWP in downlinkBWP-ToAddModList are redundantly deployed in BWP-DownlinkDedicated in spCellConfigDedicated / sCellConfigDedicated. The deployed information elements inherit the values ​​of the existing information elements in initialDownlinkBWP, and existing information elements in bwp-Dedicated may be deleted. The deployed information elements inherit the values ​​of the existing information elements in bwp-Dedicated, and existing information elements in initialDownlinkBWP may be deleted. -◆When option 2 of the second stage is applied, the existing information elements in the initialDownlinkBWP are maintained in BWP-DownlinkDedicated in spCellConfigDedicated / sCellConfigDedicated. The name of the information element based on the existing information element in the initialDownlinkBWP may be a name indicating the band used for initial access, and the expanded information element may inherit the value of the existing information element in bwp-Dedicated in the downlinkBWP in downlinkBWP-ToAddModList.

[0169] In the above, the method of changing the configuration structure for BWP-DownlinkCommon / BWP-DownlinkDedicated can also be applied to the configuration structure for BWP-UplinkCommon / BWP-UplinkDedicated, and can also be applied to the configuration structure for uplinkConfig / supplementaryUplink in ServingCellConfig / ServingCellConfigSIB.

[0170] A BWP may be a virtual BWP including one or more BWPs. In the present disclosure, BWP and virtual BWP may be interchangeable. In the present disclosure, initial DL BWP, initial DL virtual BWP, initialDownlinkBWP, and initialDownlinkVirtualBWP may be interchangeable. In the present disclosure, initial UL BWP, initial UL virtual BWP, initialUplinkBWP, and initialUplinkVirtualBWP may be interchangeable.

[0171] Embodiment B2-1 may be based on at least one of the following examples.

[0172] Example 2-10 (existing cell settings, Figure 18)

[0173] - spCellConfigCommon / sCellConfigCommon (ServingCellConfigCommon structure) in CellGroupConfig, which contains: - { - downlinkConfigCommon (DownlinkConfigCommon structure), which contains: - { - frequencyInfoDL - initialDownlinkBWP (BWP-DownlinkCommon structure), which contains: - { - pdcch-ConfigCommon - pdsch-ConfigCommon (BWP structure), which contains: - genericParameters { - locationAndBandwidth - SubcarrierSpacing - cyclicPrefix - - - -

[0174] - servingCellConfigCommon (servingCellConfigCommonSIB structure) in SIB1, which contains: - { - downlinkConfigCommon (DownlinkConfigCommonSIB structure), which contains: - { - frequencyInfoDL - initialDownlinkBWP (BWP-DownlinkCommon structure), which contains: - { - pdcch-ConfigCommon - pdsch-ConfigCommon - genericParameters (BWP structure), which contains: - { - locationAndBandwidth - SubcarrierSpacing - cyclicPrefix - - - -

[0175] - spCellConfigDedicated / sCellConfigDedicated (ServingCellConfig structure) in CellGroupConfig, which contains: - { - initialDownlinkBWP (BWP-DownlinkDedicated structure), which contains: - { - pdcch-Config - pdsch-Config - sps-Config - radioLinkMonitoringConfig -} - firstActiveDownlinkBWP-Id - bwp-InactivityTimer - defaultDownlinkBWP-Id - downlinkBWP-ToAddModList, which contains: - { - downlinkBWP (BWP-Downlink structure), which contains: - { - bwp-id=1 - bwp-Common (BWP-DownlinkCommon structure), which contains: - { - pdcch-ConfigCommon - pdsch-ConfigCommon ------------------genericParameters (BWP structure), which contains the following: ------------------{ ------------------locationAndBandwidth ------------------subcarrierSpacing ------------------cyclicPrefix ------------------ ------------------} ------------------bwp-Dedicated (BWP-Downlink structure), which contains the following: ------------------{ ------------------pdcch-Config ------------------pdsch-Config ------------------sps-Config ------------------radioLinkMonitoringConfig ------------------ ------------------ -- --

[0176] ◆ Example 2-11 (First stage, FIG. 19) The locationAndBandwidth, SubcarrierSpacing, and cyclicPrefix included in the existing information element BWP structure are expanded / placed outside the BWP structure.

[0177] Example 2-12-1 (Option 1 of the second stage, Figure 20) The existing information elements pdcch-ConfigCommon, pdsch-ConfigCommon, locationAndBandwidth, SubcarrierSpacing, cyclicPrefix, pdcch-Config, pdsch-Config, sps-Config, radioLinkMonitoringConfig, and bwp-id included in the BWP-DownlinkCommon / BWP-DownlinkDedicated structure are expanded / placed outside the BWP-DownlinkCommon / BWP-DownlinkDedicated structure.

[0178] ◆ Example 2-12-2 (Option 2 of the second stage, Figure 21) The initialDownlinkBWP (BWP-DownlinkDedicated structure) in the existing information element spCellConfigDedicated / sCellConfigDedicated (ServingCellConfig structure) is maintained. The pdcch-ConfigCommon, pdsch-ConfigCommon, locationAndBandwidth, SubcarrierSpacing, cyclicPrefix, pdcch-Config, pdsch-Config, sps-Config, radioLinkMonitoringConfig, and bwp-id included in the existing information element BWP-DownlinkCommon structure are expanded / placed outside the BWP-DownlinkCommon / BWP-DownlinkDedicated structure.

[0179] ◆ Example 2-13-1 (Third stage after option 1 in the second stage, Figure 22) The existing information elements pdcch-ConfigCommon, pdsch-ConfigCommon, locationAndBandwidth, SubcarrierSpacing, cyclicPrefix, pdcch-Config, pdsch-Config, sps-Config, and radioLinkMonitoringConfig included in the existing information element BWP-Downlink structure are expanded / placed outside the BWP-Downlink structure. The existing information elements bwp-id, pdcch-Config, pdsch-Config, sps-Config, and radioLinkMonitoringConfig included in the existing information element BWP-Downlink structure are deleted.

[0180] ◆ Example 2-13-1 (Third stage after option 2 in the second stage, Figure 23) The existing information elements pdcch-ConfigCommon, pdsch-ConfigCommon, locationAndBandwidth, SubcarrierSpacing, cyclicPrefix, pdcch-Config, pdsch-Config, sps-Config, and radioLinkMonitoringConfig included in the existing information element BWP-Downlink structure are expanded / placed outside the BWP-Downlink structure. The existing information element bwp-id included in the existing information element BWP-Downlink structure is deleted.

[0181] <<Embodiment B2-2>> Multiple identical existing information elements within one cell configuration may be integrated.

[0182] The method for integrating multiple existing information elements may be based on the following algorithm (steps 1 and 2). ◆ Step 1: An existing list of existing information elements (structures) X in the configuration for a cell is considered. ◆ Step 2: If the configuration includes the list XToAddModList, XToAddModList is deleted. In the configuration, for each existing information element Y in the existing information element X, a list YToAddModList is defined that includes one or more existing information elements Y each corresponding to one or more existing information elements X in the existing list. The order / index / name of the information elements Y may be based on embodiment B2-1.

[0183] This algorithm may be repeated as appropriate to reduce nesting within the configuration.

[0184] ◆ Example 2-2B-12 (state in which option 1 of the second stage of embodiment B2-1 is applied to option B and option 2 of embodiment B1, Figure 24) In Example 1-B2, pdcch-ConfigCommon, pdsch-ConfigCommon, locationAndBandwidth, SubcarrierSpacing, cyclicPrefix, pdcch-Config, pdsch-Config, sps-Config, radioLinkMonitoringConfig, bwp-id contained in the BWP-DownlinkCommon / BWP-DownlinkDedicated structure are deployed / placed outside the BWP-DownlinkCommon / BWP-DownlinkDedicated structure.

[0185] ◆ Example 2-2B-12-1 (state in which option 1 of the second stage of embodiment B2-1 and embodiment B2-2 have been applied once to option B and option 2 of embodiment B1; FIG. 25) --◆ Within reconfigWithSync, multiple downlinkConfigCommons within multiple CellConfigCommons within CellConfigCommonToAddModList are changed to multiple downlinkConfigCommons within downlinkConfigCommonToAddModList in CellConfigCommon. --◆ Within SpCellConfig, downlinkBWP-ToAddModLists within multiple CellConfigDedicated within CellConfigDedicatedToAddModList are changed to multiple downlinkBWP-ToAddModLists within downlinkBWP-ToAddModListToAddModList in CellConfigDedicated. In SpCellConfig, uplinkConfig / supplementaryUplink in multiple CellConfigDedicated in CellConfigDedicatedToAddModList are changed to multiple uplinkConfig / supplementaryUplink in uplinkConfigToAddModList / supplementaryUplinkToAddModList in CellConfigDedicated. Each information element (initialDownlinkBWP, firstActiveDownlinkBWP-Id, bwp-InactivityTimer, defaultDownlinkBWP-Id) in multiple CellConfigDedicated in CellConfigDedicatedToAddModList is changed to a list of information elements in CellConfigDedicated (...ToAddModList).

[0186] ◆ Example 2-2B-12-2 (state in which option 1 of the second stage of embodiment B2-1 and embodiment B2-2 are applied twice to option B and option 2 of embodiment B1, FIG. 26) --◆ Within CellConfigCommon, multiple downlinkConfigCommons in downlinkConfigCommonToAddModList are changed to multiple initialDownlinkBWPs in initialDownlinkBWPToAddModList in downlinkConfigCommon. --◆ Within CellConfigDedicated, multiple downlinkBWP-ToAddModLists in initialDownlinkBWPToAddModList / downlinkBWP-ToAddModListToAddModList are changed to multiple BWP-DLs in downlinkBWP-ToAddModList. In CellConfigDedicated, multiple uplinkConfigs / supplementaryUplinks in uplinkConfigToAddModList / supplementaryUplinkToAddModList are changed to uplinkBWP-ToAddModListToAddModList in uplinkConfig / supplementaryUplink. In CellConfigDedicated, each information element (initialUplinkBWP, firstActiveUplinkBWP-Id, bwp-InactivityTimer) in multiple uplinkConfigs / supplementaryUplinks in uplinkConfigToAddModList / supplementaryUplinkToAddModList is changed to a list of information elements (...ToAddModList) in uplinkConfig / supplementaryUplink.

[0187] ◆Example 2-2B-12-2 (state in which option 1 of the second stage of embodiment B2-1 and embodiment B2-2 are applied three times to option B and option 2 of embodiment B1, Figure 27) - ◆In downlinkConfigCommon, each information element (frequencyInfoDL, pdcch-ConfigCommon, pdsch-ConfigCommon, locationAndBandwidth, subcarrierSpacing, cyclicPrefix) in multiple initialDownlinkBWPs in initialDownlinkBWPToAddModList is changed to a list of information elements in initialDownlinkBWP (...ToAddModList). - Within CellConfigDedicated, each information element (bwp-id, pdcch-ConfigCommon, pdsch-ConfigCommon, locationAndBandwidth, subcarrierSpacing, cyclicPrefix, pdcch-Config, pdsch-Config, sps-Config, radioLinkMonitoringConfig) within multiple BWP-DLs within downlinkBWP-ToAddModList is changed to a list (...ToAddModList) of information elements within BWP-Downlink within downlinkBWP. Within uplinkConfig / supplementaryUplink, each list (initialUplinkBWPToAddModList, uplinkBWP-ToAddModListToAddModList) is changed to information elements (initialUplinkBWP, uplinkBWP-ToAddModList).

[0188] ◆Example 2-2B-12-2 (state in which option 1 of the second stage of embodiment B2-1 and embodiment B2-2 are applied four times to option B and option 2 of embodiment B1, Figure 28) - ◆In initialDownlinkBWP in downlinkConfigCommon, each list (pdcch-ConfigCommonToAddModList, pdsch-ConfigCommonToAddModList) is changed to information elements (pdcch-ConfigCommon, pdsch-ConfigCommon).

[0189] According to embodiment B2, in a configuration corresponding to one cell, by deploying / integrating existing information elements, the processing load of the gNB / UE can be reduced. Also, in a configuration corresponding to one cell, when values ​​of existing information elements may be common among multiple existing information elements, by integrating multiple existing information elements, the signaling overhead can be reduced.

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

[0191] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

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

[0193] Furthermore, notification of any information to the UE in the above embodiments may be performed periodically, semi-persistently, or aperiodically.

[0194] <<Notification of Information from UE>> In the above-described embodiments, notification of any information from the UE [to the NW] (in other words, transmission / report 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), a specific signal / channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

[0195] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID, which is not defined in existing standards, in the MAC subheader.

[0196] If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.

[0197] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.

[0198] <<Regarding Application of Each Embodiment>> In a UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the above-mentioned embodiments may be applied (used) when one or more of the following conditions are met: - a higher layer parameter indicating the specific processes / operations / controls / assumptions / information is configured; - the specific processes / operations / controls / assumptions / information is determined based on related higher layer parameters; - the specific processes / operations / controls / assumptions / information is specified / activated / triggered by a MAC CE / DCI / UCI / resource / channel / RS; - a specific UE capability indicating (or related to) the specific processes / operations / controls / assumptions / information is reported or supported; - the application of the specific processes / operations / controls / assumptions / information is determined based on specific conditions.

[0199] The specific UE capability may indicate at least one of the following: - Support for the specific process / operation / control / assumption / information - Capability of each embodiment - Capability of each option in each embodiment, or capability of a combination of multiple options in each embodiment - Capability of each option in each embodiment, or capability of a combination of multiple options in each embodiment - UE supports DWS [in the corresponding CC / serving cell] - UE supports extended PHR [in the corresponding CC / serving cell].

[0200] Furthermore, the above-mentioned specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (e.g., one or a combination of a cell, a band, a band combination, a BWP, a component carrier, etc.), or may be a capability for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or may be a capability for each subcarrier spacing (SubCarrier Spacing (SCS)), or may be a capability for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

[0201] Furthermore, the specific UE capability may be a capability that is applied to all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

[0202] If the above conditions are not met, the UE / BS may follow the behavior specified in existing 3GPP releases.

[0203] (Supplementary Notes) The following inventions are supplementary notes regarding one embodiment (Embodiment B1) of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiver that receives a cell group configuration for a cell group including a special cell and one or more secondary cells; and a controller that controls communication using the cell group based on the cell group configuration, wherein the cell configuration for one cell in the cell group configuration includes one or more information elements for multiple cells in the cell group. [Supplementary Note 2] The terminal described in Supplementary Note 1, wherein the cell group includes multiple secondary cells, and the cell configuration for one cell includes the one or more information elements for the multiple secondary cells. [Supplementary Note 3] The terminal described in Supplementary Note 1 or Supplementary Note 2, wherein the cell configuration for the special cell includes the one or more information elements for the special cell and the one or more secondary cells, and the one or more information elements are at least one of a configuration common to multiple terminals and a configuration individual to a terminal. [Supplementary Note 4] The terminal according to any one of Supplementary Notes 1 to 3, wherein a first cell configuration for the special cell includes the one or more information elements for the special cell and the one or more secondary cells, and a second cell configuration for the one or more secondary cells includes information for referencing the first cell configuration.

[0204] (Supplementary Notes) The following inventions are supplementary notes regarding one embodiment (Embodiment B2) of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiver that receives a cell configuration for a cell; and a controller that controls communication using the cell based on the cell configuration, wherein the cell configuration does not include one or more structures in a configuration of a specific wireless communication system, but includes one or more information elements in the one or more structures. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the cell configuration includes one or more information elements in one of the one or more structures. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the one or more structures indicate a bandwidth portion (BWP) configuration. [Supplementary Note 4] The terminal according to any of Supplements 1 to 3, wherein the one or more structures indicate a bandwidth portion (BWP) configuration, and the cell configuration includes an initial downlink BWP configuration.

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

[0206] 29 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 (which may be simply referred to as system 1) may be a system that realizes communication using Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) specified by the Third Generation Partnership Project (3GPP).

[0207] The wireless communication system 1 may also 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)), etc.

[0208] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (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.

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

[0210] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The location, number, shape, size, etc. of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as the base station 10.

[0211] The wireless communication system 1 may utilize multi-input multi-output (MIMO). For example, one cell may be formed by one antenna / base station 10, or may be formed by multiple antennas / base stations 10. One [virtual] cell (which may be called, for example, a supercell) may be composed of multiple [virtual] cells (which may be called, for example, subcells). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell with a quasi-static / dynamically variable physical range. In this case, the wireless communication system 1 may be called a cell-free system.

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

[0213] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the 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 higher than 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 correspond to a higher frequency band than FR2.

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

[0215] The multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), an X2 / Xn interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

[0216] The base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

[0217] The core network 30 may include network functions (Network Functions (NF)) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). A single network node may provide multiple functions. Communication with an external network (e.g., the Internet) may also be performed via the DN.

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

[0219] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the wireless communication system 1. 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), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0220] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (e.g., other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

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

[0222] Furthermore, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), or the like may be used as an uplink channel.

[0223] The PDSCH transmits user data, higher layer control information, a System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit a Master Information Block (MIB).

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

[0225] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as a UL grant, a UL DCI, etc. Note that the PDSCH may be replaced with DL data, and the PUSCH may be replaced with UL data.

[0226] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources for searching for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.

[0227] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

[0228] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

[0229] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

[0230] 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 the 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.

[0231] 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 an SS (PSS, SSS) and a PBCH (and a DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as a reference signal.

[0232] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), or the like may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).

[0233] 30 is a diagram showing an example of the configuration of a base station according to an 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 the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

[0234] In this example, the functional blocks of the characteristic parts of the present 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 unit described below may be omitted.

[0235] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

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

[0237] The transceiver 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 transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0238] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit. The transmitting unit may be configured from a transmission processing unit 1211 and an RF unit 122. The receiving unit may be configured from a reception processing unit 1212, the RF unit 122, and a measurement unit 123.

[0239] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

[0240] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0241] The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

[0243] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform transmission processing 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 on the bit string to be transmitted, and output a baseband signal.

[0244] The transceiver unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 130.

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

[0246] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (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, thereby acquiring user data, etc.

[0247] The transceiver 120 (measurement unit 123) may perform measurements on 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 measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0248] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30 (e.g., network nodes that provide 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.

[0249] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0250] The base station 10 may be separated into three elements: a radio unit (RU), a distributed unit (DU), and a central unit (CU). For example, the RU may implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level functions of the physical layer (precoding, IFFT, FFT, etc.). The DU may implement higher-level functions of the physical layer (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement the functions of the PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer.

[0251] In the present disclosure, the base station 10 may include a single device that realizes all of the functions of the RU, DU, and CU, or may include multiple devices that each realize some of the functions of the RU, DU, and CU and are connected to each other. In the present disclosure, the base station 10 may be interchangeably read as RU / DU / CU.

[0252] The transceiver 120 may transmit a cell group configuration for a cell group including a special cell and one or more secondary cells. The controller 110 may control communication using the cell group based on the cell group configuration. The cell configuration for one cell in the cell group configuration may include one or more information elements for multiple cells in the cell group.

[0253] The transceiver 120 may transmit a cell configuration for the cell. The controller 110 may control communication using the cell based on the cell configuration. The cell configuration may include one or more information elements in one or more structures in a configuration of a specific wireless communication system, without including one or more structures in the one or more structures.

[0254] (User terminal) Fig. 31 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

[0255] In this example, the functional blocks of the characteristic parts of the present 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 unit described below may be omitted.

[0256] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on common understanding in the technical field to which the present disclosure relates.

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

[0258] The transceiver 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 transceiver unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0259] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0260] The transmitting / receiving antenna 230 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

[0261] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0262] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0263] The transceiver 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, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

[0264] The transmitter / receiver unit 220 (transmission processing unit 2211) may perform transmission processing 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 on the bit string to be transmitted, and output a baseband signal.

[0265] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, or if not, it may not be necessary to perform DFT processing as the transmission processing.

[0266] The transceiver unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 230.

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

[0268] The transceiver unit 220 (reception processing unit 2212) may apply reception processing such as analog-to-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 acquire user data, etc.

[0269] The transceiver 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.

[0270] The measurement unit 223 may derive channel measurements for CSI calculation based on the channel measurement resources. The channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on the interference measurement resources. The interference measurement resources may be at least one of an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. Note that CSI-IM may be referred to as CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. Note that in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeably read as interchangeable.

[0271] The transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.

[0272] The transceiver 220 may receive a cell group configuration for a cell group including a special cell and one or more secondary cells. The controller 210 may control communication using the cell group based on the cell group configuration. The cell configuration for one cell in the cell group configuration may include one or more information elements for multiple cells in the cell group.

[0273] The cell group may include a plurality of secondary cells, and the cell configuration for one cell may include the one or more information elements for the plurality of secondary cells.

[0274] The cell configuration for the special cell includes the one or more information elements for the special cell and the one or more secondary cells, and the one or more information elements may be at least one of a configuration common to multiple terminals and a configuration individual to a terminal.

[0275] The first cell configuration for the special cell may include the one or more information elements for the special cell and the one or more secondary cells, and the second cell configuration for the one or more secondary cells may include information for referencing the first cell configuration.

[0276] The transceiver 220 may receive a cell configuration for a cell. The controller 210 may control communication using the cell based on the cell configuration. The cell configuration may include one or more information elements in one or more structures in a configuration of a specific wireless communication system, without including one or more structures in the one or more structures.

[0277] The cell configuration may include one or more information elements in a structure in the one or more structures.

[0278] The one or more structures may indicate a bandwidth portion (BWP) setting.

[0279] The one or more structures may indicate a bandwidth portion (BWP) configuration, and the cell configuration may include an initial downlink BWP configuration.

[0280] (Hardware Configuration) Note that the block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0281] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As described above, the implementation method of each is not particularly limited.

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

[0283] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0284] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

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

[0286] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transceiver unit 120 (220), etc. may be realized by the processor 1001.

[0287] The processor 1001 also reads programs (program codes), 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 in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. 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 the other functional blocks may be implemented in a similar manner.

[0288] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

[0289] Storage 1003 is a computer-readable recording medium and may be composed of at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

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

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

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

[0293] 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), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using this hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0294] In addition, the devices included in the core network 30 (for example, network nodes that provide NF) may also be realized by the above-mentioned functional block / hardware configuration.

[0295] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

[0296] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed 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.

[0297] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering performed by a transceiver in the frequency domain, and specific windowing performed by a transceiver in the time domain.

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

[0299] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.

[0300] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0301] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0302] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0303] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0304] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0305] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0306] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.

[0307] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

[0308] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may be composed of one or more resource blocks.

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

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

[0311] A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

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

[0313] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0314] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

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

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

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

[0318] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

[0319] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0320] With respect to any information (e.g., variables, constants, parameters) described in the present disclosure, even if not specifically stated in the above embodiments, any first device (e.g., UE / base station) may notify any second device (e.g., base station / UE) of information indicating / specifying (or relating to) the value of the any information.

[0321] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

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

[0323] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0324] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0325] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0326] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), these wired and / or wireless technologies are included within the definition of transmission media.

[0327] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0328] 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," "layer," "number of layers," "rank," "resource," "resource set," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," "UE panel," "transmitting entity," "receiving entity," etc. may be used interchangeably.

[0329] In the present disclosure, the term "antenna port" may be interchangeably read as an antenna port for any signal / channel (e.g., a demodulation reference signal (DMRS) port). In the present disclosure, the term "resource" may be interchangeably read as a resource for any signal / channel (e.g., a reference signal resource, an SRS resource, etc.). The resource may include time / frequency / code / space / power resources. Furthermore, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0330] The group may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, a Reference Signal (RS) group, a Control Resource Set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, and the like.

[0331] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable terms.

[0332] In addition, in the present disclosure, the terms TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc. may be read interchangeably.

[0333] Furthermore, in the present disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) property," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

[0334] In the present disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interchangeable. In the present disclosure, terms such as sequence, list, set, group, cluster, and subset may be interchangeable.

[0335] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. The "spatial relationship information (TCI state)" may be interchangeable with "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. The TCI state and the TCI may be interchangeable. The spatial relationship information and the spatial relationship may be interchangeable.

[0336] In the present disclosure, terms such as "base station (BS)," "radio 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," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0337] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can be provided with communication service 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 ​​a base station and / or base station subsystem that provides communication service within that coverage.

[0338] In the present disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control / operate based on the information.

[0339] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0340] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0341] 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. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

[0342] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

[0343] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may also include devices that do 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.

[0344] 33 is a diagram showing an example of a vehicle according to an 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, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0345] The drive unit 41 is configured with at least one of an engine, a motor, and a hybrid of an engine and a motor, for example. 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 a user.

[0346] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (for example, an input / output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

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

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

[0349] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0350] The driving assistance system unit 64 includes various devices for providing functions to prevent accidents and reduce the driver's driving burden, 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 Units (IMUs), Inertial Navigation Systems (INSs)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driving assistance functions or autonomous driving functions.

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

[0352] 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 an external device. For example, it transmits and receives various information to and from the external device 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. Furthermore, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (or may function as at least one of the base station 10 and the user terminal 20).

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

[0354] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device and displays it on an information service unit 59 provided in the vehicle. The information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 60 (or data / information decoded from the PDSCH)).

[0355] 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, axles 48, various sensors 50-58, and the like provided in the vehicle 40.

[0356] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present 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) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, terms such as an uplink channel and a downlink channel may be read as a sidelink channel.

[0357] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0358] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc.), or a combination thereof.

[0359] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0360] Each aspect / embodiment described in the present disclosure may be a technology other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

[0361] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0362] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0363] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.

[0364] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0365] Furthermore, "determination" may be considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "determining" some kind of action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.

[0366] Furthermore, in this disclosure, "determine / determining" may be interchangeably read as "assume / assuming," "expect / expecting," "consider / considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interchangeably read as "assumes not to do...."

[0367] In the present disclosure, "expect" may be interchangeably read as "be expected." For example, "expect(s) ..." ("..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be interchangeably read as "be expected ..." or "do ... (if the above "..." is a to-infinitive, a verb with "to")," etc. "does not expect ..." may be interchangeably read as "be not expected ..." or "does not ... (if the above "..." is a to-infinitive, a verb with "to")," etc. Furthermore, "An apparatus A is not expected ..." may be interchangeably read as "an apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station).

[0368] The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0369] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0370] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0371] In the present 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 "coupled" may also be interpreted in the same way as "different."

[0372] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0373] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0374] In the present disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be interchangeable. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative, as expressions with "i-th" (i is an arbitrary integer) attached (for example, "highest" may be interchangeable with "i-th highest").

[0375] In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.

[0376] In the present disclosure, terms such as "when A, B," "if A, (then) B," "B upon A," "B in response to A," "B based on A," "B during / while A," "B before A," "B at (the same time as) / on A," "B after A," "B since A," and "B until A" may be interchangeable. Note that A, B, and the like herein may be replaced with appropriate expressions such as nouns, gerunds, and regular sentences, depending on the context. Note that the time difference between A and B may be approximately zero (immediately after or immediately before). A time offset may also be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after a time offset at which A occurs." The time offset (eg, one or more symbols / slots) may be predefined or may be specified by the UE based on signaled information.

[0377] In the present disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be read interchangeably.

[0378] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The description of the present disclosure is for illustrative purposes only and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A terminal comprising: a receiving unit that receives a cell group configuration for a cell group including a special cell and one or more secondary cells; and a control unit that controls communication using the cell group based on the cell group configuration, wherein the cell configuration for one cell in the cell group configuration includes one or more information elements for multiple cells in the cell group.

2. The terminal of claim 1, wherein the cell group includes a plurality of secondary cells, and the cell configuration for one cell includes the one or more information elements for the plurality of secondary cells.

3. The terminal of claim 1, wherein the cell configuration for the special cell includes the one or more information elements for the special cell and the one or more secondary cells, and the one or more information elements are at least one of a configuration common to multiple terminals and a configuration individual to a terminal.

4. The terminal of claim 1, wherein a first cell configuration for the special cell includes the one or more information elements for the special cell and the one or more secondary cells, and a second cell configuration for the one or more secondary cells includes information for referencing the first cell configuration.

5. A wireless communication method for a terminal, comprising: receiving a cell group configuration for a cell group including a special cell and one or more secondary cells; and controlling communication using the cell group based on the cell group configuration, wherein the cell configuration for one cell in the cell group configuration includes one or more information elements for multiple cells in the cell group.

6. A base station comprising: a transmitter that transmits a cell group configuration for a cell group including a special cell and one or more secondary cells; and a controller that controls communication using the cell group based on the cell group configuration, wherein the cell configuration for one cell in the cell group configuration includes one or more information elements for multiple cells in the cell group.

Images