Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure is provided with: a control unit that controls transmission of a plurality of repetitions of a physical random access channel (PRACH) and one or more random access acknowledgement (RAR) windows based on at least one of the plurality of repetitions; and a receiving unit that receives the RAR in the one or more RAR windows. According to one mode of the invention, the coverage range of the random access process can be improved.

Description

Technical Field

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

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been standardized for the purpose of further high-speed data rates and low latency (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel. 10-14) has been standardized for the purpose of further increasing capacity and improving (evolution) of LTE (Release (Rel.) 8 and 9 of the Third Generation Partnership Project (3GPP (registered trademark))).

[0003] Successor systems of LTE (also called, for example, 5th generation mobile communication system (5G), 5G+(plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later, etc.) are also being studied.

[0004] Prior art literature

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the invention

[0007] Problems to be solved by the invention

[0008] In future wireless communication systems (eg, NR), research is underway to improve coverage.

[0009] However, the random access procedure for improving coverage is unclear. If such a random access procedure is unclear, there is a concern that communication throughput may be reduced.

[0010] Therefore, one of the objectives of the present disclosure is to provide a terminal, a wireless communication method, and a base station for improving the coverage of a random access process.

[0011] Means for solving problems

[0012] A terminal according to one embodiment of the present disclosure includes: a control unit that controls multiple repetitions of sending a physical random access channel (PRACH) and one or more random access response (RAR) windows based on at least one of the multiple repetitions; and a receiving unit that receives a RAR in the one or more RAR windows.

[0013] Effects of the Invention

[0014] According to one embodiment of the present disclosure, the coverage of the random access process can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 An example of RACH configuration information element is shown.

[0016] Figure 2A as well as Figure 2B An example showing the association between PRACH opportunities and beams.

[0017] Figure 3 This diagram shows an example of multiple PUCCH resource sets before dedicated PUCCH resources are configured.

[0018] Figure 4A as well as Figure 4B This shows an example of problem 1 / 2.

[0019] Figure 5A as well as Figure 5B An example showing problem 2 / 4.

[0020] Figure 6 This shows an example of question 5.

[0021] Fig. 7A as well as Figure 7B An example of a random access procedure according to Option 1 of Implementation #1 is shown.

[0022] Figure 8 Another example of the random access procedure involved in Option 1 of Implementation #1 is shown.

[0023] Fig. 9 An example of a random access procedure according to Option 2 of Implementation #1 is shown.

[0024] Fig.10 An example of a random access procedure according to implementation #5 is shown.

[0025] Fig.11A as well as Fig. 11B An example of a random access procedure according to Implementation #6 is shown.

[0026] Fig.12 This is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment.

[0027] Fig.13 This is a diagram showing an example of the configuration of a base station according to an embodiment.

[0028] Fig.14 This is a diagram showing an example of a configuration of a user terminal according to an embodiment.

[0029] Fig.15 This is a diagram showing an example of the hardware configuration of a base station and a user terminal involved in one embodiment.

[0030] Fig.16 It is a diagram showing an example of a vehicle according to an embodiment. DETAILED DESCRIPTION

[0031] (TCI, spatial relationship, QCL)

[0032] Under study: In NR, based on the Transmission Configuration Indication state (TCI state), the reception processing (for example, at least one of reception, demapping, demodulation, and decoding) and the transmission processing (for example, at least one of transmission, mapping, precoding, modulation, and encoding) of at least one of a signal and a channel (expressed as signal / channel) in the UE are controlled.

[0033] The TCI state may also represent the TCI state applied to the downlink signal / channel. The TCI state equivalent to the TCI state applied to the uplink signal / channel may also be expressed as a spatial relation.

[0034] The so-called TCI state refers to information related to Quasi-Co-Location (QCL) of signals / channels, and may also be called spatial reception parameters, spatial relationship information, etc. The TCI state may also be set for each channel or each signal to the UE.

[0035] QCL refers to an index that indicates the statistical properties of a signal / channel. For example, when a certain signal / channel is in a QCL relationship with other signals / channels, it can also mean that it can be assumed that at least one of the Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter) is the same among these different signals / channels (at least one of them is QCL).

[0036] In addition, the spatial reception parameter may also correspond to the reception beam of the UE (eg, reception analog beam), and the beam may also be determined based on the spatial QCL. The QCL (or at least one element of the QCL) in the present disclosure may also be rewritten as sQCL (spatial QCL).

[0037] QCL may also be specified in multiple types (QCL types). For example, four QCL types AD may be set that can assume the same parameters (or parameter sets) but are different. The following represents the parameters (also referred to as QCL parameters):

[0038] ・QCL type A (QCL-A): Doppler shift, Doppler spread, average delay, and delay spread;

[0039] ・QCL type B (QCL-B): Doppler shift and Doppler spread;

[0040] ・QCL type C (QCL-C): Doppler shift and average delay;

[0041] ・QCL type D (QCL-D): Spatial reception parameters.

[0042] The UE assumes that a certain Control Resource Set (CORESET), channel or reference signal is in a specific QCL (e.g., QCL type D) relationship with other CORESETs, channels or reference signals. This situation can also be called QCL assumption.

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

[0044] The TCI state may be, for example, information related to the QCL of the target channel (in other words, the reference signal (RS) used for the channel) and other signals (for example, other RS). The TCI state may also be set (indicated) by high-layer signaling, physical layer signaling, or a combination thereof.

[0045] The physical layer signaling may be, for example, downlink control information (Downlink Control Information (DCI)).

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

[0047] In addition, the RS that is in a QCL relationship with the channel may be, for example, at least one of a synchronization signal block (SynchronizationSignal Block (SSB)), a channel state information reference signal (CSI-RS), a measurement reference signal (Sounding Reference Signal (SRS)), a tracking CSI-RS (also called a tracking reference signal (TRS)), and a QCL detection reference signal (also called QRS).

[0048] The SSB is a signal block including at least one of a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a broadcast channel (physical broadcast channel (PBCH)). The SSB may also be referred to as an SS / PBCH block.

[0049] The RS of QCL type X in the TCI state may also mean an RS that is in a QCL type X relationship with (a DMRS of) a certain channel / signal, and the RS may also be referred to as a QCL source of QCL type X in the TCI state.

[0050] (Initial access process)

[0051] During the initial access process, the UE (RRC_IDLE mode) receives the SS / PBCH block (SSB), sends Msg.1 (PRACH / random access preamble / preamble), receives Msg.2 (PDCCH, PDSCH containing random access response (RAR)), sends Msg.3 (PUSCH scheduled by RAR UL grant), and receives Msg.4 (PDCCH, PDSCH containing UE contention resolution identity). After that, if the UE sends an ACK for Msg.4 based on the base station (network), an RRC connection is established (RRC_CONNECTED mode).

[0052] SSB reception includes PSS detection, SSS detection, PBCH-DMRS detection and PBCH reception. In PSS detection, part of the physical cell ID (PCI) is detected, OFDM symbol timing is detected (synchronized), and (rough) frequency synchronization is performed. SSS detection includes the detection of the physical cell ID. PBCH-DMRS detection includes the detection of (part of) the SSB index within a half radio frame (5ms). PBCH reception includes the detection of the system frame number (SFN) and radio frame timing (SSB index), the reception of the setting information for receiving the remaining minimum system information (RMSI, SIB1), and the identification of whether the UE can camp in the cell (carrier).

[0053] SSB has a 20 RB band and a 4-symbol time. The transmission period of SSB can be set from {5, 10, 20, 40, 80, 160} ms. In a half frame, multiple symbol positions of SSB are specified based on the frequency range (FR1, FR2).

[0054] PBCH has a payload of 56 bits. N repetitions of PBCH are sent in a period of 80 ms. N depends on the SSB transmission period.

[0055] System information consists of MIB, RMSI (SIB1) and other system information (OSI) transmitted through PBCH. SIB1 contains information for RACH configuration and RACH process. The relationship between the time / frequency resources of SSB and SIB1 PDCCH monitoring resources is set through PBCH.

[0056] A base station using beam correspondence uses multiple beams to transmit multiple SSBs in each SSB transmission period. The multiple SSBs have multiple SSB indexes. A UE that detects an SSB transmits a PRACH in a RACH opportunity associated with the SSB index and receives a RAR in a RAR window.

[0057] (Beam and Coverage)

[0058] In high frequency bands, if beamforming is not applied to the synchronization signal / reference signal, the coverage becomes narrow and it is difficult for the UE to find the base station. On the other hand, if beamforming is applied to the synchronization signal / reference signal to ensure coverage, a strong signal will arrive in a specific direction, but the signal will become more difficult to reach in other directions. In the base station before the UE is connected, if the direction of the UE is unclear, it is impossible to send the synchronization signal / reference signal using a beam that is only in the appropriate direction. Consider the following method: the base station sends multiple synchronization signals / reference signals, each with a beam in a different direction, and identifies which beam the UE has found. If a thin (narrow) beam is used for coverage, more synchronization signals / reference signals need to be sent, so there is a concern that overhead will increase and frequency utilization efficiency will decrease.

[0059] If a coarse (wide) beam is used in order to reduce the number of beams (synchronization signals / reference signals) and suppress overhead, the coverage becomes narrower.

[0060] In future wireless communication systems (for example, 6G), it is expected that the use of frequency bands such as millimeter waves and terahertz waves will be further developed. It is considered that a communication service can be provided by constructing a cell area / coverage by using a large number of thin beams.

[0061] Consider expanding the area using the existing FR2 or using a higher frequency band than the existing FR2. To achieve this, in addition to multi-TRP, reconfigurable intelligent surface (RIS), etc., it is also preferable to improve beam management.

[0062] Research is underway to enhance coverage including PRACH enhancement for frequency range (FR) 2. For example, research is underway to enhance PRACH repetition using the same beam or multiple different beams. This PRACH enhancement can also be applied to the 4-step RACH process and can also be applied to FR1.

[0063] PRACH enhancement can be applied to both short PRACH formats and other formats.

[0064] (PRACH)

[0065] like Figure 1 , the common RACH configuration (RACH-ConfigCommon) may also include the general RACH configuration (rach-ConfigGeneric), the total number of RA preambles (totalNumberOfRA-Preambles), the SSBs per RACH opportunity, and the contention-based (CB) preambles per SSB (ssb-perRACH-OccasionAndCB-PreamblesPerSSB). rach-ConfigGeneric may also include the PRACH configuration index (prach-ConfigurationIndex) and the message (message) 1FDM (msg1-FDM, the number of PRACH opportunities FDMed in one time instance). ssb-perRACH-OccasionAndCB-PreamblesPerSSB may also be the number of SSBs per RACH opportunity 1 / 8 (one eighth (one SSB is associated with 8 RACH opportunities), including the number of CB preambles per SSB.

[0066] For type 1 random access procedure (4-step random access procedure, messages 1 / 2 / 3 / 4), the UE may also be provided with the number of SS / PBCH blocks associated with one PRACH opportunity, N, and the number of CB preambles per SS / PBCH block per valid PRACH opportunity, R, via ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0067] For a Type 1 random access procedure, or for a Type 2 random access procedure with a PRACH opportunity configured independently of a Type 1 random access procedure (2-step random access procedure, message A / B), if N<1, one SS / PBCH block is mapped to 1 / N consecutive valid RACH opportunities, and for each valid PRACH opportunity, the R CB preambles with consecutive indices associated with the SS / PBCH block index start from preamble index 0. If N≥1, for each valid PRACH opportunity, the R CB preambles with consecutive indices associated with the SS / PBCH block index n (0≤n<-N-1) start from preamble index n・N_preamble^total / N. Here, N_preamble^total is given by totalNumberOfRA-Preambles for the type 1 random access procedure, and by msgA-TotalNumberOfRA-Preambles for the type 2 random access procedure with the setting of PRACH opportunities independent of the type 1 random access procedure. N_preamble^total is a multiple of N.

[0068] Starting from frame 0, the association period used to map SS / PBCH blocks to PRACH opportunities is to make N Tx SSB The minimum value in the set determined by the PRACH configuration 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 (the number of PRACH configuration periods) (the relationship specified in the specification). Here, the UE obtains N according to the value of the SSB position in the burst (ssb-PositionsInBurst) in SIB1 or in the public service cell configuration (ServingCellConfigCommon). Tx SSB If after an integer number of mapping cycles from SS / PBCH block index to PRACH opportunity during the associated period, there is a block that is not mapped to N Tx SSBIn the case of a set of PRACH opportunities or PRACH preambles with SS / PBCH block indices, an SS / PBCH block index is not mapped to the set of PRACH opportunities or PRACH preambles. The association pattern period includes more than one association period and is determined so that the pattern between PRACH opportunities and SS / PBCH block indices is repeated at most every 160ms. If there is a PRACH opportunity that is not associated with an SS / PBCH block index after an integer number of association periods, then the PRACH opportunity is not used for PRACH.

[0069] In the case of a PRACH transmission triggered by a higher layer (PRACH transmission not triggered by a PDCCH command), if ssb-ResourceList is provided, the PRACH mask index is represented by ra-ssb-OccasionMaskIndex. The ra-ssb-OccasionMaskIndex indicates that the PRACH opportunity is the PRACH opportunity for the PRACH transmission associated with the selected SS / PBCH block index.

[0070] The PRACH opportunity is mapped consecutively for each corresponding SS / PBCH block index. The index addition of the PRACH opportunity represented by the mask index value is reset for each SS / PBCH block index and each mapping period of consecutive PRACH opportunities. The UE selects the PRACH opportunity represented by the PRACH mask index value for the indicated SS / PBCH block index in the first available mapping period for PRACH transmission.

[0071] For the indicated preamble index, the order of PRACH opportunities is as follows.

[0072] ・First, the increasing order of frequency resource indexes for PRACH opportunities used for frequency reuse.

[0073] ・Second, the increasing order of time resource indexes of PRACH opportunities used for time multiplexing within a PRACH slot.

[0074] ・Third, the ascending order of the PRACH slot index.

[0075] For PRACH transmission triggered by a request from a higher layer, if csirs-ResourceList is provided, the value of ra-OccasionList represents a list of PRACH opportunities for PRACH transmission, and the PRACH opportunities are associated with the selected CSI-RS index represented by csi-RS. The index attachment of the PRACH opportunities represented by ra-OccasionList is reset for each association mode period.

[0076] For PRACH setting periods of 10, 20, 40, 80, and 160 [msec], the associated periods are {1, 2, 4, 8, 16}, {1, 2, 4, 8}, {1, 2, 4}, {1, 2}, and {1}, respectively.

[0077] The value of the PRACH mask index value (msgA-SSB-SharedRO-MaskIndex) is associated with the allowed PRACH opportunities (the value of the PRACH opportunity index) of the SSB.

