WO2024069823A1 - Terminal, wireless communication method, and base station - Google Patents

Abstract

A terminal according to one embodiment of the present disclosure includes: a reception unit that receives a setting for an inter-cell multi-transmission/reception point (TRP), and receives first information relating to a Contention Free Random Access (CFRA) resource corresponding to a first candidate cell and second information relating to a CFRA resource corresponding to a second candidate cell; and a control unit that controls a CFRA procedure in the first candidate cell on the basis of the first information, and controls a CFRA procedure in the second candidate cell on the basis of the second information. According to the one embodiment of the present disclosure, communication can be appropriately performed even when utilizing a plurality of transmission points.

Description

Terminal, wireless communication method and base station

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

Long Term Evolution (LTE) was specified for Universal Mobile Telecommunications System (UMTS) networks with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel. 10-14) was specified for the purpose of achieving higher capacity and greater sophistication over LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later, etc.) are also under consideration.

In future wireless communication systems (e.g., wireless communication systems after Rel. 17/5G), it is expected that communications will be controlled using multiple transmission/reception points (e.g., Multi-TRP (MTRP)) in a serving cell, or communications will be controlled based on inter-cell mobility including non-serving cells.

However, when a terminal (user terminal, User Equipment (UE)) performs UL transmission to multiple transmission/reception points, the issue of how to control the UL transmission (e.g., timing advance control) arises. If the UL transmission to each transmission/reception point is not appropriately controlled, the quality of communications using multiple transmission/reception points may deteriorate.

This disclosure has been made in consideration of these points, and one of its objectives is to provide a terminal, a wireless communication method, and a base station that are capable of communicating appropriately even when communicating using multiple transmission and reception points.

A terminal according to one embodiment of the present disclosure has a receiving unit that receives an inter-cell multi-transmission/reception point (TRP) configuration and receives first information regarding a Contention Free Random Access (CFRA) resource corresponding to a first candidate cell and second information regarding a CFRA resource corresponding to a second candidate cell, and a control unit that controls a CFRA procedure in the first candidate cell based on the first information and controls a CFRA procedure in the second candidate cell based on the second information.

According to one aspect of the present disclosure, communication can be performed appropriately even when multiple transmission points are used for communication.

1A to 1D are diagrams showing an example of a multi-TRP. 2A and 2B are diagrams illustrating an example of inter-cell mobility. FIG. 3 is a diagram showing an example of switching between a serving cell and an additional cell by L1/L2 signaling. FIG. 4 is a diagram showing an example of configuration example 1-3 when a candidate cell is supported. 5A to 5C are diagrams showing an example of switching between candidate cells/candidate cell groups by L1/L2 signaling in configuration examples 1-3 when candidate cells are supported. FIG. 6 is a diagram showing an example of a timing advance group (TAG) to which cells included in a cell group belong. Figure 7 shows an example of a MAC CE for a timing advance command. FIG. 8 is a diagram showing an example of an RRC information element related to option 1-2. FIG. 9 is a diagram showing another example of an RRC information element related to option 1-2. FIG. 10 is a diagram showing an example of RRC information elements related to options 1-3. FIG. 11 is a diagram showing an example of a priority operation of the RACH according to option 2-2. FIG. 12 is a diagram illustrating an example of a UL time synchronization request according to the third embodiment. FIG. 13 is a diagram showing an example of priority operation of the RACH according to option 7-2. FIG. 14 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 15 is a diagram illustrating an example of the configuration of a base station according to an embodiment. FIG. 16 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. FIG. 17 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. FIG. 18 is a diagram illustrating an example of a vehicle according to an embodiment.

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

The TCI state may represent that which applies to the downlink signal/channel. The equivalent of the TCI state which applies to the uplink signal/channel may be expressed as a spatial relation.

TCI state is information about the Quasi-Co-Location (QCL) of signals/channels and may also be called spatial reception parameters, spatial relation information, etc. TCI state may be set in the UE on a per channel or per signal basis.

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

The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be identified based on a spatial QCL. The QCL (or at least one element of the QCL) in this disclosure may be interpreted as sQCL (spatial QCL).

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

The UE's assumption that a Control Resource Set (CORESET), channel or reference signal is in a particular QCL (e.g., QCL type D) relationship with another CORESET, channel or reference signal may be referred to as a QCL assumption.

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

The TCI state may be, for example, information regarding the QCL between the target channel (in other words, the reference signal (RS) for that channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by higher layer signaling, physical layer signaling, or a combination of these.

The channel/signal to which the TCI state is applied may be called a target channel/reference signal (target channel/RS) or simply a target, and the other signal may be called a reference signal (reference RS), source RS, or simply a reference.

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

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

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 referred to as an SS/PBCH block.

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

(Multi-TRP)
In NR, one or more transmission/reception points (TRPs) (multi-TRPs) are considered to perform DL transmission to a UE using one or more panels (multi-panels). It is also considered that a UE performs UL transmission to one or more TRPs.

Note that multiple TRPs may correspond to the same cell identifier (cell identifier (ID)) or different cell IDs. The cell ID may be a physical cell ID (e.g., PCI) or a virtual cell ID.

Figures 1A-1D show examples of multi-TRP scenarios. In these examples, we assume, but are not limited to, that each TRP is capable of transmitting four different beams.

Figure 1A shows an example of a case where only one TRP (TRP1 in this example) of the multi-TRP transmits to the UE (which may be called single mode, single TRP, etc.). In this case, TRP1 transmits both a control signal (PDCCH) and a data signal (PDSCH) to the UE.

In this disclosure, single TRP mode may refer to the mode when multi-TRP (mode) is not set.

Figure 1B shows an example of a case where only one TRP (TRP1 in this example) of the multi-TRP transmits a control signal to the UE, and the multi-TRP transmits a data signal (which may be called a single master mode). The UE receives each PDSCH transmitted from the multi-TRP based on one downlink control information (Downlink Control Information (DCI)).

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

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

When multiple PDSCHs from a multi-TRP such as that shown in FIG. 1B (which may also be called multiple PDSCHs) are scheduled using one DCI, the DCI may be called a single DCI (S-DCI, single PDCCH). Also, when multiple PDSCHs from a multi-TRP such as that shown in FIG. 1D are scheduled using multiple DCIs, these multiple DCIs may be called multiple DCIs (M-DCI, multiple PDCCHs).

Each TRP in a multi-TRP may transmit a different Transport Block (TB)/Code Word (CW)/different layer. Alternatively, each TRP in a multi-TRP may transmit the same TB/CW/layer.

Non-Coherent Joint Transmission (NCJT) is being considered as one form of multi-TRP transmission. In NCJT, for example, TRP1 modulates and maps a first codeword, and transmits a first PDSCH using a first number of layers (e.g., two layers) and a first precoding by layer mapping. TRP2 modulates and maps a second codeword, and transmits a second PDSCH using a second number of layers (e.g., two layers) and a second precoding by layer mapping.

Note that multiple PDSCHs (multi-PDSCHs) that are NCJTed may be defined as partially or completely overlapping with respect to at least one of the time and frequency domains. In other words, the first PDSCH from the first TRP and the second PDSCH from the second TRP may overlap with each other in at least one of the time and frequency resources.

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

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

Such a multi-TRP scenario allows for more flexible transmission control using channels with better quality.

NCJT using multiple TRPs/panels may use high rank. To support ideal and non-ideal backhaul between multiple TRPs, both single DCI (single PDCCH, e.g., FIG. 1B) and multiple DCI (multiple PDCCH, e.g., FIG. 1D) may be supported. For both single DCI and multiple DCI, the maximum number of TRPs may be 2.

For single PDCCH design (mainly for ideal backhaul), TCI extension is being considered. Each TCI code point in the DCI may correspond to TCI state 1 or 2. The TCI field size may be the same as that of Rel. 15.

For PDCCH/CORESET as specified in Rel. 15, one TCI state without CORESETPoolIndex (also called TRP Info) is set for one CORESET.

With regard to the enhancement of PDCCH/CORESET specified in Rel. 16, in the case of multi-TRP based on multi-DCI, a CORESET pool index is set for each CORESET.

(Inter-cell mobility)
In NR, it is considered that one or more transmission/reception points (TRPs) (multi-TRPs (MTRPs)) perform DL transmission to a UE. It is also considered that a UE performs UL transmission to one or more TRPs.

In inter-cell mobility (e.g., L1/L2 inter cell mobility), a UE may receive channels/signals from multiple cells/TRPs (see Figures 2A and 2B).

Figure 2A shows an example of inter-cell mobility (e.g., Single-TRP inter-cell mobility) including non-serving cells. The UE may be configured with one TRP (or single TRP) in each cell. 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). For example, this corresponds to a case where the UE switches/switches from cell #1 to cell #3 (e.g., fast cell switch). The TRP of the serving cell may be called a primary TRP (e.g., pTRP). The TRP of the non-serving cell may be called an additional TRP (aTRP).

In this case, the selection of the port (e.g., antenna port)/TRP may be performed dynamically. The selection of the port (e.g., antenna port)/TRP may be performed based on the TCI state indicated or updated by the DCI/MAC CE. Here, a case is shown in which different physical cell ID (e.g., PCI) settings are supported for cell #1 and cell #3.

Figure 2B shows an example of a multi-TRP scenario (e.g., multi-TRP inter-cell mobility when using multi-TRP). The UE may be configured with multiple (e.g., two) TRPs (or different CORESET pool indices) in each cell. Here, the UE receives channels/signals from TRP#1 and TRP2. Also, here, the UE receives channels/signals from TRP#1 and TRP#2. TRP#1 corresponds to physical cell ID (PCI)#1, and TRP#2 corresponds to PCI#2.

