Terminal, wireless communication method, and base station

By adopting multiple PRACH transmission methods in the terminal, the problem of unclear improvement in the coverage range of the random access process in the wireless communication system is solved, and the throughput of the communication system is improved.

CN119923939APending Publication Date: 2025-05-02NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280100415.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-08-05
Publication Date
2025-05-02

AI Technical Summary

Technical Problem

In future wireless communication systems, the coverage improvement of the random access process is unclear, resulting in a decrease in communication throughput.

Method used

By implementing multiple transmission methods in the terminal, including a physical random access channel (PRACH) transmission method that does not accompany multiple repetitions, a method that uses the same beam to send multiple repetitions, a method that uses different multiple beams to send multiple repetitions, and a method that uses the same beam and different multiple beams to send multiple repetitions, in order to improve the coverage of the random access process.

Benefits of technology

Improve the coverage of random access processes, thereby improving the throughput of the communication system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119923939A_ABST
    Figure CN119923939A_ABST
Patent Text Reader

Abstract

A terminal according to one embodiment of the present disclosure includes: a control unit; a first transmission method for transmitting a physical random access channel (PRACH) that does not accompany a plurality of repetitions, a second transmission method for transmitting the plurality of repetitions using the same beam, and a third transmission method for transmitting the plurality of repetitions using a plurality of different beams are determined. One of the plurality of repeated fourth transmission methods is transmitted using the same beam and a plurality of different beams; and a transmission unit that transmits one or more PRACHs using the transmission scheme. According to one mode of the invention, the coverage range of the random access process can be improved.
Need to check novelty before this filing date? Find Prior Art

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) is standardized for the purpose of further high-speed data rate, low latency, etc. (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel. 10-14) is standardized for the purpose of further increasing the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP (registered trademark)) version (Release (Rel.) 8, 9).

[0003] Successor systems of LTE (also called, for example, fifth generation mobile communication system (5G), 5G+(plus), sixth 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), improvement of coverage is being studied.

[0009] However, the random access procedure for coverage improvement is not clear. If such a random access procedure is not clear, 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 procedure.

[0011] Means for solving problems

[0012] A terminal involved in one method of the present disclosure includes: a control unit that determines a first transmission method for sending a physical random access channel (PRACH) without multiple repetitions, a second transmission method for sending the multiple repetitions using the same beam, a third transmission method for sending the multiple repetitions using different multiple beams, and a fourth transmission method for sending the multiple repetitions using the same beam and different multiple beams; and a transmission unit that uses the transmission method to send more than one PRACH.

[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 of PRACH repetition with the same beam is shown.

[0017] Figure 3A as well as Figure 3B An example of PRACH repetition with different multiple beams is shown.

[0018] Figure 4A as well as Figure 4B An example of operations permitted in Option 4 / Option 3 is shown.

[0019] Figure 5A as well as Figure 5B An example of options 3-8 is shown.

[0020] Figure 6 A first example of the operation of operation A / C of option 4-8 is shown.

[0021] Figure 7 A second example of the operation of operation A / C of option 4-8 is shown.

[0022] Figure 8 A third example of the operation of operation A / C of option 4-8 is shown.

[0023] Fig. 9 A fourth example of the operation of operation A / C of option 4-8 is shown.

[0024] Fig.10 A first example of the operation of operation B / D of option 4-8 is shown.

[0025] Fig.11 A second example of the operation of operation B / D of option 4-8 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 according to an embodiment.

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

[0031] (TCI, spatial relationship, QCL)

[0032] In NR, the reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) and the transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, and encoding) of a control signal and at least one of a channel (expressed as signal / channel) in the UE based on the transmission configuration indication state (Transmission Configuration Indication state (TCI state)) are being studied.

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

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

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