[0078] Figure 2A An example (mapping 1) of the association between PRACH opportunities (RACH opportunities (RO)) and beams (SSB / CSI-RS) based on the high-level parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB is shown. ssb-perRACH-OccasionAndCB-PreamblesPerSSB means oneHalf, n16 (one half, n16) (N=1 / 2, R=16). When msg1-FDM is 4, 4 ROs are FDMed in one time instance, and one SSB is mapped to 2 ROs. Preamble indices 0 to 15 are associated with 2 ROs, and preamble indices 0 to 15 are associated with SS0B. Like this, when N<1, one SSB is mapped to multiple ROs. Thereby, the capacity of the RO of each beam is improved.

[0079] Figure 2B Another example (mapping 2) of the association between RO and beam based on the high-level parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB is shown. When ssb-perRACH-OccasionAndCB-PreamblesPerSSB represents n4, n16 (N=4, R=16), msg1-FDM is 4, and N_preamble^total is 64, 4 ROs are FDMed in one time instance, and 4 SSBs are mapped to one RO. SSB0 to 3 are associated with one RO. 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 preamble indexes 48 to 63 are associated with SSB3. Like this, 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 SS / PBCH block indices to be associated through the received PRACH.

[0080] The random access preamble can be sent only in the time resources specified in the random access configuration of the specification, depending on whether it is FR1 or FR2, and the spectrum type (paired spectrum / supplementary uplink (SUL) / unpaired spectrum). The PRACH configuration index is given by the higher layer parameter prach-ConfigurationIndex, or if configured by msgA-PRACH-ConfigurationIndex. In the specification, each value of the PRACH configuration index is associated with the preamble format, x and y in n_f (frame number) mod x = y, the subframe number, the starting codeword, the number of PRACH time slots in a subframe, the number of time domain PRACH opportunities in a PRACH time slot N_t^RA,slot, and the PRACH duration N_dur^RA.

[0081] Depending on different purposes, such as whether PRACH repetition can be applied to a scenario, the type of the triggered RACH process is different. The type of the RACH process may also be at least one of the following.

[0082] ・Contention-free random access (CFRA), PDCCH ordered RA (PDCCH ordered RA, RA initiated by PDCCH command), CFRA for beam failure recovery (BFR), CFRA for system information (SI) request, CFRA for reconfiguration with sync, etc.

[0083] ・Contention-based random access (CBRA), RA triggered by the MAC entity, RA triggered by RRC with events, CBRA for BFR, etc.

[0084] ・4-step RACH.

[0085] ・2-step RACH.

[0086] (PDCCH opportunity)

[0087] DCI format 1_0 contains a DCI format identifier field, a bit field that is always set to 1, and a frequency domain resource assignment field. When the cyclic redundancy check (CRC) of DCI format 1_0 is scrambled by C-RNTI and the frequency domain resource assignment field is all 1, this DCI format 1_0 is used for the random access process started by the PDCCH command, and the remaining fields are the random access preamble, UL / supplementary uplink (SUL) indicator, SS / PBCH index (SSB index), PRACH mask index, and reserved bits (12 bits).

[0088] In the case of PRACH transmission triggered by a PDCCH command, when the value of the random access preamble index field is not zero, the PRACH mask index field (PRACH mask index fiel) indicates that the PRACH opportunity is a PRACH transmission associated with the SS / PBCH block index indicated by the SS / PBCH block index field of the PDCCH command.

[0089] (Random access procedure in MAC entity)

[0090] The random access procedure is started by a PDCCH command, the MAC entity itself, or RRC for events that conform to the specification. Within the MAC entity, at any point in time, there is only one random access procedure in progress. The random access procedure for SCell is only started by a PDCCH command with a ra-PreambleIndex different from 0b000000.

[0091] When the random access process is started on the serving cell, the MAC entity performs the following operations.

[0092] ・When the random access procedure is started by a PDCCH command and the ra-PreambleIndex explicitly provided by the PDCCH is not 0b000000, or when the random access procedure is started for synchronization reconfiguration and for the BWP selected for the random access procedure, 4-step RA type contention-free random access resources are explicitly provided by rach-ConfigDedicated, RA_TYPE is set to 4-stepRA.

[0093] When the selected RA_TYPE is set to 4-step RA, the MAC entity performs the following operations.

[0094] ・When ra-PreambleIndex is explicitly provided by PDCCH and ra-PreambleIndex is not 0b000000, PREAMBLE_INDEX is set to the notified ra-PreambleIndex and the SSB notified by PDCCH is selected.

[0095] ・When an SSB is selected as described above, the next available PRACH opportunity is selected from the PRACH opportunities corresponding to the selected SSB that are permitted by the restrictions given by ra-ssb-OccasionMaskIndex (the MAC entity randomly selects a PRACH opportunity with medium probability from consecutive PRACH opportunities corresponding to the selected SSB in accordance with the specification. When determining the next available PRACH opportunity corresponding to the selected SSB, the MAC entity may also consider the possibility of generating a measurement gap).

[0096] (Time between PDCCH command reception and PRACH transmission)

[0097] If the random access procedure is started by a PDCCH command, if requested by higher layers, the UE shall transmit PRACH in the selected PRACH opportunity if the time between the last symbol received by the PDCCH command and the first symbol sent by the PRACH is greater than N_(T,2)+Δ_BWPSwitching+Δ_Delay+T_switch[msec] (time condition) as specified in the specification. Here, N_(T,2) is the duration of N_2 symbols corresponding to the PUSCH preparation time of UE processing capability 1. Assume that μ corresponds to the minimum SCS setting between the subcarrier spacing (SCS) setting of the PDCCH command and the corresponding SCS setting of the PRACH transmission. In the case that the active UL BWP does not change, Δ_BWPSwitching=0, otherwise Δ_BWPSwitching is defined in the specification. In FR1, Δ_delay=0.5msec, in FR2, Δ_delay=0.25msec. T_switch is the switching gap duration defined in the specification.

[0098] (Conditions for validity (valid) / invalidation (invalid) of PRACH opportunity (validity conditions))

[0099] In paired spectrum (FDD) or SUL band, all PRACH opportunities are valid. In unpaired spectrum (TDD), PRACH opportunities can also follow the following rules 1 and 2.

[0100] [Regulation 1]

[0101] When the UE is not provided with tdd-UL-DL-ConfigurationCommon, a PRACH opportunity in a PRACH slot does not precede an SS / PBCH block in the PRACH slot, and is valid when it starts at least N_gap symbols after the last SS / PBCH block reception symbol. Here, N_gap is specified in the specification. When channelAccessMode=semistatic is provided, the set of consecutive symbols before the start of the next channel occupancy time when the UE does not transmit does not overlap. 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.

[0102] [Regulation 2]

[0103] When the UE is provided with tdd-UL-DL-ConfigurationCommon, the PRACH opportunities in the PRACH slot are valid in the following cases.

[0104] ・The PRACH opportunity is within the UL symbol. Or,

[0105] ・This PRACH opportunity does not precede the SS / PBCH block in the PRACH timeslot, but starts at least N_gap symbols from the last DL codeword and at least N_gap codewords from the last SS / PBCH block codeword. Here, N_gap is specified in the specification. If channelAccessMode=semistatic is provided, this PRACH opportunity does not overlap with the set of consecutive codewords before the start of the next channel occupancy time without any transmission, as described 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.

[0106] (RAR window)

[0107] RA Response Window (ra-ResponseWindow) is a time window for monitoring RA Response (RAR) (SpCell only). 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 2-step RA type (SpCell only).

[0108] In the present disclosure, SpCell, primary cell (PCell), and primary secondary cell (PSCell) may be replaced with each other.

[0109] If the RA preamble is sent, the MAC entity performs the following operations 1 to 3 regardless of the possibility of generating a measurement gap.

[0110] [Operation 1]

[0111] If the contention-free RA preamble for the BFR request is sent through the MAC entity, the MAC entity performs the following operations 1-1 and 1-2.

[0112] [[Operation 1-1]] The MAC entity starts the ra-ResponseWindow set in the BFR setting (BeamFailureRecoveryConfig) in the first PDCCH opportunity after the end of the RA preamble code transmission.

[0113] [[Operation 1-2]] The MAC entity monitors PDCCH transmission in the search space indicated by the BFR search space ID (recoverySearchSpaceId) of the SpCell identified by the C-radio network temporary identifier (RNTI) while the ra-ResponseWindow is operating.

[0114] [Operation 2]

[0115] Otherwise, the MAC entity performs the following operations 2-1 and 2-2.

[0116] [[Operation 2-1]] The MAC entity starts the ra-ResponseWindow set in the common RACH configuration (RACH-ConfigCommon) in the first PDCCH opportunity after the end of the RA preamble transmission.

[0117] [[Operation 2-2]] The MAC entity monitors the PDCCH transmission of the SpCell for the RAR identified by the RA-RNTI while the ra-ResponseWindow is operating.

[0118] [Operation 3]

[0119] If the ra-ResponseWindow set in BeamFailureRecoveryConfig expires and a PDCCH transmission on the search space indicated by recoverySearchSpaceId sent to C-RNTI is received on the serving cell on which the preamble was sent, or if the ra-ResponseWindow set in RACH-ConfigCommon expires and a RAR containing RA preamble identifiers consistent with the sent preamble index (PREAMBLE_INDEX) is received, the MAC entity considers the RAR reception to have failed and increases the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) by 1.

[0120] The MAC entity may also stop the ra-ResponseWindow (and may also stop monitoring for the RAR) after successfully receiving a RAR containing RA preamble identifiers consistent with the sent PREAMBLE_INDEX.

[0121] There are two cases for monitoring the PDCCH in the RA response window: the PDCCH used for the base station's response to the BFR and the PDCCH used for the RAR. The following contents can also be applied to both cases.

[0122] If the MSGA (Msg.A) preamble is sent, the MAC entity performs the following operations 4 to 6 regardless of the possibility of generating a measurement gap.

[0123] [Operation 4]

[0124] The MAC entity starts the Msg.B response window (msgB-ResponseWindow) in the PDCCH monitoring window specified in the specification.

[0125] The msgB-ResponseWindow may also start at the first symbol of the earliest CORESET in which the UE is configured to receive a PDCCH for a Type-1-PDCCH CSS set, where the symbol is at least one symbol after the last symbol of the PRACH opportunity corresponding to the PRACH transmission. The length of the msgB-ResponseWindow may also correspond to the SCS for the Type-1-PDCCH CSS set.

[0126] [Operation 5]

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

[0128] [Operation 6]

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

[0130] The RA-RNTI associated with the PRACH opportunity in which the RA preamble is transmitted is calculated as follows.

[0131] RA-RNTI = 1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

[0132] Here, s_id is the index of the first OFDM symbol of the PRACH opportunity (0≤s_id<14). t_id is the index of the first time slot of the PRACH opportunity within the system frame (0≤t_id<80). The subcarrier spacing (SCS) used to determine t_id is based on the value of μ. f_id is the index of the PRACH opportunity 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) carrier and 1 for supplementary uplink (SUL) carrier). RA-RNTI is calculated according to the specification. RA-RNTI is the RNTI for 4-step RACH.

[0133] The MSGB-RNTI associated with the PRACH opportunity in which the RA preamble is transmitted is calculated as follows.

[0134] MSGB-RNTI = 1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2

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

[0136] (RAR monitoring)

[0137] Based on the PRACH transmission, the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in a window controlled by the aforementioned higher layers. The window starts in the first symbol of the earliest CORESET for which the UE is configured to receive a PDCCH for a type-1-PDCCH CSS set, i.e., at least 1 symbol after the last symbol of the PRACH opportunity corresponding to the PRACH transmission. The symbol period corresponds to the SCS for the type-1-PDCCH CSS set. The length of the window is based on the SCS for the type-1-PDCCH CSS set, provided by ra-responseWindow as a number of slots.

[0138] If the UE detects a DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI and the LSBs of the SFN field within the DCI format that are identical to the least significant bits (LSBs) of the system frame number (SFN) of the PRACH transmitted by the UE, and the UE receives a transport block within the corresponding PDSCH, the UE may also assume the same DMRS antenna port QCL properties with respect to the SS / PBCH blocks or CSI-RS resources used by the UE in the association of the PRACH, regardless of whether the UE is provided with a TCI-State for a CORESET receiving the PDCCH accompanied by this DCI format 1_0.

[0139] If the UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI based on a PRACH transmission started by a PDCCH order triggering a CFRA procedure for the SpCell, the UE may also assume that the PDCCH containing the DCI format 1_0 and the PDCCH order have the same DMRS antenna port QCL properties. If the UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI based on a PRACH transmission started by a PDCCH order triggering a CFRA procedure for the secondary cell, the UE may also assume the DMRS antenna port QCL properties of the CORESET associated with the Type 1-PDCCH CSS set used to receive the PDCCH containing the DCI format 1_0.

[0140] The RAR UL grant may also include at least one of 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, and a channel access-cyclic prefix extension (CPext) field.

[0141] In single cell operation, or operation accompanied by carrier aggregation in the same frequency band, if the qcl-Type set for the 'typeD' properties of the DMRS used to monitor the PDCCH in the type-1-PDCCH CSS set is not set to the same as the qcl-Type set for the 'typeD' properties of the DMRS used to monitor the PDCCH in the type-0 / 0A / 0B / 2 / 3-PDCCH CSS set or in the USS set, and the PDCCH or the associated PDSCH overlaps with the PDCCH or the associated PDSCH monitored by the UE in the type-1-PDCCH CSS set on at least one codeword, the UE does not assume to monitor the PDCCH in the type-0 / 0A / 0B / 2 / 3-PDCCH CSS set or in the USS set.

[0142] If the UE is provided with more than one search space set via PDCCH-Config, via a corresponding one of searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, peiSearchSpace, ra-SearchSpace, and CSS sets, and is provided with SI-RNTI, P-RNTI, PEI-RNTI, RA-RNTI, MsgB-RNTI, SFI-RNTI, INT-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI, for any of these RNTIs, the UE does not assume processing of information from more than one DCI format in each time slot, wherein the more than one DCI format is accompanied by a CRC scrambled with the RNTI.

