WO2022220108A1 - User equipment, wireless communication method, and base station - Google Patents

Abstract

The present invention suitably carries out communication, even if carrying out communication using a plurality of transmission points. User equipment according to one aspect of the present disclosure comprises: a control unit that, on the basis of information notified thereto from a base station, determines a timing advance corresponding to a serving cell, and timing advances respectively corresponding to one or more non-serving cells; and a transmission unit that carries out UL transmission on the basis of the timing advance corresponding to the serving cell and at least one of the timing advances respectively corresponding to the one or more non-serving cells. The timing advance corresponding to the serving cell, and the timing advance corresponding to the non-serving cells or the fellow timing advances respectively corresponding to differing non-serving cells, are configured separately.

Description

Terminal, wireless communication method and base station

The present disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems.

In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been specified for the purpose of further high data rate, low delay, etc. (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of further increasing the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

LTE successor systems (for example, 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later) are also being considered. .

In future wireless communication systems (e.g., wireless communication systems after Rel.16/5G), inter-cell mobility including non-serving cells, or multiple transmission/reception points (e.g. , Multi-TRP (MTRP) to control communication based on inter-cell mobility.

However, when UL transmission is performed to a plurality of transmission/reception points, the problem is how to control the timing (for example, timing advance (TA)) applied to UL transmission to each transmission/reception point. If the UL transmission timing to each transmission/reception point is not appropriately controlled, the quality of communication using multiple transmission/reception points may deteriorate.

The present disclosure has been made in view of this point, and aims to provide a terminal and a wireless communication method that enable appropriate communication even when communication is performed using a plurality of transmission points. be one of

A terminal according to one aspect of the present disclosure includes a control unit that determines a timing advance corresponding to a serving cell and a timing advance corresponding to one or more non-serving cells based on information notified from a base station; a transmitter that performs UL transmission based on at least one of timing advances and timing advances respectively corresponding to one or more non-serving cells, wherein the timing advance corresponding to the serving cell and the timing advance corresponding to the non-serving cell; Alternatively, timing advances respectively corresponding to different non-serving cells are set separately.

According to one aspect of the present disclosure, communication can be performed appropriately even when communication is performed using a plurality of transmission points.

1A and 1B are diagrams illustrating an example of inter-cell mobility. FIG. 2 is a diagram showing an example of application of timing advance when using a plurality of TRPs. FIG. 3 is a diagram showing an example of a MAC control element containing a timing advance command. FIG. 4 is a diagram showing another example of application of timing advance when using multiple TRPs. FIG. 5 is a diagram showing another example of application of timing advance when using multiple TRPs. FIG. 6 is a diagram showing another example of a MAC control element containing a timing advance command. 7A and 7B are diagrams showing other examples of MAC control elements that include timing advance commands. 8A and 8B are diagrams illustrating another example of application of timing advance when using multiple TRPs. FIG. 9 is a diagram illustrating an example of classification of serving cells/non-serving cells. 10A and 10B are diagrams showing an example of notifying cell identification information using DCI. FIG. 11 is a diagram illustrating an example of a schematic configuration of a radio communication system according to an embodiment. FIG. 12 is a diagram illustrating an example of the configuration of a base station according to one embodiment. FIG. 13 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment; FIG. 14 is a diagram illustrating an example of hardware configurations of a base station and a user terminal according to an embodiment.

(TCI, spatial relations, QCL)
In NR, the reception processing (e.g., reception, demapping, demodulation, decoding), transmission processing (eg, at least one of transmission, mapping, precoding, modulation, encoding).

The TCI state may represent those that apply to downlink signals/channels. The equivalent of TCI conditions applied to uplink signals/channels may be expressed as spatial relations.

The TCI state is information about the pseudo-colocation (QCL) of signals/channels, and may be called spatial reception parameters, spatial relation information, or the like. The TCI state may be set in the UE on a channel-by-channel or signal-by-signal basis.

　QCL is an index that indicates the statistical properties of a signal/channel. For example, when one signal/channel and another signal/channel have a QCL relationship, Doppler shift, Doppler spread, average delay ), delay spread, spatial parameters (e.g., spatial Rx parameter) are identical (QCL with respect to at least one of these). You may

Note that the spatial reception parameters may correspond to the reception beams of the UE (eg, reception analog beams), and the beams may be specified based on the spatial QCL. QCL (or at least one element of QCL) in the present disclosure may be read as sQCL (spatial QCL).

A plurality of types (QCL types) may be defined for the QCL. For example, four QCL types AD may be provided with different parameters (or parameter sets) that can be assumed to be the same, and the parameters (which may be called QCL parameters) are shown below:
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.

The UE's assumption that one Control Resource Set (CORESET), channel, or reference signal is in a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal is It may be called the QCL assumption.

A 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 conditions or QCL assumptions of that signal/channel.

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

In the present disclosure, higher layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

For MAC signaling, for example, MAC Control Element (MAC CE), MAC Protocol Data Unit (PDU), etc. may be used. Broadcast information includes, for example, Master Information Block (MIB), System Information Block (SIB), Remaining Minimum System Information (RMSI), and other system information ( It may be Other System Information (OSI).

Physical layer signaling may be, for example, downlink control information (DCI).

Note that the channel/signal to which the TCI state is applied may also be referred to as a target channel/reference signal (target channel/RS), simply as a target, etc., and the other signal mentioned above is a reference reference signal (reference RS), a source It may also be called RS (source RS), or simply a reference.

Channels for which the TCI state or spatial relationship is set (designated) are, for example, a downlink shared channel (PDSCH), a downlink control channel (Physical Downlink Control Channel (PDCCH)), an uplink shared channel ( Physical Uplink Shared Channel (PUSCH)) and uplink control channel (Physical Uplink Control Channel (PUCCH)).

In addition, RSs that have a QCL relationship with the channel are, for example, a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a measurement reference signal (Sounding Reference Signal (SRS)), CSI-RS for tracking (also called Tracking Reference Signal (TRS)), reference signal for QCL detection (also called QRS), reference signal for demodulation (DeModulation Reference Signal (DMRS)), etc. It may be one.

An SSB is a signal block that includes at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). An SSB may also be called an SS/PBCH block.

A QCL type X RS in a TCI state may mean an RS that has a QCL type X relationship with (the DMRS of) a certain channel/signal, and this RS is called a QCL type X QCL source in that TCI state. may

(inter-cell mobility)
In NR, one or more Transmission/Reception Points (TRP) (Multi-TRP (MTRP)) are considered to perform DL transmission to the UE. It is also being considered for UEs to perform UL transmissions on one or more TRPs.

A UE may receive channels/signals from multiple cells/TRPs in inter-cell mobility (eg, L1/L2 inter-cell mobility) (see FIGS. 1A and 1B).

FIG. 1A shows an example of inter-cell mobility (eg, Single-TRP inter-cell mobility) including non-serving cells. Here, the UE receives channels/signals from the base station/TRP of cell #1, which is the serving cell, and the base station/TRP of cell #3, which is not the serving cell (non-serving cell). showing. For example, this corresponds to the case where the UE switches/switches from cell #1 to cell #3 (eg, fast cell switch).

In this case, the DCI/MAC CE may update the TCI state and dynamically select the port (eg, antenna port)/TRP. Different physical cell IDs (eg, PCI) are set for cell #1 and cell #3.

FIG. 1B shows an example of a multi-TRP scenario (for example, multi-TRP inter-cell mobility when using multi-TRP). Here, the UE is shown receiving channels/signals from TRP#1 and TRP2. Here, a case is shown where TRP#1 exists in cell #1 (PCI#1) and TRP#2 exists in cell #2 (PCI#2).

Multi-TRPs (TRP #1, #2) may be connected by ideal/non-ideal backhauls to exchange information, data, and the like. Different codewords (CW) and different layers may be transmitted from each TRP of the multi-TRP. As one form of multi-TRP transmission, non-coherent joint transmission (NCJT) may be used as shown in FIG. 1B. Here, a case is shown where NCJT is performed between a plurality of cells (for example, cells of different PCIs). Note that the same serving cell configuration may be applied/configured to TRP#1 and TRP#2.

In NCJT, for example, TRP#1 modulate-maps a first codeword and layer-maps a first number of layers (e.g., two layers) to a first signal/channel using a first precoding. (eg, PDSCH). TRP#2 also modulation-maps a second codeword and layer-maps a second number of layers (e.g., two layers) to a second signal/channel (e.g., PDSCH).

Multiple PDSCHs to be NCJTed (multi-PDSCH) may be defined as partially or completely overlapping in at least one of the time and frequency domains. That is, the first PDSCH from TRP#1 and the second PDSCH from TRP#2 may overlap at least one of time and frequency resources.

It may be assumed that these first PDSCH and second PDSCH are not quasi-co-located (QCL). Reception of multiple PDSCHs may be translated as simultaneous reception of PDSCHs that are not of a certain QCL type (eg, QCL type D).

Multiple PDSCHs from multiple TRPs (which may be referred to as multiple PDSCHs) may be scheduled using one DCI (single DCI (S-DCI), single PDCCH) (single master mode ). One DCI may be transmitted from one TRP of a multi-TRP. A configuration that utilizes one DCI in multi-TRP may be referred to as single DCI-based multi-TRP (mTRP/MTRP).

Multiple PDSCHs from multiple TRPs may be scheduled using multiple DCIs (multiple DCI (M-DCI), multiple PDCCH (multiple PDCCH)) respectively (multimaster mode). Multiple DCIs may be transmitted from multiple TRPs respectively. A configuration that utilizes multiple DCIs in multi-TRP may be referred to as multi-DCI-based multi-TRP (mTRP/MTRP).

It may be assumed that the UE transmits separate CSI reports (CSI reports) for each TRP for different TRPs. Such CSI feedback may be referred to as separate feedback, separate CSI feedback, and so on. In the present disclosure, "separate" may be read interchangeably with "independent."

As shown in FIG. 1, when using multiple TRPs, there are cases where the distances between the UE and each TRP are different. For example, if one TRP corresponds to a serving cell and another TRP corresponds to a non-serving cell, the distance between each TRP and the UE is different.

In existing systems, the transmission timing of UL (Uplink) channels and/or UL signals (UL channels/signals) is adjusted by Timing Advance (TA). The reception timing of UL channels/signals from different user terminals (UE: User Terminal) is adjusted on the radio base station (TRP: Transmission and Reception Point, gNB: gNodeB, etc.) side.

Thus, in at least one of inter-cell mobility including non-serving cells and multi-TRP scenarios, how to control the timing of UL transmission (eg, setting / adjustment of timing advance) etc. becomes a problem .

For example, the issue is how to support different timing advances (eg, TA) in serving and non-serving cells.

Also, there is a problem of how to control PRACH transmission using the PDCCH order for timing advance measurement for serving/non-serving cells. For example, when the PRACH is triggered by a PDCCH order, the UE determines which cell the PDCCH order (or PRACH trigger) corresponds to (eg, for the serving cell or for the non-serving cell). The problem is how to judge Also, the problem is how the UE learns the PRACH configuration of the non-serving cell.

The present inventors studied UL transmission timing control for multiple cells (eg, serving cell/non-serving cell) and came up with the present embodiment.

Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Each aspect may be applied alone or in combination.

In the present disclosure, "A/B" may mean "at least one of A and B", and "A/B/C" may mean "at least one of A, B and C".

In the present disclosure, activate, deactivate, indicate (or indicate), select, configure, update, determine, etc. may be read interchangeably.

In the present disclosure, RRC, RRC parameters, RRC messages, higher layer parameters, information elements (IEs), and settings may be read interchangeably. In the present disclosure, MAC CE, update command, and activation/deactivation command may be read interchangeably. In the present disclosure, supporting, controlling, controllable, operating, and capable of operating may be read interchangeably.

Also, in the present disclosure, sequences, lists, sets, groups, groups, etc. may be read interchangeably.

In the present disclosure, Panel, Beam, Panel Group, Beam Group, Uplink (UL) transmitting entity, TRP, Spatial Relationship Information (SRI), Spatial Relationship, Control Resource Set (COntrol Resource SET (CORESET)), Physical Downlink Shared Channel ( PDSCH), codeword, base station, predetermined antenna port (e.g., demodulation reference signal (DMRS) port), predetermined antenna port group (e.g., DMRS port group), predetermined group (e.g., Code Division Multiplexing (CDM) group, predetermined reference signal group, CORESET group), predetermined resource (e.g., predetermined reference signal resource), predetermined resource set (e.g., predetermined reference signal resource set) , CORESET pool, PUCCH group (PUCCH resource group), spatial relationship group, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, etc. may be read interchangeably.

The panel may relate to at least one of the group index of the SSB/CSI-RS group, the group index of the group-based beam reporting, the group index of the SSB/CSI-RS group for the group-based beam reporting.

Also, the panel identifier (ID) and the panel may be read interchangeably. In other words, TRP ID and TRP, CORESET group ID and CORESET group, etc. may be read interchangeably.

In the present disclosure, indexes, IDs, indicators, and resource IDs may be read interchangeably. In the present disclosure, sequences, lists, sets, groups, groups, clusters, subsets, etc. may be read interchangeably.

In the present disclosure, a UE configured with multiple TRPs is configured based on at least one of the following: TRPs corresponding to DCI, TRPs corresponding to DCI-scheduled PDSCH or UL transmissions (PUCCH, PUSCH, SRS, etc.); At least one such as may be determined.
- Values of certain fields contained in the DCI (eg, the field specifying the TRP, the antenna port field, the PRI).
- DMRS corresponding to the scheduled PDSCH/PUSCH (eg, sequence, resource, CDM group, DMRS port, DMRS port group, antenna port group, etc. of the DMRS).
- A DMRS corresponding to the PDCCH on which the DCI was transmitted (for example, the relevant DMRS sequence, resource, CDM group, DMRS port, DMRS port group, etc.).
- The CORESET that received the DCI (for example, the CORESET pool ID of the CORESET, the ID of the CORESET, the scramble ID (which may be replaced with the affiliate ID), the resource, etc.).
• RSs (such as RS-related groups) used for TCI states, QCL assumptions, spatial relationship information, etc.;

In the present disclosure, a single PDCCH (DCI) may be referred to as a PDCCH (DCI) of the first scheduling type (eg, scheduling type A (or type 1)). A multi-PDCCH (DCI) may also be referred to as a PDCCH (DCI) of a second scheduling type (eg, scheduling type B (or type 2)).

In the present disclosure, for a single DCI, the i-th TRP (TRP#i) may mean the i-th TCI state, the i-th CDM group, etc. (i is an integer). For multi-DCI, the i-th TRP (TRP#i) may mean the CORESET corresponding to CORESET pool index = i, the i-th TCI state, the i-th CDM group, etc. (where i is an integer).

In the present disclosure, single PDCCH may be assumed to be supported when multiple TRPs utilize the ideal backhaul. Multi-PDCCH may be assumed to be supported when inter-multi-TRP utilizes non-ideal backhaul.

Note that the ideal backhaul may also be called DMRS port group type 1, reference signal related group type 1, antenna port group type 1, CORESET pool type 1, and so on. Non-ideal backhaul may be referred to as DMRS port group type 2, reference signal associated group type 2, antenna port group type 2, CORESET pool type 2, and so on. Names are not limited to these.

In the present disclosure, multi-TRP, multi-TRP system, multi-TRP transmission, and multi-PDSCH may be read interchangeably.

In this disclosure, single DCI (sDCI), single PDCCH, multi-TRP system based on single DCI, sDCI-based MTRP, activating two TCI states on at least one TCI codepoint may be read interchangeably. .

In the present disclosure, multi-DCI (mDCI), multi-PDCCH, multi-TRP system based on multi-DCI, mDCI-based MTRP, two CORESET pool indices or CORESET pool index = 1 (or a value of 1 or more) is set You may read each other.

The QCL of the present disclosure may be read interchangeably with QCL Type D.

In the following description, TA maintenance, adjustment, update, setting, measurement, calculation, and acquisition may be read interchangeably.

(Wireless communication method)
At least one of the following first to third options may be applied as timing advance (eg, TA) setting/adjustment for a plurality of TRPs.
(first option)
The first option describes UL transmission control that applies timing advance in initial connection (eg Initial TA) or timing advance in random access channel (eg PRACH) transmission.

<TA offset>
The UE controls the transmission timing of UL transmissions based on the TA offset (eg, first offset). The TA offset (eg, N _{TA_offset} ) may be set to the UE using higher layer signaling (eg, RRC signaling or broadcast information, etc.) from the network (eg, base station). The UE may apply a predetermined TA offset (default TA offset) to control UL transmission if no TA offset is configured in higher layer signaling (eg, higher layer parameter (n-TimingAdvanceOffset)). The predetermined TA offset may be a pre-specified value.

The TA offset may be configured to be commonly set for a plurality of TRPs (TA control 1), or may be configured to be set for a predetermined TRP (or a predetermined TRP group) (TA control 2).

<TA control 1>
The same TA offset may be set for multiple TRPs (also called serving TRPs). For example, the UE may assume that the same TA offset is configured for multiple TRPs if random access procedures (eg, PRACH transmissions) are supported in multiple TRPs. In this case, the UE applies the same TA offset for multiple TRPs to control UL transmission.

The TA offset may be set with upper layer parameters for each TRP, or may be set with upper layer parameters only for a predetermined TRP. If only a given TRP has a TA offset set in higher layer parameters, the UE may control UL transmissions assuming that the same TA offset is set for other TRPs as well.

Alternatively, the UE may assume that a predetermined TRP offset (default TRP offset) is applied to multiple TRPs if the TA offset is not set in higher layer parameters.

By applying the same TA offset to a plurality of TRPs in this way, it is possible to simplify timing advance control in a configuration that applies a plurality of TRPs. In particular, when the difference in distance between each TRP and the UE is small, it is effective to set the same TA offset for each TRP to control UL transmission.

Alternatively, if the random access procedure is supported by a predetermined TRP (for example, only one TRP) among multiple TRPs, the TA offset may be set only for the predetermined TRP.

For example, the UE may assume that if a random access procedure is supported in a given TRP, the TA offset is set only for that given TRP. In this case, the UE applies the TA offset for a given TRP to control the UL transmission. The predetermined TRP may be a TRP used for initial access.

<TA control 2>
A configuration may be adopted in which a TA offset (eg, N _{TA_offset} ) is set for a predetermined TRP (eg, one TRP) among a plurality of serving TRPs. In this case, the UE may determine the TA value based on the TA offset for UL transmissions on a given TRP and apply a TA value different from the given TRP for UL transmissions on other TRPs.

The predetermined TRP may be, for example, a TRP for contention-based PRACH transmission, or a TRP used for initial access. Another TRP may be, for example, a TRP that supports contention-free PRACH transmission. Of course, the types of predetermined TRP and other TRPs are not limited to this.

The TA value of another TRP may be determined based on the offset (eg, second offset) from the TA offset (eg, first offset) set for a given TRP. The second offset may be a TRP (or TRP group) specific offset determined for each TRP (or TRP group).

A UE determines a TA value based on a TA offset (first offset) for a given TRP to control UL transmission timing. It should be noted that it may be assumed that the second offset (hereinafter also referred to as TRP offset (TRP_offset)) is 0 for a given TRP. On the other hand, the UE may determine the TA value based on the TA offsets for other TRPs and the TRP offsets corresponding to each TRP to control the UL transmission timing.

FIG. 2 shows a case where a TA offset is set for TRP#1 and a TRP offset is set for TRP#2. The UE controls the UL transmission timing to TRP#1 based on the TA offset. Also, the UE controls the UL transmission timing to TRP#2 based on the TA offset and TRP offset.

The TRP offset corresponding to each TRP (or TRP group) may be set in the UE using higher layer signaling from the network (eg, base station). The UE determines the TA value for each TRP based on the TRP offset set by the base station. In this way, by determining the TA value for other TRPs based on the offset from the TA offset of a predetermined TRP, it is possible to suppress an increase in the number of bits to be notified.

Alternatively, the UE may determine the TRP offset corresponding to each TRP. The UE may determine the TRP offset (or TA value) corresponding to each TRP based on predetermined conditions and control the UL transmission timing for each TRP.

　The values of multiple TRP offsets may be defined in advance in the specification. For example, a unique TRP offset may be associated with each TRP (TRP index). Information about the TRP offset value may also be configured in the UE from the network.

Alternatively, a TA value used for timing advance instead of TRP offset may be set for other TRPs. In this case, information on the TA value corresponding to each TRP may be set from the base station to the UE using higher layer signaling. Also, for other TRPs, an offset from the TA value of a predetermined TRP may be set and notified to the UE.

(second option)
The second option describes UL transmission control using timing advance adjustment (TA adjustment) or UL time alignment for a given UL transmission (e.g. PUSCH, SRS and/or PUSCH). . In the following description, a case in which a timing advance command (TA command) is transmitted using a MAC control element (eg, MAC CE) will be taken as an example, but the present invention is not limited to this.

The TA command is a command indicating the transmission timing value of the uplink channel and is included in the MAC control element. A TA command is signaled at the MAC layer from the radio base station to the user terminal. The UE controls a predetermined timer (eg, TA timer) based on receiving the TA command.

The TA timer is a timer that measures the time during which the MAC control element containing the TA command is not received, in other words, the time after the MAC control element containing the TA command is received. When the TA timer expires (when the time measured by the TA timer continues for a predetermined time or longer), the uplink resource reserved for the user terminal is released, and uplink channel transmission is stopped.

It should be noted that the TA timer is started (initialized) each time a TA command is received. The UE can perform UL transmission (transmission of PUCCH, PUSCH, uplink measurement reference signal (SRS), etc.) to cells for which the TA timer has not expired. On the other hand, the UE is restricted from UL transmission other than the random access preamble (PRACH) for the cell for which the TA timer has expired.

That is, the UE controls UL transmission in each TRP based on the set TA timer, and does not transmit anything other than PRACH to the cell whose TA timer has expired. In the existing LTE system, a UE in which a TA timer is set counts the TA timer every predetermined time unit (for example, subframe or slot).

The UE may perform timing control of UL transmission by applying timing advance (multiple timing advance) for each timing advance group (TAG: Timing Advance Group) set in advance.

When applying multiple timing advance, support a timing advance group (TAG: Timing Advance Group) classified by transmission timing. The UE may control the UL transmission timing for each TAG assuming that the same TA offset (or TA value) is applied for each TAG. That is, the TA offset may be set independently for each TAG.

In this way, when multiple timing advance is applied, the UE independently adjusts the transmission timing of the TRPs belonging to each TAG, so that the radio base station can match the uplink signal reception timing from the UE.

When TAGs are set, any of the following TA controls 3-6 may be applied as TRP setting for each TAG or timer (eg, TA timer) control in each TAG.

<TA control 3>
A different TAG may be set for each TRP (or TRP group). Information about the correspondence relationship between each TRP (or DMRS port group, codeword (CW), PDCCH configuration (eg, PDCCH-config), PDSCH configuration (PDSCH-config), serving cell configuration (ServingCellConfig)) and TAG may be set by higher layer signaling from the network (eg, base station) to the UE.

For example, the base station notifies the UE of information indicating that TRP#1 and TAG#0 are compatible, and that TRP#2 and TAG#1 are compatible, using higher layer signaling or the like. The UE may determine the TAG to which each TRP belongs based on information from the base station.

Also, the base station includes the TAG ID in the MAC control element used to indicate the TA command and notifies the UE (see FIG. 3). In this case, the UE applies the TA command to the TRP associated with the TAG ID included in the MAC control element that notifies the TA command. Here, a case is shown where TAG ID=0 and TRP#1 correspond, and TAG ID=1 and TRP#2 correspond.

For example, when the UE receives the MAC control element for the TA command, the UE adjusts the timing of UL transmission (eg, at least one of PUCCH, PUSCH and SRS) in the TRP corresponding to the specified TAG.

Also, a TA timer (for example, timeAlignmentTimer) for UL transmission time alignment (UL time alignment) may be independently controlled for each TAG. For example, the UE sets and controls a TA timer for each TAG (or TRP). That is, the UE is allowed to configure different TA timers for different TAGs (or TRPs).

In this way, by associating a TRP with each TAG and performing timing advance, it is possible to flexibly perform UL transmission control (eg, transmission timing, timer control, etc.) for each TRP.

<TA control 4>
The same TAG may be set for multiple TRPs. That is, the base station may configure multiple TRPs to belong to the same TAG. Information about a predetermined TAG to which the plurality of TRPs belong may be configured from the network (eg, base station) to the UE by higher layer signaling.

For example, the base station notifies the UE of information on predetermined TAGs associated with multiple TRPs using higher layer signaling or the like. The UE may determine a given TAG to which TRPs belong based on information from the base station.

Also, the base station includes the TAG ID in the MAC control element used to indicate the TA command, and notifies the UE of it in a predetermined TRP. For example, the UE may apply the MAC control element to a predetermined TRP (eg, one TRP) among multiple TRPs. The predetermined TRP may be the TRP with the minimum or maximum TRP index, or may be the TRP that supports collision-type PRACH transmission.

　The MAC control element (or TA command) may not be applied to other TRPs. The base station may transmit the MAC control element including information about the TRP to which the MAC control element is applied. Also, the base station may transmit the MAC control element to the UE using only a predetermined TRP (eg, one TRP) among multiple TRPs.

For example, when the UE receives a MAC control element for a TA command for a given TRP, adjust the timing of UL transmission to the TRP included in the specified TAG (eg, at least one of PUCCH, PUSCH and SRS) do.

Also, a TA timer (for example, timeAlignmentTimer) for UL transmission time alignment (UL time alignment) for each TAG may be commonly controlled for multiple TRPs included in the same TAG. That is, one timer is applied as a timer for UL time adjustment of a plurality of TRPs. This makes it possible to commonly control the UL time adjustments of multiple TRPs (eg, control the timers of multiple TRPs to continue or stop at the same time), thereby simplifying the UE operation.

Alternatively, a TA timer (for example, timeAlignmentTimer) for UL transmission time alignment (UL time alignment) for each TAG may be independently controlled for each of a plurality of TRPs included in the same TAG.

[TA offset]
Also, a TA offset (for example, N _{TA_offset} ) may be set for a predetermined TRP (for example, one TRP) among a plurality of TRPs included in the same TAG. In this case, the UE determines a TA value (e.g., TA_TRP#1) based on the TA offset for UL transmissions to a given TRP (e.g., TRP#1) and to another TRP (e.g., TRP#2). A TA value different from the predetermined TRP may be applied for the UL transmission of (see FIG. 4).

The TA value of another TRP may be determined based on a second offset from the TA offset set for the given TRP (or the TA value applied to the given TRP). The second offset may be a TRP (or TRP group) specific offset determined for each TRP (or TRP group).

A UE determines a TA value based on a given offset (eg, TA offset) with respect to a given TRP to control UL transmission timing. It should be noted that it may be assumed that the second offset (hereinafter also referred to as TRP offset (TRP_offset)) is 0 for a given TRP. On the other hand, the UE may determine the TA value based on the TA offsets for other TRPs and the TRP offsets corresponding to each TRP to control the UL transmission timing.

The TRP offset corresponding to each TRP (or TRP group) may be set in the UE using higher layer signaling from the network (eg, base station). The UE determines the TA value for each TRP based on the TRP offset set by the base station. In this way, by determining the TA value for other TRPs based on the offset from the TA offset of a predetermined TRP, it is possible to suppress an increase in the number of bits to be notified.

Alternatively, the UE may determine the TRP offset corresponding to each TRP. The UE may determine the TRP offset (or TA value) corresponding to each TRP based on predetermined conditions and control the UL transmission timing for each TRP.

　The values of multiple TRP offsets may be defined in advance in the specification. For example, a unique TRP offset may be associated with each TRP (TRP index). Information about the TRP offset value may also be configured in the UE from the network.

Alternatively, a TA value used for timing advance instead of TRP offset may be set for other TRPs. In this case, information on the TA value corresponding to each TRP may be set from the base station to the UE using higher layer signaling.

Alternatively, the same TA offset may be set for multiple TRPs (also called serving TRPs).

The UE may apply a combination of TA Control 1 and TA Control 4, or TA Control 2 and TA Control 4.

<TA control 5>
In TA control 5, in a configuration in which the same TAG is set for a plurality of TRPs (or a plurality of TRPs belong to the same TAG), MAC control elements for TA commands transmitted from the base station are assigned to a plurality of TRPs. apply to That is, when the UE receives the MAC control element for the TA command, the UE applies the TA command to one or more TRPs included in the predetermined TAG specified by the MAC control element.

As a result, TA commands for one or more TRPs included in the same TAG can be notified using one MAC control element.

Any operation shown in TA control 4 may be applied to the operation other than the transmission of the MAC control element for the TA command.

The UE may apply a combination of TA Control 1 and TA Control 5, or TA Control 2 and TA Control 5.

<TA control 6>
In TA control 6, in a configuration in which the same TAG is set for a plurality of TRPs (or a plurality of TRPs belong to the same TAG), MAC control elements for TA commands transmitted from the base station are Applies to TRPs where control elements are sent. That is, when the UE receives a MAC control element for a TA command, the UE applies the TA command to the TRP that received the MAC control element (see FIG. 5).

When the UE receives a MAC control element containing a TA command in TRP#1, it applies the TA command to UL transmission of TRP#1 (for example, at least one of PUSCH, PUCCH and SRS). Further, when the UE receives a MAC control element including a TA command in TRP#2, the UE applies the TA command to UL transmission of TRP#2.

Also, the UE may independently control predetermined timers for UL time adjustment (for example, timeAlignmentTimer) for multiple TRPs included in the TAG.

Any operation shown in TA control 4 may be applied to operations other than transmission of MAC control elements for TA commands and timer control.

<TA command notification>
In the above description, a case has been shown in which the information about the TRP corresponding to each TAG is notified by higher layer signaling, but the present invention is not limited to this. TRP (or DMRS port group, codeword (CW), PDCCH configuration (for example, PDCCH-config), PDSCH configuration (PDSCH-config), serving cell configuration (ServingCellConfig), serving cell ID) may also be included. For example, TA command notification method A or TA command notification method B may be applied.

[TA command notification method A]
For example, a MAC control element containing a TA command may be provided with a predetermined bit area for designating a TRP (see FIG. 6). FIG. 6 shows an example of providing a bit area for TRP notification in addition to a bit area for TAG ID notification and a bit area for TA command notification in the MAC control element. The bit area for the TA command notification may be defined with 1 bit or 2 or more bits.

When the UE receives a MAC control element that includes a bit area for TRP notification, it controls the UL transmission timing to the TRP specified in the MAC control element based on the TA command included in the MAC control element. The UE may also apply the TA command to other TRPs included in the same TAG as the designated TRP.

[TA command notification method B]
A new LCID (Logical Channel ID) included in the MAC header (or MAC subheader) may be defined in the MAC control element used to notify the TA command.

For example, information about TRP may be included in a predetermined bit area of the MAC control element for the existing TA command. For example, the fields for TAG ID notification are TRP (or DMRS port group, codeword (CW), PDCCH configuration (eg, PDCCH-config), PDSCH configuration (PDSCH-config), serving cell configuration (ServingCellConfig), serving cell ID (either) (see FIG. 7A).

Alternatively, part of the field for TA command notification is TRP (or DMRS port group, codeword (CW), PDCCH configuration (eg, PDCCH-config), PDSCH configuration (PDSCH-config), serving cell configuration (ServingCellConfig) , serving cell ID) (see FIG. 7B).

Here, a case is shown in which 1 bit or 2 bits of the TA command notification field are used as the TRP designation field, but the number of applicable bits is not limited to this. Also, the remaining fields of the TA command notification field may be used for TA command notification. For example, the remaining fields may be used to notify a TA command, or to notify a TA command (eg, difference) based on the TA command of another TRP (eg, default TRP#0).

By using the MAC control element to notify information related to the TRP that notifies the TA command, it is possible to eliminate the need to notify the information related to the TAG ID and the TRP using higher layer signaling.

(third option)
A third option describes UL transmission control using timing advance adjustment (TA adjustment) or UL time alignment for a given UL transmission (e.g. PUSCH, SRS and/or PUSCH). . In the following description, a case in which a timing advance command (TA command) is transmitted using a random access response (RAR, also called message 2) will be taken as an example, but the present invention is not limited to this.

A random access response (hereinafter also referred to as RAR) is one of the operations in the random access procedure and is also called message 2. In the random access procedure, the base station transmits RAR as a response signal for PRACH transmitted from UE.

The RAR contains information on timing advance (eg, TA command). Upon receiving the RAR, the UE adjusts the UL transmission timing based on the TA command included in the RAR and establishes UL synchronization. Also, the UE transmits a control message of higher layers (L2/L3: Layer 2/Layer 3) using the UL resource specified by the UL grant included in the RAR (message 3).

When information about timing advance (eg, TA command) is included in RAR and transmitted to the UE, one of the following TA control 7-9 as a TA command notification method or timer (eg, TA timer) control in each TRP may apply.

<TA control 7>
A TA command contained in a RAR may apply only to a given TRP. For example, the UE may apply the TA command to a predetermined TRP (eg, one TRP) among multiple TRPs. The predetermined TRP may be the TRP with the minimum or maximum TRP index, or may be the TRP that supports collision-type PRACH transmission.

Also, a TA timer (for example, timeAlignmentTimer) for UL transmission time alignment (UL time alignment) may be commonly controlled for multiple TRPs. That is, one timer is applied as a timer for UL time adjustment of a plurality of TRPs. This makes it possible to commonly control the UL time adjustments of multiple TRPs (eg, control the timers of multiple TRPs to continue or stop at the same time), thereby simplifying the UE operation.

Alternatively, a TA timer (for example, timeAlignmentTimer) for UL transmission time alignment (UL time alignment) may be independently controlled for each of a plurality of TRPs.

[TA offset]
The UE may apply different TA values (or offsets) for each TRP. For example, an offset may be set (or defined) for each TRP. The offset corresponding to each TRP may be an offset to the TA value of the predetermined TRP, or may be an offset to the TA offset set for the predetermined TRP.

For example, the UE determines a TA value based on a given offset (eg, TA offset) with respect to a given TRP to control UL transmission timing. On the other hand, the UE may determine the TA value based on the TA offsets for other TRPs and the TRP offsets corresponding to each TRP to control the UL transmission timing.

The TRP offset corresponding to each TRP (or TRP group) may be set in the UE using higher layer signaling from the network (eg, base station). The UE determines the TA value for each TRP based on the TRP offset set by the base station. In this way, by determining the TA value for other TRPs based on the offset from the TA offset of a predetermined TRP, it is possible to suppress an increase in the number of bits to be notified.

Alternatively, the UE may determine the TRP offset corresponding to each TRP. The UE may determine the TRP offset (or TA value) corresponding to each TRP based on predetermined conditions and control the UL transmission timing for each TRP.

　The values of multiple TRP offsets may be defined in advance in the specification. For example, a unique TRP offset may be associated with each TRP (TRP index). Information about the TRP offset value may also be configured in the UE from the network.

Alternatively, a TA value used for timing advance instead of TRP offset may be set for other TRPs. In this case, information on the TA value corresponding to each TRP may be set from the base station to the UE using higher layer signaling.

Any of the operations shown in TA control 4 may be applied to other UL transmission operations based on TA control.

<TA control 8>
TA control 8 applies the TA command transmitted from the base station to a plurality of TRPs when the TA command is transmitted by RAR. That is, when the UE receives the TA command included in the RAR, it applies the TA command to multiple TRPs (eg, serving TRP).

As a result, TA commands for multiple TRPs can be notified using one RAR.

Any operation shown in TA control 7 may be applied to operations other than notification of the TA command.

<TA control 9>
In TA control 9, in the random access procedure, the timing advance (e.g., TA value) applied to PRACH transmission and the timing advance (e.g., TA value) applied to UL transmission (e.g., PUSCH) after message 3 are set separately. Control.

In the random access procedure, a PRACH transmission request for the second TRP (TRP#2) may be triggered using the other TRP (TRP#1). The PRACH transmission request may be triggered using at least one of higher layer signaling and downlink control information (eg, PDCCH order).

It may be assumed that the UE receives the PRACH response signal (RAR) in the same TRP (eg, TRP#2) as the TRP that performed the PRACH transmission. In this case, the UE may apply the timing advance (eg, TA value) from message 3 onwards based on the TA command contained in the RAR to control the UL transmission timing (see FIGS. 8A and 8B).

For example, the UE applies the TA command included in the RAR transmitted in TRP#2 to the UL transmission (eg, message 3) transmitted in TRP#2. Note that the TA value applied to PRACH transmission and the TA value applied based on the TA command included in the RAR may differ.

In FIG. 8A, when a PRACH transmission request for TRP#2 is received in TRP#1, the UE applies a predetermined TA value and transmits PRACH to TRP#2. The predetermined TA value may be determined based on a TA offset (eg, N _{TA_offset} ) signaled in higher layer parameters. Also, if the TA offset is not signaled in higher layer parameters, a predefined default TA offset may be applied. Note that the TA offset in PRACH transmission may be set in common for a plurality of TRPs (see TA control 1, for example).

When the UE transmits PRACH in TRP#2, it may control to receive RAR for the PRACH in TRP#2. Further, when the UE receives RAR in TRP # 2, the timing of UL transmission in TRP # 2 after message 3 or message 3 based on information on the timing advance included in the RAR (eg, TA command). control (see FIG. 8B). Similarly, the UE may control the UL transmission timing for TRP#1 based on the timing advance information contained in the RAR received for TRP#1.

In this way, by controlling the UL transmission timing based on the information contained in the RAR, it is possible to appropriately control the UL transmission timing after message 3. Further, by applying the TA information included in the RAR to the TRP to which the RAR is transmitted, it is possible to eliminate the need to notify the association between the TA information and the TRP.

(variation)
The following configuration may be applied as appropriate to the above first to third options.

<Operation setting by upper layer>
For UEs that support communication with multiple TRPs, whether to apply single timing advance or multiple timing advance for multiple UL transmissions may be configured in higher layer signaling.

Alternatively, for a UE that supports communication with multiple TRPs, the setting (or support/non-support) of collision-type random access for other TRPs in the same cell (or CC) may be set by higher layer signaling. .

Information about timing advance (eg, TA command) may be set in the UE by higher layer signaling as to whether it applies to one TRP or multiple TRPs.

<Various associations with TRP>
TRP ID (or DMRS port group, codeword (CW), PDCCH configuration (eg, PDCCH-config), PDSCH configuration (PDSCH-config), serving cell configuration (ServingCellConfig), serving cell ID) and a predetermined configuration may be notified to the UE using higher layer signaling or the like. The predetermined configuration may be a PRACH configuration (eg, RACH configuration), an SSB configuration (eg, SSB configuration), a CSI-RS configuration (eg, CSI-RS configuration), a CORESET configuration (eg, CORESET configuration), a PDCCH configuration (eg, PDCCH-configuration), PDSCH configuration (eg, PDSCH configuration), PUCCH configuration (eg, PUCCH-configuration), PUSCH configuration (PUSCH-configuration).

For example, the TRP ID may be notified to the UE for the PRACH configuration (relationship between at least one of SSB and CSI-RS and at least one of PRACH resource and preamble).

Also, information on the correspondence between the TRP ID and the CORESET configuration may be set in the UE using higher layer signaling. Information on the association between TRP IDs and PDCCH configurations may be set in the UE using higher layer signaling.

Thereby, the UE can appropriately grasp the SSB configuration corresponding to each TRP (for example, from which TRP the SSB with a predetermined index is transmitted).

<Transmission method of multiple TRPs and SSB>
This embodiment may be configured such that DL signals (eg, SSB) are transmitted from one or more TRPs to the UE. For example, this embodiment can be applied to at least one of the following configurations 1 to 3.

[Configuration 1]
Multiple TRPs send the same SSBs (eg, SSBs with the same index) to the UE. For example, transmission of SSB#0-#7 is permitted from a plurality of TRPs with different indexes.

[Configuration 2]
Multiple TRPs send different SSBs (eg, SSBs with the same index) to the UE. For example, SSB #0-#3 are transmitted from one of a plurality of TRPs with different indexes (eg, TRP #1), and SSB #4-#7 are transmitted from the other one TRP (eg, TRP #2). sent. That is, different SSBs are transmitted from TRPs with different indexes.

[Configuration 3]
Even if multiple TRPs are supported, SSB transmissions are transmitted only from a predetermined TRP (eg, one TRP). For example, even if the UE supports communication with multiple TRPs (eg, TRP #1 and TRP #2), SSB #0-#7 are transmitted only from a predetermined TRP (eg, TRP #1). be.

(First aspect)
In a first example, an example of TA control when using multiple cells including non-serving cells will be described. The first aspect may be applied in the first to third options above.

In the first to third options, at least one of the multiple TRPs may be a non-serving cell (eg, the first TRP#1 is the serving cell and the second TRP#2 is the non-serving cell).

Also, in the first to third options, multiple non-serving cells (eg, the first TRP#1 and the second TRP#2 are non-serving cells) may be supported. In this case, at least one of options 1-1 to 1-3 below may be applied.

<Option 1-1>
Each non-serving cell may be configured to have a separate TA or maintain a separate TA. For example, setting different TAs (or maintaining different TAs) for multiple non-serving cells may be supported. Alternatively, each non-serving cell may be supported to belong to a separate TA group (eg, TAG).

Thus, by flexibly setting the TA (or TAG) for the non-serving cell, it is possible to flexibly control the UL transmission timing based on the type of the non-serving cell/position with the UE, etc. .

<Option 1-2>
All non-serving cells may maintain the same TA (or the same TA is set) different from the serving cell. Alternatively, each non-serving cell may be configured to belong to the same TA group (eg, TAG). In this way, by setting/maintaining/adjusting TAs by classifying them into serving cells and non-serving cells, it is possible to suppress an increase in the number of TAs to be adjusted by the UE.

<Option 1-3>
Non-serving cells are classified into multiple groups, and the non-serving cells in the group maintain the same TA different from the serving cell (or the same TA is set) may be configured (see FIG. 9). FIG. 9 shows a case where group #1 includes a serving cell, non-serving cell #1, and non-serving cell #2, and group #2 includes non-serving cell #3 and non-serving cell #4.

Non-serving cells within a group may be configured to belong to the same TA group (eg, TAG).

For example, group #1 may belong to the first TAG and group #2 may belong to the second TAG. TAs configured in non-serving cells #1 and #2 included in group #1 and TAs configured in non-serving cells #3 and #4 included in group #2 may be configured separately.

Although the case where the serving cell and the non-serving cell are included in the same group (group #1) is shown here, the present invention is not limited to this. A serving cell and a non-serving cell may be configured not to be included in the same group.

Information about TAGs that non-serving cells support may be notified/configured from the base station to the UE by higher layer signaling/MAC CE/DCI or the like. Alternatively, the UE may make the decision based on the TA corresponding to each non-serving cell. The TA corresponding to the non-serving cell may be determined by the UE based on information contained in the response signal (eg, RAR) sent from the base station to the PRACH transmission based on the PDCCH order.

The number of different TAs (or TAGs) that a UE can maintain/configure in one CC (or cell, between CCs, per FR) may be determined/judged/configured based on UE capabilities. For example, in a CC, a configuration may be adopted in which up to X (eg, X=2) TAs are maintained/configured for serving/non-serving cells. This makes it possible to suppress an increase in the number of TAs configured in a UE in a cell.

(Second aspect)
In a second aspect, an example of notification/configuration of information on non-serving cells will be described. The second aspect may be applied in the first to third options above.

When information (eg, configuration information) regarding one or more non-serving cells is configured/notified to the UE through higher layer signaling, the configuration information may include information regarding random access (eg, PRACH configuration/PRACH parameters). .

For example, system information corresponding to each non-serving cell may be configured/notified to the UE.

Alternatively, for each non-serving cell, a set of dedicated RACH resources, association of RACH resources with synchronization signal blocks (eg, SSB), association of RACH resources with UE-specific CSI-RS configuration, and common Information regarding at least one of the RACH resources may be signaled/configured to the UE. These pieces of information may be set for each physical cell ID (eg, PCI)/C-RNTI.

The UE may acquire/maintain/update the TA of each non-serving cell based on the information about the non-serving cell. For example, the UE may transmit the PRACH using the PRACH configuration corresponding to the non-serving cell and determine/determine the TA of the non-serving cell based on the information contained in the response signal to the PRACH transmission.

<UE capability information>
In the second aspect, the following UE capabilities may be configured. Note that the UE capabilities below may be read as parameters (eg, higher layer parameters) set in the UE from the network (eg, base station).

UE capability information may be defined as to whether or not to support obtaining non-serving cell RACH configuration based on serving cell configuration through higher layer signaling.

UE capability information regarding the number of non-serving cells with RACH configuration (eg, the number the UE can support) may be defined.

UE capability information regarding whether to support configuration of dedicated RACH resources/common RACH resources for non-serving cells may be defined.

UE capability information regarding whether or not to support association between RACH resources of non-serving cells and synchronization signal blocks/association between RACH resources and CSI-RS may be defined.

The second aspect may be configured to apply to UEs that support/report at least one of the UE capabilities described above. Alternatively, the second aspect may be configured to be applied to the UE set from the network.

(Third aspect)
A third aspect describes an example of UE behavior when the network (eg, base station) transmits a PDCCH order requesting PRACH transmission. The third aspect may be applied in the first to third options above.

<Option 3-1>
The UE may determine the cell to which the PDCCH order (or the PRACH that transmits according to the PDCCH order) corresponds based on predetermined parameters used for the PDCCH of the PDCCH order. The predetermined parameter may be, for example, TCI status.

For example, if a base station sends a PDCCH order for PRACH, and the PDCCH (or DCI/CORESET) is associated with the TCI state from the non-serving cell, then the PRACH requested by the PDCCH order corresponds to the non-serving cell. good too. In this case, the UE may control the PRACH transmission based on the non-serving cell's PRACH configuration. The UE may then determine the TA for that non-serving cell based on the DL transmission (eg, RAR) fed back for the PRACH transmission.

If the PDCCH (or DCI/CORESET) is associated with the TCI state from the serving cell, the PRACH requested by the PDCCH order may correspond to the serving cell. In this case, the UE may control the PRACH transmission based on the PRACH configuration of the serving cell. The UE may then determine the TA for that serving cell based on the DL transmission (eg, RAR) fed back for the PRACH transmission.

<Option 3-2>
The UE may determine the cell to which the PDCCH order (or PRACH that transmits according to the PDCCH order) corresponds based on the DCI (or CORESET) used for the PDCCH order.

For example, the DCI used in the PDCCH order may include the identification information of the cell corresponding to the PRACH (eg, cell index/cell type (eg, serving cell/non-serving cell)) and notify the UE. In a given DCI format (eg, DCI format 1_0) used for PDCCH order, X reserved bits of DCI are used for cell notification in order to explicitly indicate serving/non-serving cells corresponding to PRACH. good too. The reserved bits may be reserved bits included in DCI format 1_0 in existing systems (eg, Rel.15/16).

The bit size of X may be set/determined/determined based on the set number of non-serving cells. For example, if one non-serving cell is configured, X may be 1 bit (see FIG. 10A). In this case, '0' may indicate a serving cell and '1' may indicate a non-serving cell. The most significant bit (MSB) or least significant bit (LSB) of the reserved bits may be applied to the field used to notify the cell identification information.

Also, if 3 non-serving cells are configured, X may be 2 bits (see FIG. 10B). To indicate non-serving cells, a re-indexed non-serving cell index may be applied. The association between the cell index and the bit value (or code point) may be defined in the specification, or may be set by higher layer signaling or the like. For example, a code point '0' or '00' indicates the serving cell, and the remaining bits may be associated with the configured non-serving cell index order (eg, ascending/descending order).

Alternatively, the size of X may be fixed and the number of bits may not be changed regardless of the number of non-serving cells configured. In this case, unused bits/fields may be configured as reserved bits.

<Option 3-3>
If the random access preamble index (eg, ra-PreambleIndex) is a predetermined value (eg, 0-63), part of the preamble may be configured/activated by RRC/MAC CE to be associated with non-serving cells. good.

In this case, the serving cell/non-serving cell information may be indicated by a predetermined field of a predetermined DCI format (for example, DCI format 1_0). The predetermined field may be, for example, a random access preamble index field (for example, Random Access Preamble index field). Note that preamble settings related to non-serving cells may be configured to be applied only to PRACH transmission based on PDCCH order (or configured not to be applied to collision-type PRACH transmission).

When DCI indicates a preamble related to a non-serving cell, the UE may control PRACH transmission with the indicated preamble according to the RACH setting of the non-serving cell.

The UE may adjust the TA of one or more indicated cells after PRACH based on the PDCCH order. Information about TAs may be received in response signals (eg, RAR) to PRACH transmissions.

<UE capability information>
In the third aspect, the following UE capabilities may be configured. Note that the UE capabilities below may be read as parameters (eg, higher layer parameters) set in the UE from the network (eg, base station).

UE capability information regarding whether to support PDCCH order for PRACH of non-serving cells may be defined. In this case, UE capability information (eg, the number the UE can support) regarding the number of non-serving cells that support PRACH based on PDCCH order may be defined.

UE capability information regarding whether to support CORESET by PDCCH order (eg CORESET related to TCI state of non-serving cell) may be defined.

UE capability information regarding whether to support non-serving cell based PRACH SSB or non-serving cell based PRACH CSI-RS may be defined.

　UE capability information may be defined as to whether to support extensions of a given DCI format (eg, DCI format 1_0) used for PDCCH orders of non-serving cells. In this case, UE capability information (eg, the number the UE can support) regarding the number of non-serving cells that support PRACH based on PDCCH order may be defined.

UE capability information may be defined as to whether or not to support association of non-serving cells with random access preamble indices (eg, ra-PreambleIndex). In this case, UE capability information (eg, the number that the UE can support) regarding the number of non-serving cells associated with the random access preamble index (eg, ra-PreambleIndex) may be defined.

The third aspect may be configured to apply to UEs that support/report at least one of the UE capabilities described above. Alternatively, the third aspect may be configured to be applied to the UE set from the network.

(variation)
In the first to third aspects, the following UE capabilities may be set. Note that the UE capabilities below may be read as parameters (eg, higher layer parameters) set in the UE from the network (eg, base station).

UE capability information may be defined as to whether arrival of DL data or UL data during RRC connection (eg, RRC_CONNECTED) is supported when the UL synchronization state for non-serving cells is "unsynchronized". If the UL is non-synchronised to the non-serving cell, the UE is supported/allowed to initiate RACH on the non-serving cell and the UE selects PRACH resources based on the non-serving cell's RACH configuration. You may The UL unsynchronized state may be the activated state for DL/UL data transmission.

UE capability information may be defined as to whether UL data arrival during an RRC connection is supported when PUCCH resources for SR are not available in non-serving cells.

UE capability information may be defined as to whether SR failures (eg, SR failure) in non-serving cells are supported.

UE capability information may be defined as to whether to support requests for other system information (eg, SI) for non-serving cells to establish time alignment of secondary TAGs for non-serving cells. UE capability information regarding whether to support beam failure recovery to non-serving cells may be defined to establish time alignment of secondary TAGs of non-serving cells.

(wireless communication system)
A configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this radio communication system, communication is performed using any one of the radio communication methods according to the above embodiments of the present disclosure or a combination thereof.

FIG. 11 is a diagram showing an example of a schematic configuration of a wireless communication system according to one 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), etc. specified by the Third Generation Partnership Project (3GPP). .

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

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.

The wireless communication system 1 has dual connectivity between multiple base stations within the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC) in which both MN and SN are NR base stations (gNB) )) may be supported.

A wireless communication system 1 includes a base station 11 forming a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) arranged in the macrocell C1 and forming a small cell C2 narrower than the macrocell C1. You may prepare. A user terminal 20 may be located within at least one cell. The arrangement, number, etc. of each cell and user terminals 20 are not limited to the embodiment shown in the figure. Hereinafter, the base stations 11 and 12 are collectively referred to as the base station 10 when not distinguished.

The user terminal 20 may connect to at least one of the multiple base stations 10 . The user terminal 20 may utilize at least one of carrier aggregation (CA) using a plurality of component carriers (CC) and dual connectivity (DC).

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

Also, the user terminal 20 may communicate using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.

A plurality of base stations 10 may be connected by wire (for example, an optical fiber conforming to Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (for example, 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 is an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) is an IAB Also called a node.

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

The user terminal 20 may be a terminal compatible with at least one of communication schemes such as LTE, LTE-A, and 5G.

In the radio communication system 1, a radio access scheme based on orthogonal frequency division multiplexing (OFDM) may be used. For example, in at least one of Downlink (DL) and 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.

A radio access method may be called a waveform. Note that in the radio communication system 1, other radio access schemes (for example, other single-carrier transmission schemes and other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

In the radio communication system 1, as downlink channels, 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)) or the like may be used.

In the radio communication system 1, as uplink channels, an uplink shared channel (PUSCH) shared by each user terminal 20, an uplink control channel (PUCCH), a random access channel (Physical Random Access Channel (PRACH)) or the like may be used.

User data, upper layer control information, System Information Block (SIB), etc. are transmitted by the PDSCH. User data, higher layer control information, and the like may be transmitted by PUSCH. Also, a Master Information Block (MIB) may be transmitted by the PBCH.

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

The DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. PDSCH may be replaced with DL data, and PUSCH may be replaced with UL data.

A control resource set (CControl Resource SET (CORESET)) and a search space (search space) may be used for PDCCH detection. CORESET corresponds to a resource searching for DCI. The search space corresponds to the search area and search method of PDCCH candidates. A CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with certain search spaces based on the search space settings.

One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting", etc. in the present disclosure may be read interchangeably.

By PUCCH, channel state information (CSI), acknowledgment information (for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK/NACK, etc.) and scheduling request (Scheduling Request ( SR)) may be transmitted. A random access preamble for connection establishment with a cell may be transmitted by the PRACH.

In addition, in the present disclosure, downlink, uplink, etc. may be expressed without adding "link". Also, various channels may be expressed without adding "Physical" to the head.

In the wireless communication system 1, synchronization signals (SS), downlink reference signals (DL-RS), etc. may be transmitted. In the radio communication system 1, the DL-RS includes a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DeModulation Reference Signal (DMRS)), Positioning Reference Signal (PRS)), Phase Tracking Reference Signal (PTRS)), etc. may be transmitted.

The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called SS/PBCH block, SS Block (SSB), and so on. Note that SS, SSB, etc. may also be referred to as reference signals.

Also, in the radio communication system 1, even if measurement reference signals (SRS), demodulation reference signals (DMRS), etc. are transmitted as uplink reference signals (UL-RS), good. Note that DMRS may also be called a user terminal-specific reference signal (UE-specific reference signal).

(base station)
FIG. 12 is a diagram illustrating an example of the configuration of a base station according to one embodiment. The base station 10 comprises a control section 110 , a transmission/reception section 120 , a transmission/reception antenna 130 and a transmission line interface 140 . One or more of each of the control unit 110, the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission line interface 140 may be provided.

It should be noted that this example mainly shows the functional blocks that characterize the present embodiment, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.

The control unit 110 controls the base station 10 as a whole. The control unit 110 can be configured from a controller, a control circuit, and the like, which are explained based on common recognition in the technical field according to the present disclosure.

The control unit 110 may control signal generation, scheduling (eg, resource allocation, mapping), and the like. The control unit 110 may control transmission/reception, measurement, etc. using the transmission/reception unit 120 , the transmission/reception antenna 130 and the transmission line interface 140 . The control unit 110 may generate data to be transmitted as a signal, control information, a sequence, etc., and transfer them to the transmission/reception unit 120 . The control unit 110 may perform call processing (setup, release, etc.) of communication channels, state management of the base station 10, management of radio resources, and the like.

The transmitting/receiving section 120 may include a baseband section 121 , a radio frequency (RF) section 122 and a measuring section 123 . The baseband section 121 may include a transmission processing section 1211 and a reception processing section 1212 . The transmitting/receiving unit 120 is configured from a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitting/receiving circuit, etc., which are explained based on common recognition in the technical field according to the present disclosure. be able to.

The transmission/reception unit 120 may be configured as an integrated transmission/reception unit, or may be configured from a transmission unit and a reception unit. The transmission section may be composed of the transmission processing section 1211 and the RF section 122 . The receiving section may be composed of a reception processing section 1212 , an RF section 122 and a measurement section 123 .

The transmitting/receiving antenna 130 can be configured from an antenna described based on common recognition in the technical field related to the present disclosure, such as an array antenna.

The transmitting/receiving unit 120 may transmit the above-described downlink channel, synchronization signal, downlink reference signal, and the like. The transmitting/receiving unit 120 may receive the above-described uplink channel, uplink reference signal, and the like.

The transmitting/receiving unit 120 may form at least one of the transmission beam and the reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

The transmission/reception unit 120 (transmission processing unit 1211) performs Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (for example, RLC retransmission control), Medium Access Control (MAC) layer processing (for example, HARQ retransmission control), etc. may be performed to generate a bit string to be transmitted.

The transmission/reception unit 120 (transmission processing unit 1211) performs channel coding (which may include error correction coding), modulation, mapping, filtering, and discrete Fourier transform (DFT) on the bit string to be transmitted. Processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, transmission processing such as digital-to-analog conversion may be performed, and the baseband signal may be output.

The transmitting/receiving unit 120 (RF unit 122) may perform modulation to a radio frequency band, filter processing, amplification, and the like on the baseband signal, and may transmit the radio frequency band signal via the transmitting/receiving antenna 130. .

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

The transmission/reception unit 120 (reception processing unit 1212) performs analog-to-digital conversion, Fast Fourier transform (FFT) processing, and Inverse Discrete Fourier transform (IDFT) processing on the acquired baseband signal. )) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing and PDCP layer processing. User data and the like may be acquired.

The transmitting/receiving unit 120 (measuring unit 123) may measure the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurement, Channel State Information (CSI) measurement, etc. based on the received signal. The measurement unit 123 measures received power (for example, Reference Signal Received Power (RSRP)), reception quality (for example, Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)) , signal strength (for example, Received Signal Strength Indicator (RSSI)), channel information (for example, CSI), and the like may be measured. The measurement result may be output to control section 110 .

The transmission path interface 140 transmits and receives signals (backhaul signaling) to and from devices included in the core network 30, other base stations 10, etc., and user data (user plane data) for the user terminal 20, control plane data, and the like. Data and the like may be obtained, transmitted, and the like.

Note that the transmitter and receiver of the base station 10 in the present disclosure may be configured by at least one of the transmitter/receiver 120, the transmitter/receiver antenna 130, and the transmission line interface 140.

The transmitting/receiving unit 120 may transmit information about the timing advance corresponding to the serving cell and the timing advance corresponding to one or more non-serving cells to the terminal.

The control unit 110 may control reception of UL transmission transmitted from the terminal based on at least one of the timing advance corresponding to the serving cell and the timing advance corresponding to one or more non-serving cells.

The timing advance corresponding to the serving cell and the timing advance corresponding to the non-serving cells, or the timing advances corresponding to different non-serving cells may be set separately.

(user terminal)
FIG. 13 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment; The user terminal 20 includes a control section 210 , a transmission/reception section 220 and a transmission/reception antenna 230 . One or more of each of the control unit 210, the transmitting/receiving unit 220, and the transmitting/receiving antenna 230 may be provided.

It should be noted that this example mainly shows the functional blocks of the features of the present embodiment, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.

The control unit 210 controls the user terminal 20 as a whole. The control unit 210 can be configured from a controller, a control circuit, and the like, which are explained based on common recognition in the technical field according to the present disclosure.

The control unit 210 may control signal generation, mapping, and the like. 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 .

The transmitting/receiving section 220 may include a baseband section 221 , an RF section 222 and a measurement section 223 . The baseband section 221 may include a transmission processing section 2211 and a reception processing section 2212 . The transmitting/receiving unit 220 can be configured from a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitting/receiving circuit, etc., which are explained based on common recognition in the technical field according to the present disclosure.

The transmission/reception unit 220 may be configured as an integrated transmission/reception unit, or may be configured from a transmission unit and a reception unit. The transmission section may be composed of a transmission processing section 2211 and an RF section 222 . The receiving section may include a reception processing section 2212 , an RF section 222 and a measurement section 223 .

The transmitting/receiving antenna 230 can be configured from an antenna described based on common recognition in the technical field related to the present disclosure, such as an array antenna.

The transmitting/receiving unit 220 may receive the above-described downlink channel, synchronization signal, downlink reference signal, and the like. The transmitting/receiving unit 220 may transmit the above-described uplink channel, uplink reference signal, and the like.

The transmitter/receiver 220 may form at least one of the transmission beam and the reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

The transmission/reception unit 220 (transmission processing unit 2211) performs PDCP layer processing, RLC layer processing (for example, RLC retransmission control), MAC layer processing (for example, for data and control information acquired from the control unit 210, for example , HARQ retransmission control), etc., to generate a bit string to be transmitted.

The transmitting/receiving unit 220 (transmission processing unit 2211) performs channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), and IFFT processing on a bit string to be transmitted. , precoding, digital-analog conversion, and other transmission processing may be performed, and the baseband signal may be output.

Whether or not to apply DFT processing may be based on transform precoding settings. Transmitting/receiving unit 220 (transmission processing unit 2211), for a certain channel (for example, PUSCH), if transform precoding is enabled, the above to transmit the channel using the DFT-s-OFDM waveform The DFT process may be performed as the transmission process, or otherwise the DFT process may not be performed as the transmission process.

The transmitting/receiving unit 220 (RF unit 222) may perform modulation to a radio frequency band, filter processing, amplification, and the like on the baseband signal, and may transmit the radio frequency band signal via the transmitting/receiving antenna 230. .

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

The transmission/reception unit 220 (reception processing unit 2212) performs analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (error correction) on the acquired baseband signal. decoding), MAC layer processing, RLC layer processing, PDCP layer processing, and other reception processing may be applied to acquire user data and the like.

The transmitting/receiving section 220 (measuring section 223) may measure the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal. The measuring unit 223 may measure received power (eg, RSRP), received quality (eg, RSRQ, SINR, SNR), signal strength (eg, RSSI), channel information (eg, CSI), and the like. The measurement result may be output to control section 210 .

Note that the transmitter and receiver of the user terminal 20 in the present disclosure may be configured by at least one of the transmitter/receiver 220 and the transmitter/receiver antenna 230 .

The transmitting/receiving unit 220 may perform UL transmission based on at least one of the timing advance corresponding to the serving cell and the timing advance corresponding to one or more non-serving cells.