The multi-TRP (TRP #1, #2) may be connected by an ideal/non-ideal backhaul to exchange information, data, etc. Each TRP of the multi-TRP may transmit the same or different code words (CWs) and the same or different layers. As a form of multi-TRP transmission, non-coherent joint transmission (NCJT) may be used as shown in Figure 2B. Here, the case where NCJT is performed between TPRs corresponding to different PCIs is shown. The same serving cell setting may be applied/set for TRP #1 and TRP #2.

The multiple PDSCHs (multi-PDSCHs) that are NCJTed 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 in at least one of the time and frequency resources. The first PDSCH and the second PDSCH may be used to transmit the same TB or different TBs.

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

Multiple PDSCHs from a multi-TRP (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 a multi-TRP may be referred to as single DCI-based multi-TRP (mTRP/MTRP).

Multiple PDSCHs from a multi-TRP may be scheduled using multiple DCIs (multiple DCI (M-DCI), multiple PDCCHs) respectively (multiple master mode). Multiple DCIs may be transmitted respectively from a multi-TRP. A configuration that utilizes multiple DCIs in a multi-TRP may be called a multi-DCI-based multi-TRP (mTRP/MTRP).

It may be assumed that the UE transmits separate CSI reports (CSI reports) for different TRPs. Such CSI feedback may be referred to as separate feedback, separate CSI feedback, etc. In this disclosure, "separate" may be interchangeably read as "independent."

In Rel. 17 NR, it is assumed that the MAC CE/DCI will support beam direction to a TCI state associated with a different PCI. On the other hand, in Rel. 18 NR and later, it is assumed that L1/L2 signaling (e.g., DCI/MAC CE) will support serving cell switching (e.g., instructing a change of serving cell to a cell with a different PCI) (see Figure 3).

Figure 3 shows a case where the UE switches cells from a serving cell to an additional cell (also called a candidate cell or target cell) based on a cell switching instruction from the base station.

(Candidate cell)
In inter-cell mobility, it is also assumed that one or more candidate cells are configured/managed for each serving cell.

For example, in a given higher layer parameter (e.g., ServingCellConfig), one or more candidate cells with limited information (e.g., only some parameters are notified to the UE) may be configured (Alt. 1). They may be configured in the same way as the inter-cell beam management (inter-cell BM) of existing systems (e.g., Rel. 17).

Alternatively, a complete configuration (e.g., ServingCellConfig) of one or more candidate cells may be configured and associated with each serving cell (Alt. 2). For example, a carrier aggregation configuration framework (e.g., CA configuration framework) or a Conditional Handover (CHO)/Conditional PSCell Change (CPC) configuration framework may be reused.

In Alt. 1/2, activation/deactivation of candidate cells may be controlled by MAC CE/DCI.

At least one of the following configuration examples 1 to 3 may be applied as the configuration of candidate cells (see Figure 4). Here, SpCell#0, SCell#1, and SCell#2 are configured as serving cells, and an example of the configuration/association of candidate cells (or additional cells) to serving cells/cell groups is shown. The following configuration examples 1 to 3 are merely examples, and the number of cells, the association of each cell, etc. are not limited to these and may be changed as appropriate. Alternatively, other configuration examples may be supported/applied in addition to/instead of configuration examples 1 to 3.

In configuration example 1, one or more candidate cells are associated/configured with each serving cell (see Figure 4). Specifically, candidate cells #0-1, #0-2, and #0-3 are associated with SpCell #0, candidate cell #1-1 is associated with SCell #1, and candidate cells #2-1 and #2-2 are associated with SCell #2. Information regarding the associations may be configured/instructed to the UE by the base station via RRC/MAC CE/DCI.

In configuration example 2, a candidate cell is associated/configured with a MAC entity/MCG/SCG (see Figure 4). Specifically, a case where candidate cells #3-#8 are associated with a MAC entity/MCG/SCG is shown. In this case, candidate cells are not associated with each serving cell, but are configured with a MAC entity or a cell group (e.g., MCG/SCG). Information regarding the candidate cell configured for each cell may be configured/instructed to the UE by the base station via RRC/MAC CE/DCI.

In configuration example 3, one or more candidate cell groups may be configured (see FIG. 4). Specifically, a case is shown in which candidate cell group #1 having candidate cells #0-#2, candidate cell group #2 having candidate cells #0 and #1, and candidate cell group #3 having candidate cell #0 are configured. A candidate cell group has one or more candidate cells. A candidate cell included in a candidate cell group may be associated with at least one of the serving cells. Information regarding the candidate cells may be configured/instructed to the UE by the base station via RRC/MAC CE/DCI.

In existing systems (e.g., Rel. 17), L1 beam indication (e.g., indication via the TCI status field of the DCI) to the TCI status associated with an additional PCI (or additional cell) is supported.

In Rel. 18 and later, it is assumed that new L1/L2 signals (e.g., DCI/MAC CE) that indicate a serving cell switch will be supported. At least one of an implicit indication and an explicit indication is assumed to be supported. An implicit indication may mean, for example, that a CORESET is updated by the MAC CE to a TCI state associated with an additional PCI. An explicit indication may mean that the cell switch is directly indicated by the DCI/MAC CE.

For example, in candidate cell configuration example 1, a specific candidate cell may be designated as a serving cell (or switching with the serving cell may be instructed) via L1/L2 signaling. Figure 5A shows a case where candidate cell #0-2 becomes an SpCell of the MCG/SCG (SpCell #0 and candidate cell #0-2 are switched) via L1/L2 signaling. It also shows a case where candidate cell #2-1 becomes an SCell of the MCG/SCG (SCell #2 and candidate cell #2-1 are switched) via L1/L2 signaling.

Alternatively, in candidate cell setting example 2, a specific candidate cell may be designated as a serving cell (or switching to the serving cell may be instructed) via L1/L2 signaling. Figure 5B shows a case where candidate cell #4 becomes the SpCell of the MCG/SCG (SpCell #0 and candidate cell #4 are switched) via L1/L2 signaling.

Alternatively, in candidate cell setting example 3, a specific candidate cell group (or one or more candidate cells included in the specific candidate cell group) may be changed/updated to a serving cell group via L1/L2 signaling. FIG. 5C shows a case where candidate cell group #1 (or candidate cells #0-#2 included in candidate cell group #1) becomes the serving cell group (the serving cell group and candidate cell group #1 are switched) via L1/L2 signaling.

(Timing Advance Group)
When multiple TRPs are used, the distance between the UE and each TRP may be different. The multiple TRPs may be included in the same cell (e.g., a serving cell). Alternatively, one TRP among the multiple TRPs may correspond to a serving cell and the other TRPs may correspond to a non-serving cell. In this case, it is also assumed that the distance between each TRP and the UE may be different.

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

The UE may control the timing of UL transmission by applying a timing advance (multiple timing advances) for each pre-configured timing advance group (TAG: Timing Advance Group).

When multiple timing advance is applied, Timing Advance Groups (TAGs) classified by transmission timing are supported. The UE may control the UL transmission timing for each TAG, assuming that the same TA offset (or TA value) is applied to each TAG. In other words, the TA offset may be set independently for each TAG.

When multiple timing advance is applied, the UE can independently adjust the transmission timing of cells belonging to each TAG, allowing the radio base station to align the timing of receiving uplink signals from the UE even when multiple cells are used.

TAGs (e.g., serving cells belonging to the same TAG) may be configured by higher layer parameters. The same timing advance value may be applied to serving cells belonging to the same TAG. The timing advance group that includes the SpCell of a MAC entity may be called the Primary Timing Advance Group (PTAG), and other TAGs may be called Secondary Timing Advance Groups (STAGs).

In existing systems (e.g., Rel. 16 NR), the configuration of up to four TAGs per cell group (e.g., MCG/SCG) is supported (see Figure 6). Figure 6 shows a case where three TAGs are configured for a cell group including SpCell and SCell#1 to #4. Here, the case is shown where SpCell and SCell#1 belong to the first TAG (PTAG or TAG#0), SCell#2 and SCell#3 belong to the second TAG (TAG#1), and SCell#4 belongs to the third TAG (TAG#2).

The timing advance command (TA command) may be notified to the UE using a MAC control element (e.g., MAC CE). The TA command is a command indicating the transmission timing value of the uplink channel and is included in the MAC control element. The TA command is signaled from the radio base station to the UE at the MAC layer. The UE controls a predetermined timer (e.g., TA timer) based on the reception of the TA command.

The MAC CE for the timing advance command (TAC MAC CE) may include a field for a timing advance group index (e.g., TAG ID) and a field for the timing advance command (see Figure 7).

On the other hand, in future wireless communication systems, it is expected that different TAGs (or TAG-IDs) will be set for one or more TRPs corresponding to a certain cell (or CC). It is also expected that different TRPs corresponding to a certain cell will share a common TAG. It is also expected that a MAC CE for a TA command will be applied to only one TRP, or that a MAC CE for a TA command will be applied to multiple TRPs.

Alternatively, cases are also envisaged where TRPs corresponding to different cells use different TAGs/share a common TAG. For example, in inter-cell mobility, it is also envisaged to control UL transmission based on a common/different timing advance for a serving cell (or a TRP of a serving cell) and a non-serving cell (or a TRP of a non-serving cell).

In this way, in MIMO from Rel. 18 onwards, it is expected that in multi-TRP operation using multi-DCI, two timing advances (TAs) for two TRPs will be supported.

If TAGs are configured/controlled on a per-TRP basis, a time alignment timer (e.g., timeAlignmentTimer) may be configured for each TRP. The time alignment timer may control the time at which the MAC entity considers a serving cell belonging to the associated TAG to be uplink time aligned. For example, the time alignment timer may be configured by the RRC to maintain UL time alignment.

A time alignment timer (e.g., timeAlignementTimer) may be maintained for UL time alignment. In Rel. 17, the time alignment timer (e.g., timeAlignementTimer) is per TAG. When the UE receives a MAC CE (e.g., TAC MAC CE) for a timing advance command, it starts or restarts the time alignment timer associated with the indicated timing advance group (e.g., TAG), respectively.

The MAC entity receives the TAC MAC CE and applies a timing advance command for the indicated TAG or starts or restarts a time alignment timer associated with the indicated TAG if a predefined value (N _TA ) is maintained between the indicated TAG, which may be the timing _advance between DL and UL.

The behavior when the time alignment timer expires may be defined separately for the PTAG and the STAG. Note that the timing advance group (TAG) that includes the SpCell of the MAC entity may be called the primary timing advance group (PTAG), and the other TAGs may be called secondary timing advance groups (STAGs).

For example, Rel. 17 supports the application of a specific PTAG operation when a timing advance timer corresponding to a PTAG expires, and the application of a specific STAG operation when a timing advance timer corresponding to a STAG expires.

For example, when the time alignment timer expires, the following operations (e.g., a specified PTAG operation/a specified STAG operation) may be performed.

[Predetermined PTAG Operation]
If a time alignment timer is associated with the PTAG,
Flushes (discards) all HARQ buffers of all serving cells.
- If configured, inform RRC to release PUCCH for all serving cells.
- If set, notify RRC to release SRS.
Clear all configured DL allocations and configured UL allocations.
Clear the PUSCH resources for semi-persistent CSI reporting.
- Allow all time alignment timers to expire while running.
- Maintain _NTAs for all TAGs.

[Predetermined STAG Actions]
If a time alignment timer is associated with a STAG, then for all serving cells belonging to that STAG:
Flush (discard) all HARQ buffers.
- If configured, notify RRC to release PUCCH.
- If set, notify RRC to release SRS.
Clear all configured DL and UL allocations.
Clear the PUSCH resources for semi-persistent CSI reporting.
- Maintain the _NTA of the TAG.

(TA control for each TRP/panel)
As described above, when communication is performed using multiple transmission/reception points (e.g., TRPs)/panels, it is also possible to control the timing advance (TA) for each TRP/panel.

In NR Rel. 18 and later, for RACH triggered by a PDCCH order and RACH triggered by a UE, contention-based random access (CBRA)) and contention-free random access (CFRA)) are considered/determined on a TRP or TRP TA (TA per TRP) basis.