[0036] In addition, the spatial reception parameter may also correspond to a reception beam of the UE (eg, a 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, in which the same parameters (or parameter sets) may be assumed to be different, and the parameters (also referred to as QCL parameters) are expressed as follows:

[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 relationship that the UE assumes that a certain Control Resource Set (CORESET), channel or reference signal is in a specific QCL (for example, QCL type D) with other CORESETs, channels or reference signals may also be referred to as QCL assumption.

[0043] The UE may also determine at least one of the transmit beam (Tx beam) and 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 between the channel being the object (in other words, the reference signal (RS) used for the channel) and other signals (for example, other RSs). 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 a downlink shared channel (Physical Downlink Shared Channel (PDSCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), an uplink shared channel (Physical Uplink Shared Channel (PUSCH)), and an uplink control channel (Physical Uplink Control Channel (PUCCH)).

[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) performs: reception of SS / PBCH blocks (SSBs), transmission of Msg.1 (PRACH / random access preamble / preamble), reception of Msg.2 (PDCCH, PDSCH including random access response (RAR)), transmission of Msg.3 (PUSCH scheduled by RAR UL grant), and reception of Msg.4 (PDCCH, PDSCH including UE contention resolution identity). Afterwards, if an ACK for Msg.4 is transmitted from the UE via the base station (network), the RRC connection is established (RRC_CONNECTED mode).

[0052] SSB reception includes PSS detection, SSS detection, PBCH-DMRS detection, and PBCH reception. PSS detection detects part of the physical cell ID (PCI), detects (synchronizes) OFDM symbol timing, and (roughly) synchronizes the frequency. SSS detection includes detection of the physical cell ID. PBCH-DMRS detection includes detection of (part of) the SSB index within a half radio frame (5ms). PBCH reception includes detection of the system frame number (SFN) and radio frame timing (SSB index), reception of setting information for receiving the remaining minimum system information (RMSI, SIB1), and 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 includes information for RACH configuration and RACH procedures. The relationship between the time / frequency resources of SSB and SIB1 PDCCH monitoring resources is set through PBCH.

[0056] The 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, in order to ensure coverage, if beamforming is applied to the synchronization signal / reference signal, a strong signal is transmitted in a specific direction, and it becomes more difficult to transmit signals in other directions. In the base station before the UE is connected, if the direction in which the UE is located is unknown, 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 with beams in different directions, and the UE identifies which beam has been found. If a thin (narrow) beam is used for coverage, a large number of 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 to reduce the number of beams (synchronization signals / reference signals) and suppress overhead, the coverage becomes narrower.

[0060] In future wireless communication systems (eg, 6G), it is considered that the use of frequency bands such as millimeter waves and terahertz waves will be further developed. It is considered that a plurality of thin beams are used to construct the area / coverage of a cell to provide communication services.

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

[0062] Research is underway to enhance coverage including PRACH extension for frequency range (FR) 2. For example, research is underway to use PRACH repetition using the same beam or different beams. This PRACH extension can also be applied to FR1.

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

[0064] like Figure 1 As shown, the common RACH configuration (RACH-ConfigCommon) may also include: a generic RACH configuration (rach-ConfigGeneric), a total number of RA preambles (totalNumberOfRA-Preambles), an SSB for each RACH opportunity, and a contention-based (CB) preamble for each SSB (ssb-perRACH-OccasionAndCB-PreamblesPerSSB). rach-ConfigGeneric may also include a PRACH configuration index (prach-ConfigurationIndex), message 1FDM (msg1-FDM, the number of PRACH opportunities that are FDMed in one time instance). ssb-perRACH-OccasionAndCB-PreamblesPerSSB may also include the number of CB preambles for each SSB for the number of SSBs per RACH opportunity 1 / 8 (oneEighth, one SSB is associated with 8 RACH opportunities).

[0065] 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 N of SS / PBCH blocks associated with one PRACH opportunity and the number R of CB preambles per SS / PBCH block in each activated PRACH opportunity via ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0066] For a type 1 random access procedure, or a type 2 random access procedure with a PRACH opportunity set independently of the type 1 random access procedure (2-step random access procedure, message A / B), when N < 1, one SS / PBCH block is mapped to 1 / N consecutive activated RACH opportunities, with R CB preambles with consecutive indices associated with the SS / PBCH block index per activated PRACH opportunity starting from preamble index 0. When N >= 1, R CB preambles with consecutive indices associated with the SS / PBCH block index n (0 <= n < -N-1) per activated PRACH opportunity start from preamble index n·N_preamble^total / N. Here, for the type 1 random access procedure, N_preamble^total is given by totalNumberOfRA-Preambles, and for the type 2 random access procedure with the setting of the PRACH opportunity independent of the type 1 random access procedure, N_preamble^total is given by msgA-TotalNumberOfRA-Preambles. N_preamble^total is a multiple of N.

[0067] The association period for mapping SS / PBCH blocks to PRACH opportunities starting from frame 0 is the minimum value in a set determined by the relationship (relationship specified in the specification) between the PRACH configuration period and the association period (number of PRACH configuration periods) so that N_Tx^SSB SS / PBCH block indices are mapped to PRACH opportunities at least once in the association period. Here, the UE obtains N_Tx^SSB from the value of SSB positions in burst (ssb-PositionsInBurst) in SIB1 or in the public service cell configuration (ServingCellConfigCommon). If there is a set of PRACH opportunities or PRACH preambles that are not mapped to N_Tx^SSB SS / PBCH block indices after an integer number of mapping cycles from SS / PBCH block indices to PRACH opportunities in the association period, an SS / PBCH block index is not mapped to the set of PRACH opportunities or PRACH preambles. The associated pattern period includes one or more associated periods and is determined so that the pattern between PRACH opportunities and SS / PBCH block indices repeats at most every 160 ms. If there is a PRACH opportunity that is not associated with an SS / PBCH block index after an integer number of associated periods, the PRACH opportunity is not used for PRACH.

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

[0069] In the case where ssb-perRACH-OccasionAndCB-PreamblesPerSSB for the association of PRACH opportunities (RACH opportunities (RO)) with beams (SSB / CSI-RS) represents oneHalf,n16 (N=1 / 2, R=16), and msg1-FDM is 4, 4 ROs are FDMed in one time instance, and one SSB is mapped to 2 ROs. Preamble indexes 0 to 15 are associated with 2 ROs, and preamble indexes 0 to 15 are associated with SSB0. In this way, when N<1, one SSB is mapped to multiple ROs. As a result, the capacity of the RO of each beam is improved.

[0070] In the case where 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. In this way, the same RO is associated with different SS / PBCH block indexes, and different preambles use different SS / PBCH block indexes. The base station can distinguish the associated SS / PBCH block indexes through the received PRACH.

[0071] 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 set, 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 the subframe, the number of time domain PRACH opportunities in the PRACH time slot N_t^RA,slot, and the PRACH duration N_dur^RA.

[0072] The type of RACH process triggered for different purposes varies depending on whether PRACH repetition can be applied to the scenario. The type of RACH process may also be at least one of the following.

[0073] Contention-free random access (CFRA), 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.

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

[0075] · 4-step RACH.

[0076] · 2-step RACH.

[0077] However, the settings / procedures of PRACH repetition are not clear. For example, it is not clear how the PRACH resources used for repetition (e.g., repetition mode, number of repetitions) are set, the UE operation of repetitive preamble transmission, and the impact on counters / timers related to RACH. If such settings / procedures are not clear, there is a concern that communication quality / communication throughput may deteriorate.

[0078] (RA response window)

[0079] RA response window (ra-ResponseWindow) is a time window for monitoring RA response (RAR) (special cell (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).

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

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

[0082] [Operation 1]

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

[0084] [[Operation 1-1]] The MAC entity starts the ra-ResponseWindow set in the BFR configuration (BeamFailureRecoveryConfig) in the first PDCCH timing after the end of the RA preamble transmission.

[0085] [[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) during the operation of the ra-ResponseWindow.

[0086] [Operation 2]

[0087] If this is not the case, the MAC entity performs the following operations 2-1 and 2-2.

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

[0089] [[Operation 2-2]] The MAC entity monitors the PDCCH transmission of the SpCell for the RAR identified by the RA-RNTI during the operation of the ra-ResponseWindow.

[0090] [Operation 3]

[0091] If the ra-ResponseWindow set in BeamFailureRecoveryConfig expires and a PDCCH transmission on the search space indicated by recoverySearchSpaceId for C-RNTI is received on the serving cell where the preamble is transmitted, or if the ra-ResponseWindow set in RACH-ConfigCommon expires and a RAR including RA preamble identifiers consistent with the transmitted 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.

[0092] The MAC entity may also stop the ra-ResponseWindow after successful reception of the RAR including the RA preamble identifiers that match the transmitted PREAMBLE_INDEX (and may also stop monitoring for the RAR).

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

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

[0095] [Operation 4]

[0096] In the PDCCH monitoring window specified by the specification, the MAC entity starts the Msg.B response window (msgB-ResponseWindow).

[0097] The msgB-ResponseWindow may also start at the first symbol of the earliest CORESET for which the UE is configured to receive a PDCCH for a type-1-PDCCH CSS set 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.

[0098] [Operation 5]

[0099] While the msgB-ResponseWindow is operating, the MAC entity monitors the PDCCH transmission of the SpCell for RAR identified by the MSGB-RNTI.

[0100] [Operation 6]

[0101] 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 during the operation of the msgB-ResponseWindow.

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

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

[0104] 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 for the determination of 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). RA-RNTI is calculated according to the specification. RA-RNTI is the RNTI for 4-step RACH.

[0105] The MSGB-RNTI associated with the PRACH opportunity for transmitting the RA preamble is calculated as follows.

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

[0107] 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 for the determination of 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.

[0108] (PDCCH command)

[0109] <DCI format for PDCCH command>

[0110] DCI format 1_0 includes: an identifier field of the DCI format, 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. 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).

[0111] <PRACH Timing>

[0112] In 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 indicates the PRACH timing of the PRACH transmission associated with the SS / PBCH block index indicated by the SS / PBCH Block Index field of the PDCCH command.

[0113] 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 represents the PRACH timing for PRACH transmission associated with the selected SS / PBCH block index.

[0114] The PRACH opportunities are mapped consecutively per corresponding SS / PBCH block index. The indexing of the PRACH opportunities represented by the masked index value is reset per SS / PBCH block index, per mapping cycle of consecutive PRACH opportunities. In the first available mapping cycle, the UE selects a PRACH opportunity for transmission of the PRACH represented by the PRACH masked index value for the indicated SS / PBCH block index.

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

[0116] • First, the increasing order of frequency resource indices for frequency division multiplexed PRACH opportunities.

[0117] • Second, the increasing order of time resource indices for time division multiplexed PRACH opportunities within a PRACH slot.

[0118] • Third, the ascending order of the index of the PRACH slots.

[0119] For PRACH transmission triggered in response to 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 indexing of the PRACH opportunities represented by ra-OccasionList is reset during each association mode.

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

[0121] <Random access procedure in MAC entity>

[0122] The random access procedure is initiated by RRC following a PDCCH command, the MAC entity itself, or a standardized event. Within the MAC entity, there is only one ongoing random access procedure at any time. The random access procedure of an SCell is initiated only by a PDCCH command with a ra-PreambleIndex different from 0b000000.

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

[0124] 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 contention-free random access resources of the 4-step RA type are explicitly provided by rach-ConfigDedicated for the BWP selected for the random access procedure, RA_TYPE is set to 4-stepRA.

[0125] When the selected RA_TYPE is set to 4-stepRA, the MAC entity performs the following operations.

[0126] When ra-PreambleIndex is explicitly provided from PDCCH and ra-PreambleIndex is not 0b000000, PREAMBLE_INDEX is set to the notified ra-PreambleIndex, and the SSB notified through PDCCH is selected.

[0127] ·When the SSB is selected as described above, the next available PRACH opportunity is determined from the PRACH opportunities corresponding to the selected SSB and with the restricted permission given by ra-ssb-OccasionMaskIndex (the MAC entity randomly selects a PRACH opportunity with equal probability from consecutive PRACH opportunities corresponding to the selected SSB according to the specification. When determining the next available PRACH opportunity corresponding to the selected SSB, the MAC entity may also consider the possibility of the occurrence of a measurement gap).

[0128] <Time between PDCCH command reception and PRACH transmission>

[0129] If the random access procedure is initiated by a PDCCH command, the UE, if requested by higher layers, shall transmit PRACH in the selected PRACH opportunity when the time between the last symbol received by the PDCCH command and the first symbol transmitted by the PRACH is greater than N_(T,2)+Δ_BWPSwitching+Δ_Delay+T_switch[msec] (time condition) as described 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. It is assumed that μ corresponds to the minimum SCS setting between the subcarrier spacing (SCS) setting of the PDCCH command and the SCS setting transmitted by the corresponding PRACH. Δ_BWPSwitching=0 if the active UL BWP is unchanged, otherwise Δ_BWPSwitching is defined in the specification. Δ_delay=0.5msec in FR1 and 0.25msec in FR2. T_switch is the switching gap duration defined in the specification.

[0130] <Conditions for valid / invalid PRACH timing (valid conditions)>

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

[0132] [Provision 1]

[0133] In the case where the UE is not provided with tdd-UL-DL-ConfigurationCommon, the PRACH opportunity in the PRACH slot is valid when it does not precede the SS / PBCH block in the PRACH slot but starts at least N_gap codewords after the codeword is received from the last SS / PBCH block. Here, N_gap is specified in the specification. In the case where channelAccessMode=semistatic is provided, the PRACH opportunity does not overlap with the set of consecutive codewords before the start of the next channel occupancy time not sent by the UE. The candidate SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided via ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon.

[0134] [Provision 2]

[0135] When tdd-UL-DL-ConfigurationCommon is provided to the UE, the PRACH opportunity in the PRACH slot is valid in the following cases.

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

[0137] ·The PRACH opportunity does not precede the SS / PBCH block in the PRACH timeslot, but starts at least N_gap symbols from the last DL symbol and at least N_gap symbols from the last SS / PBCH block symbol. Here, N_gap is specified in the specification. If channelAccessMode=semistatic is provided, as stated in the specification, the PRACH opportunity does not overlap with the set of consecutive symbols before the start of the next channel occupancy time without any transmission. As stated in the specification, the candidate SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided via ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon.

[0138] (RAR receiving)

[0139] In response to a PRACH transmission, the UE attempts detection of 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 in 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 provided as a number of slots based on the SCS for the type 1-PDCCH CSS set by ra-responseWindow.

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

[0141] In the case where the UE attempts to detect a DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission started by a PDCCH order triggering a CFRA procedure for the SpCell, the UE may also assume that the PDCCH including the DCI format 1_0 and the PDCCH order have the same DMRS antenna port QCL properties. In the case where the UE attempts to detect a DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission 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 for reception of the PDCCH including the DCI format 1_0.

[0142] The RAR UL grant may also include at least one of the following: a frequency hopping flag field, a PUSCH frequency resource configuration (allocation) field, a PUSCH time resource configuration field, a modulation and coding scheme (MCS) field, a TPC command field for PUSCH, a CSI request field, and a channel access-cyclic prefix extension (CPext) field.

[0143] (PRACH uplink coverage improvement)

[0144] The following two cases / types of multiple PRACH transmissions are under study.

[0145] [Case 1 / Type 1 multiple PRACH transmission]

[0146] The UE repeatedly sends Msg1 on n random access opportunities (RO) / RO resources. After that, the UE waits for the detection of Msg2 in the set type 1 PDCCH opportunity. In the present disclosure, the repeated transmission of the preamble in n RO / RO resources is sometimes referred to as an RO group. The size of the RO group (the number of ROs in the RO group) is n. After one RO group, a RAR window starts.

[0147] [Case 2 / Type 2 multiple PRACH transmission]

[0148] The UE repeatedly sends Msg1 on n random access opportunity (RO) resources. After sending Msg1 on each RO, the UE waits for the detection of Msg2 in a type 1 PDCCH opportunity. The size of the RO group (the number of ROs in the RO group) is n. After each RO, a RAR window starts.

[0149] (Beam used for PRACH repetition)

[0150] In Rel.18, the introduction of a function of PRACH repetition with the same beam and a function of PRACH repetition with multiple different beams is under study. Figure 2A An example of a case where one RAR window (type 1 multi-PRACH transmission) is used for multiple repetitions of PRACH using the same beam is shown. Figure 2B An example is shown of a case where a plurality of RAR windows are used for each of a plurality of repetitions of PRACH using the same beam (type 2 multi-PRACH transmission). Figure 3A An example of a case where one RAR window (type 1 multi-PRACH transmission) is used for multiple repetitions of PRACH using different multiple beams is shown. Figure 3BAn example is shown in which a plurality of RAR windows are used for each of a plurality of repetitions of PRACH using a plurality of different beams (type 2 multi-PRACH transmission).

[0151] However, the relationship / combination / interaction between these two functions is not clear. For example, it is not clear whether these two functions can be supported / applied simultaneously. When these two functions are not supported / applied simultaneously, it is not clear how to decide whether the UE uses the same beam to send PRACH repetitions, uses different multiple beams to send PRACH repetitions, or does not perform PRACH repetitions. When these two functions are supported / applied simultaneously, it is not clear when the UE applies these two functions simultaneously. As such, if the relationship between the two functions is unclear, there is a concern that the communication quality may be reduced.

[0152] Therefore, the inventors of the present invention conceived of the relationship between the function of PRACH repetition associated with the same beam and the function of PRACH repetition associated with a plurality of different beams.

[0153] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The wireless communication methods according to the embodiments may be applied individually or in combination.

[0154] 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".

[0155] In the present disclosure, notification, activation, deactivation, indication (or indication), selection, configuration, update, determination, etc. may also be mutually rewritten. In the present disclosure, support, control, controllable, operation, and operationable may also be mutually rewritten.

[0156] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, high-layer parameters, fields, Information Element (IE), settings, etc. may also be overwritten. In the present disclosure, Medium Access Control (MAC Control Element (CE)), update commands, activation / deactivation commands, etc. may also be overwritten.

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

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

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

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

[0161] In the present disclosure, panel, UE panel, panel group, beam, beam group, precoder, uplink (UL) transmission entity, transmission / reception point (TRP), base station, spatial relation information (SRI), spatial relation, SRS resource indicator (SRI), control resource set (CORESET), physical downlink shared channel (PDSCH), codeword (CW), transport block (TB), reference signal (RS), antenna port (e.g., demodulation reference signal (DMRS)) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, code division multiplexing (CDM)) group, reference signal group, CORESET group, physical uplink control channel (PDSCH)), codeword (CW), transport block (TB), reference signal (RS), antenna port (e.g., demodulation reference signal (DMRS)) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, code division multiplexing (CDM)) group, reference signal group, CORESET group, physical uplink control channel (PDSCH)), 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 Indicationstate (TCI state)) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state (unifiedTCI state), common TCI state (common TCI state), Quasi-Co-Location (Quasi-Co-Location (QCL)), QCL assumptions, etc. can also be overwritten with each other.

[0162] In addition, in the present disclosure, “having the ability to…” may be replaced with “the ability to support / report…”.

[0163] (Wireless Communication Method)

[0164] In each embodiment, a RACH attempt, a process from PRACH repetition to RAR reception determination, and a number of PRACH repetitions may be overwritten. A RACH attempt may also be ended by the success or failure of the corresponding RAR reception. Other RACH attempts may also be started based on the failure of RAR reception within a RACH attempt.