The control unit 210 may determine the timing advance corresponding to the serving cell and the timing advance corresponding to one or more non-serving cells based on information notified from the base station.

The timing advance corresponding to the serving cell and the timing advance corresponding to the non-serving cell, or timing advances corresponding to different non-serving cells may be set separately.

The information notified from the base station may include information regarding the configuration of random access channels corresponding to non-serving cells.

When receiving a downlink control channel that instructs transmission of the random access channel, the control unit 210 may determine a cell corresponding to the random access channel based on a transmission configuration indicator related to the downlink control channel.

When receiving a downlink control channel instructing transmission of a random access channel, the control unit 210 may determine the cell to which the random access channel corresponds based on the downlink control information transmitted on the downlink control channel.

(Hardware configuration)
It should be noted that the block diagrams used in the description of the above embodiments show blocks in units of functions. These functional blocks (components) are realized by any combination of at least one of hardware and software. Also, the method of implementing each functional block is not particularly limited. That is, each functional block may be realized using one device physically or logically coupled, or directly or indirectly using two or more physically or logically separated devices (e.g. , wired, wireless, etc.) and may be implemented using these multiple devices. A functional block may be implemented by combining software in the one device or the plurality of devices.

where function includes judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, deem , broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. Not limited. For example, a functional block (component) that performs transmission may be called a transmitting unit, a transmitter, or the like. In either case, as described above, the implementation method is not particularly limited.

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. 14 is a diagram illustrating an example of hardware configurations of a base station and a user terminal according to an embodiment. The base station 10 and user terminal 20 described above 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, and the like. .

In the present disclosure, terms such as apparatus, circuit, device, section, and unit can be read interchangeably. The hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured without some devices.

For example, although only one processor 1001 is illustrated, there may be multiple processors. Also, processing may be performed by one processor, or processing may be performed by two or more processors concurrently, serially, or otherwise. Note that processor 1001 may be implemented by one or more chips.

Each function in the base station 10 and the user terminal 20, for example, by loading predetermined software (program) on hardware such as a processor 1001 and a memory 1002, the processor 1001 performs calculations, communication via the communication device 1004 and at least one of reading and writing data in the memory 1002 and the storage 1003 .

The processor 1001, for example, operates an operating system and controls the entire computer. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, and the like. For example, at least part of the above-described control unit 110 (210), transmission/reception unit 120 (220), etc. may be realized by the processor 1001. FIG.

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

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

The storage 1003 is a computer-readable recording medium, for example, a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disk (Compact Disc ROM (CD-ROM), etc.), a digital versatile disk, Blu-ray disc), removable disc, hard disk drive, smart card, flash memory device (e.g., card, stick, key drive), magnetic stripe, database, server, or other suitable storage medium may be configured by Storage 1003 may also be called an auxiliary storage device.

The communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, or the like. The communication device 1004 includes a high-frequency switch, duplexer, filter, frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD), for example. may be configured to include For example, the transmitting/receiving unit 120 (220), the transmitting/receiving antenna 130 (230), and the like described above may be realized by the communication device 1004. FIG. The transmitter/receiver 120 (220) may be physically or logically separated into a transmitter 120a (220a) and a receiver 120b (220b).

The input device 1005 is an input device (for example, keyboard, mouse, microphone, switch, button, sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated (for example, a touch panel).

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 devices.

In addition, the base station 10 and the user terminal 20 include 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. It may be configured including hardware, and a part or all of each functional block may be realized using the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

(Modification)
The terms explained in this disclosure and the terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol and signal (signal or signaling) may be interchanged. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, a pilot signal, etc., depending on the applicable standard. A component carrier (CC) may also be called a cell, a frequency carrier, a carrier frequency, or the like.

A radio frame may consist of one or more periods (frames) in the time domain. Each of the one or more periods (frames) that make up a radio frame may be called a subframe. Furthermore, a subframe may consist of one or more slots in the time domain. A subframe may be a fixed time length (eg, 1 ms) independent of numerology.

Here, a numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. Numerology, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration , a particular filtering process performed by the transceiver in the frequency domain, a particular windowing process performed by the transceiver in the time domain, and/or the like.

A slot may consist of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbol, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) in the time domain. A slot may also be a unit of time based on numerology.

A slot may contain multiple mini-slots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be referred to as a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in time units larger than a minislot may be referred to as PDSCH (PUSCH) Mapping Type A. PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (PUSCH) mapping type B.

Radio frames, subframes, slots, minislots and symbols all represent time units when transmitting signals. Radio frames, subframes, slots, minislots and symbols may be referred to by other corresponding designations. Note that time units such as frames, subframes, slots, minislots, and symbols in the present disclosure may be read interchangeably.

