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

[Technical field]

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

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been specified for the purpose of achieving higher data rates and lower latency (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of achieving higher capacity and greater sophistication of 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 equipment (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)). [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention [Problem to be solved by the invention]

[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 (lower latency and overhead) DL / UL beam management.

[0007] In L1 / L2 inter-cell mobility, it is possible to change the serving cell using functions such as beam control without reconfiguring Radio Resource Control (RRC). In other words, it is possible to transmit and receive data to and from a non-serving cell without handover. Since handover requires RRC reconnection and creates a period during which data communication is not possible, L1 / L2 inter-cell mobility that 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, 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 occur, such as downlink control information addressed to another UE being read by mistake.

[0009] Therefore, an object of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately select a C-RNTI. [Means for solving the problem]

[0010] A terminal according to an embodiment of the present disclosure is When switching occurs A transmitter that transmits capability information indicating that at least a part of radio resource control (RRC) parameters is supported for updating; and when the capability information is transmitted, For the non-serving cell, Cell Radio Network Temporary Identifier (C-RNTI) Select a C-RNTI that is different from and a control unit. Effect of the Invention

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

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

[0013] (TCI, spatial relations, QCL) In NR, it is considered to control 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 a state that is applied to a downlink signal / channel. 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 on the Quasi-Co-Location (QCL) of signals / channels, and may be called spatial reception parameters, spatial relation information, etc. The TCI state may be configured in the UE for each channel or for each signal.

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

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

[0018] A plurality of types (QCL types) of QCL may be defined. For example, four QCL types AD may be provided, each having different parameters (or parameter sets) that can be assumed to be the same. The parameters (which may be called 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 is in a particular 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 assumptions of the signal / channel.

[0021] The TCI state may be, for example, information about the QCL of 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 of these.

[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 be, 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] In addition, 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 be referred to as an SS / PBCH block.

[0028] A TCI state information element ("TCI-state IE" of 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 an RS 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, an index of a Bandwidth Part (BWP) in which the RS is located, etc.

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

[0030] When the TRS is configured as the RS of QCL type A, unlike the demodulation reference signal (DMRS) of the PDCCH or 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 set as a QCL type A RS in the TCI state of the DMRS of PDCCH or PDSCH can assume that the parameters of the QCL type A of the DMRS of PDCCH or PDSCH and the parameters of the QCL type A of the TRS (average delay, delay spread, etc.) are the same, and can therefore obtain the parameters of the DMRS of PDCCH or PDSCH type A (average delay, delay spread, etc.) 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 by 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 (its 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 (TRPs) (multi-TRPs) 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 are diagrams illustrating 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 the multiple TRPs transmits to the UE (may be called single mode, single TRP, etc.). In this case, TRP1 transmits both a control signal (PDCCH) and a data signal (PDSCH) to the UE.

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

[0039] FIG. 1C shows an example of a case where each of the multiple TRPs transmits a part of the control signal to the UE, and the multiple TRPs transmit data signals (which 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 multiple TRP based on these parts of DCI.

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

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

[0042] Each TRP of the multi-TRP may transmit a different code word (CW) and a different layer. As one form of multi-TRP transmission, non-coherent joint transmission (NCJT) is being considered.

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

[0044] In addition, multiple PDSCHs (multi-PDSCHs) that are NCJTed may be defined as partially or completely overlapping with respect to at least one of the time and frequency domains. That is, the first PDSCH from the first TRP and the second PDSCH from the second TRP may overlap with at least one of the time and frequency resources.

[0045] The first PDSCH and the second PDSCH may be assumed to be not quasi-co-located (QCL). Reception of multiple 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 multiple TRPs, it is considered that PDSCH (transport block (TB) or codeword (CW)) repetition across multiple TRPs is supported. It is considered that repetition schemes (URLLC schemes, for example, schemes 1, 2a, 2b, 3, and 4) across multiple TRPs in the frequency domain, layer (spatial) domain, or time domain are supported. In scheme 1, multiple PDSCHs from multiple TRPs are space division multiplexed (SDM). In schemes 2a and 2b, PDSCHs from multiple TRPs are frequency division multiplexed (FDM). In scheme 2a, the redundancy version (RV) is the same for multiple TRPs. In scheme 2b, the RVs may be the same or different for multiple TRPs. 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 channels with better quality.

[0048] In the multi-master mode as shown in FIG. 1D, configurations are possible 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 configurations are possible 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. Or, the SSB of TRP1 may be 0-31, and the SSB 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 by a common framework. The unified TCI framework does not specify the TCI state or spatial relationship for each channel or RS as in Rel.15, but may specify a common beam and apply it to all or a part of multiple channels and RSs in UL and DL, or may apply a common beam for UL to all or a part of multiple channels and RSs in UL and apply a common beam for DL ​​to all or a part of multiple channels and RSs in DL. For a certain channel or RS, a common beam may be applied to all resources, or a common beam may be applied to some (one or more) resources. Which channel / RS to apply to and which resource to apply to may be specified in advance in a specification or may be instructed to a 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 (total of two common beams) 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 is a diagram showing 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 a 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. MAC CE may activate at least a part 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 applied to the 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] FIG. 4 shows an example of a separate common TCI indication for UL / DL. In the example of FIG. 4, the 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. The MAC CE may activate at least a part of the configured multiple TCI states. One or more TCI states to be activated (TCI state pool) 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, which may be a new DCI format applied to the unified TCI. The indicated TCI state may apply to any one or a subset of the entire DL.

[0060] The DCI for UL may indicate one of multiple TCI states activated by the MAC CE. The DCI may be a new DCI format applied to the 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) 5 is a diagram showing an example of switching of TCI states. The QCL source RS of TCI#1 is associated with a serving cell, and the QCL source RS of TCI#2 is associated with a non-serving cell. When the UE receives an update instruction 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 it receives only one TRP at a time. In the methods up to Rel.16, the UE updates the TCI state explicitly by RRC / MAC CE / DCI or updates the TCI state based on the latest (most recent) PRACH transmission and updates the PCI (cell) (handover).

[0064] In addition, intra-cell mobility and inter-cell mobility are not limited to a 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, it is possible to change the serving cell using functions such as beam control without resetting the RRC. In other words, it is possible to transmit and receive data to and from a non-serving cell without handover. Since handover requires RRC reconnection and creates a period when data communication is not possible, L1 / L2 inter-cell mobility that 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 (Cyclic Redundancy Check (CRC)) scrambling of DCI addressed to another UE being 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 addition, in the present disclosure, "A / B" may be read as "at least one of A and B."

[0071] In addition, in the present disclosure, panel, Uplink (UL) transmitting entity, point, TRP, TRP-ID, TRP ID, spatial relationship, control resource set (CONTROLL RESOURCE SET (CORESET)), PDSCH, codeword, base station, specific antenna port (e.g., DeModulation Reference Signal (DMRS) port), specific antenna port group (e.g., DMRS port group), specific group (e.g., Code Division Multiplexing (CDM) group, specific reference signal group, CORESET group), CORESET pool, may be read as mutually interchangeable. Also, panel identifier (ID) and panel may be read as mutually interchangeable.

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

[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 in which 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, DL-RS, QCL type, cell in which DL-RS is transmitted, etc.).

[0075] In the present disclosure, spatial relation, 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 interpreted as interchangeable.

[0076] In the present disclosure, TRS, CSI-RS for tracking, CSI-RS having TRS information (higher 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 in TCI state / QCL assumption, RS of QCL type A in 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, PL-RS, may be read as interchangeable. In the present disclosure, QCL type X-RS, DL-RS associated with QCL type X, DL-RS with QCL type X, source of DL-RS, SSB, CSI-RS, SRS, may be read as interchangeable.

[0078] In the present disclosure, normal TRP, single TRP, single TRP system, single TRP transmission, and single PDSCH may be interchangeable. In the present disclosure, multi-TRP, multi-TRP system, multi-TRP transmission, and multi-PDSCH may be interchangeable. In the present disclosure, single DCI, single PDCCH, multi-TRP based on 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 one not being set for any CORESET and no code point in the TCI field being mapped to two TCI states, communication with one transmission / reception point, and application of a single TRP may be read as interchangeable.

[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 a multiple DCI may be read as mutually interchangeable. In the present disclosure, multi-TRP based on a multiple DCI, and a CORESETPoolIndex value of 1 being set for CORESET may be read as mutually interchangeable. In the present disclosure, multi-TRP based on a single DCI, and at least one code point of a TCI field being mapped to two TCI states may be read as mutually interchangeable.

[0081] In the present disclosure, assumptions, holdings, maintenance, selections, and judgments may be mutually interchangeable.

[0082] (Wireless communication method) In one embodiment of the present disclosure, the UE uses the selected C-RNTI. Using the C-RNTI, performing blind detection of the PDCCH using the C-RNTI, decoding the PDSCH using the C-RNTI, scrambling for PUCCH / PUSCH using the C-RNTI, etc. may be mutually interchangeable. This is because the C-RNTI is used for scrambling the CRC of the PDCCH (DCI), scrambling the data (information bits) of the PDSCH / PUCCH / PUSCH, etc.

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

[0084] The UE may hold / assume the C-RNTIs of the specified / set / 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 (detection of PDCCH, descrambling of PDSCH data, etc.)).

[0086] Note that the "C-RNTI" in the present disclosure may be replaced with any identifier (e.g., other RNTIs). Also, the PCI in the present disclosure may be mutually replaced with an identifier related to the cell (e.g., cell index, serving cell index, etc.). In the present disclosure, beam indication, beam / TCI update indication, cell / serving cell / non-serving cell update indication may be mutually interchangeable.

[0087] <First embodiment> [Aspect 1-1] The UE may assume (have, maintain) a single C-RNTI for TCI states / PCIs associated with serving and non-serving cells. If the serving cell (serving cell's PCI) associated with the QCL source RS in the TCI state is updated by a beam indication (beam indication / TCI update indication / serving cell update indication), the assumption of C-RNTI is not updated. The UE assumes the single C-RNTI for UL transmission / DL reception of the channel / RS.

[0088] Fig. 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 the cell of PCI#1 to the cell of PCI#2 by the beam instruction, the assumption of C-RNTI is not updated.

[0089] [Aspect 1-2] When the UE assumes (holds, maintains) multiple (multiple) C-RNTIs and receives 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 assumption of the C-RNTI is updated. The UE assumes the updated C-RNTI for UL transmission / DL reception of the channel / RS.

[0090] Fig. 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 assumption of C-RNTI is updated.

[0091] <Second Embodiment> The second embodiment relates to the control of individual channels when a plurality of C-RNTIs are assumed as in Aspect 1-2.

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

[0093] [Aspect 2-1] The C-RNTI is used for CRC scrambling of the PDCCH. Therefore, it is preferable that the UE knows which C-RNTI is 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 reception of the CORESET (PDCCH). Here, the association between the C-RNTI and the serving cell index (PCI) may be preset by upper layer signaling or the like, may be reported by the UE, or may be determined / set based on the UE capabilities reported by the UE.

[0095] [[Option 1]] The UE may select (determine) the 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 showing an example of a TCI framework of option 1 in aspect 2-1. In the example of Fig. 8, CORESET, TCI state, and non-serving cell index (PCI) are associated. The information shown in Fig. 8 may be indicated (configured) to the UE by RRC / MAC CE / DCI. When the UE monitors a PDCCH in CORESET#1 or using TCI state#1, the UE may use a C-RNTI corresponding to a 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) the C-RNTI based on the beam indication (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 the RRC / MAC CE / DCI of 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 showing an example of a TCI framework of option 2 in aspects 2-1 and 2-2. In the example of Fig. 9, a unified-TCI codepoint, a unified-TCI state, and serving cell and non-serving cell indexes (PCIs) are associated with each other. The information shown 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] [[Variations]] The serving cell index or PCI may be set for each TCI state. And 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 set in advance by higher layer signaling or the like. This modification is applicable to Option 1 / Option 2.

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

[0101] The UE may select a C-RNTI based on a PCI used for receiving the PDSCH, where the association between the C-RNTI and the serving cell index (PCI) may be preset by higher layer signaling, etc., may be reported by the UE, or may be determined / set 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 a scheduling DCI for the PDSCH. For example, the same C-RNTI as that used for CRC scrambling of the scheduling DCI may also be used for the PDSCH scheduled by the DCI. A different C-RNTI may be selected as the C-RNTI for the PDSCH depending on whether the scheduling DCI is 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 PDSCH and the serving cell index / PCI may be set in advance by higher layer signaling or the like, and the UE may select a C-RNTI based on the association.

[0103] [[Option 1]] The UE may select (determine) the 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 showing an example of a TCI framework of option 1 in aspect 2-2. In the example of Fig. 10, a code point of a TCI state (TCI codepoint), a TCI state, and serving and non-serving cell indexes (PCI) are associated with each other. The information shown in Fig. 10 may be indicated (configured) to a UE by an RRC / MAC CE / DCI. When a UE receives a PDSCH using a TCI state corresponding to a code point of a specified TCI, the UE may use a C-RNTI corresponding to a serving cell / non-serving cell associated with the TCI state to receive the PDSCH.

[0105] [[Option 2]] The UE may select (determine) the C-RNTI by a 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. Regarding the association between the unified TCI state and the serving cell (PCI), information similar to that in the example of FIG. 9 may be indicated (configured) to the UE by the RRC / MAC CE.

[0106] The modified examples 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 the PUSCH). Therefore, it is preferable for the UE to know which C-RNTI is used for PUSCH reception before transmitting the PUSCH.

[0108] The UE may select a C-RNTI based on a PCI used for transmitting the PUSCH, where the association between the C-RNTI and the serving cell index (PCI) may be pre-specified, may be reported by the UE, or may be determined / set 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 a scheduling DCI for the PUSCH. For example, the same C-RNTI as that used for CRC scrambling of the scheduling DCI may also be used for the PUSCH scheduled by the DCI. A different C-RNTI may be selected for the PUSCH C-RNTI depending on whether the scheduling DCI is 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 PUSCH C-RNTI and the serving cell index / PCI may be set in advance by higher layer signaling or the like, and the UE may select a C-RNTI based on the association.

[0110] [[Option 1]] The UE may select (determine) the C-RNTI by 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 of the 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 showing an example of a TCI framework of option 2 in aspect 2-3. In the example of Fig. 11, the value of the SRI field, the SRI, and a serving cell index (PCI) are associated with each other. The information shown in Fig. 11 may be indicated (set) to the UE by the RRC / MAC CE / DCI.

[0112] [[Option 2]] The UE may select (determine) the C-RNTI by a 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 cases of joint common TCI indication for DL / UL and 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 FIG. 9 may be indicated (configured) to the UE by the RRC / MAC CE.

[0113] An 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 be used for each of the PDCCH, the PDSCH, and the PUSCH.

[0115] <Third embodiment> The multiple C-RNTIs may be configured by higher layer signaling or may be reported by the UE by MAC CE. The association between non-serving cell index (PCI) and C-RNTI may be configured in the UE by RRC / MAC CE / DCI. If the association is configured by 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. Also, 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, the 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, the reconfiguration of the RRC can be avoided. The "actual non-serving cell index" may mean the index of the 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, the PCI value associated with the non-serving cell index, the C-RNTI value, the RRC parameters 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 parameters 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 by RRC and various parameters. In the example of Fig. 13, the relationship between the non-serving cell index (or the above-mentioned non-serving cell flag) and the actual non-serving cell index, PCI, and C-RNTI is shown. For example, the configuration as shown in Fig. 13 may be transmitted to the UE by RRC, and the actual non-serving cell index, PCI, and C-RNTI may be updated by the MAC CE.

[0120] FIG. 14 is a diagram showing an example of re-indexing of non-serving cell IDs. An association between a re-indexed non-serving cell index (Re-indexing ID) and a PCI value as shown in FIG. 14 may be configured in the UE by RRC. For example, the MAC CE may update the re-indexed index instead of the non-serving cell index, PCI, in FIG. 13. Using the re-indexed index reduces the number of information bits and can reduce 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, when the RRC configurable number of non-serving cells is three, a Rel. 15 handover is required. However, the UE can reduce the number of handovers by updating the non-serving cell information by the 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. FIG. 16 is a diagram showing an example of RRC parameters of a serving cell and a non-serving cell. In the example of FIG. 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, in the present disclosure, a case is described in which the RRC parameters of the non-serving cell are also configured by an RRC information element called ServingCellConfig, but this is not limited thereto, and the RRC parameters of the non-serving cell may be configured by using a configuration for the non-serving cell (for example, an information element called NonServingCellConfig).

[0123] To solve the above problem, the UE may report (send) a UE capability (UE capability information) indicating that the UE supports dynamically updating (changing) at least some RRC parameters (settings) 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 TCI state / beam)). Then, when switching cells, the UE may use the RRC parameters for the switched cell. Depending on whether the UE has sent the UE capability information, the UE determines whether to have different C-RNTIs between the serving cell and the non-serving cell.

[0124] If the UE does not support (reports that it does not support) the UE capability, the UE may not assume that different RRC parameters (e.g., at least a part of parameters of ServingCellConfig) are configured in the serving cell and the non-serving cell. If the UE does not support (reports that it does not support) the UE may not assume that different C-RNTIs are possessed in the serving cell and the non-serving cell. If the UE supports (reports that it supports) the UE capability, the UE may possess / 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 the serving cell associated with the QCL source RS in the 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 the multi-C-RNTI (aspect 1-2) of the first embodiment.

[0127] [Aspect 5-1] When the UE receives a beam indication (indication regarding a non-serving cell) associated with a QCL source RS in the 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 with 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 if the UE receives a beam instruction as shown in FIG. 16, the serving cell is not updated (not updated from PCI#1).

[0131] Both the single C-RNTI (Aspect 1-1) and the multiple C-RNTI (Aspect 1-2) of the first embodiment are applicable to Aspect 5-1. The application of the single C-RNTI may mean that the C-RNTI of the serving cell is always used for UL transmission / DL reception of the UE-specific channel / 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) a TCI state 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) a TCI state corresponding to a non-serving cell.

[0133] Different RRC parameters (at least a 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-RNTIs 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 a part of the 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] The UE may determine that the serving cell is updated to the non-serving cell when it receives a beam indication (an indication regarding a non-serving cell) associated with a QCL source RS in the TCI state.

[0137] The "serving cell" may be updated in 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 a beam instruction, the assumption of the "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 assumption of the "serving cell". In order to avoid reconfiguration of the RRC, 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 according to a beam instruction.

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

[0139] In aspect 5-2, for example, when the 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 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 a part of ServingCellConfig) and the C-RNTI for the serving cell is used.

[0143] (2) When 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 the ServingCellConfig) and the C-RNTI for the serving cell is used.

