Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure includes a reception 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 within the cell group configuration includes one or more information elements for a plurality of cells within the cell group.

Description

Technical Field

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

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was standardized with the aim of further increasing data rates and reducing latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was standardized with the aim of further increasing capacity and improving the height of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

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

[0004] Existing technical documents

[0005] Non-patent literature

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

[0007] The problem that the invention aims to solve

[0008] In future wireless communication systems (e.g., NR), the bundling of multiple cells for communication is being studied.

[0009] However, the structure of the information used to configure multiple cells for communication has not been adequately studied. If this structure is not sufficiently studied, there are concerns that it could lead to increased terminal load in signaling.

[0010] Therefore, one of the purposes of this disclosure is to provide a terminal, a wireless communication method, and a base station using settings for reducing the load on a base station / terminal.

[0011] Methods for solving problems

[0012] One aspect of the terminal disclosed herein includes: a receiving unit for receiving cell group settings for a cell group, the cell group comprising a special cell and one or more sub-cells; and a control unit for controlling communication using the cell group based on the cell group settings, wherein the cell settings for one cell within the cell group settings include one or more information elements for multiple cells within the cell group.

[0013] Invention Effects

[0014] According to one method disclosed herein, the load on the base station / terminal can be reduced. Attached Figure Description

[0015] Figure 1A as well as Figure 1B This is an example of how a time slot structure is set.

[0016] Figure 2 An example of the structure of XDD.

[0017] Figure 3A as well as Figure 3B This represents an example of the settings for time-domain and frequency-domain resources for XDD operations.

[0018] Figure 4 This represents an example of a community group setting.

[0019] Figure 5 This represents an example of cell group settings using SCell.

[0020] Figures 6A to 6C This represents an example of multiple carriers within a single serving cell.

[0021] Figures 7A to 7C This represents an example of multiple carriers within a serving cell involved in implementation method A1.

[0022] Figures 8A to 8C This illustrates an example of initial access using multiple carriers within a single serving cell, as described in implementation method A2.

[0023] Figure 9This represents an example of a combination of option A and option 1 in implementation method B1.

[0024] Figure 10 This represents an example of a combination of option A and option 2 in implementation method B1.

[0025] Figure 11 This represents an example of a combination of option B and option 1 in implementation method B1.

[0026] Figure 12 This represents an example of sCellToAddModList in option B and the combination of option 1 in implementation method B1.

[0027] Figure 13 This represents an example of a combination of option C and option 1 in implementation method B1.

[0028] Figure 14 This represents an example of a combination of option D and option 1 in implementation method B1.

[0029] Figure 15 This is an example of a variation of option C and the combination of option 1 in implementation method B1.

[0030] Figure 16 This represents an example of sCellToAddModList, a variation of option C and option 1 in implementation method B1.

[0031] Figure 17 This is an example of a variation of option D and option 1 in implementation method B1.

[0032] Figure 18 This represents an example of an existing community setting.

[0033] Figure 19 This represents an example of the first stage of implementation method B2-1.

[0034] Figure 20 This represents an example of option 1 in the second stage of implementation method B2-1.

[0035] Figure 21 This represents an example of option 2 in the second stage of implementation method B2-1.

[0036] Figure 22 This represents an example of the third stage following option 1 in the second stage of implementation method B2-1.

[0037] Figure 23 This represents an example of the third stage following option 3 in the second stage of implementation method B2-1.

[0038] Figure 24This represents an example of the state of option 1 in the second stage of implementation B2-1, which is applied in options B and option 2 of implementation B1.

[0039] Figure 25 This is an example of the state of option 1 and option 2 of implementation B2-1, which is the second stage of implementation B2-1, applied once in option B and option 2 of implementation B1.

[0040] Figure 26 This is an example of the state of option 1 and option B2-2 of the second stage of implementation B2-1, which are applied twice in option B and option 2 of implementation B1.

[0041] Figure 27 This is an example of the state of option 1 and option 2 of implementation B2-1, which are applied three times in option B and option 2 of implementation B1.

[0042] Figure 28 This is an example of the state of option 1 and option 2 of the second stage of implementation B2-1, which are applied four times in options B and 2 of implementation B1.

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

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

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

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

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

[0048] (Improved frequency utilization efficiency)

[0049] In future wireless communication systems (e.g., Beyond 5G, 6G), research is underway to improve frequency utilization efficiency (e.g., optimizing existing frequency bands). Specifically, research is being conducted on elastic cells that treat multiple frequency bands as a virtual single cell, cross-division duplex (XDD) where base stations simultaneously transmit and receive within / inter-carrier, and other technologies.

[0050] (XDD)

[0051] Prior to Rel.14, LTE primarily focused on the practical application of Frequency Division Duplex (FDD), and also supported Time Division Duplex (TDD).

[0052] On the other hand, in NR after Rel.15, TDD is mainly studied, while FDD is also supported (e.g., LTE band migration).

[0053] In FDD, the ability to simultaneously receive DL and transmit UL is preferred from a latency reduction perspective. On the other hand, in FDD, the resource ratio of DL to UL is fixed (e.g., 1 to 1).

[0054] In TDD, the ratio of DL and UL resources can be changed. For example, in a typical environment where DL traffic is relatively high, the amount of DL resources can be increased to improve DL throughput.

[0055] On the other hand, considering the transmission and reception time ratio based on Time Division Duplex (TDD) prior to Rel.16, the opportunity to transmit UL signals / channels is reduced compared to the opportunity to receive DL signals / channels. In such a case, the UE cannot transmit UL signals / channels frequently, raising concerns about delays in the transmission of important UL signals / channels. Furthermore, the reduced UL transmission opportunities compared to DL reception opportunities also raise concerns about signal / channel congestion (proliferation) during UL transmissions. Moreover, in TDD, the time resources available for transmitting UL signals / channels are limited, thus restricting the application of UL coverage enhancement techniques based on repetition, for example.

[0056] In future wireless communication systems (e.g., Rel. 17 / 18 and beyond), research is underway to introduce split-duplex methods that combine TDD and Frequency Division Duplex (FDD) into UL and DL.

[0057] This segmented duplexing method can also be called XDD (Cross Division Duplex). XDD can also refer to a duplexing method that performs frequency division multiplexing of the deep learning (DL) and ultra-low learning (UL) within one component carrier (CC) or multiple CCs in the TDD band (capable of simultaneously utilizing DL and UL). When this duplexing method is applied to multiple CCs, it can also mean that while DL time resources can be utilized in one CC, UL can be utilized in other CCs. These multiple CCs can also be CCs in the same band.

[0058] Figure 1A This diagram illustrates an example of TDD settings as specified prior to Rel.16. In this example, for the UE, TDD slot / symbol settings are configured within the bandwidth of one component carrier (CC) (also referred to as the cell or serving cell).

[0059] exist Figure 1A In the example shown, the time ratio of the DL time slot to the UL time slot is 4:1. In such a traditional TDD time slot / symbol setting, UL time resources cannot be fully guaranteed, raising concerns about UL transmission delays and reduced coverage performance.

[0060] Figure 1B This diagram illustrates an example of the structure of XDD. In this example, within one component carrier (CC), the resources used for DL ​​reception overlap temporally with the resources used for UL transmission. Based on this resource structure, UL resources can be secured, thereby improving resource utilization efficiency.

[0061] For example, such as Figure 1B As illustrated in the example, by configuring the two ends of a single carrier frequency domain (CC) as deep links (DLs) and sandwiching UL resources between these DLs, cross-link interference (CLI) with adjacent carriers can be avoided and mitigated. Furthermore, a guard zone can be defined at the boundary between the DL and UL resources.

[0062] Considering the complexity of handling self-interference, we need to consider the scenario where only the base station uses both DL and UL resources simultaneously. In other words, among resources where DL and UL overlap in time, we can also set up a structure where one UE uses DL resources and other UEs use UL resources.

[0063] Figure 2 This is a diagram illustrating an example of the structure of XDD. In this example, it is assumed that a portion of the DL resource of the TDD band domain is set as a UL resource, and the DL and UL partially overlap in time.

[0064] In this example, during the DL-only period, multiple UEs (UE#1 and UE#2 in this example) receive the DL channel / signal respectively.

[0065] Furthermore, during the period when DL and UL repeat in time, one UE (UE#1 in this example) receives DL channel / signal, while other UEs (UE#2 in this example) transmit UL channel / signal. During this period, the base station simultaneously transmits and receives both DL and UL.

[0066] Furthermore, during the UL-only period, multiple UEs transmit UL channels / signals separately.

[0067] In existing NR (e.g., those specified prior to Rel. 15 / 16), the UE uses DL frequency resources and UL frequency resources in the carrier as the DL Bandwidth Part (BWP) and UL BWP, respectively. To switch DL / UL frequency resources to other DL / UL frequency resources, multiple BWP settings and a mechanism for BWP adaptation are required.

[0068] Furthermore, in existing NR, the time resources in the TDD carrier of the UE are set in the TDD configuration to at least one of DL, UL, and flexible (FL).

[0069] Methods for configuring time-domain and frequency-domain resources for XDD operations are being investigated. For example, consideration is being given to optimizing the resource allocation based on avoiding the use of a portion of the UL resources used by other UEs (e.g., UE#2). Figure 2 UE#1 sets XDD resources (during DL and UL repetition) (refer to) Figure 3A ).

[0070] Furthermore, for example, considering the use of a portion of the DL resources used by other UEs (e.g., UE#1), the following can be considered: Figure 2 UE#2 settings XDD resources (refer to) Figure 3B ).

[0071] (Virtual Community)

[0072] For 6G, research is underway to improve frequency utilization efficiency and reduce scheduling overhead by treating multiple frequency bands as a single virtual cell. In elastic cells and inter-carrier XDD, multiple carriers are bundled together and treated as a single virtual cell, with control and UL performed only on specific carriers within these multiple carriers, allowing the remaining carriers to be used for data communication. This achieves low overhead. During RRC connections, UEs supporting carrier aggregation (CA) can perform control / UL only on specific carriers through cross-carrier scheduling.

[0073] Research is underway on scheduling all the frequency resources contained in a single CC, or bundling multiple CCs to define a carrier set (virtual CC) and scheduling resources with a larger granularity than that of a CC.

[0074] (Community Group Settings / Community Settings)

[0075] In NR / 5G, dual connectivity (DC) is achieved by setting up multiple cells within a cell group, thereby centrally managing the settings of multiple cells.

[0076] By using cell group settings ( Figure 4 When adding cells, the gNB does not need to modify the information set for each cell individually; it only needs to add the cell to the cell group. Figure 5 This setting allows gNB to easily add cells, even if the settings differ for each cell.

[0077] The CellGroupConfig structure has the following structure.

[0078] ◆The CellGroupConfig structure contains spCellConfig (SpCellConfig structure, SpCell settings) and sCellToAddModList (one or more SCellConfig structures, one or more SCell settings).

[0079] -◆spCellConfig includes servCellIndex (ServCellIndex structure, serving cell index), reconfigWithSync (ReconfigWithSync structure), and spCellConfigDedicated (dedicated SpCell settings, ServingCellConfig structure).

[0080] --◆The ReconfigWithSync structure contains spCellConfigCommon (public SpCell settings, ServingCellConfigCommon structure).

[0081] -◆The SCellConfig structure contains sCellIndex (SCellIndex structure, SCell index), sCellConfigCommon (common SCell settings, ServingCellConfigCommon structure), and sCellConfigDedicated (dedicated SCell settings, ServingCellConfig structure).

[0082] ◆The ServingCellConfigCommon structure contains physCellId (PhysCellId structure, physical cell index), downlinkConfigCommon (DownlinkConfigCommon structure, common DL settings), and uplinkConfigCommon (common UL settings).

[0083] -◆The DownlinkConfigCommon structure contains the initialDownlinkBWP (BWP-DownlinkCommon structure, initial DL BWP settings).

[0084] ◆The ServingCellConfig structure contains initialDownlinkBWP (BWP-DownlinkDedicated structure), firstActiveDownlinkBWP-Id, bwp-InactivityTimer, defaultDownlinkBWP-Id, downlinkBWP-ToAddModList (one or more BWP-Downlink structures), and uplinkConfig (UplinkConfig structure, UL settings).

[0085] -◆The UplinkConfig structure contains initialUplinkBWP (BWP-UplinkDedicated structure, initial UL BWP settings), uplinkBWP-ToAddModList (one or more BWP-Uplink structures), and firstActiveUplinkBWP-Id.

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

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

[0088] ◆The BWP-UplinkCommon structure contains genericParameters (BWP structure, generic parameters).

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

[0090] When an SCell is appended, sCellToAddModList contains several sCellConfigs (sCellConfig1, sCellConfig2, ...). sCellConfigs include sCellConfigCommon and sCellConfigDedicated.

[0091] In the absence of a DC (e.g., in the presence of carrier aggregation (CA)), cell groups are not configured; instead, multiple cells are configured on a per-cell basis.

[0092] In operation, there are sometimes no differences between parameters and their values ​​in the settings of multiple cells, resulting in redundant parameters.

[0093] When the CA's bandwidth is reduced for power saving or other reasons, the CA needs to modify the bandwidth of each of the following multiple cells. Additionally, the bandwidth of the BWP within each cell needs to be modified. Modifying the nested structure settings is complex when the cell's SCS is changed.

[0094] The complexity of the configured structure increases the processing load on the base station / terminal. The presence of redundant parameters increases signaling overhead. These factors raise concerns about reduced communication throughput.

[0095] Therefore, the inventors of this invention conceived of a method for unifying the structure of settings for more than one cell.

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

[0097] (Various rewrites)

[0098] In this disclosure, terms enclosed in parentheses "()" may also indicate explanations (e.g., spelling notes), rewrites, specific examples, supplementary explanations, etc., of the term immediately preceding it. Furthermore, in this disclosure, terms enclosed in frames "[]" may be interpreted either in conjunction with the term or without it. Additionally, "()" and "[]" may also be used for purposes / meanings other than those indicated therein.

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

[0100] In this disclosure, terms such as notification, activation, deactivation, indication (or indication), selection, configuration, update, and determination can be overridden. Similarly, terms such as support, control, ability to control, operation, and ability to operate can also be overridden.

[0101] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-level parameters, fields, Information Elements (IE), settings, etc., can also be modified interchangeably. In this disclosure, Medium Access Control (MAC) elements (MAC ControlElement (CE)), update commands, activation / deactivation commands, etc., can also be modified interchangeably.

[0102] In this disclosure, 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., positioning protocol messages (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP) messages, etc. from the core network), or a combination thereof.

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

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

[0105] In this disclosure, ceil(x), the ceiling function, and the floor function can be rewritten interchangeably. In this disclosure, floor(x), the floor function, and the floor function can be rewritten interchangeably. In this disclosure, sqrt(x), the square root of x, and the root of x can be rewritten interchangeably. In this disclosure, x mod y, mod(x, y), the mod function, and the modulo operation can be rewritten interchangeably. In this disclosure, Σ... i=M M+N-1 f(i), Σ i=M M+N-1 f i f(i) or f throughout i = M, M+1, ..., M+N-1 i The summation, f(M) + f(M+1) + ... + f(M+N-1), f M +f M+1 +…+f M+N-1 They can also be rewritten interchangeably. C(n, k) represents the number of combinations of choosing k values ​​from n values ​​(combinatorial coefficient) and binomial coefficients. n C k C n k They can also be rewritten interchangeably. In this disclosure, x / / y and floor(x / y) can also be rewritten interchangeably.

[0106] In this disclosure, A b The expressions A_b, Ab, and A with b appended to the lower right corner can also be rewritten interchangeably. In this disclosure, A c The expressions A^c and A with c appended to the upper right corner can also be rewritten interchangeably. In this disclosure, A b c The expressions A_b^c, A with b appended to the lower right and c appended to the upper right, can also be rewritten interchangeably. In this disclosure, x ～ It can be represented by assigning a ~ to x, and can also be called an x-shaped tilde. In this disclosure, x – It can be represented by assigning a - to x, or it can be called x-bar (bar). In this disclosure, x ＾ It can be represented by assigning ^ to x, and can also be called an x-hat.

[0107] In this disclosure, FR can be at least one of FR1, FR2, FR2-1, FR2-2, FR3, Asia-Pacific Hertz, and Terahertz. In this disclosure, the frequency range corresponding to FR1 can be 410MHz to 7125MHz. In this disclosure, FR2 can also include FR2-1 and FR2-2, the frequency range corresponding to FR2-1 can be 24250MHz to 52600MHz, and the frequency range corresponding to FR2-1 can be 52600MHz to 71000MHz.

[0108] The following abbreviations may also be used in this disclosure.

[0109] ◆FDM: Frequency Division Multiplexing

[0110] ◆TDM: Time Division Multiplexing

[0111] In this disclosure, structures, classes, and types can also be overridden with each other.

[0112] In this disclosure, RRC IE, information elements, variables, constants, parameters, and high-level parameters can also be overridden.

[0113] In this disclosure, the terms "representative cell", "specific cell", "special cell" (SpCell), and "unified cell" can be interchanged.

[0114] In this disclosure, the terms unify, combine, bundle, and simplify can be rewritten interchangeably.

[0115] In this disclosure, blocks, setting groups, parts, locations, ranges, and structures can also be overridden with each other.

[0116] In this disclosure, management and settings can also be rewritten.

[0117] In this disclosure, the cell index, CC index, serving cell index, SCell index, and physical cell index can also be overwritten.

[0118] In this disclosure, lists, add-modify lists (ToAddModList), and release lists (ToReleaseList) can also be overridden.

[0119] In this disclosure, the following terms can be interchanged: common settings, common cell settings, intra-cell UE common settings, common settings among multiple UEs, cell common settings, cell settings, ConfigCommon, reconfigWithSync, spCellConfigCommon, sCellConfigCommon, xCellConfigCommon, and CellConfigCommon. Similarly, the following terms can be interchanged: dedicated settings, dedicated cell settings, UE dedicated settings, cell settings, spCellConfigDedicated, sCellConfigDedicated, xCellConfigDedicated, and CellConfigDedicated. Finally, the following terms can be interchanged: xCell, spCell (SpCell), sCell (SCell), cell, serving cell, and CC.

[0120] In this disclosure, in a list (XToAddModList / XToReleaseList) containing one or more information elements X, the information element X contains an index / ID (e.g., X-Id / XIndex) = i, and the information element X is represented as Xi, which can also be rewritten.

[0121] In this disclosure, specific wireless communication systems, existing wireless communication systems, and 5G / NR can be modified to each other. In this disclosure, existing information elements, information elements of specific wireless communication systems, and settings of specific wireless communication systems can also be modified to each other.

[0122] (Wireless communication method)

[0123] (Implementation Method A)

[0124] <Implementation Method A1>

[0125] User Experience Capabilities

[0126] It can also specify the ability to support DL / UL (new UE capability, new UE capability information) using multiple different carriers as one serving cell. This new UE capability can also be specified as a capability supported differently from CA.

[0127] The new UE capabilities may also be specified for at least one of the following scenarios: the multiple carriers include both DL carriers and UL carriers; the multiple carriers include multiple DL carriers; and the multiple carriers include multiple UL carriers.

[0128] Instead of processing HARQ-ACK separately for multiple serving cells in a CA, the UE can also bundle multiple carriers from a single serving cell to process HARQ-ACK. In this case, the UE's load can be reduced.

[0129] These multiple carriers may not be a pair of DL and UL carriers within a single FDD band. They may also include DL / UL carriers with different center frequencies within a single TDD band. Furthermore, they may include one of the DL and UL carriers within a single TDD band, as well as carriers from other bands.

[0130] These multiple carriers can also span multiple band domains. These multiple band domains may also exclude the SUL band domain. These multiple band domains can include multiple FDD band domains, more than one TDD band domain, or band domains with different duplex modes (e.g., more than one FDD band domain and more than one TDD band domain).

[0131] Figures 6A to 6C This represents an example of multiple carriers within a single serving cell. Figure 6A One serving cell in the example contains a UL carrier and a DL carrier within the FDD band. Figure 6B One of the examples shows a serving cell containing a UL carrier and a DL carrier with the same center frequency within a TDD band. Figure 6C In one example, a serving cell includes one NUL carrier and one DL carrier with the same center frequency in the TDD band, and one SUL carrier in the SUL band.

[0132] Figures 7A to 7C This represents an example of multiple carriers within a serving cell involved in implementation method A1. For example... Figure 7A As in the example, a serving cell can also contain multiple UL / DL carriers within the FDD band. Similarly, a serving cell can contain UL and DL carriers within a first FDD band, and UL and DL carriers within a second FDD band. Figure 7B As in the example, a serving cell contains more than one UL carrier and DL carrier with different center frequencies within a TDD band. Here, the number of UL carriers / DL carriers within a TDD band may not be one. As in this example, a serving cell may also contain two DL carriers and one UL carrier within a TDD band. Figure 7CAs in the example, a serving cell can also contain multiple UL / DL carriers within multiple bands, or these multiple bands can include a TDD band, which contains only one of the UL carriers and one of the DL carriers. As in the example, a serving cell can also contain one UL carrier within a TDD band and DL carriers within other bands (e.g., a TDD band or an FDD band).

[0133] Different DL BWPs and UL BWPs for multiple carriers can also be configured within the serving cell. For UEs with the aforementioned new UE capabilities, different DL BWPs and UL BWPs for multiple carriers can also be configured within the serving cell. DL / UL BWPs can also be configured using an offset (e.g., resource block (RB) offset) from the NR-Absolute Radio Frequency Channel Number (ARFCN, the number on the global frequency grid) / point A (the common reference point of the RB grid) and bandwidth (e.g., the number of RBs).

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

[0135] The combination of multiple DL / UL bands that can be used as a single serving cell can also be specified / limited in the specification. For example, the combination can be limited to TDD bands only, FDD bands only, multiple carriers within the same band (intra-band), or FR1 only (a combination of bands within FR1). When multiple carriers within the same TDD band are used for both DL and UL, simultaneous transmission and reception on these multiple carriers may not be possible. Furthermore, the ability to simultaneously transmit and receive using multiple carriers within the same TDD band may be determined based on whether XDD within the same carrier / band is supported.

[0136] A UE with the aforementioned new UE capabilities or other new UE capabilities can also support (or be configured to support) more than one DL BWP from multiple carriers within a serving cell. At least one of the following can also be reported as a capability (information within the new UE capability information): the number of the more than one DL BWP (maximum number), the number of the multiple carriers (maximum number), the total bandwidth of the more than one DL / BWP (maximum bandwidth), the total bandwidth of the multiple carriers (maximum bandwidth), the bandwidth from the lower limit frequency to the upper limit frequency of the more than one DL / BWP (maximum bandwidth), and the bandwidth from the lower limit frequency to the upper limit frequency of the multiple carriers (maximum bandwidth).

[0137] At a certain point in time within a single serving cell, one DL BWP can be active, or multiple DL BWPs can be active.

[0138] For UL BWP, it can be the same as the aforementioned DL BWP. A UE with the aforementioned new UE capabilities or other new UE capabilities can support (or be configured to support) more than one UL BWP from multiple different carriers within a serving cell, and can also support (or be configured to support) one UL BWP from multiple different carriers within a serving cell. A UE with the aforementioned new UE capabilities or other new UE capabilities can also support (or be configured to support) more than one DL BWP and one UL BWP from multiple different carriers within a serving cell.

[0139] At any given time within a single service cell, one UL BWP can be active, or multiple UL BWPs can be active.

[0140] Combination of DL carrier and UL carrier

[0141] In cases where multiple different carriers within a serving cell are used for DL ​​and UL (multiple carriers within a serving cell include DL carriers and UL carriers with different center frequencies, or a serving cell includes multiple TDD carriers), the UE may also follow at least one of the following time resource determination methods 1 and 2.

[0142] [Time Resource Determination Method 1]

[0143] In cases where simultaneous transmission and reception are not possible (the UE does not support simultaneous transmission and reception), the UE may also follow a single TDD UL / DL setting (or a TDD UL / DL setting common to multiple carriers) to determine the time resources available on each carrier.

[0144] [Time Resource Determination Method 2]

[0145] When simultaneous transmission and reception are possible (and the UE supports simultaneous transmission and reception), the UE can also follow the TDD UL / DL settings of each carrier to determine the available time resources on each carrier. The TDD UL / DL settings (link direction) at a given time point can be consistent or different across these multiple carriers. Alternatively, even when simultaneous transmission and reception are possible, the UE can still follow a single TDD UL / DL setting, and the ability to perform simultaneous transmission and reception in each time resource can also follow other settings (e.g., XDD-oriented settings).

[0146] Combination of multiple DL carriers

[0147] In cases where multiple different carriers within a serving cell are used for DL ​​(multiple carriers within a serving cell include multiple DL carriers), the UE may also follow at least one of the following DL BWP usage methods 1 and 2.

[0148] [DL BWP Usage Method 1]

[0149] The UE can also treat a combination of multiple DL BWPs (e.g., multiple DL BWPs spanning multiple carriers) as a single DL BWP. Within this single DL BWP, resources / channels / signals spanning multiple carriers can also be configured / scheduled. These resources / channels / RS can also be CORESET / PDSCH / CSI-RS, etc. This single DL BWP can also be considered as a DL BWP composed of pseudo-contiguous frequency resources. As a frequency index (e.g., RB index) used for scheduling within a single DL BWP, a continuous index can also be provided for the frequency resources within this single DL BWP. The subcarrier spacing (SCS) can also be common between the multiple DL BWPs (within this single DL BWP).

[0150] [DL BWP Usage Method 2]

[0151] Multiple DL BWPs (a set of multiple DL BWPs) can be active simultaneously. Resources / channels / signals across these multiple DL BWPs (multiple carriers) can also be configured / scheduled. Alternatively, it can be specified that the UE does not intend for resources / channels / signals across these multiple DL BWPs (multiple carriers) to be configured / scheduled. These resources / channels / RS can also exist only within one DL BWP (or be disabled). These resources / channels / RS can also be CORESET / PDSCH / CSI-RS, etc. SCS can be common among these multiple DL BWPs. Different SCSs are also allowed among these multiple DL BWPs. BWP handover can also be an operation that simultaneously switches multiple DL BWPs to other multiple DL BWPs. These multiple DL BWPs can be activated / deactivated (on / off) individually, or switched to other DL BWPs one by one.

[0152] According to implementation method A1, the UE uses multiple carriers (e.g., a pair of non-FDD carriers (paired spectrum), excluding SUL) as DL carriers and UL carriers in a serving cell, thereby improving frequency utilization efficiency.

[0153] <Implementation Method A2>

[0154] Alternatively, during initial access, the UE can utilize (and may support) multiple different carriers. These multiple carriers may also be included in a single serving cell. The UE may also receive an SSB (synchronization signal and at least one PBCH) on at least one of these multiple carriers.

[0155] Figures 8A to 8C This illustrates an example of initial access using multiple carriers within a single serving cell, as described in implementation method A2.

[0156] like Figure 8A As in the example, a serving cell comprises a UL carrier and a DL carrier with different center frequencies within a TDD band. Here, the number of UL carriers / DL carriers within a TDD band may not be one. As in this example, a serving cell may also comprise a first DL carrier, a UL carrier, and a second DL carrier within a TDD band. The UE may also receive an SSB in the second DL carrier and a SIB1 PDSCH in the first DL carrier, through which the initial UL BWP within the UL carrier is indicated.

[0157] like Figure 8BAs in the example, a serving cell contains multiple UL carriers and DL carriers with different center frequencies within a TDD band. Here, the number of UL carriers / DL carriers within a TDD band may not be one. As in this example, a serving cell may also contain UL carriers within a first TDD band and DL carriers within a second TDD band. The UE may also receive an SSB and a SIB1 PDSCH in the DL carrier, and the initial UL BWP within the UL carrier is indicated via SIB1.

[0158] like Figure 8C As in the example, a serving cell can also contain multiple UL / DL carriers within the FDD band. Similarly, a serving cell can contain a first UL carrier and a second DL carrier within a first FDD band, and a first UL carrier and a second DL carrier within a second FDD band. The UE can also receive an SSB in the first DL carrier and a SIB1 PDSCH in the second DL carrier, with the initial UL BWP within the first UL carrier indicated via SIB1.

[0159] Different UL carriers during initial access

[0160] UL carriers that are defined as bands other than those used for SUL (e.g., bands defined for TDD / FDD / XDD) can also be set / indicated via system information (e.g., SIB1).

[0161] A UL carrier (initial UL BWP) with a different center frequency than SIB1 can also be notified / broadcast via SIB1. SIB1 can also notify / broadcast the parameters of the initial UL BWP, as well as the NR-ARFCN / pointA of that UL carrier. Alternatively, only UEs that support the notification of the initial UL BWP may recognize the notification (the initial UL BWP). The notification of the initial UL BWP can also be a mandatory function within a specific frequency range (FR) / band / version. The UE can also perform UL transmission (random access procedure, etc.) within the initial UL BWP notified via SIB1.

[0162] Multiple DL Carriers During Initial Access

[0163] The UE may also be instructed / set to receive SIB1 PDCCH / SIB1 PDSCH on a different carrier than the one receiving the SSB. The UE may also follow at least one of the following carrier determination methods 1 to 3.

[0164] [Carrier Determination Method 1]

[0165] Multiple candidates for a band / carrier can also be specified in the specification. Information elements / fields within the MIB (PBCH) can also notify one of these multiple candidates. The UE can also monitor the SIB1 PDCCH (Type 0-PDCCH) in the notified candidate carrier.

[0166] [Carrier Determination Method 2]

[0167] Multiple candidates for the band / carrier can also be specified in the specification. Fields within the SIB1 PDCCH can also notify one of these multiple candidates. The UE can also receive the SIB1 PDSCH on the carrier of the notified candidate.

[0168] [Carrier Determination Method 3]

[0169] The received band / carrier of SIB1 PDCCH / SIB1 PDSCH can also be specified in the specification. The association between the detected SSB's band / carrier and the received band / carrier of SIB1 PDCCH / SIB1 PDSCH can also be specified in the specification. The derivation rules (calculation formulas) for deriving the received band / carrier of SIB1 PDCCH / SIB1 PDSCH from the detected SSB's band / carrier can also be specified in the specification. The UE can also follow the specification to determine a carrier different from the received carrier of the SSB as the received carrier of SIB1 PDCCH / SIB1 PDSCH. The UE can also receive SIB1 PDCCH / SIB1 PDSCH on the determined carrier.

[0170] Random access procedures in different carriers during initial access

[0171] In IDLE mode, the UE can also be instructed / set to perform a random access procedure on a different carrier than the one on which it is camped (e.g., by sending a random access preamble).

[0172] Information related to the carrier / BWP used in the random access procedure can also be notified / broadcast via SIB1. This information may include the parameters of the BWP and the NR ARFCN / pointA of the carrier / BWP.

[0173] According to implementation method A2, the UE uses multiple carriers (e.g., a pair of non-FDD carriers (paired spectrum) that do not include SUL) during initial access, thereby improving frequency utilization efficiency.

[0174] (Implementation Method B)

[0175] <Implementation Method B1>

[0176] Implementation method B1 involves changes to the structure of setting information between multiple cells.

[0177] Not limited to DC (Distributed Cell), but also in CA (Cellular Cell), cell groups can be set up to facilitate the setting, management, and modification of parameters for each cell. Multiple cells can also be managed and configured as a cell group. Information elements of each cell can be changed to common information elements shared by the cell group or multiple cells.

[0178] By making redundant existing information elements public across multiple cells or within a cell, the structure can be simplified, and the processing load on the UE can be reduced. Furthermore, by publicly setting the values ​​of redundant existing information elements, signaling overhead can be reduced.

[0179] Within a cell group / cell, there are information elements that are managed through specific units (blocks).

[0180] Inter-cell information unification method refers to the rules, regulations, and principles used to unify, combine, bundle, and simplify information among multiple cells. For example, inter-cell information unification method can also represent a unit (block) that is unified among multiple cells.

[0181] Inter-cell information management methods are the rules, regulations, and principles used to manage information in the context of unifying information across multiple cells. For example, inter-cell information management methods can also refer to sharing information between multiple cells or bundling multiple cells together as a single cell for management.

[0182] The methods for unifying information between small intervals and for managing information between small intervals can also be combined and set.

[0183] <<Methods for Unifying Information Between Small Units>>

[0184] The existing cell configurations consist of multiple blocks. Each block contains one or more information elements (RRC IE). For example, these blocks may be common settings (xCellConfigCommon, reconfigWithSync, spCellConfigCommon, sCellConfigCommon) or dedicated settings (xCellConfigDedicated, spCellConfigDedicated, sCellConfigDedicated). One or more information elements within a specific block can be unified across multiple cells. The inter-cell information unification method can also be based on at least one of the following options.

[0185] ◆Option A: Information elements set in SpCell and SCell are managed separately. All or part of the information elements set in multiple SCells can also be unified.

[0186] ◆Option B: All or part of the information elements in the SpCell and SCell settings can also be unified.

[0187] ◆Option C: All or part of the dedicated settings (spCellConfigDedicated / sCellConfigDedicated) for SpCell and SCell can be unified. The common settings (reconfigWithSync / spCellConfigCommon) for SpCell and the common settings (sCellConfigCommon) for SCell can also be separated.

[0188] ◆Option D: All or part of the common settings for SpCell and SCell can be unified. The specific settings for SpCell and SCell can also be separated.

[0189] The information elements of the block (spCellConfigCommon / sCellConfigCommon) that maintain common settings by the unified information elements can be imported into a list that manages more than one block (xToAddModList), or into a list that manages information elements within common settings.

[0190] The inter-cell information unification method can also be based on at least one of the following examples.

[0191] ◆Example 1A (Option A)

[0192] -◆The information elements (one or more) contained in multiple sCellConfigCommon within multiple sCellConfigs in CellGroupConfig and sCellToAddModList can also be unified across multiple cells.

[0193] -◆The information elements (one or more) contained in multiple sCellConfigDedicated within multiple sCellConfigs in CellGroupConfig's sCellToAddModList can also be unified across multiple cells.

[0194] ◆Example 1B (Option B)

[0195] -◆In CellGroupConfig, all or part of the spCellConfigCommon in reconfigWithSync and the multiple sCellConfigCommon contained in multiple sCellConfig in sCellToAddModList can also be unified across multiple cells.

[0196] -◆In CellGroupConfig, all or part of (more than one information element) of the multiple sCellConfigDedicated contained in spCellConfigDedicated and multiple sCellToAddModList in sCellConfig can also be unified across multiple cells.

[0197] ◆Example 1C (Option C)

[0198] -◆Within CellGroupConfig, all or part (more than one information element) of the multiple sCellConfigCommon contained in multiple sCellConfigs within sCellToAddModList can also be unified across multiple cells.

[0199] -◆In CellGroupConfig, all or part of (more than one information element) of the multiple sCellConfigDedicated contained in spCellConfigDedicated and multiple sCellToAddModList in sCellConfig can also be unified across multiple cells.

[0200] ◆Example 1D (Option D)

[0201] -◆In CellGroupConfig, all or part of the spCellConfigCommon in reconfigWithSync and the multiple sCellConfigCommon contained in multiple sCellConfig in sCellToAddModList can also be unified across multiple cells.

[0202] -◆The information elements (one or more) contained in multiple sCellConfigDedicated within multiple sCellConfigs in CellGroupConfig's sCellToAddModList can also be unified across multiple cells.

[0203] <<Inter-district Information Management Methods>>

[0204] One or more information elements that are unified through the inter-cell information unification method can also be based on at least one of the following options.

[0205] ◆Option 1: The settings for one or more representative cells (specific cells) among multiple cells can also include one or more information elements from the settings of those multiple cells. The settings of the representative cells can also be referenced for cells other than the representative cells among those multiple cells.

[0206] ◆Option 2: Multiple cells can also be unified as one or more unified cells (specific cells). The settings of a unified cell can also include the settings of these multiple cells.

[0207] <<Examples of combinations of option A and options 1 / 2>>

[0208] The inter-cell information unification method and the inter-cell information management method can also be based on at least one of the following examples.

[0209] ◆Example 1A1 (A combination of option A and option 1, Figure 9 )

[0210] -◆One of multiple SCells can also be a representative cell. A representative cell can be, for example, the SCell with the lowest index (e.g., SCellIndex=1).

[0211] --◆The SCellConfig for the representative cell may also contain a list of multiple sCellConfigCommons corresponding to each of the multiple SCells (e.g., sCellConfigCommonToAddModList). The SCellConfig for each SCell other than the representative cell may not contain sCellConfigCommons. The SCellConfig for each SCell other than the representative cell may also contain an index for referencing the sCellConfigCommon of the representative cell (e.g., serving cell index / SCell index). The UE may also obtain the sCellConfigCommon corresponding to each SCell other than the representative cell from the SCellConfigCommonToAddModList for the representative cell.

[0212] --◆The SCellConfig for a representative cell may also contain a list of multiple sCellConfigDedicated entries (e.g., sCellConfigDedicatedToAddModList) that correspond to each of the multiple SCells. The SCellConfig for each SCell other than the representative cell may not contain sCellConfigDedicated entries. The SCellConfig for each SCell other than the representative cell may also contain an index (e.g., serving cell index / SCell index) for referencing the sCellConfigDedicated entries of the representative cell. The UE may also obtain the sCellConfigDedicated entries corresponding to each SCell other than the representative cell from the SCellConfigDedicatedToAddModList for the representative cell.

[0213] --◆The value of sCellConfigCommon, in whole or in part, can be common to multiple SCells. A SCellConfig representing a cell can also contain one sCellConfigCommon. SCellConfigs for SCells other than the cell may not contain all or part of sCellConfigCommon. SCellConfigs for SCells other than the cell can also contain indexes (e.g., serving cell index / SCell index) used to reference the sCellConfigCommon representing the cell. UEs with multiple SCells can also obtain the sCellConfigCommon corresponding to each SCell other than the cell by referring to the sCellConfigCommon within the SCellConfig representing the cell.

[0214] --◆The values ​​of all or part of the sCellConfigDedicated for multiple SCells can also be common to multiple SCells. A SCellConfig representing a cell can also contain one sCellConfigDedicated. SCellConfigs for SCells other than the cell may not contain all or part of the sCellConfigDedicated. SCellConfigs for SCells other than the cell can also contain an index (e.g., serving cell index / SCell index) used to reference the sCellConfigDedicated of the cell representing the cell. The UE can also obtain the sCellConfigDedicated corresponding to each SCell other than the cell representing the cell by referring to the sCellConfigDedicated in the SCellConfig representing the cell.

[0215] ◆Example 1A2 (A combination of option A and option 2, Figure 10 )

[0216] -◆ Multiple SCells can also be unified as a single cell.

[0217] -◆CellGroupConfig can also contain a single sCellConfig for the same cell, without containing sCellToAddModList.

[0218] --◆The SCellConfig for a unified cell can also contain a list of multiple sCellConfigCommons that correspond to multiple SCells (e.g., sCellConfigCommonToAddModList). The UE can also obtain the sCellConfigCommon corresponding to each SCell from the SCellConfigCommonToAddModList for the unified cell.

[0219] --◆The SCellConfig for a single cell can also contain a list of multiple sCellConfigDedicated entries (e.g., sCellConfigDedicatedToAddModList) that correspond to each of the multiple SCells. The SCellConfig for each SCell representing a cell may not contain sCellConfigDedicated entries. The UE can also obtain the sCellConfigDedicated entries corresponding to each SCell representing a cell from the SCellConfigDedicatedToAddModList for each SCell representing a cell.

[0220] --◆The values ​​of all or part of sCellConfigCommon for multiple SCells can also be common to multiple SCells. SCellConfig for a unified cell can also include sCellConfigCommon for one cell, but not all or part of sCellConfigCommon for other cells.

[0221] --◆The values ​​of all or part of sCellConfigDedicated for multiple SCells can also be common to multiple SCells. An SCellConfig for a unified cell can also contain sCellConfigDedicated for one cell, but not all or part of sCellConfigDedicated for other cells.

[0222] ◆Example 1V (Change)

[0223] -◆The SCellConfig for each SCell can also contain a list of multiple sCellConfigCommon that correspond to each of the multiple SCells (e.g., sCellConfigCommonToAddModList). The SCellConfigCommonToAddModList can also have the same information among the multiple sCellConfigs that correspond to each of the multiple SCells.

[0224] -◆The SCellConfig for each SCell can also contain a list of multiple sCellConfigDedicated objects corresponding to each of the multiple SCells (e.g., sCellConfigDedicatedToAddModList). The SCellConfigDedicatedToAddModList can also have the same information among the multiple sCellConfig objects corresponding to the multiple SCells.

[0225] <<Details of Option 1>>

[0226] As described above, within the cell settings, at least one first information element from all information elements within spCellConfig, including spCellConfigCommon within reconfigurationWithSync, sCellConfigCommon within sCellConfig, sCellConfigDedicated within sCellConfig, and sCellConfig, can be unified across multiple cells. Within the cell settings, second information elements other than the first information elements can be either bundled as a group and unified across multiple cells, or unified as individual information elements across multiple cells.

[0227] The second information element can also be an information element other than sCellConfigCommon / sCellConfigDedicated in sCellConfig for SCell. The group can also be an information element such as sCellConfigRest. The second information element can also be at least one of the following information elements.

[0228] sCellState-r16

[0229] secondaryDRX-GroupConfig-r16

[0230] preConfGapStatus-r17

[0231] goodServingCellEvaluationBFD-r17

[0232] plmn-IdentityInfoList-r17

[0233] npn-IdentityInfoList-r17

[0234] smtcs

[0235] The second information element can also be any information element other than spCellConfigCommon in reconfigWithSync for SpCell. The group can also be an information element such as spCellConfigRest. The second information element can also be at least one of the following information elements.

[0236] smtcs

[0237] rach-ConfigDedicated

[0238] daps-UplinkPowerConfig-r16

[0239] sl-PathSwitchConfig-r17

[0240] Within a cell group, a cell or unified cell can be either one cell or multiple cells. For SpCell, if at least one of spCellConfigCommon and spCellConfigDedicated in reconfigWithSync is unified as SCell information, the index for SpCell can also be a special value (e.g., 0).

[0241] The sCellConfig for each SCell other than the representative cell can also include indexes for the representative cell (serving cell index / CC index / physical cell index / SCell index), but not all or part of sCellConfigCommon / sCellConfigDedicated. The UE can also obtain the SCell settings from the representative cell's settings based on the index for the representative cell.

[0242] For a given cell group / cell, whether the cell group setting / cell setting is applied / set based on the inter-cell information unification method / inter-cell information management method of implementation method B1, or based on the existing specification of cell group setting / cell setting, can be notified / set / instructed through RRC IE / MAC CE / DCI, or through the value / existence / validity of information elements in the cell group setting / public cell setting / private cell setting. It can also depend on the base station implementation, or be based on the UE capabilities reported by the UE. For example, if a serving cell index / CC index exists in the public cell setting / private cell setting, the cell group setting / cell setting based on the inter-cell information unification method / inter-cell information management method of implementation method B1 can be applied / set; if a serving cell index / CC index does not exist in the public cell setting / private cell setting, the cell group setting / cell setting based on the existing specification of cell group setting / cell setting can be applied / set.

[0243] The inter-cell information unification method / inter-cell information management method in Implementation Method B1 can also be further applied to Implementation Method B2. For example, when sCellConfigCommon / sCellConfigDedicated is unified, the sCellConfig for one SCell may contain a list of sCellConfigCommon / sCellConfigDedicated (sCellConfigCommonToAddModList / sCellConfigDedicatedToAddModList), which contains sCellConfigCommon / sCellConfigDedicated corresponding to multiple cells respectively. For example, when sCellConfigCommon / sCellConfigDedicated is unified, the sCellConfig for one SCell may contain a list of each information element within sCellConfigCommon / sCellConfigDedicated, which contains values ​​corresponding to multiple cells respectively.

[0244] <<Detailed information on the combination of options A and 2>>

[0245] sCellConfigCommonToAddModList / sCellConfigDedicatedToAddModList can exist within the sCellConfig of a unified cell (as mentioned above). Figure 10 (This can also exist within CellGroupConfig.)

[0246] When a new SCell is added, an SCell can also be added to the cell group based on the following rule 1.

[0247] ◆Rule 1: In the lists sCellConfigCommonToAddModList / sCellConfigDedicatedToAddModList, the index of the SCell being appended can be any index of the first, last, or intermediate cell in the list. The index of the appended SCell can be any index in the first or intermediate of the list, and if a cell corresponding to that index already exists, only one cell can be added to that index, as well as any index larger than that index.

[0248] <<Examples of combinations of options B / C / D and options 1 / 2>>

[0249] The inter-cell information unification method and the inter-cell information management method can also be based on at least one of the following examples.

[0250] ◆Example 1-B1 (A combination of option B and option 1) Figure 11 as well as Figure 12 )

[0251] -◆ can also represent a cell or a SpCell.

[0252] -◆CellGroupConfig can also contain SpCellConfig and sCellToAddModList.

[0253] --◆The `reconfigWithSync` method within `spCellConfig` can also contain a list (e.g., `CellConfigCommonToAddModList`) of multiple common cell settings (e.g., `CellConfigCommon`) corresponding to multiple cells within a cell group (including `SpCell` and `SCell`). The `SCellConfig` for each `SCell` may not contain `sCellConfigCommon`. The `SCellConfig` for each `SCell` may also contain an index representing the `SpCell`. The UE can also obtain the `CellConfigCommon` corresponding to each `SCell` from the `CellConfigCommonToAddModList` for the `SpCell`.

[0254] --◆The spCellConfigDedicated within spCellConfig can also contain a list (e.g., CellConfigDedicatedToAddModList) of multiple dedicated cell settings (e.g., CellConfigDedicated) corresponding to multiple cells within a cell group (including SpCells and SCells). The SCellConfig for each SCell may not contain spCellConfigDedicated. The SCellConfig for each SCell may also contain an index representing the SpCell. The UE can also obtain the CellConfigDedicated corresponding to each SCell from the CellConfigDedicatedToAddModList for the SpCell.

[0255] --◆Each sCellConfig within sCellToAddModList can also contain CellConfigCommonToAddModList / CellConfigDedicatedToAddModList / CellConfigCommon / CellConfigDedicated. CellConfigCommonToAddModList / CellConfigCommon can also contain an index representing the corresponding cell. The UE can also use this index to retrieve the CellConfigCommon corresponding to each SCell from CellConfigCommonToAddModList within SpCellConfig. CellConfigDedicatedToAddModList / CellConfigDedicated can also contain an index representing the corresponding cell. The UE can also use this index to retrieve the CellConfigDedicated corresponding to each cell from CellConfigDedicatedToAddModList within SpCellConfig.

[0256] --◆The values ​​of CellConfigCommon, in whole or in part, can be shared by multiple cells or multiple SCells. CellGroupConfig can also contain CellConfigCommon representing a cell, but not all or part of the values ​​of CellConfigDedicated representing other cells.

[0257] --◆The values ​​of CellConfigDedicated, in whole or in part, can be shared by multiple cells or multiple SCells. CellGroupConfig can also contain CellConfigDedicated for a cell, but not all or part of the values ​​of CellConfigDedicated for cells other than those representing cells.

[0258] ◆Example 1-B2 (A combination of option B and option 2, as mentioned above) Figure 11 )

[0259] -◆ Multiple cells within a cell group (including SpCell and SCell) can also be unified as a single cell.

[0260] -◆CellGroupConfig can also omit sCellToAddModList.

[0261] -◆CellGroupConfig can also contain spCellConfig.

[0262] --◆spCellConfig / reconfigWithSync can also contain a list (e.g., CellConfigCommonToAddModList) of multiple common cell settings (e.g., CellConfigCommon) corresponding to multiple cells within a cell group. The UE can also obtain the CellConfigCommon corresponding to each cell from CellConfigCommonToAddModList.

[0263] --◆CellConfigCommon can also contain an index representing the corresponding cell. This index can be an integer greater than or equal to 0 or greater than 1.

[0264] -◆CellGroupConfig can also contain spCellConfigDedicated.

[0265] --◆spCellConfig can also contain a list (e.g., CellConfigDedicatedToAddModList) of multiple dedicated cell settings (e.g., CellConfigDedicated) corresponding to multiple cells within a cell group. The UE can also obtain the CellConfigDedicated corresponding to each cell from CellConfigDedicatedToAddModList.

[0266] --◆CellConfigDedicated can also contain an index representing the corresponding cell. This index can be an integer greater than or equal to 0 or greater than 1.

[0267] --◆The value of CellConfigCommon, or a portion thereof, can be common to multiple cells or multiple SCells. CellGroupConfig can also contain CellConfigCommon for one cell / SCell, but not all or a portion of CellConfigCommon for other cells.

[0268] --◆The values ​​of CellConfigDedicated, in whole or in part, can be common to multiple cells or multiple SCells. CellGroupConfig can also contain CellConfigDedicated for one cell / SCell, but not all or part of CellConfigDedicated for other cells.

[0269] ◆Example 1-C1 (A combination of option C and option 1) Figure 13 and the aforementioned Figure 12 )

[0270] -◆ can also represent a cell or a SpCell.

[0271] -◆CellGroupConfig can also contain SpCellConfig and sCellToAddModList.

[0272] --◆spCellConfig can also contain reconfigWithSync / spCellConfigCommon, and a list (e.g., CellConfigCommonToAddModList) of multiple common cell settings (e.g., CellConfigCommon) corresponding to multiple SCells respectively. Each CellConfigCommon can also contain an index representing the corresponding cell.

[0273] --◆UE can also obtain the spCellConfigCommon corresponding to the SpCell from reconfigWithSync in SpCellConfig.

[0274] --◆spCellConfig can also contain a list of multiple dedicated cell settings (CellConfigDedicated) that correspond to multiple cells within a cell group (e.g., CellConfigDedicatedToAddModList). Each CellConfigDedicated can also contain an index representing the corresponding cell.

[0275] --◆UE can also obtain the CellConfigDedicated corresponding to SpCell from CellConfigDedicatedToAddModList within SpCellConfig.

[0276] --◆Each sCellConfig within sCellToAddModList can also contain CellConfigCommonToAddModList / CellConfigDedicatedToAddModList / CellConfigCommon / CellConfigDedicated. CellConfigCommonToAddModList / CellConfigCommon can also contain an index representing the corresponding cell. The UE can also use this index to retrieve the CellConfigCommon corresponding to each SCell from CellConfigCommonToAddModList within SpCellConfig. CellConfigDedicatedToAddModList / CellConfigDedicated can also contain an index representing the corresponding cell. The UE can also use this index to retrieve the CellConfigDedicated corresponding to each cell from CellConfigDedicatedToAddModList within SpCellConfig.

[0277] --◆The values ​​of CellConfigCommon, in whole or in part, can be common to multiple cells or multiple SCells. CellGroupConfig can also contain CellConfigCommon representing a cell, but not all or part of the values ​​of CellConfigDedicated representing other cells.

[0278] --◆The values ​​of CellConfigDedicated, in whole or in part, can be common to multiple cells or multiple SCells. CellGroupConfig can also contain CellConfigDedicated values ​​for cells representing cells, but not all or part of the values ​​of CellConfigDedicated values ​​for cells representing other cells.

[0279] ◆Example 1-C2 (A combination of option C and option 2, as mentioned above) Figure 13 )