[0165] In each embodiment, PRACH without repetition (first transmission method) may be PRACH in which repetition is not applied / determined / set / indicated. In each embodiment, PRACH repetition using the same beam (second transmission method) may be using the same beam / TCI state / spatial domain filter for multiple repetitions of PRACH. In each embodiment, PRACH repetition using different multiple beams (third transmission method) may be using different multiple beams / TCI states / spatial domain filters for multiple repetitions of PRACH. In each embodiment, PRACH repetition using the same beam and different multiple beams (fourth transmission method) may be: multiple repetitions of PRACH include multiple sets, each set includes more than two repetitions, the same beam / TCI state / spatial domain filter is used for more than two repetitions in each set, and different multiple beams / TCI states / spatial domain filters are used for multiple sets.

[0166] In each embodiment, the function of PRACH repetition using the same beam and the function of PRACH repetition using different multiple beams, two functions, two transmission methods, two transmission modes, and two repetition modes may be rewritten mutually.

[0167] In each embodiment, the function of PRACH without repetition, the function of PRACH repetition using the same beam, and the function of PRACH repetition using different multiple beams, three functions, three transmission methods, and three transmission modes can also be rewritten.

[0168] In each embodiment, the function of PRACH without repetition, the function of PRACH repetition using the same beam, the function of PRACH repetition using different multiple beams, and the function of PRACH repetition using the same beam and different multiple beams, four functions, four transmission methods, and four transmission modes can also be rewritten with each other.

[0169] Each figure in each embodiment (for example, Figures 6 to 11The operation of each ) is applied to the case where one RAR window is used after multiple repetitions of PRACH (type 1 multiple PRACH transmission), but can also be applied to the case where one RAR window is used after each repetition of PRACH (type 2 multiple PRACH transmission).

[0170] The UE may also determine a transmission method among a first transmission method of transmitting a physical random access channel (PRACH) without multiple repetitions, a second transmission method of transmitting the multiple repetitions using the same beam, a third transmission method of transmitting the multiple repetitions using different multiple beams, and a fourth transmission method of transmitting the multiple repetitions using the same beam and different multiple beams. The UE may also use the transmission method to transmit more than one PRACH.

[0171] <Implementation method #1>

[0172] This embodiment relates to whether PRACH repetition using the same beam and PRACH repetition using multiple different beams are applied simultaneously.

[0173] Option 1

[0174] It may be stipulated that the UE does not assume that the capability for PRACH repetition using the same beam and the capability for PRACH repetition using different multiple beams are reported simultaneously.

[0175] Option 2

[0176] It may be stipulated that the UE does not assume that the PRACH repetition using the same beam instructed / configured by the base station and the PRACH repetition using different multiple beams are activated / configured at the same time.

[0177] It may also be specified that the UE does not assume that PRACH repetitions using the same beam and PRACH repetitions using different multiple beams are simultaneously activated / configured through SIB / RRC IE. It may also be specified that the UE does not assume that there are any RACH resource sets configured with an indication for PRACH repetitions using the same beam and any RACH resource sets configured with an indication for PRACH repetitions using different multiple beams. It may also be specified that the UE does not assume that there are any RACH resource sets configured for PRACH repetitions using the same beam and any RACH resource sets configured for PRACH repetitions using different multiple beams.

[0178] Option 3

[0179] It may also be specified that the UE does not assume that these two functions are applied simultaneously in one RACH attempt.

[0180] It may also be specified that: in one RACH attempt, when the UE sends PRACH repetitions on different multiple beams, the UE does not assume that multiple PRACH repetitions using the same beam are sent. It may also be specified that: in one RACH attempt, when the UE sends PRACH repetitions on different multiple beams, the UE does not assume that a PRACH opportunity on an arbitrary RACH resource set set for PRACH repetitions using the same beam is sent. It may also be specified that: in one RACH attempt, the UE does not assume that there is an arbitrary RACH resource set set for both PRACH repetitions using the same beam and PRACH repetitions using different multiple beams.

[0181] Option 4

[0182] The UE may also be applied with these two functions simultaneously in one RACH attempt.

[0183] Option 5

[0184] It may also be specified that the UE does not assume that these two functions are applied simultaneously in one RACH attempt. Based on option 3, option 5 may also be accompanied by the following additional requirement, that is, it is not assumed that: multiple PRACH repetitions using the same beam are sent in one RACH attempt within one RACH process, and multiple PRACH repetitions using different multiple beams are sent in other RACH attempts within the RACH process (before the expiration of the preamble code transmission counter PREAMBLE_TRANSMISSION_COUNTER).

[0185] exist Figure 4A In the example, the UE sends multiple repetitions of PRACH (Msg1) using the same beam and different multiple beams in one RACH attempt. For 2 repetitions of PRACH, one beam and one RAR window are used. Multiple RAR windows correspond to different multiple beams, respectively. This example is not allowed for option 3 / 5. This example is allowed for option 4.

[0186] exist Figure 4BIn the example, the UE sends multiple repetitions of PRACH using the same beam in one RACH attempt in one RACH process, and sends multiple repetitions of PRACH using different multiple beams in other RACH attempts in the same RACH process if the reception of RAR fails. One RAR window is used for one RACH attempt. This example is not allowed for option 5. This example is allowed for option 3.

[0187] The UE may also support at least one of the following scenarios.

[0188] [Case 1] The UE reports only the capability for PRACH repetition using the same beam among the two functions, and only PRACH repetition using the same beam is activated / configured by the base station.

[0189] The UE decides whether to send PRACH without repetition or to send PRACH repetition using the same beam.

[0190] [Case 2] The UE reports only the capability for PRACH repetition using different multiple beams among the two functions, and only PRACH repetition using the same beam is activated / configured by the base station.

[0191] The UE sends PRACH without repetition.

[0192] [Case 3] A case where the UE reports the capability for PRACH repetition using the same beam and the capability for PRACH repetition using different multiple beams, and only PRACH repetition using the same beam is activated / configured by the base station.

[0193] In option 1, this situation is an error situation. In options 2 / 3 / 4 / 5, the UE decides whether to send PRACH without repetition or to send PRACH repetition using the same beam.

[0194] [Case 4] The UE reports only the capability for PRACH repetition using the same beam among the two functions, and only PRACH repetition using different multiple beams is activated / configured by the base station.

[0195] The UE sends PRACH without repetition.

[0196] [Case 5] The UE reports only the capability for PRACH repetition using different multiple beams among the two functions, and only PRACH repetition using different multiple beams is activated / configured by the base station.

[0197] The UE decides whether to send PRACH without repetition or to send PRACH repetition using different multiple beams.

[0198] [Case 6] A case where the UE reports the capability for PRACH repetition using the same beam and the capability for PRACH repetition using different multiple beams, and only the PRACH repetition using different multiple beams is activated / configured by the base station.

[0199] In option 1, this situation is an error situation. In options 2 / 3 / 4 / 5, the UE decides whether to send PRACH without repetition or to send PRACH repetition using different multiple beams.

[0200] [Case 7] The UE reports only the capability for PRACH repetition using the same beam among the two functions, and PRACH repetition using the same beam and PRACH repetition using different multiple beams are simultaneously activated / configured by the base station.

[0201] In options 1 / 3 / 4 / 5, the UE decides whether to send PRACH without repetition or to send PRACH repetition using the same beam. In option 2, this situation is an error situation.

[0202] [Case 8] The UE reports only the capability for PRACH repetition using different multiple beams among the two functions, and PRACH repetition using the same beam and PRACH repetition using different multiple beams are simultaneously activated / configured by the base station.

[0203] In options 1 / 3 / 4 / 5, the UE decides whether to send PRACH without repetition or to send PRACH repetition using different multiple beams. In option 2, this situation is an error situation.

[0204] [Case 9] The UE reports the capability for PRACH repetition using the same beam and the capability for PRACH repetition using different multiple beams, and the PRACH repetition using the same beam and the PRACH repetition using different multiple beams are simultaneously activated / configured by the base station.

[0205] In option 1 / 2, this situation is an error situation. In option 3, the UE decides which of the following to apply: PRACH without repetition, PRACH repetition using the same beam, and PRACH repetition using different multiple beams. In option 4, the UE decides which of the following to apply: PRACH without repetition, PRACH repetition using the same beam, PRACH repetition using different multiple beams, and PRACH repetition using the same beam and different multiple beams. In option 5, for each RACH attempt, the UE may also follow at least one of the following operations.

[0206] ·In the case where the RACH attempt is the first RACH attempt of the RACH procedure, or if the UE has not sent PRACH with repetition in any previous RACH attempt of the RACH procedure, the UE decides which of the following to apply: PRACH without repetition, PRACH repetition using the same beam, and PRACH repetition using different multiple beams.

[0207] When the UE transmits a plurality of PRACH repetitions using the same beam in any previous RACH attempt of the RACH procedure, the UE determines whether to apply PRACH without repetition or PRACH repetition using the same beam.

[0208] When the UE transmits a plurality of PRACH repetitions using different multiple beams in any previous RACH attempt of the RACH procedure, the UE determines whether to apply PRACH without repetition or PRACH repetition using different multiple beams.

[0209] The UE may also decide whether to perform PRACH repetition, and whether to use the same beam or multiple different beams or at least one of the same beam and multiple different beams for PRACH repetition based on at least one of the following factors.

[0210] · Definition of norms.

[0211] Indication based on SIB / RRC IE / PDCCH order.

[0212] RO setting parameters.

[0213] The current PREAMBLE_TRANSMISSION_COUNTER.

[0214] Random access restriction parameters, for example, at least one of preambleTransMax, ra-ResponseWindow, and ra-ContentionResolutionTimer.

[0215] The RSRP of one or more received SSBs or CSI-RSs.

[0216] Priority between PRACH repetition using the same beam and PRACH repetition using multiple different beams.

[0217] UE capabilities related to beam correspondence.

[0218] The UE may also decide whether to perform multiple PRACH repetitions, and whether to use the same beam or different multiple beams or the same beam and different multiple beams for the PRACH repetitions based on at least one of the configuration (deployment) scenario, duplex mode, frequency range, and whether it is a licensed band or an unlicensed band. The configuration scenario may be, for example, a terrestrial network or a non-terrestrial network, or the type of non-terrestrial network. The duplex mode may also be, for example, TDD (unpaired spectrum) or FDD (paired spectrum). The frequency range may also be, for example, FR1 / 2-1 / 2-2. Whether it is a licensed band or an unlicensed band, whether it is a licensed cell or an unlicensed cell, whether it is a shared spectrum, and whether to use shared spectrum channel access may also be rewritten mutually.

[0219] For example, the UE may transmit multiple PRACH repetitions using the same beam / different multiple beams in a geostationary orbit (GEO) scenario, and transmit PRACH without repetition in a low orbit (LEO) scenario. For example, the UE may transmit multiple PRACH repetitions using the same beam / different multiple beams in TDD (unpaired spectrum), and transmit PRACH without repetition in FDD (paired spectrum). For example, the UE may transmit multiple PRACH repetitions using the same beam / different multiple beams in a licensed band, and transmit PRACH without repetition in an unlicensed band. For example, the UE may transmit multiple PRACH repetitions using the same beam / different multiple beams in FR2-2, and transmit PRACH without repetition in FR1 / 2-1.

[0220] "Example 1"

[0221] This example relates to how the UE determines whether to transmit a PRACH without repetition or to transmit a PRACH repetition (and the number of repetitions) using the same beam. This example can also correspond to scenarios 1 / 3 / 7.

[0222] [Option 1-0]

[0223] The transmission method may also be specified by the specification. The specification may also specify that the UE always transmits PRACH repetitions using the same beam, or that the UE always transmits PRACH without repetitions. The specification may also specify different operations for different situations (within situations 1 / 3 / 7).

[0224] [Option 1-1]

[0225] This transmission method may be instructed by SIB / RRC IE / PDCCH command (for RACH procedure instructed by PDCCH). The base station may instruct whether to perform PRACH repetition using the same beam (and the number of repetitions) by SIB / RRC IE / PDCCH command.

[0226] [Option 1-2]

[0227] The transmission method may also be based on the RACH triggering method / RACH purpose. The RACH triggering method may also be that RACH is started through a PDCCH command / MAC entity / RRC. The RACH purpose may also be initial access / system information (SI) request / SpCell BFR / reconfiguration with sync.

[0228] The relationship / mapping between whether to transmit PRACH repetitions using the same beam (and the number of repetitions) and the RACH triggering method / RACH purpose may be defined by the specification or may be set by SIB / RRC IE.

[0229] [Options 1-3]

[0230] The transmission method may also be based on RO setting parameters. The RO setting parameters may also be at least one of the following: PRACH setting index, PRACH format, number of SSBs per RO, number of PRACH transmission opportunities for FDM in a time instance, number of PRACH time slots in a subframe, number of time domain PRACH opportunities in a PRACH time slot, PRACH duration, zeroCorrelationZoneConfig (cyclic shift number setting), and total number of preamble codes (for PRACH repetitions using the same beam).

[0231] The relationship / mapping between whether or not to transmit PRACH repetitions (and the number of repetitions) using the same beam and RO configuration parameters may be defined by the specification or may be configured by SIB / RRC IE.

[0232] [Options 1-4]

[0233] This transmission method may also be based on PREAMBLE_TRANSMISSION_COUNTER. When PREAMBLE_TRANSMISSION_COUNTER is larger than a certain value (specified by the specification or indicated by SIB / RRC IE), the UE may transmit PRACH repetitions using the same beam. Otherwise, the UE may transmit PRACH without repetitions.

[0234] The PRACH repetition number may also be based on the PREAMBLE_TRANSMISSION_COUNTER. For example, for a PREAMBLE_TRANSMISSION_COUNTER smaller than M1, the PRACH repetition number may also be N1. For a PREAMBLE_TRANSMISSION_COUNTER greater than M1 and less than M2, the PRACH repetition number may also be N2. For a PREAMBLE_TRANSMISSION_COUNTER greater than M2, the PRACH repetition number may also be N3.

[0235] [Options 1-5]

[0236] The transmission method may also be based on the value set for the random access restriction parameter (at least one of preambleTransMax, ra-ResponseWindow and ra-ContentionResolutionTimer). In at least one of the cases where the value set for preambleTransMax is less than a certain value Y1 / greater than Y1 / equal to Y1, the value set for ra-ResponseWindow is less than a certain value Y2 / greater than Y2 / equal to Y2, and the value set for ra-ContentionResolutionTimer is less than a certain value Y3 / greater than Y3 / equal to Y3, the UE may also send PRACH repetitions using the same beam. If this is not the case, the UE may also send PRACH without repetitions. Here, Y1, Y2, and Y3 may be specified by the specification or indicated by SIB / RRC IE.

[0237] The number of PRACH repetitions may be independent of the random access restriction parameter or may be dependent on the random access restriction parameter.

[0238] [Options 1-6]

[0239] The transmission method may also be based on the RSRP of one or more received SSBs or CSI-RSs.

[0240] The UE may also decide whether to send PRACH repetitions (and the number of repetitions) using the same beam based on at least one of the RSRP value of the selected SSB / CSI-RS (through the rules of Rel.15 / 16 / 17) and the range of the value of the RSRP gap. The gap may also be the gap between the RSRP of the selected SSB / CSI-RS and the maximum RSRP value or average RSRP value among all RSRP values ​​(or the RSRP value exceeding the rsrp-ThresholdSSB among the RSRP values ​​from the maximum value to N). Whether to perform PRACH repetition or to perform PRACH repetitions (and the number of repetitions) using the same beam may also correspond to the range of the value of the gap. The corresponding relationship / mapping may be specified in the specification or indicated by the SIB / RRC IE. For example, the mapping may also associate whether to send PRACH repetitions (and the number of repetitions) using the same beam with whether the gap is greater than a certain value / less than a certain value.

[0241] In at least one of the following cases, the UE may also send PRACH repetitions using the same beam when the received RSRP of the selected SSB / CSI-RS is less than a certain value, when the received RSRP of the selected SSB / CSI-RS is not (one of) the highest (N) RSRP values ​​among all RSRP values, and when the received RSRP of the selected SSB / CSI-RS is at least M dB less than the maximum RSRP value or the average RSRP value. If this is not the case, the UE may also send PRACH without repetitions. Here, a certain value, N, and M are integers that can be specified in the specification or indicated by SIB / RRC IE.

[0242] The UE may also decide whether to send PRACH repetitions using the same beam (and the number of repetitions) based on all RSRP values ​​(or RSRP values ​​exceeding rsrp-ThresholdSSB, or the highest N RSRP values), or based on the maximum / minimum / average / standard deviation of all RSRP values ​​(or RSRP values ​​exceeding rsrp-ThresholdSSB, or the highest N RSRP values), or based on the number of RSRP values ​​within a certain range. Whether to perform PRACH without repetition or to perform PRACH repetitions using the same beam (and the number of repetitions) may also correspond to at least one of the following: multiple different ranges of maximum / minimum / average / standard deviation of all RSRP values ​​(or RSRP values ​​exceeding rsrp-ThresholdSSB, or the highest N RSRP values), and multiple different ranges of the number of RSRP values ​​within a certain range. The corresponding relationship / mapping may be specified in the specification or indicated by SIB / RRC IE. For example, the mapping may associate whether or not to transmit PRACH repetitions using the same beam (and the number of repetitions) with whether the RSRP-based value is greater than or less than a certain value.

[0243] A combination of at least two of options 1-1 to 1-6 may also be used.

[0244] "Example 2"

[0245] This example relates to a transmission method / transmission mode of how the UE determines whether to transmit a PRACH without repetition or to transmit a PRACH with repetition using different multiple beams. This example can also correspond to scenarios 5 / 6 / 8.

[0246] [Option 2-0]

[0247] The transmission method may also be specified by the specification. The specification may also specify that the UE always transmits PRACH repetitions using different multiple beams, or that the UE always transmits PRACH without repetitions. The specification may also specify different operations for different situations (within situations 5 / 6 / 8).

[0248] [Option 2-1]

[0249] This transmission method may be instructed by SIB / RRC IE / PDCCH command (for RACH procedure ordered by PDCCH). The base station may instruct whether to perform PRACH repetition using different multiple beams (and the number of repetitions / number of beams) by SIB / RRC IE / PDCCH command.

[0250] [Option 2-2]

[0251] The transmission method may also be based on the RACH triggering method / RACH purpose. The RACH triggering method may also be that RACH is started through a PDCCH command / MAC entity / RRC. The RACH purpose may also be initial access / system information (SI) request / SpCell BFR / reconfiguration with sync.

[0252] The relationship / mapping between whether to send PRACH repetitions using different multiple beams (as well as the number of repetitions / number of beams, or multiple beams for multiple repetitions) and the RACH triggering method / RACH purpose can be defined by the specification or set by SIB / RRC IE.

[0253] [Option 2-3]

[0254] The transmission method may also be based on RO setting parameters. The RO setting parameters may also be at least one of the following: PRACH setting index, PRACH format, number of SSBs per RO, number of PRACH transmission opportunities for FDM in a time instance, number of PRACH time slots in a subframe, number of time domain PRACH opportunities in a PRACH time slot, PRACH duration, zeroCorrelationZoneConfig (cyclic shift number setting), and total number of preamble codes (for PRACH repetitions using different multiple beams).

[0255] The relationship / mapping between whether to transmit PRACH repetitions using different multiple beams (and the number of repetitions / number of beams) and RO configuration parameters may be defined by the specification or may be configured by SIB / RRC IE.

[0256] [Option 2-4]

[0257] This transmission method may also be based on PREAMBLE_TRANSMISSION_COUNTER. When PREAMBLE_TRANSMISSION_COUNTER is greater than a certain value (specified by the specification or indicated by SIB / RRC IE), the UE may transmit PRACH repetitions using different multiple beams. Otherwise, the UE may transmit PRACH without repetitions.

[0258] The number of PRACH repetitions / beams may also be based on the PREAMBLE_TRANSMISSION_COUNTER. For example, for a PREAMBLE_TRANSMISSION_COUNTER less than M1, the number of PRACH repetitions / beams may also be N1. For a PREAMBLE_TRANSMISSION_COUNTER greater than M1 but less than M2, the number of PRACH repetitions / beams may also be N2. For a PREAMBLE_TRANSMISSION_COUNTER greater than M2, the number of PRACH repetitions / beams may also be N3.

[0259] [Option 2-5]

[0260] The transmission method may also be based on the value set for the random access restriction parameter (at least one of preambleTransMax, ra-ResponseWindow, and ra-ContentionResolutionTimer). In at least one of the cases where the value set for preambleTransMax is less than a certain value Y1 / greater than Y1 / equal to Y1, the value set for ra-ResponseWindow is less than a certain value Y2 / greater than Y2 / equal to Y2, and the value set for ra-ContentionResolutionTimer is less than a certain value Y3 / greater than Y3 / equal to Y3, the UE may also send PRACH repetitions using different multiple beams. If this is not the case, the UE may also send PRACH without repetitions. Here, Y1, Y2, and Y3 may be specified by the specification or indicated by SIB / RRCIE.

[0261] The number of PRACH repetitions / beams may be independent of the random access restriction parameter or may be dependent on the random access restriction parameter.

[0262] [Options 2-6]

[0263] The transmission method may also be based on the RSRP of one or more received SSBs or CSI-RSs.

[0264] The UE may also determine whether to send PRACH repetitions (and the number of repetitions / number of beams) using different multiple beams based on at least one of the RSRP value of the selected SSB / CSI-RS (through the rules of Rel. 15 / 16 / 17) and the range of the value of the RSRP gap. The gap may also be the gap between the RSRP of the selected SSB / CSI-RS and the maximum RSRP value or average RSRP value among all RSRP values ​​(or the RSRP value exceeding the rsrp-ThresholdSSB among the RSRP values ​​from the maximum value to N). Whether to not perform PRACH repetition or to perform PRACH repetitions (and the number of repetitions / number of beams) using different multiple beams may also correspond to the range of the value of the gap. The corresponding relationship / mapping may be specified in the specification or indicated by the SIB / RRC IE. For example, the mapping may also associate whether to send PRACH repetitions (and the number of repetitions / number of beams) using different multiple beams with whether the gap is greater than a certain value / less than a certain value.

[0265] In at least one of the following cases, the UE may also send PRACH repetitions using different multiple beams when the received RSRP of the selected SSB / CSI-RS is less than a certain value, when the received RSRP of the selected SSB / CSI-RS is not (one of) the highest (N) RSRP values ​​among all RSRP values, and when the received RSRP of the selected SSB / CSI-RS is at least M dB less than the maximum RSRP value or the average RSRP value. If this is not the case, the UE may also send PRACH without repetitions. Here, a certain value, N, and M are integers that can be specified in the specification or indicated by SIB / RRC IE.