For example, one subframe may be called a TTI, a plurality of consecutive subframes may be called a TTI, and one slot or one minislot may be called a TTI. That is, at least one of the subframe and TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (eg, 1-13 symbols), or a period longer than 1 ms may be Note that the unit representing the TTI may be called a slot, mini-slot, or the like instead of a subframe.

Here, TTI refers to, for example, the minimum scheduling time unit in wireless communication. For example, in the LTE system, a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each user terminal) to each user terminal on a TTI basis. Note that the definition of TTI is not limited to this.

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

When one slot or one minislot is called a TTI, one or more TTIs (that is, one or more slots or one or more minislots) may be the minimum scheduling time unit. Also, the number of slots (the number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.

A TTI having a time length of 1 ms may be called a normal TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, or the like. A TTI that is shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, and the like.

Note that the long TTI (e.g., normal TTI, subframe, etc.) may be replaced with a TTI having a time length exceeding 1 ms, and the short TTI (e.g., shortened TTI, etc.) is less than the TTI length of the long TTI and 1 ms A TTI having the above TTI length may be read instead.

A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers (subcarriers) in the frequency domain. The number of subcarriers included in the RB may be the same regardless of the neumerology, eg twelve. The number of subcarriers included in an RB may be determined based on neumerology.

Also, an RB may contain one or more symbols in the time domain and may be 1 slot, 1 minislot, 1 subframe or 1 TTI long. One TTI, one subframe, etc. may each be configured with one or more resource blocks.

One or more RBs are Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB Also called a pair.

Also, a resource block may be composed of one or more resource elements (Resource Element (RE)). For example, 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.

A Bandwidth Part (BWP) (which may also be called a bandwidth part) represents a subset of contiguous common resource blocks (RBs) for a numerology on a carrier. good too. Here, the common RB may be identified by an RB index based on the common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

BWP may include UL BWP (BWP for UL) and DL BWP (BWP for DL). One or multiple BWPs may be configured for a UE within one carrier.

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

It should be noted that the structures of radio frames, subframes, slots, minislots, symbols, etc. described above are merely examples. For example, the number of subframes contained in a radio frame, the number of slots per subframe or radio frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, the number of Configurations such as the number of subcarriers and the number of symbols in a TTI, symbol length, cyclic prefix (CP) length, etc. can be varied.

In addition, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. may be represented. For example, radio resources may be indicated by a predetermined index.

The names used for parameters and the like in this disclosure are not restrictive names in any respect. Further, the formulas and the like using these parameters may differ from those expressly disclosed in this disclosure. Since the various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, the various names assigned to these various channels and information elements are not limiting names in any way. .

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

Also, information, signals, etc. can 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 and output through multiple network nodes.

Input/output information, signals, etc. may be stored in a specific location (for example, memory), or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated or appended. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to other devices.

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

The physical layer signaling may also be called Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal), L1 control information (L1 control signal), and the like. RRC signaling may also be called an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like. Also, MAC signaling may be notified using, for example, a MAC Control Element (CE).