If application/setting of timing advance per TRP (or on a TRP-by-TRP basis) is supported, the UE controls UL transmission in each TRP based on the timing advance corresponding to each TRP (or the timing advance group to which each TRP belongs).

Information regarding the TRP corresponding to each serving cell (e.g., TRP index/TRP ID) may be set/instructed to the UE from the base station using RRC/MAC CE/downlink control information. The UE may receive related information regarding the timing advance corresponding to each TRP (e.g., information regarding the TA value/timing advance command/time alignment timer, etc.) from the base station.

Each embodiment of the present disclosure may be applied to at least one of intra-cell multi-TRP (Intra-cell M-TRP) and inter-cell multi-TRP (Inter-cell M-TRP).

In intra-cell multi-TRP, multiple TRPs (or the activated TCI states of multiple TRPs) may be associated with the same cell ID. The cell ID may be a physical cell ID (PCI).

In inter-cell multi-TRP, multiple TRPs (or activated TCI states of multiple TRPs) may be associated with different cell IDs (e.g., PCIs). For example, in inter-cell multi-TRP, two TRPs may be interpreted as two TRPs associated with two PCIs, respectively.

If per-TRP (or per-TRP) timing advance application/setting is supported, each TRP may belong to a different TAG. Multiple TRPs (e.g., two TRPs) of a serving cell may belong to two TAGs each. A TAG may contain multiple TRPs from multiple serving cells. All TRPs/serving cells in a TAG apply/maintain the same timing advance (TA)/same time alignment timer.

In the present disclosure, a TAG may include one or more sub-TAGs. For example, two TRPs of a serving cell may belong to two sub-TAGs each and one TAG. A sub-TAG may include multiple TRPs from multiple serving cells. All TRPs/serving cells in a sub-TAG apply/maintain the same timing advance (TA)/same time alignment timer.

For example, a TA may be applied for each TRP (or an instruction may be given on a TRP TA basis). For example, at least one of the following options may be applied:

[Option 1]
A different TAG-ID may be set for each TRP, and a different MAC CE for TA command may be set for each TRP. Each TAG may maintain a time alignment timer for UL time alignment.

[Option 2]
Different TRPs may share a TAG. A MAC CE for a TA command may only apply to one TRP. The UE applies different TAs to other TRPs. For example, the UE may adjust the TA value for other TRPs (e.g., TRP#1) by a TA offset (TA_TRP_offset) based on the TA for TRP#0 (TA_TRP#0).

In this case, there may be only one time alignment timer for UL time alignment of multiple TRPs. This may mean that UL time alignment of multiple TRPs is maintained or lost simultaneously.

[Option 3]
There may be only one TAG. The MAC CE for the TA command may apply to multiple serving TRPs for the UE.

[Option 4]
There may be one TAG. MAC CEs for TA commands received on a TRP/CW/PDSCH/DMRS port group may apply to the same TRP/CW/PDSCH/DMRS port group of the TAG. Each TRP/CW/PDSCH/DMRS port group of the TAG maintains a time alignment timer for UL time alignment.

In this way, in Rel. 18 and later, it is expected that multiple timing advances will be supported in a multi-TRP (e.g., a multi-TRP using multiple DCI). For example, multiple (e.g., two) timing advances may be supported for a multi-TRP (e.g., two TRPs) using multiple DCI. In addition, the application of multiple timing advances to a multi-TRP may be supported in intra-cell/inter-cell multi-DCI multi-TRP scenarios, and may be supported in multiple frequency ranges (e.g., FR1 and FR2).

However, there are cases where the RACH procedure for each TRP (TRP TA) in a multi-TRP as described above has not been sufficiently considered.

For example, in the case of CFRA, there has been insufficient consideration given to the method of setting/determining RACH resources for each TRP.

In addition, in the existing RACH procedure, at any given time in the MAC entity, there is only one RACH procedure in progress. If the UE is triggered to perform multiple (e.g., two) RACH procedures, it is up to the UE implementation to decide how to handle this. In other words, there has been insufficient consideration given to the behavior when multiple (e.g., two) RACH procedures are triggered for multiple (e.g., two) TRPs.

Also, if the UE wants to establish time alignment for one TRP of a cell, or if the UE determines that it is "asynchronous" for one TRP of a cell, the UE may trigger a RACH procedure for that one TRP.

Considering that other TRPs of the cell are synchronized, it is conceivable that the UE may request TRP synchronization for the other TRPs via other UL signals (e.g., Scheduling Request (SR)/MAC CE).

However, there has been insufficient consideration given to the operation related to the TRP synchronization requirements.

Furthermore, if application/setting of timing advance on a per-TRP basis is supported, there is insufficient consideration given to how to control the application of timing advance commands indicated in a given MAC CE (e.g., MAC RAR).

Furthermore, in the case of multiple (e.g., two) TRPs in one cell belonging to multiple (e.g., two) TAGs, it is thought that the operation of the existing system will need to be extended, but this has not been sufficiently considered.

In addition, there has been insufficient consideration given to introducing a RACH procedure for each TRP in inter-cell mobility.

If the above considerations are insufficient, the quality of communications using multiple TRPs may deteriorate, which may hinder improvements in communications throughput.

The inventors therefore came up with a method to solve the above problem.

Below, embodiments of the present disclosure will be described in detail with reference to the drawings. The wireless communication methods according to the embodiments may be applied independently or in combination.

In this disclosure, "A/B" and "at least one of A and B" may be interpreted as interchangeable. Also, in this disclosure, "A/B/C" may mean "at least one of A, B, and C."

In this disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be read as interchangeable. In this disclosure, terms such as support, control, capable of control, operate, and capable of operating may be read as interchangeable.

In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In this disclosure, Medium Access Control (MAC Control Element (CE)), update commands, activation/deactivation commands, etc. may be interchangeable.

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

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

In the present disclosure, the physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), etc.

In this disclosure, the terms index, identifier (ID), indicator, resource ID, etc. may be interchangeable. In this disclosure, the terms sequence, list, set, group, cluster, subset, etc. may be interchangeable.

