WO2024038516A1

WO2024038516A1 - Terminal, wireless communication method, and base station

Info

Publication number: WO2024038516A1
Application number: PCT/JP2022/031057
Authority: WO
Inventors: 尚哉芝池; 祐輝松村; 聡永田; チーピンピ; ジンワン; ランチン
Original assignee: 株式会社Ｎｔｔドコモ
Priority date: 2022-08-17
Filing date: 2022-08-17
Publication date: 2024-02-22

Abstract

A terminal according to one aspect of the present disclosure comprises: a control unit which controls one or more competition resolution windows with respect to a plurality of repetitions of a physical random access channel (PRACH); and a reception unit which receives one or more downlink control information formats in the one or more competition resolution windows. According to one aspect of the present disclosure, the coverage of a random access procedure can be improved.

Description

Terminal, wireless communication method and base station

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

In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been specified for the purpose of higher data rates, lower delays, etc. (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel. 10-14) is a specification for the purpose of further increasing capacity and sophistication of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel. 8, 9). was made into

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

Improving coverage is being considered in future wireless communication systems (for example, NR).

However, the random access procedure for improving coverage is not clear. If such a random access procedure is not clear, communication throughput may decrease.

Therefore, one of the purposes of the present disclosure is to provide a terminal, a wireless communication method, and a base station that improve the coverage of random access procedures.

A terminal according to an aspect of the present disclosure includes a control unit that controls one or more contention resolution windows for a plurality of repetitions of a physical random access channel (PRACH); and a receiving unit that receives the above downlink control information format.

According to one aspect of the present disclosure, coverage of random access procedures can be improved.

FIG. 1 shows an example of a RACH configuration information element. 2A and 2B illustrate an example of PRACH occasion and beam association. FIG. 3 shows an example of a plurality of PUCCH resource sets before individual PUCCH resources are configured. 4A and 4B show an example of problem 1/2. Figures 5A and 5B show an example of problem 2/4. FIG. 6 shows an example of problem 5. 7A and 7B illustrate an example of a random access procedure according to option 1 of embodiment #1. FIG. 8 shows another example of the random access procedure according to option 1 of embodiment #1. FIG. 9 shows an example of a random access procedure according to option 2 of embodiment #1. FIG. 10 shows an example of a random access procedure according to embodiment #5. 11A and 11B show an example of a random access procedure according to embodiment #6. FIG. 12 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 13 is a diagram illustrating an example of the configuration of a base station according to an embodiment. FIG. 14 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. FIG. 15 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. FIG. 16 is a diagram illustrating an example of a vehicle according to an embodiment.

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

The TCI states may represent those that apply to downlink signals/channels. What corresponds to the TCI state applied to uplink signals/channels may be expressed as a spatial relation.

The TCI state is information regarding quasi-co-location (QCL) of signals/channels, and may also be called spatial reception parameters, spatial relation information, etc. The 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, when one signal/channel and another signal/channel have a QCL relationship, the Doppler shift, Doppler spread, and average delay are calculated between these different signals/channels. ), delay spread, and spatial parameters (e.g., spatial Rx parameters) can be assumed to be the same (QCL with respect to at least one of these). You may.

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

A plurality of types (QCL types) may be defined for QCL. For example, four QCL types A-D may be provided with different parameters (or parameter sets) that can be assumed to be the same, and the parameters (which may be referred to as QCL parameters) are shown below:
・QCL type A (QCL-A): Doppler shift, Doppler spread, average delay and delay spread,
・QCL type B (QCL-B): Doppler shift and Doppler spread,
・QCL type C (QCL-C): Doppler shift and average delay,
- QCL type D (QCL-D): Spatial reception parameters.

For the UE to assume that one 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, It may also be called a QCL assumption.

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

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

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

Channels for which TCI states or spatial relationships are set (specified) are, for example, Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), and Uplink Shared Channel (Physical Uplink Shared Channel). The channel may be at least one of a physical uplink control channel (PUCCH) and a physical uplink control channel (PUCCH).

In addition, the RS that has a QCL relationship with the channel is, for example, a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a measurement reference signal (Sounding The signal may be at least one of a tracking reference signal (SRS), a tracking CSI-RS (also referred to as a tracking reference signal (TRS)), and a QCL detection reference signal (also referred to as a QRS).

The 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). SSB may be called SS/PBCH block.

An RS of QCL type X in a TCI state may mean an RS that has a QCL type It's okay.

(Initial access procedure)
In the initial access procedure, the UE (RRC_IDLE mode) receives SS/PBCH blocks (SSB), Msg. 1 (PRACH/random access preamble/preamble) transmission, Msg. 2 (PDCCH, PDSCH including random access response (RAR)), Msg. 3 (PUSCH scheduled by RAR UL grant) transmission, Msg. 4 (PDCCH, PDSCH including UE contention resolution identity). After that, Msg. When an ACK for 4 is sent, an RRC connection is established (RRC_CONNECTED mode).

SSB reception includes PSS detection, SSS detection, PBCH-DMRS detection, and PBCH reception. PSS detection performs detection of part of the physical cell ID (PCI), detection (synchronization) of OFDM symbol timing, and (coarse) frequency synchronization. SSS detection includes detection of physical cell ID. PBCH-DMRS detection involves detection of (part of) the SSB index within a half radio frame (5ms). PBCH reception involves detecting the system frame number (SFN) and radio frame timing (SSB index), receiving configuration information for receiving remaining minimum system information (RMSI, SIB1), and allowing the UE to camp in that cell (carrier). including the recognition of whether or not.

SSB has a band of 20 RB and a time of 4 symbols. The SSB transmission cycle can be set from {5, 10, 20, 40, 80, 160} ms. In a half frame, a plurality of SSB symbol positions are defined based on the frequency range (FR1, FR2).

PBCH has a 56-bit payload. N repetitions of the PBCH are transmitted within a period of 80ms. N depends on the SSB transmission period.

System information consists of MIB carried by PBCH, RMSI (SIB1), and other system information (OSI). SIB1 includes information for performing RACH settings and RACH procedures. The time/frequency resource relationship between the SSB and the PDCCH monitoring resource for SIB1 is set by the PBCH.

A base station that uses beam correspondence transmits multiple SSBs using multiple beams in each SSB transmission period. Each of the plurality of SSBs has a plurality of SSB indexes. A UE that detects one SSB transmits a PRACH in the RACH occasion associated with that SSB index and receives a RAR in the RAR window.

(beam and coverage)
In high frequency bands, if beamforming is not applied to the synchronization signal/reference signal, the coverage will be narrow and it will be difficult for the UE to discover the base station. On the other hand, if beamforming is applied to the synchronization signal/reference signal to ensure coverage, a strong signal will reach in a specific direction, but it will be more difficult for the signal to reach in other directions. If the direction in which the UE exists is unknown at the base station before the UE is connected, it is impossible to transmit synchronization signals/reference signals using beams directed only in appropriate directions. A possible method is that the base station transmits multiple synchronization signals/reference signals, each having beams in different directions, and the UE recognizes which beam it has discovered. Using thin (narrow) beams for coverage requires transmitting many synchronization/reference signals, which may increase overhead and reduce spectrum efficiency.

If thicker (wider) beams are used to reduce the number of beams (synchronization signals/reference signals) and suppress overhead, the coverage will become narrower.

In future wireless communication systems (for example, 6G), it is thought that the use of frequency bands such as millimeter waves and terahertz waves will further advance. It is conceivable to provide communication services by building the area/coverage of cells using a large number of narrow beams.

It is possible to use the existing FR2 and expand the area, or to use a higher frequency band than the existing FR2. To realize these, improvements in beam management are preferred in addition to multi-TRP, reconfigurable intelligent surfaces (RIS), etc.

Coverage extension including PRACH extension for frequency range (FR) 2 is being considered. For example, PRACH repetition using the same beam or different beams is being considered. This PRACH extension may be applied to the 4-step RACH procedure or to FR1.

PRACH extension may be applied to the short PRACH format or to other formats.

(PRACH)
As shown in Figure 1, the common RACH configuration (RACH-ConfigCommon) includes the general RACH configuration (rach-ConfigGeneric), the total number of RA preambles (totalNumberOfRA-Preambles), the SSB for each RACH occasion, and the contention-based (CB) for each SSB. ) preamble (ssb-perRACH-OccasionAndCB-PreamblesPerSSB). The rach-ConfigGeneric may include a PRACH configuration index (prach-ConfigurationIndex) and a message 1FDM (msg1-FDM, number of PRACH occasions to be FDMed within one time instance). ssb-perRACH-OccasionAndCB-PreamblesPerSSB may include the number of CB preambles for each SSB for the number of SSBs for each RACH occasion 1/8 (oneEighth, one SSB is associated with eight RACH occasions).

For type 1 random access procedure (4-step random access procedure, messages 1/2/3/4), the UE determines the number N of SS/PBCH blocks associated with one PRACH occasion and the SS /The number R of CB preambles per PBCH block may be applied by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

For a type 1 random access procedure or for a type 2 random access procedure (two-step random access procedure, message A/B) with setting of a PRACH occasion independent of the type 1 random access procedure, if N < 1. , one SS/PBCH block is mapped to 1/N consecutive valid RACH occasions, and for each valid PRACH occasion, R CB preambles with consecutive indexes associated with the SS/PBCH block index are preambled. Starting from index 0. If N>=1, then for each valid PRACH occasion R CB preambles with consecutive indexes associated with SS/PBCH block index n (0<=n<-N-1) are created with preamble index n. N_preamble^total/Starts with N. Here, N_preamble^total is given by totalNumberOfRA-Preambles for type 1 random access procedure and msgA-TotalNumberOfRA-Preambles for type 2 random access procedure with configuration of PRACH occasion independent of type 1 random access procedure. given by. N_preamble^total is a multiple of N.

Starting from frame 0, the association period for mapping SS/PBCH blocks to PRACH occasions is such that N _Tx ^SSB SS/PBCH block indexes are mapped to a PRACH occasion at least once within the association period. is the minimum value in the set determined by the PRACH configuration period according to the relationship between the PRACH configuration period and the association period (number of PRACH configuration periods) (the relationship defined in the specification). Here, the UE obtains N _Tx ^SSB from the value of SSB positions in bursts (ssb-PositionsInBurst) in SIB1 or in the common serving cell configuration (ServingCellConfigCommon). If there is a set of PRACH occasions or PRACH preambles that are not mapped to N _Tx ^SSB SS/PBCH block indices after an integer number of mapping cycles from SS/PBCH block index to PRACH occasion within the association period The SS/PBCH block index is also not mapped to a PRACH occasion or its set of PRACH preambles. The association pattern period includes one or more association periods and is determined such that the pattern between PRACH occasion and SS/PBCH block index repeats at most every 160 ms. If there is a PRACH occasion that is not associated with an SS/PBCH block index after an integer number of association periods, that PRACH occasion is not used for PRACH.

For PRACH transmissions triggered by higher layers (PRACH transmissions not triggered by PDCCH order), if ssb-ResourceList is provided, the PRACH mask index is indicated by ra-ssb-OccasionMaskIndex. The ra-ssb-OccasionMaskIndex indicates the PRACH occasion for the PRACH transmission that is associated with the selected SS/PBCH block index.

PRACH occasions are mapped consecutively for each corresponding SS/PBCH block index. The PRACH occasion indexing indicated by the mask index value is reset every SS/PBCH block index and every successive PRACH occasion mapping cycle. The UE selects the PRACH occasion indicated by the PRACH mask index value for the indicated SS/PBCH block index for PRACH transmission in the first available mapping cycle.

For the indicated preamble index, the order of PRACH occasions is as follows.
- First, increasing order of frequency resource index for frequency multiplexed PRACH occasions.
- Second, increasing order of time resource index for time multiplexed PRACH occasions within a PRACH slot.
- Third, ascending order of PRACH slot index.

For PRACH transmissions triggered in response to requests from upper layers, if csirs-ResourceList is provided, the value of ra-OccasionList indicates the list of PRACH occasions for PRACH transmissions, and the PRACH occasions are csi-RS is associated with the selected CSI-RS index indicated by . The indexing of PRACH occasions indicated by ra-OccasionList is reset every association pattern period.

For the

PRACH setting period

10, 20, 40, 80, 160 [msec], the association period is {1, 2, 4, 8, 16}, {1, 2, 4, 8}, {1, 2, 4}, {1, 2}, and {1}.

The value of the PRACH mask index value (msgA-SSB-SharedRO-MaskIndex) is associated with the allowed PRACH occasions of the SSB (the value of the PRACH occasion index).

FIG. 2A shows an example (mapping 1) of association between a PRACH occasion (RACH occasion (RO)) and a beam (SSB/CSI-RS) based on the upper layer parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB. If ssb-perRACH-OccasionAndCB-PreamblesPerSSB indicates oneHalf,n16 (N=1/2, R=16) and msg1-FDM is 4, then 4 ROs are FDMed and 1 SSB is Mapped to two ROs. Two ROs are associated with preamble indices 0 to 15, and preamble indices 0 to 15 are associated with SSOB. Thus, if N<1, one SSB is mapped to multiple ROs. This increases the capacity of the RO per beam.

FIG. 2B shows another example (mapping 2) of the association between RO and beam based on the upper layer parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB. If ssb-perRACH-OccasionAndCB-PreamblesPerSSB indicates n4,n16 (N=4, R=16), msg1-FDM is 4, and N_preamble^total is 64, then 4 ROs are FDMed in one time instance, Four SSBs are mapped to one RO. One RO is associated with SSBs 0 to 3. Preamble indexes 0 to 15 are associated with SSB0, preamble indexes 15 to 31 are associated with SSB1, preamble indexes 32 to 47 are associated with SSB2 and SSB3 is associated with preamble indexes 48 to 63, and SSB3 is associated with SSB3. In this way, the same RO is associated with different SS/PBCH block indices and different preambles use different SS/PBCH block indices. The base station can distinguish the associated SS/PBCH block index by the received PRACH.

The random access preamble can only be transmitted on the time resources specified in the random access configuration of the specification, whether it is FR1 or FR2, and the spectrum type (paired spectrum/supplementary uplink (SUL)/unpaired spectrum). (unpaired) spectrum). The PRACH configuration index is given by the upper layer parameter prach-ConfigurationIndex or, if configured, by msgA-PRACH-ConfigurationIndex. In the specification, for each value of the PRACH configuration index, the preamble format, n_f (frame number) mod x and y at y, subframe number, starting symbol, number of PRACH slots in the subframe, time domain in the PRACH slot It is associated with at least one of the PRACH occasion number N_t^RA,slot and the PRACH duration N_dur^RA.

Whether PRACH repetition is applicable to the scenarios, the types of RACH procedures triggered by different purposes are different. The type of RACH procedure may be at least one of the following:
・Contention-free random access (CFRA), PDCCH ordered RA (PDCCH ordered RA, RA initiated by PDCCH order), CFRA for beam failure recovery (BFR), CFRA for system information (SI) request, synchronization CFRA for reconfiguration with sync, etc.
- contention-based random access (CBRA), RA triggered by MAC entity, RA triggered by RRC with event, CBRA for BFR, etc.
・4 step RACH.
・2 step RACH.

(PDCCH order)
DCI format 1_0 includes a DCI format identifier field, a bit field that is always set to 1, and a frequency domain resource assignment field. If the cyclic redundancy check (CRC) of DCI format 1_0 is scrambled by C-RNTI and the frequency domain resource allocation field is all ones, then that DCI format 1_0 is for random access procedure initiated by PDCCH order and the rest The fields are random access preamble, UL/supplementary Uplink (SUL) indicator, SS/PBCH index (SSB index), PRACH mask index, and reserved bits (12 bits).

For PRACH transmissions triggered by a PDCCH order, the PRACH mask index field specifies that if the value of the Random Access Preamble Index field is non-zero, the PRACH occasion is the SS/PBCH block index indicated by the SS/PBCH block index field of the PDCCH order. Indicates the PRACH occasion of the PRACH transmission associated with.

(Random access procedure in MAC entity)
The random access procedure is initiated by the PDCCH order, by the MAC entity itself, or by RRC for specification compliant events. Only one random access procedure is ongoing within a MAC entity at any given time. The SCell random access procedure is initiated only by PDCCH orders with ra-PreambleIndex different from 0b000000.

When a random access procedure is initiated on the serving cell, the MAC entity does the following:
- If a random access procedure is initiated by a PDCCH order and the ra-PreambleIndex explicitly provided by the PDCCH is not 0b000000, or if a random access procedure is initiated for reconfiguration with synchronization, If contention-free random access resources of step RA type are explicitly provided by rach-ConfigDedicated for the BWP selected for the random access procedure, set RA_TYPE to 4-stepRA.

If the selected RA_TYPE is set to 4-stepRA, the MAC entity does the following:
- If ra-PreambleIndex is explicitly provided by PDCCH and ra-PreambleIndex is not 0b000000, set PREAMBLE_INDEX to the notified ra-PreambleIndex and select the SSB notified by PDCCH.
- If an SSB is selected as above, determine the next available PRACH occasion from the PRACH occasions allowed by the restriction given by ra-ssb-OccasionMaskIndex and corresponding to the selected SSB (MAC The entity randomly selects a PRACH occasion among consecutive PRACH occasions with equal probability, corresponding to the selected SSB, according to the specification.The MAC entity selects the next available PRACH corresponding to the selected SSB. When determining occasions, the possibility of measurement gaps may be considered).

(Time between PDCCH order reception and PRACH transmission)
If a random access procedure is initiated by a PDCCH order, the UE, if requested by higher layers, PRACH is transmitted within the selected PRACH occasion when the time is greater than or equal to N_(T,2)+Δ_BWPSwitching+Δ_Delay+T_switch [msec] (time condition). Here, N_(T,2) is the duration of N_2 symbols corresponding to the PUSCH preparation time of UE processing capability 1. It is assumed that μ corresponds to the minimum SCS setting between the subcarrier spacing (SCS) setting of the PDCCH order and that of the corresponding PRACH transmission. If the active UL BWP does not change, Δ_BWPSwitching=0, otherwise Δ_BWPSwitching is defined in the specification. In FR1, Δ_delay=0.5 msec, and in FR2, Δ_delay=0.25 msec. T_switch is the switching gap duration defined in the specification.

(PRACH occasion valid/invalid conditions (valid conditions))
All PRACH occasions are valid in paired spectrum (FDD) or SUL bands. In unpaired spectrum (TDD), PRACH occasions may comply with

regulations

1 and 2 below.
[Regulation 1]
In case the UE is not provided with tdd-UL-DL-ConfigurationCommon, the PRACH occasion within the PRACH slot does not precede the SS/PBCH block within the PRACH slot and is at least N_gap symbols from the last SS/PBCH block received symbol. If it starts later, the PRACH occasion is valid. Here, N_gap is defined in the specifications. If channelAccessMode=semistatic is provided, there is no overlap with the set of consecutive symbols before the start of the next channel occupation time that the UE does not transmit. The candidate SS/PBCH block index of the SS/PBCH block corresponds to the SS/PBCH block index provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon.
[Regulation 2]
If the UE is provided with tdd-UL-DL-ConfigurationCommon, the PRACH occasion within the PRACH slot is valid in the following cases:
- The PRACH occasion is within the UL symbol. Or
- The PRACH occasion does not precede the SS/PBCH block in the PRACH slot, but starts at least N_gap symbols after the last DL symbol and at least N_gap symbols after the last SS/PBCH block symbol. Here, N_gap is defined in the specifications. If channelAccessMode=semistatic is provided, the PRACH occasion does not overlap with the set of consecutive symbols before the start of the next channel occupation time, where there should be no transmission, as stated in the specification. The candidate SS/PBCH block index of the SS/PBCH block corresponds to the SS/PBCH block index provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon, as described in the specification.

(RAR window)
The RA response window (ra-ResponseWindow) is a time window for monitoring the RA response (RAR) (special cell (SpCell) only). The RA contention resolution timer (ra-ContentionResolutionTimer) is a timer for RA contention resolution (SpCell only). Msg. B response window is a time window for monitoring RA response (RAR) for two-step RA type (SpCell only).

In the present disclosure, SpCell, primary cell (PCell), and primary secondary cell (PSCell) may be read interchangeably.

Once the RA preamble is transmitted, the MAC entity performs actions 1 to 3 below, regardless of the possibility that a measurement gap may occur.

[Operation 1]
If a contention-free RA preamble for a BFR request is sent by the MAC entity, the MAC entity performs the following actions 1-1 and 1-2.
[[Operation 1-1]] The MAC entity starts the ra-ResponseWindow configured in the BFR configuration (BeamFailureRecoveryConfig) in the first PDCCH occasion from the end of the RA preamble transmission.
[[Operation 1-2]] While the ra-ResponseWindow is operating, the MAC entity is indicated by the search space ID (recoverySearchSpaceId) for BFR of the SpCell identified by the C-radio network temporary identifier (RNTI). Monitor PDCCH transmission in the search space.

[Operation 2]
Otherwise, the MAC entity performs the following actions 2-1 and 2-2.
[[Operation 2-1]] The MAC entity starts the ra-ResponseWindow configured in the common RACH configuration (RACH-ConfigCommon) in the first PDCCH occasion from the end of the RA preamble transmission.
[[Operation 2-2]] The MAC entity monitors the PDCCH transmission of the SpCell for RAR identified by the RA-RNTI while the ra-ResponseWindow is operating.

[Operation 3]
If the ra-ResponseWindow configured in BeamFailureRecoveryConfig expires and the PDCCH transmission on the search space indicated by recoverySearchSpaceId destined for the C-RNTI is received on the serving cell from which its preamble was transmitted, or if If the ra-ResponseWindow configured in RACH-ConfigCommon expires and a RAR containing RA preamble identifiers matching the transmitted preamble index (PREAMBLE_INDEX) is received, the MAC entity The reception is considered a failure and the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) is incremented by 1.

The MAC entity may stop ra-ResponseWindow (may stop monitoring for RARs) after successful reception of RARs containing RA preamble identifiers matching the transmitted PREAMBLE_INDEX.

There are two cases for PDCCH monitoring within the RA response window: PDCCH for base station response to BFR and PDCCH for RAR. The following may apply to both cases.

Once the MSGA (Msg.A) preamble is transmitted, the MAC entity performs actions 4 to 6 below, regardless of the possibility of a measurement gap occurring.

[Operation 4]
The MAC entity performs Msg. Start the B response window (msgB-ResponseWindow).

msgB-ResponseWindow is the first of the earliest CORESET the UE is configured to receive a PDCCH for type 1-PDCCH CSS set that is at least one symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission. It may start at the symbol. The length of msgB-ResponseWindow may correspond to the SCS for Type 1-PDCCH CSS set.

[Operation 5]
The MAC entity monitors the PDCCH transmission of the SpCell for the RAR identified by the MSGB-RNTI while the msgB-ResponseWindow is active.

[Operation 6]
If the C-RNTI MAC CE is included in its MSGA, the MAC entity monitors the PDCCH transmission of the SpCell for the RAR identified by the C-RNTI while the msgB-ResponseWindow is active.

The RA-RNTI associated with the PRACH occasion where the RA preamble is sent is calculated as follows.
RA-RNTI = 1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

Here, s_id is the index of the first OFDM symbol of the PRACH occasion (0<=s_id<14). t_id is the index of the first slot of the PRACH occasion within the system frame (0<=t_id<80). The subcarrier spacing (SCS) for determining t_id is based on the value of μ. f_id is the index of the PRACH occasion in the frequency domain (0<=f_id<8). ul_carrier_id is the UL carrier used for RA preamble transmission (0 for normal uplink (NUL) carriers, 1 for supplementary uplink (SUL) carriers). RA-RNTI is calculated according to specifications. RA-RNTI is an RNTI for 4-step RACH.

The MSGB-RNTI associated with the PRACH occasion where the RA preamble is sent is calculated as follows.
MSGB-RNTI = 1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2

Here, s_id is the index of the first OFDM symbol of the PRACH occasion (0<=s_id<14). t_id is the index of the first slot of the PRACH occasion within the system frame (0<=t_id<80). The subcarrier spacing (SCS) for determining t_id is based on the value of μ. f_id is the index of the PRACH occasion in the frequency domain (0<=f_id<8). ul_carrier_id is the UL carrier used for RA preamble transmission (0 for normal uplink (NUL) carriers, 1 for supplementary uplink (SUL) carriers). MSGB-RNTI is an RNTI for 2-step RACH.

(RAR monitoring)
In response to the PRACH transmission, the UE attempts to detect DCI format 1_0 with the CRC scrambled by the corresponding RA-RNTI during the window controlled by the above-mentioned upper layers. In the first symbol of the earliest CORESET in which the UE is configured to receive a PDCCH for a type 1-PDCCH CSS set, i.e. at least one symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission, the window Start. The symbol period corresponds to the SCS for Type 1-PDCCH CSS set. The length of the window is based on the SCS for type 1-PDCCH CSS set and is provided by ra-responseWindow as the number of slots.

If the UE has a CRC scrambled by the corresponding RA-RNTI and the LSBs of the SFN field in the DCI format are the same as the least significant bits (LSBs) of the system frame number (SFN) for which the UE sent the PRACH. If the UE detects the DCI format 1_0 and receives the transport block in the corresponding PDSCH, the UE determines the TCI state (TCI-State) for the CORESET in which the UE receives the PDCCH with the DCI format 1_0. The UE may assume the same DMRS antenna port QCL properties for the SS/PBCH block or CSI-RS resources that the UE uses for PRACH association, whether provided or not.

If the UE attempts to detect a DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order triggering a CFRA procedure for the SpCell, the UE detects that DCI format It may be assumed that the PDCCH including 1_0 and its PDCCH order have the same DMRS antenna port QCL properties. If the UE attempts to detect a DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order that triggers a CFRA procedure for the secondary cell, the UE The DMRS antenna port QCL properties of the CORESET associated with the Type 1-PDCCH CSS set for reception of PDCCHs including format 1_0 may be assumed.

The RAR UL grant includes a frequency hopping flag field, a PUSCH frequency resource allocation field, a PUSCH time resource allocation field, a modulation and coding scheme (MCS) field, a PUSCH TPC command field, a CSI request field, Channel access may include at least one of a cyclic prefix extension (CPext) field.

In single cell operation or operation with carrier aggregation within the same frequency band, if the qcl-Type set in the 'typeD' properties of the DMRS for monitoring PDCCH in the Type 1-PDCCH CSS set is Type 0/0A/0B/2/3-PDCCH is not set the same as the qcl-Type set in the 'typeD' characteristic of the DMRS for PDCCH monitoring in the CSS set or in the USS set, and , if its PDCCH or associated PDSCH overlaps in at least one symbol with the PDCCH or associated PDSCH monitored by the UE in the Type 1-PDCCH CSS set, the UE /2/3-PDCCH It is not assumed that the PDCCH in the CSS set or in the USS set is monitored.

If the UE is provided with one or more search space sets by corresponding one or more of searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, peiSearchSpace, ra-SearchSpace, CSS set by PDCCH-Config. , and SI-RNTI, P-RNTI, PEI-RNTI, RA-RNTI, MsgB-RNTI, SFI-RNTI, INT-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI If provided, for an RNTI from any of these RNTIs, the UE does not assume that it processes information from more than one DCI format with scrambled CRC with that RNTI per slot.

(Msg3 PUSCH)
The UE sends transport blocks on the PUSCH scheduled by the RAR UL grant in the corresponding RAR message. The UE transmits its PUSCH within slot n+k ₂ +Δ+2 ^μ ·K _cell,offset . K _cell,offset is provided by CellSpecific_Koffset, if not provided, K _cell,offset =0.

_k2 is the slot offset, determined based on the row index m+1 of the allocation table provided by the PUSCH time resource allocation field value m of the RAR UL grant, and the PUSCH subcarrier spacing μPUSCH. . Δ is the additional subcarrier spacing specific slot delay time value for the first transmission of the PUSCH scheduled by the RAR, which is specific to the PUSCH subcarrier spacing μPUSCH and is applied in addition to K ₂ .

If a UE requests repeat for PUSCH transmission, the UE transmits PUSCH for N _PUSCH ^repeat slots. Here, N _PUSCH ^repeat is the MCS in RAR UL grant or DCI format 0_0 from the set of 4 values provided by numberOfMsg3Repetitions or from {1,2,3,4} if numberOfMsg3Repetitions is not provided. Indicated by the 2MSB of the field.

The UE determines whether to apply Msg3 repetition based on RSRP. If Msg repetition is configured and the RSRP of DL path loss reference is less than rsrp-ThresholdMsg3, the MAC entity assumes that Msg3 repetition is applicable to the current random access (RA) procedure.

The UE can request Msg3PUSCH repetition via a separate PRACH resource. If there is one or more sets of RA resources available, and one of the one or more sets is used to direct all functions that trigger this RA procedure, and all functions that trigger this RA procedure The MAC entity selects an RA resource if and when there is one or more sets of available RA resources configured with instructions for a subset of the functionality of the MAC entity. If Msg3 repetition indication is configured for a set of RA resources, and Msg3 repetition is not available, the MAC entity considers that set of RA resources not available for RACH procedures.

RA resources may be partitioned for each function. The functionality may include at least one of Msg3 repetition, reduced capacity (RedCap), small data transmission (SDT), and RAN slicing.

In SIB1 sent by the base station, the following is announced:
-Priority of each feature (priority, featurePriorities-r17). This priority is used to determine which FeatureCombinationPreambles the UE uses if a feature is mapped to more than one FeatureCombinationPreambles.
・Additional RO settings. The configuration includes available capabilities (which may be associated with multiple capabilities), RA resources (eg, preamble index), and a mask index for distinguishing ROs.

The UE decides which RO to use depending on its capabilities.

SIB1 includes ServingCellConfigCommonSIB. It includes UplinkConfigCommonSIB. It includes BWP-UplinkCommon (UL BWP common settings).

BWP-UplinkCommon may include RACH common settings (RACH-ConfigCommon or MsgA-ConfigCommon) and additionalRACH-ConfigList-r17 (additional RACH configuration list). additionalRACH-ConfigList-r17 may include rsrp-ThresholdMsg3-r17 (threshold).

The RACH common settings may include FeatureCombinationPreambles. FeatureCombinationPreambles associates one set (partition) of preambles with one feature combination. FeatureCombinationPreambles may include FeatureCombination (feature combination setting), startPreambleForThisPartition (index of first preamble), numberOfPreamblesPerSSB-ForThisPartition (number of preambles), and ssb-SharedRO-MaskIndex-r17 (PRACH mask index). FeatureCombination includes at least one of redCap (RedCap), smallData (SDT), sliceGroup (RAN slicing), and msg3-Repetition (Msg3 repetition). The partition is given by the index of the first preamble and the preamble number.

Available ROs are explicitly set by the PRACH mask index. At least one of the PRACH occasion indexes 1 to 8 may be set using the relationship between the PRACH mask index and the allowed PRACH occasions (ROs) of the SSB (MAC protocol specification/PRACH mask index value table). can.

The number of Msg3 repetitions is indicated by the 2 most significant bits (MSB) (upper 2 bits) of the modulation and coding scheme (MCS) field in the RAR UL grant.

In PUSCH repetition type A, when transmitting a PUSCH scheduled by a RAR UL grant, the 2MSBs of the MCS information field of the RAR UL grant are set based on whether the upper layer parameter numberOfMsg3Repetitions is set. Code points for determining the number of repetitions K are provided according to the relationship (table) between the values (code points) and the number of repetitions K. The number of slots N used for transport block size (TBS) determination is equal to one.

In PUSCH repetition type B, when transmitting a PUSCH scheduled by DCI format 0_0 with CRC scrambled by TC-RNTI, the 2MSB of the MCS information field of that DCI format determines whether the upper layer parameter numberOfMsg3Repetitions is set or not. Based on the relationship (table) between the 2MSB value (code point) of the MCS information field and the repetition number K, code points for determining the repetition number K are provided. The number of slots N used for TBS determination is equal to 1.

(contention resolution)
Once Msg3 is sent, the MAC entity follows actions 1 to 4 below.
[Action 1] If Msg3 is transmitted on a non-terrestrial network, its MAC entity starts an ra-ContentionResolutionTimer and specifies the content in the first symbol after the end of Msg3 plus the UE estimate of the UE-gNB RTT. Resume at each HARQ retransmission.
[Action 2] Otherwise, if the Msg3 transmission (first transmission or HARQ retransmission) is scheduled with type A PUSCH repetitions, the MAC entity Start or restart the ra-ContentionResolutionTimer within the symbol.
[Operation 3] Otherwise, the MAC entity starts or restarts the ra-ContentionResolutionTimer within the first symbol after the end of its Msg3 transmission.
[Action 4] The MAC entity monitors the PDCCH while the ra-ContentionResolutionTimer is running, regardless of the possibility of a measurement gap occurring.

Rel. Step 4 (Msg4) in the RA procedure of 16 NR follows the following Step 4 operation.

[Step 4 operation]
If the UE is not provided with a C-RNTI, in response to the PUSCH transmission scheduled by the RAR UL grant, the UE shall schedule a PDSCH containing the UE contention resolution identity with a CRC scrambled by the corresponding TCI-RNTI. Attempt to detect DCI format 1_0. In response to receiving the PDSCH including the UE contention resolution identity, the UE transmits HARQ-ACK information in the PUCCH. PUCCH transmissions are within the same active UL BWP as PUSCH transmissions. The minimum time between the last symbol of PDSCH reception and the first symbol of the corresponding PUCCH transmission containing HARQ-ACK information is equal to N_T,1 [msec]. N_T,1 is the duration of N_T,1 symbol corresponding to the PDSCH processing time of UE processing capacity 1 when additional PDSCH DM-RS is configured. For μ=0, the UE assumes N_T,1=14.

DCI format in response to a PUSCH transmission scheduled by RAR UL grant or in response to a corresponding PUSCH retransmission scheduled by DCI format 0_0 with CRC scrambled by TC-RNTI provided in the corresponding RAR message. If the UE detects that the PDCCH carrying that DCI format is used by the UE for PRACH association, regardless of whether the UE is provided with TCI status for the CORESET in which the UE received the PDCCH with that DCI format. The same DM-RS antenna port QCL properties as the DM-RS antenna port quasi co-location (QCL) properties for the SS/PBCH block may be assumed.

(PUCCH before individual PUCCH resource configuration)
If the UE does not have a separate PUCCH resource configuration provided by the PUCCH-ResourceSet in the PUCCH-Config, for the transmission of HARQ-ACK information on the PUCCH in the initial UL BWP of N _BWP ^size PRBs. The PUCCH resource set (default PUCCH resource) is provided by pucch-ResourceCommon through an index to the row of the table of multiple PUCCH resource sets (default PUCCH resource table, Figure 3) before individual PUCCH resource configuration specified in the specification. be done.

pucch-ResourceCommon included in SIB1 indicates index values 0 to 15. A default PUCCH resource table associates an index with a PUCCH resource set. Each PUCCH resource set includes a PUCCH format 0/1, a PUCCH first symbol, a PUCCH symbol number, a PUCCH PRB offset, and a set of initial cyclic shift indexes. The UE determines the PUCCH resource in the PUCCH resource set indicated by the index based on the PDCCH (first CCE of that PDCCH, PUCCH resource indicator field in DCI) on which to schedule the PDSCH.

The UE transmits the PUSCH using the same spatial domain transmit filter as the PUSCH transmission scheduled by the RAR UL grant.

If the UE is not provided with pdsch-HARQ-ACK-Codebook, pdsch-HARQ-ACK-Codebook-r16, pdsch-HARQ-ACK-OneShotFeedback, the UE generates at most one HARQ-ACK information bit. do.

(problem)
In the examples of FIGS. 4A, 4B, 5A, 5B, 6 for the following problems, the UE transmits PRACH repetitions (Msg1 #1 to #4) and starts a RAR window after each repetition.

In multiple PRACH repetitions involving multiple Msg2/3/4, the following several problems can be considered.

- Overlapping of multiple RAR windows.
[Problem 1] Maintenance of RAR window, monitoring/processing of PDCCH within overlapping RAR windows (FIG. 4A) is not clear.

- Overlapping of multiple Msg3s each scheduled by multiple RARs.
[Problem 2] Msg3 PUSCH transmission operation (Fig. 4B) is not clear.

- Overlapping multiple conflict resolution windows.
[Problem 3] Maintenance of multiple contention resolution windows and monitoring of PDCCHs within overlapping contention resolution windows (FIG. 5A) are not clear.

- Overlapping one or more RAR windows with one or more conflict resolution windows.
[Problem 4] Monitoring/processing of PDCCH within overlapping RAR windows/conflict resolution windows (FIG. 5B) is not clear.

- HARQ-ACK feedback for multiple Msg4.
[Problem 5] In the existing specifications, the UE does not support more than one HARQ-ACK information bit per PUCCH before dedicated PUCCH resource (RRC) configuration. The UE behavior is not clear if multiple HARQ-ACK information bits for multiple Msg4 PDSCHs are in the same slot (FIG. 6).

If such operations are not clear, there is a risk of deterioration in communication quality.

Therefore, the present inventors came up with an idea for the operation associated with PRACH repetition.

Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Note that each of the following embodiments (for example, each case) may be used alone, or may be applied in combination of at least two.

In the present disclosure, "A/B" and "at least one of A and B" may be read interchangeably. Furthermore, in the present disclosure, "A/B/C" may mean "at least one of A, B, and C."

In the present disclosure, "activate", "deactivate", "indicate", "select", "configure", "update", "determine", etc. may be read interchangeably. In this disclosure, supporting, controlling, being able to control, operating, capable of operating, etc. may be read interchangeably.

In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, upper layer parameters, information elements (IEs), settings, etc. may be read interchangeably. In the present disclosure, the terms Medium Access Control Element (CE), update command, activation/deactivation command, etc. may be read interchangeably.

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

In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), or the like. Broadcast information includes, for example, a master information block (MIB), a system information block (SIB), a minimum system information (RMSI), and other system information ( Other System Information (OSI)) may also be used.

In the present disclosure, the physical layer signaling may be, for example, downlink control information (DCI), uplink control information (UCI), etc.

In this disclosure, an index, an identifier (ID), an indicator, a resource ID, etc. may be read interchangeably. In this disclosure, sequences, lists, sets, groups, groups, clusters, subsets, etc. may be used interchangeably.

In the present disclosure, a panel, a panel group, a beam, a beam group, a precoder, an uplink (UL) transmitting entity, a transmission/reception point (TRP), a base station, a spatial relation information (SRI), Spatial relationship, SRS resource indicator (SRI), control resource set (CONtrol REsource SET (CORESET)), Physical Downlink Shared Channel (PDSCH), codeword (CW), transport block (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 (for example, 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 (unified TCI state, common TCI state, quasi-co-location (QCL), QCL assumption, etc. may be read interchangeably.

In this disclosure, "having the ability to..." may be interchanged with "supporting/reporting the ability to...".

In the present disclosure, the SSB/CSI-RS index/indicator, beam index, TCI state, spatial domain transmit filter, and spatial domain receive filter may be read interchangeably.

In the present disclosure, the terms RAR window, ra-ResponseWindow, time window, RAR timer, and timer operation period may be read interchangeably. In this disclosure, the terms conflict resolution window, conflict window, conflict resolution timer, ra-ContentionResolutionTimer, and operation period of the conflict resolution timer may be read interchangeably. In this disclosure, contention resolution identity, contention resolution ID, and UE contention resolution identity may be interchanged.

In the present disclosure, the terms port, antenna port, DMRS port, and DMRS antenna port may be read interchangeably. In this disclosure, the terms that a port is QCLed with the reception of the RS and that the port uses the same spatial domain (transmission/reception) filter as the reception of the RS may be read interchangeably.

In this disclosure, DCI (format)/PDCCH (candidate) with a CRC scrambled by a specific RNTI, DCI (format)/PDCCH (candidate) using a specific RNTI, DCI (format)/PDCCH (candidate) monitored using a specific RNTI, PDCCH (candidate) may be read interchangeably.

(Wireless communication method)
In each embodiment, RACH resource, RA resource, PRACH preamble, occasion, RACH occasion (RO), PRACH occasion, repetition resource, repetition configuration resource, resource configured for RO/repetition, time instance and frequency instance, time Resources and frequency resources, RO/preamble resources, and repetition may be read interchangeably. In each embodiment, period, period, frame, subframe, slot, symbol, occasion, and RO may be read interchangeably.

In each embodiment, PDCCH order, PDCCH order DCI, DCI format 1_0, and message (Msg) 0 may be read interchangeably. In each embodiment, PRACH, preamble, PRACH preamble, sequence, preamble format, and Msg1 may be read interchangeably. In each embodiment, a response to PRACH, RAR, Msg2, MsgB, Msg4, a base station response to BFR, and DCI scheduling response (RAR) may be read interchangeably. In each embodiment, transmissions other than PRACH in the random access procedure, Msg3, PUSCH scheduled by RAR, HARQ-ACK/PUCCH for Msg4, and MsgA PUSCH may be interchanged. In each embodiment, Msg3, PUSCH scheduled by RAR UL grant, and RRC connection request may be interchanged. In each embodiment, Msg4, contention resolution, RRC connection setup, and PDSCH with UE contention resolution identity may be interchanged.

In each embodiment, RAR, DCI that schedules RAR (PDCCH), PDSCH with UE contention resolution ID, and DCI that schedules PDSCH with UE contention resolution ID may be read interchangeably.

In each embodiment, beam, SSB, SSB index, CSI-RS, CSI-RS resource, CSI-RS resource index, and RS may be read interchangeably.

In each embodiment, a random access (RA) procedure, CFRA/CBRA, 4-step RACH/2-step RACH, a specific type of random access procedure, a random access procedure using a specific PRACH format, a random access procedure initiated by a PDCCH order. , a random access procedure not initiated by a PDCCH order, and a random access procedure initiated by an upper layer may be interchanged.

In each embodiment, time resources, Msg1, Msg2, Msg3, Msg4, HARQ-ACK information, RAR window, conflict resolution window, DCI that schedules Msg2, and DCI that schedules Msg4 may be read interchangeably. In the operation of each embodiment, the earlier time resource may be a time resource earlier than the operation among a plurality of time resources corresponding to a plurality of repetitions of PRACH, or an index (time domain index), it may be a time resource that has a smaller index than the index of its operation. In the operation of each embodiment, a later time resource may be a time resource later than the operation among a plurality of time resources corresponding to a plurality of repetitions of PRACH, or an index (time domain index), it may be a time resource that has a larger index than the index of its operation.

<Embodiment #1>
This embodiment relates to problem 1. One or more RARs for multiple PRACH repetitions with same/different beams may follow any of several options below.

《Option 1》
Only one RAR window (ra-ResponseWindow) is maintained. A common ra-ResponseWindow may be maintained for multiple iterations. The UE may follow any of several options below.

[Option 1-1]
The UE does not assume overlapping (in the time domain) of multiple RAR windows for multiple PRACH repetitions. In the example of FIG. 7A, the UE transmits multiple repetitions of PRACH (Msg1 #1 to #4). For each iteration, start a RAR window. The UE may follow at least one of several examples below.
[[Example 1]] The UE does not (does not assume to send) (later) PRACH repetitions when ra-ResponseWindow is operating.
[Example 2] The UE does not transmit (is not expected to transmit) a later PRACH repetition before detection of the RAR for the earlier PRACH transmission. The RAR may include a preamble identifier that matches the transmitted preamble index.
[[Example 3]] The UE does not assume that the length of the ra-ResponseWindow is longer than the gap of two PRACH repetitions.

[Option 1-2]
If ra-ResponseWindow is active and the UE sends a later PRACH repetition, the UE sends a message from the first PDCCH occasion after the later PRACH repetition or from the start of the later PRACH repetition. /Restart ra-ResponseWindow from the end. In the example of FIG. 7B, the UE transmits multiple repetitions of the PRACH (Msg1 #1 to #4) and starts a RAR window after each repetition. If the UE transmits the next Msg1 while the RAR window is in operation, the UE may stop the RAR window in operation.

When ra-ResponseWindow is running, RAR monitoring operations may follow any of several options below.
[[Option 1-2a]] The UE assumes that the DMRS antenna port is QCLed with reception of SSB/CSI-RS for multiple PRACH repetitions before the PDCCH monitoring occasion and for PRACH repetitions where no corresponding RAR is detected. RAR using RA-RNTI may be monitored. This option may be applicable for PRACH repetitions using the same beam.
[[Option 1-2b]] The UE performs RAR with RA-RNTI for the last PRACH repetition assuming the DMRS antenna port is QCLed with the reception of SSB/CSI-RS for that last PRACH repetition. Monitor. This option may be applicable to PRACH repetitions with the same beam and PRACH repetitions with different beams.

[[analysis]]
From the base station's perspective, the base station is not aware that the RAR window is shorter than the configured length. It may be possible for the base station to send an RAR for a previous PRACH repetition after a later PRACH repetition. In such cases, the UE may fail to receive RARs for previous PRACH repetitions.

[Option 1-3]
The UE resumes the ra-ResponseWindow for the later PRACH repetition after successfully receiving the RAR for the earlier PRACH repetition or after the expiration of the ra-ResponseWindow. In the example of FIG. 8, the UE transmits multiple repetitions of the PRACH (Msg1 #1 to #4) and starts a RAR window after each repetition. After successfully receiving the RAR for Msg1#1, the UE starts the next ra-ResponseWindow for Msg1#2. After the ra-ResponseWindow for Msg1#2 expires, the UE restarts the ra-ResponseWindow for Msg1#3. After successfully receiving the RAR for Msg1#3, the UE starts the next ra-ResponseWindow for Msg1#4.

[[example]]
If the UE transmits a later PRACH repetition before the detection of the RAR (containing a preamble identifier matching the transmitted preamble index) for the earlier PRACH repetition and before the expiration of the ra-ResponseWindow. When restarting the ra-ResponseWindow after expiration of the ra-ResponseWindow, or after detection of an RAR for an earlier PRACH repetition, the UE may follow at least one of several actions below.
- Before restarting the ra-ResponseWindow, the UE performs RAR using RA-RNTI for the previous PRACH repetition, assuming the DMRS antenna port is QCLed with reception of SSB/CSI-RS for that PRACH repetition. may be monitored.
- After restarting the ra-ResponseWindow, the UE performs RAR with RA-RNTI for a later PRACH repetition, assuming the DMRS antenna port is QCLed with the reception of SSB/CSI-RS for that PRACH repetition. May be monitored.

[[analysis]]
From the base station's perspective, the base station is not aware that the RAR window starts later than expected. It may be possible for the base station to send the RAR for a later PRACH repetition before the end of the RAR window for the earlier PRACH repetition. In such cases, the UE may fail to receive RARs for later PRACH repetitions.

[[analysis]]
The UE needs to keep track of how many windows are maintained/reserved. For example, the UE sends three PRACH repetitions before the end of the RAR window for the first PRACH repetition.

《Option 2》
A separate RAR window (ra-ResponseWindow) is maintained for each PRACH repetition. Multiple RAR windows for multiple PRACH repetitions may follow any of several options below.

[Option 2-1]
Overlapping (in the time domain) of multiple RAR windows is not allowed. It may be specified that the UE does not assume overlapping of multiple RAR windows. The UE may follow at least one of several examples below.
[Example 1] The UE does not (assumes not to) send later PRACH repetitions if any ra-ResponseWindow is active.
[Example 2] The UE does not (assumes not to) transmit a later PRACH repetition before detection of the RAR for the earlier PRACH repetition. The RAR may include a preamble identifier that matches the transmitted preamble index.
[Example 3] The UE does not assume that the start of a later PRACH repetition (or RAR window for a later PRACH repetition) is before the end of the previous RAR window.

[[analysis]]
If there is no overlapping of multiple RAR windows, the UE does not need to maintain a separate ra-ResponseWindow timer for each PRACH repetition.

[Option 2-2]
Overlapping (in the time domain) of multiple RAR windows is allowed. In the example of FIG. 9, the UE transmits multiple repetitions of the PRACH (Msg1 #1 to #4) and starts a RAR window after each repetition. The UE may use only one QCL assumption for receiving RARs in multiple RAR windows that overlap with each other.

In multiple PDCCH monitoring scenarios of type 1 CSS for multiple RAR windows, the UE monitors PDCCH candidates with RA-RNTI, assuming the DMRS antenna port is QCLed with reception of one of several options below: You may.
[[Option 2-2a]] Reception of SSB/CSI-RS corresponding to the PRACH repetition corresponding to the first/last RAR window of the multiple RAR windows.
[[Option 2-2b]] One SSB/CSI-RS (or randomly selected (or one SSB/CSI-RS selected based on a method that depends on the UE implementation).

《Variation of option 2》
The base station may set/indicate different values (number of symbols/slots) of the RAR window length corresponding to different repetition indices.

[[example]]
The RAR window length may be set individually for each iteration. For example, length 1 may be set for the first repetition, and length 2 may be set for the second repetition.

[[example]]
The RAR window length for the first/last PRACH repetition may be longer/shorter than the RAR window length for other PRACH repetitions. This example may be applicable for cases where the base station can identify the first/last PRACH repetition. For example, the case may be that the RACH resources for the first PRACH repetition are configured independently from the RACH resources for other PRACH repetitions. For example, the case may be that multiple RACH resources for multiple PRACH repetitions are configured individually and in fixed/unique locations for each PRACH repetition.

[[analysis]]
This variation may not be useful if the base station does not know which repetition the received Msg1 is.

According to this embodiment, the UE can maintain one or more RAR windows appropriately.

<Embodiment #2>
This embodiment relates to problem 1. Monitoring of PDCCH to schedule RAR may follow any of several embodiments below.

《Embodiment #2-1》
In monitoring/processing RAR within one slot, the UE may process/monitor up to X (X≧1) DCI formats with CRC scrambled by RA-RNTI per slot. X (maximum number) may follow any of several options below.
[Choice a] Rel. It will not be expanded from 15/16/17. That is, X=1. Rel. The restrictions for 15/16/17 are that the UE can use SI-RNTI, P-RNTI, PEI-RNTI, RA-RNTI, MsgB-RNTI, SFI-RNTI, INT-RNTI, TPC-PUSCH-RNTI, TPC - It may not be assumed to process information for more than one DCI format with CRC scrambled by PUCCH-RNTI or TPC-SRS-RNTI.
[Option b] X may be greater than 1. X may be defined in the specification or may be reported by the UE as a UE capability. The specification may define possible values for X for UE capability reporting.

UE behavior for RAR monitoring when there is more than one PDCCH monitoring occasion of type 1 CSS within one slot may follow at least one of several options below.

[Option 1]
The UE does not assume that there are slots that overlap with more than X RAR windows for different PRACH repetitions.

In a combination of Option 1 of Embodiment #1 and Option 1 of Embodiment #2-1, at least one of the following examples may be followed.
[[Example]] The UE does not transmit (or is not expected to transmit) (later) PRACH repetitions within the slot in which ra-ResponseWindow is operating.
[[Example]] The UE does not transmit (or is not expected to transmit) (later) PRACH repetitions within the slot in which the ra-ResponseWindow is started/restarted X'(X'≧1) times.
[[Example]] The UE does not transmit (sends) a (later) PRACH repetition in the slot in which it has detected X'(X' ≧ 1) RAR messages for one or more earlier PRACH repetitions. (not assumed). The RAR message may include a preamble identifier that matches the transmitted preamble index.
[[Example]] The RAR window for a later PRACH repetition starts from the slot after the slot in which X'(X'≧1) RAR messages for one or more earlier PRACH repetitions were successfully detected. .

In a combination of Option 2 of Embodiment #1 and Option 1 of Embodiment #2-1, at least one of the following examples may be followed.
[Example] The UE does not transmit (or is not expected to transmit) (later) PRACH repetitions within the slot in which at least N (N≧1) ra-ResponseWindows are operating.

[Option 2]
If there are slots that overlap with more than X RAR windows, the UE may follow at least one of several options:
[[Option 2-1]] The UE does not assume multiple PDCCH monitoring occasions of type 1 CSS in more than X RAR windows within one slot.
[[Option 2-2]] If the UE successfully detects X RARs on multiple PDCCH monitoring occasions within an earlier RAR window within one slot, the UE shall - Do not monitor RAR on later type 1 CSS PDCCH monitoring occasions using RNTI.
[[Option 2-3]] The UE monitors PDCCH monitoring occasions of type 1 CSS with RA-RNTI in up to X RAR windows within its slot. The X RAR windows may be the first/last X RAR windows corresponding to the reception of Y SSB/CSI-RSs from the maximum RSRP among the multiple receptions of SSB/CSI-RSs for the detected multiple RARs. It may be a RAR window of
[[Option 2-4]] The UE monitors all type 1 CSS PDCCH monitoring occasions using RA-RNTI within one slot and processes only X RARs among the detected multiple RARs. do. The X RARs may be the first/last detected RARs, the randomly selected X detected RARs, or the The reception of Y SSB/CSI-RSs from the maximum RSRP among the multiple receptions of SSB/CSI-RSs for multiple detected RARs. may be X RARs corresponding to .

The maximum number The specification may define a maximum number of possible values for UE capability reporting.

Option 1/2 may be applicable for the case of X=1 where there is no UE capability expansion. Option 1/2 may be applicable for the case where X>1 with UE capability expansion.

《Embodiment #2-2》
For multiple PRACH repetitions with different beams, the UE processes/processes one or more DCI formats with up to Y (Y≧1) different beams and CRC scrambled by RA-RNTI per slot. May be monitored. Y (maximum number) may be defined in the specification, may be configured/indicated by the SIB/RRC IE, or may be reported by the UE as a UE capability. The specification may define possible values for Y for UE capability reporting.

[Option 1]
The UE does not assume that there are slots that overlap (in the time domain) with more than Y RAR windows for different PRACH repetitions with different beams.

In a combination of Option 1 of Embodiment #1 and Option 1 of Embodiment #2-2, at least one of the following examples may be followed.
[[Example]] The UE does not transmit (or is not expected to transmit) (later) PRACH repetitions using different beams within the slot in which ra-ResponseWindow is operating.
[[Example]] The UE does not transmit (later) PRACH repetitions using different beams within the slot in which ra-ResponseWindow is started/restarted Y'(Y' ≧ 1) times (assuming that it does) do not).
[[Example]] The UE does not transmit (sends) a (later) PRACH repetition within the slot in which it has detected Y'(Y' ≧ 1) RAR messages for one or more earlier PRACH repetitions. (not assumed). The RAR message may include a preamble identifier that matches the transmitted preamble index.
[[Example]] The RAR window for a later PRACH repetition starts from the slot after the slot in which X'(X'≧1) RAR messages for one or more earlier PRACH repetitions were successfully detected. .

The maximum number X'/maximum number Y' may be defined in the specifications, may be set/instructed by the SIB/RRC IE, or may be reported by the UE as a UE capability. The specification may define a maximum number of possible values for UE capability reporting.

In a combination of Option 2 of Embodiment #1 and Option 1 of Embodiment #2-2, at least one of the following examples may be followed.
[Example] The UE does not transmit (or is not expected to transmit) (later) PRACH repetitions within the slot in which at least N (N≧1) ra-ResponseWindows are operating.

[Option 2]
If there are slots that overlap (in the time domain) with more than Y RAR windows for different PRACH repetitions with different beams, the UE may follow at least one of several options:
[[Option 2-1]] The UE does not assume multiple PDCCH monitoring occasions of type 1 CSS in more than Y RAR windows within one slot.
[[Option 2-2]] If the UE successfully detects Y RARs on multiple PDCCH monitoring occasions within an earlier RAR window within one slot, the UE shall detect Y RARs on multiple PDCCH monitoring occasions within the same slot. - Do not monitor RAR on later type 1 CSS PDCCH monitoring occasions using RNTI.
[[Option 2-3]] The UE monitors PDCCH monitoring occasions of type 1 CSS with RA-RNTI in up to Y RAR windows within its slot. The Y RAR windows may be the first/last Y RAR windows, or may be randomly selected Y RAR windows, or may be selected based on a method that is up to the UE implementation. may be Y RAR windows corresponding to the reception of Y SSB/CSI-RSs from the maximum RSRP among the multiple receptions of SSB/CSI-RSs for the detected multiple RARs. It may be a RAR window of
[[Option 2-4]] The UE monitors all Type 1 CSS PDCCH monitoring occasions using RA-RNTI within one slot and processes only Y RARs among the detected RARs. do. The Y RARs may be the first/last Y detected RARs, the randomly selected Y detected RARs, or in a manner that depends on the UE implementation. The reception of Y SSB/CSI-RSs from the maximum RSRP among the multiple receptions of SSB/CSI-RSs for multiple detected RARs may be selected based on the Y detected RARs. may be Y RARs corresponding to .

According to this embodiment, the UE can appropriately monitor/process PDCCH candidates for RAR.

<Embodiment #3>
This embodiment relates to problem 2. The Msg3 PUSCH corresponding to the received RARs may follow at least one of the following several cases.

《Case 1》
The case where the multiple Msg3 PUSCHs do not overlap in the time domain or the gap between the multiple Msg3 PUSCHs is greater than or equal to the gap (time) required for beam switching.

In this case, the UE may follow any of several options below.

[Option 1-1] The UE transmits each Msg3 PUSCH.

[Option 1-2] The UE transmits up to X (X=1 or X>1) Msg3 PUSCH in one slot. X (maximum number) may be defined in the specification, may be configured/indicated by the SIB/RRC IE, or may be reported by the UE as a UE capability. Up to X Msg3 PUSCHs may be one of several options below.
[[Option 1-2A]] First/last Msg3 PUSCH among multiple Msg3 PUSCHs in that slot/slot group.
[[Option 1-2B]] X Msg3 PUSCHs scheduled by the first/last detected X RARs among the RARs for Msg3 PUSCHs in that slot/slot group.
[[Option 1-2C]] X corresponding to X receptions of SSB/CSI-RS from the highest RSRP among multiple receptions of SSB/CSI-RS for multiple Msg3 PUSCH in that slot/slot group Msg3 PUSCH.
[[Option 1-2D]] X Msg3 PUSCHs randomly selected among multiple Msg3 PUSCHs in that slot/slot group, or X Msg3 PUSCHs selected by a method that depends on the UE implementation.

《Case 2》
The multiple Msg3 PUSCHs overlap in the time domain, or the gap between the multiple Msg3 PUSCHs is shorter than the gap (time) required for beam switching.

In this case, the UE may transmit one of multiple Msg3 PUSCHs that overlap with each other.

In this case, the UE may follow any of several options below.

[Option 2-1] The UE selects the first/last Msg3 PUSCH among multiple Msg3 PUSCHs that overlap each other in the time domain, or the Msg3 PUSCH scheduled by the first/last received RAR. Scheduled by the first/last Msg3 PUSCH or first/last received RAR of two non-overlapping PUSCHs with a gap shorter than that required for beam switching. Transmit Msg3 PUSCH.

[Option 2-2] The UE transmits Msg3 PUSCH corresponding to reception of the SSB/CSI-RS with the highest RSRP.

[Option 2-3] The UE transmits Msg3 PUSCH scheduled by RAR indicating the minimum number of Msg3 repetitions.

[Option 2-4] The UE transmits a Msg3 PUSCH that is randomly selected from among multiple Msg3 PUSCHs that overlap each other in the time domain, or a Msg3 PUSCH that is selected by a method that depends on the UE implementation. .

According to this embodiment, the UE can appropriately transmit one or more Msg3 to multiple received RARs.

<Embodiment #4>
This embodiment relates to problem 3. For Msg3 PUSCH for PRACH repetitions with same beam/different beams, one or more contention resolution windows may follow any of several options below.

《Option 1》
Only one conflict resolution window is maintained. A common contention resolution timer (ra-ContentionResolutionTimer) may be maintained for multiple iterations. The UE may follow at least one of several options below.

[Option 1-1]
The UE does not assume overlapping (in the time domain) of multiple contention resolution windows for multiple Msg3 PUSCHs scheduled by multiple RARs. The UE may follow at least one of several examples below.
[[Example 1]] The UE does not transmit (or does not assume to transmit) (later) Msg3 PUSCH when the ra-ContentionResolutionTimer is operating.
[[Example 2]] The UE schedules a PDSCH that includes the UE Contention Resolution ID and does not transmit (later) Msg3 PUSCH before detecting DCI format 1_0 with CRC scrambled by the corresponding TC-RNTI (Not intended to be sent).

[Option 1-2]
If the ra-ContentionResolutionTimer is running, the UE restarts the ra-ContentionResolutionTimer from the first symbol after the later Msg3 PUSCH or from the first symbol after the later Msg3 PUSCH.

Conflict resolution ID monitoring operations may follow any of several options below.
[[Option 1-2a]] If the ra-ContentionResolutionTimer is operational, the UE assumes that the DMRS antenna port is QCLed with reception of SSB/CSI-RS for multiple PRACH repetitions before the PDCCH monitoring occasion. monitor DCI format 1_0 with scrambled CRC by TC-RNTI, with no corresponding PDCCH detected. This option may be applicable for PRACH repetitions using the same beam.
[[Option 1-2b]] If the ra-ContentionResolutionTimer is operational, the UE assumes the DMRS antenna port is QCLed with reception of SSB/CSI-RS for that last Msg3 PUSCH. DCI format 1_0 with CRC scrambled by TC-RNTI. This option may be applicable to PRACH repetitions with the same beam or to PRACH repetitions with different beams.

[[analysis]]
From the base station's perspective, the base station is not aware that the contention resolution window is shorter than the configured length. It may be possible for the base station to send a PDCCH that schedules Msg4 for an earlier Msg3 PUSCH after a later Msg3 PUSCH.

[Option 1-3]
The contention resolution window for the later Msg3 PUSCH starts after the UE successfully detects the PDCCH for the earlier Msg3 PUSCH or after the ra-ContentionResolutionTimer expires (the UE does not detect the contention for the later Msg3 PUSCH (starts the resolution window). The UE may follow the example below.

[[example]]
If the UE transmits a later Msg3 PUSCH before the detection of a PDCCH with a CRC scrambled by TC-RNTI for an earlier Msg3 PUSCH and before the expiry of its ra-ContentionResolutionTimer, then The UE restarts the ra-ContentionResolutionTimer after expiration of the ra-ContentionResolutionTimer or after detection of a PDCCH with CRC scrambled by TC-RNTI for an earlier Msg3 PUSCH.
- Before restarting the ra-ContentionResolutionTimer, the UE sets the TC-RNTI for the previous Msg3 PUSCH assuming the DMRS antenna port is QCLed with the reception of SSB/CSI-RS for the previous Msg3 PUSCH. Monitor the PDCCH candidates to be used.
- After restarting the ra-ContentionResolutionTimer, the UE uses TC-RNTI for the later Msg3 PUSCH assuming the DMRS antenna port is QCLed with the reception of SSB/CSI-RS for the later Msg3 PUSCH. Monitor PDCCH candidates.

[[analysis]]
The UE needs to keep track of how many windows are maintained/reserved. For example, the UE transmits three Msg3 PUSCHs before the end of the contention resolution window for the first Msg3 PUSCH.

《Option 2》
A separate contention resolution window is maintained for each Msg3 PUSCH (or each PRACH iteration). A separate ra-ContentionResolutionTimer may be maintained for each PRACH repetition. Multiple conflict resolution windows for multiple PRACH iterations may follow any of several options below.

[Option 2-1]
Overlapping (in the time domain) of multiple conflict resolution windows is not allowed. It may be specified that the UE does not assume overlapping of multiple contention resolution windows for multiple Msg3 PUSCHs. The UE may follow at least one of several examples below.
[[Example 1]] The UE does not transmit (does not assume to transmit) later Msg3 PUSCH if there is any ra-ContentionResolutionTimer operating.
[[Example 2]] The UE does not (assumes not to) transmit a later Msg3 PUSCH before detecting a PDCCH that schedules a PDSCH that includes the UE Contention Resolution ID for the earlier Msg3 PUSCH.

[[analysis]]
If there is no overlapping of multiple contention resolution windows, the UE does not need to maintain a separate ra-ContentionResolutionTimer timer for each Msg3 PUSCH.

[Option 2-2]
Overlapping (in the time domain) of multiple conflict resolution windows is allowed. The UE may start another ra-ContentionResolutionTimer if there is any ra-ContentionResolutionTimer running.

In multiple Type 1-PDCCH monitoring situations within multiple contention resolution windows, the UE may use TC-RNTI, assuming the DMRS antenna port is QCLed with reception of reference signals indicated in one of several options below. PDCCH candidates using PDCCH may be monitored.
[[Option 2-2A]] Reception of SSB/CSI-RS corresponding to Msg3 PUSCH corresponding to the first/last contention resolution window of multiple contention resolution windows.
[[Option 2-2B]] Reception of SSB/CSI-RS with maximum RSRP among multiple reception of SSB/CSI-RS corresponding to multiple Msg3 PUSCH corresponding to multiple conflict resolution windows, or randomly selected reception of SSB/CSI-RSs that are selected or selected in a manner that depends on the UE implementation.

According to this embodiment, the UE can maintain one or more contention resolution windows appropriately.

<Embodiment #5>
This embodiment relates to problem 4. The overlapping (in the time domain) of the conflict resolution window and the RAR window may follow any of several options below.

《Option 1》
Overlapping of conflict resolution windows and RAR windows is not allowed. It may be specified that the UE does not assume overlapping contention resolution window and RAR window. The UE may follow at least one of several examples below.
[[Example]] The UE does not (assumes not to) send later PRACH repetitions if the (optional) ra-ContentionResolutionTimer is running.
[[Example]] After the UE detects a PDCCH that schedules a PDSCH with a UE contention resolution ID, or after a PUCCH transmission of HARQ-ACK information reported by the UE for a PDSCH with a UE contention resolution ID, Stop any ra-ResponseWindow.
[Example] The UE does not initiate an ra-ResponseWindow for a later PRACH repetition until the ra-ContentionResolutionTimer expires or until it detects a PDCCH that schedules a PDSCH with a UE Contention Resolution ID.

《Option 2》
Overlapping of conflict resolution windows and RAR windows is possible. In the example of FIG. 10, the UE transmits multiple repetitions of PRACH (Msg1 #1 to #4) and starts a RAR window after each repetition. The conflict resolution window for Msg1#1 overlaps the RAR window for Msg1#3. In this example, Msg3#1 for Msg1#1 overlaps with Msg1#3, but Msg3#1 for Msg1#1 does not need to overlap with Msg1#3.

The UE may follow at least one of the following several cases.

[Case 1]
For type 1-CSS PDCCH monitoring occasions within the contention resolution window/RAR window for multiple PRACH repetitions with the same beam, the UE may follow at least one of several options below.
[[Option 2-1A]] The UE uses both the RA-RNTI and TC-RNTI to transmit the Monitor candidates.
[[Option 2-1B]] The UE monitors PDCCH candidates using RA-RNTI, assuming a DMRS antenna port that is QCLed for reception of SSB/CSI-RS corresponding to multiple PRACH repetitions.
[[Option 2-1C]] The UE monitors PDCCH candidates using TC-RNTI, assuming a DMRS antenna port that is QCLed to receive SSB/CSI-RS corresponding to multiple PRACH repetitions.

[Case 2]
For type 1-CSS PDCCH monitoring occasions within the contention resolution window/RAR window for multiple PRACH repetitions with different multiple beams, the UE may follow at least one of several options below.

[[Option 2-2A]]
Priority is given to monitoring PDCCH scheduling Msg4 with UE contention resolution ID. The UE may monitor PDCCH candidates using TC-RNTI, assuming a DMRS antenna port that is QCLed with reception of SSB/CSI-RS corresponding to the RAR window. If multiple Type 1 PDCCH monitoring occasions are within multiple contention resolution windows, option 2-2 of embodiment #4 may be utilized.

[[Option 2-2B]]
RAR monitoring is prioritized. The UE may monitor PDCCH candidates using RA-RNTI, assuming a DMRS antenna port that is QCLed with reception of SSB/CSI-RS corresponding to the RAR window. If multiple Type 1 PDCCH monitoring occasions are within multiple RAR windows, option 2-2 of embodiment #2 may be utilized.

According to this embodiment, the UE can appropriately determine the contention resolution window and the RAR window.

<Embodiment #6>
This embodiment relates to problem 5. If the UE receives multiple PDSCHs containing UE contention resolution IDs, the UE may follow any of several options below.

《Option 1》
The UE reports only one HARQ-ACK information bit for the PDSCHs in the earliest PUCCH slot of the PUCCH slots for the PDSCHs. If the UE transmits HARQ-ACK information for any PDSCH that includes the UE contention resolution ID, it may not report HARQ-ACK information for other PDSCHs that include the UE contention resolution ID.

In the example of FIG. 11A, the UE transmits multiple repetitions of PRACH (Msg1 #1, #2). When the UE transmits HARQ-ACK information for Msg4#1 based on Msg#1 on the PUCCH, the UE does not transmit HARQ-ACK information for Msg4#2 based on Msg1#2.

《Option 2》
The UE reports HARQ-ACK information for each PDSCH in the corresponding PUCCH slot.

In the example of FIG. 11B, the UE transmits multiple repetitions of PRACH (Msg1 #1, #2). The UE transmits HARQ-ACK information for Msg4#1 based on Msg#1 on PUCCH, and transmits HARQ-ACK information for Msg4#2 based on Msg1#2 on PUCCH. In this example, the PUCCH (slot) of HARQ-ACK information for Msg4#2 is different from the PUCCH (slot) of HARQ-ACK information for Msg4#1, but the PUCCH (slot) of HARQ-ACK information for Msg4#1 is ) may be the same as

The UE may follow any of several options below.

[Option 2-1]
The UE does not expect more than one PDSCH (multi-PDSCH) with (corresponding) UE contention resolution IDs mapped to the same PUCCH slot.

[Option 2-2]
If there is more than one PDSCH (multi-PDSCH) with (corresponding) UE contention resolution IDs mapped to the same PUCCH slot, the UE may follow any of several options below.

[[Option 2-2A]]
The UE reports only 1 bit of HARQ-ACK information for its multiple PDSCHs. The 1-bit information is selected by the first/last PDCCH/PDSCH (or randomly selected PDCCH/PDSCH, or by a method depending on the UE implementation) among the plurality of PDCCH/PDSCHs corresponding to the PUCCH slot. The ACK/NACK may be an ACK/NACK for a PDCCH/PDSCH), or may be obtained from a plurality of ACK/NACK bits for the plurality of PDSCHs using a logical product or a logical sum operation.

[[Option 2-2B]]
The UE may report up to X HARQ-ACK information bits for multiple PDSCHs. In existing specifications, the UE capability may be expanded as the UE can send up to one HARQ-ACK information bit in one PUCCH before dedicated PUCCH resource configuration. Since only PUCCH format (PF) 0/1 is defined for PUCCH resources before individual PUCCH resource configuration, regarding X (maximum number), X=2 may be possible. Regarding X (maximum number), it may be possible that X>2. In this case, the default PUCCH resource before individual PUCCH resource configuration may be expanded. PUCCH resources with PF2/3/4 may be added in the default PUCCH resource table.

According to this embodiment, the UE can appropriately report HARQ-ACK information for multiple PDSCHs including the UE contention resolution ID.

<Supplement>
[variation]
In each embodiment, different options may be used for different cases. The different multiple cases may include, for example, a case where multiple PRACH repetitions use the same beam, and a case where multiple PRACH repetitions use different multiple beams.

Embodiment #2-2 replaces "RAR Window" with "Conflict Resolution Window", replaces "RA-RNTI" with "TC-RNTI", and replaces "RAR" with "Schedule PDSCH with UE Contention Resolution ID". DCI” can be used in cases where multiple conflict resolution windows overlap.

Embodiment #2-2 replaces "RAR window" with "RAR window/conflict resolution window", replaces "RA-RNTI" with "RA-RNTI/TC-RNTI", and replaces "RAR" with "RAR". A DCI that schedules a PDSCH with a UE contention resolution ID can be used in the case where the contention resolution window and the RAR window overlap.

[Notification of information to UE]
Notification of any information (from the Network (NW) (e.g., Base Station (BS)) to the UE (in other words, reception of any information from the BS at the UE) in the above embodiments ) is performed using physical layer signaling (e.g. DCI), higher layer signaling (e.g. RRC signaling, MAC CE), specific signals/channels (e.g. PDCCH, PDSCH, reference signals), or a combination thereof. It's okay.

When the above notification is performed by a MAC CE, the MAC CE may be identified by including a new logical channel ID (LCID), which is not specified in the existing standard, in the MAC subheader.

When the above notification is performed by a DCI, the above notification includes a specific field of the DCI, a radio network temporary identifier (Radio Network Temporary Identifier (RNTI)), the format of the DCI, etc.

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

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

When the above notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID that is not defined in the existing standard in the MAC subheader.

When the above notification is performed by UCI, the above notification may be transmitted using PUCCH or PUSCH.

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

[About application of each embodiment]
At least one of the embodiments described above may be applied if certain conditions are met. The specific conditions may be specified in the standard, or may be notified to the UE/BS using upper layer signaling/physical layer signaling.

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

The particular UE capability may indicate at least one of the following:
- Support for multiple RARs for multiple PRACH repetitions with same beam/different beams.
- Support for common/individual ra-ResponseWindow for multiple PRACH repetitions.
- Support for transmission of multiple Msg3 PUSCH for multiple RARs.
- Support for common/individual ra-ContentionResolutionTimer for multiple Msg3 PUSCH (or multiple PRACH repeats).
- Support for overlapping RAR and conflict resolution windows.
- Support for handling more than one DCI format with CRC scrambled by RA-RNTI within one slot.
- Maximum number of DCI formats with CRC scrambled by RA-RNTI that the UE can process within one slot.
- Support for reporting one HARQ-ACK PUCCH for multiple Msg4 receptions.
- Support for reporting HARQ-ACK PUCCH for each Msg4 reception.
- Support for reporting one/two HARQ-ACK information bits in one PUCCH before individual PUCCH source configuration.
- Support for monitoring more than one DCI format with CRC scrambled by RA-RNTI/TC-RNTI with different QCL assumptions within one slot.
- Maximum number of DCI formats with CRC scrambled by RA-RNTI/TC-RNTI that the UE can monitor within one slot with different QCL assumptions.

Further, the specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency) or a capability that is applied across all frequencies (e.g., cell, band, band combination, BWP, component carrier, etc.). or a combination thereof), or it may be a capability for each frequency range (for example, Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2). Alternatively, it may be a capability for each subcarrier spacing (SCS), or a capability for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

Furthermore, the above-mentioned specific UE capability may be a capability that is applied across all duplex schemes (commonly regardless of the duplex scheme), or may be a capability that is applied across all duplex schemes (for example, Time Division Duplex). The capability may be for each frequency division duplex (TDD)) or frequency division duplex (FDD)).