[0143] (Message 3 PUSCH (Msg3 PUSCH)

[0144] The UE sends a transport block in the PUSCH scheduled by the RAR UL grant in the corresponding RAR message. μ ・K cell,offset The PUSCH is sent within K cell,offset The cell can be provided by CellSpecific_Koffset. If it is not provided, K cell,offset =0.

[0145] k2 is the time slot offset, which is determined based on the row index m+1 of the configuration table provided by the PUSCH time resource configuration (allocation) field value m granted by the RAR UL, and the PUSCH subcarrier spacing μPUSCH. Δ is the additional subcarrier spacing specific time slot delay time value for the initial transmission of the PUSCH scheduled by the RAR, which is specific to the PUSCH subcarrier spacing μPUSCH and is applied in addition to K2.

[0146] If the UE requests repetition of PUSCH transmission, the UE PUSCH repeat Here, N PUSCH repeatFor example, it is indicated by the 2MSBs of the MCS field within the RAR UL grant or DCI format 0_0, from a set of 4 values ​​provided by numberOfMsg3Repetitions, or from {1, 2, 3, 4} if numberOfMsg3Repetitions is not provided.

[0147] The UE decides whether to apply Msg3 repetition based on RSRP. When Msg repetition is set and the RSRP referenced by the DL path loss is less than rsrp-ThresholdMsg3 (threshold), the MAC entity assumes that message 3 repetition can be applied to the current random access (RA) procedure.

[0148] The UE can request Msg3 PUSCH repetition via a dedicated PRACH resource. The MAC entity selects RA resources in the following cases: that is, there are more than one sets of available RA resources, and one of the more than one sets is used in the indication of all functions that trigger the RA process; and there are more than one set scheduling of available RA resources that are set for indication of a subset of all functions that trigger the RA process. When the Msg3 repetition operation is set for a set of RA resources, when the Msg3 repetition cannot be used, the MAC entity regards the set of RA resources as unusable for the RACH process.

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

[0150] The following contents are notified in SIB1 transmitted by the base station.

[0151] ・The priority of each function (priority, featurePriorities-r17). This priority is used to determine which FeatureCombinationPreambles the UE uses when a function is mapped to more than one FeatureCombinationPreamble.

[0152] ・Additional RO settings. This setting includes available functions (which are associated with multiple functions), RA resources (for example, preamble index), and mask index for distinguishing ROs.

[0153] The UE determines the RO to be used depending on this function.

[0154] SIB1 contains ServingCellConfigCommonSIB, which contains UplinkConfigCommonSIB, which contains BWP-UplinkCommon (UL BWP common settings).

[0155] BWP-UplinkCommon may also include RACH common configuration (RACH-ConfigCommon or MsgA-ConfigCommon), additionalRACH-ConfigList-r17 (additional RACH configuration list). additionalRACH-ConfigList-r17 may also include rsrp-ThresholdMsg3-r17 (threshold value).

[0156] RACH common settings may also include FeatureCombinationPreambles. FeatureCombinationPreambles associates a set of preambles (partitions) with a feature combination. FeatureCombinationPreambles may also include FeatureCombination (feature combination settings), startPreambleForThisPartition (index of the initial 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 initial preamble and the number of preambles.

[0157] The available RO is explicitly set by the PRACH mask index. Using the relationship between the PRACH mask index and the permitted PRACH opportunities (RO) of the SSB (MAC protocol specification / table of PRACH mask index values), at least one of the PRACH opportunity indexes 1 to 8 can be set.

[0158] 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.

[0159] In PUSCH repetition type A, when a PUSCH scheduled by a RAR UL grant is transmitted, the 2MSBs of the MCS information field of the RAR UL grant provide a code point for determining the number of repetitions K based on the relationship (table) between the value (code point) of the 2MSBs of the MCS information field and the number of repetitions K, based on whether the higher layer parameter numberOfMsg3Repetitions is set. The number of time slots N used for transport block size (TBS) determination is equal to 1.

[0160] In PUSCH repetition type B, when a PUSCH scheduled by DCI format 0_0 is transmitted and the DCI format 0_0 is accompanied by a CRC scrambled by TC-RNTI, the 2MSBs of the MCS information field of the DCI format provide a code point for determining the number of repetitions K based on the value (code point) of the 2MSBs of the MCS information field and the relationship (table) between the number of repetitions K and the number of repetitions K, based on whether the higher layer parameter numberOfMsg3Repetitions is set. The number of time slots N used for TBS determination is equal to 1

[0161] (Contention resolution)

[0162] If Msg3 is sent, the MAC entity follows operations 1 to 4 below.

[0163] [Operation 1] If Msg3 is sent on a non-terrestrial network, the MAC entity starts the ra-ContentionResolutionTimer and restarts the end of Msg3 in each HARQ retransmission within the first codeword after the UE estimate of the UE-gNB RTT.

[0164] [Operation 2] Otherwise, if the Msg3 transmission (initial transmission or HARQ retransmission) is scheduled with type A PUSCH repetition, the MAC entity starts or restarts the ra-ContentionResolutionTimer within the first codeword after all repetitions of the Msg3 transmission are completed.

[0165] [Operation 3] Otherwise, the MAC entity starts or restarts the ra-ContentionResolutionTimer within the first codeword after the Msg3 is sent.

[0166] [Operation 4] The MAC entity monitors the PDCCH regardless of the possibility of the occurrence of a measurement gap while the ra-ContentionResolutionTimer is operating.

[0167] Step 4 (Msg4) of the RA process of Rel. 16 NR follows the Step 4 operation below.

[0168] [Step 4 Operation]

[0169] In the case where no C-RNTI is provided to the UE, based on a PUSCH transmission scheduled via a RAR UL grant, the UE attempts to detect: DCI format 1_0 scheduling a PDSCH containing a UE contention resolution identity with a CRC scrambled by the corresponding TCI-RNTI. Based on reception of a PDSCH containing a UE contention resolution identity, the UE transmits HARQ-ACK information in the PUCCH. The PUCCH transmission is within the same active UL BWP as the PUSCH transmission. The minimum time between the last symbol received on the PDSCH 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 symbols equivalent to the PDSCH processing time of UE processing capability 1 when additional PDSCH DM-RS is configured. For μ=0, the UE assumes N_T,1=14.

[0170] When detecting the DCI format based on a PUSCH transmission scheduled by a RAR UL grant or a corresponding PUSCH retransmission scheduled by DCI format 0_0 with a CRC scrambled by the TC-RNTI provided in the corresponding RAR message, the UE may also assume, for the PDCCH transmitting the DCI format, the same DM-RS antenna port quasi co-location (QCL) properties as for the SS / PBCH blocks used by the UE for PRACH association, regardless of whether the TCI state of the CORESET at which the UE received the PDCCH with the DCI format was provided to the UE.

[0171] (PUCCH before dedicated PUCCH resource setting)

[0172] If the UE does not have a dedicated PUCCH resource configuration provided by PUCCH-ResourceSet in PUCCH-Config, by adding to the table of multiple PUCCH resource sets before the dedicated PUCCH resource configuration specified in the specification (default PUCCH resource table, Figure 3 ) is provided by pucch-ResourceCommon for N BWP size The PUCCH resource set (default PUCCH resources) for sending HARQ-ACK information on the PUCCH within the initial UL BWP of PRBs.

[0173] pucch-ResourceCommon included in SIB1 indicates the value of index 0 to 15. The default PUCCH resource table associates the index with the PUCCH resource set. Each PUCCH resource set includes a set of PUCCH format 0 / 1, the initial codeword of the PUCCH, the number of codewords of the PUCCH, the PRB offset of the PUCCH, and the initial cyclic offset index. The UE determines the PUCCH resources in the PUCCH resource set indicated by the index based on the PDCCH that schedules the PDSCH (the initial CCE of the PDCCH, the PUCCH resource indicator field in the DCI).

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

[0175] If the UE is not provided with any of pdsch-HARQ-ACK-Codebook, pdsch-HARQ-ACK-Codebook-r16, and pdsch-HARQ-ACK-OneShotFeedback, the UE generates at most one HARQ-ACK information bit.

[0176] (question)

[0177] In the following questions Figure 4A , 4B In the examples of 5A, 5B, and 6, the UE sends repetitions of PRACH (Msg1#1 to #4) and starts a RAR window after each repetition.

[0178] In multiple PRACH repetitions accompanied by multiple Msg2 / 3 / 4, the following issues are considered.

[0179] ・Overlap of multiple RAR windows.

[0180] [Question 1] Maintaining the RAR window and monitoring / processing the PDCCH within the overlapping RAR window ( Figure 4A ) is not clear.

[0181] ・Overlap of multiple Msg3s scheduled by multiple RARs.

[0182] [Question 2] Msg3 PUSCH transmission operation ( Figure 4B ) is not clear.

[0183] ・Overlap of multiple contention resolution windows.

[0184] [Question 3] Maintenance of multiple contention resolution windows and monitoring of PDCCH within overlapping contention resolution windows ( Figure 5B ) is not clear.

[0185] ・Overlap of more than one RAR window and more than one contention resolution window.

[0186] [Issue 4] Monitoring / processing of PDCCH within overlapping RAR windows / contention resolution windows ( Figure 5B ) is not clear.

[0187] ・HARQ-ACK feedback for multiple Msg4s.

[0188] [Question 5] In the existing specification, the UE supports more than one HARQ-ACK information bit per PUCCH before the dedicated PUCCH resource (RRC) is set. In the case where multiple HARQ-ACK information bits for multiple Msg4 PDSCHs are in the same slot ( Figure 6 ) is not clear.

[0189] If such an operation is not clear, there is a concern that the communication quality may be degraded.

[0190] Therefore, the inventors of the present invention conceived of an operation accompanied by PRACH repetition.

[0191] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In addition, each of the following embodiments (for example, each case) can be used alone or in combination of at least two.

[0192] In the present disclosure, "A / B" and "at least one of A and B" may be replaced with each other. In addition, in the present disclosure, "A / B / C" may also mean "at least one of A, B, and C".

[0193] In the present disclosure, activate, deactivate, indicate (or specify), select, configure, update, determine, etc. may also be mutually rewritten. In the present disclosure, support, control, controllable, operate, and can operate may also be mutually rewritten.

[0194] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, high-layer parameters, information elements (IE), settings, etc. may also be overwritten with each other. In the present disclosure, Medium Access Control (MAC) control elements (MAC Control Element (CE)), update commands, activation / deactivation commands, etc. may also be overwritten with each other.

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

[0196] In the present disclosure, MAC signaling may also use, for example, MAC Control Element (MACCE), MAC Protocol Data Unit (MAC Protocol Data Unit (PDU)), etc. Broadcast information may also be, for example, Master Information Block (MIB), System Information Block (SIB), minimum system information (Remaining Minimum System Information (RMSI)), Other System Information (Other System Information (OSI)), etc.

[0197] In the present disclosure, the physical layer signaling may be, for example, downlink control information (Downlink Control Information (DCI)), uplink control information (Uplink Control Information (UCI)), etc.

[0198] In the present disclosure, an index, an identifier (ID), an indicator, a resource ID, etc. may also be overwritten with each other. In the present disclosure, a sequence, a list, a set, a group, a cluster, a subset, etc. may also be overwritten with each other.

[0199] In the present disclosure, panel, panel group, beam, beam group, precoder, uplink (UL) transmission entity, transmission / reception point (TRP), base station, spatial relation information (SpatialRelation Information (SRI)), spatial relation, SRS resource indicator (SRS Resource Indicator (SRI)), control resource set (COntrol REsource SET (CORESET)), physical downlink shared channel (Physical Downlink Shared Channel (PDSCH)), codeword (Codeword (CW)), transport block (TransportBlock (TB)), reference signal (Reference Signal (RS)), antenna port (e.g., demodulation reference signal (DeModulation Reference Signal (DMRS)) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, code division multiplexing (Code Division Multiplexing (CDM)) group, reference signal group, CORESET group, physical uplink control channel (Physical Uplink Control Channel (PUCCH)) group, PUCCH resource group), resources (for example, reference signal resources, SRS resources), resource sets (for example, reference signal resource sets), CORESET pool, downlink transmission configuration indication state (Transmission Configuration Indication state) (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state (unified TCI state), common TCI state (common TCI state), Quasi-Co-Location (Quasi-Co-Location (QCL)), QCL assumptions, etc. can also be rewritten with each other.

[0200] In this article, “having the ability to…” can also be rephrased with “the ability to support / report…”.

[0201] In the present disclosure, the SSB / CSI-RS index / indicator, beam index, TCI status, spatial domain transmit filter, and spatial domain receive filter can also be rewritten with each other.

[0202] In the present disclosure, RAR window, ra-ResponseWindow, time window, RAR timer, and operation period of the timer may also be overwritten. In the present disclosure, contention resolution window, contention window, contention resolution timer, ra-ContentionResolutionTimer, and operation period of the contention resolution timer may also be overwritten. In the present disclosure, contention resolution identifier, contention resolution ID, and UE contention resolution identifier (UE contention resolutionidentity) may also be overwritten.

[0203] In the present disclosure, ports, antenna ports, DMRS ports, and DMRS antenna ports may be replaced with each other. In the present disclosure, "ports and RS reception become QCL", "ports and RS reception use the same spatial domain (transmit / receive) filter", these may also be replaced with each other.

[0204] In the present disclosure, DCI (format) / PDCCH (candidate) with CRC scrambled by a specific RNTI, DCI (format) / PDCCH (candidate) using a specific RNTI, and DCI (format) / PDCCH (candidate) monitored by a specific RNTI may be rewritten mutually.

[0205] (Wireless Communication Method)

[0206] In each embodiment, RACH resources, RA resources, PRACH preamble, opportunity, RACH opportunity (RO), PRACH opportunity, repetition resource, repetition setting resource, resource set for RO / repetition, time instance and frequency instance, time resource and frequency resource, RO / preamble resource, repetition, these may also be replaced with each other. In each embodiment, period, cycle, frame, subframe, time slot, codeword, opportunity, RO may also be replaced with each other.

[0207] In each embodiment, PDCCH command, PDCCH command DCI, DCI format 1_0, and message (Msg) 0 may also be overwritten with each other. In each embodiment, PRACH, preamble, PRACH preamble, sequence, preamble format, and Msg1 may also be overwritten with each other. In each embodiment, the response to PRACH, RAR, Msg2, MsgB, Msg4, base station response to BFR, and DCI of scheduling response (RAR) may also be overwritten with each other. In each embodiment, transmissions other than PRACH during random access, Msg3, PUSCH scheduled by RAR, HARQ-ACK / PUCCH for Msg4, and MsgA PUSCH may also be overwritten with each other. In each embodiment, Msg3, PUSCH scheduled by RAR UL grant, and RRC connection request may also be overwritten with each other. In each embodiment, Msg4, contention resolution, RRC connection setup, and PDSCH with UE contention resolution identity may be rewritten.

[0208] In each embodiment, the RAR, the DCI (PDCCH) for scheduling the RAR, the PDSCH with the UE contention resolution ID, and the DCI for scheduling the PDSCH with the UE contention resolution ID may be rewritten.

[0209] In each implementation, beam, SSB, SSB index, CSI-RS, CSI-RS resource, CSI-RS resource index, and RS may also be overwritten.

[0210] 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 started by a PDCCH command, a random access procedure not started by a PDCCH command, and a random access procedure started by a higher layer may also be rewritten with each other.

[0211] In each embodiment, time resources, Msg1, Msg2, Msg3, Msg4, HARQ-ACK information, RAR window, contention resolution window, DCI for scheduling Msg2, and DCI for scheduling Msg4 may also be rewritten with each other. In the operation of each embodiment, an earlier time resource may be a time resource earlier than the operation within a plurality of time resources corresponding to a plurality of repetitions of PRACH, or a time resource related to an index corresponding to the repetition (time domain index) and having an index smaller than the index of the operation. In the operation of each embodiment, a later time resource may also be a time resource later than the operation within a plurality of time resources corresponding to a plurality of repetitions of PRACH, or a time resource related to an index corresponding to the repetition (time domain index) and having an index larger than the index of the operation.

[0212] <Implementation method #1>

[0213] This embodiment relates to problem 1. For multiple PRACH repetitions with the same beam / different multiple beams, one or more RARs may also follow any of the following options.

[0214] Option 1

[0215] Only one RAR window (ra-ResponseWindow) is maintained. A common ra-ResponseWindow may also be maintained for multiple repetitions. The UE may also follow any of the following options.

[0216] [Option 1-1]

[0217] The UE does not assume overlap (in the time domain) of multiple RAR windows for multiple PRACH iterations. Fig. 7A In the example, the UE sends multiple iterations of PRACH (Msg1#1 to #4). For each iteration, a RAR window is started. The UE may also follow at least one of the following examples.

[0218] [[Example 1]] The UE does not send (does not assume to send) (later) PRACH repetitions while the ra-ResponseWindow is operating.

[0219] [[Example 2]] The UE does not send (does not assume to send) a later PRACH repetition before detecting the RAR for an earlier PRACH transmission. The RAR may include a preamble identifier that is consistent with the transmitted preamble index.

[0220] [[Example 3]] The UE does not assume that the length of the ra-ResponseWindow is longer than the interval between two PRACH repetitions.

[0221] [Option 1-2]

[0222] When the ra-ResponseWindow is in operation and the UE sends a later PRACH iteration, the UE restarts the ra-ResponseWindow from the first PDCCH opportunity after the later PRACH iteration, or from the start / end of the later PRACH iteration. Figure 7B In the example, the UE sends a plurality of repetitions of RACH (Msg1#1 to #4), and starts a RAR window after each repetition. When the UE sends the next Msg1 during the operation of the RAR window, the RAR window being operated may be stopped.

[0223] In case ra-ResponseWindow is in operation, RAR monitoring operation can also follow any of the following options.

[0224] [[Option 1-2a]] The UE may also monitor the RAR using the RA-RNTI for PRACH repetitions before the PDCCH monitoring opportunity and for which the corresponding RAR is not detected, by assuming that the reception of SSB / CSI-RS for multiple PRACH repetitions is QCL'd with the DMRS antenna port. This option may also be applicable to PRACH repetitions using the same beam.

[0225] [[Option 1-2b]] The UE may also monitor the RAR using the RA-RNTI for the last PRACH repetition, assuming that the reception of the SSB / CSI-RS for the last PRACH repetition is at CQL with respect to the DMRS antenna port. This option may also be applicable to PRACH repetitions using the same beam and PRACH repetitions using different beams.

[0226] [[analyze]]

[0227] From the perspective of the base station, the base station does not recognize that the RAR window is shorter than the set length. The base station can also send the RAR for the previous PRACH iteration after the later PRACH iteration. In such a situation, the UE may fail to receive the RAR for the previous PRACH iteration.

[0228] [Options 1-3]

[0229] The UE restarts the ra-ResponseWindow for a later PRACH iteration after successfully receiving the RAR for an earlier PRACH iteration or after the ra-ResponseWindow expires. Figure 8In the example, the UE sends multiple iterations of PRACH (Msg1#1 to #4), and starts the RAR window after each iteration. After successfully receiving the RAR for Msg1#1, the UE starts the ra-ResponseWindow for the next 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 ra-ResponseWindow for the next Msg1#4.

[0230] [[example]]

[0231] The UE may also follow at least one of the following operations if: the UE sends a later PRACH repetition before detection of a RAR for an earlier PRACH repetition (containing a preamble identifier consistent with the sent preamble index) and before expiration of the ra-ResponseWindow, and restarts the ra-ResponseWindow after expiration of the ra-ResponseWindow or after detection of a RAR for an earlier PRACH repetition.

[0232] ・Before the ra-ResponseWindow is restarted, the UE may monitor the RAR using the RA-RNTI by assuming that the DMRS antenna port is QCL for the reception of the SSB / CSI-RS for the PRACH repetition earlier.

[0233] ・After the ra-ResponseWindow is restarted, the UE may monitor the RAR using the RA-RNTI by assuming that the DMRS antenna port is QCL with respect to the reception of the SSB / CSI-RS for the PRACH repetition later.

[0234] [[analyze]]

[0235] From the perspective of the base station, the base station does not recognize that the RAR window starts later than expected. The base station can also send the RAR for the later PRACH repetition before the RAR window for the earlier PRACH repetition ends. In such a situation, the UE may fail to receive the RAR for the later PRACH repetition.

[0236] [[analyze]]

[0237] The UE needs to keep track of how many windows are maintained / reserved. For example, the UE sends 3 PRACH iterations before the RAR window for the initial PRACH iteration ends.

[0238] Option 2

[0239] A dedicated RAR window (ra-ResponseWindow) is maintained for each PRACH repetition. Multiple RAR windows for multiple PRACH repetitions may also follow any of the following options.

[0240] [Option 2-1]

[0241] Overlap of multiple RAR windows (in the time domain) is not allowed. The UE may also be specified not to assume overlap of multiple RAR windows. The UE may also follow at least one of the following examples.

[0242] [[Example 1]] When any ra-ResponseWindow is operating, the UE does not send (does not assume to send) a later PRACH repetition.

[0243] [[Example 2]] The UE does not send (does not assume to send) a later PRACH repetition before detecting the RAR for an earlier PRACH repetition. The RAR may also include a preamble identifier that is consistent with the transmitted preamble index.

[0244] [[Example 3]] The UE does not assume that the start of a later PRACH iteration (or the RAR window for a later PRACH iteration) is before the end of an earlier RAR window.

[0245] [[analyze]]

[0246] When there is no overlap of multiple RAR windows, the UE does not need to maintain a dedicated ra-ResponseWindow timer for each PRACH.

[0247] [Option 2-2]

[0248] Overlap (in the time domain) of multiple RAR windows is allowed. Fig. 9 In the example of , the UE transmits multiple repetitions of PRACH (Msg1#1 to #4), and starts a RAR window after each repetition. The UE may also assume that only one QCL is used for receiving RARs in multiple overlapping RAR windows.

[0249] In multiple PDCCH monitoring opportunities of type 1 CSS for multiple RAR windows, the UE assumes that the reception of DMRS antenna ports that become QCL with any of the following options, thereby monitoring PDCCH candidates with RA-RNTI.

[0250] [[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.

[0251] [[Option 2-2b]] Reception of one SSB / CSI-RS with maximum RSRP (or one SSB / CSI-RS selected randomly, or one SSB / CSI-RS selected according to a method based on actual installation of the UE) among multiple receptions of SSB / CSI-RS corresponding to multiple PRACH repetitions corresponding to the multiple RAR windows.

[0252] Variations of Option 2

[0253] The base station may also configure / instruct different values ​​(the number of symbols / slots) of the RAR window length corresponding to different repetition indices.

[0254] [[example]]

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

[0256] [[example]]

[0257] The RAR window length for the first / last PRACH repetition may also be longer / shorter than the RAR window length for other PRACH repetitions. This example may also be applicable to a situation where the base station can identify the first / last PRACH repetition. For example, this situation may also be a situation where the RACH resources for the first PRACH repetition are independently set from the RACH resources for other PRACH repetitions. For example, this situation may also be a situation where multiple RACH resources for multiple PRACH repetitions are exclusively set and are fixed / specific positions for each PRACH repetition.

[0258] [[analyze]]

[0259] When the base station cannot identify which repetition the received Msg1 belongs to, it considers that the change is useless.

[0260] According to this embodiment, the UE can appropriately maintain more than one RAR window.

[0261] <Implementation Method #2>

[0262] This embodiment relates to problem 1. The monitoring of the PDCCH that schedules the RAR may also follow any of the following embodiments.

[0263] 《Implementation Method #2-1》

[0264] In monitoring / processing RAR in a time slot, the UE may also process / monitor up to X (X ≥ 1) DCI formats in each time slot, where the DCI format is accompanied by a CRC scrambled by the RA-RNTI. X (maximum number) may also follow any of the following options.

[0265] [Option a] No enhancement from Rel. 15 / 16 / 17. That is, X=1. The limitation of Rel. 15 / 16 / 17 may also be that it is not assumed that the UE processes information for more than one DCI format in each time slot, where the DCI format is accompanied by a CRC scrambled by SI-RNTI, P-RNTI, PEI-RNTI, RA-RNTI, MsgB-RNTI, SFI-RNTI, INT-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI.

[0266] [Option b] X may also be greater than 1. X may be defined in the specification and may also be reported by the UE as a UE capability. The specification may also define the possible values ​​of X for UE capability reporting.

[0267] The UE operation of RAR monitoring in the case of more than one PDCCH monitoring opportunity of Type 1 CSS in one slot may also follow at least one of the following options.

[0268] [Option 1]

[0269] The UE does not assume that there are time slots overlapping with more than X RAR windows for different multiple PRACH iterations.

[0270] The combination of Option 1 of Implementation #1 and Option 1 of Implementation #2-1 may also follow at least one of the following examples.

[0271] [[Example]] The UE does not send (does not assume to send) (later) PRACH repetitions in the time slot where the ra-ResponseWindow is operating.

[0272] [[Example]] The UE does not send (does not assume to send) (later) PRACH repetitions in the time slot where the ra-ResponseWindow is started / restarted X' (X' ≥ 1) times.

[0273] [Example] The UE does not send (does not assume to send) (later) PRACH iterations in a time slot in which it detects X' (X' ≥ 1) RAR messages for one or more earlier PRACH iterations. The RAR message may also include a preamble identifier that matches the transmitted preamble index.

[0274] [Example] The RAR window for a later PRACH repetition starts from a time slot after a time slot in which X' (X' ≥ 1) RAR messages for one or more earlier PRACH repetitions are successfully detected.

[0275] In the combination of Option 2 of Implementation #1 and Option 1 of Implementation #2-1, at least one of the following examples may be followed.

[0276] [[Example]] The UE does not send (does not assume to send) (later) PRACH repetitions in a time slot in which at least N (N ≥ 1) ra-ResponseWindow are operating.

[0277] [Option 2]

[0278] When there are time slots overlapping with more than X RAR windows, the UE may also follow at least one of the following options.

[0279] [[Option 2-1]] The UE does not assume multiple PDCCH monitoring opportunities of type 1 CSS within more than X RAR windows in one time slot.

[0280] [[Option 2-2]] When the UE successfully detects X RARs on multiple PDCCH monitoring opportunities in an earlier RAR window in a time slot, the UE does not monitor the RAR on the later PDCCH monitoring opportunity of type 1 CSS using RA-RNTI in the same time slot.

[0281] [[Option 2-3]] The UE monitors the PDCCH monitoring opportunities of the Type 1 CSS using the RA-RNTI in a maximum of X RAR windows in the time slot. The X RAR windows may be the first / last X RAR windows, or may be X RAR windows selected randomly, or may be X RAR windows selected according to a method based on the actual installation of the UE, or may be X RAR windows corresponding to the reception of Y SSB / CSI-RS from the maximum RSRP among the multiple receptions of SSB / CSI-RS of the multiple RARs detected.

[0282] [[Option 2-4]] The UE monitors the PDCCH monitoring opportunities of all Type 1 CSSs using RA-RNTI in a time slot and processes only X RARs within the detected multiple RARs. The X RARs may be the first / last detected X RARs, or may be X randomly selected detected RARs, or may be a window of X detected RARs selected according to a method based on the actual installation of the UE, or may be X RARs corresponding to the reception of Y SSB / CSI-RS from the maximum RSRP within multiple receptions of SSB / CSI-RS for the detected multiple RARs.

[0283] The maximum number X / maximum number Y may be defined in the specification, may be set / indicated via SIB / RRC IE, or may be reported by the UE as a UE capability. For UE capability reporting, the specification may also define the value that the maximum number may take.

[0284] For the case where X=1 without UE capability enhancement, Option 1 / 2 may also be applied. For the case where X>1 with UE capability enhancement, Option 1 / 2 may also be applied.

[0285] 《Implementation Method #2-2》

[0286] For multiple PRACH repetitions using different multiple beams, the UE processes / monitors one or more DCI formats with CRC scrambled by RA-RNTI using up to Y (Y ≥ 1) different beams in each time slot. Y (maximum number) can be defined in the specification, set / indicated by SIB / RRC IE, or reported by the UE as a UE capability. For UE capability reporting, the specification can also define the values ​​that Y can take.

[0287] The UE operation of RAR monitoring in the case of more than one PDCCH monitoring opportunity of Type 1 CSS in one slot may also follow at least one of the following options.

[0288] [Option 1]

[0289] The UE does not assume the existence of a time slot that overlaps with more than Y RAR windows (in the time domain) for multiple PRACH repetitions using different multiple beams.

[0290] In the combination of Option 1 of Implementation #1 and Option 1 of Implementation #2-2, at least one of the following examples may be followed.

[0291] [[Example]] The UE does not send (does not assume to send) a (later) PRACH repetition using a different beam during the time slot in which the ra-ResponseWindow is operating.

[0292] [[Example]] The UE does not transmit (does not assume to transmit) a (later) PRACH repetition using a different beam in a time slot where the ra-ResponseWindow is started / restarted Y' (Y' ≥ 1) times.

[0293] [Example] The UE does not send (does not assume to send) (later) PRACH iterations in a time slot in which it detects Y' (Y' ≥ 1) RAR messages for one or more earlier PRACH iterations. The RAR message may also include a preamble identifier that matches the transmitted preamble index.

[0294] [Example] The RAR window for a later PRACH repetition starts from a time slot after a time slot in which X' (X' ≥ 1) RAR messages for one or more earlier PRACH repetitions are successfully detected.

[0295] The maximum number X' / maximum number Y' may be defined in the specification, may be set / indicated via SIB / RRC IE, or may be reported by the UE as a UE capability. For UE capability reporting, the specification may also define the value that the maximum number may take.

[0296] The combination of Option 2 of Implementation #1 and Option 1 of Implementation #2-2 may also follow at least one of the following examples.

[0297] [[Example]] The UE does not send (does not assume to send) (later) PRACH repetitions in a time slot in which at least N (N ≥ 1) ra-ResponseWindow are operating.

[0298] [Option 2]

[0299] When there are time slots overlapping with more than Y RAR windows (in the time domain) for different multiple PRACH repetitions utilizing different multiple beams, the UE may also follow at least one of the following options.

[0300] [[Option 2-1]] The UE does not assume multiple PDCCH monitoring opportunities of type 1 CSS within more than Y RAR windows in one time slot.

[0301] [[Option 2-2]] When the UE successfully detects Y RARs on multiple PDCCH monitoring opportunities in an earlier RAR window in a time slot, the UE does not monitor the RARs on the later PDCCH monitoring opportunities of type 1 CSS using RA-RNTI in the same time slot.

[0302] [[Option 2-3]] The UE monitors the PDCCH monitoring opportunities of the Type 1 CSS using the RA-RNTI within a maximum of Y RAR windows within the time slot. The Y RAR windows may be the first / last Y RAR windows, or may be Y RAR windows selected randomly, or may be Y RAR windows selected based on a method based on the actual installation of the UE, or may be Y RAR windows corresponding to Y SSB / CSI-RS receptions from the maximum RSRP within multiple receptions of SSB / CSI-RS of multiple RARs detected.

[0303] [[Option 2-4]] The UE monitors the PDCCH monitoring opportunities of all Type 1 CSSs using RA-RNTI in a time slot and processes only Y RARs within the detected multiple RARs. The Y RARs may be the first / last detected Y RARs, or may be the Y detected RARs selected randomly, or may be a window of Y detected RARs selected according to a method based on the actual installation of the UE, or may be the Y RARs corresponding to the reception of Y SSB / CSI-RS from the maximum RSRP within the multiple receptions of SSB / CSI-RS for the detected multiple RARs.

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

[0305] <Implementation Method #3>

[0306] This embodiment relates to Problem 2. Multiple Msg3 PUSCHs corresponding to multiple received RARs may also follow at least one of the following situations.

[0307] Scenario 1

[0308] The multiple Msg3 PUSCHs do not overlap in the time domain, or the gap between the multiple Msg3 PUSCHs is longer than the gap (time) required for beam switching.

[0309] In this case, the UE may also follow any of the following options.

[0310] [Option 1-1] UE sends each Msg3 PUSCH.

[0311] [Option 1-2] The UE sends a maximum of X (X=1 or X>1) Msg3 PUSCHs in one time slot. X (maximum number) can be defined in the specification, set / indicated by SIB / RRC IE, or reported by the UE as a UE capability. The maximum number of Msg3 PUSCHs can also be one of the following options.

[0312] [[Option 1-2A]] The first / last Msg3 PUSCH among multiple Msg3 PUSCHs in the time slot / time slot group.

[0313] [[Option 1-2B]] X Msg3 PUSCHs are scheduled by the first / last detected X RARs among multiple RARs for multiple Msg3 PUSCHs in the time slot / time slot group.

[0314] [[Option 1-2C]] For the multiple receptions of SSB / CSI-RS of multiple Msg3 PUSCHs in the time slot / time slot group, the X Msg3 PUSCHs corresponding to the reception of X SSB / CSI-RS starting from the maximum RSRP.

[0315] [[Option 1-2D]] For the X Msg3 PUSCHs randomly selected from the multiple Msg3 PUSCHs in the time slot / time slot group, or X Msg3 PUSCHs selected according to a method based on the actual installation of the UE.

[0316] Scenario 2

[0317] 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.

[0318] In this case, the UE may also send one of multiple Msg3 PUSCHs that overlap with each other.

[0319] In this case, the UE may also follow any of the following options.

[0320] [Option 2-1] The UE sends the first / last Msg3PUSCH within multiple Msg3 PUSCHs that overlap with each other in the time domain, or the Msg3 PUSCH scheduled by the first / last received RAR; or, sends the first / last Msg3 PUSCH within 2 PUSCHs that do not overlap and have a gap shorter than the gap required for beam switching; or the Msg3 PUSCH scheduled by the first / last received RAR.

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

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

[0323] [Option 2-4] The UE transmits a randomly selected Msg3 PUSCH from among a plurality of Msg3 PUSCHs that overlap each other in the time domain; or a Msg3 PUSCH selected according to a method based on actual installation of the UE.

[0324] According to this embodiment, the UE can appropriately send one or more Msg3 in response to a plurality of received RARs.

[0325] <Implementation Method #4>

[0326] This embodiment relates to problem 3. For Msg3 PUSCH for PRACH repetition using the same beam / different multiple beams, one or more contention resolution windows may also follow any of the following options.

[0327] Option 1

[0328] Only one contention resolution window is maintained. A common contention resolution timer (ra-ContentionResolutionTimer) may also be maintained for multiple iterations. The UE may also follow at least one of the following options.

[0329] [Option 1-1]

[0330] The UE does not assume the overlap (in the time domain) of multiple contention resolution windows for multiple Msg3 PUSCHs scheduled by multiple RARs. The UE may also follow at least one of the following examples.

[0331] [[Example 1]] When the UE is operating the ra-ContentionResolutionTimer, it does not send (does not assume to send) a (later) Msg3 PUSCH.

[0332] [[Example 2]] The UE does not send (does not intend to send) a (later) Msg3 PUSCH before detecting DCI format 1_0 scheduling a PDSCH containing the UE contention resolution ID and accompanied by a CRC scrambled by the corresponding TC-RNTI.

[0333] [Option 1-2]

[0334] In the case where the ra-ContentionResolutionTimer is operating, the UE restarts the ra-ContentionResolutionTimer from the first symbol after the later Msg3 PUSCH or from the first symbol of the later Msg3 PUSCH.

[0335] Contention resolution ID monitoring operations may also follow any of the following options.

[0336] [[Option 1-2a]] In case the ra-ContentionResolutionTimer is operating, the UE assumes that the reception of SSB / CSI-RS for multiple PRACH iterations is CQL for the DMRS antenna port, thereby monitoring DCI format 1_0, where the DCI format 1_0 is before the PDCCH monitoring opportunity and the corresponding PDCCH is not detected, and is accompanied by a CRC scrambled by the TC-RNTI. This option can also be applied to PRACH iterations using the same beam.

[0337] [[Option 1-2b]] When the ra-ContentionResolutionTimer is in operation, the UE assumes that the DMRS antenna port with the SSB / CSI-RS reception for the last Msg3 PUSCH is CQL, thereby monitoring the DCI format 1_0 for the last Msg3 PUSCH, where the DCI format 1_0 is accompanied by a CRC scrambled by the TC-RNTI. This option can also be applied to PRACH repetitions using the same beam, and can also be applied to PRACH repetitions using different multiple beams.

[0338] [[analyze]]

[0339] From the perspective of the base station, the base station does not recognize that the contention resolution window is shorter than the set length. The base station can also send a PDCCH for scheduling Msg4 for the previous Msg3 PUSCH after the later Msg3 PUSCH.

[0340] [Options 1-3]

[0341] The UE starts the contention resolution window for the later Msg3 PUSCH after successfully detecting the PDCCH for the earlier Msg3 PUSCH or after the ra-ContentionResolutionTimer expires (UE starts the contention resolution window for the later Msg3 PUSCH). The UE may also follow the following example.

[0342] [[example]]

[0343] If the UE sends a later Msg3 PUSCH before detection of a PDCCH with a CRC scrambled by TC-RNTI for an earlier Msg3 PUSCH and before expiration of the ra-ContentionResolutionTimer, the UE restarts the ra-ContentionResolutionTimer after expiration of the ra-ContentionResolutionTimer or after detection of a PDCCH with a CRC scrambled by TC-RNTI for an earlier Msg3 PUSCH.

[0344] ・Before the ra-ContentionResolutionTimer is restarted, the UE assumes that the DMRS antenna port is QCL with the reception of SSB / CSI-RS for the earlier Msg3 PUSCH, and monitors the PDCCH candidates using TC-RNTI for the earlier Msg3 PUSCH.

[0345] ・After the ra-ContentionResolutionTimer is restarted, the UE assumes that the DMRS antenna port is QCL for reception of SSB / CSI-RS for a later Msg3 PUSCH, and monitors the PDCCH candidates using TC-RNTI for a later Msg3 PUSCH.

[0346] [[analyze]]

[0347] From the perspective of the base station, the base station does not recognize that the contention resolution window is shorter than the assumed length. The base station can also send a PDCCH for scheduling Msg4 for an earlier Msg3 PUSCH after a later Msg3 PUSCH.

[0348] [[analyze]]

[0349] The UE needs to keep track of how many windows are maintained / reserved. For example, the UE sends 3 Msg3 PUSCHs before the contention resolution window for the initial Msg3 PUSCH ends.

[0350] Option 2

[0351] A dedicated contention resolution window is maintained for each Msg3 PUSCH (or each PRACH repetition). A dedicated ra-ContentionResolutionTimer may also be maintained for each PRACH repetition. Multiple contention resolution windows for multiple PRACH repetitions may also follow any of the following options.

[0352] [Option 2-1]

[0353] Overlap of multiple contention resolution windows (in the time domain) is not allowed. The UE may also be specified not to assume overlap of multiple contention resolution windows for multiple Msg3 PUSCHs. The UE may also follow at least one of the following examples.

[0354] [[Example 1]] When there is an ongoing ra-ContentionResolutionTimer, the UE does not send (does not assume the sending of) a later Msg3 PUSCH.

[0355] [[Example 2]] The UE does not send (does not intend to send) a later Msg3 PUSCH before detecting the PDCCH for scheduling the PDSCH, and the PDSCH contains the UE contention resolution ID for the earlier Msg3 PUSCH.

[0356] [[analyze]]

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

[0358] [Option 2-2]

[0359] Overlap (in the time domain) of multiple contention resolution windows is allowed. The UE may also start other ra-ContentionResolutionTimers while there are any ra-ContentionResolutionTimers in operation.

[0360] In multiple Type 1-PDCCH monitoring opportunities within multiple contention resolution windows, the UE may also monitor PDCCH candidates using TC-RNTI by assuming that the reception of the reference signal shown in any of the following options becomes a DMRS antenna port of QCL.

[0361] [[Option 2-2A]] Reception of SSB / CSI-RS corresponding to Msg3PUSCH corresponding to the first / last contention resolution window among multiple contention resolution windows.

[0362] [[Option 2-2B]] Reception of SSB / CSI-RS with maximum RSRP among multiple receptions of SSB / CSI-RS corresponding to multiple Msg3 PUSCHs corresponding to multiple contention resolution windows, or reception of randomly selected SSB / CSI-RS, or reception of SSB / CSI-RS selected according to a method based on actual installation of UE.

[0363] According to this embodiment, the UE can appropriately maintain more than one contention resolution window.

[0364] <Implementation method #5>

[0365] This embodiment relates to problem 4. The overlap of the contention resolution window and the RAR window (in the time domain) can also follow any of the following options.

[0366] Option 1

[0367] Overlapping of the contention resolution window and the RAR window is not allowed. The UE may also be configured not to assume overlapping of the contention resolution window and the RAR window. The UE may also follow at least one of the following examples.

[0368] [[Example]] The UE does not send (does not assume to send) a later PRACH repetition while the (arbitrary) ra-ContentionResolutionTimer is operating.

[0369] [Example] After the UE detects the PDCCH for scheduling the PDSCH with the UE contention resolution ID, or after the UE transmits the PUCCH of the HARQ-ACK information reported by the PDSCH with the UE contention resolution ID, the UE stops any ra-ResponseWindow.

[0370] [Example] The UE does not start the ra-ResponseWindow for a later PRACH until the ra-ContentionResolutionTimer expires or the PDCCH for scheduling the PDSCH with the UE contention resolution ID is detected.

[0371] Option 2

[0372] The contention resolution window and the RAR window can overlap. Fig.10 In the example, the UE sends multiple repetitions of PRACH (Msg1#1 to #4), and starts the RAR window after each repetition. The contention resolution window for Msg1#1 overlaps with the RAR window for Msg1#3. In this example, although Msg3#1 for Msg1#1 overlaps with Msg1#3, Msg3#1 for Msg1#1 does not need to overlap with Msg1#3.

[0373] The UE may also follow at least one of the following scenarios.

[0374] [Scenario 1]

[0375] For Type 1-CSS PDCCH monitoring opportunities within the contention resolution window / RAR window for multiple PRACH repetitions using the same beam, the UE may also follow at least one of the following options.

[0376] [[Option 2-1A]] The UE assumes that the reception of SSB / CSI-RS corresponding to multiple PRACH repetitions becomes a DMRS antenna port of QCL, and monitors PDCCH candidates using both RA-RNTI and TC-RNTI.

[0377] [[Option 2-1B]] The UE assumes that the reception of SSB / CSI-RS corresponding to multiple PRACH repetitions becomes a DMRS antenna port of QCL, and monitors the PDCCH candidates using RA-RNTI.

[0378] [[Option 2-1C]] The UE assumes that the reception of SSB / CSI-RS corresponding to multiple PRACH repetitions becomes a DMRS antenna port of QCL, and thus monitors PDCCH candidates using TC-RNTI.

[0379] [Scenario 2]

[0380] For Type 1-CSS PDCCH monitoring opportunities within the contention resolution window / RAR window for multiple PRACH repetitions using different multiple beams, the UE may also follow at least one of the following options.

[0381] [[Option 2-2A]]

[0382] Prioritize monitoring of the PDCCH used to schedule Msg4 with the UE contention resolution ID. The UE assumes that the reception of the SSB / CSI-RS corresponding to the RAR window becomes the DMRS antenna port of the QCL and monitors the PDCCH candidates using the TC-RNTI. If multiple Type 1 PDCCH monitoring opportunities are in multiple contention resolution windows, option 2-2 of implementation #4 can also be used.

[0383] [[Option 2-2B]]

[0384] Prioritize monitoring RAR. The UE may also assume that the reception of the SSB / CSI-RS corresponding to the RAR window becomes the DMRS antenna port of the QCL and monitor the PDCCH candidate using the RA-RNTI. If multiple type 1 PDCCH monitoring opportunities are in multiple RAR windows, option 2-2 of implementation #2 may also be used.

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

[0386] <Implementation Method #6>

[0387] This embodiment relates to problem 5. When a UE receives multiple PDSCHs including UE contention resolution IDs, the UE may follow any of the following options.

[0388] Option 1

[0389] The UE reports only one HARQ-ACK information bit for the multiple PDSCHs in the earliest PUCCH time slot among the multiple PUCCH time slots for the multiple PDSCHs. When the UE sends AHRQ-ACK information for any PDSCH containing the UE contention resolution ID, it may not report HARQ-CK information for other PDSCHs containing the UE contention resolution ID.

[0390] exist Fig.11A In the example, the UE transmits multiple iterations of PRACH (Msg1#1, #2). When the UE transmits HARQ-ACK information for Msg4#1 based on Msg#1 on the PUCCH, it does not transmit HARQ-ACK information for Msg4#2 based on Msg1#2.

[0391] Option 2

[0392] The UE reports the HARQ-ACK information for each PDSCH in the corresponding PUCCH time slot.

[0393] exist Fig. 11B In the example, the UE sends multiple repetitions of PRACH (Msg1#1, #2). The UE sends HARQ-AACK information for Msg4#1 based on Msg#1 on the PUCCH, and sends HARQ-AACK information for Msg4#2 based on Msg1#2 on the PUCCH. In this example, the PUCCH (time slot) for the HARQ-ACK information of Msg4#2 is different from the PUCCH (time slot) for the HARQ-CK information of Msg4#1, but is the same as the PUCCH (time slot) for the HARQ-ACK information of Msg4#1.

[0394] The UE may also follow any of the following options.

[0395] [Option 2-1]

[0396] The UE does not assume that more than one PDSCH (multiple PDSCHs) contain a UE contention resolution ID mapped (corresponding) to the same PUCCH slot.

[0397] [Option 2-2]

[0398] In case there are more than one PDSCH (multiple PDSCHs) containing UE contention resolution ID mapped (corresponding) to the same PUCCH slot, the UE may also follow any of the following options.

[0399] [[Option 2-2A]]

[0400] The UE reports only 1 bit of HARQ-ACK information for the multiple PDSCHs. The 1 bit can be the ACK / NACK for the first / last PDCCH / PDSCH (or a randomly selected PDCCH / PDSCH, or a PDCCH / PDSCH selected according to a method based on the actual installation of the UE) among the multiple PDCCH / PDSCHs corresponding to the PUCCH time slot, or can be obtained based on the multiple ACK / NACK bits for the multiple PDSCHs using a logical AND or logical OR operation.

[0401] [[Option 2-2B]]

[0402] The UE may also report up to X HARQ-ACK information bits for multiple PDSCHs. In existing specifications, the UE capability may also be enhanced because it is able to send up to one HARQ-ACK information bit within one PUCCH before the dedicated PUCCH resources are set up. Since only PUCCH format (PF) 0 / 1 is specified for the PUCCH resources before the dedicated PUCCH resources are set up, X=2 may also be taken for X (maximum number). In this case, X>2 may also be taken for X (maximum number). The default PUCCH resources before the dedicated PUCCH resources are set up may also be enhanced. In the default PUCCH resource table, PUCCH resources with PF2 / 3 / 4 may also be added.

[0403] The maximum number X may be defined in the specification, may be set / indicated via SIB / RRC IE, or may be reported by the UE as a UE capability. For UE capability reporting, the specification may also define the value that the maximum number may take.

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

[0405] <Supplement>

[0406] [change]

[0407] In each embodiment, different options may be used for different situations. For example, different situations may include a situation where multiple PRACHs repeatedly use the same beam and a situation where multiple PRACHs repeatedly use different beams.

[0408] Implementation #2-2 can be used in situations where multiple contention resolution windows overlap by replacing the "RAR window" with the "contention resolution window", replacing the "RA-RNTI" with the "TC-RNTI", and replacing the "RAR" with the "DCI scheduling PDSCH with UE contention resolution ID".

[0409] Implementation #2-2 can be used in situations where the contention resolution window and the RAR window overlap by replacing "RAR window" with "RAR window / contention resolution window", replacing "RA-RNTI" with "RA-RNTR / TC-RNTI", and replacing "RAR" with "RAR, and at least one of the DCIs that schedules PDSCH with UE contention resolution ID".

[0410] [Notification of information to UE]

[0411] In the above-mentioned embodiment, the notification of arbitrary information (network (NW)) (for example, notification from a base station (Base Station (BS))) to a UE (in other words, reception of arbitrary information from a BS in a UE) may also be carried out using physical layer signaling (for example, DCI), higher layer signaling (for example, RRC signaling, MAC CE), specific signals / channels (for example, PDCCH, PDSCH, reference signals), or a combination thereof.

[0412] When the above notification is performed by MAC CE, the MAC CE may be identified by including a new logical channel ID (Logical Channel ID (LCID)) not defined in the existing standard in the MAC subheader.

[0413] When the above notification is performed through DCI, the above notification can also be performed through a specific field of the DCI, a radio network temporary identifier (Radio Network Temporary Identifier (RNTI)) used in scrambling a redundant version check (Cyclic Redundancy Check (CRC)) bit assigned to the DCI, the format of the DCI, etc.

[0414] In addition, notification of any information in the above-mentioned embodiments to the UE may be performed periodically, semi-continuously, or aperiodically.

[0415] [Notification of information from UE]

[0416] In the above-mentioned embodiments, the notification of any information from the UE (to the NW) (in other words, the sending / reporting of any information in the UE to the BS) can also be carried out using physical layer signaling (e.g., UCI), high-layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0417] When the above notification is performed through MAC CE, the MAC CE can also be identified by including a new LCID that is not specified in the existing standard in the MAC subheader.

[0418] When the notification is performed through UCI, the notification may be sent using PUCCH or PUSCH.

[0419] In addition, in the above-mentioned embodiments, notification of arbitrary information from the UE may be performed periodically, semi-continuously, or aperiodically.

[0420] [About application of each embodiment]

[0421] At least one of the above-mentioned implementation modes may also be applied when a specific condition is met. The specific condition may be specified in the standard, or may be notified to the UE / BS by using high-layer signaling / physical layer signaling.

[0422] At least one of the above-mentioned embodiments may also be applied only to a UE that reports a specific UE capability or supports the specific UE capability.

[0423] The specific UE capability may also represent at least one of the following:

[0424] ・Support multiple RARs for multiple PRACH repetitions with the same beam / different multiple beams;

[0425] ・Supports public / dedicated ra-ResponseWindow for multiple PRACH repetitions;

[0426] ・Support sending of multiple Msg3 PUSCH for multiple RARs;

[0427] ・Support common / dedicated ra-contentionResolutionTimer for multiple Msg3 PUSCH (or multiple PRACH repetitions);

[0428] ・Support overlapping of RAR windows and contention resolution windows;

[0429] ・Support the handling of more than one DCI format in one slot with CRC scrambled by RA-RNTI.

[0430] ・The maximum number of DCI formats with CRC scrambled by RA-RNTI that the UE can process in one slot;

[0431] ・Support reporting of one HARQ-ACK PUCCH for multiple Msg4 receptions;

[0432] ・Support reporting of HARQ-ACK PUCCH received for each Msg4;

[0433] ・Support reporting of one / 2 HARQ-ACK information bits within a PUCCH before dedicated PUCCH resource configuration;

[0434] ・Support monitoring of more than one DCI format with CRC scrambled by RA-RNTI / TC-RNTI using different QCL assumptions within one slot;

[0435] ・The maximum number of DCI formats with CRC scrambled by RA-RNTI / TC-RNTI that the UE can monitor in one slot using different QCL assumptions.

[0436] In addition, the above-mentioned specific UE capabilities can be capabilities that are applied across the entire frequency (commonly regardless of the frequency), or capabilities for each frequency (for example, one or a combination of cells, bands, band combinations, BWPs, component carriers, etc.), or capabilities for each frequency range (for example, frequency range (Frequency Range) 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or capabilities for each subcarrier spacing (SubCarrier Spacing (SCS)), or capabilities for each feature set (Feature Set (FS)) or each CC feature set (Feature Set Per Component-carrier (FSPS)).

[0437] Furthermore, the specific UE capability may be a capability applied in all duplex modes (commonly regardless of the duplex mode) or a capability for each duplex mode (eg, time division duplex (TDD) or frequency division duplex (FDD)).

[0438] In addition, at least one of the above-mentioned embodiments may also be applied when specific information associated with the above-mentioned embodiments is set / activated / triggered by the UE through high-layer signaling / physical layer signaling (or the operation of the above-mentioned embodiments is implemented). For example, the specific information may also be information indicating activation of the functions of each embodiment, any RRC parameter for a specific version (for example, Rel. 18 / 19), etc.

[0439] When the UE does not support at least one of the above-mentioned specific UE capabilities or is not configured with the above-mentioned specific information, the UE may also apply the operations of Rel.15 / 16, for example.

[0440] (Note A)

[0441] The following inventions are added to one embodiment of the present disclosure.

[0442] [Note 1]

[0443] A terminal having:

[0444] a control unit 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; and

[0445] The receiving unit receives the RAR in the one or more RAR windows.

[0446] [Note 2]

[0447] A terminal as described in Appendix 1, wherein:

[0448] The control unit operates one RAR window for the plurality of repetitions.

[0449] [Note 3]

[0450] A terminal as described in Supplement 1 or Supplement 2, wherein:

[0451] The control unit operates the plurality of RAR windows respectively for the plurality of repetitions.

[0452] [Note 4]

[0453] A terminal as described in any one of Notes 1 to 3, wherein:

[0454] The receiving unit monitors a specific number or less of downlink control information formats in one time slot.

[0455] (Note B)

[0456] The following inventions are added to one embodiment of the present disclosure.

[0457] [Note 1]

[0458] A terminal having:

[0459] a transmitting unit, receiving a plurality of repeated random access responses (RARs) for a physical random access channel (PRACH), respectively; and

[0460] The control unit controls the transmission of a plurality of physical uplink shared channels (PUSCHs) respectively scheduled by the plurality of RARs.

[0461] [Note 2]

[0462] A terminal as described in Appendix 1, wherein:

[0463] The multiple PUSCHs do not overlap in the time domain, or the gap between the multiple PUSCHs is longer than the time required for beam switching.

[0464] [Note 3]

[0465] A terminal as described in Supplement 1 or Supplement 2, wherein:

[0466] The multiple PUSCHs do not overlap in the time domain, or the gap between the multiple PUSCHs is shorter than the time required for beam switching.

[0467] [Note 4]

[0468] A terminal as described in any one of Notes 1 to 3, wherein:

[0469] The control unit controls transmission of a specific PUSCH among the plurality of PUSCHs.

[0470] (Note C)

[0471] The following inventions are added to one embodiment of the present disclosure.

[0472] [Note 1]

[0473] A terminal having:

[0474] A control unit that controls more than one contention resolution window for a plurality of iterations of a physical random access channel (PRACH); and

[0475] The receiving unit receives one or more downlink control information formats in the one or more contention resolution windows.

[0476] [Note 2]

[0477] A terminal as described in Appendix 1, wherein:

[0478] The plurality of contention resolution windows respectively corresponding to the plurality of iterations are not allowed to overlap in the time domain.

[0479] [Note 3]

[0480] A terminal as described in Supplement 1 or Supplement 2, wherein:

[0481] The one or more contention resolution windows and random access response (RAR) windows are allowed to overlap in the time domain.

[0482] [Note 4]

[0483] A terminal as described in any one of Notes 1 to 3, wherein:

[0484] The control unit controls reception of a plurality of physical downlink shared channels corresponding to the plurality of iterations, respectively, and reporting of one or more hybrid automatic repeat request acknowledgement (HARQ-ACK) information for the plurality of physical downlink shared channels.

[0485] (Wireless Communication System)

[0486] Hereinafter, a configuration of a wireless communication system according to an embodiment of the present disclosure will be described. In the wireless communication system, communication is performed using any one of the wireless communication methods according to the above-mentioned embodiments of the present disclosure or a combination thereof.

[0487] Fig.12 1 is a diagram showing an example of a schematic structure of a wireless communication system according to an embodiment. The wireless communication system 1 (may also be simply referred to as the system 1) may also be a system that implements communication using Long Term Evolution (LTE) standardized by the Third Generation Partnership Project (3GPP), the fifth generation mobile communication system New Radio (5GNR), or the like.

[0488] In addition, the wireless communication system 1 may also support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between multiple radio access technologies (Radio Access Technology (RAT)). MR-DC may also include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (E-UTRA-NR Dual Connectivity (EN-DC))), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NR-E-UTRA Dual Connectivity (NE-DC))), etc.

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

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

[0491] The wireless communication system 1 may also include a base station 11 that forms a macro cell C1 with a relatively wide coverage, and a base station 12 (12a-12c) that is configured in the macro cell C1 and forms a small cell C2 that is narrower than the macro cell C1. The user terminal 20 may also be located in at least one cell. The configuration and number of each cell and user terminal 20 are not limited to the method shown in the figure. Hereinafter, when the base stations 11 and 12 are not distinguished, they are collectively referred to as base stations 10.

[0492] 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).

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

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

[0495] Multiple base stations 10 may also be connected by wire (e.g., optical fiber based on Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, when NR communication between base stations 11 and 12 is used as a backhaul, the base station 11 equivalent to the upper station may also be referred to as an Integrated Access Backhaul (IAB) donor, and the base station 12 equivalent to a relay station (relay) may also be referred to as an IAB node.

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

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

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

[0499] In the wireless communication system 1, a wireless access method based on orthogonal frequency division multiplexing (OFDM) may be used. For example, in at least one of the downlink (DL) and the uplink (UL), cyclic prefix OFDM (CP-OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc. may be used.

[0500] The radio access scheme may also be referred to as a waveform. In addition, in the wireless communication system 1, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the radio access schemes for UL and DL.

[0501] As downlink channels, the wireless communication system 1 may use a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20 , a broadcast channel (Physical Broadcast Channel (PBCH))), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc.

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

[0503] User data, high-layer control information, System Information Block (SIB), etc. are transmitted through PDSCH. User data, high-layer control information, etc. can also be transmitted through PUSCH. In addition, Master Information Block (MIB) can also be transmitted through PBCH.

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

[0505] In addition, the DCI for scheduling the PDSCH may also be referred to as DL allocation, DL DCI, etc., and the DCI for scheduling the PUSCH may also be referred to as UL grant, UL DCI, etc. In addition, the PDSCH may also be rewritten as DL data, and the PUSCH may also be rewritten as UL data.

[0506] In the detection of PDCCH, the control resource set (CORESET) and the search space can also be used. CORESET corresponds to the resources for searching DCI. The search space corresponds to the search area and search method of PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor the CORESET associated with a search space based on the search space setting.

[0507] A search space may also correspond to a PDCCH candidate corresponding to one or more aggregation levels. One or more search spaces may also be referred to as a search space set. In addition, the "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting" and the like in the present disclosure may also be rewritten mutually.

[0508] Uplink control information (uplink control information (UCI)) including at least one of channel state information (CSI), delivery confirmation information (e.g., also known as hybrid automatic repeat request confirmation (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR) can also be transmitted through PUCCH. The random access preamble used to establish a connection with a cell can also be transmitted through PRACH.

[0509] In the present disclosure, downlink, uplink, etc. may be expressed without “link.” In addition, various channels may be expressed without “Physical” at the beginning.

[0510] In the wireless communication system 1, a synchronization signal (Synchronization Signal (SS)), a downlink reference signal (Downlink Reference Signal (DL-RS)), etc. can also be transmitted. As DL-RS, in the wireless communication system 1, a cell-specific reference signal (Cell-specific Reference Signal (CRS)), a channel state information reference signal (Channel State Information Reference Signal (CSI-RS)), a demodulation reference signal (DeModulation Reference Signal (DMRS)), a positioning reference signal (Positioning Reference Signal (PRS)), a phase tracking reference signal (Phase Tracking Reference Signal (PTRS)), etc. can also be transmitted.

[0511] 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 also be referred to as SS / PBCH block, SS block (SS Block (SSB)), etc. In addition, SS, SSB, etc. may also be referred to as reference signals.

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

[0513] (Base Station)

[0514] Fig.131 is a diagram showing an example of a structure of a base station involved in one embodiment. The base station 10 includes a control unit 110, a transmitting and receiving unit 120, a transmitting and receiving antenna 130, and a transmission path interface (transmission line interface) 140. In addition, the control unit 110, the transmitting and receiving unit 120, the transmitting and receiving antenna 130, and the transmission path interface 140 may each be provided with more than one.

[0515] In addition, in this example, the functional blocks of the characteristic parts in this embodiment are mainly shown, and it is also conceivable that the base station 10 also has other functional blocks required for wireless communication. Part of the processing of each unit described below may also be omitted.

[0516] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, a control circuit, and the like that are described based on common knowledge in the technical field to which the present disclosure relates.

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

[0518] The transmitting and receiving unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measuring unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting and receiving unit 120 may be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter (phase shifter), a measuring circuit, a transmitting and receiving circuit, etc., which are described based on the common knowledge in the technical field involved in the present disclosure.

[0519] The transmitting and receiving unit 120 may be configured as an integrated transmitting and receiving unit, or may be configured as a transmitting unit and a receiving unit. The transmitting unit may also be configured as a transmitting processing unit 1211 and an RF unit 122. The receiving unit may also be configured as a receiving processing unit 1212, an RF unit 122, and a measuring unit 123.

[0520] The transmitting / receiving antenna 130 can be constituted by an antenna described based on common knowledge in the technical field involved in the present disclosure, such as an array antenna.

[0521] The transmitting and receiving unit 120 may also transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 120 may also receive the above-mentioned uplink channel, uplink reference signal, etc.

[0522] The transmitting and receiving unit 120 may also use digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), etc. to form at least one of a transmitting beam and a receiving beam.

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

[0524] The transmitting and receiving unit 120 (transmitting processing unit 1211) may also perform channel coding (which may also include error correction coding), modulation, mapping, filter processing (filtering processing), discrete Fourier transform (DFT) processing (as needed), inverse fast Fourier transform (IFFT) processing), precoding, digital-to-analog conversion and other transmission processing on the bit string to be transmitted, and output a baseband signal.

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

[0526] On the other hand, the transmission and reception unit 120 (RF unit 122 ) may also perform amplification, filter processing, demodulation into a baseband signal, etc. on the signal in the radio frequency band received by the transmission and reception antenna 130 .

[0527] The transmitting and receiving unit 120 (receiving processing unit 1212) may also apply receiving processing such as analog-to-digital conversion, fast Fourier transform (FFT) processing, inverse discrete Fourier transform (IDFT) processing (as needed), filter processing (filtering processing), demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to obtain user data, etc.

[0528] The transmitting and receiving unit 120 (the measuring unit 123) may also implement measurements related to the received signal. For example, the measuring unit 123 may also perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc. based on the received signal. The measuring unit 123 may also measure received power (e.g., reference signal received power (RSRP)), received quality (e.g., reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), signal to noise ratio (SNR)), signal strength (e.g., received signal strength indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may also be output to the control unit 110.

[0529] The transmission path interface 140 can also send and receive signals (return signaling) between devices included in the core network 30 (for example, a network node providing NF), other base stations 10, etc., and can also obtain and transmit user data (user plane data) and control plane data for the user terminal 20.

[0530] In addition, the transmission unit and the reception unit of the base station 10 in the present disclosure may also be constituted by at least one of the transmission and reception unit 120 , the transmission and reception antenna 130 , and the transmission path interface 140 .

[0531] The control unit 110 may also control multiple repetitions of receiving a physical random access channel (PRACH) and one or more random access response (RAR) windows based on at least one of the multiple repetitions. The transmitting and receiving unit 120 may also transmit RARs in the one or more RAR windows.

[0532] The transmitting and receiving unit 120 may also transmit a plurality of repeated random access responses (RARs) for a physical random access channel (PRACH), respectively. The control unit 110 may also control reception of a plurality of physical uplink shared channels (PUSCHs) respectively scheduled by the plurality of RARs.

[0533] The control unit 110 may also control one or more contention resolution windows for multiple iterations of the physical random access channel (PRACH). The transmitting and receiving unit 120 may also transmit one or more downlink control information formats in the one or more contention resolution windows.

[0534] (User terminal)

[0535] Fig.14 2 is a diagram showing an example of a configuration of a user terminal according to an embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. In addition, the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may each be provided with one or more.

[0536] In addition, in this example, the functional blocks of the characteristic parts in this embodiment are mainly shown, and it is also conceivable that the user terminal 20 also has other functional blocks required for wireless communication. Part of the processing of each unit described below may be omitted.

[0537] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, a control circuit, and the like that are described based on common knowledge in the technical field to which the present disclosure relates.

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

[0539] The transmitting and receiving unit 220 may also include a baseband unit 221, an RF unit 222, and a measuring unit 223. The baseband unit 221 may also include a transmitting processing unit 2211 and a receiving processing unit 2212. The transmitting and receiving unit 220 may be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measuring circuit, a transmitting and receiving circuit, etc., which are described based on the common knowledge in the technical field involved in the present disclosure.

[0540] The transmitting and receiving unit 220 may be configured as an integrated transmitting and receiving unit, or may be configured as a transmitting unit and a receiving unit. The transmitting unit may also be configured as a transmitting processing unit 2211 and an RF unit 222. The receiving unit may also be configured as a receiving processing unit 2212, an RF unit 222, and a measuring unit 223.

[0541] The transmitting / receiving antenna 230 can be constituted by an antenna described based on common knowledge in the technical field involved in the present disclosure, such as an array antenna.

[0542] The transmitting and receiving unit 220 may also receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 220 may also transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0543] The transmitting and receiving unit 220 may also use digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), etc. to form at least one of a transmitting beam and a receiving beam.

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

[0545] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may also include error correction coding), modulation, mapping, filter processing (filtering processing), DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be sent, and output a baseband signal.

[0546] In addition, whether to apply DFT processing may also be based on the setting of transform precoding. For a certain channel (e.g., PUSCH), when transform precoding is valid (enabled), the transmitting and receiving unit 220 (transmitting processing unit 2211) may also perform DFT processing as the above-mentioned transmission processing in order to transmit the channel using a DFT-s-OFDM waveform. Otherwise, the transmitting and receiving unit 220 (transmitting processing unit 2211) may also perform DFT processing as the above-mentioned transmission processing without performing DFT processing.

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

[0548] On the other hand, the transmission and reception unit 220 (RF unit 222 ) may perform amplification, filter processing (filter processing), demodulation into a baseband signal, etc. on the signal in the radio frequency band received by the transmission and reception antenna 230 .

[0549] The sending and receiving unit 220 (receiving processing unit 2212) can also apply receiving processing such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing (filtering processing), demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing and PDCP layer processing to the obtained baseband signal to obtain user data, etc.

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

[0551] In addition, the transmitting unit and the receiving unit of the user terminal 20 in the present disclosure may also be composed of at least one of the transmitting and receiving unit 220 and the transmitting and receiving antenna 230 .

[0552] The control unit 210 may also control the transmission of multiple repetitions of the physical random access channel (PRACH) and one or more random access response (RAR) windows based on at least one of the multiple repetitions. The transmitting and receiving unit 220 may also receive RAR in the one or more RAR windows (embodiment #1 / #2).

[0553] The control unit 210 may also operate one RAR window for the multiple repetitions.

[0554] The control unit 210 may also operate multiple RAR windows respectively for the multiple repetitions.

[0555] The receiving unit 220 may also monitor a specific number or less of downlink control information formats in one time slot.

[0556] The transmitting and receiving unit 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 the transmission of multiple physical uplink shared channels (PUSCHs) scheduled by the multiple RARs (embodiment #3).

[0557] The multiple PUSCHs may not overlap in the time domain, or the gap between the multiple PUSCHs may be longer than the time required for beam switching.

[0558] The multiple PUSCHs may not overlap in the time domain, or the gap between the multiple PUSCHs may be shorter than the time required for beam switching.

[0559] The control unit 210 may also control the transmission of a specific PUSCH among the multiple PUSCHs.

[0560] The control unit 210 may control one or more contention resolution windows for multiple iterations of the physical random access channel (PRACH). The transmitting and receiving unit 220 may receive one or more downlink control information formats in the one or more contention resolution windows (embodiments #4 / #5 / #6).

[0561] The multiple contention resolution windows respectively corresponding to the multiple iterations may not be allowed to overlap in the time domain.

[0562] The one or more contention resolution windows and random access response (RAR) windows may also be allowed to overlap in the time domain.

[0563] The control unit 210 may also control reception of a plurality of physical downlink shared channels corresponding to the plurality of iterations, respectively, and reporting of one or more hybrid automatic repeat request acknowledgement (HARQ-ACK) information for the plurality of physical downlink shared channels.

[0564] (Hardware structure)

[0565] In addition, the block diagram used in the description of the above-mentioned embodiment shows a block of a functional unit. These functional blocks (structural units) are implemented by any combination of at least one of hardware and software. In addition, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented by a device that is physically or logically combined, or two or more physically or logically separated devices can be directly or indirectly connected (for example, by wire, wireless, etc.) and implemented by these multiple devices. The functional block can also be implemented by combining the above-mentioned one device or the above-mentioned multiple devices with software.

[0566] Here, the functions include judging, deciding, determining, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, solving, selecting, selecting, establishing, comparing, assuming, expecting, regarding, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but are not limited to these. For example, a functional block (structural unit) that implements a sending function may also be referred to as a transmitting unit, a transmitter, etc. Any one of them is as described above, and the implementation method thereof is not particularly limited.

[0567] For example, a base station, a user terminal, etc. in one embodiment of the present disclosure may also function as a computer that performs processing of the wireless communication method of the present disclosure. Fig.15 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0568] In addition, in the present disclosure, the terms such as device, circuit, equipment, section, and unit can be interchanged. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or may exclude some of the devices.

[0569] For example, only one processor 1001 is shown, but there may be multiple processors. In addition, the processing may be performed by one processor, or may be performed by two or more processors simultaneously, sequentially, or in other ways. In addition, the processor 1001 may also be implemented by one or more chips.

[0570] The functions of the base station 10 and the user terminal 20 are realized, for example, by reading specific software (program) into hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations and controls communication via the communication device 1004, or controls at least one of the reading and writing of data in the memory 1002 and the storage 1003.

[0571] The processor 1001 controls the entire computer by, for example, operating an operating system. The processor 1001 may also be composed of a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, a register, etc. For example, at least a part of the control unit 110 (210), the transmission and reception unit 120 (220), etc. described above may also be implemented by the processor 1001.

[0572] In addition, the processor 1001 reads a program (program code), a software module, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and performs various processes based on them. As a program, a program that causes a computer to perform at least a part of the operations described in the above-mentioned embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operated in the processor 1001, and the other functional blocks can also be implemented in the same way.

[0573] The memory 1002 may also be a computer-readable recording medium, for example, composed of at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), or other appropriate storage media. The memory 1002 may also be referred to as a register, a cache, a main memory (main storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for implementing the wireless communication method involved in one embodiment of the present disclosure.

[0574] The storage 1003 may also be a computer-readable recording medium, such as a flexible disk, a floppy disk, an optical disk (such as a compact disk (Compact Disc ROM (CD-ROM)), a digital versatile disk, a Blu-ray (Blu-ray) (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (such as a card, a stick, a key drive), a magnetic stripe, a database, a server, or at least one of other appropriate storage media. The storage 1003 may also be referred to as an auxiliary storage device.

[0575] The communication device 1004 is hardware (transmitting and receiving 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, a network controller, a network card, a communication module, etc. In order to realize at least one of frequency division duplex (Frequency Division Duplex (FDD)) and time division duplex (Time Division Duplex (TDD)), the communication device 1004 may also be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the above-mentioned transmitting and receiving unit 120 (220), the transmitting and receiving antenna 130 (230), etc. may also be realized by the communication device 1004. The transmitting and receiving unit 120 (220) may also be realized by physically or logically separating the transmitting unit 120a (220a) and the receiving unit 120b (220b).

[0576] The input device 1005 is an input device that receives input from the outside (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.). The output device 1006 is an output device that performs output to the outside (e.g., a display, a speaker, a light emitting diode (LED) lamp, etc.). In addition, the input device 1005 and the output device 1006 may also be an integrated structure (e.g., a touch panel).

[0577] In addition, the processor 1001, the memory 1002 and other devices are connected via a bus 1007 for communicating information. The bus 1007 may be configured as a single bus or may be configured as different buses between the devices.

[0578] In addition, the base station 10 and the user terminal 20 may also be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA), and the hardware may be used to implement a part or all of each functional block. For example, the processor 1001 may also be implemented using at least one of these hardware.

[0579] (Variation)

[0580] In addition, the terms described in the present disclosure and the terms required for understanding the present disclosure may also be replaced with terms having the same or similar meanings. For example, channels, code elements, and signals (signals or signaling) may be rewritten one another. In addition, a signal may also be a message. A reference signal may also be referred to as RS, and may also be referred to as a pilot, a pilot signal, etc. depending on the applied standard. In addition, a component carrier (CC) may also be referred to as a cell, a frequency carrier, a carrier frequency, etc.

[0581] A radio frame may also be composed of one or more periods (frames) in the time domain. Each period (frame) of the one or more periods (frames) constituting a radio frame may also be referred to as a subframe. Further, a subframe may also be composed of one or more time slots in the time domain. A subframe may also be a fixed time length (e.g., 1 ms) that is not dependent on a parameter set (numerology).

[0582] Here, the parameter set may also be a communication parameter applied in at least one of the transmission and reception of a certain signal or channel. For example, the parameter set may also represent at least one of the subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), the number of symbols per TTI, wireless frame structure, specific filter processing performed by the transmitter and receiver in the frequency domain, specific windowing processing performed by the transmitter and receiver in the time domain, etc.

[0583] A time slot may also 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. In addition, a time slot may also be a time unit based on a parameter set.

[0584] A time slot may also contain multiple mini-slots. Each mini-slot may also be composed of one or more symbols in the time domain. In addition, a mini-slot may also be referred to as a sub-slot. A mini-slot may also be composed of a smaller number of symbols than a time slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may also be referred to as a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may also be referred to as a PDSCH (PUSCH) mapping type B.

[0585] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols may also be referred to by their respective names. In addition, time units such as frames, subframes, time slots, mini-time slots, and symbols in the present disclosure may also be replaced with each other.

[0586] For example, a subframe may be referred to as a TTI, a plurality of consecutive subframes may be referred to as a TTI, and a time slot or a mini time slot may be referred to as a TTI. That is, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. In addition, the unit representing a TTI may be referred to as a time slot, a mini time slot, etc. instead of a subframe.

[0587] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, the base station schedules each user terminal to allocate wireless resources (frequency bandwidth, transmission power, etc. that can be used in each user terminal) in TTI units. In addition, the definition of TTI is not limited to this.

[0588] TTI can also be a transmission time unit for a data packet (transport block), code block, code word, etc. that has been channel-coded, and can also be a processing unit for scheduling, link adaptation, etc. In addition, when TTI is given, the time interval (for example, the number of symbols) to which a transport block, code block, code word, etc. is actually mapped can also be shorter than the TTI.

[0589] In addition, when a time slot or a mini time slot is called a TTI, one or more TTIs (i.e., one or more time slots or one or more mini time slots) may also be the minimum time unit of scheduling. In addition, the number of time slots (mini time slots) constituting the minimum time unit of scheduling may also be controlled.

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

[0591] In addition, a long TTI (eg, normal TTI, subframe, etc.) may be rewritten as a TTI having a time length exceeding 1 ms, and a short TTI (eg, shortened TTI, etc.) may be rewritten as a TTI having a TTI length shorter than that of a long TTI and longer than 1 ms.

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

[0593] In addition, an RB may also include one or more symbols in the time domain, and may also be the length of a slot, a mini-slot, a subframe, or a TTI. A TTI, a subframe, etc. may also be composed of one or more resource blocks, respectively.

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

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

[0596] Bandwidth Part (BWP) (also referred to as partial bandwidth, etc.) can also represent a subset of contiguous common RBs (common resource blocks) for a parameter set in a carrier. Here, common RBs can also be identified by the index of the RB based on the common reference point of the carrier. PRBs can also be defined in a BWP and numbered within the BWP.

[0597] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). For a UE, one or more BWPs may be configured in one carrier.

[0598] At least one of the set BWPs may be activated, and the UE may not assume that a specific signal / channel is transmitted or received outside the activated BWP. In addition, "cell", "carrier", etc. in the present disclosure may also be rewritten as "BWP".

[0599] In addition, the above-mentioned structures such as radio frames, subframes, time slots, mini-time slots and symbols are only examples. For example, the number of subframes included in a radio frame, the number of time slots per subframe or radio frame, the number of mini-time slots included in a time slot, the number of symbols and RBs included in a time slot or mini-time slot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length can be changed in various ways.

[0600] In addition, the information, parameters, etc. described in the present disclosure may be represented by absolute values, relative values ​​relative to a specific value, or other corresponding information. For example, wireless resources may also be indicated by a specific index.

[0601] In the present disclosure, the names used for parameters, etc. are not limiting in all respects. Furthermore, the mathematical formulas, etc. using these parameters may be different from those explicitly disclosed in the present disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, and therefore, the various names assigned to these various channels and information elements are not limiting in all respects.

[0602] Information, signals, etc. described in the present disclosure may also be represented using any of a variety of different techniques. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be mentioned throughout the above description may also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0603] In addition, information, signals, etc. can be output in at least one of the following directions: from a higher layer (upper layer) to a lower layer (lower layer), and from a lower layer to a higher layer. Information, signals, etc. can also be input and output via multiple network nodes.

[0604] The input and output information, signals, etc. may be stored in a specific location (e.g., a memory), or may be managed using a management table. The input and output information, signals, etc. may be overwritten, updated, or added. The output information, signals, etc. may also be deleted. The input information, signals, etc. may also be sent to other devices.

[0605] The notification of information is not limited to the methods / implementations described in the present disclosure, and may also be performed by other methods. For example, the notification of information in the present disclosure may also be implemented through physical layer signaling (e.g., downlink control information (Downlink Control Information (DCI)), uplink control information (Uplink Control Information (UCI))), high-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.

[0606] In addition, physical layer signaling may also be referred to as layer 1 / layer 2 (Layer 1 / Layer 2 (L1 / L2)) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. In addition, RRC signaling may also be referred to as an RRC message, such as an RRC connection establishment (RRC Connection Setup) message, an RRC connection reconstruction (RRC Connection Reconfiguration) message, etc. In addition, MAC signaling may also be notified using, for example, a MAC control element (MACControl Element (CE)).

[0607] Furthermore, notification of specific information (eg, notification of “it is X”) is not limited to explicit notification, but may be performed implicitly (eg, by not notifying the specific information or by notifying other information).

[0608] The determination may be made using a value represented by one bit (0 or 1), a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(eg, comparison with a specific value).

[0609] Whether software is called software, firmware, middle-ware, microcode, hardware description language, or other names, it should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, program, sub-program, software module, application, software application, software package, routine, sub-routine, object, executable files, execution thread, procedure, function, etc.

[0610] In addition, software, instructions, information, etc. may also be sent and received via a transmission medium. For example, when the software is sent from a website, server, or other remote source using at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and wireless technology (infrared, microwave, etc.), at least one of these wired technology and wireless technology is included in the definition of transmission medium.

[0611] The terms "system" and "network" used in the present disclosure can be used interchangeably. "Network" may also refer to a device (eg, a base station) included in the network.

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

[0613] In the present disclosure, terms such as "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", and "component carrier" can be used interchangeably. There are also cases where base stations are referred to by terms such as macro cell, small cell, micro cell, and pico cell.

[0614] A base station can accommodate one or more (for example, three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services through a base station subsystem (for example, a small base station for indoor use (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a part or the entirety of the coverage area of ​​at least one of a base station and a base station subsystem that provides communication services within the coverage area.

[0615] In the present disclosure, the base station sending information to the terminal may also be rewritten as the base station instructing the terminal to control / operate based on the information.

[0616] In the present disclosure, terms such as “mobile station (MS)”, “user terminal”, “user device (User Equipment (UE))”, and “terminal” can be used interchangeably.

[0617] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, hand set, user agent, mobile client, client or several other appropriate terms.

[0618] At least one of the base station and the mobile station may also be referred to as a transmission device, a reception device, a wireless communication device, etc. In addition, at least one of the base station and the mobile station may be a device mounted on a moving object, a moving object body, etc.

[0619] The mobile body refers to a movable object, and the moving speed is arbitrary, and of course it also includes the situation where the mobile body stops. The mobile body includes, for example, vehicles, transport vehicles, cars, automatic two-wheeled vehicles (motorcycles), bicycles, connected cars, loading shovels, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, trolleys, rickshaws, ships (ships and other watercrafts), airplanes, rockets, artificial satellites, drones, multi-rotor aircraft, quadcopters, balloons and objects carried on them, and are not limited to these. In addition, the mobile body can also be a mobile body that drives autonomously based on operating instructions.

[0620] The mobile object may be a means of transportation (e.g., a vehicle, an airplane, etc.), a mobile object that moves unmanned (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). In addition, at least one of the base station and the mobile station may include a device that does not necessarily move when performing communication operations. For example, at least one of the base station and the mobile station may also be an Internet of Things (IoT) device such as a sensor.

[0621] Fig.161 is a diagram showing an example of a vehicle according to an embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, 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 unit 59, and a communication module 60.

[0622] The driving unit 41 is composed of at least one of an engine, a motor, or a combination of an engine and a motor. The steering unit 42 is composed of at least a steering wheel (also called a handlebar), and steers 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.

[0623] The electronic control unit 49 is composed of 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 unit 49 may also be referred to as an ECU (Electronic Control Unit).

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

[0625] The information service unit 59 is composed of various devices such as a vehicle navigation system, an audio system, a speaker, a display, a television, and a radio for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information obtained from an external device via the communication module 60 and the like to provide various information / services (for example, multimedia information / multimedia services) to the occupants of the vehicle 40.

[0626] The information service unit 59 may include input devices for accepting input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.), and may also include output devices for implementing output to the outside (e.g., display, speaker, LED light, touch panel, etc.).

[0627] The driving assistance system unit 64 is composed of various devices for providing functions for preventing accidents or reducing the driving load of the driver, such as millimeter wave radar, light detection and ranging (LiDAR), camera, positioning locator (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., high-precision (High Definition (HD))) map, autonomous vehicle (Autonomous Vehicle (AV)) map, etc.), gyroscope system (e.g., inertial measurement unit (Inertial Measurement Unit (IMU)), inertial navigation unit (Inertial Navigation System (INS)), etc.), artificial intelligence (Artificial Intelligence (AI)) chip, AI processor, and one or more ECUs for controlling these devices. In addition, the driving assistance system unit 64 sends and receives various information via the communication module 60 and realizes the driving assistance function or the autonomous driving function.

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

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

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

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

[0632] In addition, the communication module 60 stores various information received from the external device in the memory 62 that can be used by the microprocessor 61. The microprocessor 61 can also control the drive unit 41, the steering unit 42, the accelerator pedal 43, the brake pedal 44, the shift lever 45, the left and right front wheels 46, the left and right rear wheels 47, the axle 48, and various sensors 50-58 of the vehicle 40 based on the information stored in the memory 62.

[0633] In addition, the base station in the present disclosure may also be rewritten as a user terminal. For example, the various methods / implementations of the present disclosure may also be applied to a structure in which the communication between a base station and a user terminal is replaced by the communication between multiple user terminals (for example, it may also be referred to as device-to-device (D2D)), vehicle-to-everything (V2X), etc.). In this case, it may also be set as a structure in which the user terminal 20 has the functions possessed by the above-mentioned base station 10. In addition, terms such as "uplink" and "downlink" may also be rewritten as terms corresponding to inter-terminal communication (for example, "sidelink"). For example, uplink channels, downlink channels, etc. may also be rewritten as sidelink channels.

[0634] Likewise, the user terminal in the present disclosure may be rewritten as a base station. In this case, the base station 10 may have the functions of the user terminal 20 described above.

[0635] In the present disclosure, the actions are assumed to be performed by the base station, and sometimes by its upper node depending on the situation. Obviously, in a network including one or more network nodes having a base station, various operations performed for communication with a terminal can be performed by the base station, one or more network nodes other than the base station (for example, Mobility Management Entity (MME)), Serving-Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0636] The various methods / implementations described in this disclosure may be used alone or in combination, and may be used in a switched manner as the method is executed. In addition, the processing procedures, timings, flow charts, etc. of the various methods / implementations described in this disclosure may be reversed in order as long as they are not contradictory. For example, for the method described in this disclosure, the elements of various steps are presented in an illustrative order, but are not limited to the specific order presented.