[0266] The UE may also decide whether to send PRACH repetitions using different multiple beams (and the number of repetitions / number of beams) based on all RSRP values ​​(or RSRP values ​​exceeding rsrp-ThresholdSSB, or the highest N RSRP values), or based on the maximum / minimum / average / standard deviation of all RSRP values ​​(or RSRP values ​​exceeding rsrp-ThresholdSSB, or the highest N RSRP values), or based on the number of RSRP values ​​within a certain range. Whether to perform PRACH without repetition or to perform PRACH repetitions using different multiple beams (and the number of repetitions / number of beams) may also correspond to at least one of different multiple ranges of maximum / minimum / average / standard deviation for all RSRP values ​​(or RSRP values ​​exceeding rsrp-ThresholdSSB, or the highest N RSRP values), and different multiple ranges of the amount of RSRP values ​​within a certain range. The corresponding relationship / mapping may be specified in the specification or indicated by SIB / RRC IE. For example, the mapping may associate whether or not to transmit PRACH repetitions using different multiple beams (and the number of repetitions / number of beams) with whether the RSRP-based value is greater than a certain value / less than a certain value.

[0267] [Option 2-7]

[0268] The transmission method may also be based on the UE capability of beam correspondence. In the case where the UE does not have / does not report the capability of beam correspondence, the UE may also transmit PRACH repetitions using different multiple beams. In the case where the UE has / reports the capability of beam correspondence, the UE may also transmit PRACH without repetitions.

[0269] A combination of at least two of options 2-1 to 2-7 may also be used.

[0270] "Example 3"

[0271] This example relates to how the UE determines the transmission method / transmission mode (one of the three transmission methods) of whether to transmit PRACH without repetition, to transmit PRACH repetition using the same beam, or to transmit PRACH repetition using different multiple beams. This example can also correspond to case 9.

[0272] [Option 3-0]

[0273] The transmission method may also be specified by the specification. The specification may also specify that the UE always transmits PRACH repetitions using the same beam, or that the UE always transmits PRACH repetitions using multiple different beams (and the number of beams), or that the UE always transmits PRACH without repetitions.

[0274] [Option 3-1]

[0275] The transmission method may be indicated by SIB / RRC IE / PDCCH command (for RACH procedure ordered by PDCCH). The base station may indicate one of the three transmission methods (and the number of repetitions / beams in the case of multiple PRACH repetitions) by SIB / RRC IE / PDCCH command.

[0276] [Option 3-2]

[0277] The transmission method may also be based on the RACH triggering method / RACH purpose. The RACH triggering method may also be that RACH is started through a PDCCH command / MAC entity / RRC. The RACH purpose may also be initial access / system information (SI) request / SpCell BFR / reconfiguration with sync.

[0278] The relationship / mapping between whether to send PRACH without repetition, to send PRACH repetitions using the same beam (and the number of repetitions), or to send PRACH repetitions using different multiple beams (and the number of repetitions / number of beams) and the RACH triggering method / RACH purpose can be defined by the specification or set by SIB / RRC IE.

[0279] [Option 3-3]

[0280] The transmission method may also be based on RO setting parameters. The RO setting parameters may also be at least one of the following: PRACH setting index, PRACH format, number of SSBs per RO, number of PRACH transmission opportunities for FDM in a time instance, number of PRACH time slots in a subframe, number of time domain PRACH opportunities in a PRACH time slot, PRACH duration, zeroCorrelationZoneConfig (cyclic shift number setting), total number of preamble codes (for PRACH repetitions using the same beam / different multiple beams).

[0281] The relationship / mapping between sending PRACH without repetition, sending PRACH repetitions using the same beam (and the number of repetitions), or sending PRACH repetitions using different multiple beams (and the number of repetitions / number of beams) and RO setting parameters can be defined by the specification or set by SIB / RRC IE.

[0282] [Option 3-4]

[0283] The sending method may also be based on PREAMBLE_TRANSMISSION_COUNTER.

[0284] Whether to send PRACH without repetition, send PRACH repetitions using the same beam (and the number of repetitions), or send PRACH repetitions using different multiple beams (and the number of repetitions / number of beams) can also correspond to different ranges of PREAMBLE_TRANSMISSION_COUNTER values. The relationship / mapping between the three transmission methods and the range can be specified by the specification or set by SIB / RRC IE. For example, the mapping can also associate one of the three transmission methods with a value greater than / less than a certain value based on RSRP.

[0285] When PREAMBLE_TRANSMISSION_COUNTER is greater than X0 / less than X1, the UE may also send PRACH without repetition. When PREAMBLE_TRANSMISSION_COUNTER is greater than X2 / less than X3, the UE may also send PRACH repetitions using the same beam. The number of PRACH repetitions may also be determined based on PREAMBLE_TRANSMISSION_COUNTER. For example, when Y0<(or ≤) PREAMBLE_TRANSMISSION_COUNTER<(or ≤) Y1, the number of PRACH repetitions may also be N1. When PREAMBLE_TRANSMISSION_COUNTER is greater than X4 / less than X5, the UE may also send PRACH repetitions using different multiple beams. The number of PRACH repetitions / the number of beams may also be determined based on PREAMBLE_TRANSMISSION_COUNTER. For example, when Y2<(or ≤)PREAMBLE_TRANSMISSION_COUNTER<(or ≤)Y3, the PRACH repetition number / beam number may be N2.

[0286] [Option 3-5]

[0287] The transmission method may also be based on a value set for a random access restriction parameter (at least one of preambleTransMax and ra-ResponseWindow and ra-ContentionResolutionTimer).

[0288] Whether to send PRACH without repetition, send PRACH repetitions using the same beam (and the number of repetitions), or send PRACH repetitions using different multiple beams (and the number of repetitions / number of beams) can also correspond to different ranges of values ​​of the random access restriction parameter. The relationship / mapping between the three transmission methods and the range can be specified by the specification or set by SIB / RRC IE. For example, the mapping can also associate one of the three transmission methods with a value greater than a certain value / less than a certain value based on RSRP.

[0289] In at least one of the cases where preambleTransMax is greater than or equal to X0 / less than X1, ra-ResponseWindow is greater than or equal to Y0 / less than Y1, and ra-ContentionResolutionTimer is greater than or equal to Z0 / less than Z1, the UE may also transmit PRACH without repetition. In at least one of the cases where preambleTransMax is greater than or equal to X2 / less than X3, ra-ResponseWindow is greater than or equal to Y2 / less than Y3, and ra-ContentionResolutionTimer is greater than or equal to Z2 / less than Z3, the UE may also transmit PRACH repetition using the same beam. In at least one of the cases where preambleTransMax is greater than or equal to X4 / less than X5, ra-ResponseWindow is greater than or equal to Y4 / less than Y5, and ra-ContentionResolutionTimer is greater than or equal to Z4 / less than Z5, the UE may also transmit PRACH repetition using different multiple beams.

[0290] The number of PRACH repetitions / beams may be independent of the random access restriction parameter or may be dependent on the random access restriction parameter.

[0291] [Options 3-6]

[0292] The transmission method may also be based on the RSRP of one or more received SSBs or CSI-RSs.

[0293] The UE may also determine one of the three transmission methods (and the number of repetitions / number of beams in the case of multiple PRACH repetitions) based on at least one of the RSRP value of the selected SSB / CSI-RS (through the rules of Rel. 15 / 16 / 17), the range of the value of the RSRP gap, all RSRP values ​​(or RSRP values ​​exceeding rsrp-ThresholdSSB, or the highest N RSRP values), the maximum / minimum / average / standard deviation of all RSRP values ​​(or RSRP values ​​exceeding rsrp-ThresholdSSB, or the highest N RSRP values), and the number of RSRP values ​​within a certain range. The gap may also be the gap between the RSRP of the selected SSB / CSI-RS and the maximum RSRP value or average RSRP value among all RSRP values ​​(or RSRP values ​​exceeding rsrp-ThresholdSSB among RSRP values ​​from the maximum value to N). At least one of the three transmission methods may also correspond to the range of the value of the gap. The corresponding relationship / mapping may be specified in the specification or indicated through SIB / RRC IE. For example, the mapping may associate one of the three transmission methods with a gap greater than a certain value / less than a certain value.

[0294] In the case where the received RSRP of the selected SSB / CSI-RS is within a certain range (through the rules of Rel. 15 / 16 / 17), the gap is within a certain range, all RSRP values ​​(or RSRP values ​​exceeding rsrp-ThresholdSSB, or the highest N RSRP values) are within a certain range, the maximum / minimum / average / standard deviation of all RSRP values ​​(or RSRP values ​​exceeding rsrp-ThresholdSSB, or the highest N RSRP values) are within a certain range, the RSRP values ​​more / less than M are within a certain range, the maximum / minimum / average / standard deviation of the received RSRP values ​​of all SSB / CSI-RS are within a certain range, and the maximum / minimum / average / standard deviation of the RSRP values ​​exceeding rsrp-ThresholdSSB are within a certain range, if the received RSRP value of the selected SSB / CSI-RS is not (one of) the maximum (highest X) RSRP values ​​among the RSRP values, the UE may also send PRACH repetitions using different multiple beams. Here, a certain value, X, and M are integers, and may be defined in the specification or indicated by SIB / RRC IE. In this case, the UE may transmit PRACH repetitions using the same beam.

[0295] [Options 3-7]

[0296] The sending method may also be based on a combination of Example 1 and Example 2.

[0297] The UE may first determine whether to send PRACH repetitions using the same beam based on Example 1. If PRACH repetitions using the same beam are not selected, the UE may determine whether to send PRACH repetitions using different multiple beams based on Example 2.

[0298] The UE may first determine whether to send PRACH repetitions using different multiple beams based on Example 2. If PRACH repetitions using different multiple beams are not selected, the UE may determine whether to send PRACH repetitions using the same beam based on Example 1.

[0299] [Options 3-8]

[0300] The transmission method may be based on the priority between PRACH repetition using the same beam and PRACH repetition using different multiple beams.

[0301] The priority of the two repetition modes (PRACH repetition using the same beam and PRACH repetition using different multiple beams) can be specified in the specification or indicated by the base station (via SIB / RRC IE / PDCCH command). For example, the priority of PRACH repetition using different multiple beams can be higher or lower than the priority of PRACH repetition using the same beam.

[0302] In a RACH attempt, if the RACH attempt is the first (or up to the Xth) RACH attempt in the current RACH process (the value of PREAMBLE_TRANSMISSION_COUNTER is 0 (or less than X)), or if the UE has not sent multiple PRACH repetitions in any of the previous X (continuous) RACH attempts in the RACH process, the UE may also decide to apply a repetition method with a higher priority in the RACH attempt. The value of X may be specified by the specification or indicated by the SIB / RRC IE / PDCCH command. The value of X may also be any integer greater than 1.

[0303] When the priority of PRACH repetition using the same beam is higher than the priority of PRACH repetition using different multiple beams, the UE may decide whether to perform PRACH repetition using different multiple beams based on Example 2.

[0304] When the priority of PRACH repetition using different multiple beams is higher than the priority of PRACH repetition using the same beam, the UE may decide whether to perform PRACH repetition using the same beam based on Example 1.

[0305] In a RACH attempt, if the UE sends multiple PRACH iterations within any of the previous X (consecutive) RACH attempts within the RACH process and the RACH attempt fails, the UE may also follow any of the following operations. The value of X may be specified in the specification or indicated by SIB / RRC IE / PDCCH command. The value of X may also be any integer greater than 1.

[0306] [[Operation A]]

[0307] The UE performs multiple PRACH iterations using a repetition mode with a lower priority within the RACH attempt.

[0308] When the priority of PRACH repetitions using the same beam is higher than the priority of PRACH repetitions using different multiple beams, and the UE has failed to send multiple PRACH repetitions using the same beam in a previous RACH attempt, the UE may send multiple PRACH repetitions using different multiple beams.

[0309] When the priority of PRACH repetitions using different multiple beams is higher than the priority of PRACH repetitions using the same beam, and the UE has failed to send multiple PRACH repetitions using different multiple beams in a previous RACH attempt, the UE may send multiple PRACH repetitions using the same beam.

[0310] [[Operation B]]

[0311] The UE decides whether to apply a to-and-fro method with a lower priority within the RACH attempt.

[0312] When the priority of PRACH repetitions using the same beam is higher than the priority of PRACH repetitions using different multiple beams, and the UE has failed to send multiple PRACH repetitions using the same beam in a previous RACH attempt, the UE may also decide whether to send multiple PRACH repetitions using different multiple beams based on Example 2.

[0313] exist Figure 5AIn the example, the priority of PRACH repetitions using the same beam is higher than the priority of PRACH repetitions using different multiple beams, and the UE sent multiple PRACH repetitions using the same beam in the previous RACH attempt and RAR reception failed. The UE may also send multiple PRACH repetitions using different multiple beams in the next RACH attempt.

[0314] When the priority of PRACH repetitions using different multiple beams is higher than the priority of PRACH repetitions using the same beam, and the UE has failed to send multiple PRACH repetitions using different multiple beams in a previous RACH attempt, the UE may also decide whether to send multiple PRACH repetitions using the same beam based on Example 1.

[0315] exist Figure 5B In the example, the priority of PRACH repetitions using different multiple beams is higher than the priority of PRACH repetitions using the same beam, and the UE sent multiple PRACH repetitions using different multiple beams in the previous RACH attempt and RAR reception failed. The UE may also send multiple PRACH repetitions using the same beam in the next RACH attempt.

[0316] [Options 3-9]

[0317] The transmission method may also be based on the UE capability of beam correspondence. In the case where the UE does not have / does not report the capability of beam correspondence, the UE may also send PRACH repetitions using different multiple beams. In the case where the UE has / reports the capability of beam correspondence, the UE may also decide whether to send PRACH without repetition or send PRACH repetitions using the same beam based on Example 1.

[0318] A combination of at least two of options 3-1 to 3-9 may also be used.

[0319] "Example 4"

[0320] This example relates to how the UE determines whether to send PRACH without repetition, send PRACH repetition using the same beam, send PRACH repetition using different multiple beams, or send PRACH repetition using the same beam and different multiple beams, and the transmission method / transmission mode (one transmission method out of four transmission methods). This example can also correspond to scenario 9.

[0321] [Option 4-0]

[0322] The transmission method may also be specified by a specification. The specification may also specify that the UE always transmits PRACH repetitions using the same beam, or that the UE always transmits PRACH repetitions using different multiple beams (and the number of beams), or that the UE always transmits PRACH repetitions using the same beam and different multiple beams (and the number of beams), or that the UE always transmits PRACH without repetitions.

[0323] [Option 4-1]

[0324] The transmission method may be indicated by SIB / RRC IE / PDCCH command (for RACH procedure ordered by PDCCH). The base station may indicate one of the four transmission methods (and the number of repetitions / beams in the case of multiple PRACH repetitions) by SIB / RRC IE / PDCCH command.

[0325] [Option 4-2]

[0326] The transmission method may also be based on the RACH triggering method / RACH purpose. The RACH triggering method may also be that RACH is started through a PDCCH command / MAC entity / RRC. The RACH purpose may also be initial access / system information (SI) request / SpCell BFR / reconfiguration with sync.

[0327] The relationship / mapping between sending PRACH without repetition, sending PRACH repetitions using the same beam (and the number of repetitions), sending PRACH repetitions using different multiple beams (and the number of repetitions / number of beams), or sending PRACH repetitions using the same beam and different multiple beams (and the number of repetitions for each beam) and the RACH triggering method / RACH purpose can be defined by the specification and can also be set by SIB / RRC IE.

[0328] [Option 4-3]

[0329] The transmission method may also be based on RO setting parameters. The RO setting parameters may also be at least one of the following: PRACH setting index, PRACH format, number of SSBs per RO, number of PRACH transmission opportunities for FDM in a time instance, number of PRACH time slots in a subframe, number of time domain PRACH opportunities in a PRACH time slot, PRACH duration, zeroCorrelationZoneConfig (cyclic shift number setting), total number of preamble codes (for PRACH repetitions using the same beam / different multiple beams).

[0330] The relationship / mapping between sending PRACH without repetition, sending PRACH repetition using the same beam (and the number of repetitions), sending PRACH repetition using different multiple beams (and the number of repetitions / number of beams), or sending PRACH repetition using the same beam and different multiple beams (and the number of repetitions for each beam) and the RO setting parameters can be defined by the specification or set by SIB / RRC IE.

[0331] [Option 4-4]

[0332] The sending method may also be based on PREAMBLE_TRANSMISSION_COUNTER.

[0333] Whether to send PRACH without repetition, send PRACH repetition using the same beam (and the number of repetitions), send PRACH repetition using different multiple beams (and the number of repetitions / number of beams), or send PRACH repetition using the same beam and different multiple beams (and the number of repetitions for each beam) can also correspond to different ranges of PREAMBLE_TRANSMISSION_COUNTER values. The relationship / mapping between the four transmission methods and the range can be specified by the specification or set by SIB / RRC IE. For example, the mapping can also associate one of the four transmission methods with a value greater than a certain value / less than a certain value based on RSRP.

[0334] When PREAMBLE_TRANSMISSION_COUNTER is greater than X0 / less than X1, the UE may also send PRACH without repetition. When PREAMBLE_TRANSMISSION_COUNTER is greater than X2 / less than X3, the UE may also send PRACH repetitions using the same beam. The number of PRACH repetitions may also be determined based on PREAMBLE_TRANSMISSION_COUNTER. For example, when Y0<(or ≤) PREAMBLE_TRANSMISSION_COUNTER<(or ≤) Y1, the number of PRACH repetitions may also be N1. When PREAMBLE_TRANSMISSION_COUNTER is greater than X4 / less than X5, the UE may also send PRACH repetitions using different multiple beams. The number of PRACH repetitions / the number of beams may also be determined based on PREAMBLE_TRANSMISSION_COUNTER. For example, when Y2<(or ≤)PREAMBLE_TRANSMISSION_COUNTER<(or ≤)Y3, the number of PRACH repetitions / number of beams may also be N2. When PREAMBLE_TRANSMISSION_COUNTER is greater than X6 / less than X7, the UE may also send PRACH repetitions using the same beam and multiple different beams. At least one of the number of beams, the number of PRACH repetitions for each beam, and the total number of PRACH repetitions may also be determined based on PREAMBLE_TRANSMISSION_COUNTER. For example, when Y4<(or ≤)PREAMBLE_TRANSMISSION_COUNTER<(or ≤)Y5, the number of PRACH beams may also be N3, and the total number of PRACH repetitions may also be N4.

[0335] [Option 4-5]

[0336] The transmission method may also be based on a value set for a random access restriction parameter (at least one of preambleTransMax and ra-ResponseWindow and ra-ContentionResolutionTimer).

[0337] Whether to send PRACH without repetition, or to send PRACH repetition using the same beam (and the number of repetitions), or to send PRACH repetition using different multiple beams (and the number of repetitions / number of beams), or to send PRACH repetition using the same beam and different multiple beams (and the number of repetitions for each beam) can also correspond to different ranges of values ​​of the random access restriction parameter. The relationship / mapping between the four transmission methods and the range can be specified by the specification or set by SIB / RRC IE. For example, the mapping can also associate one of the four transmission methods with a value greater than a certain value / less than a certain value based on RSRP.

[0338] In at least one of the cases where preambleTransMax is greater than or equal to X0 / less than X1, ra-ResponseWindow is greater than or equal to Y0 / less than Y1, and ra-ContentionResolutionTimer is greater than or equal to Z0 / less than Z1, the UE may also transmit PRACH without repetition. In at least one of the cases where preambleTransMax is greater than or equal to X2 / less than X3, ra-ResponseWindow is greater than or equal to Y2 / less than Y3, and ra-ContentionResolutionTimer is greater than or equal to Z2 / less than Z3, the UE may also transmit PRACH repetition using the same beam. In at least one of the cases where preambleTransMax is greater than or equal to X4 / less than X5, ra-ResponseWindow is greater than or equal to Y4 / less than Y5, and ra-ContentionResolutionTimer is greater than or equal to Z4 / less than Z5, the UE may also transmit PRACH repetition using different multiple beams. In at least one of the cases where preambleTransMax is greater than X6 / less than X7, ra-ResponseWindow is greater than Y6 / less than Y7, and ra-ContentionResolutionTimer is greater than Z6 / less than Z7, the UE may send PRACH repetitions using the same beam and different multiple beams.

[0339] At least one of the number of beams, the number of PRACH repetitions for each beam, and the total number of PRACH repetitions may be independent of or dependent on the random access restriction parameter.

[0340] [Options 4-6]

[0341] The transmission method may also be based on the RSRP of one or more received SSBs or CSI-RSs.

[0342] The UE may also determine one of the four transmission methods (and the number of repetitions / number of beams in the case of multiple PRACH repetitions) based on at least one of the RSRP value of the selected SSB / CSI-RS (through the rules of Rel. 15 / 16 / 17), the range of the value of the RSRP gap, all RSRP values ​​(or RSRP values ​​exceeding rsrp-ThresholdSSB, or the highest N RSRP values), the maximum / minimum / average / standard deviation of all RSRP values ​​(or RSRP values ​​exceeding rsrp-ThresholdSSB, or the highest N RSRP values), and the number of RSRP values ​​within a certain range. The gap may also be the gap between the RSRP of the selected SSB / CSI-RS and the maximum RSRP value or average RSRP value among all RSRP values ​​(or RSRP values ​​exceeding rsrp-ThresholdSSB among RSRP values ​​from the maximum value to N). At least one of the four transmission methods may also correspond to the range of the value of the gap. The corresponding relationship / mapping may be specified in the specification or indicated through SIB / RRC IE. For example, the mapping may associate one of the four transmission methods with a gap greater than a certain value / less than a certain value.

[0343] In the case of reception of more than N SSB / CSI-RS with RSRP greater than X1, and the maximum RSRP is lower than X2, the UE may also send multiple PRACH repetitions using different beams, sending multiple repetitions on each beam or on several of different beams.

[0344] In the case of receiving more than N SSB / CSI-RS with RSRP greater than X3, the UE may transmit multiple PRACH repetitions using different multiple beams.

[0345] When there is only one SSB / CSI-RS reception with RSRP greater than X1, and the maximum RSRP is lower than X2, the UE may transmit multiple PRACH repetitions using the same multiple beams.

[0346] [Options 4-7]

[0347] The sending method may also be based on a combination of Example 1 and Example 2.

[0348] The UE may use Example 1 / Example 2 to determine whether the same beam, different beams, or the same beam and different beams are to be applied to multiple repetitions.

[0349] The UE may also apply Example 1 (determine whether to use PRACH repetitions of the same beam), and then apply Example 2 (determine whether to use PRACH repetitions of different multiple beams). The UE may also follow the following steps.

[0350] [[Step 1]] The UE may also decide whether to send PRACH repetitions using the same beam based on Example 1.

[0351] [[Step 2]] The UE may also decide whether to send PRACH repetitions using different multiple beams based on Example 2.

[0352] The UE may also comply with at least one of any of the following scenarios.

[0353] When PRACH using the same beam is not selected through repetition in Example 1 and PRACH using different multiple beams is not selected through repetition in Example 2, the UE may transmit PRACH without repetition.

[0354] When PRACH repetition using the same beam is not selected in Example 1 and PRACH repetition using different multiple beams is selected in Example 2, the UE may transmit PRACH repetition using different multiple beams.

[0355] When PRACH repetition using the same beam is selected in Example 1 and PRACH repetition using different multiple beams is not selected in Example 2, the UE may transmit PRACH repetition using the same beam.

[0356] When PRACH repetition using the same beam is selected according to Example 1 and PRACH repetition using different multiple beams is selected according to Example 2, the UE may transmit PRACH repetition using the same beam and different multiple beams.