In addition, at least one of the embodiments described above may be configured such that the UE configures/activates specific information related to the embodiment described above (or performs the operation of the embodiment described above) by upper layer signaling/physical layer signaling. / May be applied when triggered. For example, the specific information may be information indicating that the functions of each embodiment are enabled, arbitrary RRC parameters for a specific release (for example, Rel. 18/19), or the like.

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

(Appendix A)
Regarding one embodiment of the present disclosure, the following invention will be added.
[Additional note 1]
a controller that controls transmission of a plurality of repetitions of a physical random access channel (PRACH) and one or more random access response (RAR) windows based on at least one of the plurality of repetitions;
a receiving unit that receives RAR in the one or more RAR windows.
[Additional note 2]
The terminal according to supplementary note 1, wherein the control unit operates one RAR window for the plurality of repetitions.
[Additional note 3]
The terminal according to

Supplementary Note

1 or 2, wherein the control unit operates a plurality of RAR windows for each of the plurality of repetitions.
[Additional note 4]
The terminal according to any one of appendices 1 to 3, wherein the receiving unit monitors a specific number or less of downlink control information formats within one slot.

(Appendix B)
Regarding one embodiment of the present disclosure, the following invention will be added.
[Additional note 1]
a receiving unit that receives a plurality of random access responses (RARs) for a plurality of repetitions of a physical random access channel (PRACH), respectively;
A terminal comprising: a control unit that controls transmission of a plurality of physical uplink shared channels (PUSCH) scheduled by the plurality of RARs.
[Additional note 2]
The terminal according to supplementary note 1, wherein the plurality of PUSCHs do not overlap in the time domain, or the gap between the plurality of PUSCHs is longer than the time required for beam switching.
[Additional note 3]
The terminal according to

