Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure is provided with: a reception unit that receives settings for transmission of a plurality of random access channels; and a control unit that determines, on the basis of the setting, whether a random access channel occasion (RO) for the plurality of random access channel transmissions collides with at least one of the following resources: a symbol indicated for reception of a synchronization signal block; a symbol set as a downlink or flexible symbol by time division multiplexing setting; a symbol indicated as a downlink or flexible by a slot format indicator; and an effective opportunity for single random access channel transmission.

Description

TECHNICAL FIELD

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

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) is standardized for the purpose of further higher-speed data rates, lower delay, and so on (Non-Patent Literature 1). Further, LTE-Advanced (3GPP Rel. 10-14) is standardized for the purpose of further larger capacity, higher density, and so on of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

[0003] A subsequent system of LTE (for example, also referred to as a 5th generation mobile communication system (5G), 5G+, a 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 onwards, and so on) is also being researched.

[0004] PRIOR ART DOCUMENTS

[0005] NON-PATENT LITERATURE

[0006] Non-Patent Literature 1: 3GPP TS 36.300 V8.12.0 "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)", April 2010 SUMMARY

[0007] PROBLEMS TO BE SOLVED BY THE INVENTION

[0008] In a future wireless communication system (for example, NR), improvement of coverage is being researched.

[0009] However, a random access procedure for coverage improvement is not clear. If such a random access procedure is not clear, there is a concern that communication throughput decreases.

[0010] Therefore, the present disclosure aims to provide a terminal, a wireless communication method, and a base station that improve coverage of a random access procedure.

[0011] Means for solving the problem

[0012] A terminal according to an aspect of the present disclosure includes a reception unit that receives a plurality of random access channel transmissions of a configuration, and a control unit that determines, based on the configuration, whether a random access channel occasion (RO) for the plurality of random access channel transmissions collides with at least one of a symbol indicated for reception of a synchronization signal block, a symbol configured as downlink or flexible by time division multiplexing configuration, a symbol indicated as downlink or flexible by a slot format indicator, and a valid occasion for a single random access channel transmission.

[0013] Effects of the Invention

[0014] According to an aspect of the present disclosure, it is possible to improve coverage of a random access procedure. BRIEF DESCRIPTION OF DRAWINGS

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

[0016] Figure 2A And Figure 2B An example of association of PRACH opportunities and beams is shown.

[0017] Figure 3 An example of RAR window is shown.

[0018] Figure 4 An example of RO group is shown.

[0019] Figure 5 An example of RA-RNTI collision is shown.

[0020] Figure 6 An example of case 1 of RO / RA-RNTI collision in multiple repetitions of PRACH is shown.

[0021] Figure 7 An example of case 2 of RO / RA-RNTI collision in multiple repetitions of PRACH is shown.

[0022] Figure 8 An example of collision of RO within RO group for multiple PRACH transmissions and specific resources is shown.

[0023] Figure 9An example of a dedicated RO.

[0024] Figure 10 FIG. 1 is a diagram showing an example of an outline configuration of a wireless communication system according to an embodiment.

[0025] Figure 11 FIG. 2 is a diagram showing an example of a configuration of a base station according to an embodiment.

[0026] Figure 12 FIG. 3 is a diagram showing an example of a configuration of a user terminal according to an embodiment.

[0027] Figure 13 FIG. 4 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment.

[0028] Figure 14 FIG. 5 is a diagram showing an example of a vehicle according to an embodiment. DETAILED DESCRIPTION

[0029] (TCI, spatial relation, QCL)

[0030] In NR, it is under study to control at least one of reception processing (for example, at least one of reception, demapping, demodulation, and decoding) and transmission processing (for example, at least one of transmission, mapping, precoding, modulation, and coding) of a signal / channel in a UE based on a transmission configuration indication state (TCI state) for at least one of a signal / channel.

[0031] The TCI state can also mean a TCI state applied to a downlink signal / channel. What is equivalent to a TCI state applied to an uplink signal / channel can also be expressed as a spatial relation.

[0032] The so-called TCI state is information related to quasi-co-location (QCL) of a signal / channel, and can also be referred to as spatial reception parameters, spatial relation information, and the like. The TCI state can also be set to a UE per channel or per signal.

[0033] QCL is an indicator of the statistical properties of a signal / channel. For example, it can also mean that when a signal / channel has a QCL relationship with other signals / channels, it can be assumed that at least one of the following is the same (QCL) among these different signals / channels: Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter).

[0034] Additionally, the spatial reception parameters may also correspond to the UE's receive beam (e.g., receive analog beam), and the beam may also be determined based on the spatial QCL. The QCL (or at least one element of the QCL) in this disclosure may also be rewritten as sQCL (spatial QCL).

[0035] A QCL can also be specified with multiple types (QCL types). For example, four different QCL types (AD) can be set that can be assumed to have the same parameter (or parameter set), represented as follows:

[0036] • QCL Type A (QCL-A): Doppler shift, Doppler spread, average delay, and delay spread;

[0037] • QCL Type B (QCL-B): Doppler shift and Doppler extension;

[0038] • QCL Type C (QCL-C): Doppler shift and average delay;

[0039] • QCL Type D (QCL-D): Spatial reception parameters.

[0040] The situation in which a UE assumes a relationship between a Control Resource Set (CORESET), channel, or reference signal and other CORESETs, channels, or reference signals in a specific QCL (e.g., QCL type D) is also called a QCL assumption.

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

[0042] The TCI state can also be, for example, information related to the QCL between the target channel (in other words, the reference signal (RS) used by the channel) and other signals (e.g., other RSs). The TCI state can also be set (indicated) by higher-layer signaling, physical-layer signaling, or a combination thereof.

[0043] Physical layer signaling can also be, for example, downlink control information (DCI).

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

[0045] Furthermore, the RS that is related to the channel as QCL can be at least one of the following: a Synchronization Signal Block (SSB), a Channel State Information Reference Signal (CSI-RS), a Measurement Reference Signal (Sounding Reference Signal (SRS)), a Tracking CSI-RS (also known as a Tracking Reference Signal (TRS)), or a QCL Detection Reference Signal (also known as a QRS).

[0046] An SSB is a block of signals that includes at least one primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a broadcast channel (physical broadcast channel (PBCH)). An SSB can also be referred to as an SS / PBCH block.

[0047] The RS of QCL type X in TCI state can also refer to the RS that is in a relationship of QCL type X with a certain channel / signal (DMRS), and the RS can also be called the QCL source of QCL type X in TCI state.

[0048] (Initial access process)

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

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

[0051] The SSB has a bandwidth of 20 RBs and a duration of 4 symbols. The SSB transmission period can be set from {510, 20, 40, 80, 160} ms. Within a half-frame, multiple symbol positions of the SSB are specified based on the frequency range (FR1, FR2).

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

[0053] System information consists of MIB, RMSI (SIB1), and other system information (OSI) transmitted via PBCH. SIB1 contains information for RACH setup and the RACH process. The time / frequency resource relationship between SSB and SIB1, monitored by PDCCH, is set via PBCH.

[0054] A base station using beam correspondence transmits multiple SSBs using multiple beams in each SSB transmission cycle. Each SSB has its own SSB index. A UE that detects an SSB transmits a PRACH in the RACH opportunity associated with that SSB index and receives a RAR within the RAR window.

[0055] (Beam and coverage)

[0056] In high-frequency bands, if beamforming is not applied to the synchronization / reference signals, the coverage area narrows, making it difficult for the UE to detect the base station. Conversely, if beamforming is applied to the synchronization / reference signals to ensure coverage, strong signals will arrive in specific directions, but signals will become more difficult to reach in other directions. At the base station before the UE connects, if the UE's location is unclear, it's impossible to use beams only in the appropriate direction to transmit the synchronization / reference signals. Consider the following approach: the base station transmits multiple synchronization / reference signals with beams in different directions, and the UE identifies which beam it has detected. If a thin (narrow) beam is used for coverage, more synchronization / reference signals need to be transmitted, thus raising concerns about increased overhead and reduced frequency utilization efficiency.

[0057] If a coarse (wide) beam is used to reduce overhead by minimizing the number of beams (synchronization / reference signals), the coverage area will be narrowed.

[0058] In future wireless communication systems (e.g., 6G), the utilization of frequency bands such as millimeter waves and terahertz waves is expected to be further developed. The idea is to provide communication services by using a large number of thin beams to construct cell areas / coverage.

[0059] Consider using existing FR2 to expand the coverage area, or using a higher frequency band than existing FR2. To achieve these goals, in addition to multiple TRPs, reconfigurable intelligent surfaces (RIS), and other technologies, improved beam management is preferred.

[0060] PRACH coverage enhancement is under investigation. For example, it is being investigated to use multiple PRACH transmissions with the same beam during a 4-step RACH process (multiple repetitions of PRACH), and multiple PRACH transmissions with different beams during a 4-step RACH process. This PRACH enhancement can be applied to either frequency range (FR)2 or FR1. This PRACH extension can be applied to both short PRACH formats and other formats.

[0061] For multiple PRACH transmissions with the same beam, a single RAR window can be used for each PRACH transmission. This RAR window can also follow existing designs. Alternatively, for multiple PRACH transmissions with the same beam, a single RAR window can be used for all of the multiple PRACH transmissions.

[0062] The UE can also use different multiple transmit (Tx) beams in the transmission of multiple PRACHs across multiple ROs associated with the same SSB / CSI-RS.

[0063] (PRACH)

[0064] like Figure 1 As shown, the common RACH configuration (RACH-ConfigCommon) can also include the general RACH configuration (rach-ConfigGeneric), the total number of RA preambles (totalNumberOfRA-Preambles), the SSB for each RACH opportunity, and the contention-based (CB) preambles for each SSB (ssb-perRACH-OccasionAndCB-PreamblesPerSSB). The rach-ConfigGeneric can also include the prach-ConfigurationIndex and the message 1FDM (msg1-FDM, the number of RACH opportunities FDMned within a time instance). ssb-perRACH-OccasionAndCB-PreamblesPerSSB can also be 1 / 8 of the number of SSBs for each RACH opportunity (one-eighth, one SSB associated with 8 RACH opportunities), including the number of CB preambles for each SSB.

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

[0066] For a Type 1 random access procedure, or for a Type 2 random access procedure (2-step random access procedure, message A / B) with a PRACH opportunity set independently of the Type 1 random access procedure, if N < 1, an SS / PBCH block is mapped to 1 / N consecutive valid RACH opportunities, for each valid PRACH opportunity, R CB preambles associated with consecutive indices of the SS / PBCH block index begin from preamble index 0. If N >= 1, for each valid PRACH opportunity, R CB preambles associated with consecutive indices of the SS / PBCH block index n (0 <= n < -N-1) begin from preamble index n·N_preamble^total / N. Here, N_preamble^total is given by totalNumberOfRA-Preambles for Type 1 random access procedures, and by msgA-TotalNumberOfRA-Preambles for Type 2 random access procedures that involve setting PRACH opportunities independently of Type 1 random access procedures. N_preamble^total is a multiple of N.

[0067] Starting from frame 0, the association period used to map SS / PBCH blocks to PRACH opportunities is the minimum value within the set determined by the relationship between the PRACH configuration period and the association period (the number of PRACH configuration periods) (as specified in the specification), so that N Tx SSB Each SS / PBCH block index is mapped to a PRACH opportunity at least once during the association period. Here, the UE obtains N based on the value of the in-burst SSB position (ssb-PositionsInBurst) within SIB1 or the ServingCellConfigCommon setting. Tx SSB If, after an integer number of mapping cycles from the SS / PBCH block index to the PRACH opportunity during the association period, there are unmapped N...Tx SSB In the case of a set of PRACH opportunities or PRACH preambles for an SS / PBCH block index, an SS / PBCH block index is not mapped to that set of PRACH opportunities or PRACH preambles. An association mode period contains more than one association period and is determined to cause the pattern between PRACH opportunities and SS / PBCH block indices to repeat at a maximum of every 160ms. If there is a PRACH opportunity not associated with an SS / PBCH block index after an integer number of association periods, that PRACH opportunity is not used for PRACH.

[0068] In the case of PRACH transmissions triggered by higher layers (not PRACH transmissions triggered by PDCCH commands), if an ssb-ResourceList is provided, the PRACH mask index is represented by ra-ssb-OccasionMaskIndex. This ra-ssb-OccasionMaskIndex indicates that the PRACH opportunity is the PRACH opportunity used for a PRACH transmission associated with the selected SS / PBCH block index.

[0069] PRACH opportunities are mapped sequentially for each of the corresponding SS / PBCH block indices. For each SS / PBCH block index and each mapping period of consecutive PRACH opportunities, the index appending of the PRACH opportunity represented by the mask index value is reset. In the initial mapping period that is available, the UE selects the PRACH opportunity represented by the PRACH mask index value for the indicated SS / PBCH block index for PRACH transmission.

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

[0071] • First, the order in which the frequency resource indexes for PRACH opportunities used for frequency reuse are added.

[0072] Second, the order in which the time resource indexes for PRACH opportunities used for time multiplexing within PRACH slots are added.

[0073] Third, the PRACH slot index is in ascending order.

[0074] For PRACH transmissions triggered by requests from higher layers, if csirs-ResourceList is provided, the value of ra-OccasionList represents a list of PRACH opportunities for transmission, associated with CSI-RS indices represented by csi-RS and selected. The index appended to the PRACH opportunities represented by ra-OccasionList is reset during each association pattern.

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

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

[0077] Figure 2A This illustrates an example (mapping 1) of the association between PRACH opportunities (RACH opportunities (ROs)) and beams (SSB / CSI-RS) based on the higher-level parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB. In the case where ssb-perRACH-OccasionAndCB-PreamblesPerSSB represents oneHalf, n16 (half, n16) (N=1 / 2, R=16), and msg1-FDM is 4, in one time instance, 4 ROs are FDMed, and one SSB is mapped to 2 ROs. Preamble indices 0 to 15 are associated with 2 ROs, and preamble indices 0 to 15 are associated with SSB0. In this way, when N<1, one SSB is mapped to multiple ROs. This increases the RO capacity of each beam.

[0078] Figure 2BThis illustrates another example (mapping 2) of the association between ROs and beams based on the higher-level parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB. In the case where ssb-perRACH-OccasionAndCB-PreamblesPerSSB represents n4, n16 (N=4, R=16), msg1-FDM is 4, and N_preamble^total is 64, in one time instance, 4 ROs are FDMed, and 4 SSBs are mapped to one RO. SSB#0 through #3 are associated with one RO. Preamble indices #0 through #15 are associated with SSB#0, preamble indices #16 through #31 are associated with SSB#1, preamble indices #32 through #47 are associated with SSB#2, and preamble indices #48 through #63 are associated with SSB#3. In this way, the same RO is associated with different SS / PBCH block indices, and different preambles use different SS / PBCH block indices. The base station can distinguish the associated SS / PBCH block index by receiving the PRACH.

[0079] The random access preamble can only be transmitted within the time resources specified in the random access configuration of the specification, depending on whether it is FR1 or FR2, and the spectrum type (paired spectrum / supplementary uplink (SUL) / unpaired spectrum). The PRACH configuration index is given by the higher-layer parameter prach-ConfigurationIndex, or by msgA-PRACH-ConfigurationIndex if it is 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 opportunities N_t^RA,slot in the PRACH slot, and PRACH duration N_dur^RA.

[0080] The type of RACH process that is triggered varies depending on the purpose, such as whether the PRACH repetition can be applied to a particular scenario. The type of RACH process can also be at least one of the following.

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

[0082] • Contention-based random access (CBRA), RA triggered by MAC entities, RA triggered by RRCs associated with events, CBRA for BFR, etc.

[0083] • 4-step RACH.

[0084] • 2-step RACH.

[0085] (PDCCH command)

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

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

[0088] (The Random Access Procedure initialization in the MAC entity)

[0089] The random access procedure is initiated by a PDCCH command, the MAC entity itself, or an RRC for a compliant event. Within a MAC entity, there is only one random access procedure in progress at any given time. The random access procedure for an SCell is initiated only by a PDCCH command accompanied by a ra-PreambleIndex other than 0b000000.

[0090] When a random access procedure is initiated on the serving cell, the MAC entity performs the following operations.

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

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

[0093] • 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.

[0094] • When an SSB is selected as described above, the next available PRACH opportunity is determined from the PRACH opportunities corresponding to the selected SSB, which are allowed by the constraints given by ra-ssb-OccasionMaskIndex (the MAC entity randomly selects a PRACH opportunity with equal probability from consecutive PRACH opportunities, corresponding to the selected SSB, according to the specification. The MAC entity may also consider the possibility of generating a measurement gap when determining the next available PRACH opportunity corresponding to the selected SSB).

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