In this disclosure, the terms panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission/Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS Resource Indicator (SRI), Control Resource Set (CONTROLLER RESOLUTION SET (CORESET)), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), Antenna Port (e.g., DeModulation Reference Signal (DMRS)) port), Antenna Port group (e.g., DMRS port group), group (e.g., spatial relationship group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, quasi-co-location (QCL), QCL assumption, etc. may be read as interchangeable.

Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be read as interchangeable. "Spatial relationship information" may be read as "set of spatial relationship information", "one or more pieces of spatial relationship information", etc. TCI state and TCI may be read as interchangeable.

In this disclosure, TRP, CORESET pool index (CORESETPoolIndex), TRP ID, ID related to TRP, TAG ID, TCI state group, spatial relationship group, QCL source RS group, DL RS group, path loss RS group, PCI (for inter-cell multi-TRP) may be read as interchangeable.

In the present disclosure, being associated with different TRPs, being associated with different CORESET pool indices (CORESETPoolIndex), being associated with different TRP IDs, being associated with different IDs related to TRPs, being associated with different TAG IDs, being associated with different TCI state groups, being associated with different spatial relationship groups, being associated with different QCL source RS groups, being associated with different DL RS groups, being associated with different path loss RS groups, being associated with different PCIs (for inter-cell multi-TRP) may be read as interchangeable.

Each embodiment of the present disclosure may be applied to at least one of intra-cell multi-TRP and inter-cell multi-TRP.

In this disclosure, intra-cell multi-TRP may mean that the activated TCI states of multiple (e.g., two) TRPs are associated with the same PCI.

In this disclosure, inter-cell multi-TRP may mean that the activated TCI states of multiple (e.g., two) TRPs are associated with different PCIs.

In the present disclosure, in the case of inter-cell multi-TRP, multiple (e.g., two) TRPs may mean multiple (e.g., two) TRPs associated with multiple (e.g., two) PCIs.

(Wireless communication method)
First Embodiment
In the case of CFRA, there has been insufficient consideration given to the method of setting/determining RACH resources for each TRP.

In existing systems (up to Rel. 17), CFRA resources are provided in the RACH configuration (rach-ConfigDedicated).

If the CFRA resources associated with the SSB are explicitly provided in the RACH configuration (rach-ConfigDedicated) and at least one associated SSB is available whose RSRP (SS-RSRP) exceeds a certain threshold (rsrp-ThresholdSSB), the UE selects one SSB whose SS-RSRP exceeds a certain threshold (rsrp-ThresholdSSB).

The UE then sets a random access preamble index (ra-PreambleIndex) corresponding to the selected SSB.

Furthermore, if the CFRA resource associated with the CSI-RS is explicitly provided in the RACH configuration (rach-ConfigDedicated) and at least one CSI-RS is available among the associated CSI-RSs whose RSRP (CSI-RSRP) exceeds a certain threshold (rsrp-ThresholdCSI-RS), the UE selects one CSI-RS whose CSI-RSRP exceeds a certain threshold (rsrp-ThresholdCSI-RS).

The UE then sets a random access preamble index (ra-PreambleIndex) corresponding to the selected CSI-RS.

In the first embodiment, the method for setting/determining RACH resources for each TRP will be described below.

The UE may receive information regarding the RACH resources corresponding to each TRP. The UE may then control the RACH procedure in each TRP based on the information.

The UE may determine one or more RACH resources according to certain rules/conditions.

The RACH resource may be a RACH resource in a CFRA for each TRP. In this disclosure, the RACH resource in a CFRA may be referred to as a CFRA resource.

The particular rule/condition may be at least one of options 1-1 to 1-3 below.

<<Option 1-1>>
For the UE, one (common) set (parameters) of CFRA resources may be configured in the RACH configuration (e.g., rach-ConfigDedicated).

The one (common) set may be, for example, at least one of a parameter indicating an SSB resource list (e.g., ssb-ResourceList), a parameter indicating a PRACH mask index for random access (RA) resource selection (e.g., ra-ssb-OccasionMaskIndex), a parameter indicating a CSI-RS resource list (e.g., csi-rs-ResourceList), and a parameter indicating a threshold for CSI-RS (e.g., rsrp-ThresholdCSI-RS).

Each index related to the TRP may be associated with at least one of an SSB, a CSI-RS, a random access preamble index (e.g., ra-PreambleIndex), and a PRACH occasion.

[Option 1-1-1]
For a CFRA triggered by a PDCCH (or a PDCCH order), the index for the TRP may be indicated by the PDCCH, or the index for the TRP may be associated with the CORESET/TCI state of the PDCCH.

The RA resource may be determined based on the SSB/CSI-RS/ra-PreambleIndex/PRACH occasion associated with the index related to the TRP (or may be selected from among the SSB/CSI-RS/ra-PreambleIndex/PRACH occasion). The index related to the TRP may be indicated by the PDCCH or may be an index related to the TRP associated with the PDCCH.

The method for selecting random access resources from SSB/CSI-RS/ra-PreambleIndex/PRACH occasions may be the same as the rules in existing systems (e.g., Rel. 17 and earlier).

[Option 1-1-2]
For a CFRA triggered by a particular event/condition, the random access resource may be determined based on (or selected from) the SSB/CSI-RS/ra-PreambleIndex/PRACH occasion associated with the TRP.

The method for selecting random access resources from SSB/CSI-RS/ra-PreambleIndex/PRACH occasions may be the same as the rules in existing systems (e.g., Rel. 17 and earlier).

<<Option 1-2>>
A UE may be configured with multiple (e.g., two) sets (parameters) of CFRA resources in a RACH configuration (e.g., rach-ConfigDedicated) for multiple (e.g., two) TRPs. In other words, a UE may be configured with parameters related to CFRA resources for a first TRP and parameters related to CFRA resources for a second TRP separately.

The set may be, for example, at least one of a parameter indicating an SSB resource list (e.g., ssb-ResourceList), a parameter indicating a PRACH mask index for random access (RA) resource selection (e.g., ra-ssb-OccasionMaskIndex), a parameter indicating a CSI-RS resource list (e.g., csi-rs-ResourceList), and a parameter indicating a threshold for CSI-RS (e.g., rsrp-ThresholdCSI-RS).

For each TRP, the UE may be configured with at least one of the following parameters: a parameter indicating an SSB resource list (e.g., ssb-ResourceList), a parameter indicating a PRACH mask index for random access (RA) resource selection (e.g., ra-ssb-OccasionMaskIndex), a parameter indicating a CSI-RS resource list (e.g., csi-rs-ResourceList), and a parameter indicating a threshold for CSI-RS (e.g., rsrp-ThresholdCSI-RS).

Figure 8 is a diagram showing an example of an RRC information element related to option 1-2. In the example shown in Figure 8, CFRA resources are set separately for the first TRP and the second TRP. Note that Figure 8 is written using Abstract Syntax Notation One (ASN.1) notation (this is merely an example).

In the example shown in FIG. 8, the parameters included in the SSB-related parameters (ssb) and CSI-RS-related parameters (csi-rs) in the parameters (resources) indicating the resources of the CFRA include parameters for the first TRP and parameters for the second TRP.

Specifically, FIG. 8 shows ssb-ResourceList, ra-ssb-OccasionMaskIndex, csi-rs-ResourceList, and rsrp-ThresholdCSI-RS as parameters for the first TRP. FIG. 8 also shows ssb-ResourceList-for TRP2-r18, ra-ssb-OccasionMaskIndex-for TRP2-r18, csi-rs-ResourceList-for TRP2-r18, and rsrp-ThresholdCSI-RS-for TRP2-r18 as parameters for the second TRP.

The UE determines the CFRA resource for the first TRP based on the parameters for the first TRP, and determines the CFRA resource for the second TRP based on the parameters for the second TRP.

Note that the parameter names shown in Figure 8 are merely examples and are not limited to these.

Figure 9 is a diagram showing another example of RRC information elements related to option 1-2. In the example shown in Figure 9, similar to Figure 8 above, an example is shown in which CFRA resources are set separately for the first TRP and the second TRP. Note that Figure 9 is written using Abstract Syntax Notation One (ASN.1) notation (this is merely one example).

In the example shown in FIG. 9, parameters (resources) indicating the resources of the CFRA are specified for the first TRP and parameters for the second TRP.

Specifically, in FIG. 9, resources is shown as a parameter for the first TRP, and resources-for TRP2-r18 is shown as a parameter for the second TRP.

Note that the parameter names shown in Figure 9 are merely examples and are not limited to these.

The UE determines the CFRA resource for the first TRP based on the parameters for the first TRP, and determines the CFRA resource for the second TRP based on the parameters for the second TRP.

<Option 1-3>
For a UE, multiple sets (parameters) of CFRA resources may be configured in the RACH configuration (e.g., rach-ConfigDedicated) for multiple PCIs.

Parameters related to CFRA may be set for each PCI. The PCI may be, for example, at least one of the PCI of the serving cell and the PCI of a non-serving cell (additional PCI).

The CFRA-related parameters may be any parameters included in the CFRA parameters in the RACH configuration (e.g., rach-ConfigDedicated). The CFRA-related parameters may be, for example, at least one (or all) of a parameter indicating an RA opportunity for the CFRA (e.g., occasions), a parameter indicating a setting of a random access opportunity for the CFRA (e.g., rach-ConfigGeneric), a parameter indicating the number of SSBs per RACH opportunity (e.g., ssb-perRACH-Occasion), a parameter indicating a resource for the CFRA (e.g., resources), a parameter indicating an SSB resource list (e.g., ssb-ResourceList), a parameter indicating a PRACH mask index for RA resource selection (e.g., ra-ssb-OccasionMaskIndex), a parameter indicating a CSI-RS resource list (e.g., csi-rs-ResourceList), and a parameter indicating a threshold for the CSI-RS (e.g., rsrp-ThresholdCSI-RS).

Options 1-3 may be applied to inter-cell multi-TRP (inter-cell M-TRP). Options 1-3 may also be applied in mobility (specified in Rel. 18).

In inter-cell M-TRP (specified in Rel. 17), up to seven additional PCIs are configured and the TCI state of different PCIs can be changed in the MAC CE. For this reason, it is desirable to be able to configure the RACH of multiple (e.g., all) PCIs through RRC signaling.

Figure 10 is a diagram showing an example of RRC information elements related to options 1-3. In the example shown in Figure 10, CFRA resources are set separately for each PCI. Note that Figure 10 is written using Abstract Syntax Notation One (ASN.1) notation (this is merely an example).

In the example shown in FIG. 10, a CFRA-related parameter (CFRA) corresponding to the PCI of the serving cell, a CFRA-related parameter (CFRA-for non serving cell 1-r18) corresponding to the PCI of the first non serving cell, and a CFRA-related parameter (CFRA-for non serving cell N-r18) corresponding to the PCI of the Nth non serving cell (N is any integer) are shown. Each of these parameters may include at least one (or all) of the above-mentioned CFRA-related parameters.

The UE may determine the CFRA resources based on the RACH settings corresponding to the PCI.

Note that the names of the parameters shown in FIG. 10 are merely examples and are not limited to these. Also, FIG. 10 shows a parameter (CFRA-for non serving cell N-r18) related to the CFRA corresponding to the PCI of the Nth (N is any integer) non serving cell as an example, but parameters related to the CFRA corresponding to the PCI of the second, third, ... non serving cells may be specified.

In the first embodiment, a CFRA may be triggered for one TRP. A CFRA may be triggered for one TRP, which may mean, for example, that one TRP of a serving cell is in a "non-synchronized" state and/or that a CFRA is triggered to establish time alignment for one TRP of a serving cell.

When a CFRA is triggered for a TRP, the UE may select/determine the random access resource from among the SSB/CSI-RS/ra-PreambleIndex/PRACH Occasion associated with that TRP and provided in the RACH configuration (e.g., rach-ConfigDedicated).

In the present disclosure, a TRP being "asynchronous" may mean that a time alignment timer associated with the TRP (e.g., a timeAlignmentTimer, or a timeAlignmentTimer associated with the TAG to which the TRP belongs) has expired.

According to the first embodiment described above, the CFRA resource for each TRP can be appropriately determined.

Second Embodiment
In the existing RACH procedure, at any given time in the MAC entity, there is one ongoing RACH procedure. If the UE is triggered to multiple (e.g., two) RACH procedures, it is up to the UE implementation how to handle it.

In other words, there has been insufficient consideration given to the behavior when multiple (e.g., two) RACH procedures are triggered for multiple (e.g., two) TRPs.

In the second embodiment below, we will explain the UE operation (extended functions) when multiple RACH procedures are triggered.

A new (second) RACH procedure may be triggered in a MAC entity while a (first) RACH procedure is ongoing. The UE may receive a configuration for the new RACH procedure to be triggered. The first and second RACH procedures may be associated with different TRPs.

In the present disclosure, multiple (two) RACH procedures associated with different TRPs may mean at least one of the following:
- PDCCH orders for multiple RACH procedures each indicate a different TRP.
- PDCCH orders for multiple RACH procedures are associated with different TRPs.
- RACH resources (e.g., SSB/CSI-RS/preamble index/PRACH occasion) of multiple RACH procedures are associated with different TRPs.
- Multiple RACH procedures are triggered due to "non-synchronized" states of different TRPs.
- Multiple RACH procedures are triggered to establish time alignment for different TRPs.

The UE may follow at least one of options 2-1 and 2-2 below.

<<Option 2-1>>
The UE may decide whether to continue the first RACH procedure or to initiate a second RACH procedure.

The decision may be up to the UE implementation. In this case, the UE may decide whether to continue the first RACH procedure or to start the second RACH procedure based on certain rules/conditions.

<<Option 2-2>>
The UE may prioritize RACH procedures associated with a particular TRP.

Option 2-2 can be broadly divided into the following options 2-2-1 to 2-2-4.

[Option 2-2-1]
A particular TRP may be, for example, a TRP with a particular TRP ID.

The particular TRP ID may be, for example, the lowest (or highest) TRP ID.

The particular TRP ID may be, for example, a TRP ID whose value is 0 (or 1).

[Option 2-2-2]
A particular TRP may be, for example, a TRP associated with a particular PCI.

The particular PCI may be, for example, the PCI of the serving cell or any additional PCI.

[Option 2-2-3]
A particular TRP may be, for example, a TRP associated with a particular TAG.

The particular TAG may be, for example, a PTAG or a STAG.

[Option 2-2-4]
Each TRP may be assigned an index related to priority.

The UE may prioritize RACH procedures associated with a particular TRP based on a priority index.

The particular TRP may be, for example, a TRP to which a higher (or lower) priority index is set. A higher priority index value may indicate a higher priority, and a lower priority index value may indicate a higher priority.

In the present disclosure, prioritizing a RACH procedure associated with a particular TRP may mean that in a MAC entity, if a higher priority RACH procedure is already in progress and a lower priority RACH procedure is newly triggered, the UE continues the ongoing higher priority RACH procedure.

In the present disclosure, prioritizing a RACH procedure associated with a particular TRP may mean that, in a MAC entity, if a lower priority RACH procedure is already in progress and a new higher priority RACH procedure is triggered, the UE stops the ongoing lower priority RACH procedure and starts a new higher priority RACH procedure.

FIG. 11 is a diagram showing an example of the priority operation of the RACH related to option 2-2. The example shown in FIG. 11 shows a case where a RACH procedure for a first TRP (TRP#1) is in progress and another RACH procedure for a second TRP (TRP#2) is triggered in the middle of the procedure.

In the example shown in Figure 11, if TRP#1 is prioritized, the ongoing RACH procedure for TRP#1 is maintained and other RACH procedures for TRP#2 are not handled by the UE.

In the example shown in Figure 11, if TRP#2 is given priority, the ongoing RACH procedure for TRP#1 is stopped and the UE starts another RACH procedure for TRP#2.

According to the second embodiment described above, even if multiple RACH procedures are triggered, the RACH procedures can be processed appropriately.

Third Embodiment
If the UE wishes to establish time alignment of one TRP of a cell, or if the UE determines that it is "asynchronous" with respect to one TRP of a cell, the UE may trigger a RACH procedure for that one TRP.

Considering that other TRPs of the cell are synchronized, it is conceivable that the UE may request TRP synchronization for the other TRPs via other UL signals (e.g., Scheduling Request (SR)/MAC CE).

However, there has been insufficient consideration given to the operation related to the TRP synchronization requirements.

In the third embodiment below, we will explain the operation related to the request for synchronization of the TRP.

The particular UL signal may be, for example, a Scheduling Request (SR)/MAC CE.

The UE may send the request to the NW if certain conditions are met.

The particular condition may be based, for example, on at least one of the (UL) synchronization status per TRP and the establishment of time alignment per TRP.

For example, if the UE determines that (at least) one TRP of the serving cell is "unsynchronized," the UE may request UL time synchronization of the TRP using a specific UL signal. Also, if the UE determines that it is necessary to establish time alignment of (at least) one TRP of the serving cell, the UE may request UL time synchronization of the TRP using a specific UL signal.

If the particular UL signal is an SR, the UE may be configured with (dedicated) SR/PUCCH resources for the TRP UL time synchronization request.

The (dedicated) SR/PUCCH resource may be configured per TRP/TAG.

If the particular UL signal is a MAC CE, at least one of the following information may be included in the MAC CE:
- TRP index for asynchronous TRPs.
• Cell index of asynchronous TRP.
- TAG index of asynchronous TRP.

In the present disclosure, a TRP being asynchronous may mean that a time alignment timer (e.g., timeAlignmentTimer) associated with the TRP expires.

After transmitting a UL time synchronization request, the UE may or may not receive a response signal to the request using a specific DL signal (e.g., PDCCH/PDSCH).

The UE may assume/determine that the target TRP will be in "synchronized" state after a certain period of time has elapsed after sending the UL time synchronization request.

The UE may also assume/judge that the target TRP will be in a "synchronized" state after a certain period of time has elapsed after receiving a response signal to the request.

The specific period may be specified in advance in the specifications, may be notified to the UE by higher layer signaling (RRC/MAC CE), may be instructed to the UE by DCI, or may be determined based on reported UE capability information.

FIG. 12 is a diagram showing an example of a UL time synchronization request according to the third embodiment. In the example shown in FIG. 12, if the UE determines that (at least) one TRP of the serving cell is "asynchronous," the UE transmits a UL time synchronization request to the NW.

The third embodiment may only be applied in the cases described below:
- One TRP among the multiple TRPs of the serving cell is asynchronous and the other TRPs are synchronous (i.e., if all of the multiple TRPs are asynchronous, the UE may trigger RACH without applying this embodiment).
- An asynchronous TRP belongs to a specific cell (e.g., SCell).
- An asynchronous TRP belongs to a specific TAG (e.g., STAG).
- (In case of intra-cell multi-TRP) Asynchronous TRP belongs to a specific cell (e.g., a non-serving cell (a cell associated with the PCI of a non-serving cell)).

The third embodiment may be applied in at least one of the following cases: when the UE wants (or needs) to establish time alignment of one TRP of a cell; when the UE determines that it is "asynchronous" with respect to at least one TRP of a cell; and when the UE determines that it is "synchronous" with respect to one TRP of a cell and "asynchronous" with respect to another TRP.

According to the third embodiment described above, a request for UL time synchronization in response to TRP asynchronous operation can be appropriately transmitted.

Fourth Embodiment
The fourth embodiment describes a method for determining a TRP to which a timing advance command (TAC (e.g., one TAC)) indicated by a random access response (RAR) is applied when the TAC is applied to one TRP of a serving cell.

The UE may receive a TAC in the RAR for a serving cell with multi-TRP configured. If two TAs for the multi-TRP are supported, the UE may apply the TAC indicated in the RAR to any of the TRPs of the serving cell.

The TRP (e.g., one TRP) to which the TAC indicated in the RAR applies may be determined based on at least one of options 4-1 to 4-3 below.

<<Option 4-1>>
A TRP index may be associated with a particular CORESET/TCI state.

The particular CORESET/TCI state may be the CORESET/TCI state of the PDCCH that schedules the RAR.

The TAC contained in the RAR may be applied to the TRP of the TRP index associated with a particular CORESET/TCI state.

In this disclosure, a PDCCH that schedules an RAR may refer to a PDCCH that transmits a DCI format (DCI format 1_0) in which the CRC is scrambled by the corresponding RA-RNTI within a window controlled by higher layers that the UE attempts to detect in response to a PRACH transmission.

<<Option 4-2>>
A TRP index may be associated with a particular TCI state.

The particular TCI state may be the TCI state of the PDSCH transmitting the RAR.

The TAC contained in the RAR may be applied to the TRP of the TRP index associated with a particular TCI state.

<<Option 4-3>>
The TRP to which the TAC applies may be predefined in the specifications.

For example, the UE may determine that the TAC applies to a TRP associated with a particular TAG.

For example, the particular TAG may be a TAG with a lower (or higher) TAG ID.

For example, if one TRP is associated with a PTAG and another TRP is associated with a STAG, the particular TAG may be the PTAG (or the STAG).

The above options to be applied may be determined based on the type of RACH. For example, different options among the above options may be applied to the RACH triggered by the PDCCH order and the RACH triggered by the UE, or a common option may be applied.

In this disclosure, applying a TAC to a TRP may mean applying the TAC to a TAG associated with that TRP.

Also, in case of RACH triggered by the UE, the TAC in the MAC RAR may apply to multiple (two, both) TRPs. In case of RACH triggered by a PDCCH order, the TAC in the MAC RAR may apply to one TRP determined by at least one of the above options.

According to the fourth embodiment described above, the TRP to which the TAC is applied can be appropriately determined.

Fifth embodiment
In existing systems, when a MAC entity stops UL transmission of an SCell due to exceeding the maximum UL transmission timing difference between the TAGs of the MAC entity or the maximum UL transmission timing difference between the TAGs of any MAC entity of the UE, the MAC entity determines that the time alignment timer (timeAlignmentTimer) associated with that SCell has expired.

In addition, in existing systems, if the time alignment timer associated with the TAG to which the serving cell belongs is not running and the Configured Grant-based Small Data Transmission (CG-SDT) procedure is not in progress, the MAC entity does not perform UL transmissions other than the transmission of the random access preamble and message A (MSG A) in the serving cell.

These operations in existing systems are configured on a cell-by-cell basis. However, in the case of multiple (e.g., two) TRPs in one cell belonging to multiple (e.g., two) TAGs, it is thought that these operations will need to be extended, but this has not been sufficiently considered.

In the fifth embodiment, we will explain how to extend the above operations to operations related to multi-TRP and TA for each TRP.

If the first condition is met, the UE (MAC entity) may determine that a time alignment timer (e.g., timeAlignmentTimer) associated with the TRP of the serving cell has expired.

The first condition may be, for example, when the MAC entity stops UL transmission of the SCell because at least one of the maximum UL transmission timing difference between the TAGs of the MAC entity and the maximum UL transmission timing difference between the TAGs of any MAC entity of the UE is exceeded.

The serving cell may be, for example, a PCell/PSCell/SCell.

If the second condition is met, the UE (MAC entity) may decide not to perform a particular UL transmission associated with one TRP of the serving cell.

The second condition may be that the time alignment timer associated with the TAG to which the serving cell's TRP belongs is not running and a configured grant-based small data transmission (CG-SDT) procedure is not in progress.

The particular UL transmission may be an UL transmission other than the transmission of a random access preamble and a message A (MSG A).

According to the fifth embodiment, even when using multi-TRP and TA for each TRP, it is possible to extend the existing specification operation and control UL transmission appropriately.

Sixth embodiment (modification of the first embodiment)
In the following, a sixth embodiment will be described in which the first embodiment is applied to inter-cell mobility. Specifically, a method for setting/determining a RACH resource for each candidate cell will be described.

The UE may be configured with inter-cell multi-TRP.

The UE may receive information regarding the RACH resources corresponding to each candidate cell. The UE may then control the RACH procedure in each candidate cell based on the information.

The UE may determine one or more RACH resources according to certain rules/conditions.

The RACH resource may be a RACH resource in the CFRA for each candidate cell.

The particular rule/condition may be at least one of options 6-1 and 6-2 below.

<<Option 6-1>>
For the UE, one (common) set (parameters) of CFRA resources may be configured in the RACH configuration (e.g., rach-ConfigDedicated).

The one (common) set (parameters) of CFRA resources may be a set (parameters) for multiple (e.g., all) cells including the serving cell and one or more candidate cells.

The one (common) set may be, for example, at least one of a parameter indicating an SSB resource list (e.g., ssb-ResourceList), a parameter indicating a PRACH mask index for random access (RA) resource selection (e.g., ra-ssb-OccasionMaskIndex), a parameter indicating a CSI-RS resource list (e.g., csi-rs-ResourceList), and a parameter indicating a threshold for CSI-RS (e.g., rsrp-ThresholdCSI-RS).

Each cell index may be associated with at least one of an SSB, a CSI-RS, a random access preamble index (e.g., ra-PreambleIndex), and a PRACH opportunity.

<<Option 6-2>>
A UE may be configured with multiple sets (parameters) of CFRA resources in the RACH configuration (e.g., rach-ConfigDedicated) for multiple candidate cells.

Parameters related to CFRA may be set for each candidate cell.

The CFRA-related parameters may be any parameters included in the CFRA parameters in the RACH configuration (e.g., rach-ConfigDedicated). The CFRA-related parameters may be, for example, at least one (or all) of a parameter indicating an RA opportunity for the CFRA (e.g., occasions), a parameter indicating a setting of a random access opportunity for the CFRA (e.g., rach-ConfigGeneric), a parameter indicating the number of SSBs per RACH opportunity (e.g., ssb-perRACH-Occasion), a parameter indicating a resource for the CFRA (e.g., resources), a parameter indicating an SSB resource list (e.g., ssb-ResourceList), a parameter indicating a PRACH mask index for RA resource selection (e.g., ra-ssb-OccasionMaskIndex), a parameter indicating a CSI-RS resource list (e.g., csi-rs-ResourceList), and a parameter indicating a threshold for the CSI-RS (e.g., rsrp-ThresholdCSI-RS).

In the present disclosure, a candidate cell may be a cell related to the serving cell/additional cell or may be the same/different cell as the serving cell.

In the sixth embodiment, a CFRA may be triggered for one cell. A CFRA may be triggered for one cell, which may mean, for example, that the cell (including the serving cell/additional cell) is in a "non-synchronized" state and/or that a CFRA is triggered to establish time alignment for the cell (including the serving cell/additional cell).

When CFRA is triggered for a cell, the UE may select/determine the random access resource from among the SSB/CSI-RS/ra-PreambleIndex/PRACH occasions associated with that cell and provided in the RACH configuration (e.g., rach-ConfigDedicated).

In the present disclosure, a cell being "unsynchronized" may mean that a time alignment timer associated with the cell (e.g., timeAlignmentTimer, or the timeAlignmentTimer associated with the TAG to which the cell belongs) has expired.

According to the sixth embodiment described above, it is possible to appropriately determine the CFRA resource for each cell in inter-cell mobility.

Seventh embodiment (modification of the second embodiment)
In the seventh embodiment, an example in which the second embodiment is applied to inter-cell mobility will be described. Specifically, the operation (extended function) of a UE when multiple RACH procedures are triggered will be described.

The UE may be configured with inter-cell multi-TRP.

A new (second) RACH procedure may be triggered in a MAC entity while a (first) RACH procedure is ongoing. The first and second RACH procedures may be associated with different cells (e.g., serving/additional cells).

In the present disclosure, multiple RACH procedures associated with different cells may mean at least one of the following:
- PDCCH orders for multiple RACH procedures each indicate a different cell.
- PDCCH orders of multiple RACH procedures are associated with different cells.
- RACH resources (e.g. SSB/CSI-RS/preamble index/PRACH occasion) of multiple RACH procedures are associated with different cells.
- Multiple RACH procedures are triggered due to "non-synchronized" conditions in different cells.
- Multiple RACH procedures are triggered to establish time alignment for different cells.

The UE may follow at least one of options 7-1 and 7-2 below.

<<Option 7-1>>
The UE may decide whether to continue the first RACH procedure or to initiate a second RACH procedure.

The decision may be up to the UE implementation. In this case, the UE may decide whether to continue the first RACH procedure or to start the second RACH procedure based on certain rules/conditions.

<<Option 7-2>>
The UE may prioritize RACH procedures associated with a particular cell.

Option 7-2 can be broadly divided into the following options 7-2-1 to 7-2-4.

[Option 7-2-1]
A particular cell may be, for example, a cell having a particular cell index.

The cell index may be, for example, the lowest (or highest) cell index.

[Option 7-2-2]
The particular cell may be, for example, a serving cell.

The UE may prioritize the RACH procedure associated with the serving cell.

The UE may prioritize the RACH procedure for the TRP associated with the serving cell.

[Option 7-2-3]
A particular cell may be, for example, a cell associated with a particular TAG.

The particular TAG may be, for example, a PTAG or a STAG.

The UE may prioritize the RACH procedure for cells associated with a particular TAG.

The UE may prioritize the RACH procedure for TRPs related to cells associated with a particular TAG.

[Option 7-2-4]
Each cell may be assigned an index related to its priority.

The UE may prioritize RACH procedures associated with a particular cell based on a priority index.

The particular cell may be, for example, a cell to which a higher (or lower) priority index is set. A higher priority index value may indicate a higher priority, and a lower priority index value may indicate a higher priority.

In the present disclosure, prioritizing a RACH procedure associated with a particular cell may mean that in a MAC entity, if a higher priority RACH procedure is already in progress and a lower priority RACH procedure is newly triggered, the UE continues the ongoing higher priority RACH procedure.

In the present disclosure, prioritizing a RACH procedure associated with a particular cell may mean that, in a MAC entity, if a lower priority RACH procedure is already in progress and a new higher priority RACH procedure is triggered, the UE stops the ongoing lower priority RACH procedure and starts a new higher priority RACH procedure.

FIG. 13 is a diagram showing an example of the priority operation of the RACH according to option 7-2. The example shown in FIG. 13 shows a case in which a RACH procedure for a first cell (cell #1) is in progress and another RACH procedure for a second cell (cell #2) is triggered in the middle of the procedure.

In the example shown in Figure 13, if cell #1 is prioritized, the ongoing RACH procedure for cell #1 is maintained and another RACH procedure for cell #2 is not handled by the UE.

In the example shown in Figure 13, if cell #2 is prioritized, the ongoing RACH procedure for cell #1 is stopped and the UE initiates a new RACH procedure for cell #2.

According to the seventh embodiment described above, even if multiple RACH procedures are triggered, the RACH procedures can be processed appropriately.

Eighth embodiment (modification of the third embodiment)
In the eighth embodiment, an example in which the third embodiment is applied to inter-cell mobility will be described below. Specifically, an operation related to a request for synchronization of a cell (e.g., a cell including a serving cell/additional cell) will be described.

The UE may be configured with inter-cell multi-TRP.

The UE may request UL time synchronization of a cell (e.g., a cell including a serving cell/additional cell) from the NW (e.g., a base station) using a specific UL signal.

The UE may request UL time synchronization of the TRP from the network (NW, e.g., base station) using a specific UL signal if certain conditions are met.

The case where the particular condition is satisfied may be based on, for example, at least one of the (UL) synchronization status for each TRP and the establishment of time alignment for each TRP.

For example, if the UE determines that one TRP of a cell is "unsynchronized," the UE may request UL time synchronization of the TRP using a specific UL signal. Also, if the UE determines that it is necessary to establish time alignment of one TRP of a cell, the UE may request UL time synchronization of the TRP using a specific UL signal.

The particular UL signal may be, for example, a Scheduling Request (SR)/MAC CE.

The UE may send the request to the NW if certain conditions are met.

The particular condition may be based, for example, on at least one of the following: per-cell (UL) synchronization status and the establishment of per-cell time alignment.

The particular condition may be, for example, when the cell (synchronization status) is "asynchronous."

For example, if the UE determines that it is "unsynchronized" with respect to a cell, it may request UL time synchronization of the cell using a specific UL signal.

If the particular UL signal is an SR, the UE may be configured with (dedicated) SR/PUCCH resources for requesting UL time synchronization of the cell.

The (dedicated) SR/PUCCH resource may be configured per cell/TAG.

If the particular UL signal is a MAC CE, at least one of the following information may be included in the MAC CE:
・The cell index of the asynchronous cell.
- The TAG index associated with the unsynchronized cell.

In the present disclosure, a cell being asynchronous may mean that a time alignment timer (e.g., timeAlignmentTimer) associated with the cell or the TAG of the cell has expired.

After transmitting a UL time synchronization request, the UE may or may not receive a response signal to the request using a specific DL signal (e.g., PDCCH/PDSCH).

The UE may assume/determine that the target TRP will be in "synchronized" state after a certain period of time has elapsed after sending the UL time synchronization request.

The UE may also assume/judge that the target TRP will be in a "synchronized" state after a certain period of time has elapsed after receiving a response signal to the request.

The specific period may be specified in advance in the specifications, may be notified to the UE by higher layer signaling (RRC/MAC CE), may be instructed to the UE by DCI, or may be determined based on reported UE capability information.

The eighth embodiment may be applied only in cases where the unsynchronized cell is a specific cell (e.g., a non-serving cell).

According to the eighth embodiment described above, a request for UL time synchronization for cell asynchrony in inter-cell mobility can be appropriately transmitted.

<Additional Information>
[Notification of information to UE]
In the above-described embodiments, any information may be notified to the UE (from a network (NW) (e.g., a base station (BS))) (in other words, any information is received from the BS by the UE) using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal/channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

When the above notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader that is not specified in existing standards.

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

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

[Information notification from UE]
In the above-described embodiments, notification of any information from the UE (to the NW) (in other words, transmission/report of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal/channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

If the notification is made by a MAC CE, the MAC CE may be identified by including a new LCID in the MAC subheader that is not specified in existing standards.

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

Furthermore, in the above-mentioned embodiments, notification of any information from the UE may be performed periodically, semi-persistently, or aperiodically.

[Application of each embodiment]
At least one of the above-mentioned embodiments may be applied when a specific condition is satisfied, which may be specified in a standard or may be notified to a UE/BS using higher layer signaling/physical layer signaling.

At least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.

The specific UE capabilities may indicate at least one of the following:
Supporting specific processing/operations/control/information for at least one of the above embodiments;
Supporting multiple (e.g., two) TAs for multi-TRP;
Supporting multiple (e.g., two) TAs for intra-cell M-TRP;
Supporting multiple (e.g., two) TAs for inter-cell M-TRP;
Supporting L1/L2 inter-cell mobility.

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

The specific UE capabilities may be capabilities that are applied across all duplexing methods (commonly regardless of the duplexing method), or may be capabilities for each duplexing method (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).

Furthermore, at least one of the above-mentioned embodiments may be applied when the UE configures/activates/triggers specific information related to the above-mentioned embodiments (or performs the operations of the above-mentioned embodiments) by higher layer signaling/physical layer signaling. For example, the specific information may be information indicating the activation of multiple TAs for multi-TRP, information indicating the activation of multiple TAs for intra-cell multi-TRP, information indicating the activation of multiple TAs for inter-cell multi-TRP, information indicating the activation of L1/L2 inter-cell mobility, any RRC parameter for a specific release (e.g., Rel. 18/19), etc.

If the UE does not support at least one of the above specific UE capabilities or the above specific information is not configured, the UE may, for example, apply Rel. 15/16 operations.

(Appendix A)
With respect to one embodiment of the present disclosure, the following invention is noted.
[Appendix A-1]
A receiving unit that receives first information on a resource of a Contention Free Random Access (CFRA) corresponding to a first transmission/reception point (TRP) and second information on a resource of the CFRA corresponding to a second TRP;
A terminal having a control unit that controls a CFRA procedure in the first TRP based on the first information and controls a CFRA procedure in the second TRP based on the second information.
[Appendix A-2]
The terminal according to Appendix A-1, wherein the first information and the second information are common information.
[Appendix A-3]
The terminal according to Appendix A-1 or Appendix A-2, wherein the first information and the second information are different pieces of information each relating to a different TRP.
[Appendix A-4]
the first information corresponds to a first cell, the second information corresponds to a second cell;
The control unit is a terminal according to any one of Supplementary Note A-1 to Supplementary Note A-3 that controls a CFRA procedure in an inter-cell multi-TRP.

(Appendix B)
With respect to one embodiment of the present disclosure, the following invention is noted.
[Appendix B-1]
A receiving unit that receives a setting for a second random access channel (RACH) procedure corresponding to a second transmission/reception point (TRP) when a first RACH procedure corresponding to a first transmission/reception point (TRP) is set;
A terminal having a control unit that determines, based on a specific condition, whether to maintain the first RACH procedure or to stop the first RACH procedure and start the second RACH procedure.
[Appendix B-2]
The terminal described in Appendix B-1, in which the control unit determines whether to maintain the first RACH procedure or to stop the first RACH procedure and start the second RACH procedure based on an ID related to a specific TRP.
[Appendix B-3]
The control unit determines whether to maintain the first RACH procedure or to stop the first RACH procedure and start the second RACH procedure based on a TRP associated with a specific physical cell ID. A terminal as described in Appendix B-1 or Appendix B-2.
[Appendix B-4]
The control unit determines whether to maintain the first RACH procedure or to stop the first RACH procedure and start the second RACH procedure based on a TRP associated with a specific timing advance group. A terminal described in any of Supplementary Notes B-1 to B-3.

(Appendix C)
With respect to one embodiment of the present disclosure, the following invention is noted.
[Appendix C-1]
A transmitter that transmits a UL time synchronization request for a transmission/reception point (TRP) using a specific uplink (UL) signal based on at least one of a synchronization status for each transmission/reception point (TRP) and an establishment of time alignment for each TRP;
A terminal having a control unit that determines that multiple TRPs are synchronized after a specific period of time has elapsed after transmitting the UL signal.
[Appendix C-2]
the specific UL signal is a scheduling request;
The terminal according to Appendix C-1, wherein the control unit determines resources for the scheduling request for each TRP or for each timing advance group.
[Appendix C-3]
the particular UL signal is a Medium Access Control (MAC) control element;
A terminal described in Appendix C-1 or Appendix C-2, wherein the MAC control element includes at least one of an index related to a TRP of an asynchronous TRP, a cell index of the asynchronous TRP, and an index of a timing advance group of the asynchronous TRP.
[Appendix C-4]
The control unit further controls reception of a timing advance command (TAC) included in a random access response (RAR);
A terminal described in any of Supplementary Notes C-1 to C-3, which determines the TRP to which the TAC is applied based on at least one of a control resource set or Transmission Configuration Indication (TCI) state associated with a physical downlink control channel that schedules the TAC, a TCI state of a physical downlink shared channel that transmits the RAR, and a specific timing advance group.

(Appendix D)
With respect to one embodiment of the present disclosure, the following invention is noted.
[Appendix D-1]
A receiving unit that receives a configuration of an inter-cell multi-transmission/reception point (TRP) and receives first information regarding a resource of a Contention Free Random Access (CFRA) corresponding to a first candidate cell and second information regarding a resource of the CFRA corresponding to a second candidate cell;
A terminal having a control unit that controls a CFRA procedure in the first candidate cell based on the first information and controls a CFRA procedure in the second candidate cell based on the second information.
[Appendix D-2]
The terminal according to Supplementary Note D-1, wherein the first information and the second information are common information or separate information related to separate candidate cells.
[Appendix D-3]
The receiving unit further receives a setting for a second random access channel (RACH) procedure corresponding to the second TRP when a first RACH procedure corresponding to the first TRP is set;
The control unit further determines, based on a specific condition, whether to maintain the first RACH procedure or to stop the first RACH procedure and start the second RACH procedure. The terminal described in Appendix D-1 or Appendix D-2.
[Appendix D-4]
The terminal according to any one of Supplementary Note D-1 to Supplementary Note D-3, wherein the control unit controls transmission of a UL time synchronization request for a cell based on a synchronization status of the cell.

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

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

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

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 may support dual connectivity between multiple base stations within the same RAT (e.g., dual connectivity in which both the MN and SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

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

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

Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). Macro cell 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.

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

The multiple base stations 10 may be connected by wire (e.g., optical fiber conforming to the Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, base station 11, which corresponds to the upper station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which corresponds to a relay station, may be called an IAB 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 at least one of, for example, an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), etc.

The core network 30 may include network functions (Network Functions (NF)) such as, for example, a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Note that multiple functions may be provided by one network node. In addition, communication with an external network (e.g., the Internet) may be performed via the DN.

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

In the wireless communication system 1, a wireless access method based on Orthogonal Frequency Division Multiplexing (OFDM) may be used. For example, in at least one of the 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.

The radio access method may also be called a waveform. In the wireless communication system 1, other radio access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL radio access methods.

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

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

User data, upper layer control information, System Information Block (SIB), etc. are transmitted via PDSCH. User data, upper layer control information, etc. may also be transmitted via PUSCH. Furthermore, Master Information Block (MIB) may also be transmitted via PBCH.

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

Note that the DCI for scheduling the PDSCH may be called a DL assignment or DL DCI, and the DCI for scheduling the PUSCH may be called a UL grant or UL DCI. Note that the PDSCH may be interpreted as DL data, and the PUSCH may be interpreted as UL data.

A control resource set (COntrol REsource SET (CORESET)) and a search space may be used to detect the PDCCH. The CORESET corresponds to the resources to search for DCI. The search space corresponds to the search region and search method of PDCCH candidates. One CORESET may be associated with one or multiple search spaces. The UE may monitor the CORESET associated with a search space based on the search space configuration.

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

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

Note that in this disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

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

The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including an SS (PSS, SSS) and a PBCH (and a DMRS for PBCH) may be called an SS/PBCH block, an SS Block (SSB), etc. In addition, the SS, SSB, etc. may also be called a reference signal.

In addition, in the wireless communication system 1, a measurement reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), etc. may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific Reference Signal).

(base station)
15 is a diagram showing an example of a configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140 may each be provided in one or more units.

Note that this example mainly shows the functional blocks of the characteristic parts of this embodiment, and the base station 10 may also be assumed to have other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

The control unit 110 controls the entire base station 10. The control unit 110 can be configured from a controller, a control circuit, etc., which are described based on a common understanding in the technical field to which this disclosure pertains.

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

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

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

The transmitting/receiving antenna 130 can be configured as an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.

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

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

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

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

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

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

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

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

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

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

The transceiver unit 120 may transmit first information regarding a Contention Free Random Access (CFRA) resource corresponding to a first transceiver point (TRP) and second information regarding a CFRA resource corresponding to a second TRP. The control unit 110 may use the first information to instruct a CFRA procedure in the first TRP and use the second information to instruct a CFRA procedure in the second TRP (first embodiment).

The transceiver unit 120 may transmit settings for a second random access channel (RACH) procedure corresponding to a second TRP when a first RACH procedure corresponding to a first transmission/reception point (TRP) is set. The control unit 110 may use specific conditions to instruct the first RACH procedure to be maintained, or to stop the first RACH procedure and start the second RACH procedure (second embodiment).

The transceiver unit 120 may receive a UL time synchronization request for a transceiver point (TRP) using a specific uplink (UL) signal transmitted based on at least one of the synchronization status for each transceiver point (TRP) and the establishment of time alignment for each TRP. The control unit 110 may control the synchronization of multiple TRPs after a specific period of time has elapsed after receiving the UL signal (third embodiment).

The transceiver unit 120 may transmit an inter-cell multi-transmission/reception point (TRP) configuration, and transmit first information regarding a Contention Free Random Access (CFRA) resource corresponding to a first candidate cell and second information regarding a CFRA resource corresponding to a second candidate cell. The control unit 110 may use the first information to instruct a CFRA procedure in the first candidate cell, and may use the second information to instruct a CFRA procedure in the second candidate cell (sixth embodiment).

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

Note that this example mainly shows the functional blocks of the characteristic parts of this embodiment, and the user terminal 20 may also be assumed to have other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

The control unit 210 controls the entire user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on a common understanding in the technical field to which this disclosure pertains.

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

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

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

The transmitting/receiving antenna 230 can be configured as an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.

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

The transceiver 220 may form at least one of the transmit beam and receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.

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

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

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

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

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

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

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

In addition, the transmitting unit and receiving unit of the user terminal 20 in this disclosure may be configured by at least one of the transmitting/receiving unit 220 and the transmitting/receiving antenna 230.

The transceiver unit 220 may receive first information regarding Contention Free Random Access (CFRA) resources corresponding to a first transceiver point (TRP) and second information regarding CFRA resources corresponding to a second TRP. The control unit 210 may control the CFRA procedure in the first TRP based on the first information, and control the CFRA procedure in the second TRP based on the second information (first embodiment).

The first information and the second information may be common information (first embodiment).

The first information and the second information may be different pieces of information each relating to a different TRP (first embodiment).

The first information may correspond to a first cell, and the second information may correspond to a second cell. The control unit 210 may control a CFRA procedure in an inter-cell multi-TRP (first embodiment).

The transceiver unit 220 may receive a setting for a second random access channel (RACH) procedure corresponding to a second TRP when a first RACH procedure corresponding to a first transmission/reception point (TRP) is set. The control unit 210 may determine whether to maintain the first RACH procedure or to stop the first RACH procedure and start the second RACH procedure based on a specific condition (second embodiment).

The control unit 210 may determine whether to maintain the first RACH procedure or to stop the first RACH procedure and start the second RACH procedure based on the ID for a specific TRP (second embodiment).

The control unit 210 may determine whether to maintain the first RACH procedure or to stop the first RACH procedure and start the second RACH procedure based on the TRP associated with a specific physical cell ID (second embodiment).

The control unit 210 may determine whether to maintain the first RACH procedure or to stop the first RACH procedure and start the second RACH procedure based on the TRP associated with a particular timing advance group (second embodiment).

The transceiver unit 220 may transmit a UL time synchronization request for a transmission/reception point (TRP) using a specific uplink (UL) signal based on at least one of the synchronization status for each transmission/reception point (TRP) and the establishment of time alignment for each TRP. The control unit 210 may determine that multiple TRPs are synchronized after a specific period of time has elapsed after transmitting the UL signal (third embodiment).

The specific UL signal may be a scheduling request, and the control unit 210 may determine resources for the scheduling request for each TRP or for each timing advance group (third embodiment).

The particular UL signal may be a Medium Access Control (MAC) control element, and the MAC control element may include at least one of a TRP-related index of the asynchronous TRP, a cell index of the asynchronous TRP, and a timing advance group index of the asynchronous TRP (third embodiment).

The control unit 210 may further control reception of a timing advance command (TAC) included in a random access response (RAR). The control unit 210 may determine the TRP to which the TAC is applied based on at least one of a control resource set or a Transmission Configuration Indication (TCI) state associated with a physical downlink control channel that schedules the TAC, a TCI state of a physical downlink shared channel that transmits the RAR, and a specific timing advance group (fourth embodiment).

The transceiver unit 220 may receive an inter-cell multi-transmission/reception point (TRP) configuration, and may receive first information regarding Contention Free Random Access (CFRA) resources corresponding to a first candidate cell and second information regarding CFRA resources corresponding to a second candidate cell. The control unit 210 may control a CFRA procedure in the first candidate cell based on the first information, and control a CFRA procedure in the second candidate cell based on the second information (sixth embodiment).

The first information and the second information may be common information or may be separate information each relating to a different candidate cell (sixth embodiment).

The transceiver unit 220 may further receive a setting for a second random access channel (RACH) procedure corresponding to the second TRP when a first RACH procedure corresponding to the first TRP is set. The control unit 210 may further determine whether to maintain the first RACH procedure or to stop the first RACH procedure and start the second RACH procedure based on a specific condition (seventh embodiment).

The control unit 210 may control the transmission of a UL time synchronization request for a cell based on the synchronization status of the cell (eighth embodiment).

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

Here, the functions include, but are not limited to, judgement, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the transmission function may be called a transmitting unit, a transmitter, and the like. In either case, as mentioned above, there are no particular limitations on the method of realization.

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

In addition, in this disclosure, the terms apparatus, circuit, device, section, unit, etc. may be interpreted as interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the figures, or may be configured to exclude some of the devices.

For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, sequentially, or using other techniques. Furthermore, the processor 1001 may be implemented by one or more chips.

The functions of the base station 10 and the user terminal 20 are realized, for example, by loading specific software (programs) onto hardware such as the processor 1001 and memory 1002, causing the processor 1001 to perform calculations, control communications via the communication device 1004, and control at least one of the reading and writing of data in the memory 1002 and storage 1003.

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

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

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

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

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, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, the above-mentioned transmitting/receiving unit 120 (220), transmitting/receiving antenna 130 (230), etc. may be realized by the communication device 1004. The transmitting/receiving unit 120 (220) may be implemented as a transmitting unit 120a (220a) and a receiving unit 120b (220b) that are physically or logically separated.

The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one structure (e.g., a touch panel).

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

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

(Modification)
In addition, the terms described in this disclosure and the terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be read as mutually interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may be called a pilot, a pilot signal, or the like depending on the applied standard. A component carrier (CC) may also be called a cell, a frequency carrier, a carrier frequency, or the like.

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

Here, the numerology may be a communication parameter that is applied to at least one of the transmission and reception of a signal or channel. The numerology may indicate, for example, at least one of the following: SubCarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame configuration, a specific filtering process performed by the transceiver in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc.

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

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

A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units when transmitting a signal. A different name may be used for a radio frame, a subframe, a slot, a minislot, and a symbol, respectively. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in this disclosure may be read as interchangeable.

For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

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

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

Note that when one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. In addition, the number of slots (minislots) that constitute the minimum time unit of 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, etc. A TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

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

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

Furthermore, an RB may include one or more symbols in the time domain and may be one slot, one minislot, one subframe, or one TTI in length. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

In addition, one or more RBs may be referred to as a physical resource block (Physical RB (PRB)), a sub-carrier group (Sub-Carrier Group (SCG)), a resource element group (Resource Element Group (REG)), a PRB pair, an RB pair, etc.

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

A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by an index of the RB relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

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

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

Note that the above-mentioned structures of radio frames, subframes, slots, minislots, and symbols are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, as well as the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length can be changed in various ways.

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

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

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

In addition, information, signals, etc. may be output from a higher layer to a lower layer and/or from a lower layer to a higher layer. Information, signals, etc. may be input/output via multiple network nodes.

Input/output information, signals, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. Input/output information, signals, etc. may be overwritten, updated, or added to. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

The notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods. For example, the notification of information in this disclosure may be performed by 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 a combination of these.

The physical layer signaling may be called Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal), L1 control information (L1 control signal), etc. The RRC signaling may be called an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc. The MAC signaling may be notified, for example, using a MAC Control Element (CE).

Furthermore, notification of specified information (e.g., notification that "X is the case") is not limited to explicit notification, but may be implicit (e.g., by not notifying the specified information or by notifying other information).

The determination may be based on a value represented by a single bit (0 or 1), a Boolean value represented by true or false, or a comparison of numerical values (e.g., with a predetermined value).

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

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

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

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

In this disclosure, terms such as "Base Station (BS)", "Radio base station", "Fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission/Reception Point (TRP)", "Panel", "Cell", "Sector", "Cell group", "Carrier", "Component carrier", etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services by a base station subsystem (e.g., a small base station for indoor use (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the entire coverage area of at least one of the base station and base station subsystems that provide communication services in this coverage.

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

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

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

At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. In addition, at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

The moving body in question refers to an object that can move, and the moving speed is arbitrary, and of course includes the case where the moving body is stationary. The moving body in question includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, balloons, and objects mounted on these. The moving body in question may also be a moving body that moves autonomously based on an operating command.

The moving object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

FIG. 18 is a diagram showing an example of a vehicle according to an embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

The drive unit 41 is composed of at least one of an engine, a motor, and a hybrid of an engine and a motor, for example. The steering unit 42 includes at least a steering wheel (also called a handlebar), and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by the user.

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

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

The information service unit 59 is composed of various devices, such as a car navigation system, audio system, speakers, displays, televisions, and radios, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via the communication module 60, etc., to provide various information/services (e.g., multimedia information/multimedia services) to the occupants of the vehicle 40.

The information service unit 59 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that perform output to the outside.

The driving assistance system unit 64 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving load, such as a millimeter wave radar, a Light Detection and Ranging (LiDAR), a camera, a positioning locator (e.g., a Global Navigation Satellite System (GNSS)), map information (e.g., a High Definition (HD) map, an Autonomous Vehicle (AV) map, etc.), a gyro system (e.g., an Inertial Measurement Unit (IMU), an Inertial Navigation System (INS), etc.), an Artificial Intelligence (AI) chip, and an AI processor, and one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize a driving assistance function or an autonomous driving function.

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

The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the above-mentioned base station 10 or user terminal 20. The communication module 60 may also be, for example, at least one of the above-mentioned base station 10 and user terminal 20 (it may function as at least one of the base station 10 and user terminal 20).

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

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

The communication module 60 also stores various information received from external devices in memory 62 that can be used by the microprocessor 61. Based on the information stored in memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, various sensors 50-58, and the like provided on the vehicle 40.

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

Similarly, the user terminal in this disclosure may be interpreted as a base station. In this case, the base station 10 may be configured to have the functions of the user terminal 20 described above.

In this disclosure, operations that are described as being performed by a base station may in some cases be performed by its upper node. In a network that includes one or more network nodes having base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME) or a Serving-Gateway (S-GW)), or a combination of these.

Each aspect/embodiment described in this disclosure may be used alone, in combination, or switched between depending on the implementation. In addition, the processing procedures, sequences, flow charts, etc. of each aspect/embodiment described in this disclosure may be rearranged as long as there is no inconsistency. For example, the methods described in this disclosure present elements of various steps using an exemplary order, and are not limited to the particular 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 (x is, for example, an integer or decimal)), Future Radio Access (FRA), New-Radio The present invention may be applied to systems that use Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), and other appropriate wireless communication methods, as well as next-generation systems that are expanded, modified, created, or defined based on these. In addition, multiple systems may be combined (for example, a combination of LTE or LTE-A and 5G, etc.).

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

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

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

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