In addition, notification of predetermined information (for example, notification of “being X”) is not limited to explicit notification, but implicit notification (for example, by not notifying the predetermined information or by providing another information by notice of

The determination may be made by a value (0 or 1) represented by 1 bit, or by a boolean value represented by true or false. , may be performed by numerical comparison (eg, comparison with a predetermined value).

Software, whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise, includes instructions, instruction sets, code, code segments, program code, programs, subprograms, and software modules. , applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like.

In addition, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, the software uses wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) , a server, or other remote source, these wired and/or wireless technologies are included within the definition of transmission media.

The terms "system" and "network" used in this disclosure may be used interchangeably. A “network” may refer to devices (eg, base stations) included in a network.

In the present disclosure, "precoding", "precoder", "weight (precoding weight)", "Quasi-Co-Location (QCL)", "Transmission Configuration Indication state (TCI state)", "spatial "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "number of layers", Terms such as "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angle", "antenna", "antenna element", "panel" are interchangeable. can be used as intended.

In the present disclosure, "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 macrocell, small cell, femtocell, picocell, and the like.

A base station can accommodate one or more (eg, three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area is assigned to a base station subsystem (e.g., a small indoor base station (Remote Radio)). Head (RRH))) may also provide communication services. The terms "cell" or "sector" refer to part or all of the coverage area of at least one of the base stations and base station subsystems that serve communication within such coverage.