[0637] The various modes / implementations described in the present disclosure may be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or a decimal)), 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), systems using other appropriate wireless communication methods, and next-generation systems based on these enhancements, revisions, productions, or regulations. In addition, multiple systems may be combined (for example, LTE or LTE-A, combination with 5G, etc.) for application.

[0638] The phrase “based on” used in the present disclosure does not mean “based only on” unless otherwise specified. In other words, the phrase “based on” means both “based only on” and “based at least on”.

[0639] Any reference to an element using the terms "first", "second", etc. used in this disclosure does not fully define the amount or order of these elements. These terms can be used in this disclosure as a convenient method to distinguish between two or more elements. Therefore, reference to the first and second elements does not mean that only two elements can be used or that the first element must take precedence over the second element in some form.

[0640] The term "determining" used in this disclosure may include a variety of actions. For example, "determining" may also refer to situations where judging, calculating, computing, processing, deriving, investigating, looking up (e.g., searching in a table, database or other data structure), ascertaining, etc. are considered to be "determining".

[0641] In addition, “judgment (decision)” may also refer to situations where receiving (e.g., receiving information), transmitting (e.g., sending information), input (input), output (output), accessing (e.g., accessing data in a memory), etc. are regarded as making a “judgment (decision)”.

[0642] In addition, "judgment (decision)" can also be regarded as a situation where resolving, selecting, choosing, establishing, comparing, etc. are regarded as "judgment (decision)". That is, "judgment (decision)" can also be regarded as a situation where some actions are regarded as "judgment (decision)".