Appendix

1 or 2, wherein the plurality of PUSCHs do not overlap in the time domain, or the gap between the plurality of PUSCHs is shorter than the time required for beam switching.
[Additional note 4]
The terminal according to any one of Supplementary Notes 1 to 3, wherein the control unit controls transmission of a specific PUSCH among the plurality of PUSCHs.

(Appendix C)
Regarding one embodiment of the present disclosure, the following invention will be added.
[Additional note 1]
a controller that controls one or more contention resolution windows for multiple iterations of a physical random access channel (PRACH);
a receiving unit that receives one or more downlink control information formats in the one or more contention resolution windows.
[Additional note 2]
The terminal according to supplementary note 1, wherein a plurality of conflict resolution windows respectively corresponding to the plurality of repetitions are allowed to overlap in a time domain.
[Additional note 3]
The terminal according to

appendix

1 or 2, wherein the one or more conflict resolution windows and a random access response (RAR) window are allowed to overlap in the time domain.
[Additional note 4]
The control unit receives a plurality of physical downlink shared channels corresponding to the plurality of repetitions, and reports one or more Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) information for the plurality of physical downlink shared channels. The terminal according to any one of Supplementary Notes 1 to 3, which controls .

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

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

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

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

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

The wireless communication system 1 includes a base station 11 that forms a macro cell C1 with relatively wide coverage, and base stations 12 (12a-12c) that are located within the macro cell C1 and form a small cell C2 that is narrower than the macro cell C1. You may prepare. User terminal 20 may be located within at least one cell. The arrangement, number, etc. of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when

