Terminal, wireless communication method, and base station

Abstract

The present invention provides a terminal, a wireless communication method, and a base station that improve the coverage of random access procedures. [Solution] In a next-generation mobile communication system, the user terminal includes a transceiver 220 that receives settings for multiple random access channel transmissions, and a control unit 210 that determines, based on the settings, whether a random access channel occasion (RO) for the multiple random access channel transmissions conflicts with at least one of the following resources: a symbol instructed for receiving a synchronization signal block, a symbol set as a downlink or flexible by time division multiplexing settings, a symbol instructed as a downlink or flexible by a slot format indicator, and an effective occasion for single random access channel transmissions.

Description

Technical Field

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

Background Art

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified for the purpose of further high data rates, low latency, etc. (Non-Patent Document 1). Also, for the purpose of further large capacity and sophistication of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9), LTE-Advanced (3GPP Rel. 10-14) was specified.

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

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

[0005] Improvements to coverage are being considered for future wireless communication systems (e.g., NR).

[0006] However, the random access procedure for improving coverage is not clear. Without such a clear random access procedure, there is a risk of reduced communication throughput.

[0007] Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that improve the coverage of random access procedures. [Means for solving the problem]

[0008] A terminal according to one aspect of the present disclosure includes a receiving unit that receives a setting for multiple random access channel transmissions, and a control unit that determines, based on the setting, whether a random access channel occasion (RO) for the multiple random access channel transmissions conflicts with at least one of the following resources: a symbol instructed for receiving a synchronization signal block, a symbol set as a downlink or flexible by time division multiplexing settings, a symbol instructed as a downlink or flexible by a slot format indicator, and a valid occasion for single random access channel transmissions. [Effects of the Invention]

[0009] According to one aspect of this disclosure, coverage of random access procedures can be improved. [Brief explanation of the drawing]

[0010] [Figure 1] Figure 1 shows an example of RACH configuration information elements. [Figure 2] Figures 2A and 2B show an example of the association between PRACH occasions and beams. [Figure 3]Figure 3 shows an example of a RAR window. [Figure 4] Figure 4 shows an example of an RO group. [Figure 5] Figure 5 shows an example of a RA-RNTI collision. [Figure 6] Figure 6 shows an example of Case 1 of RO / RA-RNTI collisions in multiple iterations of PRACH. [Figure 7] Figure 7 shows an example of case 2 of RO / RA-RNTI collisions in multiple iterations of PRACH. [Figure 8] Figure 8 shows an example of a collision between an RO within an RO group for multiple PRACH transmissions and a specific resource. [Figure 9] Figure 9 shows an example of a unique RO (Robot Operandi). [Figure 10] Figure 10 shows an example of a schematic configuration of a wireless communication system according to one embodiment. [Figure 11] Figure 11 shows an example of the configuration of a base station according to one embodiment. [Figure 12] Figure 12 shows an example of the configuration of a user terminal according to one embodiment. [Figure 13] Figure 13 shows an example of the hardware configuration of a base station and a user terminal according to one embodiment. [Figure 14] Figure 14 shows an example of a vehicle according to one embodiment. [Modes for carrying out the invention]

[0011] (TCI, spatial relations, QCL) In NR, it is being considered to control the receive processing (e.g., at least one of receive, demapping, demodulation, and decoding) and transmit processing (e.g., transmit, mapping, precoding, modulation, and encoding) of at least one of the signal and channel (referred to as signal / channel) at the UE based on the Transmission Configuration Indication state (TCI state).

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

[0013] TCI status refers to information about signal / channel quasi-co-location (QCL), and may also be called spatial reception parameters or spatial relation information. TCI status may be set for each channel or signal in the UE.

[0014] QCL is an index that indicates the statistical properties of a signal / channel. For example, if two signals / channels have a QCL relationship, it may mean that we can assume that at least one of the following is identical between these different signals / channels: Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter).

[0015] The spatial reception parameters may correspond to the UE's received beam (e.g., the received analog beam), and the beam may be identified based on the spatial QCL. In this disclosure, QCL (or at least one element of QCL) may be interpreted as sQCL (spatial QCL).

[0016] QCL may have multiple types (QCL types). For example, there may be four QCL types A and D that differ in the parameters (or parameter sets) that can be assumed to be the same, and these parameters (which may also be called QCL parameters) are shown below: • QCL Type A (QCL-A): Doppler shift, Doppler spread, mean delay and delay spread, • QCL Type B (QCL-B): Doppler shift and Doppler spread, • QCL Type C (QCL-C): Doppler shift and mean delay, • QCL Type D (QCL-D): Spatial reception parameters.

[0017] The assumption by the UE that one control resource set (CORESET), channel, or reference signal is in a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be called a QCL assumption.

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

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

[0020] Physical layer signaling may include, for example, Downlink Control Information (DCI).

[0021] The channel on which the TCI state or spatial relationship is set (specified) may be, for example, at least one of the following: Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), Physical Uplink Shared Channel (PUSCH), or Physical Uplink Control Channel (PUCCH).

[0022] Furthermore, the RS that has a QCL relationship with the channel may be at least one of the following: a Synchronization Signal Block (SSB), a Channel State Information Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), a Tracking CSI-RS (also called a Tracking Reference Signal (TRS)), or a QCL detection reference signal (also called a QRS).

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

[0024] The RS of a QCL type X in a TCI state may also mean the RS in the relationship between a channel / signal (or its DMRS) and a QCL type X, and this RS may also be called the QCL source of the QCL type X in that TCI state.

[0025] (Initial access procedure) In the initial access procedure, the UE (RRC_IDLE mode) receives the SS / PBCH block (SSB), sends Msg.1 (PRACH / Random Access Preamble / Preamble), receives Msg.2 (PDCCH, PDSCH including Random Access Response (RAR)), sends Msg.3 (PUSCH scheduled by the RAR UL grant), and receives Msg.4 (PDCCH, PDSCH including UE contention resolution identity). Subsequently, when the base station (network) sends an ACK to Msg.4 from the UE, the RRC connection is established (RRC_CONNECTED mode).

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

[0027] SSB has a bandwidth of 20 RB and a duration of 4 symbols. The transmission period for SSB can be set from {5, 10, 20, 40, 80, 160} ms. Within a half frame, multiple symbol positions for SSB are defined based on the frequency range (FR1, FR2).

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

[0029] System information consists of MIBs carried by PBCH, RMSI (SIB1), and other system information (OSI). SIB1 contains information for RACH configuration and RACH procedures. The time / frequency resource relationship between SSB and PDCCH monitoring resources for SIB1 is set by PBCH.

[0030] A base station using beam correspondence transmits multiple SSBs using multiple beams during each SSB transmission cycle. Each of the multiple SSBs has multiple SSB indices. When a UE detects one SSB, it transmits a PRACH in the RACH occasion associated with that SSB index and receives a RAR in the RAR window.

[0031] (Beam and coverage) In the high-frequency band, if beamforming is not applied to the synchronization / reference signal, coverage will be narrow, making it difficult for the UE to find the base station. On the other hand, if beamforming is applied to the synchronization / reference signal to ensure coverage, a strong signal will reach in certain directions, but the signal will be even weaker in other directions. If the direction of the UE is unknown at the base station before the UE connects, it is impossible to transmit the synchronization / reference signal using a beam directed only in the correct direction. One possible solution is for the base station to transmit multiple synchronization / reference signals, each with a beam directed in a different direction, and for the UE to recognize which beam it has detected. Using a narrow beam for coverage requires transmitting many synchronization / reference signals, which increases overhead and may reduce frequency utilization efficiency.

[0032] Using wider beams (wider beams) to reduce overhead by decreasing the number of beams (synchronization / reference signals) results in narrower coverage.

[0033] In future wireless communication systems (e.g., 6G), the use of frequency bands such as millimeter waves and terahertz waves is expected to increase further. It is conceivable that communication services could be provided by constructing cell area / coverage using numerous narrow beams.

[0034] Possible approaches include expanding the area using existing FR2 beams and utilizing higher frequency bands than existing FR2 beams. To achieve these goals, improvements in beam management are preferable, in addition to multi-TRP and reconfigurable intelligent surface (RIS) systems.

[0035] PRACH coverage extensions are being considered. For example, multiple PRACH transmissions using the same beam in a 4-step RACH procedure (multiple PRACH repetitions) and multiple PRACH transmissions using different beams in a 4-step RACH procedure are being considered. These PRACH extensions may target frequency range (FR) 2 or be applied to FR 1. These PRACH extensions may be applied to short PRACH formats or other formats.

[0036] For multiple PRACH transmissions involving the same beam, one RAR window may be used for each PRACH transmission. This RAR window may follow an existing design. Alternatively, for multiple PRACH transmissions involving the same beam, only one RAR window may be used for all of the multiple PRACH transmissions.

[0037] A UE may use different multiple transmit (Tx) beams to transmit multiple PRACHs across multiple ROs associated with the same SSB / CSI-RS.

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

[0039] For a Type 1 random access procedure (a 4-step random access procedure, messages 1 / 2 / 3 / 4), the UE may apply the number of SS / PBCH blocks N associated with a single PRACH occasion and the number of CB preambles R per valid PRACH occasion and per SS / PBCH block using ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

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

[0041] Starting from frame 0, the association period for mapping SS / PBCH blocks to PRACH occasions is N Tx SSB The minimum value in a set determined by the PRACH configuration period, according to the relationship between the PRACH configuration period and the number of PRACH configuration periods (the relationship defined in the specification), such that the number of SS / PBCH block indexes maps to a PRACH occasion at least once within its association period. Here, UE is the minimum value in a set determined by the PRACH configuration period, according to the relationship between the PRACH configuration period and the association period (the number of PRACH configuration periods) (the relationship defined in the specification), such that the number of SS / PBCH block indexes maps to a PRACH occasion at least once within its association period. Tx SSBObtained. If, after an integer number of mapping cycles from SS / PBCH block index to PRACH occasion within the association period, N Tx SSB If there is a set of PRACH occasions or PRACH preambles that do not map to any SS / PBCH block index, then no SS / PBCH block index will map to that set of PRACH occasions or PRACH preambles. The association pattern period is determined to include one or more association periods, such that the pattern between the PRACH occasion and the SS / PBCH block index repeats at most every 160ms. If, after an integer number of association periods, there is a PRACH occasion that is not associated with an SS / PBCH block index, then that PRACH occasion is not used for PRACH.

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

[0043] PRACH occasions are mapped sequentially for each corresponding SS / PBCH block index. The indexing of PRACH occasions, indicated by the mask index value, is reset for each SS / PBCH block index and for each consecutive PRACH occasion mapping cycle. In the first available mapping cycle, the UE selects the PRACH occasion indicated by the PRACH mask index value for the specified SS / PBCH block index for PRACH transmission.

[0044] For the specified preamble index, the order of the PRACH occasions is as follows: • Firstly, the frequency resource index increases in order of frequency multiplexed PRACH occasions. Secondly, the time resource index increases for time-multiplexed PRACH occasions within the PRACH slot. Thirdly, the PRACH slot index is in ascending order.

[0045] For PRACH transmissions triggered by requests from higher layers, if csirs-ResourceList is provided, the value of ra-OccasionList indicates a list of PRACH occasions for the PRACH transmission, and the PRACH occasions are associated with the CSI-RS index indicated and selected by csi-RS. The indexing of PRACH occasions indicated by ra-OccasionList is reset for each association pattern period.

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

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

[0048] Figure 2A shows an example of the association between PRACH occasions (RACH occasions (RO)) and beams (SSB / CSI-RS) based on the upper layer parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB (Mapping 1). When ssb-perRACH-OccasionAndCB-PreamblesPerSSB is oneHalf,n16 (N=1 / 2, R=16) and msg1-FDM is 4, four ROs are FDM'd in one time instance, and one SSB is mapped to two ROs. Preamble indices 0 to 15 are associated with the two ROs, and preamble indices 0 to 15 are associated with SSB0. Thus, when N<1, one SSB is mapped to multiple ROs. This increases the RO capacity per beam.

[0049] Figure 2B shows another example of RO-beam association (Mapping 2) based on the higher-layer parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB. When ssb-perRACH-OccasionAndCB-PreamblesPerSSB shows n4,n16 (N=4, R=16), msg1-FDM is 4, and N_preamble^total is 64, then four ROs are FDM'd in one time instance, and four SSBs are mapped to one RO. One RO is associated with SSB#0 to #3. Preamble indices #0 to #15 are associated with SSB#0, preamble indices #16 to #31 are associated with SSB#1, preamble indices #32 to #47 are associated with SSB#2, and preamble indices #48 to #63 are associated with SSB#3. Thus, the same RO is associated with different SS / PBCH block indices, and different preambles use different SS / PBCH block indices. The base station can distinguish the associated SS / PBCH block indices based on the received PRACH.

[0050] The random access preamble can only be transmitted over time resources specified in the random access configuration of the specification, and depends 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 upper layer parameter prach-ConfigurationIndex, or by msgA-PRACH-ConfigurationIndex, if set. In the specification, each value of the PRACH configuration index is associated with at least one of the following: preamble format, x and y in n_f (frame number) mod x = y, subframe number, start symbol, number of PRACH slots in the subframe, number of time domain PRACH occasions N_t^RA,slot in the PRACH slot, and PRACH duration N_dur^RA.

[0051] Whether a PRACH iteration can be applied to a scenario depends on the type of RACH procedure triggered by different purposes. The type of RACH procedure may be at least one of the following: Contention-free random access (CFRA), PDCCH ordered RA (RA initiated by a PDCCH order), CFRA for beam failure recovery (BFR), CFRA for system information (SI) requests, CFRA for reconfiguration with sync, etc. Contention-based random access (CBRA), RAs triggered by MAC entities, RAs triggered by RRCs with events, CBRAs for BFRs, etc. • 4-step RACH. • 2-step RACH.

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

[0053] For PRACH transmissions triggered by a PDCCH order, the PRACH mask index field indicates the PRACH occasion of the PRACH transmission associated with the SS / PBCH block index indicated by the SS / PBCH block index field of the PDCCH order, provided the value of the random access preamble index field is non-zero.

[0054] (Random Access procedure initialization in MAC entities (MAC protocol specification)) Random access procedures are initiated by a PDCCH order, the MAC entity itself, or an RRC for a specification-compliant event. Within a MAC entity, there is only one random access procedure in progress at any given time. Random access procedures for SCells are initiated only by a PDCCH order with a ra-PreambleIndex different from 0b000000.

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