[0096] If a random access procedure is initiated via a PDCCH command, and if requested via a higher layer, the UE, as described in the specification, transmits a PRACH within the selected PRACH opportunity if the time between the last symbol received from the PDCCH command and the first symbol transmitted from the PRACH is N_(T,2) + Δ_BWPSwitching + Δ_Delay + T_switch[msec] or more (time condition). Here, N_(T,2) is the duration of the N_2 symbol corresponding to the PUSCH preparation time of UE processing capability 1. It is assumed that μ corresponds to the minimum SCS setting between the subcarrier spacing (SCS) setting of the PDCCH command and the corresponding SCS setting of the PRACH transmission. Δ_BWPSwitching = 0 if the UL BWP activation remains unchanged; otherwise, Δ_BWPSwitching is defined in the specification. In FR1, Δ_delay = 0.5 msec, and in FR2, Δ_delay = 0.25 msec. T_switch is the duration of the switching gap as defined in the specification.

[0097] (Conditions for the validity / invalidity of a PRACH opportunity (validity conditions))

[0098] In paired spectrum (FDD) or SUL band domain, all PRACH opportunities are valid. In unpaired spectrum (TDD), PRACH opportunities may also follow rules 1 and 2 below.

[0099] [Rule 1]

[0100] If the UE is not provided with tdd-UL-DL-ConfigurationCommon, the PRACH opportunity within the PRACH slot does not precede the SS / PBCH block within the PRACH slot, and the PRACH opportunity is valid only if it begins at least N_gap symbols after the last SS / PBCH block reception symbol. Here, N_gap is specified in the specification. When channelAccessMode=semistatic is provided, the set of consecutive symbols preceding the start of the next channel occupancy time before which the UE does not transmit is not overlapped. The candidate SS / PBCH block index corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon.

[0101] [Rule 2]

[0102] When the UE is provided with tdd-UL-DL-ConfigurationCommon, the PRACH opportunity within the PRACH slot is valid under the following conditions.

[0103] • The PRACH opportunity lies within the UL code. Alternatively,

[0104] The PRACH opportunity does not precede the SS / PBCH block within the PRACH slot, but begins at least N_gap symbols after the last DL symbol and at least N_gap symbols after the last SS / PBCH block symbol. Here, N_gap is specified in the specification. If channelAccessMode=semistatic is provided, the PRACH opportunity, as described in the specification, does not overlap with the set of consecutive symbols preceding the start of the next channel occupancy period without any transmission. The candidate SS / PBCH block index, as described in the specification, corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst within SIB1 or ServingCellConfigCommon.

[0105] (RAR window)

[0106] The RA Response Window (ra-ResponseWindow) is a time window used to monitor RA responses (RARs) (SpCell only). The RA Contention Resolution Timer (ra-ContentionResolutionTimer) is a timer for RA contest resolution (SpCell only). The Msg.B Response Window is a time window used to monitor RA responses (RARs) for 2-step RA types (SpCell only).

[0107] In this disclosure, SpCell, primary cell (PCell) and primary secondary cell (PSCell) can also be rewritten to each other.

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

[0109] [Operation 1]

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

[0111] [[Operation 1-1]]

[0112] The MAC entity begins to be configured in the ra-ResponseWindow within the BFR settings (BeamFailureRecoveryConfig) during the initial PDCCH opportunity following the end of the RA preamble transmission.

[0113] [[Operations 1-2]]

[0114] During the operation of the ra-ResponseWindow, the MAC entity monitors PDCCH transmissions in the search space indicated by the BFR of the SpCell identified by C-RNTI using the search space ID (recoverySearchSpaceId).

[0115] [Operation 2]

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

[0117] [[Operation 2-1]]

[0118] The MAC entity begins to use the ra-ResponseWindow set within the common RACH settings (RACH-ConfigCommon) during the initial PDCCH opportunity following the end of the RA preamble transmission.

[0119] [[Operation 2-2]]

[0120] During the operation of ra-ResponseWindow, the MAC entity monitors the PDCCH transmission of the SpCell used by RAR, which is identified by RA-RNTI.

[0121] [Operation 3]

[0122] If the ra-ResponseWindow set in BeamFailureRecoveryConfig expires and the PDCCH sent by the recoverySearchSpaceId to C-RNTI is received on the serving cell where the preamble was sent, or if the ra-ResponseWindow set in RACH-ConfigCommon expires and the RAR containing RA preamble identifiers consistent with the 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.

[0123] The MAC entity can also stop the ra-ResponseWindow after successfully receiving a RAR containing RA preamble identifiers that match the sent PREAMBLE_INDEX (and can also stop monitoring for RAR).

[0124] For PDCCH monitoring within the RA response window, there are two scenarios: PDCCH used for the base station's response to the BFR, and PDCCH used for the RAR. The following content can also be applied to both scenarios.

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

[0126] [Operation 4]

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

[0128] The msgB-ResponseWindow may also begin with the first symbol of the earliest CORESET of the PDCCH for a Type 1-PDCCH CSS set when the UE is configured to receive such a symbol, which is at least one symbol following the last symbol of the PRACH opportunity corresponding to the PRACH transmission. The length of the msgB-ResponseWindow may also correspond to the SCS used for the Type 1-PDCCH CSS set.

[0129] [Operation 5]

[0130] The MAC entity monitors the PDCCH transmission of the SpCell used by the RAR, identified by MSGB-RNTI, during the operation of the msgB-ResponseWindow.

[0131] [Operation 6]

[0132] If the MSGA contains a C-RNTI MAC CE, the MAC entity monitors the PDCCH transmission of the SpCell used by the RAR identified by the C-RNTI during the operation of the msgB-ResponseWindow.

[0133] (RA-RNTI (MAC protocol specification: Random Access Preamble transmission))

[0134] The RA-RNTI associated with the PRACH opportunity of sending the RA preamble is calculated as follows.

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

[0136] Here, s_id is the index of the initial OFDM symbol of the PRACH opportunity (0 <= s_id < 14 (number of symbols in the time slot)). t_id is the index of the initial time slot of the PRACH opportunity within the system frame (0 <= t_id < 80 (number of time slots within the system frame with an SCS of 120 kHz)). The subcarrier spacing (SCS) used to determine t_id is based on the value of μ. f_id is the index of the PRACH opportunity in the frequency domain (0 <= f_id < 8 (maximum number of FDM PRACH opportunities)). ul_carrier_id is the UL carrier used for RA preamble transmission (0 for normal uplink (NUL) carrier, 1 for supplementary uplink (SUL) carrier). RA-RNTI is calculated according to the specification. RA-RNTI is the RNTI used for 4-step RACH.

[0137] The MSGB-RNTI associated with the PRACH opportunity of sending the RA preamble is calculated as follows.

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

[0139] +14×80×8×2

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

[0141] The total number of RA-RNTI values ​​(the total number of PRACH opportunities within a system frame) is 14 × 80 × 8 × 2. The formula for MSGB-RNTI is the formula for RA-RNTI plus the total number of RA-RNTI values. According to this formula, conflicts between MSGB-RNTI and RA-RNTI can be avoided.

[0142] (RAR surveillance)

[0143] According to the PRACH transmission, the UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI within a window controlled by the aforementioned higher layers. This window begins in the initial symbol of the earliest CORESET of the PDCCH for the Type 1-PDCCH CSS set, i.e., after at least one symbol of the last symbol of the PRACH opportunity corresponding to the PRACH transmission. This symbol period corresponds to the SCS for the Type 1-PDCCH CSS set. The length of this window is based on the SCS for the Type 1-PDCCH CSS set and is provided by ra-responseWindow as the number of time slots.

[0144] If the UE detects a DCI format 1_0 containing a CRC scrambled by the corresponding RA-RNTI and the LSBs of the SFN field in the DCI format that are the same as the least significant bits (LSBs) of the system frame number (SFN) that the UE sent the PRACH with, and the UE receives a transport block in the corresponding PDSCH, regardless of whether the UE is provided with a CORESET for receiving a PDCCH with the DCI format 1_0, the UE can also assume the same DMRS antenna port QCL properties for the SS / PBCH block or CSI-RS resources used by the UE in the association of the PRACH.

[0145] If the UE attempts to detect DCI format 1_0 accompanied by a CRC scrambled by the corresponding RA-RNTI when sending a PRACH initiated by a PDCCH command that triggers a CFRA procedure for the SpCell, the UE may also assume that the PDCCH containing this DCI format 1_0 and the PDCCH command have the same DMRS antenna port QCL properties. Similarly, if the UE attempts to detect DCI format 1_0 accompanied by a CRC scrambled by the corresponding RA-RNTI when sending a PRACH initiated by a PDCCH command that triggers a CFRA procedure for the subcell, the UE may also assume that the DMRS antenna port QCL properties associated with the CORESET for receiving the PDCCH containing this DCI format 1_0 are valid.

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

[0147] In single-cell operation or operation accompanied by carrier aggregation within the same frequency band, if the qcl-Type of the 'typeD' property setting of the DMRS used for monitoring PDCCH in the type 1-PDCCHCSS set is not set to be the same as the qcl-Type of the 'typeD' property setting of the DMRS used for monitoring PDCCH in the type 0 / 0A / 0B / 2 / 3-PDCCHCSS 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-PDCCHCSS set at least in one symbol, the UE does not intend to monitor the PDCCH in the type 0 / 0A / 0B / 2 / 3-PDCCHCSS set or the USS set.

[0148] If the UE is provided with one or more search space sets via PDCCH-Config, through searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, peiSearchSpace, ra-SearchSpace, and CSS sets, and is provided with SI-RNTI, P-RNTI, PEI-RNTI, RA-RNTI, MsgB-RNTI, SFI-RNTI, INT-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI, in each time slot, the UE does not intend to process information from more than one DCI format from the CRC scrambled with the use of that RNTI.

[0149] (Message 3 PUSCH (Msg3 PUSCH))

[0150] The UE transmits transport blocks in the PUSCH scheduled by the RAR UL permission within the corresponding RAR message. The UE transmits transport blocks in time slot n+k2+Δ+2. μ ·K cell,offset Within, send the PUSCH. K cell,offset The value is provided via CellSpecific_Koffset; if not provided, K... cell,offset =0.

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

[0152] If the UE repeatedly requests PUSCH transmissions, the UE will cross N PUSCH repeat Each time slot is used to send PUSCH. Here, N... PUSCH repeat In other words, it is indicated from the set of 4 values ​​provided by numberOfMsg3Repetitions, or from {1, 2, 3, 4} if numberOfMsg3Repetitions is not provided, by the 2MSB of the MCS field within the RAR UL license or DCI format 0_0.

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

[0154] The UE can request Msg3PUSCH repetition via dedicated PRACH resources. The MAC entity selects RA resources in the following situations: that is, there exists more than one set of available RA resources, and one of these sets is used in the indications for all functions triggering the RA procedure; and that there exists a set of more than one available RA resources scheduled with indications for a subset of all functions triggering the RA procedure. When Msg3 repetition is configured for a set of RA resources, the MAC entity considers that set of RA resources unusable for the RACH procedure if Msg3 repetition is not available.

[0155] RA resources can also be partitioned for each function. A function can include at least one of Msg3 repetition, reduced capacity (RedCap) , small data transmission (SDT) , or RAN slicing.

[0156] The following information is notified within SIB1 transmitted via the base station.

[0157] • Function priority (featurePriorities-r17). This priority is used to determine which FeatureCombinationPreamble the UE should use if a function is mapped to more than one FeatureCombinationPreamble (feature combination preamble setting).

[0158] • Add RO settings. This setting includes available functions (which are associated with multiple functions), RA resources (e.g., preamble index), and mask indexes used to distinguish ROs.

[0159] The UE depends on this function to determine the RO to use.

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

[0161] BWP-UplinkCommon can also contain RACH common settings (RACH-ConfigCommon or MsgA-ConfigCommon) and additionalRACH-ConfigList-r17 (additional RACH settings list). additionalRACH-ConfigList-r17 can also contain rsrp-ThresholdMsg3-r17 (threshold).

[0162] The RACH public settings can also include FeatureCombinationPreambles. FeatureCombinationPreambles associate a set of preambles (partitions) with a feature combination. FeatureCombinationPreambles can also include FeatureCombination (feature combination setting), startPreambleForThisPartition (index of the initial preamble), numberOfPreamblesPerSSB-ForThisPartition (number of preambles), and ssb-SharedRO-MaskIndex-r17 (PRACH mask index). FeatureCombination includes at least one of redCap, smallData (SDT), sliceGroup (RAN slicing), and msg3-Repetition (Msg3 repetition). The partition is given by the index of the initial preamble and the number of preambles.

[0163] The available ROs are explicitly set using the PRACH mask index. Utilizing the relationship between the PRACH mask index and the licensed PRACH opportunities (ROs) of the SSB (MAC protocol specification / PRACH mask index value table), at least one of PRACH opportunity indices 1 to 8 can be set.

[0164] The number of Msg3 repeats is indicated by the two most significant bits (MSB) of the modulation and coding scheme (MCS) field within the RAR UL license.

[0165] In PUSCH repetition type A, when a PUSCH is sent that is scheduled via RAR UL permission, the 2MSB of the MCS information field of that RAR UL permission provides code points for determining the repetition number K based on whether the higher-layer parameter numberOfMsg3Repetitions is set, according to the relationship between the value of the 2MSB of the MCS information field (code points) and the repetition number K (table). The number of time slots N used to determine the transport block size (TBS) is equal to 1.

[0166] In PUSCH repetition type B, when transmitting PUSCH scheduled via DCI format 0_0, where DCI format 0_0 is accompanied by CRC scrambled via TC-RNTI, the 2MSB of the MCS information field of this DCI format, based on whether the higher-layer parameter numberOfMsg3Repetitions is set, provides code points for determining the repetition number K according to the relationship (table) between the value of the 2MSB of the MCS information field (code points) and the repetition number K. The number of time slots N used for TBS determination is equal to 1.

[0167] (Contention resolution)

[0168] If Msg3 is sent, the MAC entity follows steps 1 through 4 below.

[0169] [Operation 1]

[0170] If Msg3 is transmitted on a non-terrestrial network, the MAC entity starts the ra-ContentionResolutionTimer and restarts the HARQ retransmission within the initial symbol after the UE-gNB RTT is estimated by the UE at the end of Msg3.

[0171] [Operation 2]

[0172] Otherwise, if the Msg3 transmission (initial transmission or HARQ retransmission) is scheduled to be accompanied by repeated A PUSCH, the MAC entity starts or restarts the ra-ContentionResolutionTimer within the first symbol after all repeated Msg3 transmissions have ended.

[0173] [Operation 3]

[0174] Otherwise, the MAC entity starts or restarts the ra-ContentionResolutionTimer within the initial symbol after the Msg3 transmission ends.

[0175] [Operation 4]

[0176] The MAC entity monitors the PDCCH while the ra-ContentionResolutionTimer is operating, regardless of the possibility of a measurement gap occurring.

[0177] Step 4 (Msg4) of the RA process in Rel. 16 NR follows the steps in Step 4 below.

[0178] [Step 4]

[0179] Without providing the UE with a C-RNTI, based on the PUSCH transmission scheduled via RAR UL permission, the UE attempts to detect: a PDSCH containing the UE contention resolution identity, accompanied by a DCI format 1_0 scrambled with the corresponding TCI-RNTI. Upon receiving the PDSCH containing the UE contention resolution identity, the UE transmits HARQ-ACK information within the PUCCH. The PUCCH transmission occurs within the same active UL BWP as the PUSCH transmission. The minimum time between the last symbol of the received PDSCH and the first symbol of the corresponding PUCCH transmission containing the HARQ-ACK information is equal to N_T,1 [msec]. N_T,1 is the duration of the N_T,1 symbol, equivalent to the PDSCH processing time of UE processing capability 1 with appended PDSCH DM-RS configured. For μ=0, the UE assumes N_T,1=14.

[0180] When detecting the DCI format, either by sending a PUSCH according to a PUSCH scheduled via RAR UL permission, or by retransmitting the corresponding PUSCH according to DCI format 0_0 with a CRC scrambled by the TC-RNTI provided in the corresponding RAR message, regardless of whether the TCI state of the CORESET for the PDCCH with the DCI format received by the UE is provided to the UE, the UE may also assume the same DM-RS antenna port QCL properties for transmitting the PDCCH with the DCI format as for the DM-RS antenna port quasi co-location (QCL) properties used by the UE for PRACH association of the SS / PBCH block.

[0181] (SSB / CSI-RS selection (MAC protocol specification: Random Access Resource selection))

[0182] When the RA type (RA_TYPE) is set to 4-step RA, the MAC entity performs the following operations:

[0183] - When the RA process is initiated for SpCell beam failure recovery, and the beam failure recovery timer is operational or not set, the CFRA resource for beam failure recovery requests associated with at least one SSB / CSI-RS is explicitly provided via RRC, and at least one of the SSBs in the candidateBeamRSList with an SS-RSRP exceeding the SS-RSRP threshold (rsrp-ThresholdSSB), and at least one of the CSI-RSs in the candidateBeamRSList with an SS-RSRP exceeding the CSI-RSRP threshold (rsrp-ThresholdCSI-RS), is available, the MAC entity performs the following operations.