[0643] In addition, "judge (decide)" can also be rewritten as "assuming (assuming)", "expecting (expecting)", "considering (considering)" and so on.

[0644] The “maximum transmit power” described in the present disclosure may refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated maximum transmit power).

[0645] The terms "connected", "coupled", or all their variations used in this disclosure refer to all direct or indirect connections or combinations between two or more elements, and may include the situation where one or more intermediate elements exist between two elements that are "connected" or "coupled" to each other. The combination or connection between elements may be physical, logical, or a combination thereof. For example, "connection" may also be rewritten as "access".

[0646] In the present disclosure, when two elements are connected, it is possible to consider being "connected" or "combined" to each other using one or more wires, cables, printed electrical connections, etc., as well as being "connected" or "combined" to each other using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, light (both visible and invisible) region, etc. as several non-limiting and non-inclusive examples.

[0647] In the present disclosure, the term "A is different from B" may also mean "A and B are different from each other". In addition, the term may also mean "A and B are different from C, respectively". The terms "separate" and "combined" may also be interpreted in the same manner as "different".

[0648] When the terms “include,” “including,” and variations thereof are used in the present disclosure, these terms have an inclusive meaning, similar to the term “comprising.” Furthermore, the term “or” used in the present disclosure does not have an exclusive OR meaning.