[0056] If the selected RA_TYPE is set to 4-stepRA, the MAC entity does the following: If ra-PreambleIndex is explicitly provided by PDCCH and ra-PreambleIndex is not 0b000000, set PREAMBLE_INDEX to the notified ra-PreambleIndex and select the SSB notified by PDCCH. • If an SSB is selected as described above, the MAC entity determines the next available PRACH occasion from the PRACH occasions that are permitted by the limitations given by ra-ssb-OccasionMaskIndex and that correspond to the selected SSB (the MAC entity randomly selects a PRACH occasion with equal probability from consecutive PRACH occasions corresponding to the selected SSB, in accordance with the specification. When the MAC entity determines the next available PRACH occasion corresponding to the selected SSB, it may consider the possibility of a measurement gap occurring).

[0057] (Time between PDCCH order reception and PRACH transmission) If a random access procedure is initiated by a PDCCH order, the UE will, if requested by a higher layer, transmit a PRACH within a selected PRACH occasion, provided that the time between the last symbol of the PDCCH order reception and the first symbol of the PRACH transmission is greater than or equal to N_(T,2)+Δ_BWPSwitching+Δ_Delay+T_switch[msec] (time condition), as described in the specification, where N_(T,2) is the duration of N_2 symbols corresponding to the PUSCH preparation time for UE processing capability 1. μ is assumed to correspond to the minimum SCS setting between the subcarrier spacing (SCS) setting of the PDCCH order and the corresponding SCS setting for the PRACH transmission. If the active UL BWP does not change, Δ_BWPSwitching=0; otherwise, Δ_BWPSwitching is defined in the specification. Δ_delay=0.5msec at FR1 and Δ_delay=0.25msec at FR2. T_switch is the switching gap duration defined in the specification.

[0058] (Conditions for valid / invalid PRACH occasions (valid conditions)) In the paired spectrum (FDD) or SUL band, all PRACH occasions are valid. In the unpaired spectrum (TDD), PRACH occasions may follow provisions 1 and 2 below. [Regulation 1] If the UE does not provide tdd-UL-DL-ConfigurationCommon, a PRACH occasion in a PRACH slot is valid if it does not precede an SS / PBCH block in the PRACH slot and begins at least N_gap symbols after the last SS / PBCH block received symbol, where N_gap is defined in the specification. If channelAccessMode=semistatic is provided, it does not overlap with a set of consecutive symbols before the start of the next channel occupancy time that the UE does not transmit. Candidate SS / PBCH block indices correspond to SS / PBCH block indices provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon. [Regulation 2] If the UE is providing tdd-UL-DL-ConfigurationCommon, the PRACH occasions within the PRACH slot are valid in the following cases: • The PRACH occasion is within the UL symbol. Or, The PRACH occasion does not precede an SS / PBCH block in the PRACH slot, and begins at least N_gap symbols after the last DL symbol and at least N_gap symbols after the last SS / PBCH block symbol, where N_gap is defined in the specification. If channelAccessMode=semistatic is provided, the PRACH occasion does not overlap with a consecutive set of symbols before the start of the next channel occupancy time, which should not have any transmissions, as described in the specification. Candidate SS / PBCH block indices for SS / PBCH blocks correspond to SS / PBCH block indices provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon, as described in the specification.

[0059] (RAR window) The RA Response Window (ra-ResponseWindow) is a time window for monitoring the RA Response (RAR) (special cell (SpCell) only). The RA Contention Resolution Timer (ra-ContentionResolutionTimer) is a timer for RA conflict resolution (SpCell only). The Msg.B Response Window is a time window for monitoring the RA Response (RAR) for 2-step RA types (SpCell only).

[0060] In this disclosure, SpCell, primary cell (PCell), and primary secondary cell (PSCell) may be interpreted as interchangeable.

[0061] When the RA preamble is sent, the MAC entity performs actions 1 through 3 below, regardless of the possibility of a measurement gap occurring.

[0062] [Operation 1] If a contention-free RA preamble for a BFR request is sent by that MAC entity, that MAC entity performs the following actions 1-1 and 1-2: [[Action 1-1]] The MAC entity initiates the ra-ResponseWindow configured in the BFR setting (BeamFailureRecoveryConfig) during the first PDCCH occasion following the end of the RA preamble transmission. [[Operation 1-2]] The MAC entity monitors PDCCH transmissions in the search space indicated by the BFR search space ID (recoverySearchSpaceId) of the SpCell identified by C-RNTI while the ra-ResponseWindow is running.

[0063] [Operation 2] Otherwise, the MAC entity performs actions 2-1 and 2-2 below. [[Operation 2-1]] The MAC entity initiates the ra-ResponseWindow configured in the Common RACH Configuration (RACH-ConfigCommon) during the first PDCCH occasion following the end of the RA preamble transmission. [[Operation 2-2]] The MAC entity monitors the PDCCH transmission of SpCells for RAR identified by RA-RNTI while ra-ResponseWindow is running.

[0064] [Operation 3] If the ra-ResponseWindow set in BeamFailureRecoveryConfig expires and a PDCCH transmission on the search space indicated by the recoverySearchSpaceId addressed to C-RNTI is received on the serving cell from which the preamble was sent, or if the ra-ResponseWindow set in RACH-ConfigCommon expires and an RAR containing an RA preamble identifier matching the transmitted preamble index (PREAMBLE_INDEX) is received, the MAC entity considers the RAR reception a failure and increments the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) by 1.

[0065] The MAC entity may stop the ra-ResponseWindow after successfully receiving a RAR containing RA preamble identifiers that match the transmitted PREAMBLE_INDEX (it may stop monitoring for RARs).

[0066] For PDCCH monitoring within the RA response window, there are two cases: PDCCH for the base station's response to the BFR, and PDCCH for the RAR. The following may apply to both cases.

[0067] When an MSGA (Msg.A) preamble is sent, regardless of the possibility of a measurement gap occurring, the MAC entity performs actions 4 through 6 below.

[0068] [Operation 4] The MAC entity initiates a Msg.B response window (msgB-ResponseWindow) within the PDCCH monitoring window defined in the specification.

[0069] The msgB-ResponseWindow may begin at the first symbol of the earliest CORESET in which the UE is configured to receive a PDCCH for a type 1-PDCCH CSS set, which is at least one symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission. The length of the msgB-ResponseWindow may correspond to the SCS for the type 1-PDCCH CSS set.

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

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

[0072] (RA-RNTI(MAC protocol specification:Random Access Preamble transmission)) The RA-RNTI associated with a PRACH occasion in which an RA preamble is sent is calculated as follows: RA-RNTI = 1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