[0184] -- The MAC entity selects either one of the multiple SSBs in candidateBeamRSList that has an SS-RSRP exceeding rsrp-ThresholdSSB, or one of the multiple CSI-RSs in candidateBeamRSList that has a CSI-RSRP exceeding rsrp-ThresholdCSI-RS.

[0185] -- If a CSI-RS is selected and there exists a RA preamble index (ra-PreambleIndex) associated with the selected CSI-RS, the MAC entity sets the preamble index (PREAMBLE_INDEX) to: the ra-PreambleIndex in candidateBeamRSList corresponding to the quasi-colocated SSB of the selected CSI-RS that is QCL.

[0186] -- Otherwise, set PREAMBLE_INDEX to: the ra-PreambleIndex corresponding to the SSB or CSI-RS selected from the set of RA preambles used for beam failure recovery requests.

[0187] - Otherwise, if ra-PreambleIndex is explicitly provided via PDCCH and is not 0b000000, the MAC entity sets PREAMBLE_INDEX to the notified ra-PreambleIndex and selects the SSB notified via PDCCH.

[0188] - Otherwise, if the CFRA resources associated with multiple SSBs are explicitly provided in a dedicated RACH setting (rach-ConfigDedicated), and at least one SSB with an SS-RSRP exceeding rsrp-ThresholdSSB is available, the MAC entity selects one of the associated multiple SSBs with an SS-RSRP exceeding rsrp-ThresholdSSB and sets PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected SSB.

[0189] - Otherwise, if the CFRA resources associated with multiple CSI-RS are explicitly provided in a dedicated RACH setting (rach-ConfigDedicated), and at least one CSI-RS among the multiple CSI-RS with a CSI-RSRP exceeding rsrp-ThresholdCSI-RS is available, the MAC entity selects one of the associated multiple CSI-RS with a CSI-RSRP exceeding rsrp-ThresholdCSI-RS and sets PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected CSI-RS.

[0190] - Otherwise, if the RA process is initiated for an SI request and the SI request is explicitly provided via RRC using RA resources, the MAC entity performs the following operations.

[0191] -- If at least one SSB of an SS-RSRP with more than rsrp-ThresholdSSB is available, the MAC entity selects one SSB of the SS-RSRP with more than rsrp-ThresholdSSB.

[0192] -- Otherwise, the MAC entity selects any SSB.

[0193] -- The MAC entity selects the RA preamble corresponding to the selected SSB from the RA preambles that are verified according to the RA preamble start index (ra-PreambleStartIndex), and sets PREAMBLE_INDEX to the selected RA preamble.

[0194] - Otherwise (CBRA preamble selection), the MAC entity performs the following operations.

[0195] -- If at least one SSB of an SS-RSRP with more than rsrp-ThresholdSSB is available, the MAC entity selects one SSB of the SS-RSRP with more than rsrp-ThresholdSSB.

[0196] -- Otherwise, the MAC entity selects any SSB.

[0197] (Type 2 RA process)

[0198] During the MsgA transmission within a Type 2 RA procedure (2-step RA procedure), the UE transmits the following pair ( Figure 3 ):

[0199] - Within the MsgA RACH opportunity (RO), there is a preamble with a preamble index.

[0200] - Within each MsgA PUSCH opportunity (PO) set by MsgA PUSCH, there is one PUSCH with a PUSCH resource unit (PRU).

[0201] MsgA PRACH has the structure of MsgA preamble index (symbol field resource) within MsgA RACH opportunities (time domain resource / frequency domain resource). Figure 4 ).

[0202] MsgA PUSCH has the structure of MsgA PUSCH resource units (symbol domain resources / spatial domain resources) within MsgA PUSCH opportunities (time domain resources / frequency domain resources) within MsgA PUSCH settings (RRC settings).

[0203] Within a MsgA PUSCH opportunity (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.

[0204] (MsgA PUSCH opportunity within a Type 2 RA process)

[0205] The MsgA PUSCH opportunity (PO) that overlaps with the valid RO used in the type 1 / 2RA process is an invalid PO.

[0206] A PUSCH opportunity is valid if it does not overlap in time or frequency with any valid PRACH opportunity associated with a Type 1 RA procedure or a Type 2 RA procedure. For current spectrum (TDD) blocks and SS / PBCH blocks accompanied by an index provided via ssb-PositionsInBurst or ServingCellConfigCommon within SIB1, the UE follows several operations.

[0207] - If the UE is not provided with tdd-UL-DL-ConfigurationCommon, the PUSCH opportunity is valid if the following conditions are met.

[0208] -- This PUSCH opportunity precedes the SS / PBCH block within this PUSCH time slot, and,

[0209] -- The PUSCH opportunity occurs at least N times from the last SS / PBCH block symbol. gap Starting after a symbol, when channelAccessMode="semiStatic" is provided, this PUSCH opportunity does not overlap with the set of consecutive symbols preceding the start of the next channel occupancy time when the UE does not transmit. Here, N gap It is provided in a standard form.

[0210] - When the UE is provided with tdd-UL-DL-ConfigurationCommon, the PUSCH opportunity is valid if the following conditions are met.

[0211] -- The PUSCH opportunity is located within the UL symbol, or,

[0212] -- This PUSCH opportunity precedes the SS / PBCH block within this PUSCH time slot, and,

[0213] -- The PUSCH opportunity occurs at least N times from the last DL symbol. gap After the symbol, and starting from the last SS / PBCH block symbol at least N gap Starting after a symbol, when channelAccessMode="semiStatic" is provided, this PUSCH opportunity does not overlap with the set of consecutive symbols preceding the start of the next channel occupancy time when the UE does not transmit. Here, N gap It is provided in a standard form.

[0214] (PRACH conflict (Physical layer procedures for control: slot configuration))

[0215] In operation on a single carrier within the current spectrum (TDD), if the UE transmits SRS, PUCCH, PUSCH, or PRACH within a set of symbols configured in a time slot by a higher layer, and the UE detects the DCI format of the received CSI-RS or PDSCH from a subset of symbols in that set of symbols, the UE follows the following operation:

[0216] - If the UE does not have the ability to indicate partial cancellation, the UE will follow these steps:

[0217] -- The first symbol in the set of symbols starts from the last symbol detected by the UE in the CORESET of the DCI format. proc,2 In the event of an event occurring within the specified range, the UE does not expect to cancel the transmission of PUCCH, PUSCH, or PRACH within the set of symbols. Otherwise, the UE cancels the transmission of PUCCH, PUSCH, actual repetition of PUSCH, or PRACH within the set of symbols.

[0218] - If the UE indicates the ability to perform partial cancellation, the UE will follow these steps:

[0219] -- The UE does not expect to cancel the initial symbol from the set of symbols starting from the last symbol of the CORESET in the DCI format detected by the UE. proc,2 The UE cancels the transmission of PUCCH, PUSCH, or PRACH within the set of symbols that occurs within the set of symbols.

[0220] That is, if a PRACH triggered / set by a higher layer overlaps with a symbol scheduled for DL ​​reception via DCI, the UE cancels the PRACH.

[0221] When operating on a single carrier within the current spectrum (TDD), and in the case where the UE transmits any symbol from the set of symbols in a time slot in which the reception of a particular SS / PBCH block is indicated to the UE, the UE shall not transmit PUSCH, PUCCH, or PRACH in that time slot, nor shall the UE transmit SRS in that set of symbols in that time slot. The specific SS / PBCH block is: an SS / PBCH block based on ssb-PositionsInBurst within SIB1 (SystemInformationBlockType1); or an SS / PBCH block based on ssb-PositionsInBurst within ServingCellConfigCommon; or, if the UE is not provided with dl-OrJoint-TCIStateList, an SS / PBCH block based on ssb-PositionsInBurst within SSB-MTCAdditionalPCI associated with the physical cell ID accompanying the active TCI state for PDCCH or PDSCH; or an SS / PBCH block for the set of symbols corresponding to the time slot of the SS / PBCH block set for L1 beam measurement / reporting. When tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is provided to the UE, the set of symbols in that time slot is not expected to be indicated as uplink through tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0222] In UE

[0223] - Multiple serving cells are configured, and the set of serving cells among these multiple serving cells is provided with directionalCollisionHandling-r16 = 'enabled', and,

[0224] - Indicates support for the half-DuplexTDD-CA-SameSCS-r16 capability, and,

[0225] - If no PDCCH for monitoring DCI format 2_0 detection is configured on any of the multiple serving cells, the UE follows the procedure below:

[0226] - In the set of symbols of the time slot indicated to the UE for receiving a specific SS / PBCH block in the initial cell of the multiple serving cells, if the transmission overlaps with any symbol from the set of symbols, the UE will not transmit PUSCH, PUCCH, or PRACH in that time slot, and the UE will not transmit SRS in that set of symbols in that time slot of the specific cell. The specific SS / PBCH block is: an SS / PBCH block based on ssb-PositionsInBurst within SIB1 (SystemInformationBlockType1); or an SS / PBCH block based on ssb-PositionsInBurst within ServingCellConfigCommon; or, if the UE is not provided with dl-OrJoint-TCIStateList, an SS / PBCH block based on ssb-PositionsInBurst within SSB-MTCAdditionalPCI associated with the physical cell ID accompanying the active TCI state for PDCCH or PDSCH; or an SS / PBCH block for the set of symbols corresponding to the time slot of the SS / PBCH block set for L1 beam measurement / reporting. The specific cell is: any one of the plurality of serving cells that does not have the simultaneous transmission and reception capability indicated by simultaneousRxTxInterBandCA; and any one of the cells that corresponds to the same band as the original cell, regardless of the capability indicated by simultaneousRxTxInterBandCA.

[0227] That is, if the PRACH triggered / set by a higher layer overlaps with the SSB symbol, the UE will not send the PRACH.

[0228] (PRACH conflict (Physical layer procedures for control: UE procedure for determining slot format))

[0229] In the case where tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are provided, the UE is indicated to the UE as a flexible time slot through the set of symbols indicated by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated; or in the case where tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided, or in the case where the UE detects DCI format 2_0 with a time slot format value other than 255 for that time slot, the UE follows the following operation:

[0230] - If the SFI index field value m in DCI format 2_0 indicates that the set of symbols in this time slot is flexible, and the UE does not receive a DCI format indicating PDSCH or CSI-RS to the UE, or does not receive a DCI format indicating PUSCH, PUCCH, PRACH or SRS to the UE, RAR UL permission, fallback RAR UL permission or success RAR in the set of symbols in this time slot, the UE will neither transmit nor receive in the set of symbols in this time slot.

[0231] That is, if a PRACH without a PDCCH command overlaps with a symbol indicated as flexible by SFI, the UE will not send the PRACH.

[0232] When a UE transmits SRS, PUCCH, PUSCH, or PRACH within a set of symbols configured by a higher layer, and the UE detects that the time slot format accompanying a subset of symbols from that set of symbols is indicated as downlink or a flexible DCI format with a time slot format value other than 255, or the UE receives a DCI format indicating the reception of CSI-RS or PDSCH from a subset of symbols in that set of symbols, the UE performs the following operations:

[0233] - If the UE does not have the ability to indicate partial cancellation, the UE will follow these steps:

[0234] -- The first symbol in this set of symbols starts from the last symbol of the CORESET in the DCI format detected by the UE. proc,2In the event of an event occurring within the specified range, the UE does not expect to cancel the transmission of PUCCH, PUSCH, or PRACH within the set of symbols. Otherwise, the UE cancels the transmission of PUCCH, PUSCH, actual repetition of PUSCH, or PRACH within the set of symbols.

[0235] - If the UE indicates the ability to perform partial cancellation, the UE will follow these steps:

[0236] -- The UE does not expect cancellation of PUCCH, PUSCH, or PRACH transmissions from the following set of symbols: the first symbol in the set starting from the last symbol of the CORESET in the DCI format detected by the UE. proc,2 This occurs within the set of symbols. The UE cancels the actual repetition of PUCCH, PUSCH, or PUSCH, or PRACH transmissions within the remaining symbols of this symbol set.

[0237] That is, if a PRACH set by a higher layer overlaps with a symbol indicated as DL or flexible by SFI, the UE cancels the PRACH.

[0238] If tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are provided, and the UE indicates to the UE the set of symbols that constitute a flexible time slot through 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 does not detect DCI format 2_0 providing a time slot format for that time slot, the UE follows the following operation:

[0239] - If the UE is configured to transmit via SRS, PUCCH, PUSCH, or PRACH through a higher layer, and the UE is not provided with enableConfiguredUL, the UE will follow the following operations:

[0240] -- If the UE does not have the ability to indicate partial cancellation, the UE will follow these steps:

[0241] --- The initial symbol of the PUCCH, or PUSCH, or the actual repetition of the PUSCH, or the PRACH, begins from the last symbol of the CORESET set by the UE for monitoring the PDCCH in DCI format 2_0. proc,2 If the event occurs within the time slot, the UE does not expect the cancellation of the transmission of PUCCH, PUSCH, or actual repetition of PUSCH, or PRACH within that time slot. Otherwise, the UE cancels the transmission of PUCCH, PUSCH, or actual repetition of PUSCH, or PRACH within that time slot.

[0242] -- If the UE indicates the ability to perform partial cancellation, the UE will follow these steps:

[0243] --- This UE does not expect cancellation of the following PUCCH, PUSCH, or actual repetition of PUSCH, or PRACH transmissions within the following symbols: from the last symbol of the CORESET monitored by the UE for DCI format 2_0. proc,2 The set of symbols occurring within this time slot. The UE cancels the actual repetition of PUCCH, or PUSCH, or PUSCH, or PRACH transmission within this time slot. The UE cancels the PUCCH, or PUSCH, or PUSCH, or PRACH transmission within the remaining symbols from this set of symbols.

[0244] That is, if a PRACH triggered / set by a higher layer overlaps with a flexible symbol set to semi-static, and the UE does not detect DCI format 2_0, the UE cancels the PRACH.

[0245] (Multiple PRACH transmissions use PRACH resources)

[0246] Investigating: Multiple PRACH transmissions are sent on separate ROs (separate ROs) that are separate from a single PRACH transmission; multiple PRACH transmissions are sent on shared ROs (shared ROs) that are shared with a single PRACH transmission, using separate preambles that are separate from a single PRACH transmission.

[0247] To differentiate between multiple PRACH transmissions using the same Tx beam and a single PRACH transmission, research is underway to support multiple PRACH transmissions being transmitted on separate ROs.

[0248] To differentiate between multiple PRACH transmissions using the same Tx beam and a single PRACH transmission, research is underway to support multiple PRACH transmissions using separate preambles on a shared RO.

[0249] In multiple PRACH transmissions using the same Tx beam, a “RO group” is envisioned for at least one of the separate preambles on a shared RO and multiple PRACH transmissions on separate ROs.

[0250] - All ROs within an RO group are associated with more than one of the same SSBs.

[0251] - Shared RO / preamble means that the RO / preamble is shared with a single PRACH transmission.

[0252] - Separate RO / preamble means that the RO / preamble is separated from a single PRACH transmission.

[0253] - Effective Returns (ROs) are defined in existing specifications. Effective ROs can also follow the aforementioned efficient conditions for PRACH opportunities.

[0254] (RAR monitoring for multiple PRACH)

[0255] In RAR monitoring of multiple PRACH transmissions using the same transmit beam within a single RACH attempt, a study is underway to support only a single RAR window.

[0256] The UE repeatedly transmits Msg1 on K random access opportunities (RO) / RO resources. Afterwards, the UE waits for the detection of Msg2 in a designated type 1 PDCCH opportunity. In this disclosure, the repeated transmission of the preamble in the K RO / RO resources is sometimes referred to as an RO group. Figure 3 This is an example of timing multiple PRACH transmissions. In this example, the size of the RO group (the number of ROs within the RO group) is K. A RAR window begins after one RO group.

[0257] In this disclosure, a RO group can also be defined as consisting of K valid ROs used in TDM, each having a separate RO in both the frequency and time domains. In other words, if an RO group is selected, the ROs used for each PRACH transmission are determined. Figure 4In the example, with repetition number K=2, the RO group consists of two consecutive ROs that are TDMed.

[0258] (Analysis 1)

[0259] In RAR monitoring of multiple PRACH transmissions within a single RACH attempt, the starting position of the RAR window and the RA-RNTI used for RAR monitoring have not been adequately investigated.

[0260] In determining ROs and RO groups, consider the constraint that an RO will not (and is not envisioned) be included in the same number of RO groups sent for the same SSB / CSI-RS and PRACH. Consider using this constraint for RA-RNTI calculations based on the initial or final PRACH transmission.

[0261] Without such restrictions, RA-RNTI calculations based on the initial, final, or individual PRACH transmissions may cause RA-RNTI conflicts. For example... Figure 5 For example, without restrictions on the ROs within a RO group, there exist RO groups consisting of RO#1, 6, 11, and 13; RO groups consisting of RO#1, 6, 8, and 13; and RO groups consisting of RO#1, 4, 8, and 13.

