WO2023119647A1 - Terminal, procédé de communication sans fil et station de base - Google Patents

Terminal, procédé de communication sans fil et station de base Download PDF

Info

Publication number
WO2023119647A1
WO2023119647A1 PCT/JP2021/048309 JP2021048309W WO2023119647A1 WO 2023119647 A1 WO2023119647 A1 WO 2023119647A1 JP 2021048309 W JP2021048309 W JP 2021048309W WO 2023119647 A1 WO2023119647 A1 WO 2023119647A1
Authority
WO
WIPO (PCT)
Prior art keywords
prach
repetition
ssb
resource
repetitions
Prior art date
Application number
PCT/JP2021/048309
Other languages
English (en)
Japanese (ja)
Inventor
祐輝 松村
尚哉 芝池
聡 永田
ジン ワン
チーピン ピ
ラン チン
Original Assignee
株式会社Ｎｔｔドコモ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社Ｎｔｔドコモ filed Critical 株式会社Ｎｔｔドコモ
Priority to JP2023569009A priority Critical patent/JPWO2023119647A1/ja
Priority to PCT/JP2021/048309 priority patent/WO2023119647A1/fr
Publication of WO2023119647A1 publication Critical patent/WO2023119647A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/28—Cell structures using beam steering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA

Definitions

  • the present disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems.
  • LTE Long Term Evolution
  • 3GPP Rel. 10-14 LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of further increasing the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).
  • LTE successor systems for example, 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later
  • 5G 5th generation mobile communication system
  • 5G+ 5th generation mobile communication system
  • 6G 6th generation mobile communication system
  • NR New Radio
  • the random access procedure for improving coverage is not clear. If such a random access procedure is not clear, communication throughput may decrease.
  • one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that improve the coverage of random access procedures.
  • a terminal uses a plurality of different beams to transmit a plurality of repetitions of a physical random access channel, and receives a response to the physical random access channel within one or more windows. and a control unit for controlling the
  • FIG. 1 shows an example of a RACH configuration information element.
  • 2A and 2B show an example of PRACH occasion and beam association.
  • FIG. 3 shows an example of PRACH configuration.
  • FIG. 4 shows an example of PRACH mask index values.
  • FIG. 5 shows an example of RA configuration for BFR.
  • 6A-6D show an example of a RAR window according to embodiment #4.
  • 7A and 7B show an example of a RAR window for PRACH repetition within a short period according to embodiment #4.
  • 8A and 8B show another example of a RAR window for PRACH repetition within a short period according to embodiment #4.
  • 9A and 9B show an example of option A of embodiment #10.
  • 10A and 10B show an example of Option B of Embodiment #10.
  • 11A and 11B show an example of option A of embodiment #11.
  • FIG. 12A and 12B show an example of Option B of Embodiment #11.
  • 13A and 13B show an example of unit resource 1/2.
  • 14A and 14B show an example of the unit resource 3.
  • FIG. 15A and 15B show an example of unit resource 4/5.
  • 16A and 16B show another example of the unit resource 5.
  • FIG. 17 shows yet another example of the unit resource 5.
  • FIG. 18A and 18B show an example of a unit resource 2 according to variation A.
  • FIG. 19A and 19B show an example of a unit resource 5 according to variation A.
  • FIG. 20A and 20B show an example of variation A1.
  • 21 shows an example of transmission operation 1.
  • FIG. 22 shows an example of transmission operation 2.
  • FIG. 23 shows an example of transmission operation 3.
  • FIG. FIG. 24 shows an example of monitoring operation 2.
  • FIG. 25 shows an example of window operation 1/2.
  • FIG. 26 shows an example of window operation 3a/3b/3c.
  • Figures 27A and 27B show an example of embodiment #A9.
  • Figures 28A and 28B show an example of the new instructions.
  • 29A and 29B are diagrams showing an example of RO for PRACH repetition according to embodiment #B1.
  • 30A and 30B are diagrams illustrating another example of RO for PRACH repetition according to embodiment #B1.
  • 31A and 31B are diagrams showing an example of RO for PRACH repetition according to embodiment #B2.
  • 32A and 32B are diagrams showing an example of RO for PRACH repetition according to embodiment #B3.
  • 33A and 33B are diagrams illustrating another example of RO for PRACH repetition according to embodiment #B3.
  • FIG. 34 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment
  • FIG. 35 is a diagram illustrating an example of a configuration of a base station according to an embodiment
  • FIG. 36 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment
  • FIG. 37 is a diagram illustrating an example of hardware configurations of a base station and user terminals according to an embodiment.
  • FIG. 38 is a diagram illustrating an example of a vehicle according to one embodiment
  • the reception processing e.g., reception, demapping, demodulation, decoding
  • transmission processing e.g, at least one of transmission, mapping, precoding, modulation, encoding
  • the TCI state may represent those that apply to downlink signals/channels.
  • the equivalent of TCI conditions applied to uplink signals/channels may be expressed as spatial relations.
  • the TCI state is information about the pseudo-co-location (QCL) of signals/channels, and may be called spatial reception parameters, spatial relation information, or the like.
  • the TCI state may be set in the UE on a channel-by-channel or signal-by-signal basis.
  • QCL is an index that indicates the statistical properties of a signal/channel. For example, when one signal/channel and another signal/channel have a QCL relationship, Doppler shift, Doppler spread, average delay ), delay spread, spatial parameters (e.g., spatial Rx parameter) are identical (QCL with respect to at least one of these). You may
  • the spatial reception parameters may correspond to the reception beams of the UE (eg, reception analog beams), and the beams may be specified based on the spatial QCL.
  • QCL or at least one element of QCL in the present disclosure may be read as sQCL (spatial QCL).
  • QCL types A plurality of types (QCL types) may be defined for the QCL.
  • QCL types AD may be provided with different parameters (or parameter sets) that can be assumed to be the same, and the parameters (which may be referred to as QCL parameters) are shown below:
  • QCL type A QCL-A
  • QCL type B QCL-B
  • QCL type C QCL-C
  • QCL-D Spatial reception parameters.
  • CORESET Control Resource Set
  • QCL QCL type D
  • a UE may determine at least one of a transmit beam (Tx beam) and a receive beam (Rx beam) for a signal/channel based on the TCI conditions or QCL assumptions of that signal/channel.
  • Tx beam transmit beam
  • Rx beam receive beam
  • the TCI state may be, for example, information about the QCL between the channel of interest (in other words, the reference signal (RS) for the channel) and another signal (for example, another RS). .
  • the TCI state may be set (indicated) by higher layer signaling, physical layer signaling or a combination thereof.
  • Physical layer signaling may be, for example, downlink control information (DCI).
  • DCI downlink control information
  • Channels for which TCI states or spatial relationships are set are, for example, Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), Physical Uplink Shared Channel It may be at least one of a channel (PUSCH)) and an uplink control channel (Physical Uplink Control Channel (PUCCH)).
  • PDSCH Physical Downlink Shared Channel
  • PDCCH Physical Uplink Control Channel
  • RSs that have a QCL relationship with the channel are, for example, a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a measurement reference signal (Sounding It may be at least one of a reference signal (SRS)), a tracking CSI-RS (also called a tracking reference signal (TRS)), and a QCL detection reference signal (also called a QRS).
  • SSB synchronization signal block
  • CSI-RS channel state information reference signal
  • Sounding It may be at least one of a reference signal (SRS)), a tracking CSI-RS (also called a tracking reference signal (TRS)), and a QCL detection reference signal (also called a QRS).
  • SRS reference signal
  • TRS tracking reference signal
  • QRS QCL detection reference signal
  • An SSB is a signal block that includes at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • PBCH Physical Broadcast Channel
  • An SSB may also be called an SS/PBCH block.
  • a QCL type X RS in a TCI state may mean an RS that has a QCL type X relationship with (the DMRS of) a certain channel/signal, and this RS is called a QCL type X QCL source in that TCI state.
  • the UE receives the SS/PBCH block (SSB), Msg. 1 (PRACH/random access preamble/preamble), Msg. 2 (PDCCH, PDSCH containing random access response (RAR)), Msg. 3 (PUSCH scheduled by RAR UL grant) transmission, Msg. 4 (PDCCH, PDSCH including UE contention resolution identity).
  • Msg. is transmitted from the UE by the base station (network). 4 is sent, the RRC connection is established (RRC_CONNECTED mode).
  • SSB reception includes PSS detection, SSS detection, PBCH-DMRS detection, and PBCH reception.
  • PSS detection provides partial detection of the physical cell ID (PCI), detection of OFDM symbol timing (synchronization), and (coarse) frequency synchronization.
  • SSS detection includes detection of physical cell ID.
  • PBCH-DMRS detection involves detection of (part of) the SSB index within a half radio frame (5ms).
  • PBCH reception includes detection of the system frame number (SFN) and radio frame timing (SSB index), reception of configuration information for remaining minimum system information (RMSI, SIB1) reception, and the UE being able to camp on that cell (carrier). and recognizing whether or not
  • the SSB has a bandwidth of 20 RBs and a time of 4 symbols.
  • the SSB transmission cycle can be set from ⁇ 5, 10, 20, 40, 80, 160 ⁇ ms.
  • multiple symbol positions for SSB are defined based on the frequency range (FR1, FR2).
  • the PBCH has a payload of 56 bits. N repetitions of PBCH are transmitted within a period of 80 ms. N depends on the SSB transmission period.
  • the system information consists of the MIB carried by the PBCH, RMSI (SIB1), and other system information (OSI).
  • SIB1 includes information for performing RACH settings and RACH procedures.
  • the time/frequency resource relationship between SSB and PDCCH monitoring resources for SIB1 is configured by PBCH.
  • a base station that uses beam correspondence transmits a plurality of SSBs using a plurality of beams in each SSB transmission period.
  • the multiple SSBs each have multiple SSB indices.
  • a UE that detects one SSB transmits PRACH in the RACH occasion associated with that SSB index and receives RAR in the RAR window.
  • beam and coverage In high frequency bands, without applying beamforming to synchronization/reference signals, the coverage will be narrow and it will be difficult for UEs to discover base stations. On the other hand, if beamforming is applied to the synchronization signal/reference signal to ensure coverage, a strong signal can reach in a specific direction, but it becomes more difficult for the signal to reach other directions. If the direction in which the UE is located is unknown at the base station before the UE is connected, it is impossible to transmit synchronization signals/reference signals using beams directed only in appropriate directions. A possible method is for the base station to transmit multiple synchronization/reference signals, each with beams in different directions, and for the UE to know which beam it has found. Using narrow (narrow) beams for coverage requires transmission of many synchronization signals/reference signals, which may increase overhead and reduce spectral efficiency.
  • Coverage extensions including PRACH extensions for frequency range (FR) 2 are being considered. For example, PRACH repetition using the same beam or different beams is being considered. This PRACH extension may be applied to FR1.
  • the PRACH extension may be applied to the short PRACH format or may be applied to other formats.
  • the common RACH configuration (RACH-ConfigCommon) consists of the general RACH configuration (rach-ConfigGeneric), the total number of RA preambles (totalNumberOfRA-Preambles), the SSB for each RACH occasion and the contention-based (CB) Preamble (ssb-perRACH-OccasionAndCB-PreamblesPerSSB).
  • the rach-ConfigGeneric may include a PRACH configuration index (prach-ConfigurationIndex) and message 1 FDM (msg1-FDM, the number of PRACH occasions to be FDMed within one time instance).
  • ssb-perRACH-OccasionAndCB-PreamblesPerSSB may contain the number of CB preambles per SSB for the number of SSBs per RACH occasion 1/8 (oneEighth, one SSB associated with eight RACH occasions).
  • the UE specifies the number N of SS/PBCH blocks associated with one PRACH occasion and for each valid PRACH occasion, SS / the number R of CB preambles per PBCH block may be applied by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.
  • N_preamble ⁇ total is given by totalNumberOfRA-Preambles for Type 1 random access procedures and msgA-TotalNumberOfRA-Preambles for Type 2 random access procedures with PRACH occasion settings independent of Type 1 random access procedures.
  • N_preamble ⁇ total is a multiple of N.
  • the association period for mapping SS/PBCH blocks to PRACH occasions is such that N_Tx ⁇ SSB SS/PBCH block indices are mapped to PRACH occasions at least once within the association period.
  • the minimum value in the set determined by the PRACH setup period according to the relationship (specified relationship) between the PRACH setup period and the association period (number of PRACH setup periods).
  • the UE obtains N_Tx ⁇ SSB from the value of SSB positions in burst (ssb-PositionsInBurst) in SIB1 or in common serving cell configuration (ServingCellConfigCommon).
  • the association pattern period includes one or more association periods and is determined such that the pattern between PRACH occasions and SS/PBCH block indices repeats at most every 160 ms. After an integer number of association periods, if there is a PRACH occasion that is not associated with an SS/PBCH block index, that PRACH occasion is not used for PRACH.
  • the association periods are ⁇ 1, 2, 4, 8, 16 ⁇ , ⁇ 1, 2, 4, 8 ⁇ , ⁇ 1, 2, 4 ⁇ , ⁇ 1, 2 ⁇ , and ⁇ 1 ⁇ .
  • FIG. 2A shows an example (mapping 1) of association between PRACH occasions (RACH occasions (RO)) and beams (SSB/CSI-RS).
  • RACH occasions RACH occasions
  • SSB/CSI-RS beams
  • SSB0 is associated with preamble indices 0 through 15
  • SSB1 is associated with preamble indices 15 through 31
  • SSB2 is associated with preamble indices 32 through 47 with SSB2
  • SSB3 is associated with preamble indices 48 through 63 with SSB3.
  • the base station can distinguish the associated SS/PBCH block index by the received PRACH.
  • Random access preambles can only be sent on the time resources specified in the random access configuration of the specification, whether FR1 or FR2 and the spectrum type (paired spectrum/supplementary uplink (SUL)/unpaired (unpaired) spectrum) and
  • the PRACH configuration index is given by the higher layer parameter prach-ConfigurationIndex or by msgA-PRACH-ConfigurationIndex if configured.
  • preamble format, x and y in n_f (frame number) mod x y, subframe number, starting symbol, number of PRACH slots in subframe, time domain in PRACH slot It is associated with at least one of the PRACH occasion number N_t ⁇ RA,slot and the PRACH duration N_dur ⁇ RA (Fig. 3).
  • the type of RACH procedure may be at least one of the following. contention-free random access (CFRA), PDCCH ordered RA (RA initiated by PDCCH order), CFRA for beam failure recovery (BFR), CFRA for system information (SI) request, synchronization Such as CFRA for reconfiguration with sync. • contention-based random access (CBRA), MAC entity triggered RA, RRC triggered RA with event, CBRA for BFR, etc.; • 4-step RACH. • 2-step RACH.
  • PRACH repetition is not clear. For example, it is not clear how PRACH resources for repetition (eg, repetition pattern, number of repetitions) are configured, UE behavior of preamble repetition transmission, impact on counters/timers for RACH, etc. If such settings/procedures are not clear, there is a risk of deterioration in communication quality/communication throughput.
  • PRACH resources for repetition eg, repetition pattern, number of repetitions
  • UE behavior of preamble repetition transmission impact on counters/timers for RACH, etc. If such settings/procedures are not clear, there is a risk of deterioration in communication quality/communication throughput.
  • RA response window RA response window
  • RA response window RA response window
  • RA response window RA response window
  • RA response window RA response window
  • RA contention resolution timer ra-ContentionResolutionTimer
  • Msg Msg.
  • the B response window is the time window for monitoring RA responses (RAR) for 2-step RA type (SpCell only).
  • the MAC entity When the RA preamble is transmitted, regardless of the possibility of measurement gaps occurring, the MAC entity performs actions 1 to 3 below.
  • [Action 1] If a contention-free RA preamble for a BFR request is sent by the MAC entity, the MAC entity performs actions 1-1 and 1-2 below. [[Action 1-1]] The MAC entity starts the ra-ResponseWindow configured in the BFR configuration (BeamFailureRecoveryConfig) in the first PDCCH occasion from the end of RA preamble transmission. [[Operation 1-2]] The MAC entity is designated by the SpCell's BFR search space ID (recoverySearchSpaceId) identified by the C-radio network temporary identifier (RNTI) while the ra-ResponseWindow is running. Monitor PDCCH transmissions in the search space.
  • RecoverySearchSpaceId the C-radio network temporary identifier
  • [Action 2] Otherwise, the MAC entity performs actions 2-1 and 2-2 below.
  • the MAC entity initiates the ra-ResponseWindow configured in the common RACH configuration (RACH-ConfigCommon) in the first PDCCH occasion from the end of RA preamble transmission.
  • RACH-ConfigCommon the common RACH configuration
  • the MAC entity monitors the SpCell's PDCCH transmissions for the RAR identified by the RA-RNTI.
  • the MAC entity may stop the ra-ResponseWindow after successful reception of RAR containing RA preamble identifiers matching the transmitted PREAMBLE_INDEX (may stop monitoring for RAR).
  • PDCCH monitoring within the RA response window there are two cases: PDCCH for base station response to BFR and PDCCH for RAR. The following may apply to both cases.
  • the MAC entity When the MSGA (Msg.A) preamble is transmitted, the MAC entity performs actions 4 to 6 below regardless of the possibility of occurrence of measurement gaps.
  • the MAC entity shall, in the PDCCH monitoring window specified in the specification, Msg. Start the B response window (msgB-ResponseWindow).
  • msgB-ResponseWindow is the beginning of the earliest CORESET the UE is set to receive PDCCH for Type 1-PDCCH CSS set that is at least one symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission. symbol.
  • the length of msgB-ResponseWindow may correspond to SCS for Type 1 - PDCCH CSS set.
  • the MAC entity monitors the SpCell's PDCCH transmissions for the RAR identified by the MSGB-RNTI while the msgB-ResponseWindow is running.
  • RA-RNTI 1+s_id+14*t_id+14*80*f_id+14*80*8*ul_carrier_id
  • Subcarrier spacing (SCS) for determination of t_id is based on the value of ⁇ .
  • 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 for 4-step RACH.
  • MSGB-RNTI 1+s_id+14*t_id+14*80*f_id+14*80*8*ul_carrier_id+14*80*8*2
  • Subcarrier spacing (SCS) for determination of t_id is based on the value of ⁇ .
  • 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 for 2-step RACH.
  • DCI format 1_0 includes a DCI format identifier field, a bit field always set to 1, and a frequency domain resource assignment field. If the cyclic redundancy check (CRC) of DCI format 1_0 is scrambled by C-RNTI and the frequency domain resource allocation field is all ones, then that DCI format 1_0 is for a random access procedure initiated by PDCCH order and the rest fields are random access preamble, UL/supplementary uplink (SUL) indicator, SS/PBCH index (SSB index), PRACH mask index, reserved bits (12 bits).
  • CRC cyclic redundancy check
  • the PRACH mask index field is the SS/PBCH block i whose PRACH occasion is indicated by the SS/PBCH block index field in PDCCH order if the value of the random access preamble index field is non-zero.
  • FIG. 10 shows PRACH occasions for PRACH transmissions associated with indexes.
  • the PRACH mask index is indicated by ra-ssb-OccasionMaskIndex.
  • the ra-ssb-OccasionMaskIndex indicates the PRACH occasion for PRACH transmissions for which the PRACH occasion is associated with the selected SS/PBCH block index.
  • PRACH occasions are mapped consecutively for each corresponding SS/PBCH block index.
  • the indexing of the PRACH occasions indicated by the mask index value is reset every SS/PBCH block index, every successive PRACH occasion mapping cycle.
  • the UE selects for PRACH transmission the PRACH occasion indicated by the PRACH mask index value for the indicated SS/PBCH block index in the first mapping cycle available.
  • the order of PRACH occasions is: • First, increasing order of frequency resource indices for frequency multiplexed PRACH occasions. • Second, the increasing order of time resource indices for time-multiplexed PRACH occasions within a PRACH slot. • Third, ascending order of PRACH slot indices.
  • the value of ra-OccasionList indicates the list of PRACH occasions for PRACH transmission, where PRACH occasions are csi-RS. is associated with the selected CSI-RS index indicated by .
  • the indexing of PRACH occasions indicated by ra-OccasionList is reset every association pattern period.
  • FIG. 4 is a diagram showing an example of PRACH mask index values.
  • the PRACH mask index value/msgA-SSB-SharedRO-MaskIndex value is associated with the SSB allowed PRACH occasions (PRACH occasion index values).
  • the random access procedure is initiated by the PDCCH order, the MAC entity itself, or RRC for spec-compliant events. Within the MAC entity, there is only one random access procedure in progress at any given time.
  • the SCell random access procedure is initiated only by PDCCH orders with ra-PreambleIndex different from 0b000000.
  • the MAC entity When a random access procedure is initiated on the serving cell, the MAC entity does the following. If the random access procedure is initiated by the PDCCH order and the ra-PreambleIndex explicitly provided by the PDCCH is not 0b000000, or the random access procedure is initiated for reconfiguration with synchronization, 4 If a contention-free random access resource of step RA type is explicitly provided by rach-ConfigDedicated for the BWP selected for the random access procedure. Set RA_TYPE to 4-stepRA.
  • the MAC entity does the following. If ra-PreambleIndex is explicitly provided from PDCCH and ra-PreambleIndex is not 0b000000, set PREAMBLE_INDEX to signaled ra-PreambleIndex and select SSB signaled by PDCCH.
  • an SSB determines the next available PRACH Occasion from the PRACH Occasions that are allowed by the restrictions given by ra-ssb-OccasionMaskIndex and that correspond to the selected SSB (MAC).
  • the entity randomly selects a PRACH occasion among consecutive PRACH occasions with equal probability according to the specification corresponding to the selected SSB, and the MAC entity selects the next available PRACH corresponding to the selected SSB. When determining occasions, the possibility of measurement gaps occurring may be considered).
  • N_(T,2) is the duration of N_2 symbols corresponding to the PUSCH preparation time of UE processing capability 1.
  • PRACH occasions are valid in the paired spectrum (FDD) or SUL band.
  • PRACH occasions may comply with rules 1 and 2 below.
  • a PRACH occurrence in a PRACH slot does not precede an SS/PBCH block in a PRACH slot and is at least N_gap symbols from the last SS/PBCH block received symbol If it starts later, the PRACH occasion is valid.
  • N_gap is specified in the specification.
  • channelAccessMode semistatic is provided, it does not overlap with the set of consecutive symbols before the start of the next channel occupancy time that the UE does not transmit.
  • the candidate SS/PBCH block index of the SS/PBCH block corresponds to the SS/PBCH block index provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon.
  • PRACH occasions in PRACH slots are valid when: - The PRACH occasion is within a UL symbol.
  • the PRACH occasion does not precede an SS/PBCH block in the PRACH slot and starts at least N_gap symbols after the last DL symbol and at least N_gap symbols after the last SS/PBCH block symbol.
  • the candidate SS/PBCH block index of the SS/PBCH block corresponds to the SS/PBCH block index provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon as described in the specification.
  • the UE In response to the PRACH transmission, the UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI in a window controlled by higher layers as described above.
  • the UE At the first symbol of the earliest CORESET the UE is configured to receive PDCCH for the Type 1-PDCCH CSS set, i.e. at least one symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission, the window is Start. That symbol period corresponds to the SCS for the Type 1-PDCCH CSS set.
  • the length of the window is provided by ra-responseWindow as number of slots based on the SCS for Type 1-PDCCH CSS set.
  • the UE has the same CRC scrambled by the corresponding RA-RNTI and the least significant bits (LSBs) of the system frame number (SFN) in which the UE transmitted the PRACH, with the LSBs of the SFN field in the DCI format
  • the UE sets the TCI state (TCI-State) for CORESET to receive the PDCCH with the DCI format 1_0.
  • TCI-State TCI state
  • a UE may assume the same DMRS antenna port QCL properties for the SS/PBCH blocks or CSI-RS resources that the UE uses for PRACH association, whether provided or not.
  • the UE If the UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by the PDCCH order that triggers the CFRA procedure for the SpCell, the UE detects that DCI format It may be assumed that the PDCCH containing 1_0 and its PDCCH order have the same DMRS antenna port QCL properties.
  • the UE If the UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by the PDCCH order that triggers the CFRA procedure for the secondary cell, the UE detects that DCI DMRS antenna port QCL properties of the CORESET associated with the Type 1-PDCCH CSS set for reception of PDCCH containing format 1_0 may be assumed.
  • the UE upon reception of Msg2 (eg, base station response to RAR, BFR), the UE: A different QCL (eg, beam) may be assumed for reception of Msg2.
  • Msg2 eg, base station response to RAR, BFR
  • the UE may be assumed for reception of Msg2.
  • the purpose of PRACH repetitions with different beams is to improve base station decoding performance (assuming beam correspondence at UE, same DL/UL beam at UE). It does not mean that the UE can decode DL receptions with different beams. That is, opinion 1 below is obtained.
  • CBRA is primarily initiated by MAC/RRC.
  • CFRA can be initiated by PDCCH order or MAC/RRC (eg, BFR, listen before transmission (LBT) failure, system information (SI) request, etc.).
  • PDCCH order e.g, BFR, listen before transmission (LBT) failure, system information (SI) request, etc.
  • LBT listen before transmission
  • SI system information
  • CBRA CBRA
  • Embodiments #1/#2 described below are used for PRACH iterations with different beams. There, the reference resource/reference beam is indicated and the QCL assumption of Msg2 is assumed to be the same as the reference beam. Therefore, the best DL beam is identified as the same as the reference beam. In this case, further extensions to achieve UL beam management are possible.
  • the inventors conceived the operation for PRACH repetition with different beams. According to this operation, the PRACH reception performance in the base station can be improved, and the PRACH coverage can be improved.
  • A/B and “at least one of A and B” may be read interchangeably. Also, in the present disclosure, “A/B/C” may mean “at least one of A, B and C.”
  • activate, deactivate, indicate (or indicate), select, configure, update, determine, etc. may be read interchangeably.
  • supporting, controlling, controllable, operating, capable of operating, etc. may be read interchangeably.
  • Radio Resource Control RRC
  • RRC parameters RRC parameters
  • RRC messages higher layer parameters
  • information elements IEs
  • settings etc.
  • MAC Control Element CE
  • update command activation/deactivation command, etc.
  • higher layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.
  • RRC Radio Resource Control
  • MAC Medium Access Control
  • MAC signaling may use, for example, MAC Control Element (MAC CE), MAC Protocol Data Unit (PDU), and the like.
  • Broadcast information includes, for example, Master Information Block (MIB), System Information Block (SIB), Remaining Minimum System Information (RMSI), and other system information ( It may be Other System Information (OSI).
  • MIB Master Information Block
  • SIB System Information Block
  • RMSI Remaining Minimum System Information
  • OSI System Information
  • the physical layer signaling may be, for example, downlink control information (DCI), uplink control information (UCI), or the like.
  • DCI downlink control information
  • UCI uplink control information
  • indices, identifiers (ID), indicators, resource IDs, etc. may be read interchangeably.
  • sequences, lists, sets, groups, groups, clusters, subsets, etc. may be read interchangeably.
  • DMRS port group e.g., spatial relationship group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (for example, reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI State (unified TCI state), common TCI state (common TCI state), Quasi-Co-Location (QCL), QCL assumption, etc. may be read interchangeably.
  • TCI state downlink Transmission Configuration Indication state
  • DL TCI state uplink TCI state
  • UL TCI state uplink TCI state
  • unified TCI State unified TCI state
  • common TCI state common TCI state
  • QCL Quasi-Co-Location
  • the SSB/CSI-RS index/indicator, beam index, and TCI state may be read interchangeably.
  • period, period, frame, subframe, slot, symbol, occasion, and RO may be read interchangeably.
  • the repetition period (period), the repetition setting (configuration) period, the repetition period (periodicity), and the repetition cycle may be read interchangeably.
  • Occasion RACH Occasion (RO), PRACH Occasion, Recurrence Resource, Recurrence Configured Resource, RO/Repeat Configured Resource, Time Instance and Frequency Instance, Time Resource and Frequency Resource, RO/Preamble resources may be read interchangeably.
  • the remaining RO, the RO after the next available RO, and the RO that satisfies the time condition may be read interchangeably.
  • RO indexing and repeated resource patterns may be read interchangeably.
  • PDCCH order, PDCCH order DCI, DCI format 1_0, and message (Msg.) 0 may be read interchangeably.
  • PRACH, preamble, PRACH preamble, sequence, preamble format, Msg. 1, may be read interchangeably.
  • the response to PRACH, RAR, Msg. 2, Msg. B, Msg. 4, the base station response to BFR, and the DCI that schedules the response may be read interchangeably.
  • transmissions other than PRACH in the random access procedure, Msg. 3, PUSCH scheduled by RAR, Msg. HARQ-ACK/PUCCH for 4, Msg. A PUSCH may be read interchangeably.
  • the beam, SSB, and SSB index may be read interchangeably.
  • repetition repetition with the same beam, repetition RO with the same beam, and repetition associated with the same SSB index may be read interchangeably.
  • random access (RA) procedures CFRA/CBRA, 4-step RACH/2-step RACH, certain types of random access procedures, random access procedures using certain PRACH formats, random access procedures initiated by PDCCH order , a random access procedure not initiated by the PDCCH order, and a random access procedure initiated by higher layers may be read interchangeably.
  • reference resources, reference beams, resources corresponding to reference beams, designated resources, designated beams, selected resources, and selected beams may be read interchangeably.
  • the UE may receive configuration regarding multiple repetitions of the PRACH.
  • the UE may control its multiple repeated transmissions with different beams.
  • the UE may transmit multiple repetitions of the PRACH using different beams.
  • a UE may control the reception of responses to its PRACH within one or more windows.
  • the UE may transmit multiple repetitions of the PRACH using different beams.
  • the UE may determine subsequent UL beams based on receiving responses to its PRACH.
  • the UE may transmit multiple repetitions of the PRACH using different beams.
  • the UE may determine a reference beam corresponding to one of its different beams and determine subsequent UL beams based on reception using the reference beam in response to its PRACH.
  • Embodiments #A0 to #A10 below describe the applicability of PRACH repetition with the same beam or different beams for the following cases.
  • the applicability of PRACH repetition with the same beam or different multiple beams may be defined for the following cases. Due to its applicability, new restrictions may be defined in the specification, new UE capabilities may be defined, RRC configuration signaling may be defined. ⁇ FR1/FR2/FR2-1/FR2-2/FRx. • RA procedures (CBRA/CFRA) triggered by different purposes (PDCCH order PRACH, BFR, LBT failure, SI request, UL unsync., UL data transmission in the absence of SR).
  • CBRA/CFRA RA procedures
  • PRACH repetitions with different multiple beams only for specific RA schemes e.g. CFRA, PDCCH ordered RA, RA for BFR, RA for LBT failure, RA for SI request, RA for UL out of sync
  • RA schemes e.g. CFRA, PDCCH ordered RA, RA for BFR, RA for LBT failure, RA for SI request, RA for UL out of sync
  • RA for UL data transmission in the absence of SR e.g. CFRA, PDCCH ordered RA, RA for BFR, RA for LBT failure, RA for SI request, RA for UL out of sync
  • the UE can appropriately determine PRACH repetition with the same beam or different beams.
  • the RO/preamble reference resource for each SSB/CSI-RS may be explicitly configured by RRC or specified in the specification based on certain rules.
  • the RO/preamble index corresponding to each beam may be considered a reference resource for each beam.
  • the rule may, for example, select the resource corresponding to the minimum or maximum index of the beam/RO/preamble/resource as the reference resource.
  • the QCL assumption for Msg2 reception is: Only one beam reference resource may be selected for PRACH transmission so that there is only one. If more than one beam of reference resources is allowed to be selected for one iteration transmission, rules for the determination of QCL assumptions for Msg2 reception may be defined. The rule may, for example, select the resource corresponding to the minimum or maximum index of the beam/RO/preamble as the reference resource.
  • the UE uses the same preamble for multiple repetitions with different beams. If different preambles for multiple repetitions are used by the UE, it is difficult for the base station to know that the multiple preambles for multiple repetitions are from the same UE, and the base station decodes for different multiple preambles. It is conceivable that the combination of These problems may be mitigated if the preambles for multiple repetitions are the same.
  • FIG. 5 shows an example of RA settings for BFR.
  • SSB index For each beam (SSB index), one or more RO/preamble indices are associated. Among the one or more indices, one index of the RO/preamble reference resource is set by the RRC IE.
  • resources #0a, #0b, #0c, and #0d are associated with SSB #0, and reference resource #0a is set.
  • resources #1a, #1b, #1c, and #1d are associated with SSB #1, and reference resource #1a is set.
  • resources #2a, #2b, #2c, and #2d are associated with SSB #2, and reference resource #2b is set.
  • resources #3a, #3b, #3c, and #3d are associated with SSB #3, and reference resource #3c is configured. Examples 1 to 3 below are conceivable for this setting.
  • Example 1 The UE selects SSB #0 and #1 for preamble repetition and transmits PRACH on resources #0a (reference resource) and #1c (non-reference resource). The UE assumes the same QCL as SSB#0 for Msg2 reception.
  • Example 2 The UE selects SSB #0 and #1 for preamble repetition and transmits PRACH on resources #0a (reference resource) and #1a (reference resource). The UE does not select resources #0a and #1a (reference resources for two beams) in one iteration.
  • Example 3 The UE selects SSB #0, #1, #2 and #3 for preamble repetition and transmits PRACH on resources #0b, #1c, #2b (reference resources) and #3d. The UE assumes the same QCL as SSB#2 for Msg2 reception.
  • the UE can properly determine resources/beams for PRACH repetitions with different beams.
  • Embodiment #1 above is applicable to PDCCH ordered PRACH and other CFRA/CBRA triggered by MAC/RRC. However, some other options are possible for the PDCCH ordered PRACH.
  • the following solution may be used for the selected beam and the reference beam for the QCL assumption for Msg2.
  • the PDCCH order DCI format 1_0 shall be a beam index (SSB index) for indication of more than one beam for a PRACH repetition with different beams.
  • 'SS/PBCH index' may indicate one or more additional fields.
  • the number of additional beam index indications may be set by RRC or specified in the specification.
  • the number of additional beam index indications may be one, two, or more than two.
  • the additional one or more fields may reuse at least some of the 12 or 10 reserved bits.
  • the additional one or more fields may follow any of fields 1 and 2 below. [Field 1]
  • the field size may be the existing 6 bits.
  • the field size may be set by RRC or determined according to the SSB setting (eg, SSB-PositionInBurst). If fewer SSBs are transmitted, the field size may be less than 6 bits.
  • a QCL assumption of PDCCH order DCI format 1_0 may be assumed by the UE as a reference beam for QCL assumptions for Msg2 reception.
  • the UE can properly determine the PRACH repetition/Msg2 beam with different beams initiated by the PDCCH order.
  • New repetition resource configurations may be defined for repetition patterns or repetition resource configurations for PRACH repetitions with different beams.
  • a PRACH association period or a PRACH configuration period or a PRACH occasion mapping cycle in an existing SIB/RRC may be considered as a PRACH repetition period.
  • a UE may select multiple beams for RA preamble repetitions from its PRACH repetition period.
  • the number of iterations X may be the number of different beams selected by the UE for iterations with different beams.
  • the number of repetitions may be set by RRC IE/MAC CE, may be explicitly indicated in PDCCH order DCI format 1_0, or (similar to embodiment #B2 described below) PDCCH order DCI format 1_0 may be implied by the number of SSB index fields in the , or may be determined by the UE based on RSRP measurements. Similar to embodiments #A2/#A3 described below, the UE may determine X based on RSRP. There may be association settings between repetition numbers 1, 2, . . . , X and RO/preamble resources.
  • the rule for selecting multiple beams (SSB/CSI-RS) for one PRACH repetition by the UE may be either of selection rules 1 and 2 below.
  • the UE uses existing methods to select the N beams. For example, an existing method may be to select the N beams corresponding to measurements (eg, RSRP) exceeding a threshold. For existing methods/thresholds, either existing thresholds (e.g. rsrp-ThresholdSSB/rsrp-ThresholdCSI-RS), or new parameters for PRACH repetitions, or new for PRACH repetitions with same or different beams. parameters may be used.
  • existing thresholds e.g. rsrp-ThresholdSSB/rsrp-ThresholdCSI-RS
  • new parameters for PRACH repetitions or new for PRACH repetitions with same or different beams. parameters may be used.
  • selection rule 2 The UE uses existing methods to select the reference beam. The UE may then follow either of the following selection rules 2-1 and 2-2. [[Selection rule 2-1]] The UE selects N ⁇ 1 repeated beams based on the new absolute RSRP threshold parameter. [[Selection rule 2-2]] The UE selects the N ⁇ 1 repeated beams based on the new relative RSRP threshold parameters (eg, rsrp-offset-ThresholdSSB/rsrp-offset-ThresholdCSI-RS) based on the offset to the reference beam. For example, a beam may be selected for repetition if the offset is 6 dB or less.
  • the new relative RSRP threshold parameters eg, rsrp-offset-ThresholdSSB/rsrp-offset-ThresholdCSI-RS
  • restriction methods 1 and 2 may be applied to further restrict the beams that are selected.
  • RRC configures multiple groups of beams. In one iteration, the UE may select beams within one group.
  • group #1 includes SSB #0, #1, #2, #3
  • group #2 includes SSB #4, #5, #6, #7
  • group # Group #3 includes SSBs #8, #9, #10, #11
  • Group #4 includes SSBs #12, #13, #14, #15.
  • RRC For each beam (especially for selection rule 2), RRC sets up a list of beams associated with that beam. In one iteration, the UE may select beams within one group. If one beam is selected as a reference beam by the UE, the UE may select other N ⁇ 1 beams from the list of beams configured by RRC and associated with that reference beam.
  • RRC configures a list of SSB/CSI-RSs associated with that SSB. Assuming SSB#0-#15, SSB#0 is associated with SSB#14, #15, #1 and #2, and SSB#1 is associated with SSB#15, #0, #2 and #3. After that, the SSB index in association is sequentially incremented, and SSB #13, #14, #0, and #1 are associated with SSB #15.
  • the UE can be properly configured with PRACH repetitions with different beams.
  • Embodiments #A0 to #A10 below describe starting/restarting the RAR window for PRACH repetitions with the same beam.
  • the RAR window may start at the end of either the first iteration, each iteration, or the last iteration.
  • At least one method of embodiments #A0 through #A10 may be applied to PRACH repetitions with different beams.
  • the RAR window (ra-ResponseWindow) may be started/restarted in the first PDCCH occasion from the end of the RA preamble repetition of the reference resource or reference beam within one repetition.
  • the RAR window (ra-ResponseWindow) may be started/restarted.
  • the network Before the reference resource or reference beam is transmitted, the network does not know the QCL assumptions for RAR. Therefore, the network cannot send Msg2 to the UE and the UE may not need to monitor the RAR.
  • a new RAR window (eg, ra-ResponseWindow-r18) for PRACH repetition may be introduced.
  • Different new parameters may be introduced for PRACH iterations with the same beam or different beams.
  • RO/preamble resource #0b using beam SSB#0, RO/preamble resource #1c using beam SSB#1, and RO/preamble resource #1c using beam SSB#2. and resource #3d of RO/preamble using beam of SSB #3 are used for transmission of PRACH repetitions.
  • Resource #2b may be a reference resource
  • SSB #2 may be a reference beam.
  • FIG. 6A shows example 1 of the RAR window.
  • window operation 1 of embodiment #A8, which will be described later, is applied.
  • the RAR window is started.
  • FIG. 6B shows example 2 of the RAR window.
  • case A of window operation 2 of embodiment #A8, which will be described later, is applied.
  • the RAR window starts after the end of transmission of each resource #0b, #1c, #2b, #3d.
  • FIG. 6C shows example 3 of the RAR window.
  • #4 is applied.
  • the RAR window is started after the end of transmission of each resource #2b, #3d after resource #2b corresponding to the reference beam.
  • the QCL assumptions for RAR reception may be the same as for SSB#2.
  • FIG. 6D shows example 4 of the RAR window.
  • #4 is applied.
  • the RAR window is started.
  • the QCL assumptions for RAR reception may be the same as for SSB#2.
  • the RO for each SSB is within a short duration without large gaps as shown in the examples of FIGS. 6A-6D. Something is possible.
  • FIG. 7A shows an example of SSB and RO association.
  • RO #0a, #0b, #0c, #0d associated with SSB #0 and RO #1a, #1b, #1c, #1d associated with SSB #1 are arranged in a certain time resource. be.
  • RO #2a, #2b, #2c, #2d associated with SSB #2 and RO #3a, #3b, #3c, #3d associated with SSB #3 are arranged in subsequent time resources. be done.
  • RO #0b, #1c, #2b and #3d are used for transmission of PRACH repetitions.
  • FIG. 7B shows example 1 of the RAR window.
  • window operation 1 of embodiment #A8, which will be described later, is applied.
  • the RAR window is started.
  • FIG. 8A shows example 2 of the RAR window.
  • case A of window operation 2 of embodiment #A8, which will be described later, is applied.
  • the RAR window starts after the end of transmission of resources #0b and #1c and resources #2b and #3d.
  • FIG. 8B shows example 3 of the RAR window.
  • #4 is applied.
  • the RAR window is started.
  • the QCL assumptions for RAR reception may be the same as for SSB#2.
  • the UE can properly receive RAR for PRACH repetitions with different beams.
  • This embodiment relates to a combination of PRACH repetitions with the same beam and PRACH repetitions with different beams.
  • a UE may support a combination of two or more iterations with the same beam and one or more iterations with one or more different beams.
  • the UE does not assume that a PRACH repetition with the same beam and a PRACH repetition with different beams are configured at the same time.
  • Separate UE capabilities may be defined/reported for supporting PRACH repetitions with the same beam and supporting PRACH repetitions with different beams.
  • the UE may apply the supported PRACH repetition schemes without conditions/restrictions (at the UE's discretion).
  • the UE may apply the supported PRACH repetition schemes subject to conditions/restrictions.
  • the condition/restriction may be that RSRP/RSRQ is below a threshold, or that the first PRACH transmission failed, ie no Msg2 was received.
  • the base station may indicate/configure through SIB/RRC configuration whether PRACH repetition with the same beam or PRACH repetition with different beams is used. This indication/setting may apply only for some scenarios.
  • the scenario may include at least one of handover and UL synchronization.
  • the UE may apply default behavior.
  • the default action may be any of the following actions. ⁇ Rel. 15/16 PRACH transmissions (no repetition). • PRACH repetition with the same beam. - PRACH repetition with different beams.
  • the UE can appropriately perform at least one of PRACH repetitions with the same beam and PRACH repetitions with different beams.
  • the UE may start the RAR window (ra-ResponseWindow) in the first PDCCH occasion from the end of each repetition transmission of the RA preamble.
  • the UE may expect that at most one Msg2 (eg, base station response to RAR, BFR, etc.) is received in every RAR window.
  • the UE may assume that the beam associated with the received Msg2 (PRACH repeat transmission beam) is the selected UL beam. That selected UL beam may be used as the default UL beam/QCL source for subsequent UL transmissions.
  • the QCL assumption of DL Msg2 may be the same as the selected DL beam identified in the previous existing 4-step RACH or identified in the previous operation.
  • the selected DL beam may be, for example, a PDCCH-ordered DCI beam that triggers a PDCCH-ordered PRACH repetition with different beams.
  • the selection of that UL beam also means that the base station measures the PRACH preamble reception conditions, selects one preamble with good UL quality, and sends Msg2 within the RAR window for the selected good UL beam. good. If the base station sends Msg2 before the last PRACH repetition, its UL beam may not be the best beam, but it is a good enough UL beam.
  • the timing of decoding of Msg2 may be used to identify the UL beam corresponding to that Msg2.
  • the four UL beams used for the four iterations of PRACH correspond to SSB #0, #1, #2, and #3, respectively.
  • SSB#1 is the best DL beam identified.
  • the UE starts the RAR window after each iteration.
  • the four RAR windows are non-overlapping.
  • the QCL assumption for DL reception is the best DL beam, SSB#1.
  • the UE decodes the RAR within the RAR window for SSB#2. This means that the good UL beam/UL QCL hypothesis chosen is SSB#2.
  • Msg2 for each beam may be identified by RA-RNTI.
  • the parameters (s_id/t_id/f_id) used to calculate the RA-RNTI may be different for each iteration. This identification method allows the UE to receive multiple RA-RNTIs (multiple CRCs respectively scrambled by the multiple RA-RNTIs, multiple DCIs respectively with the multiple CRCs) in overlapping time periods. It may mean that you need to try
  • RO #0b associated with SSB #0 and RO #1c associated with SSB #1 are on the same time resource, followed by RO #2b associated with SSB #2.
  • RO#3d associated with SSB#3 are on the same time resource.
  • the UE starts RAR window #0 after RO #0b, RAR window #1 after RO #1c, RAR window #2 after RO #2b, and RO #3d. Later start RAR window #1. RAR windows #0, #1, #2 and #3 overlap. If Msg2 for SSB#0 is sent within RAR window #0, RA-RNTI#0 is used. If Msg2 for SSB#1 is sent within RAR window #1, RA-RNTI#1 is used.
  • Msg2 for SSB#2 is sent within RAR window #2, RA-RNTI#2 is used. If Msg2 for SSB#3 is sent in RAR window #3, RA-RNTI#3 is used.
  • the QCL assumption for DL reception is the best DL beam, SSB#1.
  • the UE uses different RA-RNTIs for decoding Msg2 for each SSB.
  • the UE decodes the RAR using RA-RNTI#3 for SSB#3. This means that the good UL beam/UL QCL hypothesis chosen is SSB#3.
  • the UE may start the RAR window (ra-ResponseWindow) in the first PDCCH occasion from the end of the last repetition transmission of the RA preamble.
  • the UE may expect at most one Msg2 (eg, base station response to RAR, BFR, etc.) to be received within its RAR window.
  • the UE may assume that the beam associated with the received Msg2 (PRACH repeat transmission beam) is the selected (best) UL beam. That selected UL beam may be used as the default UL beam/QCL source for subsequent UL transmissions.
  • the QCL assumption of DL Msg2 may be the same as the selected DL beam identified in the previous existing 4-step RACH or identified in the previous operation.
  • the selected DL beam may be, for example, a PDCCH-ordered DCI beam that triggers a PDCCH-ordered PRACH repetition with different beams.
  • the selection of that UL beam also means that the base station measures the PRACH preamble reception conditions, selects one preamble with good UL quality, and sends Msg2 within the RAR window for the selected good UL beam. good.
  • the UE shall attempt to receive all RA-RNTIs (multiple CRCs respectively scrambled by the multiple RA-RNTIs, multiple DCIs respectively with the multiple CRCs) for the multiple preambles sent within its RAR window. may be required.
  • the beam associated with decoded Msg2 may be identified by the RA-RNTI (corresponding to that decoded Msg2).
  • the parameters (s_id/t_id/f_id) used to calculate the RA-RNTI may be different for each iteration.
  • the four UL beams used for four PRACH repetitions correspond to SSB #0, #1, #2, and #3, respectively.
  • SSB#1 is the best DL beam identified.
  • the UE starts the RAR window after the last iteration. Within that RAR window, the QCL assumption for DL reception is the best DL beam, SSB#1.
  • the UE attempts to receive the RAR scheduling DCI with different RA-RNTIs within its RAR window.
  • the UE decodes the RAR (RAR scheduling DCI) using the RO's RA-RNTI for SSB#2. This means that the best UL beam/UL QCL hypothesis selected is SSB#2.
  • RO #0b associated with SSB #0 and RO #1c associated with SSB #1 are on the same time resource, followed by RO #2b associated with SSB #2.
  • RO#3d associated with SSB#3 are on the same time resource.
  • the UE starts the RAR window after the last RO #2b and #3d in the time domain. Within that RAR window, the QCL assumption for DL reception is the best DL beam, SSB#1.
  • the UE attempts to receive the RAR scheduling DCI with different RA-RNTIs within its RAR window.
  • the UE decodes the RAR (RAR scheduling DCI) using the RA-RNTI for SSB#3. This means that the best UL beam/UL QCL hypothesis selected is SSB#3.
  • the UE can appropriately perform at least one of PRACH repetitions with the same beam and PRACH repetitions with different beams.
  • RAR window (ra-ResponseWindow) may be started.
  • the UE may assume the reference beam as the QCL assumption for Msg2 reception.
  • the UE may assume that at most one Msg2 (eg, base station response to RAR, BFR, etc.) is received in every RAR window.
  • the UE may assume that the beam associated with the received Msg2 (PRACH repeat transmission beam) is the selected UL beam. That selected UL beam may be used as the default UL beam/QCL source for subsequent UL transmissions.
  • the QCL assumption of DL Msg2 may be the reference beam in Embodiments #1/#2.
  • the selection of that UL beam also means that the base station measures the PRACH preamble reception conditions, selects one preamble with good UL quality, and sends Msg2 within the RAR window for the selected good UL beam. good.
  • the timing of decoding of Msg2 may be used to identify the UL beam corresponding to that Msg2.
  • the four UL beams used for the four PRACH repetitions correspond to SSB #0, #1, #2 and #3, respectively.
  • the reference beam is SSB#2.
  • the reference resource is RO/preamble resource #2b.
  • the UE starts the RAR window after each iteration.
  • the four RAR windows are non-overlapping.
  • the QCL assumption for DL reception is the reference beam, SSB#2.
  • the UE decodes the RAR within the RAR window for SSB#1. This means that the good UL beam/UL QCL hypothesis selected is SSB#1.
  • Msg2 for each beam may be identified by RA-RNTI.
  • the parameters (s_id/t_id/f_id) used to calculate the RA-RNTI may be different for each iteration. This identification method allows the UE to receive multiple RA-RNTIs (multiple CRCs respectively scrambled by the multiple RA-RNTIs, multiple DCIs respectively with the multiple CRCs) in overlapping time periods. It may mean that you need to try
  • RO #0b associated with SSB #0 and RO #1c associated with SSB #1 are on the same time resource, followed by RO #2b associated with SSB #2.
  • RO#3d associated with SSB#3 are on the same time resource.
  • the UE starts RAR window #0 after RO #0b, RAR window #1 after RO #1c, RAR window #2 after RO #2b, and RO #3d. Later start RAR window #1. RAR windows #0, #1, #2 and #3 overlap. If Msg2 for SSB#0 is sent within RAR window #0, RA-RNTI#0 is used. If Msg2 for SSB#1 is sent within RAR window #1, RA-RNTI#1 is used.
  • Msg2 for SSB#2 is sent within RAR window #2, RA-RNTI#2 is used. If Msg2 for SSB#3 is sent in RAR window #3, RA-RNTI#3 is used.
  • the QCL assumption for DL reception is the reference beam, SSB#2.
  • the UE uses different RA-RNTIs for decoding Msg2 for each SSB.
  • the UE decodes the RAR using RA-RNTI#3 for SSB#3. This means that the good UL beam/UL QCL hypothesis chosen is SSB#3.
  • PRACH repetition with different beams may be an additional scheme for UL beam management only with similar functionality to SRS for beam management.
  • PRACH repetition with different beams may be a novel scheme that can be used to identify both DL and UL beams within one procedure.
  • a RAR window (ra-ResponseWindow) may be started.
  • the UE may assume the reference beam as the QCL assumption for Msg2 reception.
  • the UE may expect at most one Msg2 (eg, base station response to RAR, BFR, etc.) to be received within its RAR window.
  • the UE may assume that the beam associated with the received Msg2 (PRACH repeat transmission beam) is the best UL beam selected. That selected UL beam may be used as the default UL beam/QCL source for subsequent UL transmissions.
  • the QCL assumption of DL Msg2 may be the reference beam in Embodiments #1/#2.
  • the selection of that UL beam also means that the base station measures the PRACH preamble reception conditions, selects one preamble with good UL quality, and sends Msg2 within the RAR window for the selected good UL beam. good.
  • the UE shall attempt to receive all RA-RNTIs (multiple CRCs respectively scrambled by the multiple RA-RNTIs, multiple DCIs respectively with the multiple CRCs) for the multiple preambles sent within its RAR window. may be required.
  • the beam associated with decoded Msg2 may be identified by the RA-RNTI (corresponding to that decoded Msg2).
  • the parameters (s_id/t_id/f_id) used to calculate the RA-RNTI may be different for each iteration.
  • the four UL beams used for four PRACH repetitions correspond to SSB #0, #1, #2, and #3, respectively.
  • the reference beam is SSB#2.
  • the reference resource is RO/preamble resource #2b.
  • the UE starts the RAR window after the last iteration. Within that RAR window, the QCL assumption for DL reception is the reference beam, SSB#2.
  • the UE attempts to receive the RAR scheduling DCI with different RA-RNTIs within its RAR window.
  • the UE decodes the RAR (RAR scheduling DCI) using the RO's RA-RNTI for SSB#1. This means that the best UL beam/UL QCL hypothesis selected is SSB#1.
  • RO #0b associated with SSB #0 and RO #1c associated with SSB #1 are on the same time resource, followed by RO #2b associated with SSB #2.
  • RO#3d associated with SSB#3 are on the same time resource.
  • the UE starts the RAR window after the last RO #2b and #3d in the time domain. Within that RAR window, the QCL assumption for DL reception is the reference beam, SSB#2.
  • the UE attempts to receive the RAR scheduling DCI with different RA-RNTIs within its RAR window.
  • the UE uses the RA-RNTI for SSB#1 to decode the RAR (RAR scheduling DCI). This means that the best UL beam/UL QCL hypothesis selected is SSB#1.
  • the UE can appropriately determine the UL beam based on the indicated reference resources/reference beams for PRACH repetitions with different beams.
  • the PRACH coverage increases.
  • PRACH format B4 the format with the longest (most symbols) in the short sequence
  • some other PRACH format may be applied, or all PRACH Formats may be applied.
  • the PRACH format may be adjusted (scaled) based on the PRACH SCS.
  • 4-step RACH may be applied to PRACH repetition. 4-step RACH is most likely to be used in scenarios with limited coverage. A two-step RACH may also be applied to the PRACH repetition.
  • PRACH coverage can be improved.
  • PRACH repetition with the same beam may be applied to at least one RA of targets 1a-1 to 1a-6 below.
  • Target 1a-1 CFRA only.
  • Subject 1a-2 CBRA only.
  • Subject 1a-3 Both CFRA and CBRA.
  • RA reported by UE capability of CFRA and CBRA.
  • a UE capability for PRACH repetition with same beam is defined for at least one of CFRA and CBRA whereby the UE supports PRACH repetition with same beam for at least one RA of CFRA and CBRA may be reported.
  • RA set by RRC signaling.
  • RRC signaling may configure enable/disable of PRACH repetition for at least one of CFRA and CBRA.
  • RA for specific RA purposes.
  • PRACH repetition at least one of availability and UE capability may be defined for a specific RA purpose, and the specific RA purpose may be indicated by at least one of availability and UE capability.
  • Availability may be an information element (higher layer parameter) that enables PRACH repetition for RAs for a specific RA purpose.
  • UE capabilities may indicate support for PRACH repetition for RAs for a particular RA purpose.
  • Specific RA purposes may be, for example, PDCCH ordered RA, RA for SI request, RA for BFR, MAC layer triggered RA, RRC layer triggered RA, and so on.
  • the PRACH iteration with the same beam may be applied to at least one RA of objects 1b-1 to 1b-5 below.
  • a UE capability for PRACH repetitions with the same beam is defined for at least one of the 2-step RA and 4-step RA, whereby the UE capability for the same RA for at least one RA of the 2-step RA and 4-step RA is defined. Support for PRACH repetition with beams may be reported.
  • RRC signaling may configure enable/disable of PRACH repetition for at least one of 2-step RA and 4-step RA.
  • PRACH repetition may be applied to some or all PRACH formats.
  • UE capabilities for PRACH repetition may be defined for one, some or all PRACH formats.
  • PRACH repetition with the same beam may be applied to some or all of RRC IDLE UEs, RRC INACTIVE UEs, and RRC CONNECTED UEs.
  • a new PRACH setting may be provided in the SIB for PRACH repetition with the same beam to apply to IDLE/INACTIVE UEs.
  • a new PRACH configuration/indication may be provided by RRC signaling/MAC CE/DCI for PRACH repetition with the same beam to be applied to CONNECTED UEs.
  • At least one of the conditions/subjects under which PRACH repetitions with the same beam are available in this embodiment may be the conditions/subjects under which PRACH repetitions with different beams are available.
  • the conditions/subjects under which PRACH repetition with the same beam or different beams is applied are revealed.
  • This embodiment relates to the setting of the PRACH repetition pattern/resource/repetition number.
  • the PRACH repetition pattern/resource may be repeated for each of at least one of unit resources 1 to 6 below.
  • At least one unit resource of unit resources 1 to 6 may be configured by the SIC/RRC IE or defined in the specification.
  • the association period can be X SSB mapping periods/cycles, and includes ROs mapped to all SSBs and ROs that are not used and can be mapped to beams for repetition. It may be a period including.
  • the time units may be slots/subframes/PRACH occasions (RO) in the time domain.
  • the frequency units may be PRACH occasions in the frequency domain.
  • the second and subsequent repeated resources may occur after all SSBs have been mapped to PRACH occasions at least once.
  • the length of the PRACH setup period is 10 ms.
  • the repeating resource (association period) is two PRACH configuration periods. In each repetition resource, there are ROs for SSBs 0 to 40 in the first PRACH configuration period, and ROs for SSBs 41 to 63 and unused ROs in the second PRACH configuration period. PRACH is repeated in RO for the same SSB in each repeated resource. In this example, unused ROs are not used for iterations.
  • the second repeated resource may occur before all SSBs are mapped to PRACH occasions at least once.
  • the repeated resource is one PRACH configuration period.
  • the iteration number is two.
  • PRACH configuration period there are ROs for SSBs 41 to 63 and unused ROs.
  • PRACH is repeated in RO for the same SSB in each repeated resource.
  • the repetition resource is 2 ms. In this example, the iteration number is two.
  • the repeating resources are two time-domain ROs according to mapping 1 above.
  • the first repeating resource four ROs in the first time-domain RO are mapped with SSBs 0, 0, 1, 1, and four ROs in the second time-domain RO are mapped with SSBs 2, 2, 3, 3. mapped.
  • the same SSB is mapped in the second repeated resource as in the first repeated resource.
  • PRACH is repeated in RO for the same SSB in each repeated resource.
  • the repeated resources are two frequency domain ROs according to mapping 2 above.
  • SSBs 0 to 3 and SSBs 4 to 7 are mapped to the two frequency domain ROs in the first time domain RO in the first repetition resource, respectively.
  • the same SSB is mapped in the second repeated resource as in the first repeated resource.
  • PRACH is repeated in RO for the same SSB in each repeated resource.
  • the repeating resource is 4 ROs according to mapping 2 described above.
  • SSBs 0 through 3, SSBs 4 through 7, SSBs 8 through 11, and SSBs 12 through 15 are mapped to the four ROs in the first repeating resource (first time domain RO), respectively.
  • the same SSBs as in the first repetition resource are also mapped in the second repetition resource (second time domain RO).
  • PRACH is repeated in RO for the same SSB in each repeated resource.
  • the repeated resource is one RO according to Mapping 2 described above.
  • SSBs 0 to 3 are mapped to one RO in the first repetition resource (first frequency domain RO).
  • the same SSB as in the first repetition resource is mapped also in the second repetition resource (second frequency domain RO).
  • PRACH is repeated in RO for the same SSB in each repeated resource.
  • the repeating resource is one SSB (RO mapped to one SSB).
  • One SSB is mapped to two frequency domain ROs.
  • SSB0 is mapped to the first and second ROs (first and second frequency domain ROs) in the first repetition resource.
  • the same SSBs as in the first repetition resource are also mapped in the second repetition resource (3rd and 4th RO, 3rd and 4th frequency domain RO).
  • PRACH is repeated in RO for the same SSB in each repeated resource.
  • the number of repetitions may be explicitly or implicitly set/indicated by the SIB/RRC IE, or may be specified in the specification.
  • the explicit indication may only indicate whether the repetition is disabled (no) or the repetition is enabled. In this case, a default number of iterations may be defined in the specification. The number of iterations may be the default number of iterations if the explicit indication indicates that iterations are in effect.
  • a cell-specific PRACH repetition number may be broadcast by the SIB.
  • a UE-specific PRACH repetition number may be configured by RRC.
  • the UE-specific PRACH repetition number may be applied to PRACH for RRC INACTIVE/CONNECTED UEs.
  • the UE may determine the actual number of PRACH repetitions according to decision rules or UE implementation. For example, if the SSB RSRP/RSRQ/SINR/Quality/Power measurements are below the threshold and the UE is configured with PRACH repetition, the UE may send the PRACH multiple times (PRACH repetition may be sent).
  • the threshold may be defined in the specification or set by the RRC IE. Multiple thresholds/ranges associated with the number of PRACH repetitions may be configured.
  • the UE may determine the number of PRACH repetitions corresponding to the maximum threshold below which the measurement is below the multiple thresholds, or the PRACH corresponding to the range including the measurement among the multiple ranges.
  • the operation of the UE determining the number of repetitions may be applied only to UEs that support PRACH repetition.
  • a repetition period may mean that all indicated SSB index-to-RO mappings have been repeated Y times within that period.
  • the number of repetitions is 3 and the repetition resource is 1 RO according to the mapping 2 described above.
  • SSBs 0 to 3 are mapped to one RO in the first repetition resource (first frequency domain RO).
  • the same SSBs as in the first repetition resource are also mapped in the second and third repetition resources (second and third frequency domain ROs), respectively.
  • PRACH is repeated in RO for the same SSB in each repeated resource.
  • the first PRACH transmission may always be a single PRACH transmission. If Msg. 2 (RAR) reception, the UE may send PRACH with repetition. PRACH with repetition may involve power ramping.
  • RAR Msg. 2
  • Different PRACH resources may be configured with different repetition numbers.
  • the UE can select RO/preamble with repetition configuration for limited coverage cases.
  • UEs with good coverage can select RO/preambles without repetition.
  • the UE may, for example, have 1 iteration for SSBs 0 to 15, 2 iterations for SSB 16 to 31, 3 iterations for SSB 32 to 47, and 4 iterations for SSB 48 to 63. good.
  • the number of repetitions for preambles 0 to 31 may be 1, and the number of repetitions for preambles 32 to 63 may be 4.
  • the repetition resource is one PRACH setting period (10 ms).
  • the number of RO iterations for SSBs 0 through 40 is two, and the number of RO iterations for SSBs 41 through 63 is one.
  • PRACH is repeated in RO for the same SSB in each repeated resource.
  • Within the next PRACH setup period there will be ROs for SSBs 41 to 63 and unused ROs. The PRACH within this PRACH setup period is not repeated.
  • the repetition resource is one PRACH setting period (10 ms).
  • the repetition number for preambles 0-15 is 2 and the repetition number for preambles 16-31 is 1.
  • the number of repetitions is 2.
  • PRACH configuration period there are ROs for SSBs 41 to 63 and unused ROs.
  • PRACH is repeated in RO for the same SSB in each repeated resource. If the base station decodes/receives preamble 1 associated with SSB#x in the first repetition resource, then the base station decodes the same preamble associated with the same SSB in the second repetition resource. / Assume to receive.
  • the base station may perform joint decoding/reception to improve performance of PRACH decoding/reception.
  • preambles 16 to 31 there is no repetition. If the base station decodes/receives preamble 17 associated with SSB#y in the first repetition resource, then the base station assumes that there is no repetition associated with the same SSB in the second repetition resource. Suppose. However, the base station may decode/receive the preamble associated with SSB#y in the second repetition resource. In this case, the base station may recognize the preamble as a preamble from another UE for access. The base station may not jointly decode/receive the two preambles.
  • the repeated resource is 4 ROs according to Mapping 2 described above.
  • the number of RO iterations for SSBs 0 through 40 is two, and the number of RO iterations for SSBs 41 through 63 is one.
  • SSBs 0 through 3, SSBs 4 through 7, SSBs 8 through 11, and SSBs 12 through 15 are mapped to the four ROs in the first repeating resource (first time domain RO), respectively.
  • the same SSBs as in the first repetition resource are also mapped in the second repetition resource (second time domain RO).
  • PRACH is repeated in RO for the same SSB in each repeated resource.
  • SSBs 32 to 35, SSBs 36 to 39, SSBs 40 to 43, and SSBs 44 to 47 are mapped to four ROs in the fifth time domain RO, respectively. There are no PRACH repeats for these ROs.
  • the repeated resource is 4 ROs according to Mapping 2 described above.
  • the repetition number for preamble indexes 0 to 7 for SSB0 is 1, and the repetition number for preamble indexes 8 to 15 for SSB0 is 2.
  • the repetition number for preamble indices 16 to 23 for SSB1 is 1, and the repetition number for preamble indices 24 to 31 for SSB1 is 2.
  • the repetition number for preamble indexes 32 to 39 for SSB2 is 1, and the repetition number for preamble indexes 40 to 47 for SSB2 is 2.
  • the repetition number for preamble indexes 48 to 55 for SSB3 is 1, and the repetition number for preamble indexes 56 to 63 for SSB3 is 2.
  • SSBs 0 to 3, SSBs 4 to 7, SSBs 8 to 11, and SSBs 12 to 15 are mapped to the four ROs in the first time-domain RO, respectively.
  • Any of preamble indices 8 through 15 are used for SSB0
  • any of preamble indices SSB24 through 31 are used for SSB1
  • any of preamble indices SSB24 through 47 are used for SSB2
  • any of preamble indices SSB40 through 47 are used for SSB3.
  • the repetition number is 2 for the first time-domain RO.
  • the same SSBs as in the first repetition resource are also mapped in the second repetition resource (second time domain RO). PRACH is repeated in RO for the same SSB in each repeated resource.
  • the UE may consider the second RO mapped to each SSB as the second repetition RO for that SSB.
  • some SSB/RO may be configured with some iteration number and some SSB/RO may not be configured with iteration.
  • the UE considers 2 of the 4 ROs mapped to each SSB as ROs for the 2nd iteration for that SSB. good too.
  • the UE assigns the 2nd, 3rd, and 4th ROs of the 4 ROs mapped to each SSB to the 2nd RO for that SSB. , 3rd and 4th iteration ROs, respectively.
  • the PRACH repetition pattern/resource/number of repetitions can be determined appropriately.
  • the PRACH occasion and SSB index are usually mapped in the specification. There is no definition of PRACH beams in the specification. However, Rel. 15, the most likely UE implementation is to use the SSB beams associated with the PRACH occasions, as beam correspondence is mandatory. In this case, the base station can use SSB for reception of PRACH associated with the PRACH occasion.
  • the beam may be a CSI-RS beam.
  • This embodiment relates to UE behavior with respect to PRACH repeat transmission.
  • the association between multiple PRACH resources repeated for the same beam may be recognized by the UE.
  • the UE may know which RO is the x-th repeated transmission.
  • the UE may transmit the same PRACH preamble on ROs associated with repetitions of the same PRACH preamble until the last repetition RO within the repetition period (from the xth repetition to the last repetition).
  • the actual number of iterations may be less than the maximum number of iterations (setpoint/reported value) within one iteration period. This behavior is such that if the base station receives a PRACH preamble in the xth repetition RO associated with the SSB, the base station receives the same preamble in the (x+1)th repetition RO, (x+2)th repetition RO, etc. may mean that it expects to receive This operation may not mean that the base station must receive the same preamble in the (x+1)th repetition RO, the (x+2)th repetition RO, and so on.
  • the number of repetitions is 4. There are four repeating ROs within one repeating period. After the 2nd iteration RO, if the UE selects SSB0 for the PRACH, the UE selects that PRACH from the 3rd iteration RO to the last (4th) iteration RO associated with the same PRACH preamble/SSBO. A preamble may be sent.
  • the UE may wait until the next repetition period and start sending the PRACH preamble in the associated RO starting with the first repetition RO.
  • the UE may determine the PRACH resource (RO/preamble) based on the RSRP value. In this case, the UE may assume that different PRACH resources are configured with different repetition numbers.
  • the UE may select one preamble from preambles 16-31.
  • the UE may select preamble 20 as in the example of FIG. 22 (Medium RSRP).
  • the UE may select one preamble from preambles 32-47.
  • Threshold 4 threshold 3 may be satisfied.
  • the UE may consider the repetition number configured for each PRACH resource (may be considered as the repetition number).
  • the UE may consider the actual number of repetitions remaining for each PRACH resource (may be considered as the number of repetitions).
  • ⁇ Transmission operation 3>> When the UE selects a beam (from multiple beams) for PRACH transmission, the UE follows at least one of the following selection methods 1 to 3 (considering at least one parameter of selection methods 1 to 3): You may select that beam.
  • Selection method 1 The UE considers the RSRP value for each beam, similar to existing specifications.
  • the UE In addition to the RSRP value for each beam, the UE also considers the repetition number configured for the PRACH resource associated with each beam. For example, for beams with the same repetition number for PRACH resources, the UE may need to compare the RSRP values for each beam. For example, for beams with similar RSRP values with different repetition numbers for PRACH resources, the UE selects the beam with the appropriate repetition number based on the RSRP range (similar to transmission operation 2 above). You may For example, for beams with similar RSRP values with different repetition numbers for PRACH resources, the UE may select the beam with the highest repetition number. For example, for beams with different RSRP measurements and different repetitions of PRACH resources, the UE may select a beam with preference between RSRP measurements and repetitions.
  • All SSBs may be configured with the same maximum number of iterations (so that all beams have the same coverage performance). However, for PRACH resources (RO/preamble) associated with one SSB, some PRACH resources are configured with a large number of repetitions and some PRACH resources are configured with a smaller number of repetitions or no repetitions. may be set. A UE accessing any SSB may select PRACH resources corresponding to different repetition numbers.
  • PRACH resources RO/preamble
  • the number of repetitions is 4, and there are 4 repetition ROs within one repetition period.
  • SSBs 0, 1, 30, 31 are mapped within each iteration RO.
  • the UE may select the SSB for the PRACH considering SSB0 and SSB30 with the highest RSRP value. Considering that the next RO for SSB30 is the second iteration RO and the next RO for SSB0 is the third iteration RO, the UE selects SSB30 with a larger number than the actual number of iterations. good too.
  • the UE In addition to the RSRP value for each beam, the UE also considers the order of the next available RO iterations associated with that beam (or the remaining actual number of iterations associated with each beam). Similar to Selection Method 2, except that instead of the set number of iterations for each beam, the actual number of iterations associated with each beam is considered. In this case, all SSBs may be associated with the same maximum number of repetitions. At the time the UE selects a beam for access, the actual number of iterations remaining associated with each beam may be different.
  • the UE may set the 2nd iteration RO (3rd iteration RO, 4th iteration RO, etc.) as the next available iteration RO associated with the beam. may give the beam with the first iteration RO (second iteration RO, third iteration RO, etc.) as the next available iteration RO associated with a beam with higher priority than the beam with . This may mean that the UE selects a beam and its RO with a higher actual repetition number from all beams meeting the RSRP threshold.
  • the UE can appropriately determine PRACH resources/beams.
  • At least one of the parameters 1 to 3 below may not be affected (may not be incremented) if the second and subsequent repetitions of the preamble (second, third, . . . ) are transmitted. This may mean that repeated preamble transmissions do not affect the maximum number of transmissions/count/power ramping.
  • Preamble transmission counter PREAMBLE_TRANSMISSION_COUNTER.
  • Preamble power ramping PREAMBLE_POWER_RAMPING_COUNTER.
  • PREAMBLE_RECEIVED_TARGET_POWER Preamble received target power
  • the UE can properly transmit PRACH repetitions.
  • Whether the number of PRACH repetitions affects the number of repetitions for the rest of the RACH procedure may be either of effects 1 and 2 below.
  • the number of PRACH iterations affects the number of iterations for the rest of the RACH procedure. At least one of the following repetition numbers 1 to 4 may be derived from the PRACH repetition number. [Number of repetitions 1] Msg. A repetition number of 2. [Number of repetitions 2] Msg. A repetition number of 3. [Number of repetitions 3] Msg. A repetition number of 4. [Number of repetitions 4] Msg. 4 HARQ-ACK transmission (PUCCH) repetition count.
  • PUCCH HARQ-ACK transmission
  • the mapping between the PRACH repetition and at least one of the repetition numbers 1 to 4 may be set by higher layer signaling or may be defined in the specification.
  • the number of PRACH repetitions does not affect the number of repetitions for the rest of the RACH procedure. At least one of the repetition numbers 1 to 4 may be determined independently of the PRACH repetitions or may be specified.
  • the UE can appropriately determine the number of repetitions in the RACH procedure.
  • Msg. 2 is the following Msg. 2 Actions 1 and 2 may be followed.
  • Msg. 2 Action 1 Msg. 2 supports repetition may be configured by SIB/RRC or may be configured with RACH configuration.
  • Msg. UE capabilities for 2 repetitions may be defined.
  • Msg. 2 Action 2 Msg. Repeats of 2 are not supported.
  • Msg. B has the following Msg. Either of B actions 1 and 2 may be followed. [Msg. B operation 1] Msg. Whether B supports repetition may be configured by SIB/RRC or may be configured with RACH configuration. Msg. UE capabilities for B repetition may be defined. [Msg. B operation 2] Msg. Repeating B is not supported.
  • the UE sends Msg. 2/Msg. B can be properly received.
  • This embodiment is based on Msg. 2 and the DCI for Msg. 2 and at least one of monitoring.
  • the UE Before sending all of the PRACH repetitions, the UE sends DCI with a cyclic redundancy check (CRC) scrambled by RA-RNTI and Msg. 2 and may be determined according to any of the following monitoring operations 1, 2, 2a.
  • CRC cyclic redundancy check
  • the UE Before sending all of the PRACH repetitions, the UE sends DCI with CRC scrambled by RA-RNTI and Msg. 2 and/or not monitored. In this case, power consumption for DCI measurement can be suppressed.
  • the UE Before sending all of the PRACH repetitions, the UE sends DCI with CRC scrambled by RA-RNTI and Msg. 2 and/or at least one of. In this case the initial access will be faster. DCI with CRC scrambled by RA-RNTI and Msg. 2 and , the UE may not transmit the remaining PRACH or be required to transmit the remaining PRACH.
  • the number of PRACH repetitions is 4.
  • the UE sends DCI with CRC scrambled by RA-RNTI and Msg. 2 may be monitored.
  • the UE Before sending all of the PRACH repetitions, the UE sends DCI with CRC scrambled by RA-RNTI and Msg. 2 and at least one of (if possible/desired to monitor) may be monitored. If the base station can detect the first PRACH, Msg. 2, the base station does not allow the UE to send Msg. I don't know if I can monitor 2 or not. Therefore, if the base station sends Msg. 3, the UE sends DCI with CRC scrambled by RA-RNTI and Msg. 2, and at least one of Msg. You can send 2.
  • the UE sends Msg. 2 can be properly received.
  • the UE/MAC entity may follow at least one of the window operations 1 to 3 below for the ra-ResponseWindow.
  • the UE/MAC entity starts the ra-ResponseWindow in the first PDCCH occasion from the end of the last actual repetition transmission of the RA preamble.
  • the last actual repetition transmission may be the last repetition RO for the associated SSB within the repetition period.
  • This action may mean that the UE starts monitoring the RAR (which may include monitoring the base station's response to the BFR) after transmitting all repeated preambles.
  • ⁇ Window operation 2 ⁇ The UE/MAC entity initiates/restarts the ra-ResponseWindow in the first PDCCH occasion from the end of each actual repeated transmission of the RA preamble. This operation may mean that the UE performs RAR monitoring (which may include monitoring the base station's response to BFR) before completing transmission of all repeated preambles. Subsequent repetitions of the preamble may be dropped.
  • RAR monitoring which may include monitoring the base station's response to BFR
  • the ra-ResponseWindow may be considered as three separate windows for RAR monitoring after each PRACH. If the RAR is successfully received within the ra-ResponseWindow, the UE will send a subsequent PRACH/Msg. You may stop/drop repetitions of 1. If the RAR is successfully received within the ra-ResponseWindow, the UE sends a Msg. 3 transmission, the subsequent PRACH/Msg. You may stop/drop repetitions of 1. If the RAR is successfully received within the ra-ResponseWindow, the UE sends a Msg. 4 reception, the subsequent PRACH/Msg. You may stop/drop repetitions of 1.
  • the ra-ResponseWindow is the RAR after the first actual PRACH transmission with restarting the window after each repetition transmission. It may be considered as one window for monitoring. If the RAR is successfully received after the PRACH repetition, the UE may stop/drop subsequent preamble repetitions (may be after Msg.3/Msg.4 or Msg.3/ not after Msg.4). In this case, the UE may also stop the window.
  • Case B may also be possible when the above-described repetition setting of unit resources 2 to 6 is used and the gap distance is very small.
  • the UE selects SSB 30 and starts repeated transmission from the second repeated RO, as in FIG. 23 described above.
  • window operation 1 the UE starts the ra-ResponseWindow after every iteration (4th iteration RO).
  • window behavior 2 the UE initiates an ra-ResponseWindow after each iteration (2nd, 3rd, 4th iteration RO respectively).
  • Each ra-ResponseWindow length is less than the time interval between two iterations.
  • the UE initiates an ra-ResponseWindow after each iteration (2nd, 3rd, 4th iteration RO respectively).
  • Each ra-ResponseWindow length is longer than the time interval between two iterations.
  • the UE/MAC entity starts the ra-ResponseWindow in the first PDCCH occasion from the end of the first actual repetition transmission of the RA preamble.
  • the window may expire before the UE receives the RAR and before the PRACH repeat transmission is complete. If the base station sends the RAR after the second repeated PRACH, the UE may not be able to monitor the RAR.
  • the UE may follow any of the following window actions 3a, 3b, 3c.
  • Window operation 3a The UE may not assume that the ra-ResponseWindow expires before the end of the last preamble repetition or before the last time X (a specified time) after the last preamble repetition.
  • Window operation 3b The window expires and the expiration timing of the window is before the last repeated RO of the SSB associated with the same preamble, or the time X of the last repeated RO of the SSB associated with the same preamble. before the end of the last preamble repetition, or if the UE does not successfully receive the RAR (the ra-ResponseWindow length is not sufficient by the last repetition, i.e. before the end of the last preamble repetition, or Given that the ra-ResponseWindow expires before the last time X (a specified time) after the last preamble repetition, the UE may restart that window.
  • Window operation 3c Based on window operation 3b, the expiration timing of the window is before the last repeated RO of the SSB associated with the same preamble, or at the time of the last repeated RO of the SSB associated with the same preamble. Before X after, the UE may restart the window after the last iteration in addition to restarting the window after expiration.
  • the UE may stop/drop subsequent preamble repetitions (after Msg.3/Msg.4). (or not after Msg.3/Msg.4). In this case, the UE may also stop the window.
  • the UE selects SSB 30 and starts repeated transmission from the second repeated RO.
  • the ra-ResponseWindow starts after the first iteration (1st iteration RO) and expires after time X from the end of the last iteration (4th iteration RO).
  • the ra-ResponseWindow is started after the first iteration (1st iteration RO), expires and restarts before the end of the last iteration (4th iteration RO), Expires after the last iteration (4th iteration RO).
  • the ra-ResponseWindow is started after each iteration and restarted if it expires before the next iteration. In the last iteration (fourth iteration RO), the ra-ResponseWindow expires after time X from the end of the iteration. In the example of window operation 3c, the ra-ResponseWindow is started after the first iteration (1st iteration RO), expires and restarts before the last iteration (4th iteration RO). Additionally, the ra-ResponseWindow is restarted after the end of the last iteration (4th iteration RO).
  • UE capabilities for window operation 1/2/3/3a/3b/3c may be defined.
  • a UE capability may be defined as to whether or not to support restarting a window if it expires or repeats.
  • Window operations 1/2/3/3a/3b/3c may be applied to msgB-ResponseWindow for 2-step RACH.
  • at least one symbol of the value of the last symbol of the PRACH occasion corresponding to the PRACH transmission may additionally be considered.
  • the UE sends Msg. 2/Msg. B can be properly received.
  • RA-RNTI calculation may follow at least one of calculation methods 1 to 4 below.
  • the RA-RNTI calculation uses the parameters of the first actual PRACH transmission among all iterative ROs.
  • the parameters may include s_id/t_id/f_id. This calculation method can be applied to all window operations of embodiment #A8 above.
  • the number of repetitions is 4, DCI with CRC scrambled by RA-RNTI, and Msg. 2 and , are associated with the first iteration RO.
  • RA-RNTI is calculated using the parameters of the first actual PRACH transmission.
  • the RA-RNTI calculation uses the parameters of the last repeated PRACH transmission.
  • the parameters may include s_id/t_id/f_id. This calculation method can be applied to window operation 1 of embodiment #A8 above.
  • the RA-RNTI calculation uses the parameters of the PRACH transmission of each iteration before the end of the next iteration RO (most recent iteration).
  • the parameters may include s_id/t_id/f_id. This calculation method can be applied to window operation 2/3 of embodiment #A8 above.
  • the number of repetitions is 4, DCI with CRC scrambled by RA-RNTI, and Msg. 2 and , are associated with each iteration RO.
  • the RA-RNTI for DCI after the last iteration is calculated using the parameters of the last PRACH transmission.
  • the RA-RNTI calculation considers different parameters after restarting the ra-ResponseWindow.
  • the parameters may include s_id/t_id/f_id.
  • the RA-RNTI computation may use the parameters of the most recent iteration for the RA-RNTI within the subsequent window time.
  • the RA-RNTI calculation may use the most recent iteration parameters for the RA-RNTI within the subsequent window time, or in this condition You don't have to update the parameters.
  • a UE capability may be defined as to whether to modify the RA-RNTI for the window for repetition of PRACH preamble transmissions.
  • Calculation methods 1 to 4 may be applied to MSGB-RNTI for 2-step RACH.
  • the UE sends Msg. 2/Msg. B can be properly received.
  • ⁇ Report method 1 Different preambles/occasions of PRACH may be defined for UEs that support PRACH repetition and UEs that do not support PRACH repetition. UEs that do not support PRACH repetition must use Rel. May include 15/16 UEs.
  • Different PRACH preambles/occasions may be defined for UEs that support different numbers (maximum number) of PRACH repetitions.
  • the base station can recognize whether the UE supports PRACH repetition.
  • the UE further sends a Msg. 3 or later in the RRC IE/MAC CE may send additional information of the UE capability to support PRACH repetition.
  • the additional information may be the maximum number of PRACH repetitions that the UE supports, and indicates whether to support at least one of PRACH repetitions in 2-step RACH and PRACH repetitions in 4-step RACH. good too.
  • the same PRACH preamble/occasion may be defined for UEs that support PRACH repetition and UEs that do not support PRACH repetition.
  • UEs that do not support PRACH repetition must use Rel. May include 15/16 UEs.
  • the base station cannot recognize whether or not the UE supports PRACH repetition from the PRACH measurement.
  • the UE sends Msg. 3 or later in the RRC IE/MAC CE may send additional information of the UE capability to support PRACH repetition.
  • the additional information may indicate whether the UE supports PRACH repetitions, the maximum number of PRACH repetitions the UE supports, PRACH repetitions in 2-step RACH and 4-step RACH. may indicate whether to support at least one of PRACH repetition in .
  • the UE can properly transmit PRACH repetitions.
  • This embodiment relates to a random access procedure initiated by PDCCH order.
  • At least one indication of whether the PRACH is a repeated transmission (using the same beam) and the number of repetitions of the PRACH (using the same beam) is indicated by the following indication method: Either 1 or 2 may be followed.
  • Explicit new indications for indicating at least one of the presence or absence of repetition (repeating or non-repeating) and the number of repetitions may use reserved bits in the DCI (DCI format 1_0, PDCCH order).
  • the RRC configuration of repetition pattern/repetition resource/number of repetitions may be according to at least one of the above embodiments #A0 to #A10.
  • the DCI for PDCCH order may contain new fields for new indications. New fields may utilize one or more of the existing reserved bits.
  • FIG. 28A shows example 1 of new instructions.
  • a new indication value (code point) of 0 corresponds to non-repeating and a value of 1 corresponds to repeating. This association may be reversed. If a value of 1 indicates that iterations are enabled, the number of iterations may be according to the maximum number of iterations for each RO set by RRC, or it may be according to the actual number of iterations remaining in the iteration period.
  • FIG. 28B shows example 2 of new instructions. It is assumed that the maximum number of repetitions corresponding to each RO that is RRC-configured is four. New indication values (code points) 0, 1, 2, 3 correspond to repetition numbers 1 (non-repeating), 2, 3, 4, respectively. The maximum number of repetitions, the number of values, and the number of repetitions corresponding to each RO are not limited to this example. The maximum number of iterations may be greater than four, the number of values may be greater than four, and the number of iterations may be greater than four.
  • ⁇ Instruction Method 2 ⁇ There may be no explicit new indications to indicate at least one of the presence or absence of repetition (repeating or non-repeating) and the number of repetitions. At least one of the presence or absence of repetition (repeating or non-repeating) and the number of repetitions may be implicitly indicated by at least one of the PRACH mask index and the RO of SSB in the PDCCH order.
  • the repetition pattern/repetition resource/number of repetitions for each RO may be RRC configured.
  • the instructions/settings may comply with at least one of relations 1 to 4 below.
  • the RRC-configured repetition number may be the same.
  • RRC may configure different repetition numbers.
  • PRACH occasion (RO) index 1/2/.../7/8 different iteration numbers can be set similarly to the iteration number settings in at least one of the preceding embodiments #A0 to #A10. may be set.
  • PRACH occasions (RO) with even indices and PRACH occasions (RO) with odd indices are the number of iterations in at least one of the preceding embodiments #A0 to #A10. may be set in the same manner as the setting of
  • the number of repetitions does not have to be the maximum set value (set maximum value).
  • the repetition number may be assumed by the UE as a number obtained by referencing the rules. For example, the number of iterations may be assumed to be the number of remaining iterations associated only with the indicated/configured RO/SSBs within the iteration period, or only with the valid RO/SSBs within the iteration period.
  • association/correspondence For UEs that support PDCCH ordered PRACH repetition, a new table (association/correspondence) for PRACH mask index values may be defined. Each index may indicate the RO and iteration number.
  • Either of the following counting methods A and B may be applied to the number of repetitions indicated in the indicating method 1 or 2.
  • the RO repetition resource set for the indicated SSB may be counted regardless of whether the (RO) is valid or invalid.
  • Countering method B Valid RO repetition resources set for the indicated SSB (valid RO repetition resources among the RO repetition resources set for the indicated SSB) may be counted for the number of repetitions. .
  • Counting methods A/B may be applied not only to PDCCH-ordered PRACH, but also to MAC entity/higher layer/RRC-initiated PRACH transmissions with an indicated number of repetitions.
  • Counting method A may be applied only to non-first iterations with iteration number > 1. This may mean that the first actual PRACH transmission is always on a valid RO.
  • the determination as to whether or not the PRACH occasion is valid may be made according to the validity condition of the above-mentioned "PRACH occasion valid/invalid condition".
  • four repetitions of RO#2 for SSB#0 are set.
  • FIG. 29B is an example in which count method A is applied to the setting of FIG. 29A.
  • the UE receives PDCCH ordered DCI between the first repetition configuration resource and the second repetition configuration resource.
  • the time between the reception of the PDCCH order DCI and the resource for the first actual transmission satisfies the time condition of "time between PDCCH order reception and PRACH transmission" above.
  • Its DCI indicates SSB#0 and RO#2.
  • the indicated number of iterations is two.
  • the third repeat setting resource is invalid. In this example, invalid ROs are also counted in the number of iterations.
  • the only repetitively configured resource actually transmitted by the UE is the second repetitively configured resource.
  • FIG. 30A shows an example in which count method B is applied to the setting of FIG. 29A.
  • the UE receives PDCCH ordered DCI between the first repetition configuration resource and the second repetition configuration resource.
  • the time between the reception of the PDCCH order DCI and the resource for the first actual transmission satisfies the time condition of "time between PDCCH order reception and PRACH transmission" above.
  • Its DCI indicates SSB#0 and RO#2.
  • the indicated number of iterations is two.
  • the third repeat setting resource is invalid. In this example, invalid ROs are not counted in the number of iterations.
  • the repetitively configured resources actually transmitted by the UE are the second and fourth repetitively configured resources.
  • the repetition of the same PRACH preamble may occur over multiple repetition periods in order to meet the indicated number of repetitions. Whether or not such a case is allowed will be described later in Embodiment #B2.
  • FIG. 30B shows an example in which count method B is applied to the setting of FIG. 29A.
  • the UE receives PDCCH ordered DCI between the first repetition configured resource and the second repetition configured resource in the first repetition period.
  • the time between the reception of the PDCCH order DCI and the resource for the first actual transmission satisfies the time condition of "time between PDCCH order reception and PRACH transmission" above.
  • Its DCI indicates SSB#0 and RO#2.
  • the indicated number of iterations is four.
  • the third repeat setting resource is invalid. In this example, invalid ROs are not counted in the number of iterations.
  • the repetition configuration resources actually transmitted by the UE are the second and fourth repetition configuration resources in the first repetition period and the first and second repetition configuration resources in the second repetition period. .
  • the UE can properly transmit the PRACH repetition based on the PDCCH order.
  • At least one of the following periods 1 and 2 may be envisaged.
  • At least one of the following restrictions 1 to 4 may be applied to the combination case of any of the periods 1 and 2 described above and any of the counting methods A and B described above.
  • [Restriction 1] There is no limit on the number of iterations indicated.
  • [Restriction 2] The UE does not assume that the indicated number of repetitions is greater than the RRC configured value.
  • the RRC-configured value may be the RRC-configured maximum number of repetitions per repetition period.
  • the UE shall not assume that the indicated number of repetitions is greater than the number of remaining configured ROs in the repetition period.
  • Restriction 4 The UE shall not assume that the indicated number of repetitions is greater than the number of remaining valid ROs in the repetition period.
  • At least one of restrictions 1 and 2 may be applied to the case of period 1 and counting method A.
  • At least one of restrictions 1 to 4 may be applied to the case of period 2 and counting method A.
  • At least one of restrictions 1 and 2 may be applied to the case of period 1 and counting method B.
  • At least one of restrictions 1 to 4 may be applied to the case of period 2 and counting method B.
  • FIG. 31A shows an example of restriction 3 for the case of period 2 and counting method A.
  • the UE receives PDCCH ordered DCI between the first repetition configuration resource and the second repetition configuration resource.
  • the time between the reception of the PDCCH order DCI and the resource for the first actual transmission satisfies the time condition of "time between PDCCH order reception and PRACH transmission" above.
  • Its DCI indicates SSB#0 and RO#2.
  • the indicated number of iterations is three.
  • the third repeat setting resource is invalid.
  • FIG. 31B shows an example of restriction 4 for the case of period 2 and counting method B.
  • the UE receives PDCCH ordered DCI between the first repetition configuration resource and the second repetition configuration resource.
  • the time between the reception of the PDCCH order DCI and the resource for the first actual transmission satisfies the time condition of "time between PDCCH order reception and PRACH transmission" above.
  • Its DCI indicates SSB#0 and RO#2.
  • the indicated number of iterations is two.
  • the third repeat setting resource is invalid.
  • the UE may follow any of the following default repetition number assumptions 1 to 3 (default repetition number assumptions).
  • default repetition number assumptions 1 to 3 default repetition number assumptions.
  • the UE assumes the indicated number of repetitions to be the number of all actual remaining configured ROs within the repetition period.
  • the UE assumes the indicated number of repetitions to be the number of all actual remaining valid ROs within the repetition period.
  • any of the default repetition number assumptions 1 to 3 may apply.
  • Different assumptions among the default iteration number assumptions 1-3 may be applied for different combinations of cases of either periods 1 and 2 and either counting methods A and B.
  • the calculation of the actual number of remaining configured/valid ROs takes into account the ROs that meet the aforementioned "time between PDCCH order reception and PRACH transmission" time conditions in the repetition period.
  • Embodiment #B3 may be used to determine the actual transmission RO from the RO selected by the UE in embodiment #B2.
  • the number of PRACH repetitions based on the PDCCH order can be appropriately determined/set/indicated.
  • the UE shall send one or more next available indications from all repetition RO resources corresponding to the indicated SSB and the indicated number of repetitions.
  • An RO for the actual transmission may be selected from the proposed ROs.
  • the UE may follow at least one of selection methods 1 and 2 below.
  • the RO indexing (repeating resource pattern) may be per SSB/repetition/mapping cycle. At least one of the foregoing embodiments #A0 to #A10 may be applied to the RO indexing. If the next available RO#x is the 1st repetition configuration resource, the UE continues the ith, (i+1)th, ( The i+2)-th, .
  • PDCCH order DCI is received between the first time instance and the second time instance. Its DCI indicates SSB#0 and RO#5. The UE selects the next available RO for the indicated SSB.
  • Embodiment #B2 above may be used together with embodiment #B3 to select the RO for the actual transmission based on different interpretations of the indicated number of iterations.
  • FIG. 32B shows an example of a repeated resource pattern for each SSB.
  • Each repetition configuration resource corresponds to 8 ROs mapped to one SSB.
  • PDCCH order DCI is received between the third time instance and the fourth time instance. Its DCI indicates SSB#0 and RO#5. The UE selects for transmission from the next available RO up to the indicated number of repetitions (SSB#0 and RO#5) for the indicated SSB.
  • FIG. 33A shows an example of a repeated resource pattern for each SSB and each RO.
  • Each repetition configuration resource corresponds to one SSB and one RO.
  • PDCCH order DCI is received between the third time instance and the fourth time instance. Its DCI indicates SSB#0 and RO#5. The UE selects for transmission from the next available RO up to the indicated number of repetitions (SSB#0 and RO#5) for the indicated SSB.
  • the UE selects (as the actual transmit RO) for transmission from the next available indicated RO#(x+i*M) within the repetition period until the indicated number of repetitions is reached. may
  • the order of PRACH occasions may be: • First, increasing order of frequency resource indices for frequency multiplexed PRACH occasions. • Second, the increasing order of time resource indices for time-multiplexed PRACH occasions within a PRACH slot. • Third, ascending order of PRACH slot indices. • Fourth, the ascending order of the number of repetitions (repetition number).
  • the order of PRACH occasions corresponding to the same repetition number may be the ascending order of PRACH slot indices.
  • the order of PRACH occasions corresponding to the same PRACH slot may be in increasing order of time resource index.
  • the order of (frequency multiplexed) PRACH occasions corresponding to the same time resource index may be in increasing frequency resource index order.
  • FIG. 33B shows an example of a repeated resource pattern for each SSB.
  • Each repetition configuration resource corresponds to 8 ROs mapped to one SSB.
  • the UE may select from those ROs for the actual transmission based on the indicated number of repetitions. From the next available RO for the indicated SSB, the UE selects RO#(x+i*M) up to the indicated number of iterations for transmission.
  • the indexing of ROs in selection methods 1 and 2 may be applied not only to PDCCH-ordered PRACH, but also to other PRACH resource configurations.
  • the UE can properly determine the RO for the actual transmission of PRACH repetitions based on PDCCH order.
  • RRC IE Radio Resource Control IE
  • a higher layer parameter may indicate whether to enable the feature.
  • UE capabilities may indicate whether the UE supports the feature.
  • a UE for which a higher layer parameter corresponding to that function is set may perform that function. It may be defined that "UEs for which upper layer parameters corresponding to the function are not set shall not perform the function (for example, according to Rel. 15/16)".
  • a UE that has reported/transmitted a UE capability indicating that it supports that function may perform that function. It may be specified that "a UE that does not report UE capabilities indicating that it supports the feature shall not perform that feature (eg according to Rel. 15/16)".
  • a UE may perform a function if it reports/transmits a UE capability indicating that it supports the function and the higher layer parameters corresponding to the function are configured. "If the UE does not report/transmit a UE capability indicating that it supports the function, or if the higher layer parameters corresponding to the function are not configured, the UE does not perform the function (e.g., Rel. 15/ 16) may be defined.
  • Which embodiment/option/choice/function among the above multiple embodiments is used may be set by higher layer parameters, may be reported by the UE as UE capabilities, or may be specified in the specification. It may be specified or determined by reported UE capabilities and higher layer parameter settings.
  • UE capabilities may indicate whether the UE supports at least one of the following functions.
  • - Repetition of the same PRACH preamble occurs over multiple repetition periods.
  • Repetition of the same PRACH preamble is restricted to within one repetition period.
  • the specified number of repetitions is limited. For example, the designated number of repetitions should not exceed the RRC set value (maximum value).
  • the indicated number of iterations does not exceed the number of remaining configured ROs in one iteration period.
  • the indicated number of iterations does not exceed the number of valid ROs in one iteration period.
  • PRACH repetition in RAs for special purposes.
  • UE capabilities may indicate at least one of the following values: • Maximum number of repetitions for PDCCH ordered PRACH. • The number of PRACH iterations (maximum number). ⁇ Setting of repetition period. • Maximum number of repetitions (different beams) in PRACH repetitions with different beams.
  • the UE can implement the above functions while maintaining compatibility with existing specifications.
  • wireless communication system A configuration of a wireless communication system according to an embodiment of the present disclosure will be described below.
  • communication is performed using any one of the radio communication methods according to the above embodiments of the present disclosure or a combination thereof.
  • FIG. 34 is a diagram showing an example of a schematic configuration of a wireless communication system according to one embodiment.
  • the wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc. specified by the Third Generation Partnership Project (3GPP). .
  • LTE Long Term Evolution
  • 5G NR 5th generation mobile communication system New Radio
  • 3GPP Third Generation Partnership Project
  • the wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)).
  • RATs Radio Access Technologies
  • MR-DC is 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.
  • RATs Radio Access Technologies
  • MR-DC is 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.
  • LTE Evolved Universal Terrestrial Radio Access
  • EN-DC E-UTRA-NR Dual Connectivity
  • NE-DC NR-E -UTRA Dual Connectivity
  • the LTE (E-UTRA) base station (eNB) is the master node (MN), and the NR base station (gNB) is the secondary node (SN).
  • the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.
  • the wireless communication system 1 has dual connectivity between multiple base stations within the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC) in which both MN and SN are NR base stations (gNB) )) may be supported.
  • dual connectivity NR-NR Dual Connectivity (NN-DC) in which both MN and SN are NR base stations (gNB)
  • gNB NR base stations
  • a wireless communication system 1 includes a base station 11 forming a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) arranged in the macrocell C1 and forming a small cell C2 narrower than the macrocell C1. You may prepare.
  • a user terminal 20 may be located within at least one cell. The arrangement, number, etc. of each cell and user terminals 20 are not limited to the embodiment shown in the figure.
  • the base stations 11 and 12 are collectively referred to as the base station 10 when not distinguished.
  • the user terminal 20 may connect to at least one of the multiple base stations 10 .
  • the user terminal 20 may utilize at least one of carrier aggregation (CA) using a plurality of component carriers (CC) and dual connectivity (DC).
  • CA carrier aggregation
  • CC component carriers
  • DC dual connectivity
  • Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)).
  • Macrocell C1 may be included in FR1, and small cell C2 may be included in FR2.
  • FR1 may be a frequency band below 6 GHz (sub-6 GHz)
  • FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a higher frequency band than FR2.
  • the user terminal 20 may communicate using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.
  • TDD Time Division Duplex
  • FDD Frequency Division Duplex
  • a plurality of base stations 10 may be connected by wire (for example, an optical fiber conforming to Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (for example, NR communication).
  • wire for example, an optical fiber conforming to Common Public Radio Interface (CPRI), X2 interface, etc.
  • NR communication for example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station is an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) is an IAB Also called a node.
  • IAB Integrated Access Backhaul
  • relay station relay station
  • the base station 10 may be connected to the core network 30 directly or via another base station 10 .
  • the core network 30 may include, for example, at least one of Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), and the like.
  • EPC Evolved Packet Core
  • 5GCN 5G Core Network
  • NGC Next Generation Core
  • the user terminal 20 may be a terminal compatible with at least one of communication schemes such as LTE, LTE-A, and 5G.
  • a radio access scheme based on orthogonal frequency division multiplexing may be used.
  • OFDM orthogonal frequency division multiplexing
  • CP-OFDM Cyclic Prefix OFDM
  • DFT-s-OFDM Discrete Fourier Transform Spread OFDM
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • a radio access method may be called a waveform.
  • other radio access schemes for example, other single-carrier transmission schemes and other multi-carrier transmission schemes
  • the UL and DL radio access schemes may be used as the UL and DL radio access schemes.
  • a downlink shared channel Physical Downlink Shared Channel (PDSCH)
  • PDSCH Physical Downlink Shared Channel
  • PBCH Physical Broadcast Channel
  • PDCCH Physical Downlink Control Channel
  • an uplink shared channel (PUSCH) shared by each user terminal 20 an uplink control channel (PUCCH), a random access channel (Physical Random Access Channel (PRACH)) or the like may be used.
  • PUSCH uplink shared channel
  • PUCCH uplink control channel
  • PRACH Physical Random Access Channel
  • User data, upper layer control information, System Information Block (SIB), etc. are transmitted by the PDSCH.
  • User data, higher layer control information, and the like may be transmitted by PUSCH.
  • a Master Information Block (MIB) may be transmitted by the PBCH.
  • Lower layer control information may be transmitted by the PDCCH.
  • the lower layer control information may include, for example, downlink control information (DCI) including scheduling information for at least one of PDSCH and PUSCH.
  • DCI downlink control information
  • the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc.
  • the DCI that schedules PUSCH may be called UL grant, UL DCI, etc.
  • PDSCH may be replaced with DL data
  • PUSCH may be replaced with UL data.
  • a control resource set (CControl Resource SET (CORESET)) and a search space (search space) may be used for PDCCH detection.
  • CORESET corresponds to a resource searching for DCI.
  • the search space corresponds to the search area and search method of PDCCH candidates.
  • a CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with certain search spaces based on the search space settings.
  • One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels.
  • One or more search spaces may be referred to as a search space set. Note that “search space”, “search space set”, “search space setting”, “search space set setting”, “CORESET”, “CORESET setting”, etc. in the present disclosure may be read interchangeably.
  • PUCCH channel state information
  • acknowledgment information for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK/NACK, etc.
  • SR scheduling request
  • a random access preamble for connection establishment with a cell may be transmitted by the PRACH.
  • downlink, uplink, etc. may be expressed without adding "link”.
  • various channels may be expressed without adding "Physical" to the head.
  • synchronization signals SS
  • downlink reference signals DL-RS
  • the DL-RS includes a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DeModulation Reference Signal (DMRS)), Positioning Reference Signal (PRS)), Phase Tracking Reference Signal (PTRS)), etc.
  • CRS cell-specific reference signal
  • CSI-RS channel state information reference signal
  • DMRS Demodulation reference signal
  • PRS Positioning Reference Signal
  • PTRS Phase Tracking Reference Signal
  • the synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • a signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called SS/PBCH block, SS Block (SSB), and so on.
  • SS, SSB, etc. may also be referred to as reference signals.
  • DMRS may also be called a user terminal-specific reference signal (UE-specific reference signal).
  • FIG. 35 is a diagram illustrating an example of a configuration of a base station according to an embodiment.
  • the base station 10 comprises a control section 110 , a transmission/reception section 120 , a transmission/reception antenna 130 and a transmission line interface 140 .
  • One or more of each of the control unit 110, the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission path interface 140 may be provided.
  • this example mainly shows the functional blocks of the features of the present embodiment, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.
  • the control unit 110 controls the base station 10 as a whole.
  • the control unit 110 can be configured from a controller, a control circuit, and the like, which are explained based on common recognition in the technical field according to the present disclosure.
  • the control unit 110 may control signal generation, scheduling (for example, resource allocation, mapping), and the like.
  • the control unit 110 may control transmission/reception, measurement, etc. using the transmission/reception unit 120 , the transmission/reception antenna 130 and the transmission line interface 140 .
  • the control unit 110 may generate data to be transmitted as a signal, control information, a sequence, etc., and transfer them to the transmission/reception unit 120 .
  • the control unit 110 may perform call processing (setup, release, etc.) of communication channels, state management of the base station 10, management of radio resources, and the like.
  • the transmitting/receiving section 120 may include a baseband section 121 , a radio frequency (RF) section 122 and a measuring section 123 .
  • the baseband section 121 may include a transmission processing section 1211 and a reception processing section 1212 .
  • the transmitting/receiving unit 120 is configured from a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitting/receiving circuit, etc., which are explained based on common recognition in the technical field according to the present disclosure. be able to.
  • the transmission/reception unit 120 may be configured as an integrated transmission/reception unit, or may be configured from a transmission unit and a reception unit.
  • the transmission section may be composed of the transmission processing section 1211 and the RF section 122 .
  • the receiving section may be composed of a reception processing section 1212 , an RF section 122 and a measurement section 123 .
  • the transmitting/receiving antenna 130 can be configured from an antenna described based on common recognition in the technical field related to the present disclosure, such as an array antenna.
  • the transmitting/receiving unit 120 may transmit the above-described downlink channel, synchronization signal, downlink reference signal, and the like.
  • the transmitting/receiving unit 120 may receive the above-described uplink channel, uplink reference signal, and the like.
  • the transmitting/receiving unit 120 may form at least one of the transmission beam and the reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.
  • digital beamforming eg, precoding
  • analog beamforming eg, phase rotation
  • the transmission/reception unit 120 (transmission processing unit 1211) performs Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (for example, RLC retransmission control), Medium Access Control (MAC) layer processing (for example, HARQ retransmission control), etc. may be performed to generate a bit string to be transmitted.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • HARQ retransmission control for example, HARQ retransmission control
  • the transmission/reception unit 120 (transmission processing unit 1211) performs channel coding (which may include error correction coding), modulation, mapping, filtering, and discrete Fourier transform (DFT) on the bit string to be transmitted. Processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, transmission processing such as digital-to-analog conversion may be performed, and the baseband signal may be output.
  • channel coding which may include error correction coding
  • modulation modulation
  • mapping mapping
  • filtering filtering
  • DFT discrete Fourier transform
  • DFT discrete Fourier transform
  • the transmitting/receiving unit 120 may perform modulation to a radio frequency band, filter processing, amplification, and the like on the baseband signal, and may transmit the radio frequency band signal via the transmitting/receiving antenna 130. .
  • the transmitting/receiving unit 120 may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting/receiving antenna 130.
  • the transmission/reception unit 120 (reception processing unit 1212) performs analog-to-digital conversion, Fast Fourier transform (FFT) processing, and Inverse Discrete Fourier transform (IDFT) processing on the acquired baseband signal. )) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing and PDCP layer processing. User data and the like may be acquired.
  • FFT Fast Fourier transform
  • IDFT Inverse Discrete Fourier transform
  • the transmitting/receiving unit 120 may measure the received signal.
  • the measurement unit 123 may perform Radio Resource Management (RRM) measurement, Channel State Information (CSI) measurement, etc. based on the received signal.
  • the measurement unit 123 measures received power (for example, Reference Signal Received Power (RSRP)), reception quality (for example, Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)) , signal strength (for example, Received Signal Strength Indicator (RSSI)), channel information (for example, CSI), and the like may be measured.
  • RSRP Reference Signal Received Power
  • RSSQ Reference Signal Received Quality
  • SINR Signal to Noise Ratio
  • RSSI Received Signal Strength Indicator
  • channel information for example, CSI
  • the transmission path interface 140 transmits and receives signals (backhaul signaling) to and from devices included in the core network 30, other base stations 10, etc., and user data (user plane data) for the user terminal 20, control plane data, and the like. Data and the like may be obtained, transmitted, and the like.
  • the transmitting unit and receiving unit of the base station 10 in the present disclosure may be configured by at least one of the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission line interface 140.
  • the transmitting/receiving unit 120 may transmit settings related to multiple repetitions of the physical random access channel.
  • the controller 110 may control reception of the plurality of iterations with different beams.
  • the transceiver 120 may receive multiple repetitions of the physical random access channel transmitted using different beams.
  • the control unit 110 may control transmission of responses to the physical random access channel within one or more windows.
  • the transceiver 120 may receive multiple repetitions of the physical random access channel using different beams.
  • the control unit 110 may control the transmission of the response based on the uplink beam after the response to the physical random access channel.
  • the transceiver 120 may receive multiple repetitions of the physical random access channel using different beams.
  • the control unit 110 indicates a reference beam corresponding to one of the plurality of different beams for receiving a response to the physical random access channel, and determines the response based on the uplink beam after the response. Transmission may be controlled.
  • FIG. 36 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment.
  • the user terminal 20 includes a control section 210 , a transmission/reception section 220 and a transmission/reception antenna 230 .
  • One or more of each of the control unit 210, the transmitting/receiving unit 220, and the transmitting/receiving antenna 230 may be provided.
  • this example mainly shows the functional blocks of the features of the present embodiment, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.
  • the control unit 210 controls the user terminal 20 as a whole.
  • the control unit 210 can be configured from a controller, a control circuit, and the like, which are explained based on common recognition in the technical field according to the present disclosure.
  • the control unit 210 may control signal generation, mapping, and the like.
  • the control unit 210 may control transmission/reception, measurement, etc. using the transmission/reception unit 220 and the transmission/reception antenna 230 .
  • the control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals and transfer them to the transmission/reception unit 220 .
  • the transmitting/receiving section 220 may include a baseband section 221 , an RF section 222 and a measurement section 223 .
  • the baseband section 221 may include a transmission processing section 2211 and a reception processing section 2212 .
  • the transmitting/receiving unit 220 can be configured from a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measuring circuit, a transmitting/receiving circuit, etc., which are explained based on common recognition in the technical field according to the present disclosure.
  • the transmission/reception unit 220 may be configured as an integrated transmission/reception unit, or may be configured from a transmission unit and a reception unit.
  • the transmission section may be composed of a transmission processing section 2211 and an RF section 222 .
  • the receiving section may include a reception processing section 2212 , an RF section 222 and a measurement section 223 .
  • the transmitting/receiving antenna 230 can be configured from an antenna described based on common recognition in the technical field related to the present disclosure, such as an array antenna.
  • the transmitting/receiving unit 220 may receive the above-described downlink channel, synchronization signal, downlink reference signal, and the like.
  • the transmitting/receiving unit 220 may transmit the above-described uplink channel, uplink reference signal, and the like.
  • the transmitter/receiver 220 may form at least one of the transmission beam and the reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.
  • digital beamforming eg, precoding
  • analog beamforming eg, phase rotation
  • the transmitting/receiving unit 220 (transmission processing unit 2211) performs PDCP layer processing, RLC layer processing (eg, RLC retransmission control), MAC layer processing (eg, , HARQ retransmission control) and the like may be performed to generate a bit string to be transmitted.
  • RLC layer processing eg, RLC retransmission control
  • MAC layer processing eg, HARQ retransmission control
  • the transmission/reception unit 220 (transmission processing unit 2211) performs channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), and IFFT processing on a bit string to be transmitted. , precoding, digital-analog conversion, and other transmission processing may be performed, and the baseband signal may be output.
  • Whether or not to apply DFT processing may be based on transform precoding settings. Transmitting/receiving unit 220 (transmission processing unit 2211), for a certain channel (for example, PUSCH), if transform precoding is enabled, the above to transmit the channel using the DFT-s-OFDM waveform
  • the DFT process may be performed as the transmission process, or otherwise the DFT process may not be performed as the transmission process.
  • the transmitting/receiving unit 220 may perform modulation to a radio frequency band, filter processing, amplification, and the like on the baseband signal, and may transmit the radio frequency band signal via the transmitting/receiving antenna 230. .
  • the transmitting/receiving section 220 may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting/receiving antenna 230.
  • the transmission/reception unit 220 (reception processing unit 2212) performs analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (error correction) on the acquired baseband signal. decoding), MAC layer processing, RLC layer processing, PDCP layer processing, and other reception processing may be applied to acquire user data and the like.
  • the transmitting/receiving section 220 may measure the received signal.
  • the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal.
  • the measuring unit 223 may measure received power (eg, RSRP), received quality (eg, RSRQ, SINR, SNR), signal strength (eg, RSSI), channel information (eg, CSI), and the like.
  • the measurement result may be output to control section 210 .
  • the transmitter and receiver of the user terminal 20 in the present disclosure may be configured by at least one of the transmitter/receiver 220 and the transmitter/receiver antenna 230 .
  • the transmitting/receiving unit 220 may receive settings regarding multiple repetitions of the physical random access channel.
  • the controller 210 may control the repeated transmissions with different beams.
  • the control unit 210 may use a reference resource among a plurality of resources respectively used for a plurality of iterations for quasi co-location (QCL) assumption of reception of responses to the physical random access channel.
  • QCL quasi co-location
  • the reference resource may be indicated by downlink control information.
  • the control unit 210 may select the different beams based on the measurement result.
  • the transceiver 220 may transmit multiple repetitions of the physical random access channel using different beams.
  • the control unit 210 may control reception of responses to the physical random access channel within one or more windows.
  • the control unit 210 may start one window after the last iteration of the plurality of iterations.
  • the control unit 210 may start one window after each of the plurality of iterations.
  • the control unit 210 may determine a reference resource from a plurality of resources used for each of the plurality of iterations, and start one or more windows after the reference resource.
  • the transceiver 220 may transmit multiple repetitions of the physical random access channel using different beams.
  • the controller 210 may determine subsequent uplink beams based on receiving responses to the physical random access channel.
  • the control unit 210 may determine the uplink beam based on at least one of the timing of receiving the response and the radio network temporary identifier (RNTI) used to receive the response.
  • RNTI radio network temporary identifier
  • the control unit 210 may control monitoring of the response within a window after each of the plurality of iterations.
  • the control unit 210 may control monitoring the response within a window after the last iteration of the plurality of iterations.
  • the transceiver 220 may transmit multiple repetitions of the physical random access channel using different beams.
  • the control unit 210 determines a reference beam corresponding to one of the different beams, and determines a subsequent uplink beam based on reception using the reference beam of a response to the physical random access channel. good too.
  • the control unit 210 may determine the uplink beam based on at least one of the timing of receiving the response and the radio network temporary identifier (RNTI) used to receive the response.
  • RNTI radio network temporary identifier
  • the control unit 210 may control monitoring of the response within a window after each of the plurality of iterations.
  • the control unit 210 may control monitoring the response within a window after the last iteration of the plurality of iterations.
  • each functional block may be implemented using one device physically or logically coupled, or directly or indirectly using two or more physically or logically separated devices (e.g. , wired, wireless, etc.) and may be implemented using these multiple devices.
  • a functional block may be implemented by combining software in the one device or the plurality of devices.
  • functions include judgment, determination, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, deem , broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc.
  • a functional block (component) that performs transmission may be called a transmitting unit, a transmitter, or the like. In either case, as described above, the implementation method is not particularly limited.
  • a base station, a user terminal, etc. in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure.
  • FIG. 37 is a diagram illustrating an example of hardware configurations of a base station and user terminals according to an embodiment.
  • the base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. .
  • the hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured without some devices.
  • processor 1001 may be implemented by one or more chips.
  • predetermined software program
  • the processor 1001 performs calculations, communication via the communication device 1004 and at least one of reading and writing data in the memory 1002 and the storage 1003 .
  • the processor 1001 operates an operating system and controls the entire computer.
  • the processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, and the like.
  • CPU central processing unit
  • control unit 110 210
  • transmission/reception unit 120 220
  • FIG. 10 FIG. 10
  • the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes according to them.
  • programs program codes
  • software modules software modules
  • data etc.
  • the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be similarly implemented.
  • the memory 1002 is a computer-readable recording medium, such as Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or at least any other suitable storage medium. may be configured by one.
  • the memory 1002 may also be called a register, cache, main memory (main storage device), or the like.
  • the memory 1002 can store executable programs (program code), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.
  • the storage 1003 is a computer-readable recording medium, for example, a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disk (Compact Disc ROM (CD-ROM), etc.), a digital versatile disk, Blu-ray disc), removable disc, hard disk drive, smart card, flash memory device (e.g., card, stick, key drive), magnetic stripe, database, server, or other suitable storage medium may be configured by Storage 1003 may also be called an auxiliary storage device.
  • a computer-readable recording medium for example, a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disk (Compact Disc ROM (CD-ROM), etc.), a digital versatile disk, Blu-ray disc), removable disc, hard disk drive, smart card, flash memory device (e.g., card, stick, key drive), magnetic stripe, database, server, or other suitable storage medium may be configured by Storage 1003 may also
  • the communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, or the like.
  • the communication device 1004 includes a high-frequency switch, duplexer, filter, frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD), for example. may be configured to include
  • the transmitting/receiving unit 120 (220), the transmitting/receiving antenna 130 (230), and the like described above may be realized by the communication device 1004.
  • the transmitter/receiver 120 (220) may be physically or logically separated into a transmitter 120a (220a) and a receiver 120b (220b).
  • the input device 1005 is an input device (for example, keyboard, mouse, microphone, switch, button, sensor, etc.) that receives input from the outside.
  • the output device 1006 is an output device (for example, a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated (for example, a touch panel).
  • Each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information.
  • the bus 1007 may be configured using a single bus, or may be configured using different buses between devices.
  • the base station 10 and the user terminal 20 include a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc. It may be configured including hardware, and a part or all of each functional block may be realized using the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • PLD programmable logic device
  • FPGA field programmable gate array
  • a signal may also be a message.
  • a reference signal may be abbreviated as RS, and may also be called a pilot, a pilot signal, etc. according to an applied standard.
  • a component carrier may also be called a cell, a frequency carrier, a carrier frequency, or the like.
  • a radio frame may consist of one or more periods (frames) in the time domain.
  • Each of the one or more periods (frames) that make up a radio frame may be called a subframe.
  • a subframe may consist of one or more slots in the time domain.
  • a subframe may be a fixed time length (eg, 1 ms) independent of numerology.
  • a numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel.
  • Numerology for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration , a particular filtering process performed by the transceiver in the frequency domain, a particular windowing process performed by the transceiver in the time domain, and/or the like.
  • a slot may consist of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbol, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) in the time domain.
  • OFDM Orthogonal Frequency Division Multiplexing
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • a slot may also be a unit of time based on numerology.
  • a slot may contain multiple mini-slots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be referred to as a subslot. A minislot may consist of fewer symbols than a slot.
  • a PDSCH (or PUSCH) transmitted in time units larger than a minislot may be referred to as PDSCH (PUSCH) Mapping Type A.
  • PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (PUSCH) mapping type B.
  • Radio frames, subframes, slots, minislots and symbols all represent time units when transmitting signals. Radio frames, subframes, slots, minislots and symbols may be referred to by other corresponding designations. Note that time units such as frames, subframes, slots, minislots, and symbols in the present disclosure may be read interchangeably.
  • one subframe may be called a TTI
  • a plurality of consecutive subframes may be called a TTI
  • one slot or one minislot may be called a TTI. That is, at least one of the subframe and TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (eg, 1-13 symbols), or a period longer than 1 ms may be Note that the unit representing the TTI may be called a slot, mini-slot, or the like instead of a subframe.
  • TTI refers to, for example, the minimum scheduling time unit in wireless communication.
  • a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each user terminal) to each user terminal on a TTI basis.
  • radio resources frequency bandwidth, transmission power, etc. that can be used by each user terminal
  • a TTI may be a transmission time unit such as a channel-encoded data packet (transport block), code block, or codeword, or may be a processing unit such as scheduling and link adaptation. Note that when a TTI is given, the time interval (for example, the number of symbols) in which transport blocks, code blocks, codewords, etc. are actually mapped may be shorter than the TTI.
  • one or more TTIs may be the minimum scheduling time unit. Also, the number of slots (the number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.
  • a TTI having a time length of 1 ms may be called a normal TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, or the like.
  • a TTI that is shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, and the like.
  • the long TTI (e.g., normal TTI, subframe, etc.) may be replaced with a TTI having a time length exceeding 1 ms
  • the short TTI e.g., shortened TTI, etc.
  • a TTI having the above TTI length may be read instead.
  • a resource block is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers (subcarriers) in the frequency domain.
  • the number of subcarriers included in the RB may be the same regardless of the neumerology, eg twelve.
  • the number of subcarriers included in an RB may be determined based on neumerology.
  • an RB may contain one or more symbols in the time domain and may be 1 slot, 1 minislot, 1 subframe or 1 TTI long.
  • One TTI, one subframe, etc. may each be configured with one or more resource blocks.
  • One or more RBs are Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB Also called a pair.
  • PRB Physical Resource Block
  • SCG Sub-Carrier Group
  • REG Resource Element Group
  • PRB pair RB Also called a pair.
  • a resource block may be composed of one or more resource elements (Resource Element (RE)).
  • RE resource elements
  • 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.
  • a Bandwidth Part (which may also be called a bandwidth part) represents a subset of contiguous common resource blocks (RBs) for a numerology on a carrier.
  • the common RB may be identified by an RB index based on the common reference point of the carrier.
  • PRBs may be defined in a BWP and numbered within that BWP.
  • BWP may include UL BWP (BWP for UL) and DL BWP (BWP for DL).
  • BWP for UL
  • BWP for DL DL BWP
  • One or multiple BWPs may be configured for a UE within one carrier.
  • At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal/channel outside the active BWP.
  • BWP bitmap
  • radio frames, subframes, slots, minislots, symbols, etc. described above are merely examples.
  • the number of subframes contained in a radio frame, the number of slots per subframe or radio frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, the number of Configurations such as the number of subcarriers and the number of symbols in a TTI, symbol length, cyclic prefix (CP) length, etc. can be varied.
  • the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. may be represented. For example, radio resources may be indicated by a predetermined index.
  • data, instructions, commands, information, signals, bits, symbols, chips, etc. may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. may be represented by a combination of
  • information, signals, etc. can be output from a higher layer to a lower layer and/or from a lower layer to a higher layer.
  • Information, signals, etc. may be input and output through multiple network nodes.
  • Input/output information, signals, etc. may be stored in a specific location (for example, memory), or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated or appended. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to other devices.
  • Uplink Control Information (UCI) Uplink Control Information
  • RRC Radio Resource Control
  • MIB Master Information Block
  • SIB System Information Block
  • SIB System Information Block
  • MAC Medium Access Control
  • the physical layer signaling may also be called Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal), L1 control information (L1 control signal), and the like.
  • RRC signaling may also be called an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like.
  • MAC signaling may be notified using, for example, a MAC Control Element (CE).
  • CE MAC Control Element
  • notification of predetermined information is not limited to explicit notification, but implicit notification (for example, by not notifying the predetermined information or by providing another information (by notice of
  • the determination may be made by a value (0 or 1) represented by 1 bit, or by a boolean value represented by true or false. , may be performed by numerical comparison (eg, comparison with a predetermined value).
  • Software whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise, includes instructions, instruction sets, code, code segments, program code, programs, subprograms, and software modules. , applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like.
  • software, instructions, information, etc. may be transmitted and received via a transmission medium.
  • the software uses wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) , a server, or other remote source, these wired and/or wireless technologies are included within the definition of transmission media.
  • a “network” may refer to devices (eg, base stations) included in a network.
  • precoding "precoding weight”
  • QCL Quality of Co-Location
  • TCI state Transmission Configuration Indication state
  • spatialal patial relation
  • spatialal domain filter "transmission power”
  • phase rotation "antenna port
  • antenna port group "layer”
  • number of layers Terms such as “rank”, “resource”, “resource set”, “resource group”, “beam”, “beam width”, “beam angle”, “antenna”, “antenna element”, “panel” are interchangeable. can be used as intended.
  • base station BS
  • radio base station fixed station
  • NodeB NodeB
  • eNB eNodeB
  • gNB gNodeB
  • Access point "Transmission Point (TP)”, “Reception Point (RP)”, “Transmission/Reception Point (TRP)”, “Panel”
  • a base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, and the like.
  • a base station can accommodate one or more (eg, three) cells.
  • the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area is assigned to a base station subsystem (e.g., a small indoor base station (Remote Radio)). Head (RRH))) may also provide communication services.
  • a base station subsystem e.g., a small indoor base station (Remote Radio)). Head (RRH)
  • RRH Head
  • the terms "cell” or “sector” refer to part or all of the coverage area of at least one of the base stations and base station subsystems that serve communication within such coverage.
  • MS Mobile Station
  • UE User Equipment
  • Mobile stations include 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. , a handset, a user agent, a mobile client, a client, or some other suitable term.
  • At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, or the like. At least one of the base station and the mobile station may be a device mounted on a moving object, the mobile itself, or the like.
  • the moving body refers to a movable object, the speed of movement is arbitrary, and it naturally includes cases where the moving body is stationary.
  • Examples of such moving bodies include vehicles, transportation vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, carts, rickshaws, and ships (ships and other watercraft). , airplanes, rockets, satellites, drones, multi-copters, quad-copters, balloons and objects mounted on them.
  • the mobile body may be a mobile body that autonomously travels based on an operation command.
  • the mobile object may be a vehicle (e.g., car, airplane, etc.), an unmanned mobile object (e.g., drone, self-driving car, etc.), or a robot (manned or unmanned ).
  • a vehicle e.g., car, airplane, etc.
  • an unmanned mobile object e.g., drone, self-driving car, etc.
  • a robot manned or unmanned .
  • at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations.
  • at least one of the base station and mobile station may be an Internet of Things (IoT) device such as a sensor.
  • IoT Internet of Things
  • FIG. 38 is a diagram showing 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 (current sensor 50, revolution sensor 51, air pressure sensor 52, vehicle speed sensor 53, acceleration sensor 54, accelerator pedal sensor 55, brake pedal sensor 56, shift lever sensor 57, and object detection sensor 58), information service unit 59 and communication module 60.
  • various sensors current sensor 50, revolution sensor 51, air pressure sensor 52, vehicle speed sensor 53, acceleration sensor 54, accelerator pedal sensor 55, brake pedal sensor 56, shift lever sensor 57, and object detection sensor 58
  • information service unit 59 and communication module 60.
  • the driving unit 41 is composed of, for example, at least one of an engine, a motor, and a hybrid of an engine and a motor.
  • the steering unit 42 includes at least a steering wheel (also referred to as a steering wheel), and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by the user.
  • the electronic control unit 49 is composed of a microprocessor 61 , a memory (ROM, RAM) 62 , and a communication port (eg, input/output (IO) port) 63 . Signals from various sensors 50 to 58 provided in the vehicle are input to the electronic control unit 49 .
  • the electronic control unit 49 may be called an Electronic Control Unit (ECU).
  • ECU Electronic Control Unit
  • the signals from the various sensors 50 to 58 include a current signal from the current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46/rear wheels 47 obtained by the rotation speed sensor 51, and an air pressure sensor 52.
  • air pressure signal of front wheels 46/rear wheels 47 vehicle speed signal obtained by vehicle speed sensor 53, acceleration signal obtained by acceleration sensor 54, depression amount signal of accelerator pedal 43 obtained by accelerator pedal sensor 55, brake pedal sensor
  • the information service unit 59 includes various devices such as car navigation systems, audio systems, speakers, displays, televisions, and radios for providing (outputting) various information such as driving information, traffic information, and entertainment information, and these devices. and one or more ECUs that control The information service unit 59 provides various information/services (for example, multimedia information/multimedia services) to the occupants of the vehicle 40 using information acquired from an external device via the communication module 60 or the like.
  • various information/services for example, multimedia information/multimedia services
  • the information service unit 59 may include an input device (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) that receives input from the outside, and an output device that outputs to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).
  • an input device e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.
  • an output device e.g., display, speaker, LED lamp, touch panel, etc.
  • the driving support system unit 64 includes a millimeter wave radar, Light Detection and Ranging (LiDAR), a camera, a positioning locator (e.g., Global Navigation Satellite System (GNSS), etc.), map information (e.g., High Definition (HD)) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., inertial measurement units (IMU), inertial navigation systems (INS), etc.), artificial intelligence ( Artificial intelligence (AI) chips, AI processors, and other devices that provide functions to prevent accidents and reduce the driver's driving load, and one or more devices that control these devices ECU.
  • the driving support system unit 64 transmits and receives various information via the communication module 60, and realizes a driving support function or an automatic driving function.
  • the communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63 .
  • the communication module 60 communicates with the vehicle 40 through a communication port 63 such as a driving 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, Data (information) is transmitted and received between the axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58.
  • the communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with an external device. For example, it transmits and receives various information to and from an external device via wireless communication.
  • Communication module 60 may be internal or external to electronic control 49 .
  • the external device may be, for example, the above-described base station 10, user terminal 20, or the like.
  • the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (and may function as at least one of the base station 10 and the user terminal 20).
  • the communication module 60 receives signals from the various sensors 50 to 58 described above input to the electronic control unit 49, information obtained based on the signals, and input from the outside (user) obtained via the information service unit 59. may be transmitted to the external device via wireless communication.
  • the electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be called an input unit that receives input.
  • the PUSCH transmitted by communication module 60 may include information based on the above inputs.
  • the communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 59 provided in the vehicle.
  • the information service unit 59 is 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 data/information decoded from the PDSCH)). may be called
  • the communication module 60 stores various information received from an external device in a memory 62 that can be used by the microprocessor 61 . Based on the information stored in the memory 62, the microprocessor 61 controls the drive unit 41, the steering unit 42, the accelerator pedal 43, the brake pedal 44, the shift lever 45, the left and right front wheels 46, and the left and right rear wheels provided in the vehicle 40. 47, axle 48, and various sensors 50-58 may be controlled.
  • the base station in the present disclosure may be read as a user terminal.
  • communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.)
  • the user terminal 20 may have the functions of the base station 10 described above.
  • words such as "uplink” and “downlink” may be replaced with words corresponding to communication between terminals (for example, "sidelink”).
  • uplink channels, downlink channels, etc. may be read as sidelink channels.
  • user terminals in the present disclosure may be read as base stations.
  • the base station 10 may have the functions of the user terminal 20 described above.
  • operations that are assumed to be performed by the base station may be performed by its upper node in some cases.
  • various operations performed for communication with a terminal may involve the base station, one or more network nodes other than the base station (e.g., Clearly, this can be done by a Mobility Management Entity (MME), Serving-Gateway (S-GW), etc. (but not limited to these) or a combination thereof.
  • MME Mobility Management Entity
  • S-GW Serving-Gateway
  • each aspect/embodiment described in the present disclosure may be used alone, may be used in combination, or may be used by switching along with execution. Also, the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in the present disclosure may be rearranged as long as there is no contradiction. For example, the methods described in this disclosure present elements of the various steps using a sample order, and are not limited to the specific order presented.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-B LTE-Beyond
  • SUPER 3G IMT-Advanced
  • 4G 4th generation mobile communication system
  • 5G 5th generation mobile communication system
  • 6G 6th generation mobile communication system
  • xG x is, for example, an integer or a decimal number
  • Future Radio Access FAA
  • RAT New-Radio Access Technology
  • NR New Radio
  • NX New radio access
  • FX Future generation radio access
  • GSM registered trademark
  • CDMA2000 Code Division Multiple Access
  • UMB Ultra Mobile Broadband
  • IEEE 802 .11 Wi-Fi®
  • IEEE 802.16 WiMAX®
  • IEEE 802.20 Ultra-WideBand (UWB), Bluetooth®, or any other suitable wireless communication method. It may be applied to a system to be used, a next-generation system extended, modified, created or defined based on these.
  • any reference to elements using the "first,” “second,” etc. designations used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, references to first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.
  • determining includes judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry ( For example, looking up in a table, database, or another data structure), ascertaining, etc. may be considered to be “determining.”
  • determining (deciding) includes receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output, access ( accessing (e.g., accessing data in memory), etc.
  • determining is considered to be “determining” resolving, selecting, choosing, establishing, comparing, etc. good too. That is, “determining (determining)” may be regarded as “determining (determining)” some action.
  • Maximum transmit power described in this disclosure may mean the maximum value of transmit power, may mean the nominal maximum transmit power (the nominal UE maximum transmit power), or may mean the rated maximum transmit power (the rated UE maximum transmit power).
  • connection refers to any connection or coupling, direct or indirect, between two or more elements. and can include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” to each other. Couplings or connections between elements may be physical, logical, or a combination thereof. For example, "connection” may be read as "access”.
  • radio frequency domain when two elements are connected, using one or more wires, cables, printed electrical connections, etc., and as some non-limiting and non-exhaustive examples, radio frequency domain, microwave They can be considered to be “connected” or “coupled” together using the domain, electromagnetic energy having wavelengths in the optical (both visible and invisible) domain, and the like.
  • a and B are different may mean “A and B are different from each other.”
  • the term may also mean that "A and B are different from C”.
  • Terms such as “separate,” “coupled,” etc. may also be interpreted in the same manner as “different.”

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un terminal selon un mode de réalisation de la présente divulgation comprend : une unité de transmission qui transmet une pluralité de répétitions d'un canal d'accès aléatoire physique, à l'aide d'une pluralité de faisceaux différents ; et une unité de commande qui commande la réception de réponses aux canaux d'accès aléatoire physiques dans une ou plusieurs fenêtres. Ledit mode de réalisation de la présente divulgation permet d'améliorer la couverture pour une procédure d'accès aléatoire.
PCT/JP2021/048309 2021-12-24 2021-12-24 Terminal, procédé de communication sans fil et station de base WO2023119647A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2023569009A JPWO2023119647A1 (fr) 2021-12-24 2021-12-24
PCT/JP2021/048309 WO2023119647A1 (fr) 2021-12-24 2021-12-24 Terminal, procédé de communication sans fil et station de base

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2021/048309 WO2023119647A1 (fr) 2021-12-24 2021-12-24 Terminal, procédé de communication sans fil et station de base

Publications (1)

Publication Number Publication Date
WO2023119647A1 true WO2023119647A1 (fr) 2023-06-29

Family

ID=86901937

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/048309 WO2023119647A1 (fr) 2021-12-24 2021-12-24 Terminal, procédé de communication sans fil et station de base

Country Status (2)

Country Link
JP (1) JPWO2023119647A1 (fr)
WO (1) WO2023119647A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200107359A1 (en) * 2016-12-16 2020-04-02 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method and device for random access
US20210127425A1 (en) * 2017-03-14 2021-04-29 Lg Electronics Inc. Method for performing random access procedure between terminal and base station in wireless communication system, and device supporting same

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200107359A1 (en) * 2016-12-16 2020-04-02 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method and device for random access
US20210127425A1 (en) * 2017-03-14 2021-04-29 Lg Electronics Inc. Method for performing random access procedure between terminal and base station in wireless communication system, and device supporting same

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MEDIATEK INC.: "On 4-step RACH procedure", 3GPP DRAFT; R1-1710824_ON_4-STEP_RACH_PROCEDURE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Qingdao, P.R. China; 20170627 - 20170630, 26 June 2017 (2017-06-26), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051300028 *

Also Published As

Publication number Publication date
JPWO2023119647A1 (fr) 2023-06-29

Similar Documents

Publication Publication Date Title
WO2023119647A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2023119649A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2023119646A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2023119648A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2023105756A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2023105755A1 (fr) Terminal, procédé de communication radio et station de base
WO2023105754A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2023135754A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2023135755A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2023095272A1 (fr) Terminal, procédé de communication radio et station de base
WO2023095271A1 (fr) Terminal, procédé de communication radio et station de base
WO2023095270A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2023095269A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2023095273A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024009401A1 (fr) Terminal, procédé de communication radio, et station de base
WO2024038515A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024009400A1 (fr) Terminal, procédé de communication radio, et station de base
WO2024038514A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024009402A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024038516A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024009403A1 (fr) Terminal, procédé de radiocommunication et station de base
WO2023223551A1 (fr) Terminal, procédé de communication radio et station de base
WO2023223552A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024069840A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024154343A1 (fr) Terminal, procédé de communication sans fil et station de base

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21969078

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023569009

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE