Terminal, wireless communication method, base station and system

Abstract

A terminal according to one aspect of the present disclosure is characterized by having: a transmission unit that transmits, between a serving cell and a non-serving cell, capability information indicating that the transmission unit supports updating at least a portion of radio resource control (RRC) parameters; and a control unit that estimates that cell radio network temporary identifiers (C-RNTI) are different between the serving cell and non-serving cell when the capability information is transmitted. C-RNTI can be appropriately selected according to one aspect of the present disclosure.

Description

Terminal, wireless communication method and base station

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

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

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

[0004] In existing LTE systems (e.g., 3GPP Rel. 8-14), a user terminal (User Equipment (UE)) transmits uplink control information (Uplink Control Information (UCI)) using at least one of an UL data channel (e.g., a Physical Uplink Shared Channel (PUSCH)) and an UL control channel (e.g., a Physical Uplink Control Channel (PUCCH)).

[0005] 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

[0006] In future wireless communication systems (e.g., NR), layer 1 / layer 2 (L1 / L2) inter-cell mobility is being considered to facilitate more efficient (realizing lower delay and overhead) DL / UL beam management.

[0007] In L1 / L2 inter-cell mobility, the serving cell can be changed using functions such as beam control without reconfiguring Radio Resource Control (RRC). In other words, transmission and reception with a non-serving cell are possible without handover. Since handover requires RRC reconnection and creates a period during which data communication is unavailable, L1 / L2 inter-cell mobility, which does not require handover, is preferable.

[0008] However, there is a possibility that the Cell Radio Network Temporary Identifier (C-RNTI) used in the serving cell cannot be used as is for transmission and reception with a non-serving cell. For example, this is because the C-RNTI used in the serving cell may already be used for another user terminal (User Equipment (UE)) in the non-serving cell. If the same C-RNTI is used between UEs in the same cell, problems may arise, such as the downlink control information addressed to another UE being mistakenly read.

[0009] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately select a C-RNTI.

[0010] A terminal according to one aspect of the present disclosure is characterized by having: a transmitter that transmits capability information indicating support for updating at least some Radio Resource Control (RRC) parameters between a serving cell and a non-serving cell; and a controller that, when the capability information is transmitted, assumes different Cell Radio Network Temporary Identifiers (C-RNTIs) for the serving cell and the non-serving cell.

[0011] According to one aspect of the present disclosure, the C-RNTI can be appropriately selected.

[0012] 1A-1D are diagrams illustrating an example of a multi-TRP scenario. FIGS. 2A and 2B are diagrams illustrating an example of intra-cell mobility. FIG. 3 is a diagram illustrating an example of a joint common TCI indication for UL / DL. FIG. 4 is a diagram illustrating an example of a separate common TCI indication for UL / DL. FIG. 5 is a diagram illustrating an example of TCI state switching. FIG. 6 is a diagram illustrating an example of a C-RNTI assumption in Aspect 1-1. FIG. 7 is a diagram illustrating an example of a C-RNTI assumption in Aspect 1-2. FIG. 8 is a diagram illustrating an example of a TCI framework for Option 1 of Aspect 2-1. FIG. 9 is a diagram illustrating an example of a TCI framework for Option 2 of Aspects 2-1 and 2-2. FIG. 10 is a diagram illustrating an example of a TCI framework for Option 1 of Aspect 2-2. FIG. 11 is a diagram illustrating an example of a TCI framework for Option 2 of Aspect 2-3. FIG. 12 is a diagram illustrating an example of association between non-serving cell indices and C-RNTIs. FIG. 13 is a diagram showing an example of the relationship between actual non-serving cell indexes by RRC and various parameters. FIG. 14 is a diagram showing an example of re-indexing of non-serving cell IDs. FIG. 15 is a diagram showing an example of inter-cell movement of a UE. FIG. 16 is a diagram showing an example of RRC parameters of a serving cell and a non-serving cell. FIG. 17 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 18 is a diagram showing an example of a configuration of a base station according to an embodiment. FIG. 19 is a diagram showing an example of a configuration of a user terminal according to an embodiment. FIG. 20 is a diagram showing an example of hardware configurations of a base station and a user terminal according to an embodiment.

[0013] (TCI, spatial relationship, QCL) In NR, it is considered to control the reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, and encoding) in a UE of at least one of a signal and a channel (referred to as a signal / channel) based on a transmission configuration indication state (TCI state).

[0014] The TCI state may represent that which is applied to a downlink signal / channel, and the equivalent of the TCI state that is applied to an uplink signal / channel may be expressed as a spatial relation.

[0015] The TCI state is information about the Quasi-Co-Location (QCL) of signals / channels, and may also be called spatial reception parameters, spatial relation information, etc. The TCI state may be configured in the UE for each channel or signal.

[0016] The QCL is an index indicating the statistical properties of signals / channels. For example, if a signal / channel has a QCL relationship with another signal / channel, it may mean that it can be assumed that at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, and a spatial parameter (e.g., a spatial Rx parameter) is the same between these different signals / channels (i.e., the signals / channels have a QCL with respect to at least one of these).

[0017] The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be identified based on a spatial QCL. The QCL (or at least one element of the QCL) in the present disclosure may be replaced with sQCL (spatial QCL).

[0018] A plurality of types (QCL types) of QCL may be defined. For example, four QCL types A to D may be provided, each having different parameters (or parameter sets) that can be assumed to be the same. The parameters (which may be referred to as QCL parameters) are as follows: QCL type A (QCL-A): Doppler shift, Doppler spread, mean delay, and delay spread QCL type B (QCL-B): Doppler shift and Doppler spread QCL type C (QCL-C): Doppler shift and mean delay QCL type D (QCL-D): Spatial reception parameters.

[0019] The UE's assumption that a given Control Resource Set (CORESET), channel, or reference signal has a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be referred to as a QCL assumption.

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

[0021] The TCI state may be, for example, information about the QCL between the channel of interest (in other words, the Reference Signal (RS) for that channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by higher layer signaling, physical layer signaling, or a combination thereof.

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

[0023] The MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0024] The physical layer signaling may be, for example, Downlink Control Information (DCI).

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

[0026] Furthermore, the RS that has a QCL relationship with the channel may be, for example, at least one of a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a sounding reference signal (SRS), a tracking CSI-RS (also called a tracking reference signal (TRS)), and a QCL detection reference signal (also called a QRS).

[0027] An SSB is a signal block including at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). An SSB may also be referred to as an SS / PBCH block.

[0028] The TCI state information element ("TCI-state IE" in RRC) set by higher layer signaling may include one or more pieces of QCL information ("QCL-Info"). The QCL information may include at least one of information on RSs having a QCL relationship (RS relationship information) and information indicating a QCL type (QCL type information). The RS relationship information may include information such as an index of the RS (e.g., an SSB index, a Non-Zero-Power (NZP) CSI-RS resource identifier), an index of a cell in which the RS is located, and an index of a Bandwidth Part (BWP) in which the RS is located.

[0029] In Rel. 15 NR, both QCL type A RS and QCL type D RS, or only QCL type A RS, can be configured for a UE as the TCI state of at least one of the PDCCH and PDSCH.

[0030] When a TRS is configured as a QCL Type A RS, unlike a demodulation reference signal (DMRS) of a PDCCH or a PDSCH, the same TRS is expected to be transmitted periodically over a long period of time. The UE can measure the TRS and calculate the average delay, delay spread, etc.

[0031] A UE in which the TRS is configured as a QCL Type A RS in the TCI state of the DMRS of a PDCCH or PDSCH can assume that the QCL Type A parameters (average delay, delay spread, etc.) of the DMRS of a PDCCH or PDSCH and the TRS are the same, and can therefore obtain the Type A parameters (average delay, delay spread, etc.) of the DMRS of a PDCCH or PDSCH from the measurement result of the TRS. When performing channel estimation of at least one of the PDCCH and the PDSCH, the UE can perform more accurate channel estimation using the measurement result of the TRS.

[0032] A UE configured with a QCL type D RS can determine a UE receive beam (spatial domain receive filter, UE spatial domain receive filter) using the QCL type D RS.

[0033] An RS of QCL type X in a TCI state may refer to an RS that has a QCL type X relationship with a certain channel / signal (DMRS), and this RS may be called a QCL source of QCL type X in the TCI state.

[0034] (Multi-TRP) In NR, one or more transmission / reception points (Transmission / Reception Points (TRP)) (multi-TRP) are considered to perform DL transmission to a UE using one or more panels (multi-panels). Also, it is considered that a UE performs UL transmission to one or more TRPs.

[0035] Note that multiple TRPs may correspond to the same cell identifier (cell identifier (ID)) or different cell IDs. The cell ID may be a physical cell ID or a virtual cell ID.

[0036] 1A-1D illustrate an example of a multi-TRP scenario, assuming, but not limited to, that each TRP is capable of transmitting four different beams.

[0037] 1A shows an example of a case where only one TRP (TRP1 in this example) of multiple TRPs transmits to the UE (this may be referred to as single mode, single TRP, etc.). In this case, TRP1 transmits both control signals (PDCCH) and data signals (PDSCH) to the UE.

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

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

[0040] 1D shows an example of a multi-TRP mode in which each TRP transmits a separate control signal to the UE, and the multi-TRP transmits a data signal (also referred to as a multi-master mode). A first control signal (DCI) may be transmitted on TRP1, and a second control signal (DCI) may be transmitted on TRP2. The UE receives each PDSCH transmitted from the multi-TRP based on these DCIs.

[0041] When multiple PDSCHs from multiple TRPs as shown in Figure 1B (which may also be referred to as multiple PDSCHs) are scheduled using one DCI, the DCI may also be referred to as a single DCI (single PDCCH). Also, when multiple PDSCHs from multiple TRPs as shown in Figure 1D are scheduled using multiple DCIs, these multiple DCIs may also be referred to as multiple DCIs (multiple PDCCHs).

[0042] Each TRP of a multi-TRP may transmit a different code word (CW) and a different layer. Non-Coherent Joint Transmission (NCJT) is being considered as one form of multi-TRP transmission.

[0043] In the NCJT, for example, TRP1 modulates and layer-maps a first codeword to transmit a first PDSCH using a first number of layers (e.g., two layers) with a first precoding, and TRP2 modulates and layer-maps a second codeword to transmit a second PDSCH using a second number of layers (e.g., two layers) with a second precoding.

[0044] Note that multiple PDSCHs (multi-PDSCHs) that are non-coherent may be defined as partially or completely overlapping in time and / or frequency domains, i.e., a first PDSCH from a first TRP and a second PDSCH from a second TRP may overlap in time and / or frequency resources.

[0045] The first PDSCH and the second PDSCH may be assumed to be not quasi-co-located. Reception of multi-PDSCHs may be interpreted as simultaneous reception of PDSCHs that are not of a predetermined QCL type (e.g., QCL type D).

[0046] In URLLC for multi-TRP, it is considered that PDSCH (transport block (TB) or codeword (CW)) repetition across multi-TRP is supported. Repetition schemes (URLLC schemes, e.g., Schemes 1, 2a, 2b, 3, and 4) across multi-TRP in the frequency domain, layer (spatial) domain, or time domain are supported. In Scheme 1, multiple PDSCHs from multi-TRP are space division multiplexed (SDM). In Schemes 2a and 2b, PDSCHs from multi-TRP are frequency division multiplexed (FDM). In Scheme 2a, the redundancy version (RV) is the same for multi-TRP. In Scheme 2b, the RVs for multi-TRP may be the same or different. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are time division multiplexed (TDM). In scheme 3, multiple PDSCHs from multiple TRPs are transmitted in one slot. In scheme 4, multiple PDSCHs from multiple TRPs are transmitted in different slots.

[0047] Such a multi-TRP scenario allows for more flexible transmission control using good quality channels.

[0048] In the multi-master mode as shown in FIG. 1D, two configurations are possible: one in which the same physical cell ID is set for multiple TRPs (intra-TRP mobility, intra-cell TRP mobility, intra-cell mobility, or intra-cell multi-TRP operation), and one in which different physical cell IDs are set for multiple TRPs (inter-TRP mobility, inter-cell TRP mobility, inter-cell mobility, or inter-cell multi-TRP operation).

[0049] Figure 2A is a diagram showing an example of intra-cell mobility. As shown in Figure 2A, the same physical cell ID (PCI1) is set for TRP1 and TRP2. In this case, the SSB (SSB index) transmitted by TRP1 and the SSB transmitted by TRP2 must be different. In the example of Figure 2A, the SSB of TRP1 is 0-31, and the SSB of TRP2 is 32-63.

[0050] FIG. 2B is a diagram showing an example of inter-cell mobility. As shown in FIG. 2B, different physical cell IDs (PCI1, PCI2) are set for TRP1 and TRP2. In this case, the SSB transmitted by TRP1 and the SSB transmitted by TRP2 may overlap or may be different. In the example of FIG. 2B, the SSBs of TRP1 and TRP2 may both be 0-63. Alternatively, the SSBs of TRP1 may be 0-31, and the SSBs of TRP2 may be 32-63. In this case, the RS of the TCI state of PDSCH1 / PDSCH2 is PCI1 or PCI2.

[0051] (Unified / Common TCI Framework) According to the unified TCI framework, UL and DL channels can be controlled using a common framework. The unified TCI framework does not specify the TCI state or spatial relationship for each channel or each RS, as in Rel. 15. Instead, it specifies a common beam and applies it to all or some of the UL and DL channels and RSs. Alternatively, a common beam for the UL may be applied to all or some of the UL channels and RSs, and a common beam for the DL may be applied to all or some of the DL channels and RSs. For a certain channel or RS, a common beam may be applied to all resources, or to some (one or more) resources. The channel / RS to which the beam is applied and the resource to which the beam is applied may be specified in advance in a specification or may be instructed to the UE by higher layer control information.

[0052] One common beam for both DL and UL, or one common beam for DL ​​and one common beam for UL (two common beams overall) are considered.

[0053] The UE may assume the same TCI state for UL and DL (joint TCI state, joint TCI state pool).

[0054] FIG. 3 illustrates an example of a joint common TCI indication for UL / DL. In the example of FIG. 3, RRC (parameters, information elements) configures multiple unified TCI states for both DL and UL. Each of the multiple TCI states may have SSB, CSI-RS, or SRS as the QCL source RS. Note that one circle symbol shown in FIG. 3 (and FIG. 4 described later) may correspond to one or two TCI states for UL / DL. The MAC CE may activate at least some of the configured multiple TCI states.

[0055] One DCI for UL / DL may indicate one of multiple TCI states activated by the MAC CE. The indicated TCI state may apply to any one or a subset of the entire UL / DL. One TCI state indicated in the DCI may apply to both UL and DL. Two TCI states indicated in the DCI may apply to UL / DL, respectively.

[0056] The DCI may use the "TCI state" field in the DCI for DL, a new field for unified TCI in the DCI for UL / DL (e.g., the "new unified-TCI" field), or a new field in a new DCI format applicable to unified TCI.

[0057] As described above, in the joint common TCI indication for UL / DL, one DCI indicates both the TCI for UL and the TCI for DL.

[0058] Figure 4 shows an example of a separate common TCI indication for UL / DL. In the example of Figure 4, RRC (parameters, information elements) configures multiple unified TCI states to be used for both DL and UL. Each of the multiple TCI states may have SSB, CSI-RS, or SRS as the QCL source RS. The MAC CE may activate at least a portion of the configured multiple TCI states. One or more activated TCI states (TCI state pools) may be configured (activated) separately for UL and DL.

[0059] The DCI for DL ​​may indicate one of multiple TCI states activated by the MAC CE. This DCI may be a new DCI format that applies to a unified TCI. The indicated TCI state may apply to any one or a subset of all DL states.

[0060] The DCI for the UL may indicate one of multiple TCI states activated by the MAC CE. This DCI may be a new DCI format that applies to a unified TCI. The indicated TCI state may apply to any one or a subset of the entire UL.

[0061] As described above, in the separate common TCI indication for UL / DL, different DCIs indicate separate TCI states (separate TCI states) for the UL and DL, respectively.

[0062] (L1 / L2 Inter-Cell Mobility) Figure 5 shows an example of TCI state switching. The QCL source RS of TCI #1 is associated with the serving cell, and the QCL source RS of TCI #2 is associated with a non-serving cell. When the UE receives an instruction to update from TCI #1 to TCI #2, it refers to higher layer parameters (RRC parameters) associated with the cell associated with the updated TCI #2.

[0063] The UE may support inter-PCI dynamic point selection (DPS) when receiving only one TRP at a time. In the method up to Rel. 16, the UE either explicitly updates the TCI state via RRC / MAC CE / DCI or updates the TCI state based on the most recent PRACH transmission and updates the PCI (cell) (handover).

[0064] In addition, intra-cell mobility and inter-cell mobility are not limited to the multi-TRP configuration.

[0065] Layer 1 / Layer 2 (L1 / L2) inter-cell mobility is being considered to facilitate more efficient (lower latency and overhead) DL / UL beam management. For example, QCL / TCI-related enhancements may be made to enable inter-cell multi-TRP operation, assuming multi-DCI-based multi-PDSCH reception.

[0066] In L1 / L2 inter-cell mobility, the serving cell can be changed using functions such as beam control without RRC reconfiguration. In other words, transmission and reception with a non-serving cell are possible without handover. Since handover requires RRC reconnection and creates a period when data communication is unavailable, L1 / L2 inter-cell mobility, which does not require handover, is preferable.

[0067] However, there is a possibility that the C-RNTI used in the serving cell cannot be used as is for transmission and reception with a non-serving cell. For example, the C-RNTI used in the serving cell may already be used for another UE in the non-serving cell. If the same C-RNTI is used between UEs in the same cell, problems may occur, such as erroneously reading DCI addressed to another UE (e.g., the Cyclic Redundancy Check (CRC) of the DCI addressed to another UE may be erroneously descrambled).

[0068] Therefore, the present inventors have devised a method for appropriately selecting a C-RNTI. According to one aspect of the present disclosure, for example, high-speed inter-cell mobility can be realized.

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

[0070] In the present disclosure, "A / B" may be read as "at least one of A and B."

[0071] In the present disclosure, the terms panel, uplink (UL) transmitting entity, point, TRP, TRP-ID, TRP ID, spatial relationship, control resource set (CONTROLLER RESOLUTION SET (CORESET)), PDSCH, codeword, base station, predetermined antenna port (e.g., demodulation reference signal (DMRS) port), predetermined antenna port group (e.g., DMRS port group), predetermined group (e.g., code division multiplexing (CDM) group, predetermined reference signal group, CORESET group), and CORESET pool may be interchangeable. Also, panel identifier (ID) and panel may be interchangeable.

[0072] In the present disclosure, cell, CC, carrier, BWP, and band may be read interchangeably.

[0073] In the present disclosure, the terms index, ID, indicator, and resource ID may be interchangeable.

[0074] In the present disclosure, the TCI state may be information about a receive beam (spatial domain receive filter) instructed (configured) for the UE (e.g., DL-RS, QCL type, cell from which the DL-RS is transmitted, etc.). The QCL assumption may be information about a receive beam (spatial domain receive filter) assumed by the UE based on transmission or reception of an associated signal (e.g., PRACH) (e.g., DL-RS, QCL type, cell from which the DL-RS is transmitted, etc.).

[0075] In the present disclosure, spatial relation, spatial relation information (Spatial Relation Information (SRI)), spatial relation assumption, QCL parameter, spatial domain transmit filter, UE spatial domain transmit filter, spatial domain filter, UE transmit beam, UL transmit beam, UL precoding, UL precoder, spatially related RS, DL-RS, QCL assumption, SRI, spatial relation based on SRI, and UL TCI may be read as interchangeable.

[0076] In the present disclosure, TRS, tracking CSI-RS, CSI-RS having TRS information (upper layer parameter trs-Info), and NZP-CSI-RS resource in an NZP-CSI-RS resource set having TRS information may be read as interchangeable.