[0262] In CBRA, multiple PRACHs transmitted within a single RO (from multiple UEs) correspond to a single RN-RNTI. As of Rel. 17, only one of the multiple PRACHs transmitted within a single RO becomes the PRACH that triggers the subsequent RA procedure. In this case, the base station cannot distinguish the UE from these multiple PRACHs when transmitting RAR. The contention among these multiple PRACHs is resolved after the exchange of Msg3 and Msg4.

[0263] In multiple PRACH transmissions (multiple repetitions of PRACH) in Rel.18, consider the probability that each PRACH in a multiple PRACH transmitted in a RO becomes a PRACH in the RA process after triggering and the probability that it does not become a PRACH in the RA process after triggering.

[0264] In multiple PRACH iterations, the likelihood of RO / RA-RNTI conflicts increases, considering the possibility of false PRACH detection due to base station identification of RA-RNTI. As a scenario for RO conflicts, consider an RO shared among multiple RO groups. In multiple PRACH iterations, where the final PRACH determines the RA-RNTI and multiple RO groups may partially overlap, the final PRACH from UE#A may have overlapping scenarios in the following two ways, potentially increasing the probability of conflict.

[0265] - Scenario 1: PRACH overlaps with 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. Figure 6 In the example, the two PRACHs from UE#A and the two PRACHs from UE#B repeatedly use the same RO group (RO#0, RO#1).

[0266] - Scenario 2: PRACH overlap with UEs using different RO groups. For example, the RO group used by UE#B is different from the RO group used by UE#A. Figure 7 In the example, two PRACHs from UE#A repeatedly use RO group #0 (RO#1, RO#3). Two PRACHs from UE#B repeatedly use RO group #1 (RO#0, RO#3). Since the RA-RNTI is calculated based on the final RO of multiple repetitions, the same RA-RNTI is obtained in both UE#A and UE#B.

[0267] In the event of a RA-RNTI conflict, there are concerns that it could lead to a decrease in communication throughput.

[0268] (Analysis 2)

[0269] The research is investigating RO groups as "a specific number of valid RO(s) for multiple PRACH transmissions". In existing specifications, PRACH transmissions on valid ROs can be cancelled.

[0270] UE operations that take into account the possibility of RO conflicts within RO groups used for multiple PRACH transmissions have not been adequately studied. For example, it has not been sufficiently studied whether the UE considers RO conflicts when selecting an RO group, or what the UE's operations would be if the selected RO group contained ROs with conflicts. If such UE operations are not adequately studied, there are concerns that this could lead to a decrease in communication throughput, etc.

[0271] Therefore, the inventors of this invention conceived of operations related to conflicts between multiple ROs used for PRACH transmission.

[0272] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Furthermore, the following embodiments (e.g., various scenarios) can be used individually or in combination of at least two.

[0273] In this disclosure, "A / B" and "at least one of A and B" may be rewritten as each other. In addition, in this disclosure, "A / B / C" may also mean "at least one of A, B and C".

[0274] In this disclosure, terms such as notification, activation, deactivation, indication (or indication), selection, configuration, update, and determination can be overridden. Similarly, terms such as support, control, ability to control, operation, and ability to operate can also be overridden.

[0275] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-level parameters, fields, Information Elements (IE), settings, etc., can also be modified interchangeably. In this disclosure, Medium Access Control (MAC) control elements (CE), update commands, activation / deactivation commands, etc., can also be modified interchangeably.

[0276] In this disclosure, higher-layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., positioning protocol messages (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP) messages, etc. from the core network), or a combination thereof.

[0277] In this disclosure, MAC signaling may also use, for example, a MAC Control Element (MACCE) or a MAC Protocol Data Unit (PDU). Broadcast information may also be, for example, a Master Information Block (MIB), a System Information Block (SIB), a Minimum System Information (Remaining Minimum System Information (RMSI)), or Other System Information (OSI).

[0278] In this disclosure, physical layer signaling may also be, for example, downlink control information (DCI), uplink control information (UCI), etc.

[0279] The following abbreviations may also be used in this disclosure.

[0280] - Radio network temporary identifier: RNTI;

[0281] Time division multiplexing (TDM);

[0282] - Time-division-multiplexed: TDM;

[0283] - Frequency division multiplexing (FDM);

[0284] - Frequency-division multiplexed: FDM.

[0285] In this disclosure, a b The expressions a, a_b, and a with b appended to the lower right can also be rewritten interchangeably. In this disclosure, a c The expressions a, a^c, and a with c appended to the upper right can also be rewritten interchangeably. In this disclosure, a b c The expressions a_b^c and a with b appended to the lower right and c appended to the upper right can also be rewritten. In this disclosure, the ceil(x), ceiling function, and ceiling (rounding up) function can also be rewritten. In this disclosure, the floor(x), floor function, and floor (rounding down) function can also be rewritten.

[0286] In this disclosure, the reference signal (RS), downlink reference signal (DL-RS), and SSB / CSI-RS can be interchanged. In this disclosure, RSRP and SS-RSRP / CSI-RSRP can also be interchanged. In this disclosure, RS accompanied by RSRP, RS corresponding to RSRP, RS used for RSRP measurement, SSB accompanied by SS-RSRP, and CSI-RS accompanied by CSI-RSRP can also be interchanged.

[0287] In this disclosure, beam, SSB, SSB index, CSI-RS, CSI-RS resource, CSI-RS resource index, RS, QCL concept, TCI status, unified TCI status, DL or joint TCI status, UL TCI status, UL Tx spatial filter, spatial domain filter, spatial domain transmit filter, spatial domain receive filter, antenna port QCL parameters, QCL parameters, Tx beam, and spatial filter can also be rewritten.

[0288] In this disclosure, RACH resources, RA resources, PRACH preamble, opportunity, RACH opportunity (RO), PRACH opportunity, repetition resource, repetition setting resource, resource set for RO / repetition, time instance and frequency instance, time resource and frequency resource, RO / preamble resource, repetition, PRACH resource, time / frequency resource used for PRACH, preamble setting / index, main setting / index, and PRACH setting can also be overridden.

[0289] In this disclosure, time opportunity, time domain position, time position, PRACH opportunity, PRACH slot, period, period, symbol / slot / subframe / frame, at least one of their indices, time domain index, and T# can also be interchanged. In this disclosure, frequency domain position, frequency position, subcarrier / RE / RB / CC, at least one of their indices, frequency domain index, and F# can also be interchanged. In this disclosure, RO, RO index, and RO# can also be interchanged.

[0290] In this disclosure, the number of PRACH transmissions, the number of repetitions, the repetition factor, the aggregation factor, and K can be mutually modified. In this disclosure, multiple PRACH transmissions, more than one PRACH transmission, and multiple PRACH repetitions can also be mutually modified. In this disclosure, a single PRACH transmission and a PRACH transmission count of 1 can also be mutually modified.

[0291] 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 can also be rewritten to each other.

[0292] In this disclosure, single PRACH transmissions, existing PRACH transmissions, and existing PRACH resource settings can also be overwritten.

[0293] In this disclosure, multiple PRACH transmissions, new PRACH transmissions, and multiple PRACH resource settings can also be mutually modified. In this disclosure, separate ROs, new ROs, appended ROs, multiple ROs for PRACH transmissions, and ROs obtained by separating from existing ROs for PRACH transmissions can also be mutually modified.

[0294] In this disclosure, existing ROs may also include ROs that are set / determined via RACH-ConfigCommon / RACH-ConfigGeneric / RACH-ConfigDedicated / AdditionalRACH-Config-r17 / additionalRACH-ConfigList-r17.

[0295] In this disclosure, RA-RNTI, MSGB-RNTI, and the new RNTI can be rewritten in different ways. The formula for MSGB-RNTI can also be the formula for RA-RNTI plus the total number of values ​​of RA-RNTI.

[0296] (Wireless communication method)

[0297] The UE can also receive settings for multiple random access channel transmissions (multiple PRACH transmissions, multiple PRACH repetitions). Based on these settings, the UE can also determine whether a random access channel opportunity (RO) for the multiple random access channel transmissions conflicts with at least one of the following resources (specific resources): symbols indicated for receiving a synchronization block; symbols configured as downlink or flexible via time division multiplexing; symbols indicated as downlink or flexible via a time slot format indicator; valid opportunities for a single random access channel transmission (…). Figure 8 ).

[0298] The UE may also determine, based on the settings, multiple random access channel opportunities (ROs) used for transmission of the multiple random access channels, and based on a specific RO among the multiple ROs, determine at least one of the monitoring window start for random access response and radio network temporary identifier (RNTI, RA-RNTI).

[0299] <Implementation Method 1>

[0300] The restrictions on the overlap of multiple RO groups can also be at least one of the following restrictions.

[0301] - Restriction #1

[0302] At least one of the following restrictions may also be specified in the specification:

[0303] -- UE does not expect each RO in a certain RO group to be included in multiple RO groups.

[0304] -- The UE does not expect each RO within a RO group to be included in multiple RO groups of the same number sent for PRACH.

[0305] -- The UE does not expect that each RO within a certain RO group is included in multiple RO groups for the same SSB / CSI-RS.

[0306] -- The UE does not expect each RO within a certain RO group to be included in the same number of multiple RO groups sent for the same SSB / CSI-RS and PRACH.

[0307] -- The UE does not expect that at least one RO in a certain RO group is included in other RO groups.

[0308] -- The UE does not expect that at least one RO in a certain RO group is included in the same number of other RO groups sent for PRACH.

[0309] -- The UE does not expect that at least one RO in a certain RO group is included in other RO groups for the same SSB / CSI-RS.

[0310] -- The UE does not expect that at least one RO in a certain RO group is included in the same number of other RO groups sent for the same SSB / CSI-RS and PRACH.

[0311] - Restriction #2

[0312] At least one of the following restrictions may also be specified in the specification:

[0313] -- For the same number of PRACH transmissions, multiple overlapping RO groups have the same time span.

[0314] -- For the same number of SSB / CSI-RS and PRACH transmissions, multiple overlapping RO groups have the same time span.

[0315] -- For the same number of PRACH transmissions, the ROs within multiple RO groups with overlapping ROs have the same time-domain location.

[0316] -- For the same number of ROs transmitted for the same SSB / CSI-RS and PRACH, the ROs in multiple RO groups with overlapping ROs have the same time-domain location.

[0317] - Restriction #2a

[0318] At least one of the following restrictions may also be specified in the specification:

[0319] -- For different numbers of PRACH transmissions, multiple overlapping RO groups have the same time resource configuration for a specific RO.

[0320] -- For different numbers of PRACH transmissions, multiple overlapping RO groups have the same frequency resource configuration for a specific RO.

[0321] -- For the same SSB / CSI-RS, different numbers of PRACH transmissions, and overlapping RO groups with the same time resource configuration for a specific RO.

[0322] -- For the same SSB / CSI-RS, different numbers of PRACH transmissions, and multiple overlapping RO groups with the same frequency resource configuration for a specific RO.

[0323] - A specific RO can also be at least one of the following ROs.

[0324] -- The initial RO within each RO group.

[0325] -- The last RO within each RO group.

[0326] A specific RO can also be the RO used in the decision of RA-RNTI.

[0327] - Restriction #3

[0328] At least one of the following restrictions may also be specified in the specification:

[0329] -- One RO is contained within the same number of up to G RO groups sent for PRACH.

[0330] -- One RO is contained within a maximum of G RO groups for the same SSB / CSI-RS.

[0331] -- One RO is contained within the same number of up to G RO groups sent for the same SSB / CSI-RS and PRACH.

[0332] - Restriction #4

[0333] At least one of the following restrictions may also be specified in the specification:

[0334] -- Each of the multiple RO groups contains more than one dedicated RO.

[0335] -- Each of the multiple RO groups sent for the same number of PRACH messages contains more than one dedicated RO.

[0336] -- Each of the multiple RO groups for the same SSB / CSI-RS contains more than one dedicated RO.

[0337] -- Each of the same number of RO groups sent for the same SSB / CSI-RS and PRACH contains more than one dedicated RO.

[0338] -- Each of the multiple RO groups contains a dedicated RO.

[0339] -- Each of the multiple RO groups sent for the same number of PRACH messages contains a dedicated RO.

[0340] -- Each of the multiple RO groups for the same SSB / CSI-RS contains a dedicated RO.

[0341] -- Each of the same number of RO groups sent for the same SSB / CSI-RS and PRACH contains a dedicated RO.

[0342] - A dedicated RO is defined in implementation 2.

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

[0344] <Implementation Method 2>

[0345] For multiple PRACHs sent in a specific number of RO groups (using) specific SSB / CSI-RS and PRACH, RA-RNTI can also be calculated based on at least one of the following options.

[0346] - Option 1: The location of the time and frequency of all RO / PRACH transmissions within this RO group.

[0347] - Option 2: The location of the dedicated RO / PRACH transmission time and frequency within this RO group. This option can also be applied only if each RO group contains a dedicated RO. The definition of a dedicated RO will be described later.

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

[0349] - Option 4: The time position of the first or last RO / PRACH transmission within the RO group and the frequency position of the dedicated RO / PRACH transmission. This option can also be applied only if each RO group contains dedicated RO transmissions.

[0350] - Option 5: The time position of all RO / PRACH transmissions within the RO group and the frequency position of the first or last RO / PRACH transmission. This option can also be applied only if: for multiple RO groups with the same time span, or for multiple RO groups with different time spans, the first or last RO is not included in the multiple RO groups.

[0351] - Option 6: The time position of the dedicated RO / PRACH transmission within the RO group and the frequency position of the first or last RO / PRACH transmission. This option can also be applied only if: for multiple RO groups with the same time span, or for multiple RO groups with different time spans for dedicated ROs within each RO group, the first or last RO is not included in the multiple RO groups.

[0352] - Option 7: The time and frequency of the first or last RO / PRACH transmission, and the RO group index for the current RO group. For this option, the RO group index can also be defined (or appended).

[0353] Dedicated RO (Dedicated RO) in options 2 / 4 / 6 can also mean an RO that is only included in the current RO group. Dedicated PRACH transmission (Dedicated PRACH transmission) can also mean PRACH transmission on a dedicated RO. A dedicated RO can also not be included in other RO groups for the same SSB / CSI-RS (and the same number of PRACH transmissions). Figure 9 In the example, 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 only included in RO group #0, therefore it is a dedicated RO for RO group #0. RO#6 is only included in RO group #1, therefore it is a dedicated RO for RO group #1. RO#2 is only included in RO group #2, therefore it is a dedicated RO for RO group #2.

[0354] Details of Option 1

[0355] For multiple PRACHs transmitted in a specific number of RO groups (using) specific SSB / CSI-RS and PRACH transmissions, RA-RNTI can also be calculated based on the time and frequency of all RO / PRACH transmissions within that RO group, according to at least one of the following options.

[0356] - Option 1-1: Use the average. The formula for calculating RA-RNTI can also be any of the following.

[0357] -- 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

[0358] -- 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

[0359] - Option 1-2: Use modulo operations. The RA-RNTI calculation formula can also be any of the following.

[0360] -- 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

[0361] -- 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

[0362] - Options 1-3: Use the summation. The formula for calculating RA-RNTI can also be any of the following.

[0363] -- 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

[0364] -- 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

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

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

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

[0368] In the existing specifications, the RA-RNTI value ranges from 0 to 14×80×8×2 for a 4-step RACH and from 14×80×8×2 to 14×80×8×4 for a 2-step RACH.

[0369] Options 1-3 are based on the summation. With N=8 and Y=0 applied, the range of RA-RNTI is expanded to 14×80×8×8×2. This range may cause RA-RNTI overlap with the existing RA-RNTI range for 2-step RACH. With Y=4 applied, the range of RA-RNTI for multiple PRACH transmissions starts at 14×80×8×4. This range is further back than the existing RA-RNTI range for 2-step RACH. Options 1-3 can suppress the probability of RA-RNTI collisions between RO groups.

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

[0371] Details of Option 2

[0372] For multiple PRACHs transmitted in a specific number of RO groups (using) specific SSB / CSI-RS and PRACH transmissions, RA-RNTI can also be calculated based on the time and frequency of dedicated RO / PRACH transmissions within that RO group, according to at least one of the following options.

[0373] - Option 2-1: RA-RNTI is based on the time and frequency location of the first or last dedicated RO within the RO group. The formula for calculating RA-RNTI can also be as follows.

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

[0375] Here, for the first or last dedicated RO within a RO group used for multiple PRACH transmissions, s_id, t_id, and f_id can also be parameters for symbol index, slot index, and frequency index, respectively.

[0376] - Option 2-2: RA-RNTI is based on the time and frequency location of the first or last dedicated RO within the RO group. RA-RNT can also be calculated according to at least one of the following options.