[0357] The UE may also apply Example 2 (determine whether to use PRACH repetitions of different multiple beams), and then apply Example 1 (determine whether to use PRACH repetitions of the same beam). The UE may also follow the following steps.

[0358] [[Step 1]] The UE may also decide whether to send PRACH repetitions using different multiple beams based on Example 2.

[0359] [[Step 2]] The UE may determine, based on Example 1, whether it is necessary to use the PRACH repetition for each beam of the PRACH repetition transmission beam determined in Step 1.

[0360] The UE may also comply with at least one of any of the following scenarios.

[0361] When PRACH repetition using different multiple beams is not selected through Example 2, and PRACH repetition using the same beam is not selected through Example 1, the UE may transmit PRACH without repetition.

[0362] When PRACH repetition using different multiple beams is not selected in Example 2 and PRACH repetition using the same beam is selected in Example 1, the UE may transmit PRACH repetition using the same beam.

[0363] When PRACHs using different multiple beams are repeatedly selected through Example 2, the UE may comply with at least one of the following (a) and (b) for each of the determined multiple beams.

[0364] (a) When PRACH repetitions using the same beam are selected in Example 1, the UE may transmit multiple repetitions on the beam.

[0365] (b) When PRACH repetitions using the same beam are not selected in Example 1, the UE may transmit only one repetition on the beam.

[0366] [Options 4-8]

[0367] The transmission method may be based on the priority between PRACH repetition using the same beam and PRACH repetition using different multiple beams.

[0368] The priority of the two repetition modes (PRACH repetition using the same beam and PRACH repetition using different multiple beams) can be specified in the specification or indicated by the base station (via SIB / RRC IE / PDCCH command). For example, the priority of PRACH repetition using different multiple beams can be higher or lower than the priority of PRACH repetition using the same beam.

[0369] In a RACH attempt, if the RACH attempt is the first (or up to the Xth) RACH attempt in the current RACH process (the value of PREAMBLE_TRANSMISSION_COUNTER is 0 (or less than X)), or if the UE has not sent multiple PRACH repetitions in any of the previous X (continuous) RACH attempts in the RACH process, the UE may also decide to apply a repetition method with a higher priority in the RACH attempt. The value of X may be specified by the specification or indicated by the SIB / RRC IE / PDCCH command. The value of X may also be any integer greater than 1.

[0370] When the priority of PRACH repetition using the same beam is higher than the priority of PRACH repetition using different multiple beams, the UE may decide whether to perform PRACH repetition using different multiple beams based on Example 2.

[0371] When the priority of PRACH repetition using different multiple beams is higher than the priority of PRACH repetition using the same beam, the UE may decide whether to perform PRACH repetition using the same beam based on Example 1.

[0372] In a RACH attempt, if the UE sends multiple PRACH iterations in any of the previous X (consecutive) RACH attempts within the RACH process and the RACH attempt fails, the UE may also follow any of the following operations. The value of X may be specified in the specification or indicated by SIB / RRC IE / PDCCH command. The value of X may also be any integer greater than 1.

[0373] [[Operation A]]

[0374] The UE performs multiple PRACH iterations using a repetition mode with a lower priority within the RACH attempt.

[0375] When the priority of PRACH repetitions using the same beam is higher than the priority of PRACH repetitions using different multiple beams, and the UE has failed to send multiple PRACH repetitions using the same beam in a previous RACH attempt, the UE may send multiple PRACH repetitions using different multiple beams.

[0376] When the priority of PRACH repetitions using different multiple beams is higher than the priority of PRACH repetitions using the same beam, and the UE has failed to send multiple PRACH repetitions using different multiple beams in a previous RACH attempt, the UE may send multiple PRACH repetitions using the same beam.

[0377] If the UE sent multiple PRACH repetitions with higher priority within any previous X (consecutive) RACH attempts within the RACH process and the RACH attempt failed, and the UE sent multiple PRACH repetitions with lower priority within any previous Y (consecutive) RACH attempts within the RACH process and the RACH attempt failed, the UE may also send multiple PRACH repetitions using the same beam and different multiple beams.

[0378] [[Operation B]]

[0379] The UE transmits multiple PRACH repetitions using the same beam and multiple different beams within the RACH attempt.

[0380] When the priority of PRACH repetitions using the same beam is higher than the priority of PRACH repetitions using different multiple beams, and the UE has failed to send multiple PRACH repetitions using the same beam in a previous RACH attempt, the UE may also send multiple PRACH repetitions using the same beam and different multiple beams.

[0381] When the priority of PRACH repetitions using different multiple beams is higher than the priority of PRACH repetitions using the same beam, and the UE has failed to send multiple PRACH repetitions using different multiple beams in a previous RACH attempt, the UE may also send multiple PRACH repetitions using the same beam and different multiple beams.

[0382] [[Operation C]]

[0383] The UE decides whether to apply the iterative method with a lower priority within the RACH attempt.

[0384] When the priority of PRACH repetitions using the same beam is higher than the priority of PRACH repetitions using different multiple beams, and the UE has failed to send multiple PRACH repetitions using the same beam in a previous RACH attempt, the UE may also decide whether to send multiple PRACH repetitions using different multiple beams based on Example 2.

[0385] When the priority of PRACH repetitions using different multiple beams is higher than the priority of PRACH repetitions using the same beam, and the UE has failed to send multiple PRACH repetitions using different multiple beams in a previous RACH attempt, the UE may also decide whether to send multiple PRACH repetitions using the same beam based on Example 1.

[0386] If the UE sent multiple PRACH repetitions with higher priority within any previous X (consecutive) RACH attempts within the RACH process and the RACH attempt failed, and the UE sent multiple PRACH repetitions with lower priority within any previous Y (consecutive) RACH attempts within the RACH process and the RACH attempt failed, the UE may also send multiple PRACH repetitions using the same beam and different multiple beams.

[0387] [[Operation D]]

[0388] The UE may also decide whether to send multiple PRACH iterations using the same beam or different beams within the RACH attempt.

[0389] When the priority of PRACH repetitions using the same beam is higher than the priority of PRACH repetitions using different multiple beams, and the UE has failed to send multiple PRACH repetitions using the same beam in a previous RACH attempt, the UE may also decide whether to send multiple PRACH repetitions using different multiple beams based on Example 2. In this case, the UE may also follow at least one of the following operations D-1 and D-2.

[0390] [[[Operation D-1]]]

[0391] When it is determined that multiple PRACH repetitions using different beams are transmitted, the UE transmits multiple PRACH repetitions using the same beam and different beams. Otherwise, the UE transmits multiple PRACH repetitions using the same beam.

[0392] [[[Operation D-2]]]

[0393] When it is determined that a plurality of PRACH repetitions using different beams are transmitted, the UE transmits a plurality of PRACH repetitions using the same beam and different beams. Otherwise, the UE transmits PRACH without repetitions.

[0394] When the priority of PRACH repetitions using different multiple beams is higher than the priority of PRACH repetitions using the same beam, and the UE has failed to send multiple PRACH repetitions using different multiple beams in a previous RACH attempt, the UE may also decide whether to send multiple PRACH repetitions using the same beam based on Example 1. In this case, the UE may also perform at least one of the following operations D-3 and D-4.

[0395] [[[Operation D-3]]]

[0396] When it is determined that multiple PRACH repetitions using the same beam are transmitted, the UE transmits multiple PRACH repetitions using the same beam and multiple different beams. Otherwise, the UE transmits multiple PRACH repetitions using multiple different beams.

[0397] [[[Operation D-4]]]

[0398] When it is determined that a plurality of PRACH repetitions using the same beam are transmitted, the UE transmits a plurality of PRACH repetitions using the same beam and a plurality of different beams. Otherwise, the UE transmits PRACH without repetitions.

[0399] If the UE sent multiple PRACH repetitions with higher priority within any previous X (consecutive) RACH attempts within the RACH process and the RACH attempt failed, and the UE sent multiple PRACH repetitions with lower priority within any previous Y (consecutive) RACH attempts within the RACH process and the RACH attempt failed, the UE may also send multiple PRACH repetitions using the same beam and different multiple beams.

[0400] A specific example of operation A / C is shown below.

[0401] exist Figure 6 In the example, the priority of PRACH repetitions using the same beam is higher than the priority of PRACH repetitions using different multiple beams, and the UE sent multiple PRACH repetitions using the same beam in the previous RACH attempt and the RAR reception failed. The UE may also send multiple PRACH repetitions using different multiple beams in the next RACH attempt.

[0402] exist Figure 7 In the example of , further, in the second RACH attempt, the reception of the RAR fails. The UE may also send multiple PRACH repetitions using the same beam and different multiple beams in the next RACH attempt.

[0403] exist Figure 8 In the example, the priority of PRACH repetitions using different multiple beams is higher than the priority of PRACH repetitions using the same beam, and the UE sent multiple PRACH repetitions using different multiple beams in the previous RACH attempt and RAR reception failed. The UE may also send multiple PRACH repetitions using the same beam in the next RACH attempt.

[0404] exist Fig. 9 In the example of , further, in the second RACH attempt, the reception of the RAR fails. The UE may also send multiple PRACH repetitions using the same beam and different multiple beams in the next RACH attempt.

[0405] A specific example of the operation B / D is shown below.

[0406] exist Fig.10 In the example, the priority of PRACH repetitions using the same beam is higher than the priority of PRACH repetitions using different multiple beams, and the UE sent multiple PRACH repetitions using the same beam in the previous RACH attempt and the RAR reception failed. The UE may also send multiple PRACH repetitions using the same beam and different multiple beams in the next RACH attempt.

[0407] exist Fig.11 In the example, the priority of PRACH repetitions using different multiple beams is higher than the priority of PRACH repetitions using the same beam, and the UE sent multiple PRACH repetitions using different multiple beams in the previous RACH attempt and RAR reception failed. The UE may also send multiple PRACH repetitions using the same beam and different multiple beams in the next RACH attempt.

[0408] [Options 4-9]

[0409] The transmission method may also be based on the UE capability of the beam correspondence.

[0410] In the case where the UE does not have / does not report the capability of beam correspondence, the UE may also send PRACH repetitions using different multiple beams. The UE may also decide whether to send PRACH repetitions using the same beam based on Example 1 (for each of the different multiple beams). In the case where it is decided to send PRACH repetitions using the same beam, the UE may also send PRACH repetitions using the same beam and different multiple beams. In the case where it is decided not to send PRACH repetitions using the same beam, the UE may also send PRACH repetitions using different multiple beams.

[0411] In the case where the UE has / reports the capability of beam correspondence, the UE may also decide whether to send PRACH without repetition or send PRACH repetition using the same beam based on Example 1. In the case where it is decided to send PRACH repetition using the same beam, the UE may also send PRACH repetition using the same beam and different multiple beams. In the case where it is decided not to send PRACH repetition using the same beam, the UE may also send PRACH without repetition.

[0412] A combination of at least two of options 4-1 to 4-9 may also be used.

[0413] According to this embodiment, the UE can appropriately determine the PRACH transmission method. In addition, when performing multiple iterations, the UE can appropriately determine the beams used for the multiple iterations.

[0414] <Supplement>

[0415] During the random access procedure for initial access, the UE may also use different multiple beams for multiple repetitions of the PRACH.

[0416] When RSRP is below the threshold, the UE may also use the same beam for multiple repetitions of PRACH.

[0417] [Notification of information to UE]

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

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

[0420] In the case where the above notification is performed through DCI, the above notification may also be performed through a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used in scrambling a cyclic redundancy check (CRC) bit assigned to the DCI, the format of the DCI, etc.

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

[0422] [Notification of information from UE]