[0077] In the present disclosure, beam, spatial domain filter, spatial setting, TCI, TCI state, TCI state pool, multiple TCI states, UL TCI state, unified TCI state, unified beam, common TCI state, joint TCI state, common beam, QCL assumption, QCL information, QCL parameters, spatial domain receive filter, UE spatial domain receive filter, UE receive beam, DL beam, DL receive beam, DL precoding, DL precoder, DL-RS, RS of QCL type D for TCI state / QCL assumption, RS of QCL type A for TCI state / QCL assumption, spatial relationship, spatial domain transmit filter, UE spatial domain transmit filter, UE transmit beam, UL beam, UL transmit beam, UL precoding, UL precoder, and PL-RS may be interpreted as interchangeable. In the present disclosure, QCL type X-RS, DL-RS associated with QCL type X, DL-RS having QCL type X, source of DL-RS, SSB, CSI-RS, and SRS may be read interchangeably.

[0078] In this disclosure, the terms "normal TRP," "single TRP," "single TRP system," "single TRP transmission," and "single PDSCH" may be interchangeable. In this disclosure, the terms "multi-TRP," "multi-TRP system," "multi-TRP transmission," and "multi-PDSCH" may be interchangeable. In this disclosure, the terms "single DCI," "single PDCCH," "multi-TRP based on a single DCI," and "activating two TCI states on at least one TCI codepoint" may be interchangeable.

[0079] In the present disclosure, a single TRP, a channel using a single TRP, a channel using one TCI state / spatial relationship, multi-TRP not being enabled by RRC / DCI, multiple TCI states / spatial relationships not being enabled by RRC / DCI, a CORESETPoolIndex value of 1 not being set for any CORESET and no code point in the TCI field being mapped to two TCI states, communicating with one transmitting / receiving point, and applying a single TRP may be read interchangeably.

[0080] In the present disclosure, "multi-TRP," "channel using multi-TRP," "channel using multiple TCI states / spatial relationships," "multi-TRP being enabled by RRC / DCI," "multiple TCI states / spatial relationships being enabled by RRC / DCI," and "at least one of multi-TRP based on a single DCI" and "multi-TRP based on multiple DCI" may be interchangeable. In the present disclosure, "multi-TRP based on multiple DCI," and "setting a CORESET pool index (CORESETPoolIndex) value of 1 for the CORESET" may be interchangeable. In the present disclosure, "multi-TRP based on a single DCI," and "at least one code point in the TCI field is mapped to two TCI states" may be interchangeable.

[0081] In this disclosure, the terms assume, hold, maintain, select, and determine may be read interchangeably.

[0082] (Wireless communication method) In one embodiment of the present disclosure, a UE uses a selected C-RNTI. These terms may be interchangeably read as "using the C-RNTI," "detecting the PDCCH (blind detection) using the C-RNTI," "decoding the PDSCH using the C-RNTI," "scrambling for the PUCCH / PUSCH using the C-RNTI," etc. This is because the C-RNTI is used for scrambling the CRC of the PDCCH (DCI), scrambling data (information bits) of the PDSCH / PUCCH / PUSCH, etc.

[0083] The number of non-serving cells that a UE assumes (the number of non-serving cells that the UE controls transmission and reception to and from, in other words, the number of non-serving cells that the UE can transmit and receive from) may be determined in advance by a specification, may be configured in the UE by higher layer signaling (e.g., RRC / MAC CE), or may be determined based on the UE capabilities.

[0084] The UE may retain / assume the C-RNTIs of a specified / configured / assumed / determined number of non-serving cells in addition to the C-RNTI of the serving cell.

[0085] The UE may use the C-RNTI of the non-serving cell for transmission and reception with the non-serving cell (e.g., at least physical layer transmission and reception (PDCCH detection, PDSCH data descrambling, etc.)).

[0086] Note that the "C-RNTI" in the present disclosure may be replaced with any identifier (for example, another RNTI). Also, the PCI in the present disclosure may be replaced with an identifier related to a cell (for example, a cell index, a serving cell index, etc.). In the present disclosure, a beam instruction, a beam / TCI update instruction, and a cell / serving cell / non-serving cell update instruction may be replaced with each other.

[0087] <First embodiment> [Aspect 1-1] A UE may assume (hold, maintain) a single C-RNTI for TCI states / PCIs associated with a serving cell and a non-serving cell. When a serving cell (PCI of a serving cell) associated with a QCL source RS in a TCI state is updated by a beam instruction (beam instruction / TCI update instruction / serving cell update instruction), the assumed C-RNTI is not updated. The UE assumes the single C-RNTI for UL transmission / DL reception of channels / RSs.

[0088] 6 is a diagram showing an example of C-RNTI assumption in aspect 1-1. In the example of FIG. 6, the UE assumes C-RNTI #1 for both the serving cell and the non-serving cell. Even if the serving cell is updated from a cell with PCI #1 to a cell with PCI #2 by beam instruction, the assumed C-RNTI is not updated.

[0089] [Aspect 1-2] A UE assumes (holds, maintains) multiple (plural) C-RNTIs and, upon receiving a beam instruction (beam instruction / TCI update instruction / serving cell update instruction), if the serving cell is updated by the beam instruction, the UE may select one C-RNTI from the multiple C-RNTIs based on the beam instruction. If the serving cell (PCI of the serving cell) associated with the QCL source RS in the TCI state is updated by the beam instruction, the assumed C-RNTI is updated. The UE assumes the updated C-RNTI for UL transmission / DL reception of the channel / RS.

[0090] 7 is a diagram showing an example of C-RNTI assumption in aspect 1-2. In the example of FIG. 7, the UE assumes C-RNTI #1 for the serving cell and C-RNTI #2 for the non-serving cell. When the serving cell is updated from a cell with PCI #1 to a cell with PCI #2 by beam instruction, the assumed C-RNTI is updated.

[0091] Second Embodiment The second embodiment relates to control of individual channels when multiple C-RNTIs are assumed as in aspect 1-2.

[0092] In the present disclosure, the terms TCI state, unified TCI state, CORESET, SRI, and spatial relationship may be read as TCI state group, unified TCI state group, CORESET group, SRI group, and spatial relationship group, respectively.

[0093] [Aspect 2-1] C-RNTI is used for CRC scrambling of PDCCH. Therefore, it is preferable that the UE knows which C-RNTI will be used for PDCCH detection before blind detection (decoding). If the UE does not know the C-RNTI to be used, the decoding process of the PDCCH (DCI) by the UE becomes complicated.

[0094] The UE may select a C-RNTI based on the PCI used for receiving the CORESET (PDCCH), where the association between the C-RNTI and the serving cell index (PCI) may be pre-configured by higher layer signaling, reported by the UE, or determined / configured based on the UE capabilities reported by the UE.

[0095] [Option 1] The UE may select (determine) a C-RNTI based on the beam indication (TCI state / CORESET corresponding to the updated serving cell) based on the TCI framework of Rel. 15. The serving cell index or PCI may be configured for each TCI state or CORESET. The TCI state corresponding to the CORESET may be indicated (configured) by the RRC / MAC CE / DCI in Rel. 15 / 16. The UE may use the C-RNTI associated with the serving cell (PCI) associated with the TCI state or CORESET for blind detection. The serving cell associated with the TCI state or CORESET may be a non-serving cell.