[0280] -◆ Multiple communities within a community group can also be unified as a single community.

[0281] -◆CellGroupConfig can also omit sCellToAddModList.

[0282] -◆CellGroupConfig can also contain SpCellConfig.

[0283] --◆spCellConfig can also contain reconfigWithSync / spCellConfigCommon, and a list (e.g., CellConfigCommonToAddModList) containing multiple common cell settings (e.g., CellConfigCommon) corresponding to multiple SCells. The UE can also obtain the spCellConfigCommon corresponding to the SpCell from SpCellConfig / reconfigWithSync. The UE can also obtain the CellConfigCommon corresponding to each SCell from CellConfigCommonToAddModList within SpCellConfig.

[0284] --◆spCellConfig can also contain a list (e.g., CellConfigDedicatedToAddModList) of multiple dedicated cell settings (e.g., CellConfigDedicated) corresponding to multiple cells within a cell group. The UE can also obtain the CellConfigDedicated corresponding to each cell from the CellConfigDedicatedToAddModList within SpCellConfig.

[0285] --◆The value of CellConfigCommon, or a portion thereof, can be common to multiple cells or multiple SCells. CellGroupConfig can also contain CellConfigCommon for one cell / SCell, but not all or a portion of CellConfigCommon for other cells.

[0286] --◆The values ​​of CellConfigDedicated, in whole or in part, can be common to multiple cells or multiple SCells. CellGroupConfig can also contain CellConfigDedicated for one cell / SCell, but not all or part of CellConfigDedicated for other cells.