base stations

11 and 12 are not distinguished, they will be collectively referred to as base station 10.

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

Each CC may be included in at least one of 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 FR1 may correspond to a higher frequency band than FR2, for example.

Further, the user terminal 20 may communicate using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

The plurality of base stations 10 may be connected by wire (for example, optical fiber, X2 interface, etc. compliant with Common Public Radio Interface (CPRI)) or wirelessly (for example, NR communication). For example, when NR communication is used as a backhaul between

base stations

11 and 12, base station 11, which is an upper station, is an Integrated Access Backhaul (IAB) donor, and base station 12, which is a relay station, is an IAB donor. May also be called a node.

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

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

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

In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access method 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.

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

In the wireless communication system 1, the downlink channels include a physical downlink shared channel (PDSCH) shared by each user terminal 20, a broadcast channel (physical broadcast channel (PBCH)), and a downlink control channel (physical downlink control). Channel (PDCCH)) or the like may be used.

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

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

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

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

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

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

The PUCCH allows channel state information (CSI), delivery confirmation information (for example, may be called Hybrid Automatic Repeat Request ACKnowledgement (HARQ-ACK), ACK/NACK, etc.), and scheduling request ( Uplink Control Information (UCI) including at least one of SR)) may be transmitted. A random access preamble for establishing a connection with a cell may be transmitted by PRACH.

Note that in this disclosure, downlinks, uplinks, etc. may be expressed without adding "link". Furthermore, various channels may be expressed without adding "Physical" at the beginning.

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

The synchronization signal may be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS/PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.

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

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

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

The control unit 110 controls the entire base station 10. The control unit 110 can be configured from a controller, a control circuit, etc., which will be explained based on common recognition in the technical field related to the present disclosure.

The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), and the like. The control unit 110 may control transmission and reception, measurement, etc. using the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission path interface 140. The control unit 110 may generate data, control information, a sequence, etc. to be transmitted as a signal, and may transfer the generated data to the transmitting/receiving unit 120. The control unit 110 may perform communication channel call processing (setting, release, etc.), status management of the base station 10, radio resource management, and the like.

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

The transmitting/receiving section 120 may be configured as an integrated transmitting/receiving section, or may be configured from a transmitting section and a receiving section. The transmitting section may include a transmitting processing section 1211 and an RF section 122. The reception section may include a reception processing section 1212, an RF section 122, and a measurement section 123.

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

The transmitter/receiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitter/receiver 120 may receive the above-mentioned uplink channel, uplink reference signal, and the like.

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

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

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

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

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

The transmitting/receiving unit 120 (reception processing unit 1212) performs analog-to-digital conversion, fast Fourier transform (FFT) processing, and inverse discrete Fourier transform (IDFT) on the acquired baseband signal. )) processing (if necessary), applying reception processing such as filter processing, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing and PDCP layer processing, User data etc. may also be acquired.