[0096] FIG. 8 is a diagram illustrating an example of a TCI framework for Option 1 of Aspect 2-1. In the example of FIG. 8, a CORESET, a TCI state, and a non-serving cell index (PCI) are associated with each other. The information illustrated in FIG. 8 may be indicated (configured) to a UE by an RRC / MAC CE / DCI. When a UE monitors a PDCCH in CORESET #1 or using TCI state #1, the UE may use a C-RNTI corresponding to non-serving cell #1 (PCI #6) associated with CORESET #1 or TCI state #1 to detect the PDCCH. The non-serving cell may be replaced with a serving cell.

[0097] [Option 2] The UE may select (determine) a C-RNTI based on the beam instruction (unified TCI state / CORESET corresponding to the updated serving cell) based on the unified TCI framework in Rel. 17. The serving cell index or PCI may be indicated for each unified TCI state or CORESET. The TCI state corresponding to the CORESET may be indicated by an RRC / MAC CE / DCI in the unified TCI framework in Rel. 17. The UE may use the C-RNTI associated with the serving cell (PCI) associated with the unified TCI state or CORESET for blind detection. The serving cell associated with the unified TCI state or CORESET may be a non-serving cell.

[0098] Fig. 9 is a diagram illustrating an example of a TCI framework for Option 2 of Aspects 2-1 and 2-2. In the example of Fig. 9, a unified-TCI codepoint, a unified-TCI state, and serving and non-serving cell indices (PCIs) are associated with each other. The information illustrated in Fig. 9 may be indicated (configured) to a UE by an RRC / MAC CE / DCI. When a UE monitors a PDCCH using a unified-TCI state corresponding to a specified unified-TCI codepoint, the UE may use a C-RNTI corresponding to a serving cell / non-serving cell associated with the unified-TCI state to detect the PDCCH.