"Judgment" may also be considered to mean "deciding" to resolve, select, choose, establish, compare, etc. In other words, "judgment" may also be considered to mean "deciding" to take some kind of action.

In addition, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," etc.

The "maximum transmit power" referred to in this disclosure may mean the maximum value of transmit power, may mean the nominal UE maximum transmit power, or may mean the rated UE maximum transmit power.

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

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

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

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

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

In this disclosure, terms such as "less than", "less than", "greater than", "more than", "equal to", etc. may be read as interchangeable. In addition, in this disclosure, terms meaning "good", "bad", "big", "small", "high", "low", "fast", "slow", "wide", "narrow", etc. may be read as interchangeable, not limited to positive, comparative and superlative. In addition, in this disclosure, terms meaning "good", "bad", "big", "small", "high", "low", "fast", "slow", "wide", "narrow", etc. may be read as interchangeable, not limited to positive, comparative and superlative, as expressions with "ith" (i is any integer) (for example, "best" may be read as "ith best").

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

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

Claims (6)

1. A receiving unit that receives a configuration of an inter-cell multi-transmission/reception point (TRP) and receives first information regarding a resource of a Contention Free Random Access (CFRA) corresponding to a first candidate cell and second information regarding a resource of the CFRA corresponding to a second candidate cell;
   A terminal having a control unit that controls a CFRA procedure in the first candidate cell based on the first information and controls a CFRA procedure in the second candidate cell based on the second information.