[0377] -- Option 2-2-1: Use the average. The formula for calculating RA-RNTI can also be as follows.

[0378] --- 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

[0379] -- Option 2-2-2: Use modulo operations. The formula for calculating RA-RNTI can also be any of the following.

[0380] --- 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

[0381] --- 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

[0382] -- Option 2-2-3: Use the summation. The formula for calculating RA-RNTI can also be any of the following.

[0383] --- 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

[0384] --- 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

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

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

[0387] In options 2-2-1 / 2-2-2 / 2-2-3, for the (m-1)th dedicated RO (m=0,...,M-1) within a RO group used for multiple PRACH transmissions, s_id_m, t_id_m, and f_id_m can also be parameters representing the symbol index, time slot index, and frequency index, respectively. M can also be the number of dedicated ROs within that RO group.

[0388] In the existing specifications, the RA-RNTI value ranges from 0 to 14×80×8×2 for a 4-step RACH and from 14×80×8×2 to 14×80×8×4 for a 2-step RACH.

[0389] Option 2-2-3 is based on the summation. With N=8 and Y=0 applied, the range of RA-RNTI is expanded to 14×80×8×8×2. This range may cause RA-RNTI overlap with the existing RA-RNTI range for 2-step RACH. With Y=4 applied, the range of RA-RNTI for multiple PRACH transmissions starts at 14×80×8×4. This range is further back than the existing RA-RNTI range for 2-step RACH. Option 2-2-3 can suppress the probability of RA-RNTI collisions between RO groups.

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

[0391] Details of Option 3

[0392] For multiple PRACHs transmitted in a specific number of RO groups (using) specific SSB / CSI-RS and PRACH transmissions, RA-RNTI can also be calculated based on the time position of the first or last RO / PRACH transmission within that RO group and the frequency position of all RO / PRACH transmissions, according to at least one of the following options.

[0393] - Option 3-1: Use the average of all RO / PRACH transmitted frequency positions. The RA-RNTI calculation formula can also be as follows.

[0394] -- RA-RNTI=1+s_id+14×t_id+14×80×((Σ k=0 K-1 f_id_k)) / K)+14×80×8×ul_carrier_id

[0395] - Option 3-2: Use the total modulo operation of all RO / PRACH transmitted frequency positions. The RA-RNTI calculation formula can also be as follows.

[0396] -- 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

[0397] - Option 3-3: Use the summation. The formula for calculating RA-RNTI can also be any of the following.

[0398] -- 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

[0399] -- 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

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

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

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

[0403] In the existing specifications, the RA-RNTI value ranges from 0 to 14×80×8×2 for a 4-step RACH and from 14×80×8×2 to 14×80×8×4 for a 2-step RACH.

[0404] Option 3-3 is based on the summation. With Y=0 applied, the range of RA-RNTI is expanded to 14×80×8×8×2. This range may cause RA-RNTI overlap with the existing RA-RNTI range for 2-step RACH. With Y=4 applied, the range of RA-RNTI for multiple PRACH transmissions starts at 14×80×8×4. This range is further back than the existing RA-RNTI range for 2-step RACH. Option 3-3 can suppress the probability of RA-RNTI collisions between RO groups.

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

[0406] Details of Option 4

[0407] For multiple PRACHs transmitted in a specific number of RO groups (using) specific SSB / CSI-RS and PRACH transmissions, RA-RNTI can also be calculated based on the time position of the first or last RO / PRACH transmission within that RO group and the frequency position of the dedicated RO / PRACH transmission, according to at least one of the following options.

[0408] - Option 4-1: RA-RNTI is based on the frequency position of the first or last dedicated RO within that RO group. The formula for calculating RA-RNTI can also be as follows.

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

[0410] Here, for the first or last RO within a RO group used for multiple PRACH transmissions, s_id and t_id can also be parameters for symbol index and slot index, respectively. For the first or last dedicated RO within a RO group used for multiple PRACH transmissions, f_id can also be a parameter for frequency index.

[0411] - Option 4-2: Use the average of the frequency locations of dedicated ROs within this RO group. The RA-RNTI calculation formula can also be as follows.

[0412] -- RA-RNTI=1+s_id+14×t_id+14×80×((Σ m=0 M-1 f_id_m) / M)+14×80×8×ul_carrier_id

[0413] - Option 4-3: Use modulo operations for the frequency positions of dedicated ROs within this RO group. The RA-RNTI calculation formula can also be any of the following.

[0414] -- 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

[0415] - Option 4-4: Use the sum of the frequency positions of the dedicated ROs within this RO group. The RA-RNTI calculation formula can also be any of the following.

[0416] -- Option 4-4a:

[0417] 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

[0418] -- Option 4-4b:

[0419] 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

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

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

[0422] In options 4-2 / 4-3 / 4-4, for the first or last RO within a RO group used for multiple PRACH transmissions, s_id and t_id can also be parameters for the symbol index and slot index, respectively. For the (m-1)th (m=0,...,M-1)th dedicated RO within a RO group used for multiple PRACH transmissions, f_id_m can also be a parameter for the frequency index. M can also be the number of dedicated ROs within that RO group.

[0423] In the existing specifications, the RA-RNTI value ranges from 0 to 14×80×8×2 for a 4-step RACH and from 14×80×8×2 to 14×80×8×4 for a 2-step RACH.

[0424] Option 4-4 is based on the summation. With N=8 and Y=0 applied, the range of RA-RNTI is expanded to 14×80×8×8×2. This range may cause RA-RNTI overlap with the existing RA-RNTI range for 2-step RACH. With Y=4 applied, the range of RA-RNTI for multiple PRACH transmissions starts at 14×80×8×4. This range is further back than the existing RA-RNTI range for 2-step RACH. Option 4-4 can suppress the probability of RA-RNTI collisions between RO groups.

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

[0426] Details of Option 5

[0427] For multiple PRACHs transmitted in a specific number of RO groups (using) specific SSB / CSI-RS and PRACH transmissions, RA-RNTI can also be calculated 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, according to at least one of the following options.

[0428] - Option 5-1: Use the average of the time positions of all RO / PRACH transmissions. The RA-RNTI calculation formula can also be as follows.

[0429] -- 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

[0430] - Option 5-2: Use the modulo operation of the total time position of all RO / PRACH transmissions. The RA-RNTI calculation formula can also be as follows.

[0431] -- 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

[0432] - Option 5-3: Use the summation. The formula for calculating RA-RNTI can also be any of the following.

[0433] -- 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

[0434] -- 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

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

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

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

[0438] In the existing specifications, the RA-RNTI value ranges from 0 to 14×80×8×2 for a 4-step RACH and from 14×80×8×2 to 14×80×8×4 for a 2-step RACH.

[0439] Option 5-3 is based on the summation. With N=8 and Y=0 applied, the range of RA-RNTI is expanded to 14×80×8×8×2. This range may cause RA-RNTI overlap with the existing RA-RNTI range for 2-step RACH. With Y=4 applied, the range of RA-RNTI for multiple PRACH transmissions starts at 14×80×8×4. This range is further back than the existing RA-RNTI range for 2-step RACH. Option 5-3 can suppress the probability of RA-RNTI collisions between RO groups.

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

[0441] Details of Option 6

[0442] For multiple PRACHs transmitted in a specific number of RO groups (using) specific SSB / CSI-RS and PRACH transmissions, RA-RNTI can also be calculated based on the time position of the dedicated RO / PRACH transmission within that RO group and the frequency position of the first or last RO / PRACH transmission, according to at least one of the following options.

[0443] - Option 6-1: RA-RNTI is based on the time position of the first or last dedicated RO within that RO group. The formula for calculating RA-RNTI can also be as follows.

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

[0445] Here, for the first or last dedicated RO within a RO group used for multiple PRACH transmissions, s_id and t_id can also be parameters for symbol index and slot index, respectively. For the first or last RO within a RO group used for multiple PRACH transmissions, f_id can also be a parameter for frequency index.

[0446] - Option 6-2: Use the average of the time locations of dedicated ROs within this RO group. The RA-RNTI calculation formula can also be as follows.

[0447] -- 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

[0448] - Option 6-3: Use modulo operation for the time position of the dedicated RO within this RO group. The RA-RNTI calculation formula can also be any of the following.

[0449] -- 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

[0450] - Option 6-4: Use the sum of time locations for the dedicated ROs within this RO group. The RA-RNTI calculation formula can also be any of the following.

[0451] -- Option 6-4a:

[0452] 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

[0453] -- Option 6-4b:

[0454] 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

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

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

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

[0458] In the existing specifications, the RA-RNTI value ranges from 0 to 14×80×8×2 for a 4-step RACH and from 14×80×8×2 to 14×80×8×4 for a 2-step RACH.

[0459] Option 6-4 is based on the summation. With N=8 and Y=0 applied, the range of RA-RNTI is expanded to 14×80×8×8×2. This range may cause RA-RNTI overlap with the existing RA-RNTI range for 2-step RACH. With Y=4 applied, the range of RA-RNTI for multiple PRACH transmissions starts at 14×80×8×4. This range is further back than the existing RA-RNTI range for 2-step RACH. Option 6-4 can suppress the probability of RA-RNTI collisions between RO groups.

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

[0461] Details of Option 7

[0462] For multiple PRACHs transmitted in a specific number of RO groups (using) for a specific SSB / CSI-RS and PRACH transmission, RA-RNTI can also be calculated based on the time and frequency of the first or last RO / PRACH transmission, and the RO group index for the current RO group, according to at least one of the following options.

[0463] - 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

[0464] - 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

[0465] - 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

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

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

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

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

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

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

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

[0473] The above RA-RNTI formula can also follow at least one of the following rules.

[0474] - Rule 1

[0475] G can also be the maximum number of RO groups containing the same RO. For the same SSB / CSI-RS, G can also be the maximum number of RO groups containing the same RO. For the same number of PRACH transmissions, G can also be the maximum number of RO groups containing the same RO. For the same number of both SSB / CSI-RS and PRACH transmissions, G can also be the maximum number of RO groups containing the same RO. G can also follow the limitation #3 of implementation method 1.

[0476] - Rule 2

[0477] Y can be defined in the specification or indicated / set by the base station. Y can also be 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, etc. When Y=4 is applied, the range of RA-RNTI for multiple PRACH transmissions starts from 14×80×8×4. This range is later than the existing RA-RNTI range for 2-step RACH.

[0478] - Rule 3

[0479] For the first or last RO within a RO group used for multiple PRACH transmissions, s_id, t_id, and f_id can also be parameters for symbol index, slot index, and frequency index, respectively.

[0480] - Rule 4

[0481] ro_group_id can also be an RO group index. This RO group index can also represent an index of an RO group used for multiple PRACH transmissions among multiple RO groups, following at least one of the following options.

[0482] -- Option 7-1: Multiple RO groups within a specific period. The specific period can be, for example, an association period, a configuration period, X time slots / subframes / frames defined in the specification, or X time slots / subframes / frames indicated / set by the base station. These multiple RO groups can also be multiple RO groups for the same SSB / CSI-RS. These multiple RO groups can also be the same number of RO groups transmitted for PRACH. These multiple RO groups can also be the same number of RO groups transmitted for both the same SSB / CSI-RS and PRACH.

[0483] -- Option 7-2: A collection of multiple RO groups with overlapping ROs. These multiple RO groups can also be multiple RO groups targeting the same SSB / CSI-RS. These multiple RO groups can also be the same number of RO groups sent for PRACH. These multiple RO groups can also be the same number of RO groups sent for both the same SSB / CSI-RS and PRACH.

[0484] -- Option 7-3: The initial or final RO is multiple RO groups of the same RO. These multiple RO groups can also be multiple RO groups for the same SSB / CSI-RS. These multiple RO groups can also be multiple RO groups of the same number sent for PRACH. These multiple RO groups can also be multiple RO groups of the same number sent for both the same SSB / CSI-RS and PRACH.

[0485] The order in which the indexes are appended to the RO groups within the multiple RO groups (multiple RO groups in options 7-1 / 7-2 / 7-3) can also 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 order in which the indexes are appended to the RO groups can also follow at least one of the following examples.

[0486] - Example 1

[0487] In multiple RO groups with different time spans, RO groups with earlier start or end times can also be appended with an index that precedes those with later start or end times. The start or end time of an RO group can also refer to the time position of the first or last RO within that RO group.

[0488] - Example 2

[0489] Multiple RO groups with the same time span, the same start time position, or the same end time position can also be indexed based on frequency position. When the initial or final RO time positions of multiple RO groups are the same, at least one of the following operations can be followed.

[0490] -- In the case where the multiple RO groups have different frequency indices for the initial or final RO, either the RO group corresponding to the lower frequency index is appended with an RO group index that comes before the RO group corresponding to the higher frequency index, or the RO group corresponding to the higher frequency index is appended with an RO group index that comes before the RO group corresponding to the lower frequency index.

[0491] -- When multiple RO groups have the same frequency index for the initial or final RO, the frequency indexes for ROs that are later or earlier than the RO are compared. This means that the RO group corresponding to the lower frequency index is appended with an earlier RO group index than the RO group corresponding to the higher frequency index, or the RO group corresponding to the higher frequency index is appended with an earlier RO group index than the RO group corresponding to the lower frequency index.

[0492] In Example 1, among multiple RO groups with different time spans, the RO group with an earlier start time position is appended with a higher RO group index than the RO group with a later start time position. In Example 2, when multiple RO groups have the same initial RO time position, if the multiple RO groups have different frequency indices for the initial RO, the RO group corresponding to the lower frequency index is appended with a higher RO group index than the RO group corresponding to the higher frequency index. If the multiple RO groups have the same frequency index for the initial RO, the frequency indices for ROs later than that RO are compared, and the RO group corresponding to the lower frequency index is appended with a higher RO group index than the RO group corresponding to the higher frequency index. In the aforementioned... Figure 5 In the example, in the RO groups consisting of RO#1, 6, 11, and 13, the RO groups consisting of RO#1, 6, 8, and 13, and the RO groups consisting of RO#1, 4, 8, and 13, the initial ROs of these multiple RO groups have the same time position and the same frequency index for the initial ROs. The frequency indices of ROs that are later than the initial ROs are compared, and the RO group corresponding to the lower frequency index is appended with an index that is earlier than the RO group corresponding to the higher frequency index. Index 0 is assigned to the RO group consisting of RO#1, 4, 8, and 13, index 1 is assigned to the RO group consisting of RO#1, 6, 8, and 13, and index 2 is assigned to the RO group consisting of RO#1, 6, 11, and 13.

[0493] The ro_group_id can also be set via the RRC parameter.

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

[0495] <Implementation Method 3>

[0496] Several options in implementation method 2 can also be applied by following at least one of the following application methods.

[0497] Option 1 of implementation method 2 can be applied without any restrictions.

[0498] - When constraint #1 of implementation method 1 is applied, option 2 of implementation method 2 can be applied.

[0499] - When constraint #2 of implementation method 1 is applied, option 3 of implementation method 2 can be applied.

[0500] - When constraint #3 of implementation method 1 is applied, option 7 of implementation method 2 can be applied.

[0501] According to this embodiment, the UE can determine the appropriate RA-RNTI based on the limitations of the RO group.

[0502] <Implementation Method A1>

[0503] Considering the possibility of RO collisions in multiple PRACH transmissions using the same Tx beam, UE operation may also follow at least one of the following options.

[0504] - Option 1

[0505] The UE does not expect the first or last (valid) RO within a RO group to be accompanied by a conflict. Alternatively, the UE does not expect the first or last (valid) RO within any RO group to be accompanied by a conflict.

[0506] - Option 2

[0507] When the UE selects the RO group, conflicts are taken into account. The UE may also follow at least one of the following options.

[0508] -- Option 2-1: The UE will not decide / select the RO group with the first or last (valid) RO that has a conflict as the RO group for multiple PRACH transmissions.

[0509] -- Option 2-2: If the number of conflicting (valid) ROs is greater than a specific value X, or is above a specific value X, the UE will not decide / select the RO group as the RO group for multiple PRACH transmissions. Here, the value of X can be specified by the specification or set by the base station.

[0510] -- Option 2-3: If the number of valid ROs without conflicts is less than a specific value Y, or is below a specific value Y, the UE will not decide / select the RO group as the RO group for multiple PRACH transmissions. Here, the value of Y can be specified by the specification or set by the base station.

[0511] - Option 3

[0512] When the UE selects the RO group, conflicts are not considered. The UE operation after the RO group selection is defined. The UE may also follow at least one of the following options.

[0513] -- Option 3-1: If any (valid) RO within the RO group is conflicted, the UE will not send PRACH on that RO, or will cancel PRACH transmission. The UE may also send PRACH on the remaining (unconflicted) valid ROs within the RO group.

[0514] -- Option 3-2: If the first or last (valid) RO in a RO group is accompanied by a conflict, the UE shall not send PRACH in that RO group, or cancel PRACH sending.