[0073] Here, s_id is the index of the first OFDM symbol in the PRACH occasion (0 <= s_id < 14 (number of symbols in the slot)). t_id is the index of the first slot of the PRACH occasion in the system frame (0 <= t_id < 80 (number of slots in the system frame when SCS is 120 kHz)). The subcarrier spacing (SCS) for determining t_id is based on the value of μ. f_id is the index of the PRACH occasion in the frequency domain (0 <= f_id < 8 (maximum number of PRACH occasions to be FDM'd)). ul_carrier_id is the UL carrier used for RA preamble transmission (0 for normal uplink (NUL) carriers, 1 for supplementary uplink (SUL) carriers). RA-RNTI is calculated according to the specification. RA-RNTI is the RNTI for 4-step RACH.

[0074] The MSGB-RNTI associated with a PRACH occasion in which an RA preamble is sent is calculated as follows: MSGB-RNTI = 1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2

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

[0076] The total number of RA-RNTI values ​​(the total number of PRACH occasions in the system frame) is 14 × 80 × 8 × 2. The formula for MSGB-RNTI is obtained by adding the total number of RA-RNTI values ​​to the formula for RA-RNTI. This formula helps to avoid collisions between MSGB-RNTI and RA-RNTI.

[0077] (RAR monitoring) In response to a PRACH transmission, the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI within a window controlled by the aforementioned higher layer. The window begins at the first symbol of the earliest CORESET in which the UE is configured to receive a PDCCH for a type 1-PDCCH CSS set, i.e., at least one symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission. The symbol duration corresponds to the SCS for a type 1-PDCCH CSS set. The length of the window is provided as a number of slots by the ra-responseWindow, based on the SCS for a type 1-PDCCH CSS set.

[0078] If the UE detects its DCI format 1_0, which includes a CRC scrambled by the corresponding RA-RNTI and the same LSBs in the SFN field within the DCI format as the least significant bits (LSBs) of the system frame number (SFN) from which the UE sent the PRACH, and the UE receives the transport block in the corresponding PDSCH, the UE may assume the same DMRS antenna port QCL properties with respect to the SS / PBCH block or CSI-RS resource that the UE uses to associate the PRACH, regardless of whether the UE is provided with a TCI-State for CORESET to receive the PDCCH with the DCI format 1_0.

[0079] If a UE attempts to detect DCI format 1_0 with scrambled CRC by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order that triggers a CFRA procedure for a SpCell, the UE may assume that the PDCCH containing the DCI format 1_0 and the PDCCH order have the same DMRS antenna port QCL properties. If a UE attempts to detect DCI format 1_0 with scrambled CRC by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order that triggers a CFRA procedure for a secondary cell, the UE may assume that the DMRS antenna port QCL properties of the CORESET associated with the type 1-PDCCH CSS set for receiving the PDCCH containing the DCI format 1_0 are the same.

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

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

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

[0083] (Msg3 PUSCH) The UE transmits a transport block on the PUSCH scheduled by the RAR UL grant in the corresponding RAR message. The UE transmits that PUSCH within slot n + k2+Δ + 2 μ ·K cell,offset where K cell,offset is provided by CellSpecific_Koffset, and if not provided, K cell,offset = 0.

[0084] k2 is a slot offset and is determined based on the row index m + 1 of the allocation table provided by the PUSCH time resource allocation field value m of the RAR UL grant and the PUSCH sub - carrier spacing μPUSCH. Δ is an additional sub - carrier spacing - specific slot delay time value for the first transmission of the PUSCH scheduled by the RAR, is specific to the PUSCH sub - carrier spacing μPUSCH, and is applied in addition to K2.

[0085] If the UE requests repetition for PUSCH transmission, the UE shall NPUSCH repeat Send a PUSCH across N slots. PUSCH repeat This is indicated by the 2MSB of the MCS field in the RAR UL grant or DCI format 0_0, from the set of four values ​​provided by numberOfMsg3Repetitions, or from {1,2,3,4} if numberOfMsg3Repetitions is not provided.

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

[0087] The UE can request a Msg3PUSCH iteration via a separate PRACH resource. The MAC entity selects an RA resource if there is one or more sets of available RA resources and one of those sets is used to instruct all the functions that trigger this RA procedure, or if there is one or more sets of available RA resources to which instructions are set for a subset of all the functions that trigger this RA procedure. If a Msg3 iteration instruction is set for a set of RA resources and the Msg3 iteration is not available, the MAC entity considers that set of RA resources not available for the RACH procedure.

[0088] RA resources may be partitioned for each function. A function may include at least one of the following: Msg3 repetition, reduced capacity (RedCap), small data transmission (SDT), and RAN slicing.

[0089] The following is notified within the SIB1 transmitted by the base station: • The priority of each feature (priority, featurePriorities-r17). This priority is used by the UE to determine which FeatureCombinationPreamble to use when a feature is mapped to more than one FeatureCombinationPreamble. • Additional RO settings. These settings include available functions (which may be associated with multiple functions), RA resources (e.g., preamble indexes), and mask indexes for distinguishing ROs.

[0090] The UE determines which RO to use based on its functionality.

[0091] SIB1 contains ServingCellConfigCommonSIB. It contains UplinkConfigCommonSIB. It contains BWP-UplinkCommon (UL BWP common settings).

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

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

[0094] The PRACH mask index explicitly sets the available ROs. Using the relationship between the PRACH mask index and the permitted PRACH occasions (ROs) of the SSB (MAC protocol specification / table of PRACH mask index values), at least one of the PRACH occasion indexes from 1 to 8 can be set.

[0095] The number of Msg3 iterations is indicated by the two most significant bits (MSB) (upper two bits) of the modulation and coding scheme (MCS) field in the RAR UL grant.

[0096] In PUSCH repetition type A, when a PUSCH scheduled by a RAR UL grant is transmitted, the 2MSB of the MCS information field of that RAR UL grant provides a code point for determining the number of repetitions K, based on whether or not the upper layer parameter numberOfMsg3Repetitions is set, according to the relationship (table) between the value of the 2MSB of the MCS information field (code point) and the number of repetitions K. The number of slots N used to determine the transport block size (TBS) is equal to 1.

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

[0098] (Contention resolution) When Msg3 is sent, the MAC entity follows actions 1 through 4 below. [Action 1] If Msg3 is transmitted over a non-terrestrial network, the MAC entity starts the ra-ContentionResolutionTimer and restarts it on each HARQ retransmission in the first symbol after the UE estimation of the UE-gNB RTT has been added to the end of Msg3. [Action 2] Otherwise, if the Msg3 transmission (initial or HARQ retransmission) is scheduled with a type A PUSCH repetition, the MAC entity starts or restarts the ra-ContentionResolutionTimer in the first symbol after the end of all repetitions of the Msg3 transmission. [Action 3] Otherwise, the MAC entity starts or restarts the ra-ContentionResolutionTimer in the first symbol after the end of its Msg3 transmission. [Action 4] The MAC entity monitors the PDCCH regardless of the possibility of a measurement gap occurring while the ra-ContentionResolutionTimer is running.

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

[0100] [Step 4 Action] If the UE is not provided with a C-RNTI, in response to a PUSCH transmission scheduled by the RAR UL grant, the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding TCI-RNTI, by scheduling a PDSCH containing the UE contention resolution identity. Upon receiving the PDSCH containing the UE contention resolution identity, the UE transmits HARQ-ACK information within the PUCCH. The PUCCH transmission is within the same active UL BWP as the PUSCH transmission. The minimum time between the last symbol of the PDSCH reception and the first symbol of the corresponding PUCCH transmission containing HARQ-ACK information is equal to N_T,1 [msec], where N_T,1 is the duration of the N_T,1 symbol, corresponding to the PDSCH processing time for UE processing capability 1 if an additional PDSCH DM-RS is configured. For μ=0, the UE assumes N_T,1=14.

[0101] When a DCI format is detected in response to a PUSCH transmission scheduled by a RAR UL grant, or in response to a corresponding PUSCH retransmission scheduled by DCI format 0_0 with a CRC scrambled by TC-RNTI provided in the corresponding RAR message, the UE may assume that the PDCCH carrying that DCI format has the same DM-RS antenna port quasi co-location (QCL) properties as the DM-RS antenna port quasi co-location (QCL) properties for the SS / PBCH block used by the UE for PRACH association.

[0102] (SSB / CSI-RS selection (MAC protocol specification:Random Access Resource selection)) If the RA type (RA_TYPE) is set to 4-step RA (4-stepRA), the MAC entity performs the following actions: - If an RA procedure is initiated for SpCell beam fault recovery, and the beamFailureRecoveryTimer is running or not set, and a CFRA resource for the beam fault recovery request associated with at least one SSB / CSI-RS is explicitly provided by the RRC, and at least one of the multiple SSBs in the candidateBeamRSList with an SS-RSRP exceeding the rsrp-ThresholdSSB threshold, and one or more of the multiple CSI-RSs in the candidateBeamRSList with a CSI-RSRP exceeding the rsrp-ThresholdCSI-RS threshold, then the MAC entity performs the following actions: -- The MAC entity selects one SSB from among multiple SSBs in candidateBeamRSList that has an SS-RSRP exceeding rsrp-ThresholdSSB, or one CSI-RS from among multiple CSI-RSs in candidateBeamRSList that has a CSI-RSRP exceeding rsrp-ThresholdCSI-RS. -- If a CSI-RS is selected and there is an associated RA preamble index (ra-PreambleIndex) for the selected CSI-RS, the MAC entity sets the preamble index (PREAMBLE_INDEX) to the ra-PreambleIndex in candidateBeamRSList that corresponds to the selected CSI-RS and the quasi-colocated SSB. -- Otherwise, set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the SSB or CSI-RS selected from the set of RA preambles for beam fault recovery requests.

[0103] - If not, and ra-PreambleIndex is explicitly provided by PDCCH and that ra-PreambleIndex is not 0b000000, the MAC entity sets PREAMBLE_INDEX to the notified ra-PreambleIndex and selects the SSB notified by PDCCH.

[0104] - If not, and a CFRA resource associated with multiple SSBs is explicitly provided within a separate RACH configuration (rach-ConfigDedicated), and at least one SSB with an SS-RSRP exceeding the rsrp-ThresholdSSB is available, the MAC entity selects one of its associated SSBs with an SS-RSRP exceeding the rsrp-ThresholdSSB and sets the PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected SSB.

[0105] - If not, and the CFRA resources associated with multiple CSI-RS are explicitly provided within a separate RACH setting (rach-ConfigDedicated), and at least one of the multiple CSI-RS has a CSI-RSRP exceeding rsrp-ThresholdCSI-RS, then the MAC entity selects one of its associated CSI-RS with a CSI-RSRP exceeding rsrp-ThresholdCSI-RS and sets PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected CSI-RS.

[0106] - If not, and an RA procedure is initiated for an SI request, and an RA resource for the SI request is explicitly provided by the RRC, the MAC entity performs the following actions: -- If at least one SSB with SS-RSRP exceeding rsrp-ThresholdSSB is available, the MAC entity will select the SSB with SS-RSRP exceeding rsrp-ThresholdSSB. -- Otherwise, the MAC entity selects any SSB. -- The MAC entity selects the RA preamble corresponding to the selected SSB from the RA preambles, which are checked according to the RA preamble start index (ra-PreambleStartIndex), and sets PREAMBLE_INDEX to the selected RA preamble.

[0107] - If not (CBRA preamble selection), the MAC entity performs the following actions: -- If at least one SSB with SS-RSRP exceeding rsrp-ThresholdSSB is available, the MAC entity will select the SSB with SS-RSRP exceeding rsrp-ThresholdSSB. -- Otherwise, the MAC entity selects any SSB.

[0108] (Type 2RA procedure) In the MsgA transmission within a Type 2RA procedure (2-step RA procedure), the UE transmits the following pair (Figure 3): - Within a MsgA RACH occasion (RO), one preamble with one preamble index. - One pusher with one pusher resource unit (PRU) within each MsgA pusher occasion (PO) for each MsgA pusher configuration.

[0109] MsgA PRACH has the structure of an MsgA preamble index (code domain resource) within an MsgA RACH occasion (time domain resource / frequency domain resource) (Figure 4).

[0110] MsgA PUSCH has a structure consisting of MsgA PUSCH resource units (code domain resources / spatial domain resources) within MsgA PUSCH occasions (time domain resources / frequency domain resources) within MsgA PUSCH settings (RRC settings).

[0111] Within a MsgA PUSCH occasion (time domain resource / frequency domain resource), multiple PRUs can be multiplexed using DMRS ports / DMRS sequences. Only in CP-OFDM can more than one DMRS sequence be configured.

[0112] (MsgA push occasion in Type 2 RA procedure) MsgA PUSCH Occasion (PO) that overlaps with a valid RO for a Type 1 / 2 RA procedure is an invalid PO.

[0113] A PUSCH occasion is valid if it does not overlap in time and frequency with any valid PRACH occasion associated with a Type 1RA procedure or a Type 2RA procedure. With respect to the ampered spectrum (TDD) and the SS / PBCH block with the index provided by ssb-PositionsInBurst in SIB1 or by ServingCellConfigCommon, the UE follows several behaviors as follows:

[0114] - If the UE does not provide tdd-UL-DL-ConfigurationCommon, and the PUSCH occasion satisfies the following conditions, then the PUSCH occasion is valid. -- That PUSCH occasion precedes the SS / PBCH block within that PUSCH slot, and, -- That PUSCH occasion is at least N from the last SS / PBCH block symbol. gap The PUSCH occasion begins after a symbol, and if channelAccessMode="semiStatic" is provided, that PUSCH occasion does not overlap with a set of consecutive symbols before the start of the next channel occupancy time in which the UE does not transmit. Here, N gap This is provided within the specification table.

[0115] - A PUSCH occasion is valid if the UE is provided with tdd-UL-DL-ConfigurationCommon and the PUSCH occasion meets the following conditions: -- That PUSCH occasion is within the UL symbol, or -- That PUSCH occasion precedes the SS / PBCH block within that PUSCH slot, and, -- That PUSCH occasion is at least N from the last DL symbol. gap After the symbol, and from the last SS / PBCH block symbol, at least N gap The PUSCH occasion begins after a symbol, and if channelAccessMode="semiStatic" is provided, that PUSCH occasion does not overlap with a set of consecutive symbols before the start of the next channel occupancy time in which the UE does not transmit. Here, N gap This is provided within the specification table.

[0116] (PRACH collision (Physical layer procedures for control:Slot configuration)) In operation on a single carrier within an ampered spectrum (TDD), if a UE is configured by a higher layer to transmit SRS, PUCCH, PUSCH, or PRACH within a set of symbols in one slot, and the UE detects a DCI format instructing the UE to receive CSI-RS or PDSCH within a subset of symbols from that set, the UE will perform the following actions: - If the UE does not demonstrate partial cancellation capability, the UE will follow these actions: -- The first symbol in that set of symbols is from the last symbol in the CORESET where the UE detects its DCI format. proc,2If this occurs within a set of symbols, the UE does not expect to cancel the transmission of PUCCH, PUSCH, or PRACH within that set of symbols. Otherwise, the UE cancels the PUCCH, PUSCH, or actual repetition of PUSCH, or the PRACH transmission within that set of symbols. - If the UE exhibits partial cancellation capabilities, the UE will behave as follows: -- The UE is determined by the fact that the first symbol in its set of symbols is from the last symbol in the CORESET from which the UE detects its DCI format. proc,2 It is not expected that the send of PUCCH, PUSCH, or PRACH within a symbol from that set of symbols that occurs within it will be canceled. The UE will cancel the actual repetition of PUCCH, PUSCH, or PUSCH, or the PRACH send, within the remaining symbols from that set of symbols.

[0117] In other words, if a PRACH triggered / configured by a higher layer overlaps with a symbol scheduled for DL ​​reception by DCI, the UE cancels that PRACH.

[0118] In operation on a single carrier within an ampered spectrum (TDD), if a transmission would overlap with any symbol from a set of symbols in a slot instructed to receive a particular SS / PBCH block, the UE shall not transmit PUSCH, PUCCH, or PRACH within that slot, nor shall the UE transmit SRS within that set of symbols in that slot. The particular SS / PBCH block is an SS / PBCH block defined by ssb-PositionsInBurst in SIB1 (SystemInformationBlockType1), or by ssb-PositionsInBurst in ServingCellConfigCommon, or by ssb-PositionsInBurst in SSB-MTCAdditionalPCI associated with a physical cell ID with an active TCI state for PDCCH or PDSCH if the UE has not provided a dl-OrJoint-TCIStateList, or for a set of symbols in a slot corresponding to an SS / PBCH block configured for L1 beam measurement / reporting. If tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is provided to that UE, do not expect that the set of symbols for that slot to be indicated as an uplink by that tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0119] If UE, - Multiple serving cells are configured, and directionalCollisionHandling-r16 = 'enabled' is provided for a set of serving cells within those multiple serving cells, and, - Demonstrates support for the capabilities of half-DuplexTDD-CA-SameSCS-r16, and, - If monitoring PDCCH for DCI format 2_0 detection is not configured on any of the multiple serving cells, the UE will behave as follows: -If a transmission would overlap with any symbol from the set of symbols in a slot that instructs the UE to receive a specific SS / PBCH block in the first of the multiple serving cells, the UE shall not transmit PUSCH, PUCCH, or PRACH in that slot, and the UE shall not transmit SRS in that set of symbols for that slot in that specific cell. The specific SS / PBCH block is an SS / PBCH block that is defined by ssb-PositionsInBurst in SIB1 (SystemInformationBlockType1), or by ssb-PositionsInBurst in ServingCellConfigCommon, or by ssb-PositionsInBurst in SSB-MTCAdditionalPCI associated with a physical cell ID with an active TCI state for PDCCH or PDSCH if the UE has not provided dl-OrJoint-TCIStateList, or for a set of symbols in a slot corresponding to an SS / PBCH block configured for L1 beam measurement / reporting. The specific cell is one of the multiple serving cells that does not have the simultaneous transmit / receive capability indicated by simultaneousRxTxInterBandCA, and is one of the cells corresponding to the same band as the first cell, regardless of the capability indicated by simultaneousRxTxInterBandCA.

[0120] In other words, if a PRACH triggered / configured by a higher layer overlaps with an SSB symbol, the UE will not send that PRACH.

[0121] (PRACH collision (Physical layer procedures for control:UE procedure for determining slot format)) In the set of symbols for a slot that is instructed to be flexible and directed to the UE by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated when tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are provided, or when tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided, or when the UE finds DCI format 2_0 which provides a format for that slot using a slot format value other than 255, the UE shall behave as follows: - If the SFI index field value in DCI format 2_0 indicates that the set of symbols in that slot is flexible, and the UE does not receive a DCI format instructing the UE to receive PDSCH or CSI-RS, or does not receive a DCI format, RAR UL grant, fallback RAR UL grant, or success RAR instructing the UE to transmit PUSCH, PUCCH, PRACH, or SRS within the set of symbols in that slot, the UE will neither transmit nor receive within the set of symbols in that slot.

[0122] In other words, if a PRACH without a PDCCH order overlaps with a symbol that is designated as flexible by the SFI, the UE will not send that PRACH.

[0123] If a UE is configured by a higher layer to transmit SRS, PUCCH, PUSCH, or PRACH within a set of symbols in a slot, and the UE detects DCI format 2_0 with a slot format value other than 255 that indicates a slot format with a subset of symbols from that set of symbols as downlink or flexible, or receives a DCI format that indicates to the UE to receive CSI-RS or PDSCH within a subset of symbols from that set of symbols, then the UE will perform the following actions: - If the UE does not demonstrate partial cancellation capability, the UE will follow these actions: -- The first symbol in that set of symbols is from the last symbol in the CORESET where the UE detects its DCI format. proc,2 If this occurs within a set of symbols, the UE does not expect to cancel the transmission of PUCCH, PUSCH, or PRACH within that set of symbols. Otherwise, the UE cancels the PUCCH, PUSCH, or actual repetition of PUSCH, or the PRACH transmission within that set of symbols. - If the UE exhibits partial cancellation capabilities, the UE will behave as follows: -- The UE is determined by the fact that the first symbol in its set of symbols is from the last symbol in the CORESET from which the UE detects its DCI format. proc,2 It is not expected that the send of PUCCH, PUSCH, or PRACH within a symbol from that set of symbols that occurs within it will be canceled. The UE will cancel the actual repetition of PUCCH, PUSCH, or PUSCH, or the PRACH send, within the remaining symbols from that set of symbols.

[0124] In other words, if a PRACH set by a higher layer overlaps with a symbol that is designated as DL or flexible by the SFI, the UE cancels that PRACH.

[0125] If tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are provided, in the set of symbols for the slots that are directed to the UE as flexible by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated, or if tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided, and the UE has not found a DCI format 2_0 that provides the slot format for that slot, the UE will behave as follows: - If the UE is configured by a higher layer to send SRS, PUCCH, PUSCH, or PRACH, and the UE does not have enableConfiguredUL provided, the UE will behave as follows: -- If the UE does not demonstrate partial cancellation capability, the UE will follow these actions: --- If the first symbol of PUCCH, or PUSCH, or actual repetition of PUSCH, or PRACH is set to monitor PDCCH for DCI format 2_0 from the last symbol of CORESET proc,2 If this occurs within a slot, the UE does not expect to cancel the transmission of PUCCH, PUSCH, or the actual repetition of PUSCH, or PRACH within that slot. Otherwise, the UE cancels the transmission of PUCCH, PUSCH, or the actual repetition of PUSCH, or PRACH within that slot. -- If the UE exhibits partial cancellation capabilities, the UE will behave as follows: --- That UE is set to monitor PDCCH for DCI format 2_0 from the last symbol of CORESET T proc,2 It is not expected that the UE will cancel any PUCCH, PUSCH, or actual repetition of PUSCH, or PRACH transmissions within the symbols from that set of symbols that occur within it. The UE will cancel any PUCCH, PUSCH, or actual repetition of PUSCH, or PRACH transmissions within that slot. The UE will cancel any PUCCH, PUSCH, or actual repetition of PUSCH, or PRACH transmissions within the remaining symbols from that set of symbols.

[0126] In other words, if a PRACH triggered / set by a higher layer overlaps with a semi-statically set flexible symbol, and the UE does not detect DCI format 2_0, the UE will cancel that PRACH.

[0127] (PRACH resource for sending multiple PRACH messages) It is being considered that multiple PRACH transmissions will be transmitted on ROs (separate ROs) that are separate from single PRACH transmissions, and that multi-PRACH transmissions will be transmitted on ROs (shared ROs) that are shared with single PRACH transmissions, using preambles that are separate from single PRACH transmissions.

[0128] To distinguish multiple PRACH transmissions using the same Tx beam from single PRACH transmissions, support is being considered for transmitting multiple PRACH transmissions on separate ROs.

[0129] To distinguish multiple PRACH transmissions using the same Tx beam from single PRACH transmissions, support is being considered for multiple PRACH transmissions to be transmitted using a separate preamble on a shared RO.

[0130] In multiple PRACH transmissions using the same Tx beam, an "RO group" is assumed for at least one of the following: a separate preamble on a shared RO, and multiple PRACH transmissions on separate ROs. - All ROs within a single RO group are associated with one or more of the same SSBs. - A shared RO / preamble means that the RO / preamble is shared with a single PRACH transmission. - Separate RO / preamble means that the RO / preamble is separated from the single PRACH transmission. - Effective ROs are defined in the existing specifications. Effective ROs may also follow the validity conditions of the PRACH occasions described above.

[0131] (RAR monitoring for multiple PRACHs) In multiple PRACH transmissions using the same transmit beam, it is being considered that only a single RAR window should be supported for RAR monitoring of multiple PRACH transmissions within a single RACH attempt.

[0132] The UE repeatedly sends Msg1 on K random access occasions (ROs) / RO resources. The UE then waits for the detection of Msg2 on a configured type 1PDCCH occasion. In this disclosure, the repeated transmission of preambles on K ROs / RO resources may be referred to as an RO group. Figure 3 shows an example of the timing of multi-PRACH transmissions. In this example, the size of the RO group (the number of ROs in the RO group) is K. One RAR window begins after one RO group.

[0133] In this disclosure, an RO group may be defined as consisting of K TDM-processed active ROs, each having a single RO in the frequency domain and the time domain. In other words, once an RO group is selected, the ROs for each PRACH transmission are determined. In the example in Figure 4, when the number of repetitions K=2, the RO group consists of two TDM-processed consecutive ROs.

[0134] (Analysis 1) In RAR monitoring for multiple PRACH transmissions within a single RACH attempt, the starting position of the RAR window and the RA-RNTI for RAR monitoring have not been adequately considered.

[0135] In determining ROs and RO groups, a possible restriction is that a single RO cannot (and is not expected to) be included in multiple RO groups for the same SSB / CSI-RS and the same number of PRACH transmissions. Using this restriction, RA-RNTI calculations based on the first or last PRACH transmission can be considered.

[0136] If there were no such restrictions, RA-RNTI calculations based on the first, last, or each PRACH transmission could lead to RA-RNTI collisions. As shown in the example in Figure 5, if there are no restrictions on ROs within an RO group, there could be an RO group consisting of RO#1, 6, 11, and 13; an RO group consisting of RO#1, 6, 8, and 13; and an RO group consisting of RO#1, 4, 8, and 13.

[0137] In CBRA, multiple PRACHs transmitted from a single RO (from multiple UEs) correspond to a single RN-RNTI. Up to Rel. 17, only one of the multiple PRACHs transmitted from a single RO will trigger the subsequent RA procedure. In this case, the base station cannot distinguish the UEs from the multiple PRACHs when transmitting the RAR. After the exchange of Msg3 and Msg4, the conflict of the multiple PRACHs is resolved.

[0138] In Rel.18's multiple PRACH transmission (multiple repetitions of PRACH), each of the multiple PRACHs transmitted in a single RO may either trigger a subsequent RA procedure or may not trigger one.

[0139] In multiple iterations of PRACH, the likelihood of RO / RA-RNTI collisions increases, and it is possible that PRACH may be misdetected by the base station identifying RA-RNTI. In the case of RO collisions, one RO may be shared among multiple RO groups. In multiple iterations of PRACH, if the last PRACH determines RA-RNTI and multiple RO groups may partially overlap, the last PRACH from UE#A may overlap the following two cases, which could increase the collision probability. - Case 1: Overlap with PRACH from UEs using the same RO group. For example, the RO group used by UE#B is the same as the RO group used by UE#A. In the example in Figure 6, the two PRACH iterations from UE#A and the two PRACH iterations from UE#B use the same RO group (RO#0, RO#1). - Case 2: Overlap with PRACH from UEs using different RO groups. For example, the RO group used by UE#B is different from the RO group used by UE#A. In the example in Figure 7, the two PRACH iterations from UE#A use RO group #0 (RO#1, RO#3). The two PRACH iterations from UE#B use RO group #1 (RO#0, RO#3). If RA-RNTI is calculated based on the last RO of multiple iterations, the same RA-RNTI will be obtained for UE#A and UE#B.

[0140] When RA-RNTI collisions occur in this way, it can lead to a decrease in communication throughput and other problems.

[0141] (Analysis 2) It is being considered that an RO group is a "valid RO(s) for a specific number of multiple PRACH transmissions." In the existing specifications, PRACH transmissions on a valid RO can be canceled.

[0142] The UE's behavior in considering the possibility of collisions between ROs within an RO group for multiple PRACH transmissions has not been adequately considered. For example, whether the UE considers RO collisions when selecting an RO group, or how the UE behaves when the selected RO group contains ROs that will result in collisions, has not been adequately considered. Failure to adequately consider such UE behavior may lead to a decrease in communication throughput.

[0143] Therefore, the inventors conceived of an operation concerning collisions of ROs for multiple PRACH transmissions.

[0144] The embodiments relating to this disclosure will be described in detail below with reference to the drawings. Each of the following embodiments (for example, each case) may be used individually or at least two may be applied in combination.

[0145] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0146] In this disclosure, terms such as notice, activate, deactivate, indicate, select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and operable may be interpreted interchangeably.

[0147] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Element (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0148] In this disclosure, the upper-layer signaling may be any or a combination thereof, such as Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and other messages (e.g., messages from the core network, such as positioning protocol messages (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages).

[0149] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0150] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).

[0151] The following abbreviations may be used in this disclosure. - radio network temporary identifier:RNTI - time division multiplexing: TDM -time-division-multiplexed:TDM is enabled -frequency division multiplexing:FDM - frequency-division is multiplied:FDM is applied.

[0152] In this disclosure, a b The notation a_b and a with a subscript b may be interchangeable. In this disclosure, a c The notation a^c and a with a c superscripted to the right may be interpreted as interchangeable. In this disclosure, a b c The notation a_b^c, where a is subscripted to the right and c to the right, may be interpreted as interchangeable. In this disclosure, ceil(x), ceiling function, and ceiling function may be interpreted as interchangeable. In this disclosure, floor(x), floor function, and floor function may be interpreted as interchangeable.

[0153] In this disclosure, the reference signal (RS), downlink reference signal (DL-RS), and SSB / CSI-RS may be interpreted as interchangeable. In this disclosure, RSRP, SS-RSRP / CSI-RSRP may be interpreted as interchangeable. In this disclosure, RS with RSRP, RS corresponding to RSRP, RS used for measuring RSRP, SSB with SS-RSRP, and CSI-RS with CSI-RSRP may be interpreted as interchangeable.

[0154] In this disclosure, beam, SSB, SSB index, CSI-RS, CSI-RS resource, CSI-RS resource index, RS, QCL assumption, TCI state, unified TCI state, DL or joint TCI state, UL TCI state, UL Tx spatial filter, spatial domain filter, spatial domain transmit filter, spatial domain receive filter, antenna port QCL parameter, QCL parameter, Tx beam, and spatial filter may be interpreted as each other.

[0155] In this disclosure, RACH resource, RA resource, PRACH preamble, occasion, RACH occasion (RO), PRACH occasion, repetition resource, repetition setting resource, resource set for RO / repetition, time instance and frequency instance, time resource and frequency resource, RO / preamble resource, repetition, PRACH resource, time / frequency resource for PRACH, preamble setting / index, mask setting / index, and PRACH setting may be interpreted as one another.

[0156] In this disclosure, time occasion, time domain position, time position, PRACH occasion, PRACH slot, period, period, symbol / slot / subframe / frame, at least one of their indices, time domain index, T# may be interpreted as one another. In this disclosure, frequency domain position, frequency position, subcarrier / RE / RB / CC, at least one of their indices, frequency domain index, F# may be interpreted as one another. In this disclosure, RO, RO index, RO# may be interpreted as one another.

[0157] In this disclosure, the number of PRACH transmissions, the number of repetitions, the repetition factor, the aggregation factor, and K may be interpreted interchangeably. In this disclosure, multiple PRACH transmissions, the number of PRACH transmissions being greater than one, and multiple repetitions of PRACH may be interpreted interchangeably. In this disclosure, single PRACH transmission and the number of PRACH transmissions being one may be interpreted interchangeably.

[0158] In this disclosure, multiple PRACH transmissions, multiple PRACH transmissions using the same Tx beam, multiple PRACH transmissions using different Tx beams, and multiple PRACH transmissions including multiple PRACH transmissions using the same Tx beam and multiple PRACH transmissions using different Tx beams may be interpreted interchangeably.

[0159] In this disclosure, single PRACH transmission, existing PRACH transmission, and existing PRACH resource configuration may be interpreted as mutually exclusive.

[0160] In this disclosure, multiple PRACH transmission, new PRACH transmission, and multiple PRACH resource configuration may be interpreted interchangeably. In this disclosure, separated RO, new RO, additional RO, RO for multiple PRACH transmission, and RO separated from existing RO for PRACH transmission may be interpreted interchangeably.

[0161] In this disclosure, existing ROs may include ROs configured / determined by RACH-ConfigCommon / RACH-ConfigGeneric / RACH-ConfigDedicated / AdditionalRACH-Config-r17 / additionalRACH-ConfigList-r17.

[0162] In this disclosure, RA-RNTI, MSGB-RNTI, and novel RNTI may be interpreted interchangeably. The formula for MSGB-RNTI may be the formula for RA-RNTI plus the total number of RA-RNTI values.

[0163] (Wireless communication method) The UE may receive a setting for multiple random access channel transmissions (multiple PRACH transmissions, multiple PRACH repetitions). Based on the setting, the UE may determine whether a random access channel occasion (RO) for the multiple random access channel transmissions conflicts with at least one resource (specific resource) among the symbols indicated for receiving a synchronization signal block, symbols set as downlink or flexible by time division multiplexing settings, symbols indicated as downlink or flexible by a slot format indicator, and valid occasions for single random access channel transmissions (Figure 8).

[0164] Based on the above settings, the UE may determine a plurality of random access channel occasions (ROs) to be used for each of the plurality of random access channel transmissions, and based on a specific RO among the plurality of ROs, it may determine at least one of a window start and a radio network temporary identifier (RNTI, RA-RNTI) for monitoring random access responses.

[0165] <Embodiment 1> The restriction on overlapping of multiple RO groups may be at least one of the following restrictions:

[0166] - Restriction #1 At least one of the following limitations may be specified in the specification: -- UE does not expect each RO within a given RO group to be included in multiple RO groups. -- The UE does not expect each RO within an RO group to be included in multiple RO groups for the same number of PRACH transmissions. -- UE does not expect each RO within a given RO group to be included in multiple RO groups for the same SSB / CSI-RS. -- The UE does not expect each RO within a given RO group to be included in multiple RO groups for the same number of SSB / CSI-RS and PRACH transmissions. -- UE does not expect at least one RO within one RO group to be included in another RO group. -- The UE does not expect that at least one RO in one RO group will be included in another RO group for the same number of PRACH transmissions. -- UE does not expect that at least one RO within a given RO group will be included in another RO group for the same SSB / CSI-RS. -- The UE does not expect that at least one RO within one RO group will be included in another RO group for the same number of SSB / CSI-RS and PRACH transmissions.

[0167] - Restriction #2 At least one of the following limitations may be specified in the specification: -- For the same number of PRACH transmissions, multiple overlapping RO groups have the same time span. -- For the same number of SSB / CSI-RS and PRACH transmissions, overlapping RO groups have the same time span. -- For the same number of PRACH transmissions, each RO within a group of multiple ROs with overlapping ROs has the same time domain position. -- For the same number of SSB / CSI-RS and PRACH transmissions, each RO within a group of multiple ROs with overlapping ROs has the same time domain position.

[0168] - Restriction #2a At least one of the following limitations may be specified in the specification: -- For different numbers of PRACH transmissions, multiple overlapping RO groups have the same time resource allocation for a given RO. -- For different numbers of PRACH transmissions, multiple overlapping RO groups have the same frequency resource allocation for a given RO. -- Multiple RO groups overlapping with different numbers of PRACH transmissions to the same SSB / CSI-RS have the same time resource allocation for a given RO. -- For different numbers of PRACH transmissions to the same SSB / CSI-RS, multiple RO groups that overlap have the same frequency resource allocation for a given RO.

[0169] - A specific RO may be at least one of the following ROs: -- The first RO within each RO group. -- The last RO within each RO group.

[0170] The specified RO may be the RO used in determining RA-RNTI.

[0171] - Restriction #3 At least one of the following limitations may be specified in the specification: -- A single RO can be contained within a group of up to G ROs for the same number of PRACH transmissions. -- A single RO can be contained within a group of up to G ROs for the same SSB / CSI-RS. -- One RO can be contained within a group of up to G ROs for the same number of SSB / CSI-RS and PRACH transmissions.

[0172] - Restriction #4 At least one of the following limitations may be specified in the specification: -- Each of the multiple RO groups contains one or more unique ROs. -- Each of the multiple RO groups for the same number of PRACH transmissions contains one or more unique ROs. -- Each of the multiple RO groups for the same SSB / CSI-RS contains one or more unique ROs. -- Each of the multiple RO groups for the same number of SSB / CSI-RS and PRACH transmissions contains one or more unique ROs. -- Each of the multiple RO groups contains one unique RO. -- Each of the multiple RO groups for the same number of PRACH transmissions contains one unique RO. -- Each of the multiple RO groups for the same SSB / CSI-RS contains one unique RO. -- Each of multiple RO groups for the same number of SSB / CSI-RS and PRACH transmissions contains one unique RO.

[0173] - A unique RO is defined in Embodiment 2.

[0174] According to this embodiment, overlapping RO groups can be appropriately limited.

[0175] <Embodiment 2> For multiple PRACHs transmitted in an RO group for a specific number of PRACH transmissions with a particular SSB / CSI-RS, RA-RNTI may be calculated based on at least one of the following options:

[0176] - Option 1: The time and frequency position of all RO / PRACH transmissions within that RO group.

[0177] - Option 2: The time and frequency location of a unique RO / PRACH transmission within that RO group. This option may only apply if each RO group contains a unique RO. The definition of a unique RO will be described later.

[0178] - Option 3: The time position of the first or last RO / PRACH transmission within that RO group, and the frequency position of all RO / PRACH transmissions.

[0179] - Option 4: The time position of the first or last RO / PRACH transmission within that RO group, and the frequency position of the unique RO / PRACH transmission. This option may only apply if each RO group contains a unique RO transmission.

[0180] - Option 5: The time positions of all RO / PRACH transmissions within that RO group, and the frequency positions of the first or last RO / PRACH transmission. This option may be applied only to multiple RO groups with the same time span, or to multiple RO groups with different time spans, if the first or last RO is not included within the multiple RO groups.

[0181] - Option 6: The time position of a unique RO / PRACH transmission within that RO group, and the frequency position of the first or last RO / PRACH transmission. This option may be applied only to multiple RO groups with the same time span, or to multiple RO groups with different time spans for unique ROs within each RO group, provided that the first or last RO is not included in the multiple RO groups.

[0182] - Option 7: The time and frequency position of the first or last RO / PRACH transmission, and the RO group index relative to the current RO group. An RO group index may be defined (additional may be added) for this option.

[0183] In options 2 / 4 / 6, a unique RO may mean an RO that belongs only to the current RO group. A unique PRACH transmission may mean a PRACH transmission on a unique RO. A unique RO does not have to belong to any other RO group for the same SSB / CSI-RS (and the same number of PRACH transmissions). In the example in Figure 9, RO group #0 consists of RO#1, 3, 5, and 7, RO group #1 consists of RO#0, 3, 5, and 6, and RO group #2 consists of RO#0, 2, 5, and 7. RO#1 is a unique RO for RO group #0 because it belongs only to RO group #0. RO#6 is a unique RO for RO group #1 because it belongs only to RO group #1. RO#2 is a unique RO for RO group #2 because it belongs only to RO group #2.

[0184] Details of Option 1 For multiple PRACHs transmitted in an RO group for a specific number of specific SSB / CSI-RS and PRACH transmissions, RA-RNTI may be calculated according to at least one of the following options, based on the time and frequency positions of all RO / PRACH transmissions within that RO group.

[0185] - Option 1-1: The mean is used. The RA-RNTI calculation formula may be any of the following: -- RA-RNTI=1+floor[(Σ k=0 K-1 (s_id_k+14×t_id_k+14×80×f_id_k)) / K]+14×80×8×ul_carrier_id -- RA-RNTI=1+ceil[(Σ k=0 K-1 (s_id_k+14×t_id_k+14×80×f_id_k)) / K]+14×80×8×ul_carrier_id

[0186] - Option 1-2: Modulo operations are used. The RA-RNTI calculation formula may be any of the following: -- RA-RNTI=1+(Σ k=0 K-1 (s_id_k+14×t_id_k+14×80×f_id_k)) mod (14×80×8)+14×80×8×ul_carrier_id -- RA-RNTI=1+(Σ k=0 K-1 s_id_k) mod 14+(Σ k=0 K-1 t_id_k) mod 80 × + (Σ k=0 K-1 f_id_k) mod 8+14×80×8×ul_carrier_id

[0187] - Options 1-3: The sum is used. The RA-RNTI calculation formula may be any of the following: -- RA-RNTI=1+Σ k=0 K-1 (s_id_k+14×t_id_k+14×80×f_id_k)+14×80×8×N×ul_carrier_id+14×80×8×Y -- RA-RNTI=1+Σ k=0 K-1 (s_id_k+14×t_id_k+14×80×f_id_k)+14×80×8×ul_carrier_id+14×80×8×Y

[0188] The value of N may be defined in the specification or may be instructed / set by the base station. For example, N may be 8 or any other value. N may also be the maximum number of PRACH repeats (the maximum value of the repeat factor K).

[0189] The value of Y may be defined in the specification or may be instructed / set by the base station. For example, Y may be 0, 4, or any other value.

[0190] In options 1-1 / 1-2 / 1-3, for the k-1 (k=0,...,K-1)th RO in an RO group for multiple PRACH transmissions, s_id_k, t_id_k, and f_id_k may be parameters for the symbol index, slot index, and frequency index, respectively. K may also be the number of RO / PRACH transmissions in that RO group.

[0191] In the existing specifications, the range of RA-RNTI values ​​for 4-step RACH is from 0 to 14×80×8×2, and the range of RA-RNTI values ​​for 2-step RACH is from 14×80×8×2 to 14×80×8×4.

[0192] Options 1-3 are based on summation. When N=8 and Y=0 are applied, the RA-RNTI range is expanded from 0 to 14×80×8×8×2. This range may cause RA-RNTI to overlap with the existing RA-RNTI range for 2-step RACH. When Y=4 is applied, the RA-RNTI range for multiple PRACH transmissions starts from 14×80×8×4. This range is later than the existing RA-RNTI range for 2-step RACH. According to options 1-3, the probability of RA-RNTI collisions between RO groups can be reduced.

[0193] The motivation for options 1-1 / 1-2 is to maintain the same RA-RNTI range as the existing RA-RNTI range for 4-step RACH.

[0194] Details of Option 2 For a specific number of PRACH transmissions in an RO group, the RA-RNTI may be calculated according to at least one of the following options, based on the time and frequency position of the unique RO / PRACH transmissions within that RO group.

[0195] - Option 2-1: RA-RNTI is based on the time and frequency position of the first or last unique RO within that RO group. The formula for calculating RA-RNTI may also be as follows: -- RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id Here, for the first or last unique RO in an RO group for multiple PRACH transmissions, s_id, t_id, and f_id may be parameters for the symbol index, slot index, and frequency index, respectively.

[0196] - Option 2-2: RA-RNTI is based on the time and frequency position of the first or last unique RO within that RO group. RA-RNTI may be calculated according to at least one of the following options:

[0197] -- Option 2-2-1: The mean is used. The formula for calculating RA-RNTI may also be as follows: --- RA-RNTI=1+(Σ m=0 M-1 (s_id_m+14×t_id_m+14×80×f_id_m)) / M+14×80×8×ul_carrier_id

[0198] -- Option 2-2-2: Modulo operations are used. The RA-RNTI calculation formula may be any of the following: --- RA-RNTI=1+(Σ m=0 M-1 (s_id_m+14×t_id_m+14×80×f_id_m)) mod (14×80×8)+14×80×8×ul_carrier_id --- RA-RNTI=1+(Σ m=0 M-1 s_id_m) mod 14+(Σ m=0 M-1 t_id_m) mod 80+(Σ m=0 M-1 f_id_m) mod 8+14×80×8×ul_carrier_id

[0199] -- Option 2-2-3: The sum is used. The calculation formula for RA-RNTI may be any of the following. --- RA-RNTI = 1 + Σ m=0 M-1 (s_id_m + 14 × t_id_m + 14 × 80 × f_id_m) + 14 × 80 × 8 × N × ul_carrier_id + 14 × 80 × 8 × Y --- RA-RNTI = 1 + Σ m=0 M-1 (s_id_m + 14 × t_id_m + 14 × 80 × f_id_m) + 14 × 80 × 8 × ul_carrier_id + 14 × 80 × 8 × Y

[0200] The value of N may be defined in the specification or instructed / set by the base station. For example, N may be 8 or other values. N may be the maximum number of PRACH repetitions (the maximum value of the repetition factor K).

[0201] The value of Y may be defined in the specification or instructed / set by the base station. For example, Y may be 0, 4, or other values.

[0202] In Option 2-2-1 / 2-2-2 / 2-2-3, for the m-1 (m = 0,..., M-1)th unique RO in the RO group for multiple PRACH transmissions, s_id_m, t_id_m, and f_id_m may be parameters of the symbol index, slot index, and frequency index, respectively. M may be the number of unique ROs in that RO group.

[0203] In the existing specification, the range of the RA-RNTI value for the 4-step RACH is from 0 to 14 × 80 × 8 × 2, and the range of the RA-RNTI value for the 2-step RACH is from 14 × 80 × 8 × 2 to 14 × 80 × 8 × 4.

[0204] Option 2-2-3 is based on summation. When N=8 and Y=0 are applied, the RA-RNTI range is expanded from 0 to 14×80×8×8×2. This range may cause RA-RNTI to overlap with the existing RA-RNTI range for 2-step RACH. When Y=4 is applied, the RA-RNTI range for multiple PRACH transmissions starts from 14×80×8×4. This range is later than the existing RA-RNTI range for 2-step RACH. According to option 2-2-3, the probability of RA-RNTI collisions between RO groups can be reduced.

[0205] The motivation for option 2-2-1 / 2-2-2 is to maintain the same RA-RNTI range as the existing RA-RNTI range for 4-step RACH.

[0206] Details of Option 3 For multiple PRACHs transmitted in an RO group for a specific number of PRACH transmissions, the RA-RNTI may be calculated according to at least one of the following options, based on the time position of the first or last RO / PRACH transmission in that RO group and the frequency position of all RO / PRACH transmissions.

[0207] - Option 3-1: The average of the frequency positions of all RO / PRACH transmissions is used. The formula for calculating RA-RNTI may also be as follows: -- RA-RNTI=1+s_id+14×t_id+14×80×((Σ k=0 K-1 f_id_k)) / K)+14×80×8×ul_carrier_id

[0208] - Option 3-2: The modulo calculation of the sum of the frequency positions of all RO / PRACH transmissions is used. The formula for calculating RA-RNTI may also be as follows: -- RA-RNTI=1+s_id+14×t_id+14×80×(Σ k=0 K-1(f_id_k) mod 8)+14×80×8×ul_carrier_id

[0209] - Option 3-3: The sum is used. The calculation formula for RA-RNTI may be any of the following: -- RA-RNTI=1+s_id+14×t_id+14×80×(Σ k=0 K-1 f_id_k)+14×80×8×N×ul_carrier_id+14×80×8×Y -- RA-RNTI=1+s_id+14×t_id+14×80×(Σ k=0 K-1 f_id_k)+14×80×8×ul_carrier_id+14×80×8×Y

[0210] The value of N may be defined in the specification or may be instructed / set by the base station. For example, N may be 8 or any other value. N may also be the maximum number of PRACH repeats (the maximum value of the repeat factor K).

[0211] The value of Y may be defined in the specification or may be instructed / set by the base station. For example, Y may be 0, 4, or any other value.

[0212] In options 3-1 / 3-2 / 3-3, for the first or last RO in an RO group for multiple PRACH transmissions, s_id and t_id may be the symbol index and slot index parameters, respectively. For the k-1 (k=0,...,K-1)th RO in an RO group for multiple PRACH transmissions, f_id_k may be the frequency index parameter. K may be the number of RO / PRACH transmissions in that RO group.

[0213] In the existing specifications, the range of RA-RNTI values ​​for 4-step RACH is from 0 to 14×80×8×2, and the range of RA-RNTI values ​​for 2-step RACH is from 14×80×8×2 to 14×80×8×4.

[0214] Option 3-3 is based on summation. If Y=0 is applied, the RA-RNTI range is expanded from 0 to 14×80×8×8×2. This range may cause RA-RNTI to overlap with the existing RA-RNTI range for 2-step RACH. If Y=4 is applied, the RA-RNTI range for multiple PRACH transmissions starts from 14×80×8×4. This range is later than the existing RA-RNTI range for 2-step RACH. According to option 3-3, the probability of RA-RNTI collisions between RO groups can be reduced.

[0215] The motivation for option 3-1 / 3-2 is to maintain the same RA-RNTI range as the existing RA-RNTI range for 4-step RACH.

[0216] Details of Option 4 For multiple PRACHs transmitted in an RO group for a specific number of PRACH transmissions, the RA-RNTI may be calculated according to at least one of the following options, based on the time position of the first or last RO / PRACH transmission within that RO group and the frequency position of the unique RO / PRACH transmission.

[0217] - Option 4-1: RA-RNTI is based on the frequency position of the first or last unique RO within that RO group. The formula for calculating RA-RNTI may also be as follows: -- RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id Here, for the first or last RO in an RO group for multiple PRACH transmissions, s_id and t_id may be the symbol index and slot index parameters, respectively. For the first or last unique RO in an RO group for multiple PRACH transmissions, f_id may be the frequency index parameter.

[0218] - Option 4-2: The average with respect to the frequency positions of the unique ROs within that RO group is used. The calculation formula for RA-RNTI may be as follows. -- RA-RNTI = 1 + s_id + 14×t_id + 14×80×((Σ m=0 M-1 f_id_m) / M) + 14×80×8×ul_carrier_id

[0219] - Option 4-3: A modulo operation with respect to the frequency positions of the unique ROs within that RO group is used. The calculation formula for RA-RNTI may be any of the following. -- RA-RNTI = 1 + s_id + 14×t_id + 14×80×(Σ m=0 M-1 f_id_m) mod 8 + 14×80×8×ul_carrier_id

[0220] - Option 4-4: The sum with respect to the frequency positions of the unique ROs within that RO group is used. The calculation formula for RA-RNTI may be any of the following. -- Option 4-4a: RA-RNTI = 1 + s_id + 14×t_id + 14×80×(Σ m=0 M-1 f_id_m) + 14×80×8×N×ul_carrier_id + 14×80×8×Y -- Option 4-4b: RA-RNTI = 1 + s_id + 14×t_id + 14×80×(Σ m=0 M-1 f_id_m) + 14×80×8×ul_carrier_id + 14×80×8×Y

[0221] The value of N may be defined in the specification or may be instructed / set from the base station. For example, N may be 8 or may be other values. N may be the maximum number of PRACH repetitions (the maximum value of the repetition factor K).

[0222] The value of Y may be defined in the specification or may be instructed / set by the base station. For example, Y may be 0, 4, or any other value.

[0223] In options 4-2 / 4-3 / 4-4, for the first or last RO in an RO group for multiple PRACH transmissions, s_id and t_id may be the symbol index and slot index parameters, respectively. For the m-1 (m=0,...,M-1)th unique RO in an RO group for multiple PRACH transmissions, f_id_m may be the frequency index parameter, where M is the number of unique ROs in that RO group.

[0224] In the existing specifications, the range of RA-RNTI values ​​for 4-step RACH is from 0 to 14×80×8×2, and the range of RA-RNTI values ​​for 2-step RACH is from 14×80×8×2 to 14×80×8×4.

[0225] Option 4-4 is based on summation. When N=8 and Y=0 are applied, the RA-RNTI range is expanded from 0 to 14×80×8×8×2. This range may cause RA-RNTI to overlap with the existing RA-RNTI range for 2-step RACH. When Y=4 is applied, the RA-RNTI range for multiple PRACH transmissions starts from 14×80×8×4. This range is later than the existing RA-RNTI range for 2-step RACH. According to option 4-4, the probability of RA-RNTI collisions between RO groups can be reduced.

[0226] The motivation for options 4-2 / 4-3 is to maintain the same RA-RNTI range as the existing RA-RNTI range for 4-step RACH.

[0227] Details of Option 5 For a specific number of PRACH transmissions in an RO group, the RA-RNTI may be calculated according to at least one of the following options, based on the time position of all RO / PRACH transmissions within that RO group and the frequency position of the first or last RO / PRACH transmission.

[0228] - Option 5-1: The average of the time positions of all RO / PRACH transmissions is used. The formula for calculating RA-RNTI may also be as follows: -- RA-RNTI=1+(Σ k=0 K-1 (s_id_k+14×t_id_k)) / K+14×80×f_id+14×80×8×ul_carrier_id

[0229] - Option 5-2: The modulo operation of the sum of the time positions of all RO / PRACH transmissions is used. The formula for calculating RA-RNTI may also be as follows: -- RA-RNTI=1+(Σ k=0 K-1 (s_id_k+14×t_id_k))mod (14×80)+14×80×f_id+14×80×8×ul_carrier_id

[0230] - Option 5-3: The sum is used. The calculation formula for RA-RNTI may be any of the following: -- RA-RNTI=1+Σ k=0 K-1 (s_id_k+14×t_id_k)+14×80×f_id+14×80×8×N×ul_carrier_id+14×80×8×Y -- RA-RNTI=1+Σ k=0 K-1 (s_id_k+14×t_id_k)+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×Y

[0231] The value of N may be defined in the specification or may be instructed / set by the base station. For example, N may be 8 or any other value. N may also be the maximum number of PRACH repeats (the maximum value of the repeat factor K).

[0232] The value of Y may be defined in the specification or may be instructed / set by the base station. For example, Y may be 0, 4, or any other value.

[0233] In options 5-1 / 5-2 / 5-3, for the k-1 (k=0,...,K-1)th RO in an RO group for multiple PRACH transmissions, s_id_k and t_id_k may be the symbol index and slot index parameters, respectively. For the first or last RO in an RO group for multiple PRACH transmissions, f_id may be the frequency index parameter. K may be the number of RO / PRACH transmissions in that RO group.

[0234] In the existing specifications, the range of RA-RNTI values ​​for 4-step RACH is from 0 to 14×80×8×2, and the range of RA-RNTI values ​​for 2-step RACH is from 14×80×8×2 to 14×80×8×4.

[0235] Option 5-3 is based on summation. When N=8 and Y=0 are applied, the RA-RNTI range is expanded from 0 to 14×80×8×8×2. This range may cause RA-RNTI to overlap with the existing RA-RNTI range for 2-step RACH. When Y=4 is applied, the RA-RNTI range for multiple PRACH transmissions starts from 14×80×8×4. This range is later than the existing RA-RNTI range for 2-step RACH. According to option 5-3, the probability of RA-RNTI collisions between RO groups can be reduced.

[0236] The motivation for option 5-1 / 5-2 is to maintain the same RA-RNTI range as the existing RA-RNTI range for 4-step RACH.

[0237] Details of Option 6 For multiple PRACHs transmitted in an RO group for a specific number of specific SSB / CSI-RS and PRACH transmissions, RA-RNTI may be calculated according to at least one of the following options, based on the time position of a unique RO / PRACH transmission within that RO group and the frequency position of the first or last RO / PRACH transmission.

[0238] - Option 6-1: RA-RNTI is based on the time position of the first or last unique RO within that RO group. The formula for calculating RA-RNTI may also be as follows: -- RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id Here, for the first or last unique RO in an RO group for multiple PRACH transmissions, s_id and t_id may be the symbol index and slot index parameters, respectively. For the first or last RO in an RO group for multiple PRACH transmissions, f_id may be the frequency index parameter.

[0239] - Option 6-2: The average of the time positions of unique ROs within that RO group is used. The formula for calculating RA-RNTI may also be as follows: -- RA-RNTI=1+(Σ m=0 M-1 (s_id_m+14×t_id_m)) / M+14×80×f_id+14×80×8×ul_carrier_id

[0240] - Option 6-3: Modulo operations are performed on the time position of unique ROs within that RO group. The RA-RNTI calculation formula may be any of the following: -- RA-RNTI=1+(Σm=0 M-1 ((s_id_m + 14 × t_id_m)) mod (14 × 80) + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id

[0241] - Option 6-4: The sum with respect to the time positions of the unique ROs within that RO group is used. The calculation formula for RA-RNTI may be any of the following. -- Option 6-4a: RA-RNTI = 1 + Σ m=0 M-1 (s_id_m + 14 × t_id_m) + 14 × 80 × f_id + 14 × 80 × 8 × N × ul_carrier_id + 14 × 80 × 8 × Y -- Option 6-4b: RA-RNTI = 1 + Σ m=0 M-1 (s_id_m + 14 × t_id_m) + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id + 14 × 80 × 8 × Y

[0242] The value of N may be defined in the specification or may be instructed / set by the base station. For example, N may be 8 or other values. N may be the maximum number of PRACH repetitions (the maximum value of the repetition factor K).

[0243] The value of Y may be defined in the specification or may be instructed / set by the base station. For example, Y may be 0, 4, or other values.

[0244] In Options 6-2 / 6-3 / 6-4, for the m-1 (m = 0,..., M-1)th unique RO within the RO group for multiple PRACH transmissions, s_id_m and t_id_m may each be parameters of the symbol index and slot index, respectively. For the first or last RO within the RO group for multiple PRACH transmissions, f_id may be a parameter of the frequency index. M may be the number of unique ROs within that RO group.

[0245] In the existing specifications, the range of RA-RNTI values ​​for 4-step RACH is from 0 to 14×80×8×2, and the range of RA-RNTI values ​​for 2-step RACH is from 14×80×8×2 to 14×80×8×4.

[0246] Option 6-4 is based on summation. When N=8 and Y=0 are applied, the RA-RNTI range is expanded from 0 to 14×80×8×8×2. This range may cause RA-RNTI to overlap with the existing RA-RNTI range for 2-step RACH. When Y=4 is applied, the RA-RNTI range for multiple PRACH transmissions starts from 14×80×8×4. This range is later than the existing RA-RNTI range for 2-step RACH. According to option 6-4, the probability of RA-RNTI collisions between RO groups can be reduced.

[0247] The motivation for options 6-2 / 6-3 is to maintain the same RA-RNTI range as the existing RA-RNTI range for 4-step RACH.

[0248] Details of Option 7 For multiple PRACHs transmitted in an RO group for a specific number of specific SSB / CSI-RS and PRACH transmissions, RA-RNTI may be calculated according to at least one of the following options, based on the time and frequency position of the first or last RO / PRACH transmission and the RO group index for the current RO group. - RA-RNTI=1+ro_group_id+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×Y - RA-RNTI=1+ro_group_id+s_id×G+14×G×t_id+14×G×80×f_id+14×G×80×8×ul_carrier_id+14×80×8×Y - RA-RNTI=1+ro_group_id+s_id+14×G×t_id+14×G×80×f_id+14×G×80×8×ul_carrier_id+14×80×8×Y - RA-RNTI=1+ro_group_id+s_id+14×t_id+14×G×80×f_id+14×G×80×8×ul_carrier_id+14×80×8×Y - RA-RNTI=1+ro_group_id+s_id+14×t_id+14×80×f_id+14×G×80×8×ul_carrier_id+14×80×8×Y - RA-RNTI=1+ro_group_id+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2×G+14×80×8×Y - RA-RNTI=1+s_id+14×(t_id+ro_group_id)+14×(80+G)×f_id+14×(80+G)×8×ul_carrier_id+14×80×8×Y - RA-RNTI=1+s_id+14×t_id+14×80×(f_id+ro_group_id)+14×80×(8+G)×ul_carrier_id+14×80×8×Y - RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×(ul_carrier_id+ro_group_id)+14×80×8×Y - RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×ro_group_id+14×80×8×Y

[0249] The above RA-RNTI formula may conform to at least one of the following provisions.

[0250] - Regulation 1 G may be the maximum number of RO groups containing the same RO. G may be the maximum number of RO groups containing the same RO for the same SSB / CSI-RS. G may be the maximum number of RO groups containing the same RO for the same number of PRACH transmissions. G may be the maximum number of RO groups containing the same RO for the same SSB / CSI-RS and the same number of PRACH transmissions. G may be subject to restriction #3 of Embodiment 1.

[0251] - Regulation 2 Y may be defined in the specification or instructed / configured by the base station. Y may be 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, etc. If Y=4 is applied, the RA-RNTI range for multiple PRACH transmissions starts from 14 × 80 × 8 × 4. This range is later than the existing RA-RNTI range for 2-step RACH.

[0252] - Regulation 3 For the first or last RO in an RO group for multiple PRACH transmissions, s_id, t_id, and f_id may be parameters for the symbol index, slot index, and frequency index, respectively.

[0253] - Regulation 4 ro_group_id may be an RO group index. This RO group index may represent an index of an RO group for multiple PRACH transmissions among multiple RO groups that follow at least one of the following options: -- Option 7-1: Multiple RO groups within a specified period. The specified period may be, for example, an association period, a configuration period, X slots / subframes / frames defined by the specification, or X slots / subframes / frames instructed / configured by the base station. The multiple RO groups may be multiple RO groups for the same SSB / CSI-RS. The multiple RO groups may be multiple RO groups for the same number of PRACH transmissions. The multiple RO groups may be multiple RO groups for the same SSB / CSI-RS and the same number of PRACH transmissions. -- Option 7-2: A set of multiple RO groups with overlapping ROs. These multiple RO groups may be multiple RO groups for the same SSB / CSI-RS. These multiple RO groups may be multiple RO groups for the same number of PRACH transmissions. These multiple RO groups may be multiple RO groups for the same SSB / CSI-RS and the same number of PRACH transmissions. -- Option 7-3: Multiple RO groups where the first or last RO is the same RO. These multiple RO groups may also be multiple RO groups for the same SSB / CSI-RS. These multiple RO groups may also be multiple RO groups for the same number of PRACH transmissions. These multiple RO groups may also be multiple RO groups for the same SSB / CSI-RS and the same number of PRACH transmissions.

[0254] The indexing order for the RO groups within the multiple RO groups (multiple RO groups of options 7-1 / 7-2 / 7-3) may be based on at least one of the time positions of the multiple ROs within the RO group and the frequency positions of the multiple ROs within the RO group. The indexing order for the RO groups may follow at least one of the following examples.

[0255] - Example 1 In multiple RO groups with different time spans, an RO group with an earlier start time position or end time position may be indexed earlier than an RO group with a later start time position or end time position. The start time position or end time position of an RO group may mean the time position of the first or last RO within that RO group.

[0256] - Example 2 Multiple RO groups having the same time span or the same start time position or the same end time position may be indexed based on frequency position. If the time position of the first or last RO of multiple RO groups is the same, at least one of the following operations may be followed. -- If the multiple RO groups have different frequency indices with respect to the first or last RO, the RO group corresponding to the lower frequency index may be assigned an earlier RO group index than the RO group corresponding to the higher frequency index, and the RO group corresponding to the higher frequency index may be assigned an earlier RO group index than the RO group corresponding to the lower frequency index. -- If multiple RO groups have the same frequency index for the first or last RO, the frequency indices for ROs later or earlier than that RO are compared, and the RO group corresponding to the lower frequency index may be assigned an earlier RO group index than the RO group corresponding to the higher frequency index, and the RO group corresponding to the higher frequency index may be assigned an earlier RO group index than the RO group corresponding to the lower frequency index.

[0257] In Example 1, among multiple RO groups with different time spans, the RO group with an earlier start time position is assigned an earlier RO group index than the RO group with a later start time position. In Example 2, if the time position of the first RO of multiple RO groups is the same, and those multiple RO groups have different frequency indices relative to the first RO, the RO group corresponding to the lower frequency index is assigned an earlier RO group index than the RO group corresponding to the higher frequency index. If those multiple RO groups have the same frequency index relative to the first RO, the frequency indices relative to subsequent ROs are compared, and the RO group corresponding to the lower frequency index is assigned an earlier RO group index than the RO group corresponding to the higher frequency index. In the example in Figure 5 above, the RO group consisting of RO#1, 6, 11, and 13, the RO group consisting of RO#1, 6, 8, and 13, and the RO group consisting of RO#1, 4, 8, and 13 all have the same time position for the first RO of the multiple RO groups, and have the same frequency index for the first RO. The frequency index for ROs after that RO is compared, and the RO group corresponding to the lower frequency index is assigned an earlier RO group index than the RO group corresponding to the higher frequency index. The RO group consisting of RO#1, 4, 8, and 13 is assigned index 0, the RO group consisting of RO#1, 6, 8, and 13 is assigned index 1, and the RO group consisting of RO#1, 6, 11, and 13 is assigned index 2.

[0258] ro_group_id may also be set by the RRC parameter.

[0259] According to this embodiment, the UE can appropriately determine RA-RNTI.

[0260] <Embodiment 3> Some of the options in Embodiment 2 may be applied according to at least one of the following methods of application. - Option 1 of Embodiment 2 can be applied without any limitations. - If constraint #1 of Embodiment 1 applies, option 2 of Embodiment 2 can be applied. - If constraint #2 of Embodiment 1 applies, option 3 of Embodiment 2 can be applied. - If constraint #3 of Embodiment 1 applies, option 7 of Embodiment 2 can be applied.

[0261] According to this embodiment, the UE can determine an appropriate RA-RNTI for the RO group's limitations.

[0262] <Embodiment A1> Considering the possibility of RO collisions in multiple PRACH transmissions using the same Tx beam, the UE operation may follow at least one of the following options:

[0263] - Option 1 The UE does not expect the first or last (effective) RO within an RO group to be in conflict. Alternatively, the UE does not expect any first or last (effective) RO within any RO group to be in conflict.

[0264] - Option 2 When the UE selects an RO group, conflicts are taken into consideration. The UE may follow at least one of the following options: -- Option 2-1: The UE does not determine / select the RO group that has the first or last (valid) RO with a collision as the RO group for multiple PRACH transmissions. -- Option 2-2: If the number of (effective) ROs with collisions is greater than or equal to a specific value X, the UE will not determine / select the RO group as an RO group for multiple PRACH transmissions, where the value of X may be specified by the specification or set by the base station. -- Option 2-3: If the number of non-collision (effective) ROs is less than or equal to a specific value Y, the UE will not determine / select the RO group as an RO group for multiple PRACH transmissions. Here, the value of Y may be specified by the specification or set by the base station.

[0265] - Option 3 When the UE selects an RO group, collisions are not considered. The UE's behavior after selecting an RO group is defined. The UE may follow at least one of the following options: -- Option 3-1: If any (active) RO in the RO group is involved in a conflict, the UE will not send a PRACH on that RO, or will cancel the PRACH transmission. The UE may send PRACHs on the (remaining) active ROs in that RO group that are not involved in a conflict. -- Option 3-2: If the first or last (valid) RO in an RO group is involved in a conflict, the UE will not send a PRACH within that RO group, or will cancel the PRACH transmission. -- Option 3-3: If the number of (active) ROs with collisions within the selected RO group is greater than or equal to a specific value X, the UE will not transmit PRACH within that RO group, or will cancel the PRACH transmission. Here, the value of X may be defined by the specification or set by the base station. -- Option 3-4: If the number of non-collision (valid) ROs in the selected RO group is less than or equal to a specific value Y, the UE will not send PRACHs within that RO group, or will cancel PRACH transmissions. Here, the value of Y may be defined by the specification or set by the base station.

[0266] According to this embodiment, the UE can appropriately control multiple PRACH transmissions even if there is a possibility of collision.

[0267] <Embodiment A2> The definition of "collision" in the terms "collision-involved" and "non-collision-involved" in this disclosure may include at least one of the following collision cases: - Any symbol designated as DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and its RO overlap. - An overlap between any symbol indicated for receiving an SS / PBCH block by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon and its RO. - Any symbol designated as DL by DCI format 2_0 / SFI and its RO must overlap. - Any symbol designated as flexible by DCI Format 2_0 / SFI and its RO (Role-Optic) must overlap. - Any symbol indicated by the detected DCI for PDSCH / CSI-RS reception and its RO overlap. - When tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are configured, and any symbol is set to flexible by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated, and the UE is configured to monitor DCI format 2_0 / SFI, and the UE does not detect DCI format 2_0 / SFI, then the symbol and its RO will overlap. - In the time domain / frequency domain, any valid RO for a single PRACH transmission associated with a Type 1RA procedure overlaps with that RO. - In the time domain / frequency domain, any valid RO associated with a type 2RA procedure overlaps with that RO. - Any valid push occasion associated with a type 2RA procedure and its RO overlap in the time domain / frequency domain.

[0268] Whether a particular collision case is included among the above-mentioned collision cases may be specified by the specifications or set by the base station.

[0269] According to this embodiment, the UE can handle collisions appropriately.

[0270] <Variations of Embodiments A1 / A2> Embodiments A1 / A2 can be applied to cases of multiple PRACH transmission using multiple different Tx beams.

[0271] Different options in Embodiments A1 / A2 may be applied to cases of multiple PRACH transmission using the same Tx beam and cases of multiple PRACH transmission using different Tx beams. Of the options in Embodiments A1 / A2, the options applicable to each case may be defined by the specifications or set by the base station.

[0272] Embodiments A1 / A2 can be applied to multiple PRACH transmissions with a specific RACH type. The specific RACH type may be a specific RACH triggering method, a specific RACH purpose, etc. - Example: Embodiments A1 / A2 may be applied to a specific RACH triggering method. The specific RACH triggering method may be, for example, an RA procedure initiated / triggered by a PDCCH / MAC entity / RRC. - Example: Embodiments A1 / A2 may be applied to a specific RACH purpose. The specific RACH purpose method may be, for example, at least one of initial access, SI request, SpCell BFR, and reconfiguration with sync.

[0273] <Analysis> As mentioned above, it is being considered that only a single RAR window will be supported for multiple PRACH transmissions. Insufficient consideration has been given to whether the RAR window should start after the RO for the first iteration or after the RO for the last iteration.

[0274] Furthermore, in embodiments A1 / A2, a UE may not send a PRACH on a specific RO within an RO group, but may send a PRACH on other ROs within that RO group. The RA-RNTI calculation in such cases is unclear. For example, it is unclear whether the RA-RNTI calculation considers only the first or last RO among the ROs that actually send a PRACH, or whether it does not depend on whether a PRACH is actually sent. For example, if the RAR window starts after the last PRACH transmission in a series of PRACH transmissions using RO#0, #1, #2, and #3, and the last PRACH is not sent due to a collision at RO#3, it is unclear whether the RAR window starts after RO#2 or after RO#3.

[0275] <Embodiment B1> The RAR window for multiple PRACH transmissions (using the same Tx beam) may follow at least one of the following options:

[0276] - Option 1 The RAR window starts after the last symbol of the first or last valid RO within the RO group determined for multiple PRACH transmissions.

[0277] - Option 2 The RAR window starts after the last symbol of the first or last (actually sent) PRACH send in a multi-PRACH send.

[0278] - Option 3 The RAR window starts after the last symbol of the first or last valid RO that meets specific conditions within the RO group determined for multiple PRACH transmissions.

[0279] The specific condition may be that the "collision" of Embodiment A2 does not occur in that RO. The specific condition may be one of the following conditions, or it may be a condition obtained by an AND / OR operation of two or more conditions. - Any symbol designated as DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and its RO must not overlap. - No symbol indicated for receiving an SS / PBCH block by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon should overlap with its RO (Role-Optic). - Any symbol designated as DL by DCI format 2_0 / SFI and its RO must not overlap. - Any symbol designated as flexible by DCI Format 2_0 / SFI and its RO (Role-Optic) must not overlap. - No symbols indicated by the detected DCI for PDSCH / CSI-RS reception and their ROs must overlap. - If tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are configured and any symbol is set to flexible by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated, and the UE is configured to monitor DCI format 2_0 / SFI, and the UE does not detect DCI format 2_0 / SFI, then the symbol and its RO shall not overlap. - In the time domain / frequency domain, any valid RO for a single PRACH transmission associated with a Type 1RA procedure and that RO must not overlap. - In the time domain / frequency domain, any valid RO associated with a type 2RA procedure and that RO must not overlap. - In the time domain / frequency domain, any valid push occasion associated with a type 2RA procedure and its RO must not overlap.

[0280] According to this embodiment, the UE can appropriately determine the RAR window for multiple PRACH transmissions.

[0281] <Embodiment B2> RA-RNTI for monitoring RAR for multiple PRACH transmissions (using the same Tx beam) may be calculated according to at least one of the following options:

[0282] - Option 1 The RAR window starts after the last symbol of the first or last valid RO within the RO group determined for multiple PRACH transmissions.

[0283] - Option 2 The RAR window starts after the last symbol of the first or last (actually sent) PRACH send in a multi-PRACH send.

[0284] - Option 3 The RAR window starts after the last symbol of the first or last valid RO that meets specific conditions within the RO group determined for multiple PRACH transmissions.

[0285] - Option 4 The RAR window starts after the last symbol of all or unique valid ROs within the RO group determined for multiple PRACH transmissions.

[0286] - Option 5 The RAR window starts after the last symbol of all or unique PRACH transmissions (actually transmitted) within a group of PRACH transmissions.

[0287] - Option 6 The RAR window is initiated after the last symbol of a valid RO that meets specific conditions within the RO group determined for multiple PRACH transmissions.

[0288] The specific condition may be that the "collision" of Embodiment A2 does not occur in that RO. The specific condition may be one of the following conditions, or it may be a condition obtained by an AND / OR operation of two or more conditions. - Any symbol designated as DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and its RO must not overlap. - No symbol indicated for receiving an SS / PBCH block by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon should overlap with its RO (Role-Optic). - Any symbol designated as DL by DCI format 2_0 / SFI and its RO must not overlap. - Any symbol designated as flexible by DCI Format 2_0 / SFI and its RO (Role-Optic) must not overlap. - No symbols indicated by the detected DCI for PDSCH / CSI-RS reception and their ROs must overlap. - If tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are configured and any symbol is set to flexible by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated, and the UE is configured to monitor DCI format 2_0 / SFI, and the UE does not detect DCI format 2_0 / SFI, then the symbol and its RO shall not overlap. - In the time domain / frequency domain, any valid RO for a single PRACH transmission associated with a Type 1RA procedure and that RO must not overlap. - In the time domain / frequency domain, any valid RO associated with a type 2RA procedure and that RO must not overlap. - In the time domain / frequency domain, any valid push occasion associated with a type 2RA procedure and its RO must not overlap.

[0289] According to this embodiment, the UE can appropriately determine the RAR window for multiple PRACH transmissions.

[0290] <Variations of Embodiments B1 / B2> Embodiments B1 / B2 can be applied to cases of multiple PRACH transmissions using multiple different Tx beams.

[0291] Different options in Embodiments B1 / B2 may be applied to cases of multiple PRACH transmission using the same Tx beam and cases of multiple PRACH transmission using different Tx beams. Of the options in Embodiments B1 / B2, the options applicable to each case may be defined by the specifications or set by the base station.

[0292] <Supplement> [Notification of information to UE] In the embodiments described above, notification of any information from a Network (NW) (e.g., a Base Station (BS)) to a UE (in other words, reception of any information from a BS at the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0293] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader.

[0294] If the above notification is made by a DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble the Cyclic Redundancy Check (CRC) bits assigned to the DCI, or the format of the DCI.

[0295] Furthermore, the notification of any information to the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

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

[0297] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID, not specified in existing standards, in the MAC subheader.

[0298] If the above notice is issued by the UCI, the notice may be sent using PUCCH or PUSCH.

[0299] Furthermore, the notification of any information from the UE in the above-described embodiments may be periodic, semi-persistent, or aperiodic.

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

[0301] At least one of the embodiments described above may apply to at least one of the following random access (RA) systems, or may be limited to at least one of the following RA systems. CBRA. CFRA. • RA ordered by PDCCH. • RA (Research Advisor) for system information acquisition (SI acquisition).

[0302] At least one of the embodiments described above may apply only to a UE that has reported or supports a particular UE capability.

[0303] The specific UE capability may represent at least one of the following: • To support specific processing / operation / control / information for at least one of the above embodiments. • Support for separate RO for multiple PRACH transmissions. • Support for setting up separate ROs for multiple PRACH transmissions based on existing PRACH settings. • Support SSB-RO mapping rules for separate ROs for multiple PRACH transmissions. • To support separate ROs for multiple PRACH transmissions, which overlap in the time domain and frequency domain with the valid PRACH occasions for single PRACH transmissions associated with Type 1RA procedures. • To support separate ROs for multiple PRACH transmissions, which overlap in the time domain and frequency domain with the valid PRACH occasions for single PRACH transmissions associated with Type 2RA procedures. • Support for separate ROs for multiple PRACH transmissions that overlap in the time domain and frequency domain with MsgA PUSCH occasions associated with Type 2RA procedures. • Support for separate ROs for multiple PRACH transmissions that overlap in the time domain with the valid PRACH occasions for single PRACH transmissions associated with Type 1RA procedures. • Support for separate ROs for multiple PRACH transmissions that overlap in the time domain with the valid PRACH occasions for single PRACH transmissions associated with Type 2RA procedures. • Support for isolated ROs for multiple PRACH transmissions that overlap in the time domain with MsgA PUSCH occasions associated with Type 2RA procedures.

[0304] Furthermore, the above-mentioned specific UE capabilities may be capabilities that apply across all frequencies (commonly regardless of frequency), capabilities per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), capabilities per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities per subcarrier spacing (SCS), or capabilities per feature set (FS) or feature set per component-carrier (FSPC).

[0305] Furthermore, the specific UE capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).

[0306] Furthermore, at least one of the embodiments described above may be applied when the UE is configured / activated / triggered by upper layer signaling / physical layer signaling to perform certain information (or the actions of the embodiments described above) related to the embodiments described above. For example, such certain information may be information indicating the activation of at least one action of the embodiments described above, or arbitrary RRC parameters for a particular release (e.g., Rel. 18 / 19).

[0307] In Rel.YY (for example, YY is 18 or greater), the RRC parameter that enables operation XXX may be expressed as XXX_rYY(XXX-rYY).

[0308] If the UE does not support at least one of the above-mentioned specific UE capabilities or does not have the above-mentioned specific information configured, the behavior of, for example, Rel.15 / 16 may be applied.

[0309] (Note) The following invention is added with respect to one embodiment of this disclosure. [Note 1] A receiving unit that receives settings for multiple random access channel transmissions, A terminal having, based on the above settings, a control unit that determines whether a random access channel occasion (RO) for multiple random access channel transmissions conflicts with at least one resource, which includes symbols indicated for receiving a synchronization signal block, symbols set as downlink or flexible by time division multiplexing settings, symbols indicated as downlink or flexible by a slot format indicator, and valid occasions for single random access channel transmission. [Note 2] If it is determined that the RO conflicts with the resource, the control unit does not include the RO in the multiple ROs for the multiple random access channel transmission, as described in Appendix 1. [Note 3] If it is determined that the RO conflicts with the resource, the control unit includes the RO in the multiple ROs for transmitting multiple random access channels and does not transmit random access channels in the RO, as described in Appendix 1 or Appendix 2 of the terminal. [Note 4] The control unit applies the same beam or the same transmission configuration indicator (TCI) state to the multiple random access channel transmissions, as described in any of the terminals described in Appendix 1 to Appendix 3.