[0287] ◆Example 1-D1 (A combination of option D and option 1, Figure 14 and the aforementioned Figure 12 )

[0288] -◆ can also represent a cell or a SpCell.

[0289] -◆CellGroupConfig can also contain SpCellConfig and sCellToAddModList.

[0290] --◆spCellConfig / reconfigWithSync can also contain a list (e.g., CellConfigCommonToAddModList) of multiple common cell settings (e.g., CellConfigCommon) that correspond to multiple cells within a cell group. Each CellConfigCommon can also contain an index representing the corresponding cell.

[0291] --◆UE can also obtain the CellConfigCommon corresponding to SpCell from CellConfigCommonToAddModList within SpCellConfig.

[0292] --◆spCellConfig can also contain spCellConfigDedicated.

[0293] --◆UE can also obtain the spCellConfigDedicated corresponding to the SpCell from SpCellConfig.

[0294] --◆spCellConfig can also contain a list (e.g., CellConfigDedicatedToAddModList) of multiple dedicated cell settings (e.g., CellConfigDedicated) that correspond to multiple SCells within a cell group. Each CellConfigDedicated can also contain an index representing the corresponding cell.

[0295] --◆Each sCellConfig within sCellToAddModList can also contain CellConfigCommonToAddModList / CellConfigDedicatedToAddModList / CellConfigCommon / CellConfigDedicated. CellConfigCommonToAddModList / CellConfigCommon can also contain an index representing the corresponding cell. The UE can also use this index to retrieve the CellConfigCommon corresponding to each SCell from CellConfigCommonToAddModList within SpCellConfig. CellConfigDedicatedToAddModList / CellConfigDedicated can also contain an index representing the corresponding cell. The UE can also use this index to retrieve the CellConfigDedicated corresponding to each cell from CellConfigDedicatedToAddModList within SpCellConfig.