[0099] [[Modification]] The serving cell index or PCI may be set for each TCI state. Then, a non-serving flag (x bits) may be used to save RRC overhead. For example, to indicate up to three non-serving cells, a 2-bit flag may be used to indicate one of {serving cell, non-serving cell #1, non-serving cell #2, non-serving cell #3}. In this case, the association between the serving cell index (or PCI) and the non-serving cell #1 / #2 / #3 may be configured in advance by higher layer signaling, etc. This modification is applicable to Option 1 / Option 2.

[0100] [Aspect 2-2] The C-RNTI is used for data scrambling (scrambling initialization of PDSCH). Therefore, it is preferable that the UE knows which C-RNTI will be used for PDSCH reception before receiving the PDSCH.

[0101] The UE may select a C-RNTI based on the PCI used for receiving the PDSCH, where the association between the C-RNTI and the serving cell index (PCI) may be pre-configured by higher layer signaling, etc., reported by the UE, or determined / configured based on the UE capabilities reported by the UE.

[0102] [Option 0] The UE may select (determine) a C-RNTI for PDSCH data scrambling based on information (C-RNTI / serving cell / PCI) corresponding to the scheduling DCI for the PDSCH. For example, the same C-RNTI used for CRC scrambling of the scheduling DCI may also be used for the PDSCH scheduled by the DCI. A different C-RNTI for the PDSCH may be selected depending on whether the scheduling DCI is for a serving cell or a non-serving cell (or the serving cell index / PCI corresponding to the scheduling DCI). For example, an association between the C-RNTI of the PDSCH and the serving cell index / PCI may be configured in advance by higher layer signaling or the like, and the UE may select a C-RNTI based on that association.

[0103] [Option 1] The UE may select (determine) a C-RNTI based on the beam indication (TCI state corresponding to the updated serving cell) based on the TCI framework of Rel. 15. The serving cell index or PCI may be configured for each TCI state. The TCI state of the PDSCH may be indicated (configured) by the RRC / MAC CE / DCI in Rel. 15 / 16. For PDSCH reception, the UE may use the C-RNTI associated with the serving cell (PCI) associated with the TCI state.

[0104] Fig. 10 is a diagram illustrating an example of a TCI framework for Option 1 of Aspect 2-2. In the example of Fig. 10, a codepoint of a TCI state (TCI codepoint), a TCI state, and serving and non-serving cell indices (PCIs) are associated with each other. The information illustrated in Fig. 10 may be indicated (configured) to a UE by an RRC / MAC CE / DCI. When the UE receives a PDSCH using a TCI state corresponding to a specified TCI codepoint, the UE may use a C-RNTI corresponding to the serving cell / non-serving cell associated with the TCI state to receive the PDSCH.

[0105] [Option 2] The UE may select (determine) a C-RNTI based on the beam indication (unified TCI state corresponding to the updated serving cell) based on the unified TCI framework in Rel. 17. The serving cell index or PCI may be indicated for each unified TCI state. The TCI state of the PDSCH may be indicated by the RRC / MAC CE / DCI of the unified TCI framework in Rel. 17. For PDSCH reception, the UE may use the C-RNTI associated with the serving cell (PCI) associated with the unified TCI state. Information similar to that in the example of Figure 9 regarding the association between the unified TCI state and the serving cell (PCI) may be indicated (configured) to the UE by the RRC / MAC CE.

[0106] The modifications in the above aspect 2-1 may also be applied to each option in aspect 2-2.

[0107] [Aspect 2-3] The C-RNTI is used for data scrambling (scrambling initialization of PUSCH). Therefore, it is preferable that the UE knows which C-RNTI will be used for PUSCH reception before transmitting PUSCH.

[0108] The UE may select a C-RNTI based on the PCI used for transmitting the PUSCH, where the association between the C-RNTI and the serving cell index (PCI) may be configured in advance in a specification, reported by the UE, or determined / configured based on the UE capabilities reported by the UE.

[0109] [Option 0] The UE may select (determine) a C-RNTI for PUSCH data scrambling based on information (C-RNTI / serving cell / PCI) corresponding to the scheduling DCI for the PUSCH. For example, the same C-RNTI used for CRC scrambling of the scheduling DCI may also be used for the PUSCH scheduled by the scheduling DCI. A different C-RNTI for the PUSCH may be selected depending on whether the scheduling DCI is for a serving cell or a non-serving cell (or the serving cell index / PCI corresponding to the scheduling DCI). For example, an association between the C-RNTI for the PUSCH and the serving cell index / PCI may be configured in advance by higher layer signaling or the like, and the UE may select a C-RNTI based on that association.

[0110] [Option 1] The UE may select (determine) the C-RNTI based on the beam indication (TCI state / SRI / spatial relationship corresponding to the updated serving cell) based on the TCI / Sounding Reference Signal (SRS) Resource Index (SRI) framework of Rel. 15. The serving cell index or PCI may be configured for each TCI state / SRI / spatial relationship. The TCI state / SRI / spatial relationship for PUSCH may be indicated (configured) by the RRC / MAC CE / DCI in Rel. 15 / 16. For PUSCH transmission, the UE may use the C-RNTI associated with the serving cell (PCI) associated with the TCI state / SRI / spatial relationship.

[0111] Fig. 11 is a diagram illustrating an example of a TCI framework for Option 2 of Aspect 2-3. In the example of Fig. 11, the value of the SRI field, the SRI, and the serving cell index (PCI) are associated with each other. The information illustrated in Fig. 11 may be indicated (configured) to the UE by the RRC / MAC CE / DCI.

[0112] [Option 2] The UE may select (determine) the C-RNTI based on the beam indication (unified TCI state corresponding to the updated serving cell) based on the unified TCI framework in Rel. 17. The serving cell index or PCI may be indicated for each unified TCI state. The TCI state of the PUSCH may be indicated (configured) by the RRC / MAC CE / DCI of the Rel. 17 unified TCI framework for both the joint common TCI indication for DL / UL and the separate common TCI indication for DL / UL. For PUSCH transmission, the UE may use the C-RNTI associated with the serving cell (PCI) associated with the unified TCI state. Regarding the association between the unified TCI state and the serving cell (PCI), information similar to that in the example of Figure 9 may be indicated (configured) to the UE by the RRC / MAC CE.

[0113] The example in which "per TCI state" in the modified example of the above aspect 2-1 is replaced with "per TCI state / SRI / spatial relationship" may be applied to each option of aspect 2-3.

[0114] According to the second embodiment, the UE can appropriately select one of the multi-C-RNTIs to use for each of the PDCCH, the PDSCH, and the PUSCH.

[0115] <Third embodiment> Multi-C-RNTI may be configured by higher layer signaling or may be reported by the UE via MAC CE. The association between a non-serving cell index (PCI) and a C-RNTI may be configured in the UE via RRC / MAC CE / DCI. If the association is configured via MAC CE / DCI, RRC reconfiguration to update the association is avoided. The C-RNTI of the serving cell may be determined by the same rules as in Rel. 15 / 16.

[0116] Fig. 12 is a diagram showing an example of association between non-serving cell indexes and C-RNTIs. The association between the non-serving cell index (PCI) and C-RNTI shown in Fig. 12 may be set in the UE by RRC / MAC CE / DCI. Alternatively, the UE may report the association shown in Fig. 12 to the network (base station) by MAC CE or the like. For example, in Fig. 12, non-serving cell index #1 corresponds to PCI #245 and is associated with C-RNTI #1.

[0117] The number of RRC configurable non-serving cells may be limited, for example, to 1 or 3. RRC reconfiguration may be performed to change the serving cell to a cell other than the RRC configured non-serving cells.

[0118] If the MAC CE can update the association between the non-serving cell index configured by the RRC and the actual non-serving cell index / PCI / C-RNTI, it is possible to avoid reconfiguration of the RRC. The "actual non-serving cell index" may refer to the index of a non-serving cell that is actually available to the UE. For example, the MAC CE may include at least one of the non-serving cell index configured by the RRC, a PCI value associated with the non-serving cell index, a C-RNTI value, an RRC parameter in the ServingCellConfig, etc. Alternatively, the RRC may configure multiple patterns indicating the association between the actual non-serving cell index and the PCI value, the C-RNTI value, the RRC parameter in the ServingCellConfig, etc., and the MAC CE may indicate a pattern index indicating one of the multiple patterns corresponding to the non-serving cell index configured by the RRC.

[0119] Fig. 13 is a diagram showing an example of the relationship between the actual non-serving cell index and various parameters by the RRC. The example of Fig. 13 shows the relationship between the non-serving cell index (or the non-serving cell flag described above) and the actual non-serving cell index, PCI, and C-RNTI. For example, the configuration shown in Fig. 13 may be transmitted to the UE by the RRC, and the actual non-serving cell index, PCI, and C-RNTI may be updated by the MAC CE.

[0120] Figure 14 is a diagram illustrating an example of re-indexing of a non-serving cell ID. The RRC may configure the UE with an association between the re-indexed non-serving cell index (Re-indexing ID) and the PCI value, as shown in Figure 14. For example, the MAC CE may update the re-indexed index instead of the non-serving cell index, PCI, of Figure 13. Using the re-indexed index reduces the number of information bits, thereby reducing RRC signaling overhead.

[0121] Fig. 15 is a diagram showing an example of inter-cell movement of a UE. In the example of Fig. 15, the UE moves from a serving cell to multiple non-serving cells (seven non-serving cells) in sequence. For example, if the number of RRC configurable non-serving cells is three, a Rel. 15 handover is required. However, the UE can reduce the number of handovers by updating non-serving cell information using MAC CE.

[0122] <Fourth Embodiment> When at least some RRC parameters (configurations) of a serving cell and a non-serving cell are different, the UE needs to maintain two sets of configurations and apply different sets of configurations to PDCCH / PDSCH from different cells. In this case, there is a problem that the complexity of UE operation increases. Figure 16 is a diagram showing an example of RRC parameters of a serving cell and a non-serving cell. In the example of Figure 16, the RRC parameters of the serving cell (ServingCellConfig#1) are different from the RRC parameters of the non-serving cell (ServingCellConfig#2). Note that, although the present disclosure describes a case in which the RRC parameters of a non-serving cell are also configured using an RRC information element called ServingCellConfig, this is not limiting, and the RRC parameters of a non-serving cell may be configured using a configuration for the non-serving cell (e.g., an information element called NonServingCellConfig).

[0123] To solve the above problem, the UE may report (transmit) UE capability (UE capability information) indicating that it supports dynamically updating (changing) at least some RRC parameters (configurations) between a serving cell and a non-serving cell (e.g., when switching from a serving cell to a non-serving cell or vice versa (when updating the TCI state / beam)). Then, when switching cells, the UE may use the RRC parameters for the switched cell. Depending on whether the UE has transmitted the UE capability information, the UE determines whether to have different C-RNTIs between the serving cell and the non-serving cell.

[0124] If a UE does not support (or reports that it does not support) the UE capability, the UE may not assume that different RRC parameters (e.g., at least some of the parameters in ServingCellConfig) are configured in the serving cell and the non-serving cell. If a UE does not support (or reports that it does not support) the UE capability, the UE may not assume that different C-RNTIs are held in the serving cell and the non-serving cell. If a UE supports (or reports that it supports) the UE, the UE may hold / assume / select different C-RNTIs in the serving cell and the non-serving cell.

[0125] The process of the fourth embodiment may be applied in combination with, for example, aspect 1-1 or aspect 1-2 of the first embodiment.

[0126] Fifth Embodiment When a serving cell associated with a QCL source RS in a TCI state is updated (to another cell) by beam direction, the UE may assume / determine / select a C-RNTI based on whether the "serving cell" in the existing specifications is updated. This C-RNTI is the single C-RNTI (aspect 1-1) or multi-C-RNTI (aspect 1-2) of the first embodiment.

[0127] [Aspect 5-1] When the UE receives a beam instruction (an instruction related to a non-serving cell) associated with a QCL source RS in a TCI state, the UE may determine that the serving cell is not updated to the non-serving cell.

[0128] The "serving cell" may not be updated for L1 / L2 inter-cell mobility, and the definition of the existing specification may be reused. In other words, the "serving cell" may correspond to a special cell (primary cell, primary secondary cell) and a secondary cell. The "serving cell" may correspond to a cell for which RRC parameters are configured by the ServingCellConfig information element.

[0129] In aspect 5-1, the difference between a serving cell and a non-serving cell is whether the QCL source RS corresponding to the TCI state / SRI / spatial relationship is associated with the serving cell or the non-serving cell.

[0130] In aspect 5-1, for example, even when the UE receives a beam instruction as shown in FIG. 16, the serving cell is not updated (not updated from PCI #1).

[0131] Aspect 5-1 is applicable to both the single C-RNTI (Aspect 1-1) and the multi-C-RNTI (Aspect 1-2) of the first embodiment. Applying a single C-RNTI may mean that the C-RNTI of the serving cell is always used for UL transmission / DL reception of UE-specific channels / RS, regardless of the QCL source associated with the serving cell or a non-serving cell.

[0132] If the serving cell is not updated, CORESET#0 / UE group common CORESET may be configured to have (or be associated with) TCI states corresponding to only the serving cell, and only the UE-specific CORESET and UE-specific PDSCH may be configured to have (or be associated with) TCI states corresponding to non-serving cells.

[0133] Different RRC parameters (at least part of ServingCellConfig) / different C-RNTIs may be used depending on the CORESET associated with UL transmission / DL reception. For example, PDSCH is scheduled by DCI received in a common CORESET or a UE-specific CORESET. For example, the RRC parameters and C-RNTI used for UL transmission / DL reception may be determined based on at least one of the following (1) and (2):

[0134] (1) When CORESET #0 / UE group common CORESET (search space) is associated with UL transmission / DL reception, at least one of the RRC parameters for the serving cell (at least part of ServingCellConfig) and the C-RNTI for the serving cell is used.

[0135] (2) If another CORESET / UE-specific CORESET (search space) is associated with UL transmission / DL reception, at least one of the RRC parameters for the non-serving cell (at least part of the ServingCellConfig) and the C-RNTI for the non-serving cell is used.

[0136] [Aspect 5-2] When the UE receives a beam instruction (an instruction related to a non-serving cell) associated with a QCL source RS in a TCI state, the UE may determine that the serving cell is updated to the non-serving cell.

[0137] The "serving cell" may be updated during L1 / L2 inter-cell mobility. When the serving cell associated with the QCL source RS of the TCI state / SRI / spatial relationship is updated by beam instruction, the assumed "serving cell" may be updated. In this case, the RRC configuration (at least a part of ServingCellConfig) and C-RNTI to be used may be updated according to the assumed "serving cell." To avoid RRC reconfiguration, multiple sets of updated RRC parameters (at least a part of ServingCellConfig) / C-RNTI may be configured in advance as described in the fourth embodiment, and the UE may select one of the RRC parameters / C-RNTI in response to the beam instruction.

[0138] Aspect 5-2 is applicable to both the single C-RNTI (Aspect 1-1) and the multi-C-RNTI (Aspect 1-2) of the first embodiment. When the single C-RNTI is applied, the UE has one C-RNTI, which is updated by an RRC reconfiguration / random access procedure during L1 / L2 inter-cell mobility. When the multi-C-RNTI is applied, the UE may possess / maintain multiple C-RNTIs and select one of the C-RNTIs according to the beam instruction.

[0139] In aspect 5-2, for example, when a UE receives a beam instruction as shown in FIG. 16, the serving cell is updated (updated from PCI #1 to PCI #2).

[0140] If the serving cell can be updated, CORESET#0 / UE group common CORESET may be configured to have (or be associated with) the TCI state corresponding to the non-serving cell.

[0141] The same RRC parameters (at least part of the ServingCellConfig) / same C-RNTI may be used regardless of the CORESET associated with UL transmission / DL reception. For example, PDSCH is scheduled by DCI received in a common CORESET or a UE-specific CORESET. For example, the RRC parameters and C-RNTI used for UL transmission / DL reception may be determined based on at least one of the following (1) and (2):

[0142] (1) When CORESET #0 / UE group common CORESET (search space) is associated with UL transmission / DL reception, at least one of the RRC parameters for the serving cell (at least part of ServingCellConfig) and the C-RNTI for the serving cell is used.

[0143] (2) If another CORESET / UE-specific CORESET (search space) is associated with UL transmission / DL reception, at least one of the RRC parameters for the serving cell (at least part of ServingCellConfig) and the C-RNTI for the serving cell is used.

[0144] According to the fifth embodiment, the UE can appropriately select / assume a C-RNTI in each of the cases where the serving cell is updated and where it is not updated.

[0145] Sixth Embodiment For example, any combination of the following Case A and Case B (for example, combinations of A1 and B1, A1 and B2, A2 and B1, and A2 and B2) may be allowed. In addition, in all examples of Case A and Case B, both the single C-RNTI (Aspect 1-1) and multi-C-RNTI (Aspect 1-2) of the first embodiment are applicable.

[0146] [Case A] (A1) The "serving cell" is updated when the UE performs UL transmission / DL reception of a channel / RS to a non-serving cell (i.e., when the QCL source RS of the UL transmission / DL reception of the channel / RS is associated with a non-serving cell). This case has the advantage of lowering the complexity of the UE and eliminating the need for the UE to receive DL signals from the "non-serving cell."

[0147] (A2) The "serving cell" is not updated when the UE performs UL transmission / DL reception of a channel / RS to a non-serving cell (i.e., when the QCL source RS for UL transmission / DL reception of the channel / RS is associated with a non-serving cell). In this case, there is an advantage that the impact on the specifications is small, the operation of Rel. 15 can be maintained, and the impact on the implementation of the UE is low.

[0148] [Case B] (B1) The cell configurations of the serving cell and the non-serving cells may be almost the same (or completely the same), which has the advantage of reducing the RRC overhead and reducing the complexity of the UE since the RRC parameters (ServingCellConfig) for the cell configuration held by the UE are the same (common to the serving cell and the non-serving cells).

[0149] (B2) Different sets of cell configurations may be permitted for the serving cell and non-serving cells. The UE may be configured differently in at least some of the RRC parameters (ServingCellConfig). This has the advantage of enabling flexible network (NW) operation and improving performance.

[0150] <UE Capabilities> The above-described embodiments / aspects may be applied only when at least one of corresponding UE capabilities (UE capability information) is reported (transmitted) and corresponding parameters are configured by a higher layer. The UE may report at least one of the following (1) to (7) as the UE capabilities, and the UE may be configured according to the report.

[0151] (1) Whether the UE supports the L1 / L2 inter-cell mobility function. (2) In the L1 / L2 inter-cell mobility, the number of TCI states corresponding to non-serving cells (or the total number of TCI states corresponding to serving cells and non-serving cells) configurable by the RRC for each component carrier (CC) (or for all CCs, or for all CCs per band). Note that the number of TCI states configurable by the RRC may be related to the memory capability of the UE. (3) In the L1 / L2 inter-cell mobility, the number of TCI states corresponding to non-serving cells (or the total number of TCI states corresponding to serving cells and non-serving cells) activatable by the MAC CE for each CC (or for all CCs, or for all CCs per band). Note that the number of activatable TCI states may be related to the processing capability of the UE. (4) The number of non-serving cells (number of different PCIs) that the UE can support for each CC (or for all CCs, or for all CCs per band) in L1 / L2 inter-cell mobility. Also, the number of C-RNTIs that the UE can support for L1 / L2 inter-cell mobility. (5) Whether the UE supports updating / changing the "serving cell" for L1 / L2 inter-cell mobility (corresponding to the fifth embodiment). (6) Whether the UE supports different RRC parameters (at least a part of ServingCellConfig) for serving and non-serving cells. (7) Whether the UE supports dynamic change of the serving cell at the DCI level. If the UE does not support dynamic change at the DCI level, the UE may only support dynamic change of the serving cell at the MAC CE level (later than DCI). Here, a change of the serving cell refers to either an assumed change of the serving cell (e.g., as in Aspect 5-2) or only a change of the QCL source RS associated with the serving cell (as in Aspect 5-1).

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

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

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

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

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

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

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

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

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

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

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

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

[0164] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the wireless communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).

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

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

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

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

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

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

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

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

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

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

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

[0176] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including an SS (PSS, SSS) and a PBCH (and a DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as a reference signal.

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

[0178] (Base Station) Fig. 18 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

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

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

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

[0182] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

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

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

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

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

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

[0188] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

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

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

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

[0192] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0193] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30, other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

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

[0195] The transceiver 120 may transmit an instruction regarding a beam. When the serving cell is updated by the instruction, the transceiver 120 may receive an uplink signal using one of a plurality of Cell Radio Network Temporary Identifiers (C-RNTIs) selected based on the instruction.

[0196] The transceiver 120 may receive capability information indicating support for updating at least some Radio Resource Control (RRC) parameters between the serving cell and the non-serving cells.

[0197] When transmitting the capability information, the control unit 110 may assume different Cell Radio Network Temporary Identifiers (C-RNTIs) for the serving cell and the non-serving cells.

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

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

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

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

[0202] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

[0215] The transceiver 220 may also receive instructions regarding the beam.

[0216] When a serving cell is updated based on the beam-related instruction, the control unit 210 may select one C-RNTI from among a plurality of Cell Radio Network Temporary Identifiers (C-RNTIs) based on the instruction. The control unit 210 may select the one C-RNTI based on a Transmission Configuration Indication state (TCI state) corresponding to the updated serving cell or a unified TCI state.

[0217] The control unit 210 may select the one C-RNTI to be used for scrambling the physical downlink shared channel or the physical uplink shared channel based on information corresponding to downlink control information that schedules the physical downlink shared channel or the physical uplink shared channel.

[0218] The transceiver 220 may transmit capability information indicating that it supports updating at least some Radio Resource Control (RRC) parameters between the serving cell and the non-serving cell.

[0219] When transmitting the capability information, the control unit 210 may assume different Cell Radio Network Temporary Identifiers (C-RNTIs) for the serving cell and the non-serving cells.

[0220] When the control unit 210 receives an instruction regarding a non-serving cell associated with a quasi-co-location source reference signal (QCL source RS) in a transmission configuration indication state (TCI state), the control unit 210 may determine that the serving cell is not (or will be) updated to the non-serving cell.

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

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

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

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

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

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

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

[0228] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be implemented in a similar manner.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0268] In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0269] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

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

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

[0272] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0273] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, terms such as an uplink channel and a downlink channel may be read as a sidelink channel.

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

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

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

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

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

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

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

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