The transmitting/receiving unit 120 (measuring unit 123) may perform measurements regarding the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurement, Channel State Information (CSI) measurement, etc. based on the received signal. The measurement unit 123 is the receiving power (for example, the Reference Signal Received Power (RSRP)), the receiving quality (eg, the Reference Signal Received Quality (RSRQ), Signal To Interference Plus Noi. SE RATIO (SINR), Signal to Noise Ratio (SNR) , signal strength (for example, Received Signal Strength Indicator (RSSI)), propagation path information (for example, CSI), etc. may be measured. The measurement results may be output to the control unit 110.

The transmission path interface 140 transmits and receives signals (backhaul signaling) between devices included in the core network 30 (for example, network nodes providing NF), other base stations 10, etc., and provides information for the user terminal 20. User data (user plane data), control plane data, etc. may be acquired and transmitted.

Note that the transmitting unit and receiving unit of the base station 10 in the present disclosure may be configured by at least one of the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission path interface 140.

The control unit 110 may control reception of a plurality of repetitions of a physical random access channel (PRACH) and one or more random access response (RAR) windows based on at least one of the plurality of repetitions. The transmitter/receiver 120 may transmit RAR in the one or more RAR windows.

The transmitting/receiving unit 120 may transmit multiple random access responses (RAR) for multiple repetitions of the physical random access channel (PRACH), respectively. The control unit 110 may control reception of a plurality of physical uplink shared channels (PUSCH) scheduled by the plurality of RARs.

The control unit 110 may control one or more contention resolution windows for multiple repetitions of the physical random access channel (PRACH). The transceiver 120 may transmit one or more downlink control information formats in the one or more conflict resolution windows.

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

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

The control unit 210 controls the entire user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which will be explained based on common recognition in the technical field related to the present disclosure.

The control unit 210 may control signal generation, mapping, etc. The control unit 210 may control transmission and reception using the transmitting/receiving unit 220 and the transmitting/receiving antenna 230, measurement, and the like. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as a signal, and may transfer the generated data to the transmitting/receiving unit 220.

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

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

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

The transmitter/receiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitter/receiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, and the like.

The transmitting/receiving unit 220 may form at least one of a transmitting beam and a receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

The transmission/reception unit 220 (transmission processing unit 2211) performs PDCP layer processing, RLC layer processing (e.g. RLC retransmission control), MAC layer processing (e.g. , HARQ retransmission control), etc., to generate a bit string to be transmitted.

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

Note that 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 (for example, PUSCH), the transmitting/receiving unit 220 (transmission processing unit 2211) performs the above processing in order to transmit the channel using the DFT-s-OFDM waveform. DFT processing may be performed as the transmission processing, or if not, DFT processing may not be performed as the transmission processing.

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

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

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

The transmitting/receiving unit 220 (measuring unit 223) may perform measurements regarding the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal. The measurement unit 223 may measure received power (for example, RSRP), reception quality (for example, RSRQ, SINR, SNR), signal strength (for example, RSSI), propagation path information (for example, CSI), and the like. The measurement results may be output to the control unit 210.

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

The control unit 210 may control transmission of a plurality of repetitions of a physical random access channel (PRACH) and one or more random access response (RAR) windows based on at least one of the plurality of repetitions. The transmitter/receiver 220 may receive RAR in the one or more RAR windows (Embodiment #1/#2).

The control unit 210 may operate one RAR window for the plurality of repetitions.

The control unit 210 may operate a plurality of RAR windows for each of the plurality of repetitions.

The receiving unit 220 may monitor a specific number or less of downlink control information formats within one slot.

The transmitter/receiver 220 may receive multiple random access responses (RARs) for multiple repetitions of the physical random access channel (PRACH), respectively. The control unit 210 may control transmission of a plurality of physical uplink shared channels (PUSCH) scheduled by the plurality of RARs (Embodiment #3).

The plurality of PUSCHs may not overlap in the time domain, or the gap between the plurality of PUSCHs may be longer than the time required for beam switching.

The plurality of PUSCHs may not overlap in the time domain, or the gap between the plurality of PUSCHs may be shorter than the time required for beam switching.

The control unit 210 may control transmission of a specific PUSCH among the plurality of PUSCHs.

The control unit 210 may control one or more contention resolution windows for multiple repetitions of the physical random access channel (PRACH). The transmitter/receiver 220 may receive one or more downlink control information formats in the one or more conflict resolution windows (Embodiment #4/#5/#6).

A plurality of conflict resolution windows corresponding to the plurality of repetitions may be allowed to overlap in the time domain.

The one or more conflict resolution windows and a random access response (RAR) window may be allowed to overlap in the time domain.

The control unit 210 receives a plurality of physical downlink shared channels corresponding to the plurality of repetitions, and receives one or more Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) information for the plurality of physical downlink shared channels. Reporting and may be controlled.

(Hardware configuration)
It should be noted that the block diagram used to explain the above embodiment shows blocks in functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically coupled device, or may be realized using two or more physically or logically separated devices directly or indirectly (e.g. , wired, wireless, etc.) and may be realized using a plurality of these devices. The functional block may be realized by combining software with the one device or the plurality of devices.

Here, functions include judgment, decision, judgement, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, and consideration. , broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. Not limited. For example, a functional block (configuration unit) that performs transmission may be called a transmitting unit, a transmitter, or the like. In either case, as described above, the implementation method is not particularly limited.

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

Note that in this disclosure, words such as apparatus, circuit, device, section, unit, etc. can be read interchangeably. The hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured not to include some of the devices.

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

Each function in the base station 10 and the user terminal 20 is performed by, for example, loading predetermined software (program) onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations and communicates via the communication device 1004. This is achieved by controlling at least one of reading and writing 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 by a central processing unit (CPU) that includes interfaces with peripheral devices, a control device, an arithmetic unit, registers, and the like. For example, at least a portion of the above-mentioned control unit 110 (210), transmitting/receiving unit 120 (220), etc. may be realized by the processor 1001.

Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes in accordance with these. As the program, a program that causes a computer to execute at least part of the operations described in the above embodiments is used. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and operated in the processor 1001, and other functional blocks may also be realized in the same way.

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

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

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

The input device 1005 is an input device (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (for example, a display, a speaker, a light emitting diode (LED) lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).

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

The base station 10 and user terminal 20 also include a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc. It may be configured to include hardware, and a part or all of each functional block may be realized using the hardware. For example, processor 1001 may be implemented using at least one of these hardwares.

(Modified example)
Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol and signal may be interchanged. Also, the signal may be a message. The reference signal may also be abbreviated as RS, and may be called a pilot, pilot signal, etc. depending on the applicable standard. Further, a component carrier (CC) may 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 (eg, 1 ms) that does not depend on numerology.

Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. Numerology includes, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, and radio frame structure. , 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 be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) in the time domain. Furthermore, a slot may be a time unit based on numerology.

A slot may include multiple mini-slots. Each minislot may be made up of one or more symbols in the time domain. Furthermore, a mini-slot may also be called a sub-slot. A minislot may be made up of fewer symbols than a slot. PDSCH (or PUSCH) transmitted in time units larger than minislots may be referred to as PDSCH (PUSCH) mapping type A. PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (PUSCH) mapping type B.

Radio frames, subframes, slots, minislots, and symbols all represent time units when transmitting signals. Other names may be used for the radio frame, subframe, slot, minislot, and symbol. Note that time units such as frames, subframes, slots, minislots, and symbols in the present disclosure may be read interchangeably.

For example, one subframe may be called a TTI, a plurality of consecutive subframes may be called a TTI, and one slot or one minislot may be called a TTI. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (for example, 1-13 symbols), or a period longer than 1ms. It may be. 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 minimum time unit for scheduling in wireless communication. For example, in the LTE system, a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each user terminal) to each user terminal on a TTI basis. Note that the definition of TTI is not limited to this.

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

Note that when one slot or one minislot is called a TTI, one or more TTIs (that is, one or more slots or one or more minislots) may be the minimum time unit for scheduling. Further, the number of slots (minislot number) that constitutes the minimum time unit of the scheduling may be controlled.

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

Note that long TTI (for example, normal TTI, subframe, etc.) may be read as TTI with a time length exceeding 1 ms, and short TTI (for example, short TTI, etc.) It may also be read as a TTI having the above TTI length.

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

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

Note that one or more RBs include a physical resource block (Physical RB (PRB)), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, and an RB. They may also be called pairs.

Additionally, a resource block may be configured by one or more resource elements (REs). For example, 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.

Bandwidth Part (BWP) (also called partial bandwidth, etc.) refers to a subset of consecutive common resource blocks (RB) for a certain numerology in a certain carrier. Good too. Here, the common RB may be specified by an RB index based on a common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

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

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 of the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be replaced with "BWP".

Note that the structures of the radio frame, subframe, slot, minislot, symbol, etc. described above 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 symbols included in an RB, The number of subcarriers, the number of symbols within a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.

In addition, the information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values from a predetermined value, or using other corresponding information. may be expressed. For example, radio resources 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 mathematical formulas etc. using these parameters may differ from those explicitly disclosed in this disclosure. Since the various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable designation, the various names assigned to these various channels and information elements are not in any way exclusive designations. .

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

Additionally, information, signals, etc. may be output from the upper layer to the lower layer and from the lower layer to at least one of the upper layer. Information, signals, etc. may be input and output via multiple network nodes.

Input/output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Information, signals, etc. that are input and output can be overwritten, updated, or added. The output information, signals, etc. may be deleted. The input information, signals, etc. may be transmitted to other devices.

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 physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals, or a combination thereof It may be carried out by

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

Further, notification of prescribed information (for example, notification of "X") is not limited to explicit notification, but may be made implicitly (for example, by not notifying the prescribed information or by providing other information) (by notification).

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

Software includes instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, whether referred to as software, firmware, middleware, microcode, hardware description language, or by any other name. , should be broadly construed to mean an application, software application, software package, routine, subroutine, object, executable, thread of execution, procedure, function, etc.

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

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

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

In the present disclosure, "Base Station (BS)", "Wireless base station", "Fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission/Reception Point (TRP)", "Panel" , "cell," "sector," "cell group," "carrier," "component carrier," and the like may be used interchangeably. A base station is sometimes referred to by terms such as macrocell, small cell, femtocell, and picocell.

A base station can accommodate one or more (eg, three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, each of which is connected to a base station subsystem (e.g., an indoor small base station (Remote Radio Communication services can also be provided by the Head (RRH)). The term "cell" or "sector" refers to part or all of the coverage area of a base station and/or base station subsystem that provides communication services in this coverage.

In the present disclosure, a base station transmitting information to a terminal may be interchanged with 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" are used interchangeably. can be done.

A mobile station is 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 a base station and a mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, or the like.

The moving body refers to a movable object, and the moving speed is arbitrary, and naturally includes cases where the moving body is stopped. The mobile objects include, for example, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, carts, rickshaws, and ships (ships and other watercraft). , including, but not limited to, airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, balloons, and items mounted thereon. Furthermore, the mobile object may be a mobile object that autonomously travels based on a travel command.

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

FIG. 16 is a diagram illustrating 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 (current sensor 50, (including a rotation speed sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service section 59, and a communication module 60. Be prepared.

The drive unit 41 is composed of, for example, at least one of an engine, a motor, and a hybrid of an engine and a motor. The steering unit 42 includes at least a steering wheel (also referred to as a steering wheel), 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 includes a microprocessor 61, a memory (ROM, RAM) 62, and a communication port (for example, an input/output (IO) port) 63. Signals from various sensors 50-58 provided in the vehicle are input to the electronic control unit 49. The electronic control section 49 may be called an electronic control unit (ECU).

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

The information service department 59 includes various devices for providing (outputting) various information such as driving information, traffic information, and entertainment information, such as car navigation systems, audio systems, speakers, displays, televisions, and radios, and these devices. It consists of one or more ECUs that control the The information service unit 59 provides various information/services (for example, multimedia information/multimedia services) to the occupants of the vehicle 40 using information acquired from an external device via the communication module 60 or the like.

The information service unit 59 may include an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accepts input from the outside, and an output device that performs output to the outside (for example, (display, speaker, LED lamp, touch panel, etc.).

The driving support system unit 64 includes millimeter wave radar, Light Detection and Ranging (LiDAR), a camera, a positioning locator (for example, Global Navigation Satellite System (GNSS), etc.), and map information (for example, High Definition (HD)). maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., inertial measurement units (IMUs), inertial navigation systems (INS), etc.), artificial intelligence ( Artificial Intelligence (AI) chips, AI processors, and other devices that provide functions to prevent accidents and reduce the driver's driving burden, as well as one or more devices that control these devices. It consists of an ECU. Further, the driving support system section 64 transmits and receives various information via the communication module 60, and realizes a driving support function or an automatic 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 communicates via the communication port 63 with 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, which are included in the vehicle 40. Data (information) is transmitted and received between the axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58.

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 external devices. For example, various information is transmitted and received with an 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 base station 10, user terminal 20, etc. described above. Further, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (it may function as at least one of the base station 10 and the user terminal 20).

The communication module 60 receives signals from the various sensors 50 to 58 described above that are input to the electronic control unit 49, information obtained based on the signals, and input from the outside (user) obtained via the information service unit 59. At least one of the information based on the information may be transmitted to an external device via wireless communication. The electronic control unit 49, various sensors 50-58, information service unit 59, etc. may be called an input unit that receives 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, inter-vehicle information, etc.) transmitted from an external device, and displays it on the information service section 59 provided in the vehicle. The information service unit 59 is an output unit that outputs information (for example, outputs information to devices such as a display and a speaker based on the PDSCH (or data/information decoded from the PDSCH) received by the communication module 60). may be called.

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

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

Similarly, the user terminal in the present disclosure may be replaced with a base station. In this case, the base station 10 may have the functions that the user terminal 20 described above has.

In this disclosure, the operations performed by the base station may be performed by its upper node in some cases. In a network that includes one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (e.g. It is clear that this can be performed by a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc. (though not limited thereto), or a combination thereof.

Each aspect/embodiment described in this disclosure may be used alone, in combination, or may be switched and used in accordance with execution. Further, the order of the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this disclosure may be changed as long as there is no contradiction. For example, the methods described in this disclosure use an example order to present elements of the various steps 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 an integer or decimal number, for example)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802 .11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), and other appropriate wireless communication methods. The present invention may be applied to systems to be used, next-generation systems expanded, modified, created, or defined based on these systems. Furthermore, a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G) may be applied.

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

As used in this disclosure, any reference to elements using the designations "first," "second," etc. does not generally limit the amount or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, 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 any way.

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

In addition, "judgment (decision)" includes receiving (e.g., receiving information), transmitting (e.g., sending information), input (input), output (output), access ( may be considered to be "determining", such as accessing data in memory (eg, accessing data in memory).

In addition, "judgment" is considered to mean "judging" resolving, selecting, choosing, establishing, comparing, etc. Good too. In other words, "judgment (decision)" may be considered to be "judgment (decision)" of some action.

Furthermore, "judgment (decision)" may be read as "assuming", "expecting", "considering", etc.

The "maximum transmit power" described in this disclosure may mean the maximum value of transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the It may also mean rated UE maximum transmit power).

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

In this disclosure, when two elements are connected, they may be connected using one or more electrical wires, cables, printed electrical connections, etc., as well as in the radio frequency domain, microwave can be considered to be "connected" or "coupled" to each other using electromagnetic energy having wavelengths in the light (both visible and invisible) range.

In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." Note that the term may also mean that "A and B are each different from C". Terms such as "separate" and "coupled" may also be interpreted similarly to "different."

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

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

In the present disclosure, "less than or equal to", "less than", "more than", "more than", "equal to", etc. may be read interchangeably. In addition, in this disclosure, "good", "bad", "large", "small", "high", "low", "early", "slow", "wide", "narrow", etc. The words are not limited to the original, comparative, and superlative, and may be interpreted interchangeably. In addition, in this disclosure, words meaning "good", "bad", "large", "small", "high", "low", "early", "slow", "wide", "narrow", etc. may be interpreted as an expression with "the i-th" (i is any integer), not only in the elementary, comparative, and superlative, but also interchangeably (for example, "the highest" can be interpreted as "the i-th highest"). may be read interchangeably).

In this disclosure, "of", "for", "regarding", "related to", "associated with", etc. are used to refer to each other. It may be read differently.

Although the invention according to the present disclosure has been described in detail above, it is clear for those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the invention as determined based on the claims. Therefore, the description of the present disclosure is for the purpose of illustrative explanation and does not have any limiting meaning on the invention according to the present disclosure.

Claims

a controller that controls one or more contention resolution windows for multiple iterations of a physical random access channel (PRACH);
a receiving unit that receives one or more downlink control information formats in the one or more contention resolution windows.
The terminal according to claim 1, wherein a plurality of conflict resolution windows respectively corresponding to the plurality of repetitions are allowed to overlap in the time domain.
The terminal of claim 1, wherein the one or more contention resolution windows and a random access response (RAR) window are allowed to overlap in the time domain.
The control unit receives a plurality of physical downlink shared channels corresponding to the plurality of repetitions, and reports one or more Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) information for the plurality of physical downlink shared channels. The terminal according to claim 1, wherein the terminal controls:
controlling one or more contention resolution windows for multiple iterations of a physical random access channel (PRACH);
receiving one or more downlink control information formats in the one or more contention resolution windows.
a controller that controls one or more contention resolution windows for multiple iterations of a physical random access channel (PRACH);
a transmitter configured to transmit one or more downlink control information formats in the one or more contention resolution windows.