[0515] -- Option 3-3: If the number of conflicting (valid) ROs within the selected RO group is greater than a specific value X, or is above a specific value X, the UE will not send PRACH within that RO group, or will cancel PRACH transmission. Here, the value of X can be specified by the standard or set by the base station.

[0516] -- Option 3-4: If the number of non-conflicting (valid) ROs within the selected RO group is less than a specific value Y, or is below a specific value Y, the UE will not send PRACH within that RO group, or will cancel PRACH transmission. Here, the value of Y can be specified by the standard or set by the base station.

[0517] According to this implementation, even if there is a possibility of conflict, the UE can properly control the transmission of multiple PRACH.

[0518] <Implementation Method A2>

[0519] The definition of "conflict" in "with conflict" / "without conflict" in this disclosure may also include at least one of the following conflict scenarios.

[0520] - Any symbol indicated as DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated overlaps with this RO.

[0521] - Any symbol indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon that is used for the reception of SS / PBCH blocks overlaps with this RO.

[0522] - Any symbol indicated as DL by DCI format 2_0 / SFI overlaps with this RO.

[0523] - By means of DCI format 2_0 / SFI, it is indicated that the symbol overlaps with the RO as flexible and arbitrary.

[0524] - Any symbol used for receiving PDSCH / CSI-RS that overlaps with the RO is indicated by the detected DCI.

[0525] - When tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are set, and any symbol is set to flexible by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated, and the UE is set to monitor DCI format 2_0 / SFI, and the UE does not detect that the symbol overlaps with the RO in the case of DCI format 2_0 / SFI.

[0526] - In the time / frequency domain, any valid RO associated with a type 1 RA procedure for a single PRACH transmission overlaps with this RO.

[0527] - In the time / frequency domain, any valid RO associated with a type 2 RA process overlaps with this RO.

[0528] - In the time / frequency domain, any valid PUSCH opportunity associated with a Type 2 RA process overlaps with this RO.

[0529] Whether a conflict situation is included among the above-mentioned conflict situations can be specified by the standard or set by the base station.

[0530] According to this embodiment, the UE can properly handle conflicts.

[0531] <Changes in Implementation Methods A1 / A2>

[0532] Implementation methods A1 / A2 can be applied to situations where multiple PRACH transmissions are used with different Tx beams.

[0533] For scenarios involving multiple PRACH transmissions using the same Tx beam and multiple PRACH transmissions using different Tx beams, different options in implementation methods A1 / A2 can also be applied. The options in implementation methods A1 / A2 that apply to each scenario can be specified by a standard or set by the base station.

[0534] Implementation methods A1 / A2 can be applied to multiple PRACH transmissions accompanied by a specific RACH type. The specific RACH type can also be a specific RACH triggering method, a specific RACH purpose, etc.

[0535] - Example: Implementation methods A1 / A2 can also be applied to specific RACH triggering methods. Specific RACH triggering methods can also be RA processes that are started / triggered by PDCCH / MAC entities / RRC.

[0536] - Example: Implementation methods A1 / A2 can also be applied to a specific RACH purpose. The specific RACH purpose method can be, for example, at least one of initial access, SI request, SpCell BFR, and reconfiguration with synchronization.

[0537] <Analysis>

[0538] As mentioned above, research is underway to support only a single RAR window for multiple PRACH transmissions. Whether the RAR window begins after the initial repeated RO or after the final repeated RO has not yet been fully investigated.

[0539] Furthermore, in implementations A1 / A2, the UE can send PRACH on other ROs within the same RO group but not on a specific RO within that RO group. In such cases, the RA-RNTI calculation is ambiguous. For example, it is unclear whether the RA-RNTI calculation considers only the first or last RO among those with actual PRACH transmissions, or whether it is independent of whether a transmission actually occurs. For instance, if the RAR window begins after the last PRACH transmission in a series of PRACH transmissions using ROs #0, #1, #2, and #3, it is unclear whether the RAR window begins after RO #2 or after RO #3 if the last PRACH is not transmitted due to a conflict with RO #3.

[0540] <Implementation Method B1>

[0541] RAR windows for multiple PRACH transmissions (using the same Tx beam) can also follow at least one of the following options.

[0542] - Option 1

[0543] The RAR window begins after the last symbol of the first or last valid RO within a RO group that is determined for use in multiple PRACH transmissions.

[0544] - Option 2

[0545] The RAR window begins after the last symbol of the first or last (actually) PRACH transmission in a series of PRACH transmissions.

[0546] - Option 3

[0547] The RAR window begins after the last symbol of the first or last valid RO within the RO group that meets specific conditions, which is determined to be used for multiple PRACH transmissions.

[0548] A specific condition can also be that no "conflict" occurs in implementation A2 within this RO. This specific condition can be one of the following conditions, or it can be a condition obtained through AND / OR calculations of two or more conditions.

[0549] - Any symbol indicated as DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated does not overlap with the RO.

[0550] - Any symbol used for receiving SS / PBCH blocks that is indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon does not overlap with this RO.

[0551] - Any symbol indicated as DL by DCI format 2_0 / SFI does not overlap with the RO.

[0552] - By means of DCI format 2_0 / SFI, it is indicated that the arbitrary symbols are flexible and do not overlap with the RO.

[0553] - Any symbol used for receiving PDSCH / CSI-RS, as indicated by the detected DCI, does not overlap with the RO.

[0554] - When tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are set, any symbol is set to flexible via tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated, and the UE is set to monitor DCI format 2_0 / SFI, and the UE does not detect that the symbol does not overlap with the RO in the case of DCI format 2_0 / SFI.

[0555] - In the time / frequency domain, any valid RO associated with a type 1 RA procedure for a single PRACH transmission does not overlap with that RO.

[0556] - In the time / frequency domain, any valid RO associated with a type 2 RA process does not overlap with this RO.

[0557] - In the time / frequency domain, any valid PUSCH opportunity associated with a Type 2 RA process does not overlap with this RO.

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

[0559] <Implementation Method B2>

[0560] The RA-RNTI used to monitor RARs transmitted for multiple PRACHs (using the same Tx beam) can also be calculated according to at least one of the following options.

[0561] - Option 1

[0562] The RAR window begins after the last symbol of the first or last valid RO within a RO group that is determined for use in multiple PRACH transmissions.

[0563] - Option 2

[0564] The RAR window begins after the last symbol of the first or last (actually) PRACH transmission in a series of PRACH transmissions.

[0565] - Option 3

[0566] The RAR window begins after the last symbol of the first or last valid RO within the RO group that meets specific conditions, which is determined to be used for multiple PRACH transmissions.

[0567] - Option 4

[0568] The RAR window begins after the last symbol of all or dedicated valid ROs within the RO group determined for multiple PRACH transmissions.

[0569] - Option 5

[0570] The RAR window begins after the last symbol of all or a dedicated (actually) PRACH transmission in a series of PRACH transmissions.

[0571] - Option 6

[0572] The RAR window begins after the last symbol of a valid RO that meets specific conditions within the RO group that has been determined for use in multiple PRACH transmissions.

[0573] A specific condition can also be that no "conflict" occurs in implementation A2 within this RO. This specific condition can be one of the following conditions, or it can be a condition obtained through AND / OR calculations of two or more conditions.

[0574] - Any symbol indicated as DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated does not overlap with the RO.

[0575] - Any symbol used for receiving SS / PBCH blocks that is indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon does not overlap with this RO.

[0576] - Any symbol indicated as DL by DCI format 2_0 / SFI does not overlap with the RO.

[0577] - By means of DCI format 2_0 / SFI, it is indicated that the arbitrary symbols are flexible and do not overlap with the RO.

[0578] - Any symbol used for receiving PDSCH / CSI-RS, as indicated by the detected DCI, does not overlap with the RO.

[0579] - When tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are set, any symbol is set to flexible by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated, and the UE is set to monitor DCI format 2_0 / SFI, and the UE does not detect that the symbol does not overlap with the RO in the case of DCI format 2_0 / SFI.

[0580] - In the time / frequency domain, any valid RO associated with a type 1 RA procedure for a single PRACH transmission does not overlap with that RO.

[0581] - In the time / frequency domain, any valid RO associated with a type 2 RA process does not overlap with this RO.

[0582] - In the time / frequency domain, any valid PUSCH opportunity associated with a Type 2 RA process does not overlap with this RO.

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

[0584] <Changes in Implementation Methods B1 / B2>

[0585] Implementation methods B1 / B2 can be applied to situations where multiple PRACH transmissions are used with different Tx beams.

[0586] For scenarios involving multiple PRACH transmissions using the same Tx beam and multiple PRACH transmissions using different Tx beams, different options from implementations B1 / B2 can also be used. The options in implementations B1 / B2 applicable to each scenario can be specified by a standard or set by the base station.

[0587] <Supplement>

[0588] [Information notification to UE]

[0589] In the above embodiments, any information (e.g., notification from the base station (BS) to the UE) (in other words, the reception of any information from the BS in the UE) can also be delivered using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signals), or combinations thereof.

[0590] When the above notification is made via MAC CE, the MAC CE can also be identified by including a new Logical Channel ID (LCID) in the MAC sub-header that is not specified in the existing standard.

[0591] When the above notification is made through a DCI, the notification can also be made through specific fields of the DCI, the Radio Network Temporary Identifier (RNTI) used in the scrambling of the Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0592] Furthermore, the notification of any information to the UE in the above embodiments can also be performed periodically, semi-persistently, or non-periodically.

[0593] [Notification from UE]

[0594] In the above embodiments, any information notification from the UE (to the NW) (in other words, the transmission / reporting of any information in the UE to the BS) can also 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 combinations thereof.

[0595] In the case of notification via MAC CE, the MAC CE can also be identified by including a new LCID in the MAC subheader that is not specified in the existing standard.

[0596] When the above notification is made via UCI, the notification may also be sent using PUCCH or PUSCH.

[0597] Furthermore, notifications of any information from the UE in the above embodiments can also be performed periodically, semi-persistently, or non-periodically.

[0598] [Regarding the application of each implementation method]

[0599] At least one of the above-described implementation methods can also be applied under certain conditions. These specific conditions can be specified in the standard or notified to the UE / BS using higher-layer signaling / physical-layer signaling.

[0600] At least one of the above-described embodiments can be applied to at least one of the following random access (RA) systems, or it can be limited to only at least one of the following RA systems.

[0601] ·CBRA.

[0602] CFRA.

[0603] • The RA who was ordered to PDCCH.

[0604] • RA used for system information acquisition (SI acquisition).

[0605] At least one of the above-described implementation methods may also be applied only to UEs that have reported a specific UE capability or support that specific UE capability.

[0606] This specific UE capability can also represent at least one of the following:

[0607] • Supports at least one specific processing / operation / control / information related to the above implementation.

[0608] • Supports separate ROs for multiple PRACH transmissions.

[0609] • Supports setting up separate ROs for multiple PRACH transmissions based on existing PRACH settings.

[0610] • Supports SSB-RO mapping rules for separate ROs used for multiple PRACH transmissions.

[0611] • Supports multiple PRACH transmissions with separate ROs that overlap in the time and frequency domains for a single PRACH transmission, which are associated with a Type 1 RA procedure and have valid PRACH opportunities for a single PRACH transmission.

[0612] • Supports multiple PRACH transmissions with separate ROs that overlap in the time and frequency domains for a single PRACH transmission, which are associated with a Type 2 RA procedure and have valid PRACH opportunities for a single PRACH transmission.

[0613] • Supports multiple PRACH transmissions with separate ROs that overlap in the time and frequency domains for MsgA PUSCH opportunities associated with Type 2 RA procedures.

[0614] • Supports multiple PRACH transmissions with separate ROs that overlap in the time domain for a single PRACH transmission and are associated with a Type 1 RA procedure for a single PRACH transmission.

[0615] • Supports multiple PRACH transmissions with separate ROs that overlap in the time domain for a single PRACH transmission and are associated with a Type 2 RA procedure for a single PRACH transmission.

[0616] • Supports separate RO for multiple PRACH transmissions that overlap in the time domain for MsgA PUSCH opportunities associated with Type 2 RA procedures.

[0617] Furthermore, the aforementioned specific UE capabilities can be applied across the entire frequency range (commonly independent of frequency), or per frequency (e.g., one or a combination of cells, bands, band combinations, BWPs, component carriers, etc.), or per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or per subcarrier spacing (SCS), or per feature set (FS) or per CC feature set (FSPS).

[0618] Furthermore, the aforementioned specific UE capabilities can be either capabilities that are applied in all duplex modes (common regardless of the duplex mode) or capabilities that are applicable to each duplex mode (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).

[0619] Furthermore, at least one of the above embodiments can also be applied when the UE is set / activated / triggered by specific information associated with the above embodiments (or performs the operation of the above embodiments) via higher-layer signaling / physical layer signaling. For example, the specific information may be information indicating activation of at least one operation of the above embodiments, arbitrary RRC parameters for a specific version (e.g., Rel. 18 / 19), etc.

[0620] In Rel.YY (for example, YY is 18 or higher), the RRC parameter of the activation operation XXX can also be represented as XXX_rYY (XXX-rYY).

[0621] Even if at least one of the specific UE capabilities mentioned above is not supported or the specific information mentioned above is not set, the UE may still apply the operation of Rel.15 / 16, for example.

[0622] (Postscript)

[0623] With respect to one embodiment of this disclosure, the following invention is noted.

[0624] [Postscript 1]

[0625] A terminal having:

[0626] The receiving unit receives settings for transmissions from multiple random access channels; and

[0627] The control unit, based on the settings, determines whether a random access channel opportunity (RO) for transmission of the plurality of random access channels conflicts with at least one of the following resources: a symbol indicated for reception of a synchronization signal block; a symbol set as downlink or flexible by time division multiplexing settings; a symbol indicated as downlink or flexible by a time slot format indicator; and a valid opportunity for transmission of a single random access channel.

[0628] [Postscript 2]

[0629] The terminal as described in Appendix 1, wherein,

[0630] If the RO is determined to conflict with the resource, the control unit will not include the RO in the plurality of ROs used for transmission of the plurality of random access channels.

[0631] [Postscript 3]

[0632] The terminal as described in Appendix 1 or Appendix 2, wherein,

[0633] If the RO is determined to conflict with the resource, the control unit includes the RO in the plurality of ROs used for transmitting the plurality of random access channels, and does not transmit the random access channel in the RO.

[0634] [Postscript 4]

[0635] The terminal as described in any of Notes 1 to 3, wherein,

[0636] The control unit applies the same beam or the same transmission configuration indicator (TCI) state in the multiple random access channels.

[0637] (Postscript)

[0638] With respect to one embodiment of this disclosure, the following invention is noted.

[0639] [Postscript 1]

[0640] A terminal having:

[0641] The receiving unit receives settings for transmissions from multiple random access channels; and

[0642] The control unit, based on the settings, determines a plurality of random access channel opportunities (ROs) to be used for transmission of the plurality of random access channels, and based on a specific RO among the plurality of ROs, determines at least one of the following: the window start for monitoring random access responses and the radio network temporary identifier (RNTI).

[0643] [Postscript 2]

[0644] The terminal as described in Appendix 1, wherein,

[0645] The specific RO is any one of the following among the plurality of ROs: the first valid RO, the last valid RO, the RO that was first actually transmitted to the random access channel, and the RO that was last actually transmitted to the random access channel.

[0646] [Postscript 3]

[0647] The terminal as described in Appendix 1 or Appendix 2, wherein,

[0648] The specific RO is any one of the following: the first valid RO, the last valid RO, the RO initially actually transmitted to the random access channel, and the RO last actually transmitted to the random access channel, wherein the one or more ROs does not conflict with at least one of the following resources: symbols indicated for receiving a synchronization signal block; symbols configured as downlink or flexible via time division multiplexing; symbols indicated as downlink or flexible via a time slot format indicator; and valid opportunities for transmission to a single random access channel.

[0649] [Postscript 4]

[0650] The terminal as described in any of Notes 1 to 3, wherein,

[0651] The control unit applies the same beam or the same transmission configuration indicator (TCI) state in the multiple random access channels.

[0652] (Wireless communication system)

[0653] The structure of a wireless communication system according to one embodiment of this disclosure will now be described. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above embodiments of this disclosure.

[0654] Figure 10 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment. The wireless communication system 1 (also referred to simply as System 1) may also be a system that uses Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5GNR) as standardized by the Third Generation Partnership Project (3GPP).

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

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

[0657] Wireless communication system 1 can also support dual connectivity between multiple base stations within the same RAT (e.g., MN and SN are dual connectivity between NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0658] The wireless communication system 1 may also include a base station 11 forming a macro cell C1 with a relatively wide coverage area, and a base station 12 (12a-12c) configured within the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. The user terminal 20 may also be located within at least one cell. The configuration and number of each cell and the user terminal 20 are not limited to the arrangement shown in the figure. Hereinafter, without distinguishing between base stations 11 and 12, they will be collectively referred to as base station 10.