[0296] --◆The values ​​of CellConfigCommon, in whole or in part, can be common to multiple cells or multiple SCells. CellGroupConfig can also contain CellConfigCommon representing a cell, but not all or part of the values ​​of CellConfigDedicated representing other cells.

[0297] --◆The values ​​of CellConfigDedicated, in whole or in part, can be common to multiple cells or multiple SCells. CellGroupConfig can also contain CellConfigDedicated values ​​for cells representing cells, but not all or part of the values ​​of CellConfigDedicated values ​​for cells representing other cells.

[0298] ◆Example 1-D2 (A combination of option D and option 2, as mentioned above) Figure 14)

[0299] -◆ Multiple communities within a community group can also be unified as a single community.

[0300] -◆CellGroupConfig can also omit sCellToAddModList.

[0301] -◆CellGroupConfig can also contain SpCellConfig.

[0302] --◆spCellConfig / reconfigWithSync can also contain a list (e.g., CellConfigCommonToAddModList) of multiple common cell settings (e.g., CellConfigCommon) corresponding to multiple cells within a cell group. The UE can also obtain the spCellConfigCommon corresponding to the spCell from reconfigWithSync within SpCellConfig. The UE can also obtain the sCellConfigCommon corresponding to each SCell from SCellConfigCommonToAddModList within SpCellConfig.

[0303] --◆spCellConfig can also contain spCellConfigDedicated. The UE can also obtain the spCellConfigDedicated corresponding to the SpCell from SpCellConfig.

[0304] --◆spCellConfig can also contain a list (e.g., CellConfigDedicatedToAddModList) of multiple dedicated cell settings (e.g., CellConfigDedicated) corresponding to multiple SCells within a cell group. The UE can also obtain the CellConfigDedicated corresponding to each SCell from the CellConfigDedicatedToAddModList within SpCellConfig.

[0305] --◆The value of CellConfigCommon, or a portion thereof, can be common to multiple cells or multiple SCells. CellGroupConfig can also contain CellConfigCommon for one cell / SCell, but not all or a portion of CellConfigCommon for other cells.

[0306] --◆The values ​​of CellConfigDedicated, in whole or in part, can be common to multiple cells or multiple SCells. CellGroupConfig can also contain CellConfigDedicated for one cell / SCell, but not all or part of CellConfigDedicated for other cells.

[0307] -◆When an SCell is added to a cell group, rule 1 mentioned above can also be applied.

[0308] ◆Example 1-C1-2 (A variation of the combination of option C and option 1) Figure 15 as well as Figure 16 )

[0309] -◆ can also represent a cell or a SpCell.

[0310] -◆CellGroupConfig can also contain SpCellConfig.

[0311] -◆CellGroupConfig can also contain sCellToAddModList.

[0312] -◆CellGroupConfig can also contain a list (e.g., CellConfigCommonToAddModList) of multiple common cell settings (e.g., CellConfigCommonToAddModList) that correspond to multiple SCells respectively. Each CellConfigCommon can also contain an index representing the corresponding cell.

[0313] -◆CellGroupConfig can also contain a list of multiple dedicated cell settings (CellConfigDedicated) that correspond to multiple cells within the cell group (e.g., CellConfigDedicatedToAddModList). Each CellConfigDedicated can also contain an index representing the corresponding cell.

[0314] --◆spCellConfig can also include reconfigWithSync / spCellConfigCommon.

[0315] --◆Each sCellConfig within sCellToAddModList can also contain CellConfigCommonToAddModList / CellConfigDedicatedToAddModList / CellConfigCommon / CellConfigDedicated. CellConfigCommonToAddModList / CellConfigCommon can also contain an index representing the corresponding cell. The UE can also use this index to retrieve the CellConfigCommon corresponding to each SCell from CellConfigCommonToAddModList within SpCellConfig. CellConfigDedicatedToAddModList / CellConfigDedicated can also contain an index representing the corresponding cell. The UE can also use this index to retrieve the CellConfigDedicated corresponding to each cell from CellConfigDedicatedToAddModList within SpCellConfig.

[0316] --◆UE can also obtain the spCellConfigCommon corresponding to the SpCell from SpCellConfig / reconfigWithSync.

[0317] ◆Example (a variation of the combination of option C and option 2, as mentioned above) Figure 15 )

[0318] -◆ Multiple communities within a community group can also be unified as a single community.

[0319] -◆CellGroupConfig can also contain SpCellConfig. The UE can also obtain the spCellConfigCommon corresponding to the SpCell from SpCellConfig / reconfigWithSync.

[0320] -◆CellGroupConfig can also omit sCellToAddModList.

[0321] -◆CellGroupConfig can also contain a list (e.g., CellConfigCommonToAddModList) of multiple common cell settings (e.g., CellConfigCommon) corresponding to multiple SCells respectively. The UE can also obtain the CellConfigCommon corresponding to each SCell from CellConfigCommonToAddModList.

[0322] -◆CellGroupConfig can also contain a list (e.g., CellConfigDedicatedToAddModList) of multiple dedicated cell settings (e.g., CellConfigDedicated) corresponding to multiple cells within the cell group. The UE can also obtain the CellConfigCommon corresponding to each cell from CellConfigCommonToAddModList.

[0323] ◆Example 1-D1-2 (A variation of the combination of option D and option 1) Figure 17 and the aforementioned Figure 16 )

[0324] -◆ can also represent a cell or a SpCell.

[0325] -◆CellGroupConfig can also contain sCellToAddModList.

[0326] -◆CellGroupConfig can also contain a list (e.g., CellConfigCommonToAddModList) of multiple common cell settings (e.g., CellConfigCommon) that correspond to multiple cells within the cell group. Each CellConfigCommon can also contain an index representing the corresponding cell.

[0327] -◆CellGroupConfig can also contain spCellConfigDedicated. The UE can also obtain the spCellConfigDedicated corresponding to SpCell from CellGroupConfig.

[0328] -◆CellGroupConfig can also contain a list (e.g., CellConfigDedicatedToAddModList) of multiple dedicated cell settings (e.g., CellConfigDedicated) corresponding to multiple SCells within the cell group. Each sCellConfigDedicated can also contain an index representing the corresponding cell.

[0329] --◆Each sCellConfig within sCellToAddModList can also contain CellConfigCommonToAddModList / CellConfigDedicatedToAddModList / CellConfigCommon / CellConfigDedicated. CellConfigCommonToAddModList / CellConfigCommon can also contain an index representing the corresponding cell. The UE can also use this index to retrieve the CellConfigCommon corresponding to each SCell from CellConfigCommonToAddModList within SpCellConfig. CellConfigDedicatedToAddModList / CellConfigDedicated can also contain an index representing the corresponding cell. The UE can also use this index to retrieve the CellConfigDedicated corresponding to each cell from CellConfigDedicatedToAddModList within SpCellConfig.

[0330] ◆Example 1-D2-2 (A variation of the combination of option D and option 2, as mentioned above) Figure 17 )

[0331] -◆ Multiple communities within a community group can also be unified as a single community.

[0332] -◆CellGroupConfig can also omit sCellToAddModList.

[0333] -◆CellGroupConfig can also contain a list (e.g., CellConfigCommonToAddModList) of multiple common cell settings (e.g., CellConfigCommon) corresponding to multiple cells within the cell group. The UE can also obtain the CellConfigCommon corresponding to each cell from CellConfigCommonToAddModList.

[0334] -◆CellGroupConfig can also contain spCellConfigDedicated. The UE can also obtain the spCellConfigDedicated corresponding to SpCell from CellGroupConfig.

[0335] -◆CellGroupConfig can also contain a list (e.g., CellConfigDedicatedToAddModList) of multiple dedicated cell settings (e.g., CellConfigDedicated) corresponding to multiple SCells within the cell group. The UE can also obtain the CellConfigDedicated corresponding to each SCell from CellConfigDedicatedToAddModList.

[0336] Compared to options B / C / D, the examples above include combinations with option 3, but options B / C / D can also be combined with options 1 / 2.

[0337] <<Unified Operation>>

[0338] In the existing specifications, in the individual settings of multiple cells, at least one of the following options can also be unified into a single cell setting.

[0339] ◆Option 1: This existing information element does not have a list structure. This existing information element could also be, for example, downlinkConfigCommon in spCellconfigCommon / sCellConfigCommon.