[0144] According to the fifth embodiment, the UE can appropriately select / assume the 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 cases A and 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 cases A and B, both the single C-RNTI (aspect 1-1) and the 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., the QCL source RS of the UL transmission / DL reception of the channel / RS is associated with a non-serving cell). In this case, the UE has the advantage of lowering the complexity and the UE does not need 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., the QCL source RS of the UL transmission / DL reception of the channel / RS is associated with a non-serving cell). In this case, there is a merit 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 cell may be substantially the same (or exactly the same). As a result, the RRC overhead is small, and the RRC parameter (ServingCellConfig) of the cell configuration possessed by the UE becomes one (common to the serving cell and the non-serving cell), so there is an advantage that the complexity of the UE is low.

[0149] (B2) A set of different cell configurations may be permitted for the serving cell and the non-serving cell. The UE may have different settings in at least a part of the RRC parameter (ServingCellConfig). In this case, flexible network (NW) operations are possible, and there is an advantage that the performance is improved.

[0150] <UE capability (UE capability)> Each of the above embodiments / aspects may be applied only when at least one of the corresponding UE capability (UE capability information) is reported (transmitted) and the corresponding parameter is set by the upper layer. The UE may report at least one of the following (1) to (7) as the UE capability, and settings may be made according to the report.

[0151] (1) Whether the UE supports the function of mobility between L1 / L2 cells. (2) In mobility between L1 / L2 cells, the number of TCI states corresponding to the non-serving cell (or the total number of TCI states corresponding to the serving cell and the non-serving cell) for each Component Carrier (CC) (or all CCs, or all CCs for each band) that can be set by RRC. Note that the number of TCI states set by RRC may be related to the memory capacity of the UE. (3) In 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) that can be activated by a MAC CE for each CC (or for all CCs, or for all CCs for each band). Note that the number of TCI states that can be activated may be related to the processing capability of the UE. (4) The number of non-serving cells (the number of different PCIs) that the UE can support for each CC (or for all CCs, or for all CCs for each 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 or not to support updating / changing the "serving cell" in L1 / L2 inter-cell mobility (corresponding to the fifth embodiment). (6) Whether different RRC parameters (at least a part of ServingCellConfig) are supported between serving and non-serving cells. (7) Whether dynamic change of serving cell at DCI level is supported. If the UE does not support dynamic change at DCI level, the UE may only support dynamic change of serving cell at MAC CE level (later than DCI). Here, change of serving cell means change of assumed serving cell (e.g., as in aspect 5-2) or change of QCL source RS related to serving cell only (as in aspect 5-1).

[0152] (Wireless communication system) A 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 or a combination of the wireless communication methods according to the above embodiments of the present disclosure.

[0153] 17 is a diagram showing 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), 5th generation mobile communication system New Radio (5G NR), or the like, which are specified by the Third Generation Partnership Project (3GPP).

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

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

[0156] The wireless communication system 1 may support dual connectivity between multiple base stations in the same RAT (for example, dual connectivity in which both the MN and the 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 macro cell C1 with a relatively wide coverage, and a base station 12 (12a - 12c) that is disposed within the macro cell C1 and forms a small cell C2 that is narrower than the macro cell C1. The user terminal 20 may be located within at least one cell. The arrangement, number, etc. of each cell and the user terminal 20 are not limited to the mode shown in the figure. Hereinafter, when the base stations 11 and 12 are not distinguished, they are collectively referred to as the base station 10.

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

[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, or 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, definitions, etc. of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a frequency band higher than FR2.

[0160] Also, the user terminal 20 may communicate 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 conforming to Common Public Radio Interface (CPRI), 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 at least one of, for example, 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 compatible with at least one of communication methods such as LTE, LTE-A, and 5G.

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

[0165] The radio access scheme may be called a waveform. In the wireless communication system 1, other radio access schemes (for example, 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 a downlink channel.

[0167] In addition, 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)), etc. 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 of at least one of the PDSCH and the PUSCH.

[0170] In addition, DCI for scheduling PDSCH may be called DL assignment, DL DCI, etc., and DCI for scheduling PUSCH may be called UL grant, UL DCI, etc. In addition, PDSCH may be replaced with DL data, and 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 to search 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 multiple search spaces. The UE may monitor a 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 called a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," and "CORESET setting" in the present disclosure may be read as interchangeable terms.

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

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

[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 the SS (PSS, SSS) and the PBCH (and the DMRS for the PBCH) may be called an SS / PBCH block, an SS Block (SSB), or the like. In addition, the SS, SSB, and the like may also be called a reference signal.

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

[0178] (base station) 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 one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140 may be provided.

[0179] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and the base station 10 may be assumed to have other functional blocks necessary for wireless communication. Some of the processes 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 with 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 transmission and reception unit 120, the transmission and reception 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 transmission and reception unit 120. The control unit 110 may perform call processing (setting, release, 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, an RF unit 122, and a measurement unit 123.

[0184] The transmitting / receiving antenna 130 can be composed of an antenna described based on common understanding in the technical field to which the present disclosure pertains, 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 a transmission beam and a reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

[0187] The transceiver 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 transceiver 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 to a radio frequency band, filtering, amplification, and the like on the baseband signal, and transmit the radio frequency band signal via the transceiver antenna .

[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 signal received by the transceiver antenna .

[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) for the user terminal 20, control plane data, etc.

[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 that updating of at least some Radio Resource Control (RRC) parameters between a serving cell and a non-serving cell is supported.

[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) 19 is a diagram showing an example of the configuration of a user terminal according to an embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230.

[0199] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and the user terminal 20 may be assumed to have other functional blocks necessary for wireless communication. Some of the processes 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 with 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.

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

[0202] The transmitting / receiving unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting / receiving unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitting / receiving circuit, and the like, 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 composed of an antenna described based on common understanding in the technical field to which this disclosure pertains, 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 220 may form at least one of a transmission beam and a reception beam using digital beamforming (eg, precoding), analog beamforming (eg, 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 transceiver 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 sequence to be transmitted, and output a baseband signal.

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

[0210] The transceiver unit 220 (RF unit 222) may perform modulation to a radio frequency band, filtering, amplification, and the like on the baseband signal, 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 signal received by the transceiver antenna 230.

[0212] The transceiver 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] In addition, the transmitting section and the receiving section of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving section 220 and the transmitting / receiving antenna 230.

[0215] In addition, the transceiver 220 may receive instructions regarding the beam.

[0216] When a serving cell is updated by 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 cells.

[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 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 control unit 210 may determine that the serving cell is not updated (or is updated) to the non-serving cell.

[0221] (Hardware configuration) 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. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by wire, wirelessly, etc.). The functional blocks may be realized by combining the one device or the multiple devices with software.

[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, selection, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the function of transmission may be called a transmitting unit, a transmitter, and the like. In either case, as described above, the method of realization is not particularly limited.

[0223] For example, a base station, a user terminal, etc. in 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 showing an example of a hardware configuration of a base station and a user terminal according to an embodiment. The above-mentioned 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 this disclosure, the terms "apparatus," "circuit," "device," "section," "unit," and the like can be read 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. Also, the processes may be performed by one processor, or the processes may be performed by two or more processors simultaneously, sequentially, or in other manners. Also, the 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 a specific software (program) onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations, controls communications via a communication device 1004, and controls at least one of reading and writing of data in the memory 1002 and the storage 1003.

[0227] The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured with 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), transmission / reception unit 120 (220), etc. may be realized by the processor 1001.

[0228] Moreover, the processor 1001 reads out 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 according to the programs. As the programs, programs that cause a computer to execute at least a part of the operations described in the above-mentioned embodiments are used. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and operated by the processor 1001, and the other functional blocks may be realized 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, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically EPROM (EEPROM), a Random Access Memory (RAM), and other suitable storage media. The memory 1002 may be called a register, a cache, a main memory (primary storage device), and the like. The memory 1002 can store a program (program code), a software module, and the like that is executable to implement a wireless communication method according to an embodiment of the present disclosure.

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

[0231] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order 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 performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

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

[0235] (Modification) In addition, the terms explained in this disclosure and the terms necessary for understanding this 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 read as mutually interchangeable. A signal may also be a message. A reference signal may also be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applied standard. A component carrier (CC) may also be called a cell, a frequency carrier, a 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 the transmission and reception of a signal or channel, and may indicate at least one of, for example, a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), a number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transceiver in the frequency domain, and a specific windowing process 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, a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) 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 be composed of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may be composed 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, sub-frame, slot, mini-slot, and symbol all represent time units for transmitting signals. Different names may be used for the radio frame, sub-frame, slot, mini-slot, and symbol respectively. Note that the time units such as frame, sub-frame, slot, mini-slot, and symbol in this disclosure may be read interchangeably with each other.

[0241] For example, 1 sub-frame may be called a TTI, or a plurality of consecutive sub-frames may be called a TTI, or 1 slot or 1 mini-slot may be called a TTI. That is, at least one of the sub-frame and the TTI may be the sub-frame (1 ms) in the existing LTE, or 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, mini-slot, etc. instead of a sub-frame.

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

[0243] The TTI may be the transmission time unit for a channel-encoded data packet (transport block), code block, codeword, etc., or may be the processing unit for scheduling, link adaptation, etc. Note that when the TTI is given, the time interval (for example, the number of symbols) in which the transport block, code block, codeword, etc. are actually mapped may be shorter than the TTI.

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

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

[0246] Note that a long TTI (e.g., a normal TTI, a subframe, etc.) may be read as a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be read as a TTI having a TTI length less than that of a long TTI and equal to or more than 1 ms.

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

[0248] Also, an RB may include one or a plurality of symbols in the time domain, and may have a length of 1 slot, 1 mini-slot, 1 subframe, or 1 TTI. One TTI, one subframe, etc. may each be constituted by one or a plurality of resource blocks.

[0249] In addition, one or more RBs may be called 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 fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a numerology on a carrier, where the common RBs may be identified by the index of the RBs 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 (a BWP for UL) and a DL BWP (a 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 replaced with "BWP".

[0254] The above-mentioned structures of radio frames, subframes, slots, minislots, and symbols 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, and other configurations can be changed in various ways.

[0255] In addition, the information, parameters, etc. described in the present disclosure may be represented using absolute values, may be represented using relative values ​​from a predetermined value, or may be represented 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 limiting in any way. Furthermore, the formulas 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 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, the 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 a plurality of network nodes.

[0259] The input / output information, signals, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. The information, signals, etc. to be input / output may be overwritten, updated, or appended. The output information, signals, etc. may be deleted. The input information, signals, etc. may be transmitted to other devices.

[0260] The notification of information is not limited to the modes / 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 implemented by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

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

[0262] Also, the notification of predetermined information (e.g., the notification of "being X") is not limited to an explicit notification and may be performed implicitly (e.g., by not performing the notification of the predetermined information or by the notification of another piece of information).

[0263] The determination may be made based on a value represented by a single bit (0 or 1), a Boolean value represented as true or false, or by comparing numerical values ​​(e.g., 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] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the 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, etc.), then 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 this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," and the like may be used interchangeably.

[0268] In this 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. A base station may also be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, etc.

[0269] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the entire coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small base station for indoor use (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or a base station subsystem that provides communication services in this 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 called 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 moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving 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 include a device that does not necessarily move during communication operation. 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, the base station in the present disclosure may be read as a user terminal. For example, each aspect / embodiment 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 a plurality of 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, an uplink channel, a downlink channel, etc. may be read as a sidelink channel.

[0274] Similarly, the user terminal in the present disclosure may be interpreted as a base station. In this 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 performed by a base station may be performed by its upper node in some cases. It is clear that in a network including one or more network nodes having base stations, various operations performed for communication with terminals 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) and a Serving-Gateway (S-GW)), or a combination thereof.

[0276] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to implementation. In addition, the processing procedures, sequences, flow charts, etc. of each aspect / embodiment described in this disclosure may be reordered 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 implemented using any of a wide variety of standards, including 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 a decimal point)), 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 The present invention may be applied to systems using 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), other appropriate wireless communication methods, next-generation systems that are based on these, etc. Also, 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] Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient 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 precede the second element in some way.

[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, and the like.

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

[0282] Also, "determination" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. That is, "determination" may be considered to be "deciding" to perform some action.

[0283] Additionally, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," etc.

[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 the 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, and the like, as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, and the like, 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." Further, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0288] In this disclosure, where articles have been 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 as modified and altered forms without departing from the spirit and scope of the invention defined based on the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have 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.

Images