[0659] User terminal 20 may also connect to at least one of multiple base stations 10. User terminal 20 may also utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

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

[0661] In addition, user terminal 20 can also use at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) to communicate in each CC.

[0662] Multiple base stations 10 can also be connected via wired (e.g., fiber optic, X2 interface, etc. based on Common Public Radio Interface (CPRI)) or wireless (e.g., NR communication). For example, when NR communication between base stations 11 and 12 is used as a backhaul, base station 11, which is equivalent to a host station, can also be referred to as an Integrated Access Backhaul (IAB) donor, and base station 12, which is equivalent to a relay station, can also be referred to as an IAB node.

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

[0664] The core network 30 may also include, for example, network functions (NFs) 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). Alternatively, multiple functions can be provided through a single network node. Furthermore, communication with external networks (e.g., the Internet) can also be achieved via the DN.

[0665] User terminal 20 can also be at least one terminal that supports communication methods such as LTE, LTE-A, and 5G.

[0666] In wireless communication system 1, wireless access methods based on Orthogonal Frequency Division Multiplexing (OFDM) can also be used. For example, in at least one of the downlink (DL) and uplink (UL) links, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA) can also be used.

[0667] The wireless access method can also be referred to as a waveform. In addition, in the wireless communication system 1, other wireless access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) can also be used in the wireless access methods of UL and DL.

[0668] As a downlink channel, the wireless communication system 1 can also use downlink shared channels (Physical Downlink Shared Channel (PDSCH)), broadcast channels (Physical Broadcast Channel (PBCH)), downlink control channels (Physical Downlink Control Channel (PDCCH)) and so on, which are shared among the user terminals 20.

[0669] In addition, as uplink channels, the wireless communication system 1 may also use uplink shared channels (Physical Uplink Shared Channel (PUSCH)), uplink control channels (Physical Uplink Control Channel (PUCCH)), random access channels (Physical Random Access Channel (PRACH)) and so on, which are shared by each user terminal 20.

[0670] User data, high-level control information, and System Information Blocks (SIBs) are transmitted via the PDSCH. User data and high-level control information can also be transmitted via the PUSCH. In addition, the Master Information Block (MIB) can also be transmitted via the PBCH.

[0671] Lower-layer control information can also be transmitted via PDCCH. Lower-layer control information may include, for example, downlink control information (DCI), which includes scheduling information for at least one of PDSCH and PUSCH.

[0672] Additionally, the DCI that schedules PDSCH can also be called DL allocation, DL DCI, etc., and the DCI that schedules PUSCH can also be called UL authorization, UL DCI, etc. Furthermore, PDSCH can be rewritten as DL data, and PUSCH can be rewritten as UL data.

[0673] In PDCCH detection, a Control Resource Set (CORESET) and a search space can also be utilized. A CORESET corresponds to the resources used to search for DCIs. The search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor CORESETs associated with a specific search space based on search space settings.

[0674] A search space can also correspond to a PDCCH candidate corresponding to one or more aggregation levels. One or more search spaces can also be referred to as a search space set. In addition, the terms "search space", "search space set", "search space setting", "search space set setting", "CORESET", and "CORESET setting" in this disclosure can be rewritten interchangeably.

[0675] At least one uplink control message (uplink control information (UCI)) containing channel state information (CSI), delivery confirmation information (such as Hybrid Automatic Repeat reQuest ACK knowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR) can also be transmitted via PUCCH. The random access preamble used to establish a connection with the cell can also be transmitted via PRACH.

[0676] In addition, in this disclosure, downlink, uplink, etc., may be described without the word "link". Furthermore, various channels may be described without the word "physical".

[0677] In wireless communication system 1, synchronization signals (SS) and downlink reference signals (DL-RS) can also be transmitted. As DL-RS, wireless communication system 1 can also transmit cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), positioning reference signals (PRS), phase tracking reference signals (PTRS), etc.

[0678] Synchronization signals can be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block containing SS (PSS, SSS) and PBCH (and DMRS for PBCH) can also be called an SS / PBCH block, SS block (SSB), etc. In addition, SS, SSB, etc. can also be called reference signals.

[0679] Furthermore, in wireless communication system 1, the uplink reference signal (UL-RS) can also transmit measurement reference signals (sounding reference signals (SRS)) and demodulation reference signals (DMRS). Additionally, DMRS can also be referred to as user terminal-specific reference signals (UE-specific reference signals).

[0680] (Base station)

[0681] Figure 11 This diagram illustrates an example of the structure of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmit / receive unit 120, a transmit / receive antenna 130, and a transmission path interface (transmission line interface) 140. Alternatively, the control unit 110, the transmit / receive unit 120, the transmit / receive antenna 130, and the transmission path interface 140 may each be provided in more than one manner.

[0682] Furthermore, in this example, only the functional blocks of the characteristic parts of this embodiment are shown. It can also be imagined that the base station 10 also has other functional blocks required for wireless communication. Some of the processing of each unit described below can also be omitted.

[0683] The control unit 110 performs overall control of the base station 10. The control unit 110 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the art to which this disclosure pertains.

[0684] The control unit 110 can also control signal generation and scheduling (e.g., resource allocation, mapping). The control unit 110 can also control transmission, reception, and measurement using the transmit / receive unit 120, transmit / receive antenna 130, and transmission path interface 140. The control unit 110 can also generate data, control information, sequences, etc., to be transmitted as signals and forward them to the transmit / receive unit 120. The control unit 110 can also perform call processing (setting, releasing, etc.) of the communication channel, status management of the base station 10, and management of wireless resources.

[0685] The transmitting / receiving unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting / receiving unit 120 may be composed of transmitters / receivers, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmitting / receiving circuits, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0686] The transmitting and receiving unit 120 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 1211 and an RF unit 122. The receiving unit can also be composed of a receiving processing unit 1212, an RF unit 122, and a measurement unit 123.

[0687] The transmitting and receiving antenna 130 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

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

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

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

[0691] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform transmission processing such as channel coding (which may also include error correction coding), modulation, mapping, filter processing (filtering processing), Discrete Fourier Transform (DFT) processing (as needed), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output the baseband signal.

[0692] The transmitting and receiving unit 120 (RF unit 122) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 130.

[0693] On the other hand, the transmitting and receiving unit 120 (RF unit 122) can also amplify, filter, and demodulate the signals of the wireless frequency band received through the transmitting and receiving antenna 130 into the baseband signal.

[0694] The transmitting and receiving unit 120 (receiving and processing unit 1212) can also perform receiving and processing on the acquired baseband signal, including analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to acquire user data.

[0695] The transmitting / receiving unit 120 (measurement unit 123) can also perform measurements related to the received signal. For example, the measurement unit 123 can also perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc., based on the received signal. The measurement unit 123 can also measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results can also be output to the control unit 110.

[0696] The transmission path interface 140 can also transmit and receive signals (backhaul signaling) between the device included in the core network 30 (e.g., the network node providing the NF), other base stations 10, etc., and can also acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0697] In addition, the transmitting unit and receiving unit of the base station 10 in this disclosure may also be composed of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0698] Additionally, the transmit / receive unit 120 can also transmit settings for multiple random access channel transmissions. The control unit 110 can also, based on these settings, determine whether a random access channel opportunity (RO) for the multiple random access channel transmissions conflicts with at least one of the following resources: symbols indicated for receiving a synchronization block; symbols configured as downlink or flexible via time division multiplexing settings; symbols indicated as downlink or flexible via a time slot format indicator; and valid opportunities for a single random access channel transmission.

[0699] Additionally, the transmit / receive unit 120 can also transmit settings for multiple random access channels. The control unit 110 can also, based on these settings, determine multiple random access channel opportunities (ROs) to be used for the transmission of the multiple random access channels, and, based on a specific RO among the multiple ROs, determine at least one of the following: the window start for monitoring random access responses and the radio network temporary identifier (RNTI).

[0700] (User terminal)

[0701] Figure 12 This diagram illustrates an example of the structure 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. Alternatively, the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may each be provided as one or more.

[0702] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the user terminal 20 may also have other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0703] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the technical field to which this disclosure pertains.

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

[0705] The transmitting / receiving unit 220 may also include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may also include a transmitting processing unit 2211 and a receiving processing unit 2212. The transmitting / receiving unit 220 may be composed of transmitters / receivers, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmitting / receiving circuits, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0706] The transmitting and receiving unit 220 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit can also be composed of a receiving processing unit 2212, an RF unit 222, and a measurement unit 223.

[0707] The transmitting and receiving antenna 230 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0708] The transmitting / receiving unit 220 can also receive the downlink channel, synchronization signal, downlink reference signal, etc., mentioned above. The transmitting / receiving unit 220 can also transmit the uplink channel, uplink reference signal, etc., mentioned above.

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

[0710] The transmitting and receiving unit 220 (transmitting processing unit 2211) may, for example, perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control) on the data and control information obtained from the control unit 210, and generate a bit string to be transmitted.

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

[0712] Furthermore, whether or not to apply DFT processing can be based on the transform precoding settings. For a certain channel (e.g., PUSCH), if transform precoding is enabled, the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as described above for transmitting the channel using the DFT-s-OFDM waveform; otherwise, the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as described above for transmitting the channel without performing DFT processing.

[0713] The transmitting and receiving unit 220 (RF unit 222) can also perform modulation, filtering (filtering), amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 230.

[0714] On the other hand, the transmitting and receiving unit 220 (RF unit 222) can also amplify, filter (filter) and demodulate the baseband signal for the wireless frequency band signal received by the transmitting and receiving antenna 230.

[0715] The transmitting and receiving unit 220 (receiving and processing unit 2212) can also perform receiving and processing on the acquired baseband signal, such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, and acquire user data.

[0716] The transmitting / receiving unit 220 (measurement unit 223) can also perform measurements related to the received signal. For example, the measurement unit 223 can also perform RRM measurements, CSI measurements, etc., based on the received signal. The measurement unit 223 can 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 can also be output to the control unit 210.

[0717] Additionally, the measurement unit 223 can also derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources can be, for example, non-zero power (NZP) CSI-RS resources. Furthermore, the measurement unit 223 can also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources can be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. Additionally, CSI-IM can also be referred to as CSI-Interference Management (IM), and can be interchanged with zero power (ZP) CSI-RS. Furthermore, in this disclosure, CSI-RS, NZPCSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., can also be interchanged.

[0718] Alternatively, the transmitting and receiving units of the user terminal 20 in this disclosure may also be composed of at least one transmitting / receiving unit 220 and transmitting / receiving antenna 230.

[0719] Additionally, the transmit / receive unit 220 can also receive settings for transmission via multiple random access channels. The control unit 210 can also, based on these settings, determine whether a random access channel opportunity (RO) for transmission via the multiple random access channels conflicts with at least one of the following resources: symbols indicated for reception of a synchronization signal block; symbols configured as downlink or flexible via time division multiplexing settings; symbols indicated as downlink or flexible via a time slot format indicator; and valid opportunities for transmission via a single random access channel.

[0720] If the RO is determined to conflict with the resource, the control unit 210 may also exclude the RO from the plurality of ROs used for transmission of the plurality of random access channels.

[0721] If the RO is determined to conflict with the resource, the control unit 210 may also include the RO in the plurality of ROs used for transmitting the plurality of random access channels, and not transmit the random access channel in the RO.

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

[0723] Additionally, the transmit / receive unit 220 can also receive settings for multiple random access channel transmissions. The control unit 210 can also, based on these settings, determine multiple random access channel opportunities (ROs) used for the transmissions of the multiple random access channels, and, based on a specific RO among the multiple ROs, determine at least one of the following: the window start for monitoring random access responses and the radio network temporary identifier (RNTI).

[0724] The specific RO can also be any one of the following among the plurality of ROs: the first valid RO, the last valid RO, the RO that was first actually transmitted to the random access channel, and the RO that was last actually transmitted to the random access channel.

[0725] The specific RO can also be any one of more than one ROs, including the first valid RO, the last valid RO, the RO initially actually transmitted to the random access channel, and the RO last actually transmitted to the random access channel, wherein the more than one RO does not conflict with at least one of the following resources: symbols indicated for receiving a synchronization signal block; symbols configured as downlink or flexible via time division multiplexing; symbols indicated as downlink or flexible via a time slot format indicator; and valid opportunities for transmission to a single random access channel.

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

[0727] (Hardware structure)

[0728] Furthermore, the block diagrams used in the description of the above embodiments illustrate functional units. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Moreover, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using a single device that is physically or logically combined, or it can be implemented by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. A functional block can also be implemented by combining the aforementioned single device or multiple devices with software.

[0729] Here, the functions include judgment, decision, determination, calculation, calculation, processing, export, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, regard as, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, a functional block (structural unit) that implements the sending function can also be called a transmitting unit, transmitter, etc. Each of these, as described above, is not particularly limited in its implementation method.

[0730] For example, in one embodiment of this disclosure, the base station, user terminal, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 13This diagram illustrates an example of the hardware structure of a base station and a user terminal according to one embodiment. The base station 10 and the user terminal 20 described above can also be physically configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0731] Furthermore, in this disclosure, terms such as apparatus, circuit, device, section, and unit can be interchanged. The hardware structure of base station 10 and user terminal 20 can be configured to include one or more of the apparatuses shown in the figures, or it can be configured not to include any of the apparatuses.

[0732] For example, only one processor 1001 is shown, but there can be multiple processors. Furthermore, processing can be performed by one processor, or simultaneously, sequentially, or by two or more processors using other methods. Additionally, processor 1001 can be implemented using more than one chip.

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

[0734] The processor 1001 enables the operating system to operate and control the computer as a whole. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic devices, registers, etc. For example, at least a portion of the control unit 110 (210), the transmit / receive unit 120 (220), etc., described above may also be implemented by the processor 1001.

[0735] 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 performs various processes accordingly. As a program, a program that causes the computer to perform at least a portion of the operations described in the above embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operated in the processor 1001; similar implementations can be made for other functional blocks.

[0736] The memory 1002 may also be a computer-readable recording medium, such as being composed of at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage media. The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 is capable of storing executable programs (program code), software modules, etc., for implementing the wireless communication method according to an embodiment of this disclosure.

[0737] Storage device 1003 may also be a computer-readable recording medium, such as a flexible disc, floppy disk, optical disk (e.g., a compact disc ROM), digital multifunction disk, Blu-ray disc, removable disk, hard disk drive, smart card, flash memory device (e.g., a card, stick, key drive), magnetic stripe, database, server, or at least one other suitable storage medium. Storage device 1003 may also be referred to as an auxiliary storage device.

[0738] The communication device 1004 is hardware (transmitting and receiving device) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. To implement at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD), the communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the aforementioned transmit / receive unit 120 (220) and transmit / receive antenna 130 (230) may also be implemented by the communication device 1004. The transmit / receive unit 120 (220) may also be implemented by physically or logically separating the transmit unit 120a (220a) and the receive unit 120b (220b).

[0739] Input device 1005 is an input device that receives input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, light-emitting diode (LED) lamp, etc.). Alternatively, input device 1005 and output device 1006 can also be an integrated structure (e.g., a touch panel).

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

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

[0742] (Modified example)

[0743] Furthermore, the terms described in this disclosure, as well as those necessary for understanding this disclosure, may be replaced with terms that have the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be interchanged. Additionally, a signal may also be a message. A reference signal can also be abbreviated as RS, and may be referred to as pilot, pilot signal, etc., depending on the applied standard. Furthermore, a component carrier (CC) may also be referred to as cell, frequency carrier, carrier frequency, etc.

[0744] A radio frame can also be composed of one or more periods (frames) in the time domain. Each of these periods (frames) that constitute a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

[0745] Here, the parameter set can also be communication parameters applied in at least one of the transmission and reception of a signal or channel. For example, the parameter set can also represent 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 structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, and specific windowing processing performed by the transmitter and receiver in the time domain.

[0746] In the time domain, a time slot can also be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.). In addition, a time slot can also be a time unit based on a set of parameters.

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

[0748] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can also use their respective other names. Furthermore, the time units such as frames, subframes, time slots, mini-time slots, and symbols in this disclosure can be interchanged.

[0749] For example, a subframe can also be called a TTI, multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is, at least one of a subframe and a TTI can be a subframe in existing LTE (1ms), a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but rather a time slot, mini-time slot, etc.

[0750] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules radio resources (frequency bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0751] TTI can also be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., and can also be a unit of processing such as scheduling and link adaptation. In addition, when a TTI is given, the actual time interval (e.g., the number of symbols) mapped to transmission blocks, code blocks, codewords, etc. can be shorter than the TTI.

[0752] Additionally, where a time slot or a mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can also serve as the minimum time unit for scheduling. Furthermore, the number of time slots (mini-time slots) constituting the minimum time unit of the schedule can also be controlled.

[0753] A TTI with a duration of 1ms can also be referred to as a normal TTI (TTI in 3GPPRel.8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI can also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub-time slot, a time slot, etc.

[0754] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) can also be rewritten as a TTI with a duration of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) can also be rewritten as a TTI with a duration of less than a long TTI but more than 1 ms.