2. The terminal according to claim 1, wherein the first information and the second information are common information or different information each relating to a different candidate cell.
3. The receiving unit further receives a setting for a second random access channel (RACH) procedure corresponding to the second TRP when a first RACH procedure corresponding to the first TRP is set;
   The terminal according to claim 1, wherein the control unit further determines, based on a specific condition, whether to maintain the first RACH procedure or to stop the first RACH procedure and start the second RACH procedure.
4. The terminal according to claim 1, wherein the control unit controls the transmission of a UL time synchronization request for a cell based on the synchronization status of the cell.
5. receiving an inter-cell multi-transmission/reception point (TRP) configuration, and receiving first information on a Contention Free Random Access (CFRA) resource corresponding to a first candidate cell and second information on a CFRA resource corresponding to a second candidate cell;
   A wireless communication method for a terminal, comprising the steps of controlling a CFRA procedure in the first candidate cell based on the first information, and controlling a CFRA procedure in the second candidate cell based on the second information.
6. A transmitter that transmits a configuration of an inter-cell multi-transmission/reception point (TRP) and transmits first information on a resource of a Contention Free Random Access (CFRA) corresponding to a first candidate cell and second information on a resource of the CFRA corresponding to a second candidate cell;
   A base station comprising: a control unit that uses the first information to instruct a CFRA procedure in the first candidate cell and uses the second information to instruct a CFRA procedure in the second candidate cell.

Images