[0649] In the present disclosure, when an article is added by translation like a, an, and the in English, for example, the present disclosure may also include a case where the noun following the article is in plural form.

[0650] In the present disclosure, "below", "less than", "above", "more than", "equal to", etc. can also be rephrased with each other. In addition, in the present disclosure, sentences meaning "good", "bad", "big", "small", "high", "low", "early", "late", "wide", "narrow", etc. can also be rephrased with each other, without being limited to the original degree, comparative degree, and superlative degree. In addition, in the present disclosure, sentences meaning "good", "bad", "big", "small", "high", "low", "early", "late", "wide", "narrow", etc. can also be rephrased with each other as expressions with "ith" attached, without being limited to the original degree, comparative degree, and superlative degree (for example, "highest" can also be rephrased with "i-th highest").

[0651] In the present disclosure, “of,” “for,” “regarding,” “related to,” “associated with,” etc. may also be replaced by each other.

[0652] The invention involved in the present disclosure is described in detail above, but it is obvious to those skilled in the art that the invention involved in the present disclosure is not limited to the embodiments described in the present disclosure. The invention involved in the present disclosure can be implemented as a modified and altered mode without departing from the gist and scope of the invention determined based on the description of the claims. Therefore, the description of the present disclosure is for the purpose of illustrative description and does not have any limiting meaning on the invention involved in the present disclosure.

Claims

1. A terminal having: a control unit 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; and The receiving unit receives the RAR in the one or more RAR windows.

2. The terminal according to claim 1, wherein: The control unit operates one RAR window for the plurality of repetitions.

3. The terminal according to claim 1, wherein: The control unit operates the plurality of RAR windows respectively for the plurality of repetitions.

4. The terminal according to claim 1, wherein: The receiving unit monitors a specific number or less of downlink control information formats in one time slot.

5. A wireless communication method of a terminal, comprising: The step of transmitting a plurality of repetitions of a physical random access channel (PRACH) and controlling one or more random access response (RAR) windows based on at least one of the plurality of repetitions; and In the one or more RAR windows, a step of receiving RAR.

6. A base station, comprising: a control unit that controls 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; and The sending unit sends the RAR in the one or more RAR windows.

Images