In this disclosure, terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", and "terminal" are used interchangeably. can be

Mobile stations include subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals. , a handset, a user agent, a mobile client, a client, or some other suitable term.

At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, or the like. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, or the like. The mobile object may be a vehicle (e.g., car, airplane, etc.), an unmanned mobile object (e.g., drone, self-driving car, etc.), or a robot (manned or unmanned ). Note that at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations. For example, at least one of the base station and mobile station may be an Internet of Things (IoT) device such as a sensor.

Also, the base station in the present disclosure may be read as a user terminal. For example, communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.) Regarding the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, the user terminal 20 may have the functions of the base station 10 described above. Also, words such as "up" and "down" may be replaced with words corresponding to inter-terminal communication (for example, "side"). For example, uplink channels, downlink channels, etc. may be read as side channels.

Similarly, user terminals in the present disclosure may be read as base stations. In this case, the base station 10 may have the functions of the user terminal 20 described above.

In the present disclosure, operations that are assumed to be performed by the base station may be performed by its upper node in some cases. In a network that includes one or more network nodes with a base station, various operations performed for communication with a terminal may involve the base station, one or more network nodes other than the base station (e.g., Clearly, this may be done by a Mobility Management Entity (MME), Serving-Gateway (S-GW), etc. (but not limited to these) or a combination thereof.

Each aspect/embodiment described in the present disclosure may be used alone, may be used in combination, or may be used by switching along with execution. Also, the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in the present disclosure may be rearranged as long as there is no contradiction. For example, the methods described in this disclosure present elements of the various steps using a sample order, and are not limited to the specific order presented.

Each aspect/embodiment described in this disclosure includes Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system ( 4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal number)), Future Radio Access (FRA), New - Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB) , IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth®, or other suitable wireless It may be applied to systems using communication methods, next-generation systems extended based on these, and the like. Also, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

The term "based on" as used in this disclosure does not mean "based only on" unless otherwise specified. In other words, the phrase "based on" means both "based only on" and "based at least on."

Any reference to elements using the "first," "second," etc. designations 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, references to first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

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

Also, "determining (deciding)" includes receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output, access ( accessing (e.g., accessing data in memory), etc.

Also, "determining" is considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. good too. That is, "determining (determining)" may be regarded as "determining (determining)" some action.

Also, "judgment (decision)" may be read as "assuming", "expecting", or "considering".

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

In this disclosure, when two elements are connected, using one or more wires, cables, printed electrical connections, etc., and as some non-limiting and non-exhaustive examples, radio frequency domain, microwave They can be considered to be “connected” or “coupled” together using the domain, electromagnetic energy having wavelengths in the optical (both visible and invisible) domain, and the like.

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 that "A and B are different from C". Terms such as "separate," "coupled," etc. may also be interpreted in the same manner as "different."

Where "include," "including," and variations thereof are used in this disclosure, these terms are inclusive, as is the term "comprising." is intended. Furthermore, the term "or" as used in this disclosure is not intended to be an exclusive OR.

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

Although the invention according to the present disclosure has been described in detail above, it is obvious 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 modifications and changes without departing from the spirit and scope of the invention determined based on the description of the claims. Therefore, the description of the present disclosure is for illustrative purposes and does not impose any limitation on the invention according to the present disclosure.

This application is based on Japanese Patent Application No. 2021-069179 filed on April 15, 2021. All of this content is included here.

Claims (6)

1. A control unit that determines the timing advance corresponding to the serving cell and the timing advance corresponding to one or more non-serving cells based on information notified from the base station;
   A transmitting unit that performs UL transmission based on at least one of the timing advance corresponding to the serving cell and the timing advance corresponding to one or more non-serving cells, respectively;
   A terminal, wherein a timing advance corresponding to the serving cell and a timing advance corresponding to the non-serving cell, or timing advances corresponding to different non-serving cells are set separately.
2. The terminal according to claim 1, characterized in that the information notified from the base station includes information on setting up a random access channel corresponding to a non-serving cell.
3. The control unit, when receiving a downlink control channel instructing transmission of a random access channel, determines a cell corresponding to the random access channel based on a transmission configuration indicator related to the downlink control channel. The terminal according to claim 1, wherein:
4. The control unit, when receiving a downlink control channel instructing transmission of a random access channel, determines a cell to which the random access channel corresponds based on downlink control information transmitted on the downlink control channel. The terminal according to claim 1, wherein:
5. Determining the timing advance corresponding to the serving cell and the timing advance corresponding to one or more non-serving cells based on information notified from the base station;
   performing UL transmission based on at least one of timing advances corresponding to the serving cell and timing advances corresponding to one or more non-serving cells, respectively;
   A wireless communication method for a terminal, wherein a timing advance corresponding to the serving cell and a timing advance corresponding to the non-serving cell, or timing advances corresponding to different non-serving cells are set separately.
6. A transmitting unit that transmits information about timing advances corresponding to a serving cell and timing advances corresponding to one or more non-serving cells to a terminal;
   A control unit that controls reception of UL transmissions transmitted from the terminal based on at least one of the timing advance corresponding to the serving cell and the timing advance corresponding to one or more non-serving cells,
   A base station, wherein a timing advance corresponding to the serving cell and a timing advance corresponding to the non-serving cell, or timing advances corresponding to different non-serving cells are set separately.

Images