[0282] Also, "determination" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "deciding" some action.

[0283] Furthermore, "judgment (decision)" may be read as "assuming," "expecting," "considering," or the like.

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

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

[0286] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

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

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

[0289] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and explanatory and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A transmitter for transmitting capability information indicating that the capability information supports updating at least some Radio Resource Control (RRC) parameters when switching between a serving cell and a non-serving cell is performed; A control unit that selects a Cell Radio Network Temporary Identifier (C-RNTI) for the non-serving cell that is different from a Cell Radio Network Temporary Identifier (C-RNTI) of the serving cell when the capability information is transmitted; A terminal having the above configuration.

2. The control unit determines that the serving cell is updated to the non-serving cell when receiving an indication regarding a non-serving cell associated with a quasi-co-location source reference signal (QCL source RS) in a transmission configuration indication state (TCI state). The terminal according to claim 1.

3. Different settings are made for the serving cell and the non-serving cell. The terminal according to claim 1.

4. The transmitter transmits capability information indicating a number of TCI states corresponding to non-serving cells for each band, the number being configurable by an RRC. The terminal according to claim 1.

5. The transmitter transmits capability information indicating a number of TCI states corresponding to non-serving cells for each band that can be activated by a Medium Access Control Element (MAC CE). The terminal according to claim 1.

6. transmitting capability information indicating support for updating at least some Radio Resource Control (RRC) parameters when a switch between a serving cell and a non-serving cell is performed; selecting a Cell Radio Network Temporary Identifier (C-RNTI) for the non-serving cell that is different from a Cell Radio Network Temporary Identifier (C-RNTI) of the serving cell if the capability information is transmitted; A wireless communication method for a terminal having the above configuration.

7. A receiver for receiving capability information indicating that the receiver supports updating at least some Radio Resource Control (RRC) parameters when switching between a serving cell and a non-serving cell is performed; a control unit that selects a Cell Radio Network Temporary Identifier (C-RNTI) for the non-serving cell that is different from a Cell Radio Network Temporary Identifier (C-RNTI) of the serving cell when the capability information is received; A base station having

8. A system including a terminal and a base station, The terminal includes: A transmitter for transmitting capability information indicating that the capability information supports updating at least some Radio Resource Control (RRC) parameters when switching between a serving cell and a non-serving cell is performed; A control unit that selects a Cell Radio Network Temporary Identifier (C-RNTI) for the non-serving cell that is different from a Cell Radio Network Temporary Identifier (C-RNTI) of the serving cell when the capability information is transmitted, The base station, A receiving unit for receiving the capability information. system.