[0755] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can also contain one or more consecutive subcarriers. The number of subcarriers in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers in an RB can also be determined based on the parameter set.

[0756] Furthermore, an RB can contain one or more symbols in the time domain, and can also be a time slot, a mini-time slot, a subframe, or the length of a TTI. A TTI, a subframe, etc., can also be composed of one or more resource blocks.

[0757] In addition, one or more RBs can also be referred to as Physical Resource Blocks (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0758] In addition, a resource block can also consist of one or more resource elements (REs). For example, an RE can also be a radio resource area consisting of a subcarrier and a symbol.

[0759] The Bandwidth Part (BWP) (also referred to as partial bandwidth, etc.) can also represent a subset of consecutive common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can also be determined by the index of RBs based on the common reference point of the carrier. PRBs can also be defined in a BWP and appended with numbers within that BWP.

[0760] A BWP can also include a UL BWP (the BWP used by UL) and a DL BWP (the BWP used by DL). For a UE, one or more BWPs can also be set within a single carrier.

[0761] At least one of the configured BWPs can be active, and the UE may not intend to transmit or receive specific signals / channels outside of the active BWPs. Additionally, terms such as "cell" and "carrier" in this disclosure may be replaced with "BWP".

[0762] Furthermore, the structures described above, such as radio frames, subframes, time slots, mini-time slots, and symbols, are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

[0763] Furthermore, the information, parameters, etc., described in this disclosure can be represented by absolute values, relative values ​​with respect to a specific value, or other corresponding information. For example, wireless resources can also be indicated by a specific index.

[0764] In this disclosure, the names used for parameters, etc., are not limiting names in any respect. Furthermore, the mathematical expressions, etc., using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name; therefore, the various names assigned to these various channels and information elements are not limiting names in any respect.

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

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

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

[0768] The notification of information is not limited to the methods / implementations described in this disclosure, and may also be carried out by other methods. For example, the notification of information in this disclosure may also be implemented by physical layer signaling (e.g., downlink control information (DCI), uplink control information (UCI), etc.), higher layer signaling (e.g., radio resource control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB) etc.), medium access control (MAC) signaling), other signals, or combinations thereof.

[0769] In addition, physical layer signaling can also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. Furthermore, RRC signaling can also be referred to as RRC messages, such as RRC connection setup messages, RRC connection reconfiguration messages, etc. Additionally, MAC signaling can also be notified using, for example, the MAC control element (CE).

[0770] Furthermore, notification of specific information (e.g., a notification of “is X”) is not limited to explicit notification, but can also be implicit (e.g., by not providing that specific information, or by providing other information).

[0771] The determination can be made by a value represented by a single bit (0 or 1), by a true or false value (boolean), or by a numerical comparison (e.g., a comparison with a specific value).

[0772] Whether software is called software, firmware, middleware, microcode, hardware description language, or any other name, it should be broadly interpreted to refer to 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, etc.

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

[0774] The terms “system” and “network” as used in this disclosure are interchangeable. “Network” may also mean devices included in a network (e.g., base stations).

[0775] In this disclosure, the terms “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”, “beamwidth”, “beam angle”, “antenna”, “antenna element”, “panel”, “UE panel”, “transmitting entity”, and “receiving entity” are used interchangeably.

[0776] Furthermore, in this disclosure, the antenna port can also be rewritten with an antenna port used for any signal / channel (e.g., a DeModulation Reference Signal (DMRS) port). In this disclosure, the resources can also be rewritten with resources used for any signal / channel (e.g., reference signal resources, SRS resources, etc.). Additionally, the resources may also include time / frequency / code / space / power resources. Moreover, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0777] The aforementioned groups may include, for example, at least one of the following: spatial relation group, code division multiplexing (CDM) group, reference signal (RS) group, control resource set (CORESET) group, PUCCH group, antenna port group (e.g., DMRS port group), layer group, resource group, beam group, antenna group, panel group, etc.

[0778] Furthermore, in this disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), RS, etc., can also be rewritten to each other.

[0779] Furthermore, in this disclosure, the TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, and joint TCI state can also be rewritten to each other.

[0780] Furthermore, in this disclosure, terms such as "QCL", "QCL concept", "QCL relationship", "QCL type information", "QCL property (QCLproperty / properties)", "specific QCL type (e.g., type A, type D) property", and "specific QCL type (e.g., type A, type D)" can be rewritten interchangeably.

[0781] In this disclosure, indexes, identifiers (IDs), indicators, indications, resource IDs, etc., can be interchanged. Sequences, lists, sets, groups, clusters, subsets, etc., can also be interchanged.

[0782] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) can be interchanged. "Spatial relationship information (TCI state)" can also be interchanged with "a set of spatial relationship information (TCI states)," "one or more spatial relationship information," etc. TCI state and TCI can also be interchanged. Spatial relationship information and spatial relationships can also be interchanged.

[0783] In this disclosure, the terms "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" are used interchangeably. There are also instances where the terms macro cell, small cell, femtocell, and picocell are used to refer to a base station.

[0784] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, its overall coverage area can be divided into several smaller areas, each of which can also provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0785] In this disclosure, the act of a base station sending information to a terminal can also be rewritten in relation to the act of the base station instructing the terminal to perform control / operation based on that information.

[0786] In this disclosure, the terms “Mobile Station (MS)”, “user terminal”, “user equipment (UE)”, and “terminal” are used interchangeably.

[0787] There are also instances where mobile stations are referred to as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or several other appropriate terms.

[0788] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Additionally, at least one of the base station and the mobile station can also be a device mounted on a moving object, the moving object itself, etc.

[0789] The term "mobile body" refers to a movable object whose speed is arbitrary, including situations where the body is stationary. Examples of such mobile bodies include vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships (ships and other watercraft), airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, hot air balloons, and objects carried on them, but are not limited to these. Furthermore, the mobile body can also be a mobile body that moves autonomously based on operational commands.

[0790] The mobile entity can be a means of transportation (e.g., a vehicle, an airplane, etc.), a mobile entity moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Additionally, at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station can also be an Internet of Things (IoT) device such as a sensor.

[0791] Figure 14 This is a diagram illustrating 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 speed sensor 51, a 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.

[0792] The drive unit 41 is comprised of at least one of an engine, a motor, or a combination of an engine and a motor. The steering unit 42 is configured to include at least a steering wheel (also called a steering handle) that steers at least one of the front wheels 46 and the rear wheels 47 based on operation of the steering wheel by the user.

[0793] The electronic control unit 49 consists of a microprocessor 61, a memory (ROM, RAM) 62, and a communication port (e.g., an input / output (IO) port) 63). Signals from various sensors 50-58 present in the vehicle are input to the electronic control unit 49. The electronic control unit 49 can also be referred to as an electronic control unit (ECU).

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

[0795] The information service unit 59 consists of various devices for providing (outputting) various information such as driving information, traffic information, and entertainment information, including navigation systems, audio systems, speakers, displays, televisions, and radios, as well as one or more ECUs for controlling these devices. The information service unit 59 uses information obtained from external devices via the communication module 60, etc., to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

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

[0797] The driver assistance system unit 64 comprises various devices used to provide functions for preventing accidents or reducing the driver's workload, such as millimeter-wave radar, light detection and ranging (LiDAR), cameras, positioning detectors (e.g., Global Navigation Satellite System (GNSS), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyroscope systems (e.g., Inertial Measurement Unit (IMU), Inertial Navigation System (INS), etc.), artificial intelligence (AI) chips, and AI processors, and one or more ECUs that control these devices. Furthermore, the driver assistance system unit 64 sends and receives various information via communication module 60 to realize driver assistance functions or autonomous driving functions.

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

[0799] The communication module 60 can be controlled by the microprocessor 61 of the electronic control unit 49 and is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information with external devices via wireless communication. The communication module 60 can be located both inside and outside the electronic control unit 49. The external device can be, for example, the aforementioned base station 10, user terminal 20, etc. Furthermore, the communication module 60 can be, for example, at least one of the aforementioned base station 10 and user terminal 20 (or it can function as at least one of the base station 10 and user terminal 20).

[0800] The communication module 60 can also wirelessly transmit at least one of the signals input to the electronic control unit 49 from the various sensors 50-58 described above, the information obtained based on these signals, and the information based on input from an external (user) source obtained via the information service unit 59 to an external device. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., can also be referred to as input units that receive input. For example, the PUSCH transmitted via the communication module 60 can also contain information based on the aforementioned inputs.

[0801] The communication module 60 receives various information (traffic information, signal information, workshop information, etc.) sent from external devices and displays it on the vehicle's information service unit 59. The information service unit 59 can also be referred to as an output unit that outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH received by the communication module 60 (or the data / information decoded from the PDSCH).

[0802] Furthermore, the communication module 60 stores various types of information received from external devices into a memory 62 that can be utilized by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 can also control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, gear shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, and various sensors 50-58, etc., of the vehicle 40.

[0803] Furthermore, the base station in this disclosure can also be rewritten as a user terminal. For example, various methods / implementations of this disclosure can be applied to structures where communication between the base station and the user terminal is replaced by communication between multiple user terminals (e.g., also referred to as device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, it can also be configured such that the user terminal 20 has the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be rewritten as terms corresponding to inter-terminal communication (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can also be rewritten as sidelink channel.

[0804] Similarly, the user terminal in this disclosure can also be rewritten as a base station. In this case, it can also be configured such that the base station 10 has the functions of the user terminal 20 described above.

[0805] In this disclosure, actions are assumed to be performed by the base station, and sometimes, depending on the circumstances, by its upper node. In a network containing one or more network nodes having a base station, the various operations performed for communication with a terminal can obviously be performed by the base station, one or more network nodes other than the base station (e.g., consider a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc., but not limited to these), or combinations thereof.

[0806] The various methods / implementations described in this disclosure can be used individually or in combination, and can be switched as needed during execution. Furthermore, the processing procedures, timing sequences, flowcharts, etc., of the various methods / implementations described in this disclosure can be rearranged as long as they do not contradict each other. For example, for the method described in this disclosure, the illustrated order is used to indicate various steps, but the order in which they are indicated is not limited.

[0807] The various methods / implementations described in this disclosure can also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG, where x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Futuregeneration Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE This includes 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-Wideband (UWB)), Bluetooth (registered trademark), systems utilizing other suitable wireless communication methods, and next-generation systems derived from, modified, generated, or specified based on these methods. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A, combinations with 5G, etc.) for application.

[0808] As used in this disclosure, the term "based on" does not mean "based on only" unless otherwise specified. In other words, the term "based on" means both "based on only" and "based on at least".

[0809] Any reference to an element using the designations "first," "second," etc., as used in this disclosure does not comprehensively limit the quantity or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to the first and second elements does not imply that only two elements may be used, or that the first element must take precedence over the second element in some form.

[0810] The term "determining" as used in this disclosure can encompass a wide variety of operations. For example, "determining" can also refer to judging, calculating, computing, processing, deriving, investigating, looking up (search, inquiry) (e.g., searching in a table, database or other data structure), and ascertaining.

[0811] In addition, "judgment (decision)" can also refer to receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, accessing (e.g., accessing data in memory), etc., as situations where "judgment (decision)" is performed.

[0812] Furthermore, "judgment (decision)" can also refer to situations where resolving, selecting, choosing, establishing, or comparing are considered as making a "judgment (decision)". That is, "judgment (decision)" can also refer to certain operations as situations where a "judgment (decision)" is made. In this disclosure, "judgment (decision)" can also be rewritten in relation to the operations described above.

[0813] Furthermore, in this disclosure, "determine / determining" can also be interchanged with "assume / assuming," "expect / expecting," "consider / considering," etc. Additionally, in this disclosure, "not assuming to proceed..." can also be interchanged with "assuming not to proceed..."

[0814] In this disclosure, "expect" can also be interchanged with "be expected." For example, "expect(s) ..." ("..." can also be expressed using a "that" clause, an indefinite "to", etc.) can be interchanged with "be expected ...." "Does not expect..." can also be interchanged with "be not expected...". Furthermore, "An apparatus A is not expected..." can also be interchanged with "Apparatus B other than apparatus A does not expect..." (for example, if apparatus A is a UE, apparatus B can also be a base station).

[0815] The term "maximum transmit power" as used in this disclosure may refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated UE maximum transmit power).

[0816] As used in this disclosure, the terms “connected,” “coupled,” or all variations thereof, refer to all direct or indirect connections or combinations between two or more elements, and can include cases where there is one or more intermediate elements between two mutually “connected” or “coupled” elements. The connections or combinations between elements can be physical, logical, or a combination thereof. For example, “connection” can also be rewritten as “access.”

[0817] In this disclosure, when two elements are connected, it is possible to consider using more than one wire, cable, printed electrical connection, etc. to be "connected" or "combined" with each other, and as several non-limiting and non-exclusive examples, to use electromagnetic energy with wavelengths having wireless frequency domain, microwave region, light (both visible and invisible) region to be "connected" or "combined" with each other.

[0818] In this disclosure, the term "A is different from B" can also mean "A and B are different from each other." Additionally, the term can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0819] When the terms "include," "including," and variations thereof are used in this disclosure, these terms, like the term "comprising," mean inclusive. Furthermore, the term "or" as used in this disclosure does not mean XOR.

[0820] In this disclosure, for example, in cases where articles are added through translation, such as a, an, and the in English, the disclosure may also include cases where the noun following these articles is in a plural form.

[0821] In this disclosure, words such as "below," "less than," "above," "more," and "equal to" can be interchanged. Furthermore, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "early," "slow," "wide," and "narrow," etc., are not limited to the positive, comparative, and superlative degrees, and can be interchanged. Additionally, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "early," "slow," "wide," and "narrow," etc., as expressions appended with "the i-th" (where i is any integer), are not limited to the positive, comparative, and superlative degrees, and can be interchanged (for example, "highest" can also be interchanged with "the i-th highest").

[0822] In this disclosure, "of", "for", "regarding", "related to", "associated with", etc., can also be rewritten interchangeably.

[0823] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "in response to A", "based on A", "during / while A", "before A", "at (the same time as) / on A", "after A", "since A", and "until A" can be rewritten interchangeably. Furthermore, A and B can be replaced with nouns, gerunds, or ordinary sentences depending on the context. Additionally, the time difference between A and B can be approximately 0 (immediately after or immediately before). Moreover, a time offset can be applied to the time A occurs. For example, "A" can be rewritten interchangeably with "before / after the time offset of A". This time offset (e.g., more than one symbol / slot) can be predetermined or determined by the UE based on the information it is notified of.

[0824] In this disclosure, timing, moment, time, time instance, arbitrary time unit (e.g., time slot, sub-time slot, symbol, subframe), period, opportunity, resource, etc., can also be overridden.

[0825] The inventions disclosed herein have been described in detail above. However, it will be apparent to those skilled in the art that the inventions disclosed herein are not limited to the embodiments described herein. The description herein is for illustrative purposes only and is not intended to limit the inventions disclosed herein in any way.

[0826] This application is based on Japan Patent Application No. 2023-68752, filed on April 19, 2023. Its entire contents are contained herein.

Claims

1. A terminal having: a reception unit that receives settings for a plurality of random access channel transmissions; and a control unit that determines, based on the settings, whether a random access channel occasion (RO) for the plurality of random access channel transmissions collides with at least one of a symbol indicated for reception of a synchronization signal block, a symbol set as downlink or flexible by time division multiplexing settings, a symbol indicated as downlink or flexible by a slot format indicator, and a valid occasion for a single random access channel transmission.

2. The terminal according to claim 1, wherein, in a case where the RO is determined to collide with the resource, the control unit does not include the RO in a plurality of ROs for the plurality of random access channel transmissions.

3. The terminal according to claim 1, wherein, in a case where the RO is determined to collide with the resource, the control unit includes the RO in a plurality of ROs for the plurality of random access channel transmissions and does not transmit a random access channel in the RO.

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

5. A wireless communication method, which is a wireless communication method of a terminal, having: a step of receiving settings for a plurality of random access channel transmissions; and a step of determining, based on the settings, whether a random access channel occasion (RO) for the plurality of random access channel transmissions collides with at least one of a symbol indicated for reception of a synchronization signal block, a symbol set as downlink or flexible by time division multiplexing settings, a symbol indicated as downlink or flexible by a slot format indicator, and a valid occasion for a single random access channel transmission.

6. A base station having: a transmission unit that transmits settings for a plurality of random access channel transmissions; and a control unit that determines, based on the settings, whether a random access channel occasion (RO) for the plurality of random access channel transmissions collides with at least one of a symbol indicated for reception of a synchronization signal block, a symbol set as downlink or flexible by time division multiplexing settings, a symbol indicated as downlink or flexible by a slot format indicator, and a valid occasion for a single random access channel transmission. ​ ​ ​ ​ ​ ​ ​ ​ ​

Images