[0310] (Note) The following invention is added with respect to one embodiment of this disclosure. [Note 1] A receiving unit that receives settings for multiple random access channel transmissions, A terminal having a control unit that determines a plurality of random access channel occasions (ROs) to be used for each of the plurality of random access channel transmissions based on the above settings, and determines at least one of a window start and a radio network temporary identifier (RNTI) for monitoring random access responses based on a specific RO among the plurality of ROs. [Note 2] The terminal described in Appendix 1, wherein the specified RO is one of the following among the multiple ROs: the first active RO, the last active RO, the RO from which the random access channel is actually transmitted first, and the RO from which the random access channel is actually transmitted last. [Note 3] The terminal as described in Appendix 1 or Appendix 2, wherein the specified RO is one or more ROs that do not conflict with at least one resource of the following: a symbol indicated for receiving a synchronization signal block, a symbol set as a downlink or flexible by time division multiplexing, a symbol indicated as a downlink or flexible by a slot format indicator, and a valid occasion for single random access channel transmission, the first valid RO, the last valid RO, the RO on which the random access channel is actually transmitted first, and the RO on which the random access channel is actually transmitted last. [Note 4] The control unit applies the same beam or the same transmission configuration indicator (TCI) state to the multiple random access channel transmissions, as described in any of the terminals described in Appendix 1 to Appendix 3.

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

[0312] Figure 10 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 (which may also be simply called system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

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

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

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

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

[0317] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).

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

[0319] Furthermore, the user terminal 20 may communicate using at least one of the following methods at each CC: Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

[0320] Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, if NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node.

[0321] Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0322] The core network 30 may 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), and Operation, Administration and Maintenance (Management) (OAM). Multiple functions may be provided by a single network node. Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.

[0323] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0324] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. For example, 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 in at least one of the downlink (DL) and uplink (UL).

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

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

[0327] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0328] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

[0329] Lower-layer control information may be transmitted by PDCCH. The lower-layer control information may include, for example, Downlink Control Information (DCI) which includes scheduling information for at least one of PDSCH and PUSCH.

[0330] Furthermore, the DCI that schedules PDSCH may be called a DL assignment or DL ​​DCI, and the DCI that schedules PUSCH may be called a UL grant or UL DCI. Furthermore, PDSCH may be interpreted as DL data, and PUSCH may be interpreted as UL data.

[0331] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with a particular search space based on the search space configuration.

[0332] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

[0333] PUCCH may transmit uplink control information (UCI) which includes at least one of the following: channel state information (CSI), delivery acknowledgment (e.g., Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell.

[0334] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted when describing various channels.

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

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

[0337] Furthermore, in the wireless communication system 1, the Uplink Reference Signal (UL-RS) may transmit the Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. The DMRS may also be called the User-Specific Reference Signal (UE-specific Reference Signal).

[0338] (base station) Figure 11 shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, transceiver unit 120, transceiver antenna 130, and transmission line interface 140 may be provided.

[0339] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0340] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

[0342] The transmitting / receiving unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0343] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.

[0344] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0345] The transmitting / receiving unit 120 may transmit the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 may also receive the uplink channel, uplink reference signal, etc.

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

[0347] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform processing on data and control information acquired from the control unit 110, for example, at the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (e.g., RLC retransmission control), the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), etc., to generate a bit sequence to be transmitted.

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

[0349] The transmitting / receiving unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 130.

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

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

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

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

[0354] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0355] The transmitting / receiving unit 120 may also transmit settings for multiple random access channel transmission. Based on these settings, the control unit 110 may determine whether a random access channel occasion (RO) for the multiple random access channel transmission conflicts with at least one of the following resources: a symbol instructed for receiving a synchronization signal block, a symbol set as a downlink or flexible by time division multiplexing settings, a symbol instructed as a downlink or flexible by a slot format indicator, or a valid occasion for single random access channel transmission.

[0356] The transmitting / receiving unit 120 may also transmit settings for multiple random access channel transmissions. Based on these settings, the control unit 110 may determine the multiple random access channel occasions (ROs) to be used for each of the multiple random access channel transmissions, and based on a specific RO among the multiple ROs, it may determine at least one of the window start and radio network temporary identifier (RNTI) for monitoring random access responses.

[0357] (User terminal) Figure 12 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0358] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0359] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

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

[0361] The transmitting / receiving unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0362] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223.

[0363] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0364] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.

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

[0366] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc., on data and control information acquired from the control unit 210, etc., to generate a bit sequence to be transmitted.

[0367] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion, and output a baseband signal.

[0368] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.

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

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

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

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

[0373] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources may be, for example, Non Zero Power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources may be at least one of the following: an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.

[0374] In this disclosure, the transmitting and receiving units of the user terminal 20 may consist of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

[0375] The transmitting / receiving unit 220 may also receive settings for multiple random access channel transmissions. Based on these settings, the control unit 210 may determine whether a random access channel occasion (RO) for the multiple random access channel transmissions conflicts with at least one of the following resources: symbols instructed for receiving a synchronization signal block, symbols set as a downlink or flexible by time division multiplexing settings, symbols instructed as a downlink or flexible by a slot format indicator, and valid occasions for single random access channel transmissions.

[0376] If it is determined that the RO will collide with the resource, the control unit 210 may choose not to include the RO in the multiple ROs for the multiple random access channel transmission.

[0377] If it is determined that the RO collides with the resource, the control unit 210 may include the RO in the multiple ROs for multiple random access channel transmission and may not transmit random access channels in the RO.

[0378] The control unit 210 may apply the same beam or the same transmission configuration indicator (TCI) state to the multiple random access channel transmissions.

[0379] The transmitting / receiving unit 220 may also receive settings for multiple random access channel transmissions. Based on these settings, the control unit 210 may determine the multiple random access channel occasions (ROs) to be used for each of the multiple random access channel transmissions, and based on a specific RO among the multiple ROs, it may determine at least one of the window start and radio network temporary identifier (RNTI) for monitoring random access responses.

[0380] The specified RO may be any of the following ROs: the first active RO, the last active RO, the RO from which the random access channel is actually transmitted first, and the RO from which the random access channel is actually transmitted last.

[0381] The specified RO may be one or more ROs that do not conflict with at least one resource of the following: a symbol indicated for receiving a synchronization signal block, a symbol set as a downlink or flexible by time division multiplexing, a symbol indicated as a downlink or flexible by a slot format indicator, and a valid occasion for single random access channel transmission, and may be the first valid RO, the last valid RO, the RO on which the random access channel is actually transmitted first, and the RO on which the random access channel is actually transmitted last.

[0382] The control unit 210 may apply the same beam or the same transmission configuration indicator (TCI) state to the multiple random access channel transmissions.

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

[0384] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

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

[0386] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

[0387] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, processing may be performed by one processor, or by two or more processors simultaneously, sequentially, or by other means. Note that processor 1001 may be implemented using one or more chips.

[0388] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication via the communication device 1004, or to control at least one of the reading and writing of data in the memory 1002 and storage 1003.

[0389] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

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

[0391] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. Memory 1002 may also be called a register, cache, or main memory. Memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of this disclosure.

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

[0393] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitting / receiving unit 120 (220), transmitting / receiving antenna 130 (230), etc., may be implemented by the communication device 1004. The transmitting / receiving unit 120 (220) may be implemented with physically or logically separated implementations of a transmitting unit 120a (220a) and a receiving unit 120b (220b).

[0394] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

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

[0397] (modified version) In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

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

[0399] Here, the neuralelogy may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neuralelogy may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, or specific windowing processes performed by the transceiver in the time domain.

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

[0401] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called a PDSCH (PUSCH) mapping type B.

[0402] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

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

[0404] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0405] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0406] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0407] A TTI with a time length of 1 ms may also be called a normal TTI (TTI in 3GPP Rel.8-12), a long TTI, a normal subframe, a long subframe, or a slot. A TTI shorter than a normal TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, or a slot.

[0408] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

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

[0410] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. Each TTI, subframe, etc., may consist of one or more resource blocks.

[0411] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

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

[0413] A Bandwidth Part (BWP) (also called a partial bandwidth) may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.

[0414] A BWP may include UL BWPs (BWPs for UL) and DL BWPs (BWPs for DL). One or more BWPs may be configured within a single carrier for a UE.

[0415] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0416] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative examples. For instance, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots within a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0417] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or corresponding other information. For example, wireless resources may be indicated by a predetermined index.

[0418] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements that use these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0419] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0420] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

[0421] Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices.

[0422] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof).

[0423] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Element (CE).

[0424] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information).

[0425] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

[0426] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

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

[0428] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0429] In this disclosure, terms such as “precoding,” “precoder,” “weight (precoding weight),” “quasi-co-location (QCL),” “transmission configuration indication state (TCI state),” “spatial relation,” “spatial domain filter,” “transmit power,” “phase rotation,” “antenna port,” “layer,” “number of layers,” “rank,” “resource,” “resource set,” “beam,” “beam width,” “beam angle,” “antenna,” “antenna element,” “panel,” “UE panel,” “transmitting entity,” and “receiving entity” may be used interchangeably.

[0430] In this disclosure, "antenna port" may be interpreted interchangeably with "antenna port for any signal / channel" (e.g., a Demodulation Reference Signal (DMRS) port). In this disclosure, "resource" may be interpreted interchangeably with "resource for any signal / channel" (e.g., a reference signal resource, an SRS resource, etc.). Resources may include time / frequency / code / spatial / power resources. Furthermore, a spatial domain transmit filter may include at least one of a spatial domain transmit filter and a spatial domain receive filter.

[0431] The above group may include, for example, at least one of the following: a spatial relationship group, a code division multiplexing (CDM) group, a reference signal (RS) group, a control resource set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, or a panel group.

[0432] Furthermore, in this disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), RS, etc., may be interpreted as being interchangeable.

[0433] Furthermore, in this disclosure, TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc., may be interpreted interchangeably.

[0434] Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL properties," "specific QCL type (e.g., type A, type D) properties," and "specific QCL type (e.g., type A, type D)" may be interpreted as interchangeable.

[0435] In this disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, subset, etc., may be interpreted interchangeably.

[0436] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information (TCI state)" may be interpreted as mutually exclusive as "a set of spatial relationship information (TCI state)," "one or more spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive. Spatial relationship information and spatial relationship may be interpreted as mutually exclusive.

[0437] In this 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" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0438] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0439] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information.

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

[0441] A mobile station may also be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term.

[0442] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.

[0443] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.

[0444] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0445] Figure 14 shows an example of a vehicle according to one 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, a pneumatic 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.

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

[0447] The electronic control unit 49 consists of a microprocessor 61, memory (ROM, RAM) 62, and communication ports (e.g., input / output (IO) ports) 63. Signals from various sensors 50-58 installed in the vehicle are input to the electronic control unit 49. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

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

[0449] The information service unit 59 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, displays, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

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

[0451] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver assistance functions or autonomous driving functions.

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

[0453] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

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

[0455] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 59 installed in the vehicle. The information service unit 59 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 60).

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

[0457] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, uplink channel and downlink channel may be interpreted as sidelink channel.

[0458] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.

[0459] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes with base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0460] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements in an exemplary order and are not limited to that specific order.

[0461] Each aspect / embodiment described in this disclosure includes Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (where x is, for example, an integer or 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®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), and IEEE This may apply to systems utilizing 802.20, Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, as well as next-generation systems that are extended, modified, created, or defined based on these. It may also apply to combinations of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

[0462] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0463] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0464] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to include judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0465] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0466] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" something like resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" may be considered as "judging (deciding)" something about an action. In this disclosure, "judgment (decision)" may be interpreted interchangeably with the actions described above.

[0467] Furthermore, in this disclosure, “determine / determining” may be interpreted as “assume / assuming,” “expect / expecting,” or “consider / considering.” In addition, in this disclosure, “not assuming that…” may be interpreted as “assuming that…”

[0468] In this disclosure, “expect” may be interpreted as “be expected.” For example, “expect(s) …” (where “...” may be expressed as a that clause, an infinitive, etc.) may be interpreted as “be expected ….” “does not expect …” may be interpreted as “be not expected ….” Furthermore, “An apparatus A is not expected …” may be interpreted as “An apparatus B other than apparatus A does not expect …” (for example, if apparatus A is a UE, apparatus B may be a base station).

[0469] The term "maximum transmit power" as used in this disclosure may mean the maximum value of the transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0470] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0471] In this disclosure, when two elements are connected, they can be considered to be “connected” or “coupled” to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, or optical domain (both visible and invisible).

[0472] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0473] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0474] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0475] In this disclosure, terms such as "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. Furthermore, in this disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").

[0476] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.

[0477] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "B based on A", "B during / while A", "B before A", "B at (the same time as) / on A", "B after A", "B since A", and "B until A" may be interchangeable. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately 0 (immediately after or immediately before). A time offset may also be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on the information provided.

[0478] In this disclosure, timing, time, duration, time instance, any unit of time (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc., may be interpreted interchangeably.

[0479] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The descriptions herein are illustrative and not intended to be restrictive in any way to the invention described herein.

Claims

1. A receiving unit that receives settings for multiple random access channel transmissions, A terminal having, based on the above settings, a control unit that determines whether a random access channel occasion (RO) for multiple random access channel transmissions conflicts with at least one resource, which includes symbols instructed for receiving a synchronization signal block, symbols configured as a downlink or flexible by time division multiplexing, symbols instructed as a downlink or flexible by a slot format indicator, and valid occasions for single random access channel transmission.

2. If the RO is determined to be in conflict with the resource, the control unit does not include the RO in the plurality of ROs for the plurality of random access channel transmissions, as per claim 1.

3. If the RO is determined to be in conflict with the resource, the control unit includes the RO in the plurality of ROs for transmitting the plurality of random access channels and does not transmit random access channels in the RO, as described in claim 1.

4. The terminal according to claim 1, wherein the control unit applies the same beam or the same transmission configuration indicator (TCI) state to the multiple random access channel transmissions.

5. The steps include receiving the settings for multiple random access channel transmissions, A wireless communication method for a terminal, comprising the step of determining whether a random access channel occasion (RO) for multiple random access channel transmissions, based on the above settings, conflicts with at least one resource among symbols instructed for receiving a synchronization signal block, symbols configured as downlink or flexible by time division multiplexing settings, symbols instructed as downlink or flexible by a slot format indicator, and valid occasions for single random access channel transmission.

6. A transmission unit that transmits settings for multiple random access channel transmissions, A base station having a control unit that determines, based on the above settings, whether a random access channel occasion (RO) for multiple random access channel transmissions conflicts with at least one resource, which includes symbols indicated for receiving a synchronization signal block, symbols set as downlink or flexible by time division multiplexing settings, symbols indicated as downlink or flexible by a slot format indicator, and valid occasions for single random access channel transmission.

Images