[0423] The notification of arbitrary information from the UE (to the NW) in the above-mentioned embodiment (in other words, the sending / reporting of arbitrary information from the UE to the BS) may also be performed 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.

[0424] In the case where the above notification is performed through MAC CE, the MAC CE may also be identified by including a new LCID which is not specified in the existing standard in the MAC subheader.

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

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

[0427] [About the application of each embodiment]

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

[0429] At least one of the above-mentioned implementation modes may also be applied only to a UE that reports a specific UE capability (UE capability) or supports the specific UE capability.

[0430] The specific UE capability may also indicate at least one of the following:

[0431] PRACH repetition with the same beam.

[0432] PRACH repetition with different multiple beams.

[0433] PRACH repetition with the same beam and different multiple beams.

[0434] Based on the configuration / instruction by SIB / RRC IE, it is determined whether to transmit the PRACH without repetition or to transmit multiple PRACHs with the same beam / different beams and repetition.

[0435] Priority of PRACH repetitions with the same beam and priority of PRACH repetitions with different multiple beams. This priority may be defined in the specification or may be set / indicated by SIB / RRC IE.

[0436] In addition, the above-mentioned specific UE capabilities can be capabilities that are applied across all frequencies (commonly regardless of 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 1 (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 feature set per component carrier (Feature Set Per Component-carrier (FSPC)).

[0437] Furthermore, the specific UE capability may be a capability applied across 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 to a case where specific information associated with the above-mentioned embodiments (or the operation of the above-mentioned embodiments) is set / activated / triggered by the UE through high-layer signaling / physical layer signaling. For example, the specific information may also be information indicating activation of the functions of each embodiment, any RRC parameter for a specific version (e.g., Rel.18 / 19), etc.

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

[0440] (Note)

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

[0442] [Note 1]

[0443] A terminal having:

[0444] a control unit, determining a transmission method among a first transmission method of transmitting a physical random access channel (PRACH) without a plurality of repetitions, a second transmission method of transmitting the plurality of repetitions using the same beam, a third transmission method of transmitting the plurality of repetitions using different beams, and a fourth transmission method of transmitting the plurality of repetitions using the same beam and different beams; and

[0445] The sending unit uses the sending method to send more than one PRACH.

[0446] [Note 2]

[0447] A terminal as described in Note 1, wherein the control unit determines the transmission mode based on at least one of the following: an indication of the transmission mode, a triggering method of a random access process, a purpose of the random access process, a setting of the PRACH, a transmission counter of the PRACH, restricted parameters of the random access process, a synchronization signal block and a channel state information reference signal receiving power, a priority of at least one of the second transmission mode and the third transmission mode, capability information related to beam correspondence, a network type, a duplex mode, and a frequency range.

[0448] [Note 3]

[0449] A terminal as described in Note 1 or Note 2, wherein the control unit does not report both the ability to repeatedly use the same beam for the multiple repetitions and the ability to repeatedly use different multiple beams for the multiple repetitions, or does not assume both the use of the same beam for the multiple repetitions and the use of different multiple beams for the multiple repetitions, or does not apply both the same beam and different multiple beams within a random access channel attempt.

[0450] [Note 4]

[0451] A terminal as described in any one of Notes 1 to 3, wherein the control unit applies both the same beam and different multiple beams within one random access channel attempt.

[0452] (Wireless Communication System)

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

[0454] 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 through Long Term Evolution (LTE) standardized by the Third Generation Partnership Project (3GPP), the fifth generation mobile communication system New Radio (5GNR), or the like.

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

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

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

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

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

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

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

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

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

[0464] The core network 30 may also include 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 a DN.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0480] (Base Station)

[0481] Fig.13 1 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0494] 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, 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.

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

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

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

[0498] The control unit 110 may also determine a transmission method among a first transmission method of transmitting a physical random access channel (PRACH) without multiple repetitions, a second transmission method of transmitting the multiple repetitions using the same beam, a third transmission method of transmitting the multiple repetitions using different beams, and a fourth transmission method of transmitting the multiple repetitions using the same beam and different beams. The transmitting and receiving unit 120 may also receive more than one PRACH using the transmission method.

[0499] (User terminal)

[0500] Fig.142 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.

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

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

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

[0504] 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 explained based on the common knowledge in the technical field involved in the present disclosure.

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

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

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

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

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

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

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

[0512] The transmitting and receiving unit 220 (RF unit 222 ) 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 230 .

[0513] On the other hand, the transmission and reception unit 220 (RF unit 222 ) may 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 230 .

[0514] 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, 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.

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

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

[0517] The control unit 210 may also determine a transmission method among a first transmission method of transmitting a physical random access channel (PRACH) without multiple repetitions, a second transmission method of transmitting the multiple repetitions using the same beam, a third transmission method of transmitting the multiple repetitions using different beams, and a fourth transmission method of transmitting the multiple repetitions using the same beam and different beams. The transmitting and receiving unit 220 may also use the transmission method to transmit more than one PRACH.

[0518] The control unit 210 may also determine the transmission mode based on at least one of the following: an indication of the transmission mode, a triggering method of the random access process, the purpose of the random access process, the setting of the PRACH, a transmission counter of the PRACH, restricted parameters of the random access process, the receiving power of the synchronization signal block and the channel state information reference signal, the priority of at least one of the second transmission mode and the third transmission mode, capability information related to beam correspondence, the type of network, the duplex mode, and the frequency range.

[0519] The control unit 210 may also not report both the ability to repeatedly use the same beam for the multiple transmissions and the ability to repeatedly use different beams for the multiple transmissions, or may not be assumed to be set to repeatedly use the same beam for the multiple transmissions and to repeatedly use different beams for the multiple transmissions, or may not apply both the same beam and different beams within a random access channel attempt.

[0520] The control unit 210 may also apply both the same beam and different multiple beams within one random access channel attempt.

[0521] (Hardware structure)

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

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

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

[0525] In addition, in the present disclosure, the terms such as device, circuit, equipment, section, and unit can be interchanged. The hardware structure 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.

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

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

[0528] 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 above-mentioned control unit 110 (210), the transmission and reception unit 120 (220), etc. may also be implemented by the processor 1001.

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

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

[0531] 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 suitable storage media. The storage 1003 may also be referred to as an auxiliary storage device.

[0532] 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 (FDD) and 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).

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

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

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

[0536] (Variation)

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

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

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

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

[0541] A time slot may also include multiple mini time slots. Each mini time slot may also be composed of one or more symbols in the time domain. In addition, a mini time slot may also be referred to as a sub-time slot. A mini time 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 time slot may also be referred to as a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini time slot may also be referred to as a PDSCH (PUSCH) mapping type B.

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

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

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

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

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

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

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

[0549] Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers (subcarriers) in the frequency domain. The number of subcarriers included in 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.

[0550] In addition, an RB may 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.

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

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

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

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

[0555] At least one of the set BWPs may be activated, and the UE may not assume that it will transmit or receive a specific signal / channel other than the activated BWP. In addition, "cell", "carrier", etc. in the present disclosure may also be rewritten as "BWP".

[0556] 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 in each 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0572] In the present disclosure, a case where a base station sends information to a terminal and a case where the base station instructs the terminal to control / operate based on the information may be mutually replaced.

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

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

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

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

[0577] 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 also includes 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.

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

[0579] 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 steering wheel), and performs steering of 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.

[0580] The electronic control unit 49 may also be 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).

[0581] 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 rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 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.

[0582] The information service unit 59 is composed of various devices such as a car 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, etc. to provide various information / services (for example, multimedia information / multimedia services) to the occupants of the vehicle 40.

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

[0584] 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 device (for example, Global Navigation Satellite System (GNSS)), map information (for example, high-precision (High Definition (HD)) map, autonomous vehicle (Autonomous Vehicle (AV)) map, etc.), gyroscope system (for example, 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 that control 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.

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

[0586] 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 between external devices 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).

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

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

[0589] 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, the various sensors 50-58, etc., which are provided in the vehicle 40 based on the information stored in the memory 62.

[0590] 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 rewritten as 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 of 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.

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

[0592] In the present disclosure, operations are assumed to be performed by a 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 may be performed by a 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.

[0593] The various methods / implementations described in this disclosure may be used individually 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 swapped in order as long as they are not contradictory. For example, for the methods described in this disclosure, the elements of various steps are presented in an illustrative order, but are not limited to the specific order presented.

[0594] 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 expanded, modified, created or specified based on them. In addition, multiple systems can also be combined (for example, LTE or LTE-A, combination with 5G, etc.) for application.

[0595] 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”.

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

[0597] The term "determining" used in the present disclosure may include a variety of operations. 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 regarded as performing "determining".

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

[0599] 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 operations are regarded as "judgment (decision)".

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

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

[0602] 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 can 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 can be physical, logical, or a combination thereof. For example, "connection" can also be rewritten as "access".

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

[0604] 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".

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

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

[0607] In the present disclosure, "below", "less than", "above", "more than", "equal to", etc. may also be rephrased with each other. Furthermore, in the present disclosure, words meaning "good", "bad", "big", "small", "high", "low", "early", "late", "wide", "narrow", etc. may also be rephrased with each other without being limited to the original form, comparative form, and superlative form. Furthermore, in the present disclosure, words meaning "good", "bad", "big", "small", "high", "low", "early", "late", "wide", "narrow", etc. may also be rephrased with each other as expressions to which "ith (i is an arbitrary integer)" is attached without being limited to the original form, comparative form, and superlative form (for example, "highest" may also be rephrased with "i-th highest").

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

[0609] The invention involved in the present disclosure has been 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, determining a transmission method among a first transmission method of transmitting a physical random access channel (PRACH) without multiple repetitions, a second transmission method of transmitting the multiple repetitions using the same beam, a third transmission method of transmitting the multiple repetitions using different multiple beams, and a fourth transmission method of transmitting the multiple repetitions using the same beam and different multiple beams; and The sending unit uses the sending method to send more than one PRACH.

2. The terminal according to claim 1, wherein: The control unit determines the transmission mode based on at least one of the following: an indication of the transmission mode, a triggering method of a random access process, a purpose of the random access process, a setting of the PRACH, a transmission counter of the PRACH, restricted parameters of the random access process, a synchronization signal block and a channel state information reference signal receiving power, a priority of at least one of the second transmission mode and the third transmission mode, capability information related to beam correspondence, a network type, a duplex mode, and a frequency range.

3. The terminal according to claim 1, wherein: The control unit does not report both the ability to repeatedly use the same beam for the multiple repetitions and the ability to repeatedly use different multiple beams for the multiple repetitions, or is not assumed to be set to both repeatedly use the same beam for the multiple repetitions and repeatedly use different multiple beams for the multiple repetitions, or does not apply both the same beam and different multiple beams within a random access channel attempt.

4. The terminal according to claim 1, wherein: The control unit applies both the same beam and different multiple beams within one random access channel attempt.

5. A wireless communication method, which is a wireless communication method of a terminal, comprising: The step of determining a transmission method of a first transmission method of transmitting a physical random access channel (PRACH) without multiple repetitions, a second transmission method of transmitting the multiple repetitions using the same beam, a third transmission method of transmitting the multiple repetitions using different multiple beams, and a fourth transmission method of transmitting the multiple repetitions using the same beam and different multiple beams; and The step of sending more than one PRACH using the transmission method.

6. A base station, comprising: a control unit that determines a transmission method among a first transmission method of transmitting a physical random access channel (PRACH) without multiple repetitions, a second transmission method of transmitting the multiple repetitions using the same beam, a third transmission method of transmitting the multiple repetitions using different multiple beams, and a fourth transmission method of transmitting the multiple repetitions using the same beam and different multiple beams; and The receiving unit uses the sending mode to receive more than one PRACH.