[0340] ◆Option 2: The existing information element has a list structure. This existing information element can also be, for example, the downlinkBWP-ToAddModList in spCellConfigDedicated / sCellConfigDedicated.

[0341] The unification of existing information elements in options 1 and 2 can also be based on the following methods.

[0342] ◆Option 1: (Without a list structure) Existing information elements are unified across multiple cells and defined as a single list. An append change list with the name of an existing information element + "ToAddModList" and a release list with the name of an existing information element + "ToReleaseList" can also be defined. Information element names within the list can also be represented by the name of an existing information element + its index. Each list can also be a list of existing information elements (or their indices). Lists can also be based on at least one of the following options.

[0343] -◆Option 1: Existing information elements corresponding to SpCells are configured in the initial position in the list, and existing information elements corresponding to SCells are configured in the list in ascending order of SCell index. The order / index of more than one existing information element in the list can also be based on at least one of the following options 1x / 1y.

[0344] --◆Option 1x: The index of the information element corresponding to SpCell is 0. The index of the information element corresponding to SCell can also be the index of an existing information element corresponding to SCell. For example, if downlinkConfigCommon within spCellconfigCommon and the two downlinkConfigCommon within sCellConfigCommon are unified, and the indices of the existing information elements corresponding to the two SCells are 1 and 2, then in the unified list downlinkConfigCommonToAddModList, the indices 0, 1, and 2 of downlinkConfigCommon can also be defined. Alternatively, the downlinkConfigCommon with index 0 can correspond to one SpCell (the downlinkConfigCommon within spCellConfigCommon), and the downlinkConfigCommon with indices 1 and 2 can correspond to two SCells (the downlinkConfigCommon within the two SCellConfigCommon).

[0345] --◆Option 1y:

[0346] The index of the information element corresponding to SpCell is 1. The index of the information element corresponding to SCell can also be the value obtained by adding 1 to the index of the existing information element corresponding to the SCell. For example, when the downlinkConfigCommon within spCellConfigCommon and the two downlinkConfigCommon within sCellConfigCommon are unified, and the indices of the existing information elements corresponding to the two SCells are 1 and 2, the indices 1, 2, and 3 of downlinkConfigCommon can also be defined in the unified list downlinkConfigCommonToAddModList. Alternatively, the downlinkConfigCommon with index 1 can correspond to one SpCell (the downlinkConfigCommon within spCellConfigCommon), and the downlinkConfigCommon with indices 2 and 3 can correspond to two SCells (the downlinkConfigCommon within the two SCellConfigCommon).

[0347] -◆Option 2: Existing information elements corresponding to SCells are configured in the list in ascending order of SCell index. Existing information elements corresponding to SpCells can also be configured at the end of the list. The index of an existing information element corresponding to a SpCell can be either the value obtained by adding 1 to the last index of the existing information element corresponding to the SCell, or a special value for the SpCell (e.g., 0).

[0348] -◆Option 3: More than one existing information element is configured in a list in the order it is notified via settings / instructions. Settings / instructions can also be RRC IE / MAC CE / DCI / SIB.

[0349] -◆Option 4: In the list, there are no restrictions on the order of more than one existing information element.

[0350] ◆Option 2: (With a list structure) Existing information elements are unified across multiple cells and defined as a single list. The unified list can also be based on at least one of the following options.

[0351] -◆Option 1: The unified list has a nested structure. The unified list can also be named according to the same rules as Option 1. For example, the name of the unified append change list can also be the name of the existing information element + the name of "ToAddModList" ("...ToAddModListToAddModList").

[0352] -◆Option 2: The unified list does not have a nested structure. The unified list can also be a list of more than one element within more than one existing information element (the list before unification). In the unified list, the order / index of more than one element can also be based on at least one of the following options 1a / 1b.

[0353] --◆Option 1a: The indices of elements within the unified list can also be represented by x and y. x can also be based on the rules of Option 1x / 1y of Option 1. y can also be the index corresponding to an existing information element of the corresponding cell. For example, if the existing information element downlinkBWP-ToAddModList corresponding to SpCell contains 3 BWP-Downlinks, and these 3 BWP-Downlinks have indices 1, 2, and 3 respectively, by applying Option 1a (and Option 1x), the 3 BWP-Downlinks in the unified list downlinkBWP-ToAddModList can also have indices 0-1, 0-2, and 0-3. The names of elements within the unified list can also be the element name within the existing information element + "xy", the element name within the existing information element + "xy", the element name within the existing information element + "x, y", etc.

[0354] --◆Option 1b: The index of an element within the unified list can also be represented by z. The maximum number of elements within an existing information element can also be MAX. Within the unified list, the index z of the element corresponding to SpCell can also be the index of an existing information element corresponding to SpCell. Within the unified list, the index z of the element corresponding to SCell can also use the index i corresponding to that SCell and the index j of an existing information element corresponding to that SCell, where i × MAX + j. For example, if the downlinkBWP-ToAddModList within the existing information element spCellConfigCommon corresponding to SpCell contains two BWP-Downlinks with indices 1 and 2 respectively, and the downlinkBWP-ToAddModList within the existing information element sCellConfigCommon corresponding to index 1 of SCell contains two BWP-Downlinks with indices 1 and 2 respectively, and MAX is 4, then the indices of the elements within the unified list can also be 1, 2, 5, or 6. Here, indices 1 and 2 of the elements in the unified list correspond to the two BWP-Downlinks within the downlinkBWP-ToAddModList of the existing information element spCellConfigCommon, respectively. Similarly, indices 5 and 6 of the elements in the unified list correspond to the two BWP-Downlinks within the downlinkBWP-ToAddModList of the existing information element sCellConfigCommon at index 1 of SCell. The names of the elements in the unified list can also be the element names of existing information elements plus "z", etc.

[0355] -◆Option 3: One or more existing information elements are configured in a unified list according to the order / index notified by the settings / instructions. The settings / instructions can also be RRC IE / MAC CE / DCI / SIB. The name of the unified list and at least one of the names of the elements within that list can also be based on Option 1 or 2.

[0356] According to implementation method B1, by unifying existing information elements in multiple settings corresponding to multiple cells, the processing load of the gNB / UE can be reduced. Furthermore, when the values ​​of existing information elements are common across multiple cells, by unifying existing information elements across multiple cells, signaling overhead can be reduced.

[0357] <Implementation Method B2>

[0358] Implementation method B2 involves changes to the structure of settings information within the cell.

[0359] A combination of implementation method B1 and implementation method B2 can also be used. Either one of the following implementation methods B2-1 and B2-2, or both, can be used.

[0360] <<Implementation Method B2-1>>

[0361] Alternatively, within a single cell setting, existing information elements (with nested structures) that are bundled with multiple existing information elements are deleted, and the nested structure is reduced.

[0362] By unnesting existing information elements, their functionality can be disabled or disabled. Existing information elements with nested structures can be at least one of BWP, pdcch-config, pdcch-ConfigCommon, pdsch-Config, or pdsch-ConfigCommon.

[0363] For example, the method for unnesting settings associated with BWP (BWP-DownlinkCommon / BWP-DownlinkDedicated) can also have the following three phases.

[0364] ◆Phase 1: You can also unhide the nested structure of the existing information element genericParameters (BWP structure).

[0365] -◆At least one of the locationAndBandwidth, subcarrierSpacing, and cyclicPrefix contained in the existing information element genericParameters can be configured / deployed either outside of or in parallel with genericParameters, or removed from genericParameters. This process can be applied to all existing information elements containing genericParameters, or to a subset of existing information elements containing genericParameters. Existing information elements containing genericParameters include BWP-DownlinkCommon, BWP-Common within BWP-Downlink, etc. This process can affect DownlinkConfigCommonSIB, DownlinkConfigCommon, downlinkBWP-ToAddModList within ServingCellConfig, etc.

[0366] ◆Phase 2: Alternatively, the nested structure of existing information elements BWP-DownlinkCommon / BWP-DownlinkDedicated can be unnested. This phase can also be based on at least one of the following options.

[0367] Option 1: Existing information elements such as pdcch-Config, pdcch-ConfigCommon, pdsch-Config, pdsch-ConfigCommon, genericParameters, bwp-id, sps-Config, and radioLinkMonitoringConfig contained in BWP-DownlinkCommon / BWP-DownlinkDedicated can be configured / deployed either outside of or in parallel with BWP-DownlinkCommon / BWP-DownlinkDedicated, or removed from BWP-DownlinkCommon / BWP-DownlinkDedicated. In Phase 1, when a nested structure of genericParameters is deployed, existing information elements deployed from genericParameters (at least one of locationAndBandwidth, subcarrierSpacing, and cyclicPrefix) can also be configured / deployed outside of or in parallel with DownlinkCommon / BWP-DownlinkDedicated.

[0368] -◆Option 2: Alternatively, the nested structure of at least one of the existing information element spCellConfigDedicated and initialDownlinkBWP within the existing information element sCellConfigDedicated can be maintained.

[0369] ◆Stage 3: Alternatively, you can reduce the complexity of the settings by deleting all or part of the settings related to BWP. This will also disable BWP's functionality.

[0370] -◆When applying option 1 in phase 2, existing information elements within `initialDownlinkBWP` and `downlinkBWP-ToAddModList` within `downlinkBWP-ToAddModList` are repeatedly deployed. Deployed information elements may inherit values ​​from existing information elements within `initialDownlinkBWP`, and existing information elements within `bwp-Dedicated` are deleted.

[0371] -◆When applying option 2 in phase 2, existing information elements within the initialDownlinkBWP are maintained within the BWP-DownilnkDedicated section of spCellConfigDedicated / sCellConfigDedicated. The names of information elements based on existing information elements within the initialDownlinkBWP can also represent the names of the bands used for initial access. Deployed information elements can also inherit the values ​​of existing information elements within the BWP-Dedicated section of downlinkBWP within downlinkBWP-ToAddModList.

[0372] The above-mentioned method for changing the structure of settings related to BWP-DownlinkCommon / BWP-DownlinkDedicated can also be applied to the structure of settings related to BWP-UplinkCommon / BWP-UplinkDedicated, and can also be applied to the structure of settings related to uplinkConfig / supplementaryUplink within ServingCellConfig / ServingCellConfigSIB.

[0373] A BWP can also be a virtual BWP containing one or more BWPs. In this disclosure, BWPs and virtual BWPs can be rewritten interchangeably. In this disclosure, the initial DL BWP, initial DL virtual BWP, initial Downlink BWP, and initial Downlink Virtual BWP can also be rewritten interchangeably. In this disclosure, the initial UL BWP, initial UL virtual BWP, initial Uplink BWP, and initial Uplink Virtual BWP can also be rewritten interchangeably.

[0374] Implementation method B2-1 may also be based on at least one of the following examples.

[0375] ◆Example 2-10 (Existing community settings, Figure 18 )

[0376] The `spCellConfigCommon / sCellConfigCommon` (ServingCellConfigCommon structure) within `CellGroupConfig` contains the following:

[0377] -{

[0378] --downlinkConfigCommon (DownlinkConfigCommon structure), which contains the following:

[0379] --{

[0380] ---frequencyInfoDL

[0381] ---initialDownlinkBWP (BWP-DownlinkCommon structure), which contains the following:

[0382] ---{

[0383] ----pdcch-ConfigCommon

[0384] --- pdsch-ConfigCommon (BWP structure), which contains the following:

[0385] ----genericParameters{

[0386] -----locationAndBandwidth

[0387] ----SubcarrierSpacing

[0388] -----cyclicPrefix

[0389] ---

[0390] ---}

[0391] --}

[0392] -}

[0393] The servingCellConfigCommon (servingCellConfigCommonSIB structure) within SIB1 contains the following:

[0394] -{

[0395] --downlinkConfigCommon (DownlinkConfigCommonSIB structure), which contains the following:

[0396] --{

[0397] ---frequencyInfoDL

[0398] ---initialDownlinkBWP (BWP-DownlinkCommon structure), which contains the following:

[0399] ---{

[0400] ----pdcch-ConfigCommon

[0401] ----pdsch-ConfigCommon

[0402] ---genericParameters (BWP structure), which contains the following:

[0403] ---{

[0404] -----locationAndBandwidth

[0405] ----SubcarrierSpacing

[0406] -----cyclicPrefix

[0407] ---

[0408] ---}

[0409] --}

[0410] -}

[0411] The `spCellConfigDedicated / sCellConfigDedicated` (ServingCellConfig structure) within `CellGroupConfig` contains the following:

[0412] -{

[0413] --initialDownlinkBWP (BWP-DownlinkDedicated structure), which contains the following:

[0414] --{

[0415] --- pdcch-Config

[0416] --- pdsch-Config

[0417] ---sps-Config

[0418] ---radioLinkMonitoringConfig

[0419] --}

[0420] --firstActiveDownlinkBWP-Id

[0421] --bwp-InactivityTimer

[0422] --defaultDownlinkBWP-Id

[0423] --downlinkBWP-ToAddModList, which contains the following:

[0424] --{

[0425] --- downlinkBWP (BWP-Downlink structure), which contains the following:

[0426] ---{

[0427] --bwp-id=1

[0428] --- bwp-Common (BWP-DownlinkCommon structure), which contains the following:

[0429] ---{

[0430] -----pdcch-ConfigCommon

[0431] ----pdsch-ConfigCommon

[0432] ---genericParameters (BWP structure), which contains the following:

[0433] ---{

[0434] -----locationAndBandwidth

[0435] ------subcarrierSpacing

[0436] ------cyclicPrefix

[0437] ---

[0438] ---

[0439] --- bwp-Dedicated (BWP-Downlink structure), which contains the following:

[0440] ---{

[0441] --pdcch-Config

[0442] --pdsch-Config

[0443] --sps-Config

[0444] ----radioLinkMonitoringConfig

[0445] ---

[0446] ---}

[0447] --}

[0448] -}

[0449] ◆Example 2-11 (Phase 1, Figure 19 )

[0450] The locationAndBandwidth, SubcarrierSpacing, and cyclicPrefix contained in the existing information element BWP structure are deployed / configured outside the BWP structure.

[0451] ◆Example 2-12-1 (Option 1 in Stage 2) Figure 20 )

[0452] The existing information elements pdcch-ConfigCommon, pdsch-ConfigCommon, locationAndBandwidth, SubcarrierSpacing, cyclicPrefix, pdcch-Config, pdsch-Config, sps-Config, radioLinkMonitoringConfig, and bwp-id contained in the BWP-DownlinkCommon / BWP-DownlinkDedicated structure are deployed / configured outside the BWP-DownlinkCommon / BWP-DownlinkDedicated structure.

[0453] ◆Example 2-12-2 (Option 2 in Stage 2) Figure 21 )

[0454] The initialDownlinkBWP (BWP-DownlinkDedicated structure) within the existing information elements spCellConfigDedicated / sCellConfigDedicated (ServingCellConfig structure) is maintained. The pdcch-ConfigCommon, pdsch-ConfigCommon, locationAndBandwidth, SubcarrierSpacing, cyclicPrefix, pdcch-Config, pdsch-Config, sps-Config, radioLinkMonitoringConfig, and bwp-id contained in the existing information element BWP-DownlinkCommon structure are deployed / configured outside the BWP-DownlinkCommon / BWP-DownlinkDedicated structure.

[0455] ◆Example 2-13-1 (The third stage following option 1 in stage 2, Figure 22 )

[0456] The existing information elements pdcch-ConfigCommon, pdsch-ConfigCommon, locationAndBandwidth, SubcarrierSpacing, cyclicPrefix, pdcch-Config, pdsch-Config, sps-Config, and radioLinkMonitoringConfig contained in the existing BWP-Downlink structure have been deployed / configured outside the BWP-Downlink structure. The existing information elements bwp-id, pdcch-Config, pdsch-Config, sps-Config, and radioLinkMonitoringConfig contained in the existing BWP-Downlink structure have been deleted.

[0457] ◆Example 2-13-1 (The third stage after option 2 in stage 2, Figure 23 )

[0458] The existing information elements pdcch-ConfigCommon, pdsch-ConfigCommon, locationAndBandwidth, SubcarrierSpacing, cyclicPrefix, pdcch-Config, pdsch-Config, sps-Config, and radioLinkMonitoringConfig contained in the existing BWP-Downlink structure have been deployed / configured outside the BWP-Downlink structure. The existing information element bwp-id contained in the existing BWP-Downlink structure has been deleted.

[0459] <<Implementation Method B2-2>>

[0460] Multiple identical existing information elements within a single community setting can also be unified.

[0461] A unified approach for multiple existing information elements can also be based on the following algorithms (Projects 1 and 2).

[0462] ◆Project 1: The existing list of existing information elements (structures) X within the settings of the cell is being monitored.

[0463] ◆Project 2: If the setting includes the list XToAddModList, XToAddModList is deleted. Within this setting, for each existing information element Y within an existing information element X, a list YToAddModList is defined containing one or more existing information elements Y corresponding to one or more existing information elements X in the existing list. The order / index / name of the information elements Y can also be based on implementation method B2-1.

[0464] The nested structure within the setting can also be reduced by appropriately repeating the algorithm.

[0465] ◆Example 2-2B-12 (In options B and 2 of implementation B1, the state of option 1 in the second stage of implementation B2-1 is applied.) Figure 24 )

[0466] In Example 1-B2, the pdcch-ConfigCommon, pdsch-ConfigCommon, locationAndBandwidth, SubcarrierSpacing, cyclicPrefix, pdcch-Config, pdsch-Config, sps-Config, radioLinkMonitoringConfig, and bwp-id contained in the BWP-DownlinkCommon / BWP-DownlinkDedicated structure can also be deployed / configured outside the BWP-DownlinkCommon / BWP-DownlinkDedicated structure.

[0467] ◆Example 2-2B-12-1 (In options B and 2 of implementation B1, option 1 of the second stage of implementation B2-1 and the state of implementation B2-2 are applied once.) Figure 25 )

[0468] -◆In reconfigWithSync, multiple downlinkConfigCommon within CellConfigCommon in CellConfigCommonToAddModList are changed to multiple downlinkConfigCommon within downlinkConfigCommonToAddModList of CellConfigCommon.

[0469] -◆ Within SpCellConfig, multiple downlinkBWP-ToAddModLists within CellConfigDedicated are changed to multiple downlinkBWP-ToAddModLists within CellConfigDedicatedToAddModList. Within SpCellConfig, multiple uplinkConfig / supplementaryUplinks within CellConfigDedicated are changed to multiple uplinkConfig / supplementaryUplinks within CellConfigDedicatedUplinkConfigToAddModList / supplementaryUplinkToAddModList. Each information element (initialDownlinkBWP, firstActiveDownlinkBWP-Id, bwp-InactivityTimer, defaultDownlinkBWP-Id) within CellConfigDedicated is changed to a list of information elements (...ToAddModList) within CellConfigDedicated.

[0470] ◆Example 2-2B-12-2 (In options B and 2 of implementation B1, the state of option 1 of the second stage of implementation B2-1 and the state of implementation B2-2 are applied twice.) Figure 26 )

[0471] -◆In CellConfigCommon, multiple downlinkConfigCommon instances in downlinkConfigCommonToAddModList are changed to multiple initialDownlinkBWP instances in initialDownlinkBWPToAddModList within downlinkConfigCommon.

[0472] -◆ Within CellConfigDedicated, multiple downlinkBWP-ToAddModLists within initialDownlinkBWPToAddModList / downlinkBWP-ToAddModListToAddModList are changed to multiple BWP-DLs within downlinkBWP-ToAddModList. Within CellConfigDedicated, multiple uplinkConfig / supplementaryUplinks within uplinkConfigToAddModList / supplementaryUplinkToAddModList are changed to uplinkBWP-ToAddModListToAddModList within uplinkConfig / supplementaryUplink. Within CellConfigDedicated, the information elements (initialUplinkBWP, firstActiveUplinkBWP-Id, bwp-InactivityTimer) within multiple uplinkConfig / supplementaryUplink elements in uplinkConfigToAddModList / supplementaryUplinkToAddModList are changed to a list of information elements (...ToAddModList) within uplinkConfig / supplementaryUplink.

[0473] ◆Example 2-2B-12-2 (In options B and 2 of implementation B1, option 1 of the second stage of implementation B2-1 and the state of implementation B2-2 are applied three times.) Figure 27 )

[0474] -◆In downlinkConfigCommon, the information elements (frequencyInfoDL, pdcch-ConfigCommon, pdsch-ConfigCommon, locationAndBandwidth, subcarrierSpacing, cyclicPrefix) in multiple initialDownlinkBWPs within initialDownlinkBWPToAddModList are changed to a list of information elements within initialDownlinkBWPs (...ToAddModList).

[0475] -◆ Within CellConfigDedicated, the information elements (bwp-id, pdcch-ConfigCommon, pdsch-ConfigCommon, locationAndBandwidth, subcarrierSpacing, cyclicPrefix, pdcch-Config, pdsch-Config, sps-Config, radioLinkMonitoringConfig) within multiple BWP-DLs in downlinkBWP-ToAddModList are changed to a list (...ToAddModList) of information elements within BWP-Downlink in downlinkBWP. Within uplinkConfig / supplementaryUplink, the lists (initialUplinkBWPToAddModList, uplinkBWP-ToAddModListToAddModList) are changed to information elements (initialUplinkBWP, uplinkBWP-ToAddModList).

[0476] ◆Example 2-2B-12-2 (In options B and 2 of implementation B1, the state of option 1 of the second stage of implementation B2-1 and the state of implementation B2-2 are applied four times.) Figure 28 )

[0477] -◆In the initialDownlinkBWP within downlinkConfigCommon, each list (pdcch-ConfigCommonToAddModList, pdsch-ConfigCommonToAddModList) is changed to an information element (pdcch-ConfigCommon, pdsch-ConfigCommon).

[0478] According to implementation method B2, in a configuration corresponding to one cell, the processing load of the gNB / UE can be reduced by deploying / unifying existing information elements. Furthermore, in a configuration corresponding to one cell, when the values ​​of multiple existing information elements are common, signaling overhead can be reduced by unifying these multiple existing information elements.

[0479] <Supplement>

[0480] <<Information Notification to UE>>

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

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

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

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

[0485] <<Notifications from UE>>

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

[0487] In cases where the aforementioned notification is made via a MAC CE, the MAC CE can also be identified by including a new LCID, which is not specified in the existing standard, in the MAC subheader.

[0488] If the above notification is made through UCI, the above notification may also be sent using PUCCH or PUSCH.

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

[0490] <<Application of Each Implementation Method>>

[0491] In the UE / BS, a specific processing / operation / control / conception / information for at least one of the above embodiments may also be applied (or used) if any one or more of the following conditions are met:

[0492] • High-level parameters are set to represent the specific processing / operation / control / conception / information mentioned above;

[0493] The specific processing / operation / control / concept / information mentioned above is determined based on the associated high-level parameters;

[0494] The aforementioned specific processing / operation / control / conception / information is specified / activated / triggered via MAC CE / DCI / UCI / resource / channel / RS;

[0495] • Report or support indicating the specific UE capability (or associated with) the aforementioned specific processing / operation / control / conception / information;

[0496] The application of the aforementioned specific processing / operation / control / conception / information can also be judged based on specific conditions.

[0497] The specific UE capability mentioned above can also represent at least one of the following:

[0498] • Supports the specific processing / operation / control / concept / information mentioned above;

[0499] • The capabilities of each implementation method;

[0500] • The capabilities of each option in each implementation, or the capabilities of a combination of multiple options in each implementation;

[0501] • The capabilities of each option in each implementation, or the capabilities of a combination of multiple options in each implementation;

[0502] • The UE supports DWS [within the corresponding CC / serving cell];

[0503] • The UE supports enhanced PHR [within the corresponding CC / serving cell].

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

[0505] Furthermore, the aforementioned specific UE capabilities can be either the ability to be applied across all duplex modes (commonly regardless of the duplex mode) or the capability for each duplex mode (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).

[0506] If the above conditions are not met, the UE / BS may also follow the operations specified in the existing 3GPP version.

[0507] (Postscript)

[0508] With respect to one embodiment of this disclosure (Embodiment B1), the following invention is noted.

[0509] [Postscript 1]

[0510] A terminal having:

[0511] The receiving unit receives cell group settings for a cell group, wherein the cell group includes special cells and one or more secondary cells; and

[0512] The control unit, based on the cell group settings, controls the communication using the cell group.

[0513] The cell setting for one cell within the cell group includes one or more information elements for multiple cells within the cell group.

[0514] [Postscript 2]

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

[0516] The cell group includes multiple sub-cells, and the cell setting for one cell includes one or more information elements for the multiple sub-cells.

[0517] [Postscript 3]

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

[0519] The cell settings for the special cell include one or more information elements for the special cell and the one or more sub-cells, wherein the one or more information elements are at least one of settings common to multiple terminals and settings specific to the terminal.

[0520] [Postscript 4]

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

[0522] The first cell setting for the special cell includes one or more information elements for the special cell and the one or more sub-cells, and the second cell setting for the one or more sub-cells includes reference information for the first cell setting.

[0523] (Postscript)

[0524] With respect to one embodiment of this disclosure (Embodiment B2), the following invention is noted.

[0525] [Postscript 1]

[0526] A terminal having:

[0527] The receiving unit receives the cell settings for the cell; and

[0528] The control unit, based on the cell settings, controls the communications using the cell.

[0529] The cell setting includes one or more information elements within the one or more structures, but does not include one or more structures within the setting of a specific wireless communication system.

[0530] [Postscript 2]

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

[0532] The cell setting includes one or more information elements in one of the more than one structures.

[0533] [Postscript 3]

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

[0535] The one or more structures represent the setting of the bandwidth portion (BWP).

[0536] [Postscript 4]

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

[0538] The one or more structures represent the settings of the bandwidth portion (BWP), and the cell settings represent the settings of the initial downlink BWP.

[0539] (Wireless communication system)

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

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

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

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

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

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

[0546] Alternatively, the wireless communication system 1 can also utilize Multiple Input Multiple Output (MIMO). For example, a cell can be formed by one antenna / base station 10 or by multiple antennas / base stations 10. A [virtual] cell (e.g., also referred to as a super cell) can also be composed of multiple [virtual] cells (e.g., also referred to as sub-cells). A super cell can also correspond to a cell with a fixed physical range, and a sub-cell can also correspond to a cell with a semi-static / dynamically varying physical range. In this case, the wireless communication system 1 can also be referred to as a cellless system.

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

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

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

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

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

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

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

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

[0555] Wireless access methods can also be referred to as waveforms. In addition, in wireless communication system 1, other wireless access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) can also be applied in the wireless access methods of UL and DL.

[0556] As a downlink channel, the wireless communication system 1 can also use downlink shared channels (Physical Downlink Shared Channel (PDSCH)), broadcast channels (Physical Broadcast Channel (PBCH)), downlink control channels (Physical Downlink Control Channel (PDCCH)) and so on, which are shared among the user terminals 20.

[0557] In addition, as uplink channels, the wireless communication system 1 may also use uplink shared channels (Physical Uplink Shared Channel (PUSCH)), uplink control channels (Physical Uplink Control Channel (PUCCH)), random access channels (Physical Random Access Channel (PRACH)) and so on, which are shared by each user terminal 20.

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

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

[0560] Additionally, the DCI for scheduling PDSCH can also be called DL allocation, DL DCI, etc., and the DCI for scheduling PUSCH can also be called UL authorization, UL DCI, etc. Furthermore, PDSCH can be rewritten as DL data, and PUSCH can be rewritten as UL data.

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

[0562] A search space can also correspond to a PDCCH candidate that matches one or more aggregation levels. One or more search spaces can also be referred to as a search space set. In addition, the terms "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting" etc. disclosed herein can be rewritten interchangeably.

[0563] Uplink control information (UCI) can also be transmitted via PUCCH, including at least one of the following: Channel State Information (CSI), delivery confirmation information (e.g., also known as Hybrid Automatic Repeat reQuest ACK knowledgement (HARQ-ACK), ACK / NACK, etc.), and Scheduling Request (SR). Random access preambles used for establishing a connection with the cell can also be transmitted via PRACH.

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

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

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

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

[0568] (Base station)

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

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

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

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

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

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

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

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

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

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

[0579] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform transmission processing such as channel coding (which may also include error correction coding), modulation, mapping, filter processing, Discrete Fourier Transform (DFT) processing (as needed), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output the baseband signal.

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

[0581] On the other hand, the transmitting and receiving unit 120 (RF unit 122) can also amplify, filter, demodulate baseband signals, etc., for signals in the wireless frequency band that are received by the transmitting and receiving antenna 130.

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

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

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

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

[0586] Additionally, base station 10 can be divided into three elements: Radio Unit (RU), Distributed Unit (DU), and Central Unit (CU). For example, the RU can implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level physical layer functions (precoding, IFFT, FFT, etc.). The DU can implement higher-level physical layer functions (from coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU can implement PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

[0587] In this disclosure, base station 10 may include a single device that implements all the functions of RU, DU, and CU, or it may include multiple devices that implement partial functions of RU, DU, and CU respectively and are interconnected. In this disclosure, base station 10 and RU / DU / CU can also be rewritten.

[0588] The transmitting / receiving unit 120 can also transmit cell group settings for a cell group, which includes a special cell and one or more sub-cells. The control unit 110 can also control communication using the cell group based on the cell group settings. The cell settings for one cell within the cell group settings can also include one or more information elements for multiple cells within the cell group.

[0589] The transmitting / receiving unit 120 can also transmit cell settings for a specific cell. The control unit 110 can also control communication using the cell based on the cell settings. The cell settings can also include one or more information elements within the one or more structures, but not one or more structures within the settings of a specific wireless communication system.

[0590] (User terminal)

[0591] Figure 31 This diagram illustrates an example of the structure of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Alternatively, more than one of each of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be included.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0609] The transmitting / receiving unit 220 can also receive cell group settings for a cell group, which includes a special cell and one or more sub-cells. The control unit 210 can also control communication using the cell group based on the cell group settings. The cell settings for one cell within the cell group settings can also include one or more information elements for multiple cells within the cell group.

[0610] Alternatively, the cell group may include multiple sub-cells, and a cell setting for a cell may include one or more information elements for the multiple sub-cells.

[0611] The cell settings for the special cell include one or more information elements for the special cell and the one or more sub-cells. The one or more information elements may be at least one of settings common to multiple terminals and settings specific to a terminal.

[0612] Alternatively, the first cell for the special cell may be configured to include one or more information elements for the special cell and the one or more sub-cells, and the second cell for the one or more sub-cells may be configured to include information for reference in the configuration of the first cell.

[0613] The transmitting / receiving unit 220 can also receive cell settings for a specific cell. The control unit 210 can also control communication using the cell based on the cell settings. The cell settings can include one or more information elements within the one or more structures, but not one or more structures within the settings of a specific wireless communication system.

[0614] The cell setting may also include one or more information elements within one or more of the structures.

[0615] The one or more structures can also represent the setting of the bandwidth portion (BWP).

[0616] Alternatively, the one or more structures may represent the settings of the bandwidth portion (BWP), and the cell settings may include the settings of the initial downlink BWP.

[0617] (Hardware structure)

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

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

[0620] For example, in one embodiment of this disclosure, the base station, user terminal, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 32 This diagram illustrates an example of the hardware structure of a base station and a user terminal according to one embodiment. The base station 10 and the user terminal 20 described above can also be physically configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

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

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

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

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

[0625] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and performs various processes accordingly. As a program, a program that causes the computer to perform at least a portion of the operations described in the above embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operated in the processor 1001; similar implementations can be made for other functional blocks.

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

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

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

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

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

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

[0632] In addition, the devices included in the core network 30 (e.g., network nodes that provide NF) can also be implemented through the functional block / hardware structure described above.

[0633] (Variation example)

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

[0635] A radio frame can also be composed of one or more periods (frames) in the time domain. Each of these periods (frames) that constitutes a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

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

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

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

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

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

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

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

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

[0644] A TTI with a duration of 1 ms can also be referred to as a normal TTI (TTI in 3GPP Rel.8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI can also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub-time slot, a time slot, etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0659] Regarding any information (e.g., variables, constants, parameters) recorded in this disclosure, even if not specifically stated in the above embodiments, information indicating the value of such arbitrary information (or information associated with such arbitrary information) may be notified from any first device (e.g., UE / base station) to any second device (e.g., base station / UE).

[0660] The notification of information is not limited to the methods / implementations described in this disclosure, and may also be carried out by other methods. For example, the notification of information in this disclosure may also be implemented by physical layer signaling (e.g., downlink control information (DCI), uplink control information (UCI), etc.), higher layer signaling (e.g., radio resource control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB) etc.), medium access control (MAC) signaling), other signals, or combinations thereof.

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

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

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

[0664] Whether it is called software, firmware, middleware, microcode, hardware description language, or any other name, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, program, subprogram, software module, application, software application, software package, routine, subroutine, object, executable file, execution thread, process, function, etc.

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

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

[0667] In this disclosure, the terms “precoding”, “precoder”, “weight (precoding weight)”, “quasi-co-location (QCL)”, “transmission configuration indication state (TCI state)”, “spatial relation”, “spatial domain filter”, “transmit power”, “phase rotation”, “antenna port”, “layer”, “number of layers”, “rank”, “resource”, “resource set”, “beam”, “beamwidth”, “beam angle”, “antenna”, “antenna element”, “panel”, “UE panel”, “transmitting entity”, and “receiving entity” are used interchangeably.

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

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

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

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

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

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

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

[0675] In this disclosure, the terms "Base Station (BS)", "Wireless Base Station", "Fixed Station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access Point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Panel", "Cell", "Sector", "Cell Group", "Carrier", and "Component Carrier" are used interchangeably. There are also instances where terms such as macro cell, small cell, femtocell, and picocell are used to refer to base stations.

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

[0677] In this disclosure, the information sent by the base station to the terminal and the control / operation instructed by the base station to the terminal based on that information can also be rewritten.

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

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

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

[0681] The term "mobile body" refers to a movable object whose speed is arbitrary, including situations where the body is stationary. Examples of such mobile bodies include vehicles, transport vehicles, automobiles, autonomous two-wheelers, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, trailers, rickshaws, ships (bottles and other watercraft), airplanes, rockets, artificial satellites, drones, multi-rotor aircraft, quadcopters, balloons, and objects carried on them, but are not limited to these. Furthermore, the mobile body can also be a mobile body that moves autonomously based on operational commands.

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

[0683] Figure 33This figure illustrates an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a gear shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a speed sensor 51, 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 gear shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0684] The drive unit 41 is comprised of at least one of an engine, a motor, or a combination of an engine and a motor. The steering unit 42 is configured to include at least a steering wheel (also called a handlebar) and to steer at least one of the front wheel 46 and the rear wheel 47 based on the operation of the steering wheel operated by the user.

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

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

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

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

[0689] The driver assistance system unit 64 comprises various devices used to provide functions for preventing accidents or reducing the driver's workload, such as millimeter-wave radar, light detection and ranging (LiDAR), cameras, positioning devices (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyroscope systems (e.g., Inertial Measurement Unit (IMU)) and Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, and one or more ECUs that control these devices. Furthermore, the driver assistance system unit 64 sends and receives various information via the communication module 60 to realize driver assistance or autonomous driving functions.

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

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

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

[0693] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) sent from external devices and displays it to the information service unit 59 provided by the vehicle. The information service unit 59 can also be referred to as an information output unit (e.g., outputting information to devices such as displays and speakers based on the PDSCH received by the communication module 60 (or the data / information decoded from the PDSCH)).

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

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

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

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

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

[0699] The various methods / implementations described in this disclosure can also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Futuregeneration radio access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE This includes 802.11 (Wi-Fi, a registered trademark), IEEE 802.16 (WiMAX, a registered trademark), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, systems utilizing other appropriate wireless communication methods, and next-generation systems extended, modified, established, or defined based on them. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A, combinations with 5G, etc.) for application.

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

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

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

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

[0704] Furthermore, "judgment (decision)" can also refer to situations where resolving, selecting, choosing, establishing, or comparing are considered as making a "judgment (decision)". In other words, "judgment (decision)" can also refer to certain actions as situations where a "judgment (decision)" is made. In this disclosure, "judgment (decision)" and the aforementioned operations can also be rewritten interchangeably.

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

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

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

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

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

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

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

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

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

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

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

[0716] In this disclosure, timing, moment, time, time instance, arbitrary time unit (e.g., time slot, sub-time slot, symbol, subframe), period, occasion, resource, etc., can also be rewritten to each other.

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

Claims

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

2. The terminal as described in claim 1, wherein, The cell group includes multiple sub-cells, and the cell setting for one cell includes one or more information elements for the multiple sub-cells.

3. The terminal as described in claim 1, wherein, The cell settings for the special cell include one or more information elements for the special cell and the one or more sub-cells, wherein the one or more information elements are at least one of settings common to multiple terminals and settings specific to the terminal.

4. The terminal as described in claim 1, wherein, The first cell setting for the special cell includes one or more information elements for the special cell and the one or more sub-cells, and the second cell setting for the one or more sub-cells includes reference information for the first cell setting.

5. A wireless communication method for a terminal, comprising: The steps for receiving cell group settings for a cell group, wherein the cell group includes special cells and one or more sub-cells; and The steps for controlling communication using the cell group based on the cell group settings. The cell setting for one cell within the cell group includes one or more information elements for multiple cells within the cell group.

6. A base station, comprising: The transmitting unit transmits cell group settings for a cell group, wherein the cell group includes special cells and one or more secondary cells; and The control unit, based on the cell group settings, controls the communication using the cell group. The cell setting for one cell within the cell group includes one or more information elements for multiple cells within the cell group.

Images