WO2024009402A1 - Terminal, wireless communication method, and base station - Google Patents

Terminal, wireless communication method, and base station Download PDF

Info

Publication number
WO2024009402A1
WO2024009402A1 PCT/JP2022/026726 JP2022026726W WO2024009402A1 WO 2024009402 A1 WO2024009402 A1 WO 2024009402A1 JP 2022026726 W JP2022026726 W JP 2022026726W WO 2024009402 A1 WO2024009402 A1 WO 2024009402A1
Authority
WO
WIPO (PCT)
Prior art keywords
repetitions
msg3
msg1
prach
random access
Prior art date
Application number
PCT/JP2022/026726
Other languages
French (fr)
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 PCT/JP2022/026726 priority Critical patent/WO2024009402A1/en
Publication of WO2024009402A1 publication Critical patent/WO2024009402A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities

Definitions

  • the present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system.
  • LTE Long Term Evolution
  • 3GPP Rel. 10-14 is a specification for the purpose of further increasing capacity and sophistication of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel. 8, 9). was made into
  • LTE Long Term Evolution
  • 5G 5th generation mobile communication system
  • 5G+ plus
  • NR New Radio
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • 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 purposes 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 includes a transmitting unit that transmits first capability information regarding the ability to repeat a message 1 and second capability information regarding the ability to repeat a message 3; Based on the second capability information, a first random access procedure is performed that includes the repetition of the message 1 and the repetition of the message 3, or a second random access procedure that does not include at least one of the repetition of the message 1 and the repetition of the message 3 is performed. and a control unit that determines whether to perform a random access procedure.
  • FIG. 1A and 1B show an example of multi-PRACH transmission.
  • FIG. 2 shows an example of the relationship between PRACH mask index and allowed PRACH occasions (RO) of SSB.
  • FIG. 3 shows an example of the relationship between the 2MSB value (code point) of the MCS information field and the number of repetitions K.
  • 4A and 4B show an example of the relationship between Msg1 and Msg2.
  • FIG. 5 shows an example of the RACH procedure for RSRP with DL path loss reference according to embodiment #1a-1.
  • FIG. 6 shows an example of the RACH procedure for RSRP with DL path loss reference according to Example 1 of Embodiment #1a-2.
  • FIG. 7 shows an example of the RACH procedure for RSRP with DL path loss reference according to Example 2 of Embodiment #1a-2.
  • FIG. 8 shows an example of the RACH procedure for RSRP with DL path loss reference according to the embodiment 1a-3.
  • 9A and 9B show an example of application conditions according to embodiment #1a-4.
  • FIG. 10 shows an example of the RSRP threshold.
  • FIG. 11 shows an example of transmission beam 1-1A.
  • FIG. 12 shows another example of the transmission beam 1-1A.
  • FIG. 13 shows an example of transmission beam 1-1B.
  • FIG. 14 shows a first example of transmit beams 1-2A.
  • FIG. 15 shows a second example of transmit beams 1-2A.
  • FIG. 16 shows a third example of transmit beams 1-2A.
  • FIG. 17 shows a fourth example of transmit beams 1-2A.
  • FIG. 18 shows an example of the transmission beam 2-1A.
  • FIG. 19 shows another example of the transmission beam 2-1A.
  • FIG. 20 shows an example of transmission beam 2-2A.
  • FIG. 21 shows another example of the transmission beam 2-2A.
  • 22A to 22C show examples of candidate values for the number of Msg3 repeats.
  • FIG. 23 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment.
  • FIG. 24 is a diagram illustrating an example of the configuration of a base station according to an embodiment.
  • FIG. 25 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment.
  • FIG. 26 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment.
  • FIG. 27 is a diagram illustrating an example of a vehicle according to an embodiment.
  • the UE performs reception processing (e.g. reception, demapping, demodulation, Controlling at least one of decoding), transmission processing (eg, at least one of transmission, mapping, precoding, modulation, and encoding) is being considered.
  • reception processing e.g. reception, demapping, demodulation, Controlling at least one of decoding
  • transmission processing e.g, at least one of transmission, mapping, precoding, modulation, and encoding
  • the TCI states may represent those that apply to downlink signals/channels. What corresponds to the TCI state applied to uplink signals/channels may be expressed as a spatial relation.
  • the TCI state is information regarding quasi-co-location (QCL) of signals/channels, and may also be called spatial reception parameters, spatial relation information, etc.
  • the TCI state may be set in the UE on a per-channel or per-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, the Doppler shift, Doppler spread, and average delay are calculated between these different signals/channels. ), delay spread, and spatial parameters (e.g., spatial Rx parameters) can be assumed to be the same (QCL with respect to at least one of these). You may.
  • the spatial reception parameters may correspond to the UE's reception beam (eg, reception analog beam), and the beam may be identified 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 QCL.
  • QCL types A-D 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): Doppler shift, Doppler spread, average delay and delay spread, ⁇ QCL type B (QCL-B): Doppler shift and Doppler spread, ⁇ QCL type C (QCL-C): Doppler shift and average delay, - QCL type D (QCL-D): Spatial reception parameters.
  • Control Resource Set CORESET
  • channel or reference signal is in a particular QCL (e.g. QCL type D) relationship with another CORESET, channel or reference signal, It may also be called a QCL assumption.
  • QCL Control Resource Set
  • the UE may determine at least one of a transmit beam (Tx beam) and a receive beam (Rx beam) for the signal/channel based on the TCI state or QCL assumption of the signal/channel.
  • Tx beam transmit beam
  • Rx beam receive beam
  • the TCI state may be, for example, information regarding the QCL between a target channel (in other words, a reference signal (RS) for the channel) and another signal (for example, another RS). .
  • the TCI state may be set (indicated) by upper layer signaling, physical layer signaling, or a combination thereof.
  • the 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), and Uplink Shared Channel (Physical Uplink Shared Channel).
  • the channel may be at least one of a physical uplink control channel (PUCCH) and a physical uplink control channel (PUCCH).
  • the RS that has a QCL relationship with the channel is, for example, a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a measurement reference signal (Sounding Reference Signal (SRS)), tracking CSI-RS (also referred to as Tracking Reference Signal (TRS)), and QCL detection reference signal (also referred to as QRS).
  • SSB synchronization signal block
  • CSI-RS channel state information reference signal
  • SRS Sounding Reference Signal
  • TRS Tracking Reference Signal
  • QRS QCL detection reference signal
  • the 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 RS of QCL type X in a TCI state may mean an RS that has a QCL type You can.
  • the UE receives SS/PBCH blocks (SSB), Msg. 1 (PRACH/random access preamble/preamble) transmission, Msg. 2 (PDCCH, PDSCH including random access response (RAR)), Msg. 3 (PUSCH scheduled by RAR UL grant) transmission, Msg. 4 (PDCCH, PDSCH including UE contention resolution identity).
  • SSB SS/PBCH blocks
  • Msg. 1 PRACH/random access preamble/preamble
  • Msg. 2 PDCCH, PDSCH including random access response (RAR)
  • Msg. 3 PUSCH scheduled by RAR UL grant
  • Msg. 4 (PDCCH, PDSCH including UE contention resolution identity).
  • SSB reception includes PSS detection, SSS detection, PBCH-DMRS detection, and PBCH reception.
  • PSS detection performs detection of part of the physical cell ID (PCI), detection (synchronization) of OFDM symbol timing, 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 involves detecting the system frame number (SFN) and radio frame timing (SSB index), receiving configuration information for receiving remaining minimum system information (RMSI, SIB1), and allowing the UE to camp in that cell (carrier). including the recognition of whether or not.
  • the SSB has a band of 20 RB and a time of 4 symbols.
  • the SSB transmission cycle can be set from ⁇ 5, 10, 20, 40, 80, 160 ⁇ ms.
  • a plurality of SSB symbol positions are defined based on the frequency range (FR1, FR2).
  • PBCH has a 56-bit payload. N repetitions of the PBCH are transmitted within a period of 80ms. N depends on the SSB transmission period.
  • SIB1 includes information for performing RACH settings and RACH procedures.
  • the time/frequency resource relationship between the SSB and the PDCCH monitoring resource for SIB1 is set by the PBCH.
  • a base station that uses beam correspondence transmits multiple SSBs using multiple beams in each SSB transmission period.
  • Each of the plurality of SSBs has a plurality of SSB indexes.
  • a UE that detects one SSB transmits a PRACH in the RACH occasion associated with that SSB index and receives a RAR in the RAR window.
  • beam and coverage In high frequency bands, if beamforming is not applied to the synchronization signal/reference signal, the coverage will be narrow and it will be difficult for the UE to discover the base station. On the other hand, if beamforming is applied to the synchronization signal/reference signal to ensure coverage, a strong signal will reach in a specific direction, but it will be more difficult for the signal to reach in other directions. If the direction in which the UE exists 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 that the base station transmits multiple synchronization signals/reference signals, each having beams in different directions, and the UE recognizes which beam it has discovered. Using thin (narrow) beams for coverage requires transmitting many synchronization/reference signals, which may increase overhead and reduce spectrum efficiency.
  • Coverage extension including PRACH extension for frequency range (FR) 2 is being considered. For example, PRACH repetition using the same beam or different beams is being considered. This PRACH extension may be applied to FR1.
  • PRACH extension may be applied to the short PRACH format or to other formats.
  • the common RACH configuration includes 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 for each SSB (ssb-perRACH). -OccasionAndCB-PreamblesPerSSB).
  • the rach-ConfigGeneric may include a PRACH configuration index (prach-ConfigurationIndex) and a message 1FDM (msg1-FDM, number of PRACH occasions to be FDMed within one time instance).
  • ssb-perRACH-OccasionAndCB-PreamblesPerSSB may include the number of CB preambles for each SSB for the number of SSBs for each RACH occasion 1/8 (oneEighth, one SSB is associated with eight RACH occasions).
  • the UE determines the number N of SS/PBCH blocks associated with one PRACH occasion and the 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 procedure and msgA-TotalNumberOfRA-Preambles for type 2 random access procedure with configuration of PRACH occasion independent of type 1 random access procedure. given by. 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 indexes are mapped to PRACH occasions at least once within the association period.
  • N_Tx ⁇ SSB is the minimum value in the set determined by the PRACH configuration period according to the relationship (relationship defined in the specification) between the PRACH configuration period and the association period (number of PRACH configuration periods).
  • the UE obtains N_Tx ⁇ SSB from the value of SSB positions in bursts (ssb-PositionsInBurst) in SIB1 or in the common serving cell configuration (ServingCellConfigCommon).
  • the SS/PBCH block index is also not mapped to a PRACH occasion or its set of PRACH preambles.
  • the association pattern period includes one or more association periods and is determined such that the pattern between PRACH occasion and SS/PBCH block index repeats at most every 160 ms. If there is a PRACH occasion that is not associated with an SS/PBCH block index after an integer number of association periods, that PRACH occasion is not used for PRACH.
  • the association period is ⁇ 1, 2, 4, 8, 16 ⁇ , ⁇ 1, 2, 4, 8 ⁇ , ⁇ 1, 2, 4 ⁇ , ⁇ 1, 2 ⁇ , and ⁇ 1 ⁇ .
  • One RO is associated with SSBs 0 to 3.
  • Preamble indexes 0 to 15 are associated with SSB0
  • preamble indexes 15 to 31 are associated with SSB1
  • preamble indexes 32 to 47 are associated with SSB2
  • SSB3 is associated with preamble indexes 48 to 63
  • SSB3 is associated with SSB3.
  • the same RO is associated with different SS/PBCH block indices and different preambles use different SS/PBCH block indices.
  • the base station can distinguish the associated SS/PBCH block index by the received PRACH.
  • the random access preamble can only be transmitted on the time resources specified in the random access configuration of the specification, whether it is FR1 or FR2, and the spectrum type (paired spectrum/supplementary uplink (SUL)/unpaired spectrum). (unpaired) spectrum).
  • the PRACH configuration index is given by the upper layer parameter prach-ConfigurationIndex or, if configured, by msgA-PRACH-ConfigurationIndex.
  • the type of RACH procedure may be at least one of the following: ⁇ Contention-free random access (CFRA), PDCCH ordered RA (PDCCH ordered RA, RA initiated by PDCCH order), CFRA for beam failure recovery (BFR), CFRA for system information (SI) request, synchronization CFRA for reconfiguration with sync, etc. - contention-based random access (CBRA), RA triggered by MAC entity, RA triggered by RRC 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 RACH-related counters/timers, 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 RACH-related counters/timers, etc. If such settings/procedures are not clear, there is a risk of deterioration in communication quality/communication throughput.
  • the RA response window (ra-ResponseWindow) is a time window for monitoring the RA response (RAR) (SpCell only).
  • the RA contention resolution timer (ra-ContentionResolutionTimer) is a timer for RA contention resolution (SpCell only).
  • Msg. B response window is a time window for monitoring RA response (RAR) for two-step RA type (SpCell only).
  • the MAC entity performs actions 1 to 3 below, regardless of the possibility that a measurement gap may occur.
  • the MAC entity performs the following actions 2-1 and 2-2.
  • the MAC entity starts the ra-ResponseWindow configured in the common RACH configuration (RACH-ConfigCommon) in the first PDCCH occasion from the end of the RA preamble transmission.
  • the MAC entity monitors the PDCCH transmission of the SpCell for RAR identified by the RA-RNTI while the ra-ResponseWindow is operating.
  • the MAC entity may stop ra-ResponseWindow (may stop monitoring for RARs) after successful reception of RARs containing RA preamble identifiers matching the transmitted PREAMBLE_INDEX.
  • PDCCH monitoring within the RA response window There are two cases for PDCCH monitoring within the RA response window: PDCCH for base station response to BFR and PDCCH for RAR. The following may apply to both cases.
  • the MAC entity performs actions 4 to 6 below, regardless of the possibility of a measurement gap occurring.
  • msgB-ResponseWindow is the first of the earliest CORESET the UE is configured to receive a 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. It may start at the symbol.
  • the length of msgB-ResponseWindow may correspond to the SCS for Type 1-PDCCH CSS set.
  • the MAC entity monitors the PDCCH transmission of the SpCell for the RAR identified by the MSGB-RNTI while the msgB-ResponseWindow is active.
  • RA-RNTI 1+s_id+14 ⁇ t_id+14 ⁇ 80 ⁇ f_id+14 ⁇ 80 ⁇ 8 ⁇ ul_carrier_id
  • the subcarrier spacing (SCS) for determining 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) carriers, 1 for supplementary uplink (SUL) carriers).
  • RA-RNTI is calculated according to specifications.
  • RA-RNTI is an 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
  • the subcarrier spacing (SCS) for determining 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) carriers, 1 for supplementary uplink (SUL) carriers).
  • MSGB-RNTI is an RNTI for 2-step RACH.
  • DCI format 1_0 includes a DCI format identifier field, a bit field that is always set to 1, and a frequency domain resource assignment field. If the cyclic redundancy check (CRC) of DCI format 1_0 is scrambled by C-RNTI and the frequency domain resource allocation field is all ones, then that DCI format 1_0 is for random access procedure initiated by PDCCH order and the rest
  • the fields are random access preamble, UL/supplementary Uplink (SUL) indicator, SS/PBCH index (SSB index), PRACH mask index, and reserved bits (12 bits).
  • the PRACH mask index field specifies that if the value of the Random Access Preamble Index field is non-zero, the PRACH occasion is the SS/PBCH block i indicated by the SS/PBCH block index field of the PDCCH order. indicates the PRACH occasion of the PRACH transmission associated with the index.
  • the PRACH mask index is indicated by ra-ssb-OccasionMaskIndex.
  • the ra-ssb-OccasionMaskIndex indicates the PRACH occasion for the PRACH transmission that is associated with the selected SS/PBCH block index.
  • PRACH occasions are mapped consecutively for each corresponding SS/PBCH block index.
  • the PRACH occasion indexing indicated by the mask index value is reset every SS/PBCH block index and every successive PRACH occasion mapping cycle.
  • the UE selects the PRACH occasion indicated by the PRACH mask index value for the indicated SS/PBCH block index for PRACH transmission in the first available mapping cycle.
  • the order of PRACH occasions is as follows. - First, increasing order of frequency resource index for frequency multiplexed PRACH occasions. - Second, increasing order of time resource index for time multiplexed PRACH occasions within a PRACH slot. - Third, ascending order of PRACH slot index.
  • the value of ra-OccasionList indicates the list of PRACH occasions for PRACH transmissions, and the 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.
  • the value of the PRACH mask index value (msgA-SSB-SharedRO-MaskIndex) is associated with the allowed PRACH occasions of the SSB (the value of the PRACH occasion index).
  • the random access procedure is initiated by the PDCCH order, by the MAC entity itself, or by RRC for specification compliant events. Only one random access procedure is ongoing within a MAC entity 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 a random access procedure is initiated by a PDCCH order and the ra-PreambleIndex explicitly provided by the PDCCH is not 0b000000, or if a random access procedure is initiated for reconfiguration with synchronization, If contention-free random access resources of step RA type are 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 by PDCCH and ra-PreambleIndex is not 0b000000, set PREAMBLE_INDEX to the notified ra-PreambleIndex and select the SSB notified by PDCCH.
  • MAC next available PRACH occasion from the PRACH occasions allowed by the restriction given by ra-ssb-OccasionMaskIndex and corresponding to the selected SSB (MAC).
  • the entity randomly selects a PRACH occasion among consecutive PRACH occasions with equal probability, corresponding to the selected SSB, according to the specification.
  • the MAC entity selects the next available PRACH corresponding to the selected SSB.
  • the possibility of measurement gaps may be considered).
  • N_(T,2) is the duration of N_2 symbols corresponding to the PUSCH preparation time of UE processing capability 1. It is assumed that ⁇ corresponds to the minimum SCS setting between the subcarrier spacing (SCS) setting of the PDCCH order and that of the corresponding PRACH transmission.
  • SCS subcarrier spacing
  • ⁇ _BWPSwitching 0, otherwise ⁇ _BWPSwitching is defined in the specification.
  • ⁇ _delay 0.5 msec
  • ⁇ _delay 0.25 msec
  • T_switch is the switching gap duration defined in the specification.
  • PRACH occasion ⁇ Conditions for valid/invalid of PRACH occasion (valid conditions)> All PRACH occasions are valid in paired spectrum (FDD) or SUL bands. In unpaired spectrum (TDD), PRACH occasions may comply with regulations 1 and 2 below. [Regulation 1] In case the UE is not provided with tdd-UL-DL-ConfigurationCommon, the PRACH occasion within the PRACH slot does not precede the SS/PBCH block within the 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 defined in the specifications.
  • channelAccessMode semistatic is provided, there is no overlap with the set of consecutive symbols before the start of the next channel occupation 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.
  • the PRACH occasion within the PRACH slot is valid in the following cases: - The PRACH occasion is within the UL symbol.
  • Step 4 in CBRA Rel.
  • Step 4 (Msg4) in the RA procedure of 16 NR follows the Step 4 operation below.
  • DCI format in response to a PUSCH transmission scheduled by RAR UL grant or in response to a corresponding PUSCH retransmission scheduled by DCI format 0_0 with CRC scrambled by TC-RNTI provided in the corresponding RAR message. If the UE detects that the PDCCH carrying that DCI format is used by the UE for PRACH association, regardless of whether the UE is provided with TCI status for the CORESET in which the UE received the PDCCH with that DCI format.
  • the same DM-RS antenna port QCL properties as the DM-RS antenna port quasi co-location (QCL) properties for the SS/PBCH block may be assumed.
  • the UE In response to the PRACH transmission, the UE attempts to detect DCI format 1_0 with the CRC scrambled by the corresponding RA-RNTI during the window controlled by the above-mentioned upper layers.
  • the window Start In the first symbol of the earliest CORESET in which the UE is configured to receive a PDCCH for a type 1-PDCCH CSS set, i.e. at least one symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission, the window Start.
  • the symbol period corresponds to the SCS for Type 1-PDCCH CSS set.
  • the length of the window is based on the SCS for type 1-PDCCH CSS set and is provided by ra-responseWindow as the number of slots.
  • the UE attempts to detect a DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order triggering a CFRA procedure for the SpCell, the UE detects that DCI format It may be assumed that the PDCCH including 1_0 and its PDCCH order have the same DMRS antenna port QCL properties.
  • the UE decides whether to apply Msg3 repetition based on RSRP. If Msg repetition is configured and the RSRP of DL path loss reference is less than rsrp-ThresholdMsg3, the MAC entity assumes that Msg3 repetition is applicable to the current random access (RA) procedure.
  • RA random access
  • the UE can request Msg3PUSCH repetition via a separate PRACH resource. If there is one or more sets of RA resources available, and one of the one or more sets is used to direct all functions that trigger this RA procedure, and all functions that trigger this RA procedure.
  • the MAC entity selects an RA resource if and when there is one or more sets of available RA resources configured with instructions for a subset of the functionality of the MAC entity. If Msg3 repetition indication is configured for a set of RA resources, and Msg3 repetition is not available, the MAC entity considers that set of RA resources not available for RACH procedures.
  • RA resources may be partitioned for each function.
  • the functionality may include at least one of Msg3 repetition, reduced capacity (RedCap), small data transmission (SDT), and RAN slicing.
  • SIB1 includes ServingCellConfigCommonSIB. It includes UplinkConfigCommonSIB. It includes BWP-UplinkCommon (UL BWP common settings).
  • BWP-UplinkCommon may include RACH common settings (RACH-ConfigCommon or MsgA-ConfigCommon) and additionalRACH-ConfigList-r17 (additional RACH configuration list).
  • additionalRACH-ConfigList-r17 may include rsrp-ThresholdMsg3-r17 (threshold).
  • the RACH common settings may include FeatureCombinationPreambles.
  • FeatureCombinationPreambles associates one set (partition) of preambles with one feature combination.
  • FeatureCombinationPreambles may include FeatureCombination (feature combination setting), startPreambleForThisPartition (index of first preamble), numberOfPreamblesPerSSB-ForThisPartition (number of preambles), and ssb-SharedRO-MaskIndex-r17 (PRACH mask index).
  • FeatureCombination includes at least one of redCap (RedCap), smallData (SDT), sliceGroup (RAN slicing), and msg3-Repetition (Msg3 repetition). The partition is given by the index of the first preamble and the preamble number.
  • the number of Msg3 repetitions is indicated by the 2 most significant bits (MSB) (upper 2 bits) of the modulation and coding scheme (MCS) field in the RAR UL grant.
  • MSB most significant bits
  • MCS modulation and coding scheme
  • FIG. 3 shows an example of the relationship (table) between the 2MSB value (code point) of the MCS information field and the number of repetitions K.
  • PUSCH repetition type A when transmitting a PUSCH scheduled by a RAR UL grant, the 2MSB of the MCS information field of the RAR UL grant is set according to the table in FIG. 3, based on whether the upper layer parameter numberOfMsg3Repetitions is set.
  • the number of slots N used for transport block size (TBS) determination is equal to one.
  • PUSCH repetition type B when transmitting a PUSCH scheduled by DCI format 0_0 with CRC scrambled by TC-RNTI, the 2MSB of the MCS information field of that DCI format determines whether the upper layer parameter numberOfMsg3Repetitions is set or not. Based on the table of FIG. 3, we provide code points for determining the number of iterations K. The number of slots N used for TBS determination is equal to 1.
  • Rel.17 the UE capability of Msg3 repetition was introduced and Rel. 18, the introduction of the UE capability of repeating Msg3 is being considered.
  • the following problems can be considered.
  • A/B and “at least one of A and B” may be read interchangeably. Furthermore, in the present disclosure, “A/B/C” may mean “at least one of A, B, and C.”
  • Radio Resource Control RRC
  • RRC parameters RRC parameters
  • RRC messages RRC messages
  • upper layer parameters information elements (IEs), settings, etc.
  • IEs information elements
  • CE Medium Access Control Element
  • update command activation/deactivation command, etc.
  • the upper layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof.
  • RRC Radio Resource Control
  • MAC Medium Access Control
  • MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), or the like.
  • Broadcast information includes, for example, a master information block (MIB), a system information block (SIB), a minimum system information (RMSI), and other system information ( Other System Information (OSI)) may also be used.
  • MIB master information block
  • SIB system information block
  • RMSI minimum system information
  • OSI Other System Information
  • the physical layer signaling may be, for example, downlink control information (DCI), uplink control information (UCI), etc.
  • DCI downlink control information
  • UCI uplink control information
  • an index an identifier (ID), an indicator, a resource ID, etc.
  • ID an identifier
  • indicator an indicator
  • resource ID a resource ID
  • sequences, lists, sets, groups, groups, clusters, subsets, etc. may be used interchangeably.
  • a panel, a UE panel, a panel group, a beam, a beam group, a precoder, an uplink (UL) transmitting entity, a transmission/reception point (TRP), a base station, and a spatial relation information (SRI) are described.
  • SRS resource indicator SRI
  • control resource set CONtrol REsource SET (CORESET)
  • Physical Downlink Shared Channel PDSCH
  • codeword CW
  • Transport Block Transport Block
  • TB transport Block
  • RS reference signal
  • antenna port e.g. demodulation reference signal (DMRS) port
  • antenna port group e.g.
  • DMRS port group groups (e.g., spatial relationship groups, Code Division Multiplexing (CDM) groups, reference signal groups, CORESET groups, Physical Uplink Control Channel (PUCCH) groups, PUCCH resource groups), resources (e.g., reference signal resources, 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 Unified TCI state, common TCI state, quasi-co-location (QCL), QCL assumption, etc. may be read interchangeably.
  • groups e.g., spatial relationship groups, Code Division Multiplexing (CDM) groups, reference signal groups, CORESET groups, Physical Uplink Control Channel (PUCCH) groups, PUCCH resource groups
  • resources e.g., reference signal resources, SRS resource
  • resource set for example, reference signal resource set
  • CORESET pool downlink Transmission Configuration Indication state (TCI state) (DL TCI state), up
  • the SSB/CSI-RS index/indicator, beam index, and TCI state may be read interchangeably.
  • RACH resource, RA resource, PRACH preamble, occasion, RACH occasion (RO), PRACH occasion, repetition resource, repetition configuration resource, resource configured for RO/repetition, time instance and frequency instance, time Resources and frequency resources, RO/preamble resources, and repetition may be read interchangeably.
  • period, period, frame, subframe, slot, symbol, occasion, and RO 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, and Msg1 may be read interchangeably.
  • the response to PRACH, the base station response to RAR, Msg2, MsgB, Msg4, and BFR, and the DCI that schedules the response may be read interchangeably.
  • transmissions other than PRACH in the random access procedure, Msg3, PUSCH scheduled by RAR, HARQ-ACK/PUCCH for Msg4, and MsgA PUSCH may be interchanged.
  • Msg3, PUSCH scheduled by RAR UL grant, and RRC connection request may be interchanged.
  • Msg4 contention resolution, RRC connection setup, and PDSCH with UE contention resolution identity may be interchanged.
  • beam, SSB, and SSB index may be read interchangeably.
  • the DL path loss reference, PL-RS, SSB, and CSI-RS may be read interchangeably.
  • repeat period repeat configuration period
  • repeat period repeat period
  • repeat cycle repeat cycle
  • a random access (RA) procedure CFRA/CBRA, 4-step RACH/2-step RACH, a specific type of random access procedure, a random access procedure using a specific PRACH format, a random access procedure initiated by a PDCCH order.
  • a random access procedure not initiated by a PDCCH order and a random access procedure initiated by an upper layer may be interchanged.
  • Each embodiment may assume the following cases 1 and 2 (case 1 and case 2 described above).
  • [Case 1] One RAR may be sent for multiple repetitions of Msg1 (FIG. 4A).
  • [Case 2] One RAR may be sent for each iteration of multiple iterations of Msg1 (FIG. 4B).
  • the UE may transmit first capability information regarding the repeat capability of Msg1 and second capability information regarding the repeat capability of Msg3. Based on the first capability information and the second capability information, the UE performs a first random access procedure including repeating Msg1 and repeating Msg3, or performs a first random access procedure including repeating Message 1 and repeating Message 3. It may be determined whether to perform a second random access procedure that does not include at least one.
  • the type of RACH resource may be at least one of the following types. - One or more sets of RACH resources for RACH procedures without Msg1 or Msg3 repetitions. - One or more sets of RACH resources for RACH procedures with Msg3 repetitions and without Msg1 repetitions. - One or more sets of RACH resources for RACH procedures with Msg1 repetitions and without Msg3 repetitions.
  • the number of Msg1/Msg3 repetitions may be different between multiple sets of RACH resources for RACH procedures with Msg1/Msg3 repetitions.
  • Example 1 It may be specified that the UE is not assumed to report Msg1 repeat capability and Msg3 repeat capability at the same time.
  • a UE that reports both Msg1 repetition capability and Msg3 repetition capability determines whether to perform only Msg1 repetition or only Msg3 repetition within one RACH procedure based on a certain condition.
  • the condition may be an RSRP condition of SSB.
  • the UE may follow at least one of the following several UE actions:
  • range 1 If the RSRP of the selected SSB is within range 1, the UE determines that only Msg1 repetitions are applied for subsequent RACH procedures.
  • range 1 may have an RSRP of at least one of smaller than threshold 1 and larger than threshold 2.
  • range 2 If the RSRP of the selected SSB is within range 2, the UE determines that only Msg3 repetitions are applied for subsequent RACH procedures.
  • range 2 may have an RSRP of at least one of smaller than threshold 3 and larger than threshold 4.
  • range 3 If the RSRP of the selected SSB is within range 3, the UE determines that neither Msg1 nor Msg3 repetitions are applied for subsequent RACH procedures.
  • range 3 may be that the RSRP is greater than threshold 5.
  • - Range 1/2/3/threshold 1/2/3/4/5 may be defined in the specification or may be indicated by the base station via the PBCH/SIB1 PDSCH/RRC IE.
  • FIG. 5 shows an example of the RACH procedure for RSRP with DL path loss reference according to embodiment #1a-1.
  • Rel. 16 UEs with two-step RACH capability apply two-step RACH if RSRP is greater than or equal to rsrp-ThresholdMsgA.
  • Rel. 16 UEs with 2-step RACH capability apply 4-step RACH if RSRP is lower than rsrp-ThresholdMsgA.
  • RA resources for 2-step RACH and 4-step RACH may be selected from pool #1.
  • a UE with a capability of 17 Msg3 repetitions applies a 4-step RACH without Msg3 repetitions if the RSRP is above the threshold rsrp-ThresholdMsg3, and 4 steps with Msg3 repetitions if the RSRP is lower than the threshold rsrp-ThresholdMsg3.
  • RA resources for 2-step RACH, 4-step RACH without Msg3 repetition may be selected from pool #1.
  • RA resources for 4-step RACH with Msg3 repetition may be selected from pool #2.
  • a UE with a capability of 18 Msg1 repetitions applies a 4-step RACH without Msg1 repetitions if the RSRP is above the threshold rsrp-ThresholdMsg1 and 4 steps with Msg1 repetitions if the RSRP is lower than the threshold rsrp-ThresholdMsg1.
  • Step RACH may be applied.
  • RA resources for 2-step RACH, 4-step RACH without Msg1 repetition may be selected from pool #1.
  • RA resources for 4-step RACH with Msg1 repetition may be selected from pool #3.
  • a UE that supports Msg1 repetition and Msg3 repetition may apply 2-step RACH if RSRP is greater than or equal to rsrp-ThresholdMsgA. If RSRP is lower than rsrp-ThresholdMsgA and greater than or equal to threshold rsrp-ThresholdMsg3, the UE may apply 4-step RACH without Msg1 or Msg3 repetitions. If the RSRP is lower than the threshold rsrp-ThresholdMsg3 and greater than or equal to the threshold rsrp-ThresholdMsg1, the UE may apply 4-step RACH with Msg3 repetitions and without Msg1 repetitions.
  • the UE may apply 4-step RACH with Msg1 repetitions and without Msg3 repetitions.
  • RA resources for 2-step RACH, 4-step RACH without Msg1 repetition and Msg3 repetition may be selected from pool #1.
  • RA resources for 4-step RACH with Msg3 repetitions and without Msg1 repetitions may be selected from pool #2.
  • RA resources for 4-step RACH with Msg1 repetition and without Msg3 repetition may be selected from pool #3.
  • the type of RACH resource may be at least one of the following types. - One or more sets of RACH resources for RACH procedures without Msg1 or Msg3 repetitions. - One or more sets of RACH resources for RACH procedures with Msg3 repetitions and without Msg1 repetitions. - One or more sets of RACH resources for RACH procedures with Msg1 repetitions and without Msg3 repetitions. - One or more sets of RACH resources for RACH procedures with both Msg1 and Msg3 repetitions.
  • the number of Msg1/Msg3 repetitions may be different between multiple sets of RACH resources for RACH procedures with Msg1/Msg3 repetitions.
  • UE behavior may be based on certain conditions.
  • the condition may be an RSRP condition of SSB.
  • Each UE operation may correspond to a range of SSB RSRPs.
  • the condition may be at least one of SSB RSRP being equal to or greater than threshold 1 and lower than threshold 2.
  • Threshold 1 may be rsrp-Threshold-NoRep.
  • the condition may be at least one of the following: the SSB RSRP is equal to or greater than the threshold value 3, or lower than the threshold value 4.
  • Threshold 3 may be rsrp-Threshold-NoRep.
  • Threshold 4 may be rsrp-ThresholdMsg3.
  • the condition may be at least one of SSB RSRP being equal to or greater than the threshold value 5 and lower than the threshold value 6.
  • Threshold 6 may be rsrp-ThresholdMsg1.
  • the threshold values 1/2/3/4/5/6 may be defined in the specifications or may be instructed by the base station via the PBCH/SIB1 PDSCH/RRC IE.
  • Each UE operation may correspond to a range of SSB RSRPs.
  • the condition may be at least one of SSB RSRP being equal to or greater than threshold 1 and lower than threshold 2.
  • Threshold 1 may be rsrp-ThresholdMsg3.
  • the condition may be at least one of SSB RSRP being equal to or greater than the threshold value 5 and lower than the threshold value 6.
  • Threshold 5 may be rsrp-ThresholdMsg1.
  • Threshold 6 may be rsrp-ThresholdMsg3.
  • Msg1 repeats are applied.
  • the condition may be at least one of the following: the SSB RSRP is equal to or greater than the threshold value 3, or lower than the threshold value 4.
  • Threshold 3 may be rsrp-ThresholdMsg3.
  • Threshold 4 may be rsrp-ThresholdMsg1.
  • the condition may be at least one of the following: the SSB RSRP is equal to or greater than the threshold value 7, or lower than the threshold value 8.
  • the threshold 8 may be rsrp-ThresholdMsg1Msg3.
  • the threshold values 1/2/3/4/5/6/7/8 may be defined in the specifications, or may be instructed by the base station via the PBCH/SIB1 PDSCH/RRC IE.
  • Msg3 becomes more of a bottleneck than Msg1. Therefore, if Msg1 repeats are required, it is preferred that Msg3 repeats are also required. This makes Example 1 more preferred than Example 2.
  • FIG. 6 shows an example of the RACH procedure for RSRP with DL path loss reference according to Example 1 of Embodiment #1a-2.
  • a UE that supports Msg1 repetition and Msg3 repetition may apply 2-step RACH if RSRP is greater than or equal to rsrp-ThresholdMsgA. If RSRP is lower than rsrp-ThresholdMsgA and greater than or equal to threshold rsrp-ThresholdMsg3, the UE may apply 4-step RACH without Msg1 or Msg3 repetitions. If the RSRP is lower than the threshold rsrp-ThresholdMsg3 and greater than or equal to the threshold rsrp-ThresholdMsg1, the UE may apply 4-step RACH with Msg3 repetitions and without Msg1 repetitions.
  • the UE may apply 4-step RACH with Msg1 and Msg3 repetitions.
  • RA resources for 2-step RACH, 4-step RACH without Msg1 repetition and Msg3 repetition may be selected from pool #1.
  • RA resources for 4-step RACH with Msg3 repetitions and without Msg1 repetitions may be selected from pool #2.
  • RA resources for 4-step RACH with Msg1 repeat and Msg3 repeat may be selected from pool #3.
  • FIG. 7 shows an example of the RACH procedure for RSRP with DL path loss reference according to Example 2 of Embodiment #1a-2.
  • a UE that supports Msg1 repetition and Msg3 repetition may apply 2-step RACH if RSRP is greater than or equal to rsrp-ThresholdMsgA. If RSRP is lower than rsrp-ThresholdMsgA and greater than or equal to threshold rsrp-ThresholdMsg3, the UE may apply 4-step RACH without Msg1 or Msg3 repetitions. If the RSRP is lower than the threshold rsrp-ThresholdMsg3 and greater than or equal to the threshold rsrp-ThresholdMsg1, the UE may apply 4-step RACH with Msg3 repetitions and without Msg1 repetitions.
  • the UE may apply 4-step RACH with Msg1 repetitions and without Msg3 repetitions. If the RSRP is lower than the threshold rsrp-ThresholdMsg1Msg3, the UE may apply 4-step RACH with Msg1 and Msg3 repetitions.
  • RA resources for 2-step RACH, 4-step RACH without Msg1 repetition and Msg3 repetition may be selected from pool #1.
  • RA resources for 4-step RACH with Msg3 repetitions and without Msg1 repetitions may be selected from pool #2.
  • RA resources for 4-step RACH with Msg1 repetition and without Msg3 repetition may be selected from pool #3.
  • RA resources for 4-step RACH with Msg1 repeat and Msg3 repeat may be selected from pool #4.
  • a UE reporting Msg1 repetition capability may be defined as having Msg3 repetition capability.
  • the type of RACH resource may be at least one of the following types. - One or more sets of RACH resources for RACH procedures without Msg1 or Msg3 repetitions. - One or more sets of RACH resources for RACH procedures with Msg3 repetitions and without Msg1 repetitions. - One or more sets of RACH resources for RACH procedures with both Msg1 and Msg3 repetitions.
  • the number of Msg1/Msg3 repetitions may be different between multiple sets of RACH resources for RACH procedures with Msg1/Msg3 repetitions.
  • UE behavior may be based on certain conditions.
  • the condition may be an RSRP condition of SSB.
  • Each UE operation may correspond to a range of SSB RSRP.
  • the condition may be at least one of SSB RSRP being equal to or greater than threshold 1 and lower than threshold 2.
  • Threshold 1 may be rsrp-Threshold-NoRep.
  • the condition may be at least one of the following: the SSB RSRP is equal to or greater than the threshold value 3, or lower than the threshold value 4.
  • Threshold 3 may be rsrp-Threshold-NoRep.
  • Threshold 4 may be rsrp-ThresholdMsg3.
  • the condition may be at least one of SSB RSRP being equal to or greater than the threshold value 5 and lower than the threshold value 6.
  • Threshold 6 may be rsrp-ThresholdMsg1.
  • the threshold values 1/2/3/4/5/6 may be defined in the specifications or may be instructed by the base station via the PBCH/SIB1 PDSCH/RRC IE.
  • a UE that supports Msg1 repetition and Msg3 repetition may apply 2-step RACH if RSRP is greater than or equal to rsrp-ThresholdMsgA. If RSRP is lower than rsrp-ThresholdMsgA and greater than or equal to threshold rsrp-ThresholdMsg3, the UE may apply 4-step RACH without Msg1 or Msg3 repetitions. If the RSRP is lower than the threshold rsrp-ThresholdMsg3 and greater than or equal to the threshold rsrp-ThresholdMsg1, the UE may apply 4-step RACH with Msg3 repetitions and without Msg1 repetitions.
  • Embodiment #1a-4 ⁇ Some of embodiments #1a-1 to #1a-3 may be combined. Embodiment #1a-2/#1a-3 may be applied when at least one of the following application conditions is met.
  • the applicable conditions are applicable condition 1 and applicable condition 4.
  • the applicable conditions are applicable condition 2 and applicable condition 3.
  • the UE can appropriately determine the repetition of Msg1/Msg3.
  • ⁇ Embodiment #1b ⁇ There is a trade-off between the number of PRACH repetitions and the number of resources for PRACH. It is preferable for the base station to be able to control at least one of whether PRACH repetitions are performed and the maximum number of PRACH repetitions.
  • the UE may receive settings/instructions regarding information regarding whether to perform PRACH repetition.
  • the information regarding whether to perform PRACH repetition may be at least one of the following information.
  • the information indicates whether to turn on or turn off the PRACH repeat function. That information may be implied based on another setting. For example, the RO/RA resource configuration may imply whether PRACH repetition is on or off. For example, the presence or absence of a configuration regarding the RSRP threshold may imply whether PRACH repetition is turned on or off.
  • the information indicates the number of PRACH repetitions.
  • the candidate value may include at least one of ⁇ 1, 2, 4, 8, 16, 32 ⁇ .
  • a value of 1 may be equivalent to turning off PRACH repetition.
  • the information may be an RSRP threshold.
  • the RSRP threshold for determining whether to perform PRACH repetition may be defined for each entry. For example, if the RSRP threshold is a sufficiently small value (eg - ⁇ ), the UE behavior may be that no PRACH repetition occurs. For example, if the RSRP threshold is a small value, the UE behavior may be that fewer UEs perform PRACH repetitions. For example, if the RSRP threshold is a large value, the UE behavior may be that more UEs perform PRACH repetitions. For example, if the RSRP threshold is a sufficiently large value, the UE behavior may be that more UEs perform PRACH repetitions.
  • the RSRP threshold may be defined in the specification, set by RRC, or indicated via MAC CE/DCI.
  • Information regarding whether to perform PRACH repetition may be configured/instructed by at least one of the following several configuration/instruction methods.
  • Combinations of some of these settings/instruction methods may be supported.
  • the information is configured via the SIB1 PDSCH and RRC IE.
  • the bit width of the setting/instruction may differ between different setting/instruction methods. For example, 1 bit may be used in setting/instruction method 1 and 2 bits may be used in setting/instruction method 2.
  • At least configuration/instruction method 1 is supported to support PRACH repetition during initial access.
  • Setting/instructing information regarding whether to perform PRACH repetition may require that at least one of the following several requirements be met.
  • the UE can appropriately determine the repetition of Msg1/Msg3.
  • the UE may receive information regarding the first random access procedure including the repetition of Msg1. Based on the information, the UE uses a first random access resource for the first random access procedure, and uses a second random access resource different from the first random access resource to perform a second random access procedure that does not include the repetition of Msg1. May be used for access procedures.
  • ⁇ Embodiment #Xa ⁇ PRACH repetition may be performed only within specific RA resources.
  • the specific RA resource may be at least one of the following several RA resources.
  • RA resource 4 Some combinations of RA resources 1 to 3. RA resource 1+RA resource 3, or RA resource 2+RA resource 3.
  • the PRACH (Msg1) repeat may follow at least one of several PRACH repeat definitions: [PRACH Repetition Definition 1] Multiple PRACH transmissions with the same beam. [PRACH Repetition Definition 2] Multiple PRACH transmissions with different beams. [PRACH Repetition Definition 3] Multiple PRACH transmissions (with the same beam or different beams) before expiration of the RAR window. [PRACH Repetition Definition 4] Multiple PRACH transmissions including the first PRACH transmission. [PRACH repetition definition 5] Multiple PRACH transmissions that do not include the first PRACH transmission. In this case, the first PRACH transmission is Rel. It may be transmitted using the same RA resource as the RA resource for 15/16 PRACH transmission. Subsequent PRACH transmissions may be transmitted within the RA resources in embodiment #Xa-1.
  • the RA resource, PRACH preamble, and PRACH preamble index may be read interchangeably.
  • ⁇ Embodiment #Xa-3 ⁇ RA resources for PRACH repetition may follow at least one of several partitioning methods:
  • RA resource 1 It may be assumed that the above-mentioned RA resource 1 is applied. At least one of the following several RA resource configurations may be configured for RA resources for which at least Msg3 repeats are available: [[RA resource setting 1-1]] Number of preamble indexes available for PRACH repetition. If there is only a configuration for the number of preamble indexes, the first preamble index available for PRACH repetition may be determined for each specific rule. For example, the first preamble index may be the first preamble index configured with Msg3 repetition. All available preamble indexes configured for PRACH repetition may be accommodated in the preamble index applicable to Msg3 repetition starting from the determined preamble index.
  • the RA resources for PRACH repetition may be RA resources other than RA resources in which none of the functions of Msg3 repetition, RedCap, RAN slicing, and SDT are available.
  • RA resource 3 It may be assumed that the above-mentioned RA resource 3 is applied. At least one of the following several RA resource configurations may be configured for RA resources for which at least Msg3 repeats are available: [[RA Resource Settings 3-1]] First preamble index available for PRACH repetition. [[RA resource setting 3-2]] Number of preamble indexes available for PRACH repetition.
  • ⁇ Embodiment #Xb ⁇ PRACH repetition may be performed only within a specific RACH occasion (RO).
  • the specific RO may be at least one of the following several ROs.
  • a PRACH repetition may follow at least one of several PRACH repetition definitions: [PRACH Repetition Definition 1] Multiple PRACH transmissions with the same beam. [PRACH Repetition Definition 2] Multiple PRACH transmissions with different beams. [PRACH Repetition Definition 3] Multiple PRACH transmissions (with the same beam or different beams) before expiration of the RAR window. [PRACH Repetition Definition 4] Multiple PRACH transmissions including the first PRACH transmission. [PRACH repetition definition 5] Multiple PRACH transmissions that do not include the first PRACH transmission. In this case, the first PRACH transmission is Rel. It may be transmitted using the same RA resource as the RA resource for 15/16 PRACH transmission. Subsequent PRACH transmissions may be transmitted within the RO in embodiment #Xb-1.
  • the RO for PRACH repetition may follow at least one of several partitioning methods:
  • the mask index constraints/extensions may be subject to at least one of the following several constraints/extensions.
  • the available PRACH mask index entries may be expanded based on at least one of several expansion methods below.
  • [Extension method 1] Add an entry for PRACH occasion index X.
  • X may be an integer greater than 8.
  • Extension method 2 Adding entries for the first/second/third/.../Xth PRACH occasion in the X PRACH occasions.
  • X may be an integer greater than 2.
  • X may be 3, 4, or 5.
  • bit width for PRACH mask index configuration may be expanded to cover more than 16 entries.
  • the UE can appropriately determine RACH resources for PRACH repetition.
  • the UE may receive information regarding a random access procedure including multiple repetitions of Msg1 and multiple repetitions of Msg3.
  • the UE may determine one or more second beams to be used for the plurality of repetitions of the Msg3 based on the one or more first beams to be used for the plurality of repetitions of the Msg1 based on the information. good.
  • the transmission beam of the Msg3 repetition may depend on at least one beam of the Msg1 repetition and the detected RAR.
  • the transmission beam for Msg3 repetition may be any of the following several transmission beams.
  • the same beam for all Msg3 repetitions may be determined by the beam of Msg1 repetition.
  • the beam for Msg3 repetitions may be the same as the beam for Msg1 repetitions ( Figure 11).
  • the beam of Msg3 repetition may follow the beam of the first/last/random Msg1 repetition. In the example of FIG. 12, the four repetitions of Msg3 use the beam used in the first repetition of the four repetitions of Msg1.
  • the same beam for all Msg3 repetitions may be determined by the detected RAR.
  • the beam may be determined by explicit instructions within the RAR. One field within the RAR may direct the beam for Msg3 repetitions. It may be specified that the UE assumes that its indicated beam is obtained from Msg1 repeat beams. In the example of FIG. 13, the RAR indicates the beam used for four repetitions of Msg3. That beam is the one used in one of the four iterations of Msg1.
  • the beam may be determined by an implicit indication such as RA-RNTI. For example, the beam may be determined by the RO corresponding to the RA-RNTI used for the detected RAR.
  • the beams of multiple Msg3 repetitions may be determined by the beams of Msg1 repetitions. If the Msg1 repeats use different beams, the Msg3 repeat beams may follow the Msg1 repeat beams. - Example: If the number of Msg1 repeats is equal to the number of Msg3 repeats, the mapping between the beams of Msg1 repeats and the beams of Msg3 repeats may be a one-to-one mapping. In the example of FIG. 14, the four beams used for the four repetitions of Msg3 are the four beams used for the four repetitions of Msg1.
  • the mapping of multiple Msg1 repeat beams and multiple Msg3 repeat beams may be sequential mapping or cyclic mapping.
  • the two beams used for the two repetitions of Msg1 are cyclically applied to the four beams used for the four repetitions of Msg3 (cyclic mapping).
  • each beam used in the two repetitions of Msg1 is applied twice in succession to the four beams used in the four repetitions of Msg3 (sequential mapping).
  • the beam of N Msg3 repeats may be a beam of N Msg1 repeats from the beginning/from the end/randomly.
  • the two beams used for the two repetitions of Msg3 are the two beams used for the first two of the four repetitions of Msg1.
  • the beam of multiple Msg3 repetitions may be determined by the detected RAR.
  • the beam may be determined by explicit instructions within the RAR. It may be specified that the UE assumes that its indicated beam is obtained from Msg1 repeat beams.
  • the beam of multiple repetitions for Msg3 may depend on at least one of the beams of the corresponding Msg1 repetition, the corresponding RAR, and all Msg1 repetitions.
  • the UE may follow at least one of the following several actions. - The UE does not assume different repetition numbers for multiple Msg3PUSCHs. - The UE does not assume that the total number of repetitions for multiple Msg3PUSCHs exceeds a certain value. - The UE does not assume that any previous repetition of Msg3PUSCH will collide with any subsequent repetition of Msg3PUSCH. - The UE does not assume that any previous Msg3PUSCH repetition starts/ends later than any subsequent Msg3PUSCH repetition.
  • the transmission beam for Msg3 repetition may be any of the following several transmission beams.
  • the beam of Msg3 repetition may be the same as transmit beam 2-1A.
  • the beam of Msg3 repetition may follow the beam of the first/last/random Msg1 repetition.
  • Transmission beam 2-2 A different beam may be used for every Msg3 repetition.
  • the beams of multiple Msg3 repetitions may be determined by the beams of all Msg1 repetitions. If the Msg1 repeats use different beams, the Msg3 repeat beams may follow the Msg1 repeat beams. - Example: If the number of Msg1 repeats is equal to the number of Msg3 repeats, the mapping between the beams of Msg1 repeats and the beams of Msg3 repeats may be a one-to-one mapping. - Example: If the number of Msg1 repeats is less than the number of Msg3 repeats, the mapping of multiple Msg1 repeat beams and multiple Msg3 repeat beams may be sequential mapping or cyclic mapping.
  • the two beams used for the two repetitions of Msg1 are cyclically applied to the four beams used for the four repetitions of Msg3 (cyclic mapping).
  • each beam used in the two repetitions of Msg1 is applied twice in succession to the four beams used in the four repetitions of Msg3 (sequential mapping).
  • the beam of N Msg3 repeats may be a beam of N Msg1 repeats from the beginning/from the end/randomly.
  • the beams of multiple Msg3 repetitions may be determined by the corresponding RAR.
  • the beam may be determined by explicit instructions within the RAR.
  • One field within the RAR may direct one or more beams for Msg3 repetitions. It may be specified that the UE assumes that its indicated beam is obtained from Msg1 repeat beams.
  • the UE when performing Msg1 repetition and Msg3 repetition, the UE can appropriately determine the beam for Msg3 repetition.
  • the UE may receive instruction information regarding the number of repetitions of Msg3.
  • the UE may determine the number of repetitions of Msg3 based on the instruction information and information regarding the repetition of Msg1 within a random access procedure including the repetition of Msg3.
  • the interpretation of the number of Msg3 repeats indicated by RAR is Rel. You may follow the 17 rules. That is, two bits from the MCS field may be reused for its interpretation based on the four candidate values. In the example of FIG. 22A, two bits from the MCS field indicate one value out of four candidate values for the number of Msg3 repeats.
  • At least one of the number of bits of the indication and the candidate value for the number of Msg3 repetitions indicated by the RAR is Rel. It may be different from the 17 rules.
  • X bits from the MCS field may be used to indicate one value from up to 2X candidate values for the number of Msg3 repeats. X may be equal to 2, less than 2, or more than 2. Up to 2X candidate values may be defined in the specification or configured by the PBCH/SIB1 PDSCH/RRC IE. Candidate values do not have to exceed upper limits such as 4/8/16/32/64.
  • two bits from the MCS field indicate one value out of four candidate values for the number of Msg3 repeats.
  • one bit from the MCS field indicates one value from two candidate values for the number of Msg3 repeats.
  • the value/range of the required number of Msg3 repeats is Rel.
  • the value may be greater than 17. Therefore, for the case with Msg1 repetition, the value defined/set for the number of Msg3 repetitions may be different from the value for the case without Msg1 repetition.
  • At least one of the number of bits of the indication and the candidate value for the number of Msg3 repeats is RAR for only one Msg1 repeat for multiple Msg1 repeats. may be different between the case where RARs are sent (case 1) and the case where multiple RARs are sent for multiple Msg1 repetitions (case 2).
  • RAR For example, if only one RAR is sent for multiple Msg1 repetitions (case 1), then It may be used for instructions.
  • X may be equal to 2, less than 2, or more than 2.
  • Up to 2X candidate values may be defined in the specification or configured by the PBCH/SIB1 PDSCH/RRC IE. Up to 2X candidate values are Rel. It may be the same as the candidate value set for a UE that supports 17 Msg3 repetitions. Candidate values do not have to exceed upper limits such as 4/8/16/32/64.
  • a new field of X bits in the RAR may be used to indicate one value from up to 2X candidate values for the number of Msg3 repeats.
  • the Y bits from the MCS field are 2 times the number of Msg3 repetitions, indicating one value from up to Y candidate values. May be used for. Y may be equal to 2, less than 2, or more than 2.
  • Up to 2 Y candidate values may be defined in the specification or configured by the PBCH/SIB1 PDSCH/RRC IE.
  • Up to 2X candidate values are Rel. It may be the same as the candidate value set for a UE that supports 17 Msg3 repetitions. Candidate values do not have to exceed upper limits such as 4/8/16/32/64.
  • a new field of Y bits in the RAR may be used to indicate one value from up to 2 Y candidate values for the number of Msg3 repeats.
  • Two bits from the MCS field in the first RAR may be used to indicate one value from up to four candidate values for the number of Msg3 repeats (similar to Rel.17).
  • a new field of Y bits in the second and subsequent RARs may be used to indicate one value from up to 2 Y candidate values for the number of Msg3 repeats.
  • the interpretation of the number of Msg3 repetitions indicated by the RAR may depend on the number of Msg1 repetitions within the current RACH procedure. For example, if the base station can know the number of Msg1 repetitions, the RACH resource pool may be associated with the number of Msg1 repetitions, or there is only one number of repetitions for Msg1. It may be a case.
  • At least one of the number of indication bits and the candidate value for the number of Msg3 repetitions is different between cases of different numbers of Msg1 repetitions. Good too.
  • X bits from the MCS field may be used to indicate one value from up to 2X candidate values for the number of Msg3 repetitions.
  • X may be equal to 2, less than 2, or more than 2.
  • Up to 2X candidate values may be defined in the specification or configured by the PBCH/SIB1 PDSCH/RRC IE.
  • Up to 2X candidate values are Rel. It may be the same as the candidate value set for a UE that supports 17 Msg3 repetitions. Candidate values do not have to exceed upper limits such as 4/8/16/32/64.
  • a new field of X bits in the RAR may be used to indicate one value from up to 2X candidate values for the number of Msg3 repeats.
  • Two bits from the MCS field in the first RAR may be used to indicate one value from up to four candidate values for the number of Msg3 repeats (similar to Rel.17).
  • a new field of X bits in the second and subsequent RARs may be used to indicate one value from up to 2X candidate values for the number of Msg3 repeats.
  • Y bits from the MCS field may be used to indicate one value from up to 2 Y candidate values for the number of Msg3 repetitions.
  • Y may be equal to 2, less than 2, or more than 2.
  • Up to 2 Y candidate values may be defined in the specification or configured by the PBCH/SIB1 PDSCH/RRC IE.
  • Up to 2X candidate values are Rel. It may be the same as the candidate value set for a UE that supports 17 Msg3 repetitions. Candidate values do not have to exceed upper limits such as 4/8/16/32/64.
  • a new field of Y bits in the RAR may be used to indicate one value from up to 2 Y candidate values for the number of Msg3 repeats.
  • Two bits from the MCS field in the first RAR may be used to indicate one value from up to four candidate values for the number of Msg3 repeats (similar to Rel.17).
  • a new field of Y bits in the second and subsequent RARs may be used to indicate one value from up to 2 Y candidate values for the number of Msg3 repeats.
  • At least one of the number of bits of the indication and the candidate value for the number of Msg3 repetitions is the case where multiple Msg1 repetitions use the same beam;
  • the Msg1 repetitions may differ between cases using different beams.
  • X bits from the MCS field may be used to indicate one value from up to 2X candidate values for the number of Msg3 repetitions.
  • X may be equal to 2, less than 2, or more than 2.
  • Up to 2X candidate values may be defined in the specification or configured by the PBCH/SIB1 PDSCH/RRC IE.
  • Up to 2X candidate values are Rel. It may be the same as the candidate value set for a UE that supports 17 Msg3 repetitions. Candidate values do not have to exceed upper limits such as 4/8/16/32/64.
  • a new field of X bits in the RAR may be used to indicate one value from up to 2X candidate values for the number of Msg3 repeats.
  • Two bits from the MCS field in the first RAR may be used to indicate one value from up to four candidate values for the number of Msg3 repeats (similar to Rel.17).
  • a new field of X bits in the second and subsequent RARs may be used to indicate one value from up to 2X candidate values for the number of Msg3 repeats.
  • Y bits from the MCS field may be used to indicate one value from up to 2 Y candidate values for the number of Msg3 repetitions.
  • Y may be equal to 2, less than 2, or more than 2.
  • Up to 2 Y candidate values may be defined in the specification or configured by the PBCH/SIB1 PDSCH/RRC IE.
  • Up to 2X candidate values are Rel. It may be the same as the candidate value set for a UE that supports 17 Msg3 repetitions. Candidate values do not have to exceed upper limits such as 4/8/16/32/64.
  • a new field of Y bits in the RAR may be used to indicate one value from up to 2 Y candidate values for the number of Msg3 repeats.
  • Two bits from the MCS field in the first RAR may be used to indicate one value from up to four candidate values for the number of Msg3 repeats (similar to Rel.17).
  • a new field of Y bits in the second and subsequent RARs may be used to indicate one value from up to 2 Y candidate values for the number of Msg3 repeats.
  • ⁇ Embodiment #3-5 Interpretation of the number of Msg3 repeats indicated by RAR may depend on some combination of embodiments #3-2, #3-3, #3-4. - For example, the interpretation may depend on the combination of embodiments #3-2 and #3-3. - For example, the interpretation may depend on the combination of embodiments #3-2 and #3-4. - For example, the interpretation may depend on the combination of embodiments #3-3 and #3-4. - For example, the interpretation may depend on the combination of embodiments #3-2, #3-3, and #3-4.
  • the UE can appropriately determine the number of repetitions of Msg3.
  • ⁇ Supplement> The operations of at least one of the embodiments described above may apply only to UEs that have reported or support a particular UE capability.
  • the particular UE capability may indicate at least one of the following: - Supporting specific processing/operation/control/information for at least one of the above embodiments. - Support simultaneous Msg1 repetition and Msg3 repetition (combination/joint operation of Msg1 repetition and Msg3 repetition). - Support both Msg1 and Msg3 repetitions within one RACH procedure in the case where one RAR for multiple Msg1 repetitions is sent (case 1). - Supporting both Msg1 and Msg3 repetitions within one RACH procedure in the case where multiple RARs for multiple Msg1 repetitions are sent (Case 2).
  • the above-mentioned specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (for example, cell, band, BWP). , capability for each frequency range (for example, Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or for each subcarrier spacing (SCS). It may be the ability of
  • the above-mentioned specific UE capability may be a capability that is applied across all duplex schemes (commonly regardless of the duplex scheme), or may be a capability that is applied across all duplex schemes (for example, Time Division Duplex).
  • the capability may be for each frequency division duplex (TDD)) or frequency division duplex (FDD)).
  • the UE is configured with specific information related to the above-described embodiments by upper layer signaling.
  • the specific information may be information indicating enabling at least one operation of the embodiments described above, any RRC parameters for a specific release (eg, Rel. 18), and the like.
  • the UE does not support at least one operation of the specific UE capabilities or is not configured with the specific information, for example, Rel. 15/16/17 operations may be applied.
  • a transmitter that transmits first capability information regarding the ability to repeat message 1 and second capability information regarding the ability to repeat message 3; Based on the first capability information and the second capability information, a first random access procedure including repeating the message 1 and repeating the message 3 is performed, or at least repeating the message 1 and repeating the message 3.
  • a control unit that determines whether to perform a second random access procedure that does not include one.
  • the information includes at least one of a number of preamble indexes for the first random access resource and a first preamble index for the first random access resource.
  • Supplementary Note 1 wherein the control unit uses a first random access channel occasion for the first random access procedure, and uses a second random access channel occasion different from the first random access channel occasion for the second random access procedure. Or the terminal described in Appendix 2.
  • the control unit determines a first random access channel occasion for the first random access procedure based on at least one of a mask index and a second random access channel occasion for the second random access procedure.
  • the terminal according to any one of Supplementary Notes 1 to 3 to be determined.
  • a terminal comprising: a control unit that determines the number of repetitions of the message 3 based on the instruction information and information regarding the repetition of the message 1 in a random access procedure including the repetition of the message 3.
  • the terminal according to supplementary note 1 wherein the information relates to the number of repetitions of the message 1.
  • wireless communication system The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below.
  • communication is performed using any one or a combination of the wireless communication methods according to the above-described embodiments of the present disclosure.
  • FIG. 23 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an 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 support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)).
  • MR-DC has dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), and dual connectivity between NR and LTE (NR-E -UTRA Dual Connectivity (NE-DC)).
  • RATs Radio Access Technologies
  • MR-DC has dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), and dual connectivity between NR and LTE (NR-E -UTRA Dual Connectivity (NE-DC)).
  • E-UTRA 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 (Master Node (MN)), and the NR base station (gNB) is the secondary node (Secondary Node (SN)).
  • the NR base station (gNB) is the MN
  • 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) where both the MN and SN are NR base stations (gNB)). )) may be supported.
  • dual connectivity NR-NR Dual Connectivity (NN-DC) where both the MN and SN are NR base stations (gNB)).
  • the wireless communication system 1 includes a base station 11 that forms a macro cell C1 with relatively wide coverage, and base stations 12 (12a-12c) that are located within the macro cell C1 and form a small cell C2 that is narrower than the macro cell C1. You may prepare.
  • User terminal 20 may be located within at least one cell. The arrangement, number, etc. of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.
  • the user terminal 20 may be connected to at least one of the plurality of base stations 10.
  • the user terminal 20 may use at least one of carrier aggregation (CA) using a plurality of component carriers (CC) and dual connectivity (DC).
  • CA carrier aggregation
  • CC component carriers
  • DC dual connectivity
  • Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)).
  • Macro cell C1 may be included in FR1
  • 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 FR1 may correspond to a higher frequency band than FR2, for example.
  • 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
  • the plurality of base stations 10 may be connected by wire (for example, optical fiber, X2 interface, etc. compliant with Common Public Radio Interface (CPRI)) or wirelessly (for example, NR communication).
  • wire for example, optical fiber, X2 interface, etc. compliant with Common Public Radio Interface (CPRI)
  • NR communication for example, when NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is an upper station, is an Integrated Access Backhaul (IAB) donor, and base station 12, which is a relay station, is an IAB donor. May also be called a node.
  • IAB Integrated Access Backhaul
  • the base station 10 may be connected to the core network 30 via another base station 10 or directly.
  • 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 systems such as LTE, LTE-A, and 5G.
  • an orthogonal frequency division multiplexing (OFDM)-based wireless access method 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 wireless access method may also be called a waveform.
  • other wireless access methods for example, other single carrier transmission methods, other multicarrier transmission methods
  • the UL and DL radio access methods may be used as the UL and DL radio access methods.
  • the downlink channels include a physical downlink shared channel (PDSCH) shared by each user terminal 20, a broadcast channel (physical broadcast channel (PBCH)), and a downlink control channel (physical downlink control). Channel (PDCCH)) or the like may be used.
  • PDSCH physical downlink shared channel
  • PBCH physical broadcast channel
  • PDCCH downlink control channel
  • uplink channels include a physical uplink shared channel (PUSCH) shared by each user terminal 20, an uplink control channel (PUCCH), and a random access channel. (Physical Random Access Channel (PRACH)) or the like may be used.
  • PUSCH physical 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, upper layer control information, etc. may be transmitted by PUSCH.
  • a Master Information Block (MIB) may be transmitted via the PBCH.
  • Lower layer control information may be transmitted by PDCCH.
  • the lower layer control information may include, for example, downlink control information (DCI) that includes scheduling information for at least one of PDSCH and PUSCH.
  • DCI downlink control information
  • DCI that schedules PDSCH may be called DL assignment, DL DCI, etc.
  • 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 (CONtrol REsource SET (CORESET)) and a search space may be used to detect the PDCCH.
  • CORESET corresponds to a resource for searching DCI.
  • the search space corresponds to a search area and a search method for PDCCH candidates (PDCCH candidates).
  • PDCCH candidates PDCCH candidates
  • One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.
  • 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.
  • the PUCCH allows channel state information (CSI), delivery confirmation information (for example, may be called Hybrid Automatic Repeat Request ACKnowledgement (HARQ-ACK), ACK/NACK, etc.), and scheduling request ( Uplink Control Information (UCI) including at least one of SR)) may be transmitted.
  • CSI channel state information
  • delivery confirmation information for example, may be called Hybrid Automatic Repeat Request ACKnowledgement (HARQ-ACK), ACK/NACK, etc.
  • UCI Uplink Control Information including at least one of SR
  • a random access preamble for establishing a connection with a cell may be transmitted by PRACH.
  • downlinks, uplinks, etc. may be expressed without adding "link”.
  • various channels may be expressed without adding "Physical” at the beginning.
  • a synchronization signal (SS), a downlink reference signal (DL-RS), and the like may be transmitted.
  • the DL-RS includes a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), and a demodulation reference signal (DeModulation).
  • Reference Signal (DMRS)), Positioning Reference Signal (PRS), Phase Tracking Reference Signal (PTRS), etc. may be transmitted.
  • the synchronization signal may be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS).
  • a signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS/PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.
  • DMRS Downlink Reference Signal
  • UL-RS uplink reference signals
  • SRS Sounding Reference Signal
  • DMRS demodulation reference signals
  • UE-specific reference signal user terminal-specific reference signal
  • FIG. 24 is a diagram illustrating an example of the configuration of a base station according to an embodiment.
  • the base station 10 includes a control section 110, a transmitting/receiving section 120, a transmitting/receiving antenna 130, and a transmission line interface 140. Note that 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 functional blocks that are characteristic 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 entire base station 10.
  • the control unit 110 can be configured from a controller, a control circuit, etc., which will be explained based on common recognition in the technical field related to the present disclosure.
  • the control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), and the like.
  • the control unit 110 may control transmission and reception, measurement, etc. using the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission path interface 140.
  • the control unit 110 may generate data, control information, a sequence, etc. to be transmitted as a signal, and may transfer the generated data to the transmitting/receiving unit 120.
  • the control unit 110 may perform communication channel call processing (setting, release, etc.), status management of the base station 10, radio resource management, 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 transmitter/receiver unit 120 includes a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitter/receiver circuit, etc., which are explained based on common understanding in the technical field related to the present disclosure. be able to.
  • the transmitting/receiving section 120 may be configured as an integrated transmitting/receiving section, or may be configured from a transmitting section and a receiving section.
  • the transmitting section may include a transmitting processing section 1211 and an RF section 122.
  • the reception section may include 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 form at least one of a transmitting beam and a receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.
  • digital beamforming e.g., precoding
  • analog beamforming e.g., phase rotation
  • the transmitting/receiving 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 transmitting/receiving unit 120 performs channel encoding (which may include error correction encoding), modulation, mapping, filter processing, and discrete Fourier transform (DFT) on the bit string to be transmitted.
  • a baseband signal may be output by performing transmission processing such as processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion.
  • IFFT Inverse Fast Fourier Transform
  • the transmitting/receiving unit 120 may perform modulation, filter processing, amplification, etc. on the baseband signal in a radio frequency band, and may transmit the signal in the radio frequency band via the transmitting/receiving antenna 130. .
  • the transmitting/receiving section 120 may perform amplification, filter processing, demodulation into a baseband signal, etc. on the radio frequency band signal received by the transmitting/receiving antenna 130.
  • the transmitting/receiving unit 120 (reception processing unit 1212) performs analog-to-digital conversion, fast Fourier transform (FFT) processing, and inverse discrete Fourier transform (IDFT) on the acquired baseband signal. )) processing (if necessary), applying reception processing such as filter processing, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing and PDCP layer processing, User data etc. may also be acquired.
  • FFT fast Fourier transform
  • IDFT inverse discrete Fourier transform
  • the transmitting/receiving unit 120 may perform measurements regarding 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 is the receiving power (for example, Reference Signal Received Power (RSRP)), Receive Quality (eg, Reference Signal Received Quality (RSRQ), Signal To InterfERENCE PLUS NOI. SE RATIO (SINR), Signal to Noise Ratio (SNR) , signal strength (for example, Received Signal Strength Indicator (RSSI)), propagation path information (for example, CSI), etc. may be measured.
  • the measurement results may be output to the control unit 110.
  • the transmission path interface 140 transmits and receives signals (backhaul signaling) between devices included in the core network 30, other base stations 10, etc., and transmits and receives user data (user plane data) for the user terminal 20, control plane It is also possible to acquire and transmit data.
  • 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 path interface 140.
  • the transmitting/receiving unit 120 may receive first ability information regarding the ability to repeat message 1 and second ability information regarding the ability to repeat message 3.
  • the control unit 110 performs a first random access procedure including repeating the message 1 and repeating the message 3 based on the first capability information and the second capability information, or performs a first random access procedure including repeating the message 1 and repeating the message 3. It may be determined whether to perform a second random access procedure that does not include at least one of the repetitions of 3.
  • the transmitting/receiving unit 120 may transmit information regarding the first random access procedure including repeating message 1. Based on the information, the control unit 110 uses a first random access resource for the first random access procedure, and uses a second random access resource different from the first random access resource that does not include repetition of the message 1. It may also be used in the second random access procedure.
  • the transmitting/receiving unit 120 may transmit information regarding a random access procedure including multiple repetitions of message 1 and multiple repetitions of message 3. Based on the information, the control unit 110 controls one or more second beams used for the plurality of repetitions of the message 3 based on the one or more first beams used for the plurality of repetitions of the message 1. You may decide.
  • the transmitting/receiving unit 120 may transmit instruction information regarding the number of repetitions of message 3.
  • the control unit 110 may determine the number of repetitions of the message 3 based on the instruction information and information regarding the repetition of the message 1 in the random access procedure including the repetition of the message 3.
  • FIG. 25 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 transmitting/receiving section 220, and a transmitting/receiving antenna 230. Note that 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 functional blocks that are characteristic 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 entire user terminal 20.
  • the control unit 210 can be configured from a controller, a control circuit, etc., which will be explained based on common recognition in the technical field related to the present disclosure.
  • the control unit 210 may control signal generation, mapping, etc.
  • the control unit 210 may control transmission and reception using the transmitting/receiving unit 220 and the transmitting/receiving antenna 230, measurement, and the like.
  • the control unit 210 may generate data, control information, sequences, etc. to be transmitted as a signal, and may transfer the generated data to the transmitting/receiving unit 220.
  • the transmitting/receiving section 220 may include a baseband section 221, an RF section 222, and a measuring 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 related to the present disclosure.
  • the transmitting/receiving section 220 may be configured as an integrated transmitting/receiving section, or may be configured from a transmitting section and a receiving section.
  • the transmitting section may include a transmitting processing section 2211 and an RF section 222.
  • the reception 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, such as an array antenna, as described based on common recognition in the technical field related to the present disclosure.
  • the transmitter/receiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc.
  • the transmitter/receiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, and the like.
  • the transmitting/receiving unit 220 may form at least one of a transmitting beam and a receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.
  • digital beamforming e.g., precoding
  • analog beamforming e.g., phase rotation
  • the transmission/reception unit 220 (transmission processing unit 2211) performs PDCP layer processing, RLC layer processing (e.g. RLC retransmission control), MAC layer processing (e.g. , HARQ retransmission control), etc., to generate a bit string to be transmitted.
  • RLC layer processing e.g. RLC retransmission control
  • MAC layer processing e.g. , HARQ retransmission control
  • the transmitting/receiving unit 220 (transmission processing unit 2211) performs channel encoding (which may include error correction encoding), modulation, mapping, filter processing, DFT processing (as necessary), and IFFT processing on the bit string to be transmitted. , precoding, digital-to-analog conversion, etc., and output a baseband signal.
  • DFT processing may be based on the settings of transform precoding.
  • the transmitting/receiving unit 220 transmits the above processing in order to transmit the channel using the DFT-s-OFDM waveform.
  • DFT processing may be performed as the transmission processing, or if not, DFT processing may not be performed as the transmission processing.
  • the transmitting/receiving unit 220 may perform modulation, filter processing, amplification, etc. on the baseband signal in a radio frequency band, and may transmit the signal in the radio frequency band via the transmitting/receiving antenna 230. .
  • the transmitting/receiving section 220 may perform amplification, filter processing, demodulation into 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), filter processing, demapping, demodulation, and decoding (error correction) on the acquired baseband signal. (which may include decoding), MAC layer processing, RLC layer processing, and PDCP layer processing may be applied to obtain user data and the like.
  • the transmitting/receiving unit 220 may perform measurements regarding the received signal.
  • the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal.
  • the measurement unit 223 may measure received power (for example, RSRP), reception quality (for example, RSRQ, SINR, SNR), signal strength (for example, RSSI), propagation path information (for example, CSI), and the like.
  • the measurement results may be output to the control unit 210.
  • the transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting/receiving unit 220 and the transmitting/receiving antenna 230.
  • the transmitting/receiving unit 220 may transmit first ability information regarding the ability to repeat message 1 and second ability information regarding the ability to repeat message 3.
  • the control unit 210 performs a first random access procedure including repeating the message 1 and repeating the message 3 based on the first capability information and the second capability information, or performs a first random access procedure including repeating the message 1 and repeating the message 3. It may be determined whether to perform a second random access procedure that does not include at least one of the repetitions of 3.
  • the control unit 210 may use a first random access resource for the first random access procedure, and may use a second random access resource different from the first random access resource for the second random access procedure.
  • the control unit 210 may determine whether to perform the first random access procedure or the second random access procedure based on a comparison between the received reference signal power and a threshold value.
  • the control unit 210 may control reception of information regarding at least one of the maximum number of repetitions of the message 1 and a threshold for reference signal reception power.
  • the transmitting/receiving unit 220 may receive information regarding the first random access procedure including repeating message 1. Based on the information, the control unit 210 uses a first random access resource for the first random access procedure, and uses a second random access resource different from the first random access resource that does not include repetition of the message 1. It may also be used in the second random access procedure.
  • the information may include at least one of a number of preamble indexes for the first random access resource and a first preamble index for the first random access resource.
  • the control unit 210 may use a first random access channel occasion for the first random access procedure, and use a second random access channel occasion different from the first random access channel occasion for the second random access procedure. good.
  • the control unit 210 determines a first random access channel occasion for the first random access procedure based on at least one of a mask index and a second random access channel occasion for the second random access procedure. may be determined.
  • the transceiver unit 220 may receive information regarding a random access procedure including multiple repetitions of message 1 and multiple repetitions of message 3. Based on the information, the control unit 210 controls one or more second beams used for the plurality of repetitions of the message 3 based on the one or more first beams used for the plurality of repetitions of the message 1. You may decide.
  • the control unit 210 may determine the one or more second beams from among the one or more first beams.
  • One random access response may be sent for multiple repetitions of the message 1.
  • One random access response may be sent for each of multiple repetitions of said message 1.
  • the transmitting/receiving unit 220 may receive instruction information regarding the number of repetitions of message 3.
  • the control unit 210 may determine the number of repetitions of the message 3 based on the instruction information and information regarding the repetition of the message 1 in the random access procedure including the repetition of the message 3.
  • the information may relate to the number of repetitions of the message 1.
  • the information may relate to the number of random access responses to the message 1.
  • the information may relate to the number of beams used for repeating the message 1.
  • each functional block may be realized using one physically or logically coupled device, or may be realized using two or more physically or logically separated devices directly or indirectly (e.g. , wired, wireless, etc.) and may be realized using a plurality of these devices.
  • the functional block may be realized by combining software with the one device or the plurality of devices.
  • functions include judgment, decision, judgement, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, and consideration. , broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc.
  • a functional block (configuration unit) 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. 26 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal 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, etc. .
  • 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 not to include some of the devices.
  • processor 1001 may be implemented using one or more chips.
  • Each function in the base station 10 and the user terminal 20 is performed by, for example, loading predetermined software (program) onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations and communicates via the communication device 1004. This is achieved by controlling at least one of reading and writing data in the memory 1002 and storage 1003.
  • predetermined software program
  • the processor 1001 operates an operating system to control the entire computer.
  • the processor 1001 may be configured by a central processing unit (CPU) that includes interfaces with peripheral devices, a control device, an arithmetic unit, registers, and the like.
  • CPU central processing unit
  • the above-mentioned control unit 110 (210), transmitting/receiving unit 120 (220), etc. may be realized by the processor 1001.
  • 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 in accordance with these.
  • programs program codes
  • software modules software modules
  • data etc.
  • the control unit 110 may be realized by a control program stored in the memory 1002 and operated in the processor 1001, and other functional blocks may also be realized in the same way.
  • the memory 1002 is a computer-readable recording medium, and includes at least one of Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), and other suitable storage media. It may be composed of one. Memory 1002 may be called a register, cache, main memory, or the like.
  • the memory 1002 can store executable programs (program codes), software modules, and the like to implement a wireless communication method according to an embodiment of the present disclosure.
  • the storage 1003 is a computer-readable recording medium, such as a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disk (CD-ROM), etc.), a digital versatile disk, removable disk, hard disk drive, smart card, flash memory device (e.g., card, stick, key drive), magnetic stripe, database, server, or other suitable storage medium. It may be configured by Storage 1003 may also be called an auxiliary storage device.
  • a computer-readable recording medium such as a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disk (CD-ROM), etc.), a digital versatile disk, removable disk, hard disk drive, smart card, flash memory device (e.g., card, stick, key drive), magnetic stripe, database, server, or other suitable storage medium. It may be configured by Storage 1003 may also be called an auxiliary storage device.
  • the communication device 1004 is hardware (transmission/reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc., for example.
  • the communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). It may be configured to include.
  • FDD frequency division duplex
  • TDD time division duplex
  • 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 (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts 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 performs output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (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 for each device.
  • the base station 10 and user terminal 20 also 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 to include 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 hardwares.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • PLD programmable logic device
  • FPGA field programmable gate array
  • channel, symbol and signal may be interchanged.
  • the signal may be a message.
  • the reference signal may also be abbreviated as RS, and may be called a pilot, pilot signal, etc. depending on the applicable standard.
  • a component carrier CC may be called a cell, a frequency carrier, a carrier frequency, or the like.
  • a radio frame may be composed of one or more periods (frames) in the time domain.
  • Each of the one or more periods (frames) constituting a radio frame may be called a subframe.
  • a subframe may be composed of one or more slots in the time domain.
  • a subframe may have a fixed time length (eg, 1 ms) that does not depend on numerology.
  • the numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel.
  • Numerology includes, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, and radio frame configuration. , a specific filtering process performed by the transceiver in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc.
  • a slot may be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) in the time domain. Further, a slot may be a time unit based on numerology.
  • OFDM Orthogonal Frequency Division Multiplexing
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • a slot may include multiple mini-slots. Each minislot may be made up of one or more symbols in the time domain. Furthermore, a mini-slot may also be called a sub-slot. A minislot may be made up of fewer symbols than a slot.
  • PDSCH (or PUSCH) transmitted in time units larger than minislots 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. Other names may be used for the radio frame, subframe, slot, minislot, and symbol. 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.
  • at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (for example, 1-13 symbols), or a period longer than 1ms. It may be.
  • the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.
  • TTI refers to, for example, the minimum time unit for scheduling 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
  • the TTI may be a transmission time unit of a channel-coded data packet (transport block), a code block, a codeword, etc., or may be a processing unit of scheduling, link adaptation, etc. Note that when a TTI is given, the time interval (for example, the number of symbols) to which transport blocks, code blocks, code words, etc. are actually mapped may be shorter than the TTI.
  • one slot or one minislot is called a TTI
  • one or more TTIs may be the minimum time unit for scheduling.
  • the number of slots (minislot number) that constitutes 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, etc.
  • TTI TTI in 3GPP Rel. 8-12
  • normal TTI long TTI
  • normal subframe normal subframe
  • long subframe slot
  • TTI that is shorter than the normal TTI may be referred to as an abbreviated TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
  • long TTI for example, normal TTI, subframe, etc.
  • short TTI for example, short TTI, etc. It may also be read as a TTI having the above TTI length.
  • a resource block is a resource allocation unit in the time domain and frequency domain, and may include one or more continuous subcarriers (subcarriers) in the frequency domain.
  • the number of subcarriers included in an RB may be the same regardless of the numerology, and may be 12, for example.
  • the number of subcarriers included in an RB may be determined based on numerology.
  • an RB may include one or more symbols in the time domain, and may have a length of one slot, one minislot, one subframe, or one TTI.
  • One TTI, one subframe, etc. may each be composed of one or more resource blocks.
  • one or more RBs include a physical resource block (Physical RB (PRB)), a sub-carrier group (SCG), a resource element group (REG), and a PRB/RB. It may also be called a group/set/pair.
  • PRB Physical resource block
  • SCG sub-carrier group
  • REG resource element group
  • a resource block may be configured by one or more resource elements (REs).
  • REs resource elements
  • 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.
  • Bandwidth Part (also called partial bandwidth, etc.) refers to a subset of consecutive common resource blocks (RB) for a certain numerology in a certain carrier.
  • the common RB may be specified by an RB index based on a 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 UL BWP
  • BWP for DL DL BWP
  • One or more BWPs may be configured within one carrier for a UE.
  • 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 of the active BWP.
  • “cell”, “carrier”, etc. in the present disclosure may be replaced with "BWP”.
  • the structures of the radio frame, subframe, slot, minislot, symbol, etc. described above are merely examples.
  • the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of symbols included in an RB The number of subcarriers, the number of symbols within a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.
  • radio resources may be indicated by a predetermined index.
  • data, instructions, commands, information, signals, bits, symbols, chips, etc. which may be referred to throughout the above description, may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may also be represented by a combination of
  • information, signals, etc. may be output from the upper layer to the lower layer and from the lower layer to at least one of the upper layer.
  • Information, signals, etc. may be input and output via 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. Information, signals, etc. that are input and output can be overwritten, updated, or added. The output information, signals, etc. may be deleted. The input information, signals, etc. may be transmitted to other devices.
  • Notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods.
  • the notification of information in this disclosure may be physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals, or a combination thereof It may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals, or a combination thereof It may be carried out by
  • 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), etc.
  • RRC signaling may 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 prescribed information is not limited to explicit notification, but may be made implicitly (for example, by not notifying the prescribed information or by providing other information) (by notification).
  • the determination may be made by a value expressed by 1 bit (0 or 1), or by a boolean value expressed by true or false. , may be performed by numerical comparison (for example, comparison with a predetermined value).
  • Software includes instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, whether referred to as software, firmware, middleware, microcode, hardware description language, or by any other name. , should be broadly construed to mean an application, software application, software package, routine, subroutine, object, executable, thread of execution, procedure, function, etc.
  • software, instructions, information, etc. may be sent and received via a transmission medium.
  • a transmission medium such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.
  • wired technology such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.
  • wireless technology such as infrared, microwave, etc.
  • Network may refer to devices (eg, base stations) included in the network.
  • precoding "precoding weight”
  • QCL quadsi-co-location
  • TCI state "Transmission Configuration Indication state
  • space space
  • spatial relation "spatial 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”, and “panel” are interchangeable.
  • Base Station BS
  • Wireless base station Wireless base station
  • Fixed station NodeB
  • eNB eNodeB
  • gNB gNodeB
  • Access point "Transmission Point (TP)”, “Reception Point (RP)”, “Transmission/Reception Point (TRP)”, “Panel”
  • cell “sector,” “cell group,” “carrier,” “component carrier,” and the like
  • a base station is sometimes referred to by terms such as macrocell, small cell, femtocell, and picocell.
  • a base station can accommodate one or more (eg, three) cells. If a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area is connected to a base station subsystem (e.g., an indoor small base station (Remote Radio Communication services can also be provided by the Head (RRH)).
  • a base station subsystem e.g., an indoor small base station (Remote Radio Communication services can also be provided by the Head (RRH)
  • RRH Remote Radio Communication services
  • the term “cell” or “sector” refers to part or all of the coverage area of a base station and/or base station subsystem that provides communication services in this coverage.
  • a base station transmitting information to a terminal may be interchanged with the base station instructing the terminal to control/operate based on the information.
  • MS Mobile Station
  • UE User Equipment
  • a mobile station is a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal. , handset, user agent, mobile client, client, or some other suitable terminology.
  • At least one of a base station and a mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc.
  • a transmitting device may be called a transmitting device, a receiving device, a wireless communication device, etc.
  • the base station and the mobile station may be a device mounted on a moving object, the moving object itself, or the like.
  • the moving body refers to a movable object, and the moving speed is arbitrary, and naturally includes cases where the moving body is stopped.
  • the mobile objects include, for example, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, carts, rickshaws, and ships (ships and other watercraft). , including, but not limited to, airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, balloons, and items mounted thereon.
  • the mobile object may be a mobile object that autonomously travels based on a travel command.
  • the moving object may be a vehicle (for example, a car, an airplane, etc.), an unmanned moving object (for example, a drone, a self-driving car, etc.), or a robot (manned or unmanned). ).
  • a vehicle for example, a car, an airplane, etc.
  • an unmanned moving object for example, a drone, a 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 the mobile station may be an Internet of Things (IoT) device such as a sensor.
  • IoT Internet of Things
  • FIG. 27 is a diagram illustrating an example of a vehicle according to an embodiment.
  • the vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (current sensor 50, (including a rotation speed sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service section 59, and a communication module 60. Be prepared.
  • the drive 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 includes a microprocessor 61, a memory (ROM, RAM) 62, and a communication port (for example, an input/output (IO) port) 63. Signals from various sensors 50-58 provided in the vehicle are input to the electronic control unit 49.
  • the electronic control section 49 may be called an electronic control unit (ECU).
  • 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 wheel 46/rear wheel 47 obtained by the rotation speed sensor 51, and a signal obtained by the air pressure sensor 52.
  • air pressure signals of the front wheels 46/rear wheels 47 a vehicle speed signal acquired by the vehicle speed sensor 53, an acceleration signal acquired by the acceleration sensor 54, a depression amount signal of the accelerator pedal 43 acquired by the accelerator pedal sensor 55, and a brake pedal sensor.
  • 56 a shift lever 45 operation signal obtained by the shift lever sensor 57, and an object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc. There are signals etc.
  • the information service department 59 includes various devices such as car navigation systems, audio systems, speakers, displays, televisions, and radios that provide (output) various information such as driving information, traffic information, and entertainment information, and these devices. It consists of one or more ECUs that control the 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 (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accepts input from the outside, and an output device that performs output to the outside (for example, display, speaker, LED lamp, touch panel, etc.).
  • an input device for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.
  • an output device that performs output to the outside (for example, display, speaker, LED lamp, touch panel, etc.).
  • the driving support system unit 64 includes millimeter wave radar, Light Detection and Ranging (LiDAR), a camera, a positioning locator (for example, Global Navigation Satellite System (GNSS), etc.), and map information (for example, High Definition (HD)). maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., inertial measurement units (IMUs), 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 burden, as well as one or more devices that control these devices. It consists of an ECU. Further, the driving support system section 64 transmits and receives various information via the communication module 60, and realizes a driving support function or an automatic driving function.
  • LiDAR Light Detection and Ranging
  • GNSS Global Navigation Satellite System
  • HD High Definition
  • maps for example, autonomous vehicle (AV) maps, etc.
  • gyro systems e.g.,
  • 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 via the communication port 63 with 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, which are included in the vehicle 40.
  • 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 external devices. For example, various information is transmitted and received with an external device via wireless communication.
  • the communication module 60 may be located either inside or outside the electronic control unit 49.
  • the external device may be, for example, the base station 10, user terminal 20, etc. described above.
  • the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (it 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 that are 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. At least one of the information based on the information may be transmitted to an external device via wireless communication.
  • the electronic control unit 49, various sensors 50-58, information service unit 59, etc. may be called an input unit that receives input.
  • the PUSCH transmitted by the communication module 60 may include information based on the above input.
  • 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 section 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 a display and a speaker based on the PDSCH (or data/information decoded from the PDSCH) received by the communication module 60). may be called.
  • the communication module 60 also stores various information received from external devices into 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, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, and left and right rear wheels provided in the vehicle 40. 47, axle 48, various sensors 50-58, etc. may be controlled.
  • the base station in the present disclosure may be replaced by a user terminal.
  • communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, it may be called Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.).
  • D2D Device-to-Device
  • V2X Vehicle-to-Everything
  • each aspect/embodiment of the present disclosure may be applied.
  • the user terminal 20 may have the functions that the base station 10 described above has.
  • words such as "uplink” and “downlink” may be replaced with words corresponding to inter-terminal communication (for example, "sidelink”).
  • uplink channels, downlink channels, etc. may be replaced with sidelink channels.
  • the user terminal in the present disclosure may be replaced with a base station.
  • the base station 10 may have the functions that the user terminal 20 described above has.
  • the operations performed by the base station may be performed by its upper node in some cases.
  • various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (e.g. It is clear that this can be performed by a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc. (though not limited thereto), or a combination thereof.
  • MME Mobility Management Entity
  • S-GW Serving-Gateway
  • Each aspect/embodiment described in this disclosure may be used alone, in combination, or may be switched and used in accordance with execution. Further, the order of the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this disclosure may be changed as long as there is no contradiction. For example, the methods described in this disclosure use an example order to present elements of the various steps and are not limited to the particular 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 an integer or decimal number, for example
  • 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 (registered trademark)
  • IEEE 802.16 WiMAX (registered trademark)
  • IEEE 802.20 Ultra-WideBand (UWB), Bluetooth (registered trademark), and other appropriate wireless communication methods.
  • the present invention may be applied to systems to be used, next-generation systems expanded, modified,
  • the phrase “based on” does not mean “based solely on” unless explicitly stated otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”
  • any reference to elements using the designations "first,” “second,” etc. does not generally limit the amount or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, reference to a first and second element does not imply that only two elements may be employed or that the first element must precede the second element in any way.
  • determining may encompass a wide variety of actions. For example, “judgment” can mean judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry ( For example, searching in a table, database, or other data structure), ascertaining, etc. may be considered to be “determining.”
  • judgment (decision) includes receiving (e.g., receiving information), transmitting (e.g., sending information), input (input), output (output), access ( may be considered to be “determining”, such as accessing data in memory (eg, accessing data in memory).
  • judgment is considered to mean “judging” resolving, selecting, choosing, establishing, comparing, etc. Good too.
  • judgment (decision) may be considered to be “judgment (decision)” of some action.
  • the "maximum transmit power" described in this disclosure may mean the maximum value of transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the It may also mean rated UE maximum transmit power).
  • connection refers to any connection or coupling, direct or indirect, between two or more elements.
  • the coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connection” may be replaced with "access.”
  • microwave when two elements are connected, they may be connected using one or more electrical wires, cables, printed electrical connections, etc., as well as in the radio frequency domain, microwave can be considered to be “connected” or “coupled” to each other using electromagnetic energy having wavelengths in the light (both visible and invisible) range.
  • a and B are different may mean “A and B are different from each other.” Note that the term may also mean that "A and B are each different from C”. Terms such as “separate” and “coupled” may also be interpreted similarly to “different.”
  • the i-th (i is any integer), not only in the elementary, comparative, and superlative, but also interchangeably (for example, "the highest” can be interpreted as “the i-th highest”). may be read interchangeably).

Landscapes

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

Abstract

A terminal according to an aspect of the present disclosure comprises: a transmission unit that transmits first capability information concerning a capability for repetition of a message 1, and second capability information concerning a capability for repetition of a message 3; and a control unit that determines whether, on the basis of the first capability information and the second capability information, to perform a first random-access procedure that includes repetition of the message 1 and repetition of the message 3, or a second random access procedure that does not include at least one of the repetition of the message 1 and repetition of the message 3. According to the aspect of the present disclosure, the coverage of a random-access procedure can be improved.

Description

端末、無線通信方法及び基地局Terminal, wireless communication method and base station
　本開示は、次世代移動通信システムにおける端末、無線通信方法及び基地局に関する。 The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system.
　Universal　Mobile　Telecommunications　System（ＵＭＴＳ）ネットワークにおいて、更なる高速データレート、低遅延などを目的としてLong　Term　Evolution（ＬＴＥ）が仕様化された（非特許文献１）。また、ＬＴＥ（Third　Generation　Partnership　Project（３ＧＰＰ（登録商標））　Release（Ｒｅｌ．）８、９）の更なる大容量、高度化などを目的として、ＬＴＥ－Ａｄｖａｎｃｅｄ（３ＧＰＰ　Ｒｅｌ．１０－１４）が仕様化された。 In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been specified for the purpose of higher data rates, lower delays, etc. (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel. 10-14) is a specification for the purpose of further increasing capacity and sophistication of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel. 8, 9). was made into
　ＬＴＥの後継システム（例えば、5th　generation　mobile　communication　system（５Ｇ）、５Ｇ＋（plus）、6th　generation　mobile　communication　system（６Ｇ）、New　Radio（ＮＲ）、３ＧＰＰ　Ｒｅｌ．１５以降などともいう）も検討されている。 Successor systems to LTE (for example, also referred to as 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later) are also being considered. .
　将来の無線通信システム（例えば、ＮＲ）において、カバレッジの改善が検討されている。 Improving coverage is being considered in future wireless communication systems (for example, NR).
　しかしながら、カバレッジ改善のためのランダムアクセス手順が明らかでない。このようなランダムアクセス手順が明らかでなければ、通信スループットが低下するおそれがある。 However, the random access procedure for improving coverage is not clear. If such a random access procedure is not clear, communication throughput may decrease.
　そこで、本開示は、ランダムアクセス手順のカバレッジを改善する端末、無線通信方法及び基地局を提供することを目的の１つとする。 Therefore, one of the purposes 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 according to an aspect of the present disclosure includes a transmitting unit that transmits first capability information regarding the ability to repeat a message 1 and second capability information regarding the ability to repeat a message 3; Based on the second capability information, a first random access procedure is performed that includes the repetition of the message 1 and the repetition of the message 3, or a second random access procedure that does not include at least one of the repetition of the message 1 and the repetition of the message 3 is performed. and a control unit that determines whether to perform a random access procedure.
　本開示の一態様によれば、ランダムアクセス手順のカバレッジを改善できる。 According to one aspect of the present disclosure, coverage of random access procedures can be improved.
図１Ａ及び１Ｂは、マルチＰＲＡＣＨ送信の一例を示す。1A and 1B show an example of multi-PRACH transmission. 図２は、ＰＲＡＣＨマスクインデックスと、ＳＳＢの許可されるＰＲＡＣＨオケージョン（ＲＯ）と、の関係の一例を示す。FIG. 2 shows an example of the relationship between PRACH mask index and allowed PRACH occasions (RO) of SSB. 図３は、ＭＣＳ情報フィールドの２ＭＳＢの値（コードポイント）と、繰り返し数Ｋと、の関係の一例を示す。FIG. 3 shows an example of the relationship between the 2MSB value (code point) of the MCS information field and the number of repetitions K. 図４Ａ及び４Ｂは、Ｍｓｇ１及びＭｓｇ２の関係の一例を示す。4A and 4B show an example of the relationship between Msg1 and Msg2. 図５は、実施形態＃１ａ－１に係るＤＬパスロス参照のＲＳＲＰに対するＲＡＣＨ手順を一例を示す。FIG. 5 shows an example of the RACH procedure for RSRP with DL path loss reference according to embodiment #1a-1. 図６は、実施形態＃１ａ－２の例１に係るＤＬパスロス参照のＲＳＲＰに対するＲＡＣＨ手順を一例を示す。FIG. 6 shows an example of the RACH procedure for RSRP with DL path loss reference according to Example 1 of Embodiment #1a-2. 図７は、実施形態＃１ａ－２の例２に係るＤＬパスロス参照のＲＳＲＰに対するＲＡＣＨ手順を一例を示す。FIG. 7 shows an example of the RACH procedure for RSRP with DL path loss reference according to Example 2 of Embodiment #1a-2. 図８は、実施形態１ａ－３に係るＤＬパスロス参照のＲＳＲＰに対するＲＡＣＨ手順を一例を示す。FIG. 8 shows an example of the RACH procedure for RSRP with DL path loss reference according to the embodiment 1a-3. 図９Ａ及び９Ｂは、実施形態＃１ａ－４に係る適用条件の一例を示す。9A and 9B show an example of application conditions according to embodiment #1a-4. 図１０は、ＲＳＲＰ閾値の一例を示す。FIG. 10 shows an example of the RSRP threshold. 図１１は、送信ビーム１－１Ａの一例を示す。FIG. 11 shows an example of transmission beam 1-1A. 図１２は、送信ビーム１－１Ａの別の一例を示す。FIG. 12 shows another example of the transmission beam 1-1A. 図１３は、送信ビーム１－１Ｂの一例を示す。FIG. 13 shows an example of transmission beam 1-1B. 図１４は、送信ビーム１－２Ａの第１の例を示す。FIG. 14 shows a first example of transmit beams 1-2A. 図１５は、送信ビーム１－２Ａの第２の例を示す。FIG. 15 shows a second example of transmit beams 1-2A. 図１６は、送信ビーム１－２Ａの第３の例を示す。FIG. 16 shows a third example of transmit beams 1-2A. 図１７は、送信ビーム１－２Ａの第４の例を示す。FIG. 17 shows a fourth example of transmit beams 1-2A. 図１８は、送信ビーム２－１Ａの一例を示す。FIG. 18 shows an example of the transmission beam 2-1A. 図１９は、送信ビーム２－１Ａの別の一例を示す。FIG. 19 shows another example of the transmission beam 2-1A. 図２０は、送信ビーム２－２Ａの一例を示す。FIG. 20 shows an example of transmission beam 2-2A. 図２１は、送信ビーム２－２Ａの別の一例を示す。FIG. 21 shows another example of the transmission beam 2-2A. 図２２Ａから２２Ｃは、Ｍｓｇ３繰り返しの数の候補値の一例を示す。22A to 22C show examples of candidate values for the number of Msg3 repeats. 図２３は、一実施形態に係る無線通信システムの概略構成の一例を示す図である。FIG. 23 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. 図２４は、一実施形態に係る基地局の構成の一例を示す図である。FIG. 24 is a diagram illustrating an example of the configuration of a base station according to an embodiment. 図２５は、一実施形態に係るユーザ端末の構成の一例を示す図である。FIG. 25 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. 図２６は、一実施形態に係る基地局及びユーザ端末のハードウェア構成の一例を示す図である。FIG. 26 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. 図２７は、一実施形態に係る車両の一例を示す図である。FIG. 27 is a diagram illustrating an example of a vehicle according to an embodiment.
（ＴＣＩ、空間関係、ＱＣＬ）
　ＮＲでは、送信設定指示状態（Transmission　Configuration　Indication　state（ＴＣＩ状態））に基づいて、信号及びチャネルの少なくとも一方（信号／チャネルと表現する）のＵＥにおける受信処理（例えば、受信、デマッピング、復調、復号の少なくとも１つ）、送信処理（例えば、送信、マッピング、プリコーディング、変調、符号化の少なくとも１つ）を制御することが検討されている。 (TCI, spatial relations, QCL)
In NR, the UE performs reception processing (e.g. reception, demapping, demodulation, Controlling at least one of decoding), transmission processing (eg, at least one of transmission, mapping, precoding, modulation, and encoding) is being considered.
　ＴＣＩ状態は下りリンクの信号／チャネルに適用されるものを表してもよい。上りリンクの信号／チャネルに適用されるＴＣＩ状態に相当するものは、空間関係（spatial　relation）と表現されてもよい。 The TCI states may represent those that apply to downlink signals/channels. What corresponds to the TCI state applied to uplink signals/channels may be expressed as a spatial relation.
　ＴＣＩ状態とは、信号／チャネルの疑似コロケーション（Quasi-Co-Location（ＱＣＬ））に関する情報であり、空間受信パラメータ、空間関係情報（Spatial　Relation　Information）などと呼ばれてもよい。ＴＣＩ状態は、チャネルごと又は信号ごとにＵＥに設定されてもよい。 The TCI state is information regarding quasi-co-location (QCL) of signals/channels, and may also be called spatial reception parameters, spatial relation information, etc. The TCI state may be set in the UE on a per-channel or per-signal basis.
　ＱＣＬとは、信号／チャネルの統計的性質を示す指標である。例えば、ある信号／チャネルと他の信号／チャネルがＱＣＬの関係である場合、これらの異なる複数の信号／チャネル間において、ドップラーシフト（Doppler　shift）、ドップラースプレッド（Doppler　spread）、平均遅延（average　delay）、遅延スプレッド（delay　spread）、空間パラメータ（spatial　parameter）（例えば、空間受信パラメータ（spatial　Rx　parameter））の少なくとも１つが同一である（これらの少なくとも１つに関してＱＣＬである）と仮定できることを意味してもよい。 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, the Doppler shift, Doppler spread, and average delay are calculated between these different signals/channels. ), delay spread, and spatial parameters (e.g., spatial Rx parameters) can be assumed to be the same (QCL with respect to at least one of these). You may.
　なお、空間受信パラメータは、ＵＥの受信ビーム（例えば、受信アナログビーム）に対応してもよく、空間的ＱＣＬに基づいてビームが特定されてもよい。本開示におけるＱＣＬ（又はＱＣＬの少なくとも１つの要素）は、ｓＱＣＬ（spatial　QCL）で読み替えられてもよい。 Note that the spatial reception parameters may correspond to the UE's reception beam (eg, reception analog beam), and the beam may be identified based on the spatial QCL. QCL (or at least one element of QCL) in the present disclosure may be read as sQCL (spatial QCL).
　ＱＣＬは、複数のタイプ（ＱＣＬタイプ）が規定されてもよい。例えば、同一であると仮定できるパラメータ（又はパラメータセット）が異なる４つのＱＣＬタイプＡ－Ｄが設けられてもよく、以下に当該パラメータ（ＱＣＬパラメータと呼ばれてもよい）について示す：
　・ＱＣＬタイプＡ（ＱＣＬ－Ａ）：ドップラーシフト、ドップラースプレッド、平均遅延及び遅延スプレッド、
　・ＱＣＬタイプＢ（ＱＣＬ－Ｂ）：ドップラーシフト及びドップラースプレッド、
　・ＱＣＬタイプＣ（ＱＣＬ－Ｃ）：ドップラーシフト及び平均遅延、
　・ＱＣＬタイプＤ（ＱＣＬ－Ｄ）：空間受信パラメータ。 A plurality of types (QCL types) may be defined for QCL. For example, four QCL types A-D 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): Doppler shift, Doppler spread, average delay and delay spread,
・QCL type B (QCL-B): Doppler shift and Doppler spread,
・QCL type C (QCL-C): Doppler shift and average delay,
- QCL type D (QCL-D): Spatial reception parameters.
　ある制御リソースセット（Control　Resource　Set（ＣＯＲＥＳＥＴ））、チャネル又は参照信号が、別のＣＯＲＥＳＥＴ、チャネル又は参照信号と特定のＱＣＬ（例えば、ＱＣＬタイプＤ）の関係にあるとＵＥが想定することは、ＱＣＬ想定（QCL　assumption）と呼ばれてもよい。 For the UE to assume that one Control Resource Set (CORESET), channel or reference signal is in a particular QCL (e.g. QCL type D) relationship with another CORESET, channel or reference signal, It may also be called a QCL assumption.
　ＵＥは、信号／チャネルのＴＣＩ状態又はＱＣＬ想定に基づいて、当該信号／チャネルの送信ビーム（Ｔｘビーム）及び受信ビーム（Ｒｘビーム）の少なくとも１つを決定してもよい。 The UE may determine at least one of a transmit beam (Tx beam) and a receive beam (Rx beam) for the signal/channel based on the TCI state or QCL assumption of the signal/channel.
　ＴＣＩ状態は、例えば、対象となるチャネル（言い換えると、当該チャネル用の参照信号（Reference　Signal（ＲＳ）））と、別の信号（例えば、別のＲＳ）とのＱＣＬに関する情報であってもよい。ＴＣＩ状態は、上位レイヤシグナリング、物理レイヤシグナリング又はこれらの組み合わせによって設定（指示）されてもよい。 The TCI state may be, for example, information regarding the QCL between a target channel (in other words, a reference signal (RS) for the channel) and another signal (for example, another RS). . The TCI state may be set (indicated) by upper layer signaling, physical layer signaling, or a combination thereof.
　物理レイヤシグナリングは、例えば、下り制御情報（Downlink　Control　Information（ＤＣＩ））であってもよい。 The physical layer signaling may be, for example, downlink control information (DCI).
　ＴＣＩ状態又は空間関係が設定（指定）されるチャネルは、例えば、下り共有チャネル（Physical　Downlink　Shared　Channel（ＰＤＳＣＨ））、下り制御チャネル（Physical　Downlink　Control　Channel（ＰＤＣＣＨ））、上り共有チャネル（Physical　Uplink　Shared　Channel（ＰＵＳＣＨ））、上り制御チャネル（Physical　Uplink　Control　Channel（ＰＵＣＣＨ））の少なくとも１つであってもよい。 Channels for which TCI states or spatial relationships are set (specified) are, for example, Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), and Uplink Shared Channel (Physical Uplink Shared Channel). The channel may be at least one of a physical uplink control channel (PUCCH) and a physical uplink control channel (PUCCH).
　また、当該チャネルとＱＣＬ関係となるＲＳは、例えば、同期信号ブロック（Synchronization　Signal　Block（ＳＳＢ））、チャネル状態情報参照信号（Channel　State　Information　Reference　Signal（ＣＳＩ－ＲＳ））、測定用参照信号（Sounding　Reference　Signal（ＳＲＳ））、トラッキング用ＣＳＩ－ＲＳ（Tracking　Reference　Signal（ＴＲＳ）とも呼ぶ）、ＱＣＬ検出用参照信号（ＱＲＳとも呼ぶ）の少なくとも１つであってもよい。 In addition, the RS that has a QCL relationship with the channel is, for example, a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a measurement reference signal (Sounding Reference Signal (SRS)), tracking CSI-RS (also referred to as Tracking Reference Signal (TRS)), and QCL detection reference signal (also referred to as QRS).
　ＳＳＢは、プライマリ同期信号（Primary　Synchronization　Signal（ＰＳＳ））、セカンダリ同期信号（Secondary　Synchronization　Signal（ＳＳＳ））及びブロードキャストチャネル（Physical　Broadcast　Channel（ＰＢＣＨ））の少なくとも１つを含む信号ブロックである。ＳＳＢは、ＳＳ／ＰＢＣＨブロックと呼ばれてもよい。 The 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). SSB may be called SS/PBCH block.
　ＴＣＩ状態のＱＣＬタイプＸのＲＳは、あるチャネル／信号（のＤＭＲＳ）とＱＣＬタイプＸの関係にあるＲＳを意味してもよく、このＲＳは当該ＴＣＩ状態のＱＣＬタイプＸのＱＣＬソースと呼ばれてもよい。 An RS of QCL type X in a TCI state may mean an RS that has a QCL type You can.
（初期アクセス手順）
　初期アクセス手順において、ＵＥ（RRC_IDLEモード）は、ＳＳ／ＰＢＣＨブロック（ＳＳＢ）の受信、Ｍｓｇ．１（ＰＲＡＣＨ／ランダムアクセスプリアンブル／プリアンブル）の送信、Ｍｓｇ．２（ＰＤＣＣＨ、random　access　response（ＲＡＲ）を含むＰＤＳＣＨ）の受信、Ｍｓｇ．３（ＲＡＲ　ＵＬグラントによってスケジュールされるＰＵＳＣＨ）の送信、Ｍｓｇ．４（ＰＤＣＣＨ、UE　contention　resolution　identityを含むＰＤＳＣＨ）の受信、を行う。その後、ＵＥから基地局（ネットワーク）によってＭｓｇ．４に対するＡＣＫが送信されるとＲＲＣ接続が確立される（RRC_CONNECTEDモード）。 (Initial access procedure)
In the initial access procedure, the UE (RRC_IDLE mode) receives SS/PBCH blocks (SSB), Msg. 1 (PRACH/random access preamble/preamble) transmission, Msg. 2 (PDCCH, PDSCH including random access response (RAR)), Msg. 3 (PUSCH scheduled by RAR UL grant) transmission, Msg. 4 (PDCCH, PDSCH including UE contention resolution identity). After that, Msg. When an ACK for 4 is sent, an RRC connection is established (RRC_CONNECTED mode).
　ＳＳＢの受信は、ＰＳＳ検出、ＳＳＳ検出、ＰＢＣＨ－ＤＭＲＳ検出、ＰＢＣＨ受信、を含む。ＰＳＳ検出は、物理セルＩＤ（ＰＣＩ）の一部の検出と、ＯＦＤＭシンボルタイミングの検出（同期）と、（粗い）周波数同期と、を行う。ＳＳＳ検出は、物理セルＩＤの検出を含む。ＰＢＣＨ－ＤＭＲＳ検出は、ハーフ無線フレーム（５ｍｓ）内におけるＳＳＢインデックス（の一部）の検出を含む。ＰＢＣＨ受信は、system　frame　number（ＳＦＮ）及び無線フレームタイミング（ＳＳＢインデックス）の検出と、remaining　minimum　system　information（ＲＭＳＩ、ＳＩＢ１）受信用の設定情報の受信と、ＵＥがそのセル（キャリア）にキャンプできるか否かの認識と、を含む。 SSB reception includes PSS detection, SSS detection, PBCH-DMRS detection, and PBCH reception. PSS detection performs detection of part of the physical cell ID (PCI), detection (synchronization) of OFDM symbol timing, 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 involves detecting the system frame number (SFN) and radio frame timing (SSB index), receiving configuration information for receiving remaining minimum system information (RMSI, SIB1), and allowing the UE to camp in that cell (carrier). including the recognition of whether or not.
　ＳＳＢは、２０ＲＢの帯域と４シンボルの時間を有する。ＳＳＢの送信周期は、｛５、１０、２０、４０、８０、１６０｝ｍｓから設定可能である。ハーフフレームにおいて、周波数レンジ（ＦＲ１、ＦＲ２）に基づき、ＳＳＢの複数のシンボル位置が規定されている。 SSB has a band of 20 RB and a time of 4 symbols. The SSB transmission cycle can be set from {5, 10, 20, 40, 80, 160} ms. In a half frame, a plurality of SSB symbol positions are defined based on the frequency range (FR1, FR2).
　ＰＢＣＨは、５６ビットのペイロードを有する。８０ｍｓの周期内にＰＢＣＨのＮ個の繰り返しが送信される。ＮはＳＳＢ送信周期に依存する。 PBCH has a 56-bit payload. N repetitions of the PBCH are transmitted within a period of 80ms. N depends on the SSB transmission period.
　システム情報は、ＰＢＣＨによって運ばれるＭＩＢと、ＲＭＳＩ（ＳＩＢ１）と、other　system　information（ＯＳＩ）と、からなる。ＳＩＢ１は、ＲＡＣＨ設定、ＲＡＣＨ手順を行うための情報を含む。ＳＳＢとＳＩＢ１用ＰＤＣＣＨモニタリングリソースとの間の時間／周波数のリソースの関係は、ＰＢＣＨによって設定される。 System information consists of MIB carried by PBCH, RMSI (SIB1), and other system information (OSI). SIB1 includes information for performing RACH settings and RACH procedures. The time/frequency resource relationship between the SSB and the PDCCH monitoring resource for SIB1 is set by the PBCH.
　ビームコレスポンデンスを用いる基地局は、ＳＳＢ送信周期毎に複数のＳＳＢを複数のビームを用いてそれぞれ送信する。複数のＳＳＢは、複数のＳＳＢインデックスをそれぞれ有する。１つのＳＳＢを検出したＵＥは、そのＳＳＢインデックスに関連付けられたＲＡＣＨオケージョンにおいて、ＰＲＡＣＨを送信し、ＲＡＲウィンドウにおいて、ＲＡＲを受信する。 A base station that uses beam correspondence transmits multiple SSBs using multiple beams in each SSB transmission period. Each of the plurality of SSBs has a plurality of SSB indexes. A UE that detects one SSB transmits a PRACH in the RACH occasion associated with that SSB index and receives a RAR in the RAR window.
（ビームとカバレッジ）
　高周波数帯においては、同期信号／参照信号に対してビームフォーミングを適用しなければ、カバレッジが狭くなり、ＵＥが基地局を発見することが難しくなる。一方、カバレッジを確保するために、同期信号／参照信号にビームフォーミングを適用すると、特定の方向には強い信号が届くようになるが、それ以外の方向にはさらに信号が届きにくくなる。ＵＥの接続前の基地局において、ＵＥが存在する方向が不明であるとすると、適切な方向のみへのビームを用いて、同期信号／参照信号を送信することは不可能である。基地局が、異なる方向のビームをそれぞれ有する複数の同期信号／参照信号を送信し、ＵＥが、どのビームを発見したかを認識する方法が考えられる。カバレッジのために細い（狭い）ビームを用いると、多くの同期信号／参照信号を送信する必要があるため、オーバーヘッドが増加し、周波数利用効率が低下するおそれがある。 (beam and coverage)
In high frequency bands, if beamforming is not applied to the synchronization signal/reference signal, the coverage will be narrow and it will be difficult for the UE to discover the base station. On the other hand, if beamforming is applied to the synchronization signal/reference signal to ensure coverage, a strong signal will reach in a specific direction, but it will be more difficult for the signal to reach in other directions. If the direction in which the UE exists 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 that the base station transmits multiple synchronization signals/reference signals, each having beams in different directions, and the UE recognizes which beam it has discovered. Using thin (narrow) beams for coverage requires transmitting many synchronization/reference signals, which may increase overhead and reduce spectrum efficiency.
　ビーム（同期信号／参照信号）の数を減らしてオーバーヘッドを抑えるために、太い（広い）ビームを用いると、カバレッジが狭くなる。 If thicker (wider) beams are used to reduce the number of beams (synchronization signals/reference signals) and suppress overhead, the coverage will become narrower.
　将来の無線通信システム（例えば、６Ｇ）においては、ミリ波やテラヘルツ波などの周波数帯の利用がさらに進むと考えられる。多数の細いビームを用いて、セルのエリア／カバレッジを構築することによって、通信サービスを提供することが考えられる。 In future wireless communication systems (for example, 6G), it is thought that the use of frequency bands such as millimeter waves and terahertz waves will further advance. It is conceivable to provide communication services by building the area/coverage of cells using a large number of narrow beams.
　既存のＦＲ２を用い、エリアを拡大すること、既存のＦＲ２よりも高い周波数帯を用いること、が考えられる。これらの実現のために、マルチＴＲＰ、reconfigurable　intelligent　surface（ＲＩＳ）などに加え、ビーム管理の改善が好ましい。 It is possible to use the existing FR2 and expand the area, or to use a higher frequency band than the existing FR2. To realize these, improvements in beam management are preferred in addition to multi-TRP, reconfigurable intelligent surfaces (RIS), etc.
　frequency　range（ＦＲ）２用のＰＲＡＣＨ拡張を含むカバレッジ拡張が検討されている。例えば、同じビーム又は異なる複数ビームを用いるＰＲＡＣＨ繰り返し（repetition）が検討されている。このＰＲＡＣＨ拡張は、ＦＲ１に適用されてもよい。 Coverage extension including PRACH extension for frequency range (FR) 2 is being considered. For example, PRACH repetition using the same beam or different beams is being considered. This PRACH extension may be applied to FR1.
　ＰＲＡＣＨ拡張が、短ＰＲＡＣＨフォーマットに適用されてもよいし、他のフォーマットに適用されてもよい。 PRACH extension may be applied to the short PRACH format or to other formats.
　共通ＲＡＣＨ設定（RACH-ConfigCommon）は、一般ＲＡＣＨ設定（rach-ConfigGeneric）と、ＲＡプリアンブル総数（totalNumberOfRA-Preambles）と、ＲＡＣＨオケージョン毎のＳＳＢ及びＳＳＢ毎のcontention-based（ＣＢ）プリアンブル（ssb-perRACH-OccasionAndCB-PreamblesPerSSB）と、を含んでもよい。rach-ConfigGenericは、ＰＲＡＣＨ設定インデックス（prach-ConfigurationIndex）と、メッセージ１ＦＤＭ（msg1-FDM、１つの時間インスタンス内においてＦＤＭされるＰＲＡＣＨオケージョンの数）と、を含んでもよい。ssb-perRACH-OccasionAndCB-PreamblesPerSSBは、ＲＡＣＨオケージョン毎のＳＳＢ数１／８（oneEighth、８個のＲＡＣＨオケージョンに１つのＳＳＢが関連付けられること）に対し、ＳＳＢ毎のＣＢプリアンブルの数を含んでもよい。 The common RACH configuration (RACH-ConfigCommon) includes 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 for each SSB (ssb-perRACH). -OccasionAndCB-PreamblesPerSSB). The rach-ConfigGeneric may include a PRACH configuration index (prach-ConfigurationIndex) and a message 1FDM (msg1-FDM, number of PRACH occasions to be FDMed within one time instance). ssb-perRACH-OccasionAndCB-PreamblesPerSSB may include the number of CB preambles for each SSB for the number of SSBs for each RACH occasion 1/8 (oneEighth, one SSB is associated with eight RACH occasions).
　タイプ１ランダムアクセス手順（４ステップランダムアクセス手順、メッセージ１／２／３／４）に対し、ＵＥは、１つのＰＲＡＣＨオケージョンに関連付けられるＳＳ／ＰＢＣＨブロックの数Ｎと、有効なＰＲＡＣＨオケージョン毎、ＳＳ／ＰＢＣＨブロック毎のＣＢプリアンブルの数Ｒとを、ssb-perRACH-OccasionAndCB-PreamblesPerSSBによって適用されてもよい。 For type 1 random access procedure (4-step random access procedure, messages 1/2/3/4), the UE determines the number N of SS/PBCH blocks associated with one PRACH occasion and the SS /The number R of CB preambles per PBCH block may be applied by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.
　タイプ１ランダムアクセス手順に対し、又は、タイプ１ランダムアクセス手順と独立したＰＲＡＣＨオケージョンの設定を伴うタイプ２ランダムアクセス手順（２ステップランダムアクセス手順、メッセージＡ／Ｂ）に対し、もしＮ＜１の場合、１つのＳＳ／ＰＢＣＨブロックが１／Ｎ個の連続する有効なＲＡＣＨオケージョンにマップされ、有効なＰＲＡＣＨオケージョン毎にＳＳ／ＰＢＣＨブロックインデックスに関連付けられた連続インデックスを伴うＲ個のＣＢプリアンブルが、プリアンブルインデックス０から始まる。もしＮ＞＝１の場合、有効なＰＲＡＣＨオケージョン毎にＳＳ／ＰＢＣＨブロックインデックスｎ（０＜＝ｎ＜－Ｎ－１）に関連付けられた連続インデックスを伴うＲ個のＣＢプリアンブルが、プリアンブルインデックスｎ・N_preamble^total／Ｎから始まる。ここで、N_preamble^totalは、タイプ１ランダムアクセス手順に対し、totalNumberOfRA-Preamblesによって与えられ、タイプ１ランダムアクセス手順と独立したＰＲＡＣＨオケージョンの設定を伴うタイプ２ランダムアクセス手順に対し、msgA-TotalNumberOfRA-Preamblesによって与えられる。N_preamble^totalは、Ｎの倍数である。 For a type 1 random access procedure or for a type 2 random access procedure (two-step random access procedure, message A/B) with setting of a PRACH occasion independent of the type 1 random access procedure, if N < 1. , one SS/PBCH block is mapped to 1/N consecutive valid RACH occasions, and for each valid PRACH occasion, R CB preambles with consecutive indexes associated with the SS/PBCH block index are preambled. Starting from index 0. If N>=1, then for each valid PRACH occasion R CB preambles with consecutive indexes associated with SS/PBCH block index n (0<=n<-N-1) are created with preamble index n. N_preamble^total/Starts with N. Here, N_preamble^total is given by totalNumberOfRA-Preambles for type 1 random access procedure and msgA-TotalNumberOfRA-Preambles for type 2 random access procedure with configuration of PRACH occasion independent of type 1 random access procedure. given by. N_preamble^total is a multiple of N.
　フレーム０から始まり、ＳＳ／ＰＢＣＨブロックをＰＲＡＣＨオケージョンにマップするための、関連付け期間は、N_Tx^SSB個のＳＳ／ＰＢＣＨブロックインデックスがその関連付け期間内において少なくとも１回、ＰＲＡＣＨオケージョンにマップされるように、ＰＲＡＣＨ設定期間と関連付け期間（ＰＲＡＣＨ設定期間の数）との関係（仕様に規定される関係）に従ってＰＲＡＣＨ設定期間によって決定されるセット内の最小値である。ここで、ＵＥは、ＳＩＢ１内の、又は、共通サービングセル設定（ServingCellConfigCommon）内の、バースト内ＳＳＢ位置（ssb-PositionsInBurst）の値からN_Tx^SSBを得る。もし関連付け期間内のＳＳ／ＰＢＣＨブロックインデックスからＰＲＡＣＨオケージョンへの整数回のマッピングサイクルの後、N_Tx^SSB個のＳＳ／ＰＢＣＨブロックインデックスへマップされない、ＰＲＡＣＨオケージョン又はＰＲＡＣＨプリアンブルのセットがある場合、１つのＳＳ／ＰＢＣＨブロックインデックスも、ＰＲＡＣＨオケージョン又はＰＲＡＣＨプリアンブルのそのセットへマップされない。関連付けパターン期間は、１つ以上の関連付け期間を含み、ＰＲＡＣＨオケージョン及びＳＳ／ＰＢＣＨブロックインデックスの間のパターンが多くとも１６０ｍｓ毎に繰り返すように決定される。整数回の関連付け期間の後の、ＳＳ／ＰＢＣＨブロックインデックスに関連付けられないＰＲＡＣＨオケージョンがあれば、そのＰＲＡＣＨオケージョンはＰＲＡＣＨに用いられない。 Starting from frame 0, the association period for mapping SS/PBCH blocks to PRACH occasions is such that N_Tx^SSB SS/PBCH block indexes are mapped to PRACH occasions at least once within the association period. , is the minimum value in the set determined by the PRACH configuration period according to the relationship (relationship defined in the specification) between the PRACH configuration period and the association period (number of PRACH configuration periods). Here, the UE obtains N_Tx^SSB from the value of SSB positions in bursts (ssb-PositionsInBurst) in SIB1 or in the common serving cell configuration (ServingCellConfigCommon). One The SS/PBCH block index is also not mapped to a PRACH occasion or its set of PRACH preambles. The association pattern period includes one or more association periods and is determined such that the pattern between PRACH occasion and SS/PBCH block index repeats at most every 160 ms. If there is a PRACH occasion that is not associated with an SS/PBCH block index after an integer number of association periods, that PRACH occasion is not used for PRACH.
　ＰＲＡＣＨ設定期間１０、２０、４０、８０、１６０［ｍｓｅｃ］に対し、関連付け期間は、それぞれ｛１，２，４，８，１６｝、｛１，２，４，８｝、｛１，２，４｝、｛１，２｝、｛１｝である。 For the PRACH setting period 10, 20, 40, 80, 160 [msec], the association period is {1, 2, 4, 8, 16}, {1, 2, 4, 8}, {1, 2, 4}, {1, 2}, and {1}.
　ＰＲＡＣＨオケージョン（ＲＡＣＨオケージョン（ＲＯ））とビーム（ＳＳＢ／ＣＳＩ－ＲＳ）の関連付けのためのssb-perRACH-OccasionAndCB-PreamblesPerSSBがoneHalf,n16を示し（Ｎ＝１／２、Ｒ＝１６）、msg1-FDMが４である場合、１つの時間インスタンスに４つのＲＯがＦＤＭされ、１つのＳＳＢが２つのＲＯにマップされる。２つのＲＯにプリアンブルインデックス０から１５が関連付けられ、プリアンブルインデックス０から１５がＳＳ０Ｂに関連付けられる。このように、Ｎ＜１の場合、１つのＳＳＢが複数のＲＯにマップされる。これによって、ビーム毎のＲＯの容量が高められる。 ssb-perRACH-OccasionAndCB-PreamblesPerSSB for association of PRACH occasion (RACH occasion (RO)) and beam (SSB/CSI-RS) indicates oneHalf,n16 (N=1/2, R=16), msg1- If FDM is 4, 4 ROs are FDMed in one time instance and 1 SSB is mapped to 2 ROs. Two ROs are associated with preamble indices 0 to 15, and preamble indices 0 to 15 are associated with SSOB. Thus, if N<1, one SSB is mapped to multiple ROs. This increases the capacity of the RO per beam.
　ssb-perRACH-OccasionAndCB-PreamblesPerSSBがn4,n16を示し（Ｎ＝４、Ｒ＝１６）、msg1-FDMが４、N_preamble^totalが６４である場合、１つの時間インスタンスに４つのＲＯがＦＤＭされ、４つのＳＳＢが１つのＲＯにマップされる。１つのＲＯにＳＳＢ０から３に関連付けられる。ＳＳＢ０にプリアンブルインデックス０から１５が関連付けられ、ＳＳＢ１にプリアンブルインデックス１５から３１が関連付けられ、ＳＳＢ２にプリアンブルインデックス３２から４７がＳＳＢ２が関連付けられ、ＳＳＢ３にプリアンブルインデックス４８から６３がＳＳＢ３が関連付けられる。このように、同じＲＯが異なるＳＳ／ＰＢＣＨブロックインデックスに関連付けられ、異なるプリアンブルが異なるＳＳ／ＰＢＣＨブロックインデックスを用いる。基地局は、受信したＰＲＡＣＨによって、関連付けられたＳＳ／ＰＢＣＨブロックインデックスを区別できる。 If ssb-perRACH-OccasionAndCB-PreamblesPerSSB indicates n4,n16 (N=4, R=16), msg1-FDM is 4, and N_preamble^total is 64, then 4 ROs are FDMed in one time instance, Four SSBs are mapped to one RO. One RO is associated with SSBs 0 to 3. Preamble indexes 0 to 15 are associated with SSB0, preamble indexes 15 to 31 are associated with SSB1, preamble indexes 32 to 47 are associated with SSB2 and SSB3 is associated with preamble indexes 48 to 63, and SSB3 is associated with SSB3. In this way, the same RO is associated with different SS/PBCH block indices and different preambles use different SS/PBCH block indices. The base station can distinguish the associated SS/PBCH block index by the received PRACH.
　ランダムアクセスプリアンブルは、仕様のランダムアクセス設定に規定された時間リソースのみにおいて送信されることができ、ＦＲ１であるかＦＲ２であるかと、スペクトラムタイプ（ペアード（paired）スペクトラム／supplementary　uplink（ＳＵＬ）／アンペアード（unpaired）スペクトラム）と、に依存する。ＰＲＡＣＨ設定インデックスは、上位レイヤパラメータprach-ConfigurationIndexによって、又は、もし設定されればmsgA-PRACH-ConfigurationIndexによって、与えられる。仕様において、ＰＲＡＣＨ設定インデックスの各値に対し、プリアンブルフォーマット、n_f（フレーム番号）　mod　x　=　yにおけるx及びy、サブフレーム番号、開始シンボル、サブフレーム内のＰＲＡＣＨスロット数、ＰＲＡＣＨスロット内の時間ドメインＰＲＡＣＨオケージョン数N_t^RA,slot、ＰＲＡＣＨ継続時間N_dur^RA、の少なくとも１つに関連付けられている。 The random access preamble can only be transmitted on the time resources specified in the random access configuration of the specification, whether it is FR1 or FR2, and the spectrum type (paired spectrum/supplementary uplink (SUL)/unpaired spectrum). (unpaired) spectrum). The PRACH configuration index is given by the upper layer parameter prach-ConfigurationIndex or, if configured, by msgA-PRACH-ConfigurationIndex. In the specification, for each value of the PRACH configuration index, the preamble format, n_f (frame number) mod x and y at y, subframe number, starting symbol, number of PRACH slots in the subframe, time domain in the 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.
　ＰＲＡＣＨ繰り返しがシナリオへ適用できるかどうか、異なる目的によってトリガされるＲＡＣＨ手順のタイプは異なる。ＲＡＣＨ手順のタイプは、以下の少なくとも１つであってもよい。
・contention-free　random　access（ＣＦＲＡ）、ＰＤＣＣＨオーダＲＡ（PDCCH　ordered　RA、ＰＤＣＣＨオーダによって開始される（initiated）ＲＡ）、beam　failure　recovery（ＢＦＲ）用ＣＦＲＡ、system　information（ＳＩ）要求用ＣＦＲＡ、同期を伴う再設定（reconfiguration　with　sync）用ＣＦＲＡなど。
・contention-based　random　access（ＣＢＲＡ）、ＭＡＣエンティティによってトリガされたＲＡ、イベントを伴うＲＲＣによってトリガされたＲＡ、ＢＦＲ用ＣＢＲＡなど。
・４ステップＲＡＣＨ。
・２ステップＲＡＣＨ。 Whether PRACH repetition is applicable to the scenarios, the types of RACH procedures triggered by different purposes are different. The type of RACH procedure may be at least one of the following:
・Contention-free random access (CFRA), PDCCH ordered RA (PDCCH ordered RA, RA initiated by PDCCH order), CFRA for beam failure recovery (BFR), CFRA for system information (SI) request, synchronization CFRA for reconfiguration with sync, etc.
- contention-based random access (CBRA), RA triggered by MAC entity, RA triggered by RRC with event, CBRA for BFR, etc.
・4 step RACH.
・2 step RACH.
　しかしながら、ＰＲＡＣＨ繰り返しの設定／手順が明らかでない。例えば、繰り返しのためのＰＲＡＣＨリソース（例えば、繰り返しパターン、繰り返し数）がどのように設定されるか、プリアンブル繰り返し送信のＵＥ動作、ＲＡＣＨに関するカウンタ／タイマへの影響、などが明らかでない。このような設定／手順が明らかでなければ、通信品質／通信スループットの劣化のおそれがある。 However, the setting/procedure for 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 RACH-related counters/timers, etc. If such settings/procedures are not clear, there is a risk of deterioration in communication quality/communication throughput.
（ＲＡ応答ウィンドウ）
　ＲＡ応答ウィンドウ（ra-ResponseWindow）は、ＲＡ応答（ＲＡＲ）をモニタするための時間ウィンドウである（ＳｐＣｅｌｌのみ）。ＲＡ競合解決タイマ（ra-ContentionResolutionTimer）は、ＲＡ競合解決のタイマである（ＳｐＣｅｌｌのみ）。Ｍｓｇ．Ｂ応答ウィンドウは、２ステップＲＡタイプのためのＲＡ応答（ＲＡＲ）をモニタするための時間ウィンドウである（ＳｐＣｅｌｌのみ）。 (RA response window)
The RA response window (ra-ResponseWindow) is a time window for monitoring the RA response (RAR) (SpCell only). The RA contention resolution timer (ra-ContentionResolutionTimer) is a timer for RA contention resolution (SpCell only). Msg. B response window is a time window for monitoring RA response (RAR) for two-step RA type (SpCell only).
　ＲＡプリアンブルが送信されると、測定ギャップが発生する可能性に関わらず、ＭＡＣエンティティは、以下の動作１から３を行う。 Once the RA preamble is transmitted, the MAC entity performs actions 1 to 3 below, regardless of the possibility that a measurement gap may occur.
［動作１］
　もしＢＦＲリクエスト用のコンテンションフリーＲＡプリアンブルがそのＭＡＣエンティティによって送信された場合、そのＭＡＣエンティティは、以下の動作１－１及び１－２を行う。
［［動作１－１］］そのＭＡＣエンティティは、ＲＡプリアンブル送信の終了からの最初のＰＤＣＣＨオケージョンにおいて、ＢＦＲ設定（BeamFailureRecoveryConfig）内に設定されたra-ResponseWindowを開始する。
［［動作１－２］］そのＭＡＣエンティティは、ra-ResponseWindowが動作している間、Ｃ－radio　network　temporary　identifier（ＲＮＴＩ）によって識別されるＳｐＣｅｌｌのＢＦＲ用サーチスペースＩＤ（recoverySearchSpaceId）によって指示されたサーチスペースにおいてＰＤＣＣＨ送信をモニタする。 [Operation 1]
If a contention-free RA preamble for a BFR request is sent by the MAC entity, the MAC entity performs the following actions 1-1 and 1-2.
[[Operation 1-1]] The MAC entity starts the ra-ResponseWindow configured in the BFR configuration (BeamFailureRecoveryConfig) in the first PDCCH occasion from the end of the RA preamble transmission.
[[Operation 1-2]] While the ra-ResponseWindow is operating, the MAC entity is indicated by the search space ID (recoverySearchSpaceId) for BFR of the SpCell identified by the C-radio network temporary identifier (RNTI). Monitor PDCCH transmission in the search space.
［動作２］
　そうでない場合、そのＭＡＣエンティティは、以下の動作２－１及び２－２を行う。
［［動作２－１］］そのＭＡＣエンティティは、ＲＡプリアンブル送信の終了からの最初のＰＤＣＣＨオケージョンにおいて、共通ＲＡＣＨ設定（RACH-ConfigCommon）内に設定されたra-ResponseWindowを開始する。
［［動作２－２］］そのＭＡＣエンティティは、ra-ResponseWindowが動作している間、ＲＡ－ＲＮＴＩによって識別されるＲＡＲ用のＳｐＣｅｌｌのＰＤＣＣＨ送信をモニタする。 [Operation 2]
Otherwise, the MAC entity performs the following actions 2-1 and 2-2.
[[Operation 2-1]] The MAC entity starts the ra-ResponseWindow configured in the common RACH configuration (RACH-ConfigCommon) in the first PDCCH occasion from the end of the RA preamble transmission.
[[Operation 2-2]] The MAC entity monitors the PDCCH transmission of the SpCell for RAR identified by the RA-RNTI while the ra-ResponseWindow is operating.
［動作３］
　もしBeamFailureRecoveryConfig内に設定されたra-ResponseWindowが満了し、且つ、Ｃ－ＲＮＴＩ宛のrecoverySearchSpaceIdによって指示されたサーチスペース上のＰＤＣＣＨ送信がそのプリアンブルが送信されたサービングセル上において受信された場合、又は、もしRACH-ConfigCommon内に設定されたra-ResponseWindowが満了し、且つ、送信されたプリアンブルインデックス（PREAMBLE_INDEX）に一致するＲＡプリアンブル識別子（identifiers）を含むＲＡＲが受信された場合、そのＭＡＣエンティティは、そのＲＡＲ受信を失敗と見なし、プリアンブル送信カウンタ（PREAMBLE_TRANSMISSION_COUNTER）を１によってインクリメントする。 [Operation 3]
If the ra-ResponseWindow configured in BeamFailureRecoveryConfig expires and the PDCCH transmission on the search space indicated by recoverySearchSpaceId destined for the C-RNTI is received on the serving cell from which its preamble was transmitted, or if If the ra-ResponseWindow configured in RACH-ConfigCommon expires and a RAR containing RA preamble identifiers matching the transmitted preamble index (PREAMBLE_INDEX) is received, the MAC entity The reception is considered a failure and the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) is incremented by 1.
　そのＭＡＣエンティティは、送信されたPREAMBLE_INDEXに一致するＲＡプリアンブル識別子（identifiers）を含むＲＡＲの受信成功の後のra-ResponseWindowを停止してもよい（ＲＡＲ用のモニタリングを停止してもよい）。 The MAC entity may stop ra-ResponseWindow (may stop monitoring for RARs) after successful reception of RARs containing RA preamble identifiers matching the transmitted PREAMBLE_INDEX.
　ＲＡ応答ウィンドウ内のＰＤＣＣＨモニタリングに対し、ＢＦＲに対する基地局の応答のためのＰＤＣＣＨと、ＲＡＲのためのＰＤＣＣＨと、の２つのケースがある。以下の内容は、両方のケースに適用されてもよい。 There are two cases for PDCCH monitoring within the RA response window: PDCCH for base station response to BFR and PDCCH for RAR. The following may apply to both cases.
　ＭＳＧＡ（Ｍｓｇ．Ａ）プリアンブルが送信されると、測定ギャップが発生する可能性に関わらず、ＭＡＣエンティティは、以下の動作４から６を行う。 Once the MSGA (Msg.A) preamble is transmitted, the MAC entity performs actions 4 to 6 below, regardless of the possibility of a measurement gap occurring.
［動作４］
　そのＭＡＣエンティティは、仕様に規定されたＰＤＣＣＨモニタリングウィンドウにおいて、Ｍｓｇ．Ｂ応答ウィンドウ（msgB-ResponseWindow）を開始する。 [Operation 4]
The MAC entity performs Msg. Start the B response window (msgB-ResponseWindow).
　msgB-ResponseWindowは、ＵＥが、ＰＲＡＣＨ送信に対応するＰＲＡＣＨオケージョンの最後のシンボルの後の少なくとも１つのシンボルであるタイプ１－ＰＤＣＣＨ　ＣＳＳセットに対するＰＤＣＣＨを受信することを設定された、最も早いＣＯＲＥＳＥＴの最初のシンボルにおいて開始してもよい。msgB-ResponseWindowの長さは、タイプ１－ＰＤＣＣＨ　ＣＳＳセット用のＳＣＳに対応してもよい。 msgB-ResponseWindow is the first of the earliest CORESET the UE is configured to receive a 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. It may start at the symbol. The length of msgB-ResponseWindow may correspond to the SCS for Type 1-PDCCH CSS set.
［動作５］
　そのＭＡＣエンティティは、msgB-ResponseWindowが動作している間、ＭＳＧＢ－ＲＮＴＩによって識別されるＲＡＲ用のＳｐＣｅｌｌのＰＤＣＣＨ送信をモニタする。 [Operation 5]
The MAC entity monitors the PDCCH transmission of the SpCell for the RAR identified by the MSGB-RNTI while the msgB-ResponseWindow is active.
［動作６］
　もしＣ－ＲＮＴＩ　ＭＡＣ　ＣＥが、そのＭＳＧＡ内に含まれた場合、そのＭＡＣエンティティは、msgB-ResponseWindowが動作している間、Ｃ－ＲＮＴＩによって識別されるＲＡＲ用のＳｐＣｅｌｌのＰＤＣＣＨ送信をモニタする。 [Operation 6]
If the C-RNTI MAC CE is included in its MSGA, the MAC entity monitors the PDCCH transmission of the SpCell for the RAR identified by the C-RNTI while the msgB-ResponseWindow is active.
　ＲＡプリアンブルが送信されるＰＲＡＣＨオケージョンに関連付けられたＲＡ－ＲＮＴＩは、以下のように計算される。
　RA-RNTI　=　1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id The RA-RNTI associated with the PRACH occasion where the RA preamble is sent is calculated as follows.
RA-RNTI = 1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id
　ここで、s_idは、ＰＲＡＣＨオケージョンの最初のＯＦＤＭシンボルのインデックスである（0<=s_id<14）。t_idは、システムフレーム内のＰＲＡＣＨオケージョンの最初のスロットのインデックスである（0<=t_id<80）。t_idの決定のためのサブキャリア間隔（ＳＣＳ）は、μの値に基づく。f_idは、周波数ドメインにおけるＰＲＡＣＨオケージョンのインデックスである（0<=f_id<8）。ul_carrier_idは、ＲＡプリアンブル送信に用いられるＵＬキャリアである（normal　uplink（ＮＵＬ）キャリアに対して0、supplementary　uplink（ＳＵＬ）キャリアに対して1）。ＲＡ－ＲＮＴＩは、仕様に従って計算される。ＲＡ－ＲＮＴＩは、４ステップＲＡＣＨ用のＲＮＴＩである。 Here, s_id is the index of the first OFDM symbol of the PRACH occasion (0<=s_id<14). t_id is the index of the first slot of the PRACH occasion within the system frame (0<=t_id<80). The subcarrier spacing (SCS) for determining t_id is based on the value of μ. f_id is the index of the PRACH occasion in the frequency domain (0<=f_id<8). ul_carrier_id is the UL carrier used for RA preamble transmission (0 for normal uplink (NUL) carriers, 1 for supplementary uplink (SUL) carriers). RA-RNTI is calculated according to specifications. RA-RNTI is an 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 The MSGB-RNTI associated with the PRACH occasion where the RA preamble is sent is calculated as follows.
MSGB-RNTI = 1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2
　ここで、s_idは、ＰＲＡＣＨオケージョンの最初のＯＦＤＭシンボルのインデックスである（0<=s_id<14）。t_idは、システムフレーム内のＰＲＡＣＨオケージョンの最初のスロットのインデックスである（0<=t_id<80）。t_idの決定のためのサブキャリア間隔（ＳＣＳ）は、μの値に基づく。f_idは、周波数ドメインにおけるＰＲＡＣＨオケージョンのインデックスである（0<=f_id<8）。ul_carrier_idは、ＲＡプリアンブル送信に用いられるＵＬキャリアである（normal　uplink（ＮＵＬ）キャリアに対して0、supplementary　uplink（ＳＵＬ）キャリアに対して1）。ＭＳＧＢ－ＲＮＴＩは、２ステップＲＡＣＨ用のＲＮＴＩである。 Here, s_id is the index of the first OFDM symbol of the PRACH occasion (0<=s_id<14). t_id is the index of the first slot of the PRACH occasion within the system frame (0<=t_id<80). The subcarrier spacing (SCS) for determining t_id is based on the value of μ. f_id is the index of the PRACH occasion in the frequency domain (0<=f_id<8). ul_carrier_id is the UL carrier used for RA preamble transmission (0 for normal uplink (NUL) carriers, 1 for supplementary uplink (SUL) carriers). MSGB-RNTI is an RNTI for 2-step RACH.
（ＰＤＣＣＨオーダ）
＜ＰＤＣＣＨオーダ用ＤＣＩフォーマット＞
　ＤＣＩフォーマット１＿０は、ＤＣＩフォーマットの識別子フィールドと、常に１にセットされたビットフィールドと、周波数ドメインリソース割り当て（frequency　domain　resource　assignment）フィールドと、を含む。ＤＣＩフォーマット１＿０のcyclic　redundancy　check（ＣＲＣ）がＣ－ＲＮＴＩによってスクランブルされ、周波数ドメインリソース割り当てフィールドが全て１である場合、そのＤＣＩフォーマット１＿０は、ＰＤＣＣＨオーダによって開始されるランダムアクセス手順用であり、残りのフィールドは、ランダムアクセスプリアンブル、ＵＬ／supplementary　Uplink（ＳＵＬ）インジケータ、ＳＳ／ＰＢＣＨインデックス（ＳＳＢインデックス）、ＰＲＡＣＨマスクインデックス、予約（reserved）ビット（１２ビット）、である。 (PDCCH order)
<DCI format for PDCCH order>
DCI format 1_0 includes a DCI format identifier field, a bit field that is always set to 1, and a frequency domain resource assignment field. If the cyclic redundancy check (CRC) of DCI format 1_0 is scrambled by C-RNTI and the frequency domain resource allocation field is all ones, then that DCI format 1_0 is for random access procedure initiated by PDCCH order and the rest The fields are random access preamble, UL/supplementary Uplink (SUL) indicator, SS/PBCH index (SSB index), PRACH mask index, and reserved bits (12 bits).
＜ＰＲＡＣＨオケージョン＞
　ＰＤＣＣＨオーダによってトリガされたＰＲＡＣＨ送信の場合、ＰＲＡＣＨマスクインデックスフィールドは、ランダムアクセスプリアンブルインデックスフィールドの値がゼロでない場合、ＰＲＡＣＨオケージョンが、ＰＤＣＣＨオーダのＳＳ／ＰＢＣＨブロックインデックスフィールドによって示されるＳＳ／ＰＢＣＨブロックｉンデックスに関連付けられているＰＲＡＣＨ送信のＰＲＡＣＨオケージョンを示す。 <PRACH Occasion>
For PRACH transmissions triggered by a PDCCH order, the PRACH mask index field specifies that if the value of the Random Access Preamble Index field is non-zero, the PRACH occasion is the SS/PBCH block i indicated by the SS/PBCH block index field of the PDCCH order. indicates the PRACH occasion of the PRACH transmission associated with the index.
　上位レイヤによってトリガされたＰＲＡＣＨ送信（ＰＤＣＣＨオーダによってトリガされないＰＲＡＣＨ送信）の場合、もしssb-ResourceListが提供されると、ＰＲＡＣＨマスクインデックスはra-ssb-OccasionMaskIndexによって示される。そのra-ssb-OccasionMaskIndexは、ＰＲＡＣＨオケージョンが、選択されたＳＳ／ＰＢＣＨブロックインデックスに関連付けられているＰＲＡＣＨ送信のための、そのＰＲＡＣＨオケージョンを示す。 For PRACH transmissions triggered by higher layers (PRACH transmissions not triggered by PDCCH order), if ssb-ResourceList is provided, the PRACH mask index is indicated by ra-ssb-OccasionMaskIndex. The ra-ssb-OccasionMaskIndex indicates the PRACH occasion for the PRACH transmission that is associated with the selected SS/PBCH block index.
　ＰＲＡＣＨオケージョンは、対応するＳＳ／ＰＢＣＨブロックインデックス毎に連続してマッピングされる。マスクインデックス値によって示されるＰＲＡＣＨオケージョンのインデックス付けは、ＳＳ／ＰＢＣＨブロックインデックス毎、連続するＰＲＡＣＨオケージョンのマッピングサイクル毎に、リセットされる。ＵＥは、利用可能な最初のマッピングサイクルにおいて、指示されたＳＳ／ＰＢＣＨブロックインデックスに対するＰＲＡＣＨマスクインデックス値によって示されるＰＲＡＣＨオケージョンを、ＰＲＡＣＨ送信用に選択する。 PRACH occasions are mapped consecutively for each corresponding SS/PBCH block index. The PRACH occasion indexing indicated by the mask index value is reset every SS/PBCH block index and every successive PRACH occasion mapping cycle. The UE selects the PRACH occasion indicated by the PRACH mask index value for the indicated SS/PBCH block index for PRACH transmission in the first available mapping cycle.
　指示されたプリアンブルインデックスに対し、ＰＲＡＣＨオケージョンの順序は、以下である。
・第１に、周波数多重されたＰＲＡＣＨオケージョンのための周波数リソースインデックスの増加順。
・第２に、ＰＲＡＣＨスロット内の時間多重されたＰＲＡＣＨオケージョンのための時間リソースインデックスの増加順。
・第３に、ＰＲＡＣＨスロットのインデックスの昇順。 For the indicated preamble index, the order of PRACH occasions is as follows.
- First, increasing order of frequency resource index for frequency multiplexed PRACH occasions.
- Second, increasing order of time resource index for time multiplexed PRACH occasions within a PRACH slot.
- Third, ascending order of PRACH slot index.
　上位レイヤからの要求に応じてトリガされるＰＲＡＣＨ送信に対し、もしcsirs-ResourceListが提供されている場合、ra-OccasionListの値は、ＰＲＡＣＨ送信のＰＲＡＣＨオケージョンのリストを示し、ＰＲＡＣＨオケージョンはcsi-RSによって示された選択されたＣＳＩ－ＲＳインデックスに関連付けられる。ra-OccasionListによって示されるＰＲＡＣＨオケージョンのインデックス付けは、関連付けパターン期間毎にリセットされる。 For PRACH transmissions triggered in response to requests from upper layers, if csirs-ResourceList is provided, the value of ra-OccasionList indicates the list of PRACH occasions for PRACH transmissions, and the 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.
　ＰＲＡＣＨマスクインデックス値（msgA-SSB-SharedRO-MaskIndex）の値は、ＳＳＢの許容されるＰＲＡＣＨオケージョン（ＰＲＡＣＨオケージョンインデックスの値）に関連付けられる。 The value of the PRACH mask index value (msgA-SSB-SharedRO-MaskIndex) is associated with the allowed PRACH occasions of the SSB (the value of the PRACH occasion index).
＜ＭＡＣエンティティにおけるランダムアクセス手順＞
　ランダムアクセス手順は、ＰＤＣＣＨオーダ、ＭＡＣエンティティ自身、又は、仕様に準拠したイベントのためのＲＲＣによって開始される。ＭＡＣエンティティ内において、任意の時点において進行中のランダムアクセス手順は１つだけである。ＳＣｅｌｌのランダムアクセス手順は、0b000000と異なるra-PreambleIndexを伴うＰＤＣＣＨオーダによってのみ開始される。 <Random access procedure in MAC entity>
The random access procedure is initiated by the PDCCH order, by the MAC entity itself, or by RRC for specification compliant events. Only one random access procedure is ongoing within a MAC entity at any given time. The SCell random access procedure is initiated only by PDCCH orders with ra-PreambleIndex different from 0b000000.
　サービングセル上においてランダムアクセス手順が開始された場合、ＭＡＣエンティティは、以下のことを行う。
・ランダムアクセス手順がＰＤＣＣＨオーダによって開始され、且つ、ＰＤＣＣＨによって明示的に提供されたra-PreambleIndexが0b000000でない場合、又は、ランダムアクセス手順が同期を伴う再設定（reconfiguration）のために開始され、４ステップＲＡタイプのコンテンションフリーのランダムアクセスリソースが、ランダムアクセス手順のために選択されたＢＷＰに対し、rach-ConfigDedicatedによって明示的に提供されている場合、RA_TYPEを4-stepRAに設定する。 When a random access procedure is initiated on the serving cell, the MAC entity does the following:
- If a random access procedure is initiated by a PDCCH order and the ra-PreambleIndex explicitly provided by the PDCCH is not 0b000000, or if a random access procedure is initiated for reconfiguration with synchronization, If contention-free random access resources of step RA type are explicitly provided by rach-ConfigDedicated for the BWP selected for the random access procedure, set RA_TYPE to 4-stepRA.
　選択されたRA_TYPEが4-stepRAに設定されている場合、ＭＡＣエンティティは次のことを行う。
・ra-PreambleIndexがＰＤＣＣＨから明示的に提供され、且つ、ra-PreambleIndexが0b000000ではない場合、PREAMBLE_INDEXを通知されたra-PreambleIndexにセットし、ＰＤＣＣＨによって通知されたＳＳＢを選択する。
・上記のようにＳＳＢが選択された場合、ra-ssb-OccasionMaskIndexによって与えられた制限によって許可され、選択されたＳＳＢに対応する、ＰＲＡＣＨオケージョンから、次に利用可能なＰＲＡＣＨオケージョンを決定する（ＭＡＣエンティティは、仕様に従って、選択されたＳＳＢに対応して、連続するＰＲＡＣＨオケージョンの中から等確率でランダムにＰＲＡＣＨオケージョンを選択する。ＭＡＣエンティティは、選択されたＳＳＢに対応する次に利用可能なＰＲＡＣＨオケージョンを決定する場合、測定ギャップの発生の可能性を考慮してもよい）。 If the selected RA_TYPE is set to 4-stepRA, the MAC entity does the following:
- If ra-PreambleIndex is explicitly provided by PDCCH and ra-PreambleIndex is not 0b000000, set PREAMBLE_INDEX to the notified ra-PreambleIndex and select the SSB notified by PDCCH.
- If an SSB is selected as above, determine the next available PRACH occasion from the PRACH occasions allowed by the restriction given by ra-ssb-OccasionMaskIndex and corresponding to the selected SSB (MAC The entity randomly selects a PRACH occasion among consecutive PRACH occasions with equal probability, corresponding to the selected SSB, according to the specification.The MAC entity selects the next available PRACH corresponding to the selected SSB. When determining occasions, the possibility of measurement gaps may be considered).
＜ＰＤＣＣＨオーダ受信とＰＲＡＣＨ送信の間の時間＞
　もしＰＤＣＣＨオーダによってランダムアクセス手順が開始された場合、ＵＥは、上位レイヤによって要求されれば、仕様に記述されたように、ＰＤＣＣＨオーダ受信の最後のシンボルとＰＲＡＣＨ送信の最初のシンボルとの間の時間が、N_(T,2)+Δ_BWPSwitching+Δ_Delay+T_switch［msec］以上である場合（時間条件）の、選択されたＰＲＡＣＨオケージョン内においてＰＲＡＣＨを送信する。ここで、N_(T,2)は、ＵＥ処理能力１（UE　processing　capability　1）のＰＵＳＣＨ準備時間に対応するN_2シンボルの継続時間である。μは、ＰＤＣＣＨオーダのサブキャリア間隔（ＳＣＳ）設定と、それに対応するＰＲＡＣＨ送信のＳＣＳ設定と、の間の最小ＳＣＳ設定に対応すると仮定する。アクティブＵＬ　ＢＷＰが変化しない場合、Δ_BWPSwitching=0であり、そうでない場合、Δ_BWPSwitchingは仕様に定義される。ＦＲ１においてΔ_delay=0.5msecであり、ＦＲ２においてΔ_delay=0.25msecである。T_switchは、仕様に定義されているスイッチングギャップ継続時間である。 <Time between PDCCH order reception and PRACH transmission>
If a random access procedure is initiated by a PDCCH order, the UE, if requested by higher layers, PRACH is transmitted within the selected PRACH occasion when the time is greater than or equal to N_(T,2)+Δ_BWPSwitching+Δ_Delay+T_switch [msec] (time condition). Here, N_(T,2) is the duration of N_2 symbols corresponding to the PUSCH preparation time of UE processing capability 1. It is assumed that μ corresponds to the minimum SCS setting between the subcarrier spacing (SCS) setting of the PDCCH order and that of the corresponding PRACH transmission. If the active UL BWP does not change, Δ_BWPSwitching=0, otherwise Δ_BWPSwitching is defined in the specification. In FR1, Δ_delay=0.5 msec, and in FR2, Δ_delay=0.25 msec. T_switch is the switching gap duration defined in the specification.
＜ＰＲＡＣＨオケージョンの有効（valid）／無効（invalid）の条件（有効条件）＞
　ペアード（paired）スペクトラム（ＦＤＤ）又はＳＵＬバンドにおいて、全てのＰＲＡＣＨオケージョンが有効である。アンペアード（unpaired）スペクトラム（ＴＤＤ）において、ＰＲＡＣＨオケージョンは、以下の規定１及び２に従ってもよい。
［規定１］
　ＵＥがtdd-UL-DL-ConfigurationCommonを提供されていない場合において、ＰＲＡＣＨスロット内のＰＲＡＣＨオケージョンが、ＰＲＡＣＨスロット内のＳＳ／ＰＢＣＨブロックに先行せず、最後のＳＳ／ＰＢＣＨブロック受信シンボルから少なくともN_gapシンボル後に開始する場合、そのＰＲＡＣＨオケージョンは有効である。ここで、N_gapは仕様において規定されている。channelAccessMode=semistaticが提供された場合、ＵＥが送信しない次のチャネル占有時間の開始前の連続するシンボルのセットと重複しない。ＳＳ／ＰＢＣＨブロックの候補（candidate）ＳＳ／ＰＢＣＨブロックインデックスは、ＳＩＢ１内の又はServingCellConfigCommon内のssb-PositionsInBurstによって提供されるＳＳ／ＰＢＣＨブロックインデックスに対応する。
［規定２］
　ＵＥがtdd-UL-DL-ConfigurationCommonを提供されている場合、ＰＲＡＣＨスロット内のＰＲＡＣＨオケージョンは、以下の場合に有効である。
・そのＰＲＡＣＨオケージョンがＵＬシンボル内にある。又は、
・そのＰＲＡＣＨオケージョンがＰＲＡＣＨスロット内のＳＳ／ＰＢＣＨブロックに先行せず、最後のＤＬシンボルから少なくともN_gapシンボル後、且つ、最後のＳＳ／ＰＢＣＨブロックシンボルから少なくともN_gapシンボル後に、開始する。ここで、N_gapは仕様に規定される。もしchannelAccessMode=semistaticが提供された場合、そのＰＲＡＣＨオケージョンは、仕様に記載されているように、いかなる送信もあってはならない次のチャネル占有時間の開始前の連続するシンボルのセットと重複しない。ＳＳ／ＰＢＣＨブロックの候補ＳＳ／ＰＢＣＨブロックインデックスは、仕様に記載されているように、ＳＩＢ１内の又はServingCellConfigCommon内のssb-PositionsInBurstによって提供されるＳＳ／ＰＢＣＨブロックインデックスに対応する。 <Conditions for valid/invalid of PRACH occasion (valid conditions)>
All PRACH occasions are valid in paired spectrum (FDD) or SUL bands. In unpaired spectrum (TDD), PRACH occasions may comply with regulations 1 and 2 below.
[Regulation 1]
In case the UE is not provided with tdd-UL-DL-ConfigurationCommon, the PRACH occasion within the PRACH slot does not precede the SS/PBCH block within the 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. Here, N_gap is defined in the specifications. If channelAccessMode=semistatic is provided, there is no overlap with the set of consecutive symbols before the start of the next channel occupation 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.
[Regulation 2]
If the UE is provided with tdd-UL-DL-ConfigurationCommon, the PRACH occasion within the PRACH slot is valid in the following cases:
- The PRACH occasion is within the UL symbol. Or
- The PRACH occasion does not precede the SS/PBCH block in the PRACH slot, but starts at least N_gap symbols after the last DL symbol and at least N_gap symbols after the last SS/PBCH block symbol. Here, N_gap is defined in the specifications. If channelAccessMode=semistatic is provided, the PRACH occasion does not overlap with the set of consecutive symbols before the start of the next channel occupation time, where there should be no transmission, as stated in the specification. The candidate SS/PBCH block index of the SS/PBCH block corresponds to the SS/PBCH block index provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon, as described in the specification.
（ＣＢＲＡにおけるステップ４）
　Ｒｅｌ．１６　ＮＲのＲＡ手順におけるステップ４（Ｍｓｇ４）は、以下のステップ４動作に従う。 (Step 4 in CBRA)
Rel. Step 4 (Msg4) in the RA procedure of 16 NR follows the Step 4 operation below.
［ステップ４動作］
　ＵＥにＣ－ＲＮＴＩが提供されていない場合、ＲＡＲ　ＵＬグラントによってスケジュールされたＰＵＳＣＨ送信に応じて、ＵＥは、UE　contention　resolution　identityを含むＰＤＳＣＨをスケジュールし対応するＴＣＩ－ＲＮＴＩによってスクランブルされたＣＲＣを伴うＤＣＩフォーマット１＿０の検出を試みる。UE　contention　resolution　identityを含むＰＤＳＣＨの受信に応じて、ＵＥは、ＰＵＣＣＨ内においてＨＡＲＱ－ＡＣＫ情報を送信する。ＰＵＣＣＨ送信は、ＰＵＳＣＨ送信と同じアクティブＵＬ　ＢＷＰ内である。ＰＤＳＣＨ受信の最後のシンボルと、ＨＡＲＱ－ＡＣＫ情報を含み対応するＰＵＣＣＨ送信の最初のシンボルと、の間の最小時間は、N_T,1［msec］に等しい。N_T,1は、追加ＰＤＳＣＨ　ＤＭ－ＲＳが設定されている場合のＵＥ処理能力１のＰＤＳＣＨ処理時間に相当するN_T,1シンボルの継続時間である。μ=0に対し、ＵＥは、N_T,1=14を想定する。 [Step 4 operation]
If the UE is not provided with a C-RNTI, in response to the PUSCH transmission scheduled by the RAR UL grant, the UE shall schedule a PDSCH containing the UE contention resolution identity with a CRC scrambled by the corresponding TCI-RNTI. Attempt to detect DCI format 1_0. In response to receiving the PDSCH including the UE contention resolution identity, the UE transmits HARQ-ACK information in the PUCCH. PUCCH transmissions are within the same active UL BWP as PUSCH transmissions. The minimum time between the last symbol of PDSCH reception and the first symbol of the corresponding PUCCH transmission containing HARQ-ACK information is equal to N_T,1 [msec]. N_T,1 is the duration of N_T,1 symbol corresponding to the PDSCH processing time of UE processing capacity 1 when additional PDSCH DM-RS is configured. For μ=0, the UE assumes N_T,1=14.
　ＲＡＲ　ＵＬグラントによってスケジュールされたＰＵＳＣＨ送信に応じて、又は、対応するＲＡＲメッセージに提供されたＴＣ－ＲＮＴＩによってスクランブルされたＣＲＣを伴うＤＣＩフォーマット０＿０によってスケジュールされ対応するＰＵＳＣＨ再送に応じて、ＤＣＩフォーマットを検出する場合、ＵＥがそのＤＣＩフォーマットを伴うＰＤＣＣＨを受信したＣＯＲＥＳＥＴに対するＴＣＩ状態がＵＥに提供されているか否かに関わらず、ＵＥは、そのＤＣＩフォーマットを運ぶＰＤＣＣＨが、ＵＥによってＰＲＡＣＨ関連付けに用いられたＳＳ／ＰＢＣＨブロックに対するＤＭ－ＲＳアンテナポートquasi　co-location（ＱＣＬ）特性（properties）と同じＤＭ－ＲＳアンテナポートＱＣＬ特性を想定してもよい。 DCI format in response to a PUSCH transmission scheduled by RAR UL grant or in response to a corresponding PUSCH retransmission scheduled by DCI format 0_0 with CRC scrambled by TC-RNTI provided in the corresponding RAR message. If the UE detects that the PDCCH carrying that DCI format is used by the UE for PRACH association, regardless of whether the UE is provided with TCI status for the CORESET in which the UE received the PDCCH with that DCI format. The same DM-RS antenna port QCL properties as the DM-RS antenna port quasi co-location (QCL) properties for the SS/PBCH block may be assumed.
（ＲＡＲ受信）
　ＰＲＡＣＨ送信に応じて、ＵＥは、前述の上位レイヤによって制御されるウィンドウ中において、対応するＲＡ－ＲＮＴＩによってスクランブルされたＣＲＣを伴うＤＣＩフォーマット１＿０の検出を試みる。ＵＥがタイプ１－ＰＤＣＣＨ　ＣＳＳセットに対するＰＤＣＣＨを受信することを設定された最も早いＣＯＲＥＳＥＴの最初のシンボルにおいて、すなわち、ＰＲＡＣＨ送信に対応するＰＲＡＣＨオケージョンの最後のシンボルの少なくとも１シンボル後において、そのウィンドウは開始する。そのシンボル期間は、タイプ１－ＰＤＣＣＨ　ＣＳＳセットに対するＳＣＳに対応する。そのウィンドウの長さは、タイプ１－ＰＤＣＣＨ　ＣＳＳセットに対するＳＣＳに基づき、ra-responseWindowによってスロット数として提供される。 (RAR reception)
In response to the PRACH transmission, the UE attempts to detect DCI format 1_0 with the CRC scrambled by the corresponding RA-RNTI during the window controlled by the above-mentioned upper layers. In the first symbol of the earliest CORESET in which the UE is configured to receive a PDCCH for a type 1-PDCCH CSS set, i.e. at least one symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission, the window Start. The symbol period corresponds to the SCS for Type 1-PDCCH CSS set. The length of the window is based on the SCS for type 1-PDCCH CSS set and is provided by ra-responseWindow as the number of slots.
　もしＵＥが、対応するＲＡ－ＲＮＴＩによってスクランブルされたＣＲＣと、ＵＥがＰＲＡＣＨを送信したsystem　frame　number（ＳＦＮ）のleast　significant　bits（ＬＳＢｓ）と同じ、ＤＣＩフォーマット内のＳＦＮフィールドのＬＳＢｓと、を伴うそのＤＣＩフォーマット１＿０を検出し、且つ、ＵＥが、対応するＰＤＳＣＨ内のトランスポートブロックを受信した場合、ＵＥが、そのＤＣＩフォーマット１＿０を伴うＰＤＣＣＨを受信するＣＯＲＥＳＥＴ用のＴＣＩ状態（TCI-State）を提供されるか否かに関わらず、ＵＥがＰＲＡＣＨの関連付けに用いる、ＳＳ／ＰＢＣＨブロック又はＣＳＩ－ＲＳリソースに関して、ＵＥは、同じＤＭＲＳアンテナポートＱＣＬ特性（properties）を想定してもよい。 If the UE has a CRC scrambled by the corresponding RA-RNTI and the LSBs of the SFN field in the DCI format are the same as the least significant bits (LSBs) of the system frame number (SFN) for which the UE sent the PRACH. If the UE detects the DCI format 1_0 and receives the transport block in the corresponding PDSCH, the UE determines the TCI state (TCI-State) for the CORESET in which the UE receives the PDCCH with the DCI format 1_0. The UE may assume the same DMRS antenna port QCL properties for the SS/PBCH block or CSI-RS resources that the UE uses for PRACH association, whether provided or not.
　もしＵＥが、ＳｐＣｅｌｌに対するＣＦＲＡ手順をトリガするＰＤＣＣＨオーダによって開始されるＰＲＡＣＨ送信に応じて、対応するＲＡ－ＲＮＴＩによってスクランブルされたＣＲＣを伴うＤＣＩフォーマット１＿０の検出を試みる場合、ＵＥは、そのＤＣＩフォーマット１＿０を含むＰＤＣＣＨと、そのＰＤＣＣＨオーダと、が同じＤＭＲＳアンテナポートＱＣＬ特性（properties）を有すると想定してもよい。もしＵＥが、セカンダリセルに対するＣＦＲＡ手順をトリガするＰＤＣＣＨオーダによって開始されるＰＲＡＣＨ送信に応じて、対応するＲＡ－ＲＮＴＩによってスクランブルされたＣＲＣを伴うＤＣＩフォーマット１＿０の検出を試みる場合、ＵＥは、そのＤＣＩフォーマット１＿０を含むＰＤＣＣＨの受信のためのタイプ１－ＰＤＣＣＨ　ＣＳＳセットに関連付けられたＣＯＲＥＳＥＴのＤＭＲＳアンテナポートＱＣＬ特性（properties）を想定してもよい。 If the UE attempts to detect a DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order triggering a CFRA procedure for the SpCell, the UE detects that DCI format It may be assumed that the PDCCH including 1_0 and its PDCCH order have the same DMRS antenna port QCL properties. If the UE attempts to detect a DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order that triggers a CFRA procedure for the secondary cell, the UE The DMRS antenna port QCL properties of the CORESET associated with the Type 1-PDCCH CSS set for reception of PDCCHs including format 1_0 may be assumed.
　ＲＡＲ　ＵＬグラントは、周波数ホッピングフラグフィールドと、ＰＵＳＣＨ周波数リソース配置（allocation）フィールドと、ＰＵＳＣＨ時間リソース配置フィールドと、modulation　and　coding　scheme（ＭＣＳ）フィールドと、ＰＵＳＣＨ用ＴＰＣコマンドフィールドと、ＣＳＩリクエストフィールドと、チャネルアクセス－cyclic　prefix延長（CPext）フィールドと、の少なくとも１つを含んでもよい。 The RAR UL grant includes a frequency hopping flag field, a PUSCH frequency resource allocation field, a PUSCH time resource allocation field, a modulation and coding scheme (MCS) field, a PUSCH TPC command field, a CSI request field, Channel access may include at least one of a cyclic prefix extension (CPext) field.
（ＰＲＡＣＨの上りリンクカバレッジ改善）
　マルチＰＲＡＣＨ送信の以下の２つのケース／タイプが検討されている。 (PRACH uplink coverage improvement)
The following two cases/types of multi-PRACH transmission are considered.
［ケース１／タイプ１マルチＰＲＡＣＨ送信］
　ＵＥは、ｎ個のランダムアクセスオケージョン（ＲＯ）／ＲＯリソース上においてＭｓｇ１を繰り返し送信する。その後、ＵＥは、設定されたタイプ１ＰＤＣＣＨオケージョンにおけるＭｓｇ２の検出を待つ。本開示において、ｎ個のＲＯ／ＲＯリソースにおけるプリアンブルの繰り返し送信を、ＲＯグループと呼ぶことがある。図１Ａは、タイプ１マルチＰＲＡＣＨ送信のタイミングの一例を示す。この例において、ＲＯグループのサイズ（ＲＯグループ内のＲＯの数）は、ｎである。１つのＲＯグループの後に、１つのＲＡＲウィンドウが開始される。 [Case 1/Type 1 multi-PRACH transmission]
The UE repeatedly transmits Msg1 on n random access occasions (RO)/RO resources. The UE then waits for the detection of Msg2 in the configured Type 1 PDCCH occasion. In this disclosure, repeated transmission of preambles in n RO/RO resources may be referred to as an RO group. FIG. 1A shows an example of timing for type 1 multi-PRACH transmission. In this example, the size of the RO group (number of ROs in the RO group) is n. After one RO group, one RAR window is started.
［ケース２／タイプ２マルチＰＲＡＣＨ送信］
　ＵＥは、ｎ個のランダムアクセスオケージョン（ＲＯ）リソース上においてＭｓｇ１を繰り返し送信する。各ＲＯ上のＭｓｇ１の送信の後、ＵＥは、タイプ１ＰＤＣＣＨオケージョンにおけるＭｓｇ２の検出を待つ。図１Ｂは、タイプ２マルチＰＲＡＣＨ送信のタイミングの一例を示す。この例において、ＲＯグループのサイズ（ＲＯグループ内のＲＯの数）は、ｎである。各ＲＯの後に、１つのＲＡＲウィンドウが開始される。 [Case 2/Type 2 multi-PRACH transmission]
The UE repeatedly transmits Msg1 on n random access occasion (RO) resources. After the transmission of Msg1 on each RO, the UE waits for the detection of Msg2 on type 1 PDCCH occasions. FIG. 1B shows an example of timing for type 2 multi-PRACH transmission. In this example, the size of the RO group (number of ROs in the RO group) is n. After each RO, one RAR window is started.
（Ｒｅｌ．１７　Ｍｓｇ３繰り返し）
　ＵＥは、ＲＳＲＰに基づいて、Ｍｓｇ３繰り返しを適用するかを決定する。Ｍｓｇ繰り返しが設定され、且つ、ＤＬパスロス参照のＲＳＲＰがrsrp-ThresholdMsg3（閾値）より小さい場合、ＭＡＣエンティティは、現在のランダムアクセス（ＲＡ）手順にＭｓｇ３繰り返しが適用可能であると想定する。 (Rel.17 Msg3 repeat)
The UE decides whether to apply Msg3 repetition based on RSRP. If Msg repetition is configured and the RSRP of DL path loss reference is less than rsrp-ThresholdMsg3, the MAC entity assumes that Msg3 repetition is applicable to the current random access (RA) procedure.
　ＵＥは、個別のＰＲＡＣＨリソースを介してＭｓｇ３ＰＵＳＣＨ繰り返しを要求できる。利用可能なＲＡリソースの１つ以上のセットがあり、且つ、その１つ以上のセットの１つが、このＲＡ手順をトリガする全ての機能の指示に用いられる場合と、このＲＡ手順をトリガする全ての機能のサブセットに対する指示を設定される、利用可能なＲＡリソースの１つ以上のセットがある場合と、において、ＭＡＣエンティティは、ＲＡリソースを選択する。Ｍｓｇ３繰り返し指示がＲＡリソースのセットのために設定される場合において、Ｍｓｇ３繰り返しが利用可能でない場合、ＭＡＣエンティティは、そのＲＡリソースのセットを、ＲＡＣＨ手順に利用可能でないと見なす。 The UE can request Msg3PUSCH repetition via a separate PRACH resource. If there is one or more sets of RA resources available, and one of the one or more sets is used to direct all functions that trigger this RA procedure, and all functions that trigger this RA procedure The MAC entity selects an RA resource if and when there is one or more sets of available RA resources configured with instructions for a subset of the functionality of the MAC entity. If Msg3 repetition indication is configured for a set of RA resources, and Msg3 repetition is not available, the MAC entity considers that set of RA resources not available for RACH procedures.
　機能ごとにＲＡリソースが分割され（partitioned）てもよい。機能は、Ｍｓｇ３繰り返し、reduced　capacity（ＲｅｄＣａｐ）、small　data　transmission（ＳＤＴ）、ＲＡＮ　slicing、の少なくとも１つを含んでもよい。 RA resources may be partitioned for each function. The functionality may include at least one of Msg3 repetition, reduced capacity (RedCap), small data transmission (SDT), and RAN slicing.
　基地局によって送られるＳＩＢ１内において、以下が通知される。
・各機能の優先度（priority、featurePriorities-r17）。この優先度は、ある機能が１つより多いFeatureCombinationPreambles（機能組み合わせプリアンブル設定）へマップされる場合にＵＥがどのFeatureCombinationPreamblesを用いるかの決定に用いられる。
・追加ＲＯ設定。その設定は、利用可能な機能（それは、複数の機能に関連付けられてもよい）、ＲＡリソース（例えば、プリアンブルインデックス）、ＲＯを区別するためのマスクインデックス、を含む。 In SIB1 sent by the base station, the following is announced:
-Priority of each feature (priority, featurePriorities-r17). This priority is used to determine which FeatureCombinationPreambles the UE uses if a feature is mapped to more than one FeatureCombinationPreambles.
・Additional RO settings. The configuration includes available capabilities (which may be associated with multiple capabilities), RA resources (eg, preamble index), and a mask index for distinguishing ROs.
　ＵＥは、その機能に依存して、使用するＲＯを決定する。 The UE decides which RO to use depending on its capabilities.
　ＳＩＢ１は、ServingCellConfigCommonSIBを含む。それは、UplinkConfigCommonSIBを含む。それは、BWP-UplinkCommon（ＵＬ　ＢＷＰ共通設定）を含む。 SIB1 includes ServingCellConfigCommonSIB. It includes UplinkConfigCommonSIB. It includes BWP-UplinkCommon (UL BWP common settings).
　BWP-UplinkCommonは、ＲＡＣＨ共通設定（RACH-ConfigCommon又はMsgA-ConfigCommon）、additionalRACH-ConfigList-r17（追加ＲＡＣＨ設定リスト）を含んでもよい。additionalRACH-ConfigList-r17は、rsrp-ThresholdMsg3-r17（閾値）を含んでもよい。 BWP-UplinkCommon may include RACH common settings (RACH-ConfigCommon or MsgA-ConfigCommon) and additionalRACH-ConfigList-r17 (additional RACH configuration list). additionalRACH-ConfigList-r17 may include rsrp-ThresholdMsg3-r17 (threshold).
　ＲＡＣＨ共通設定は、FeatureCombinationPreamblesを含んでもよい。FeatureCombinationPreamblesは、プリアンブルの１つのセット（パーティション）を１つの機能組み合わせに関連付ける。FeatureCombinationPreamblesは、FeatureCombination（機能組み合わせ設定）、startPreambleForThisPartition（最初のプリアンブルのインデックス）、numberOfPreamblesPerSSB-ForThisPartition（プリアンブル数）、ssb-SharedRO-MaskIndex-r17（ＰＲＡＣＨマスクインデックス）、を含んでもよい。FeatureCombinationは、redCap（ＲｅｄＣａｐ）、smallData（ＳＤＴ）、sliceGroup（ＲＡＮ　slicing）、msg3-Repetition（Ｍｓｇ３繰り返し）、の少なくとも１つを含む。パーティションは、最初のプリアンブルのインデックスと、プリアンブル数と、によって与えられる。 The RACH common settings may include FeatureCombinationPreambles. FeatureCombinationPreambles associates one set (partition) of preambles with one feature combination. FeatureCombinationPreambles may include FeatureCombination (feature combination setting), startPreambleForThisPartition (index of first preamble), numberOfPreamblesPerSSB-ForThisPartition (number of preambles), and ssb-SharedRO-MaskIndex-r17 (PRACH mask index). FeatureCombination includes at least one of redCap (RedCap), smallData (SDT), sliceGroup (RAN slicing), and msg3-Repetition (Msg3 repetition). The partition is given by the index of the first preamble and the preamble number.
　ＰＲＡＣＨマスクインデックスによって、利用可能なＲＯが明示的に設定される。図２は、ＰＲＡＣＨマスクインデックスと、ＳＳＢの許可されるＰＲＡＣＨオケージョン（ＲＯ）と、の関係（ＭＡＣプロトコル仕様／ＰＲＡＣＨマスクインデックス値のテーブル）の一例を示す。ＰＲＡＣＨオケージョンインデックス１から８の少なくとも１つが設定されることができる。 Available ROs are explicitly set by the PRACH mask index. FIG. 2 shows an example of the relationship (MAC protocol specification/PRACH mask index value table) between the PRACH mask index and the allowed PRACH occasions (ROs) of SSB. At least one of PRACH occasion indexes 1 to 8 may be configured.
　Ｍｓｇ３繰り返しの数は、ＲＡＲ　ＵＬグラント内のmodulation　and　coding　scheme（ＭＣＳ）フィールドの２　most　significant　bit（ＭＳＢ）（上位２ビット）によって指示される。 The number of Msg3 repetitions is indicated by the 2 most significant bits (MSB) (upper 2 bits) of the modulation and coding scheme (MCS) field in the RAR UL grant.
　図３は、ＭＣＳ情報フィールドの２ＭＳＢの値（コードポイント）と、繰り返し数Ｋと、の関係（テーブル）の一例を示す。ＰＵＳＣＨ繰り返しタイプＡにおいて、ＲＡＲ　ＵＬグラントによってスケジュールされるＰＵＳＣＨを送信する場合、そのＲＡＲ　ＵＬグラントのＭＣＳ情報フィールドの２ＭＳＢは、上位レイヤパラメータnumberOfMsg3Repetitionsが設定されたか否かに基づき、図３のテーブルに従い、繰り返し数Ｋの決定のためのコードポイントを提供する。transport　block　size（ＴＢＳ）決定に用いられるスロット数Ｎは１に等しい。 FIG. 3 shows an example of the relationship (table) between the 2MSB value (code point) of the MCS information field and the number of repetitions K. In PUSCH repetition type A, when transmitting a PUSCH scheduled by a RAR UL grant, the 2MSB of the MCS information field of the RAR UL grant is set according to the table in FIG. 3, based on whether the upper layer parameter numberOfMsg3Repetitions is set. Provide code points for determining the number of iterations K. The number of slots N used for transport block size (TBS) determination is equal to one.
　ＰＵＳＣＨ繰り返しタイプＢにおいて、ＴＣ－ＲＮＴＩによってスクランブルされるＣＲＣを伴うＤＣＩフォーマット０＿０によってスケジュールされるＰＵＳＣＨを送信する場合、そのＤＣＩフォーマットのＭＣＳ情報フィールドの２ＭＳＢは、上位レイヤパラメータnumberOfMsg3Repetitionsが設定されたか否かに基づき、図３のテーブルに従い、繰り返し数Ｋの決定のためのコードポイントを提供する。ＴＢＳ決定に用いられるスロット数Ｎは１に等しい。 In PUSCH repetition type B, when transmitting a PUSCH scheduled by DCI format 0_0 with CRC scrambled by TC-RNTI, the 2MSB of the MCS information field of that DCI format determines whether the upper layer parameter numberOfMsg3Repetitions is set or not. Based on the table of FIG. 3, we provide code points for determining the number of iterations K. The number of slots N used for TBS determination is equal to 1.
　Ｒｅｌ．１７において、Ｍｓｇ３繰り返しのＵＥ能力が導入され、Ｒｅｌ．１８においては、Ｍｓｇ３繰り返しのＵＥ能力の導入が検討されている。ここで、以下の問題が考えられる。 Rel. In Rel.17, the UE capability of Msg3 repetition was introduced and Rel. 18, the introduction of the UE capability of repeating Msg3 is being considered. Here, the following problems can be considered.
［問題１］
　ＵＥがこれらの両方の能力を報告するか、これらの能力の間に関係があるか、もしＵＥがこれらの両方の能力を有する場合にＭｓｇ１繰り返し及びＭｓｇ３繰り返しの２つの機能が共に働くか、などが問題となる。 [Problem 1]
whether the UE reports both these capabilities, whether there is a relationship between these capabilities, whether the two functions of Msg1 repeat and Msg3 repeat work together if the UE has both these capabilities, etc. becomes a problem.
［問題２］
　もしこれらの２つの機能が共に働く場合、既存のＭｓｇ３繰り返し動作に関する影響があるかが問題となる。例えば、Ｍｓｇ３繰り返しのビーム、Ｍｓｇ３繰り返しの数、各ＲＡＲに対応する各Ｍｓｇ３に対するＭｓｇ３繰り返しの関係、などが問題となる。複数のＭｓｇ１繰り返しに対して１つのＲＡＲが送信されるケース１と、複数のＭｓｇ１繰り返しに対して複数のＲＡＲが送信されるケース２と、が検討されてもよい。 [Problem 2]
If these two functions work together, the question is whether there is an impact on the existing Msg3 repeat operation. For example, issues include the beam of Msg3 repetitions, the number of Msg3 repetitions, and the relationship of Msg3 repetitions to each Msg3 corresponding to each RAR. Case 1, where one RAR is sent for multiple Msg1 repetitions, and Case 2, where multiple RARs are sent for multiple Msg1 repetitions, may be considered.
　このように、Ｍｓｇ１／３の繰り返しに関する動作が明らかでない。このような動作が明らかでなければ、スループットの低下などを招くおそれがある。 In this way, the operation regarding the repetition of Msg1/3 is not clear. If such operations are not clear, there is a risk that throughput will be reduced.
　そこで、本発明者らは、ランダムアクセス手順における繰り返しの動作を着想した。 Therefore, the present inventors came up with the idea of repeating operations in the random access procedure.
　以下、本開示に係る実施形態について、図面を参照して詳細に説明する。各実施形態に係る無線通信方法は、それぞれ単独で適用されてもよいし、組み合わせて適用されてもよい。 Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. The wireless communication methods according to each embodiment may be applied singly or in combination.
　本開示において、「Ａ／Ｂ」及び「Ａ及びＢの少なくとも一方」は、互いに読み替えられてもよい。また、本開示において、「Ａ／Ｂ／Ｃ」は、「Ａ、Ｂ及びＣの少なくとも１つ」を意味してもよい。 In the present disclosure, "A/B" and "at least one of A and B" may be read interchangeably. Furthermore, in the present disclosure, "A/B/C" may mean "at least one of A, B, and C."
　本開示において、アクティベート、ディアクティベート、指示（又は指定（indicate））、選択（select）、設定（configure）、更新（update）、決定（determine）などは、互いに読み替えられてもよい。本開示において、サポートする、制御する、制御できる、動作する、動作できるなどは、互いに読み替えられてもよい。 In the present disclosure, "activate", "deactivate", "indicate", "select", "configure", "update", "determine", etc. may be read interchangeably. In this disclosure, supporting, controlling, being able to control, operating, capable of operating, etc. may be read interchangeably.
　本開示において、無線リソース制御（Radio　Resource　Control（ＲＲＣ））、ＲＲＣパラメータ、ＲＲＣメッセージ、上位レイヤパラメータ、情報要素（ＩＥ）、設定などは、互いに読み替えられてもよい。本開示において、Medium　Access　Control制御要素（ＭＡＣ　Control　Element（ＣＥ））、更新コマンド、アクティベーション／ディアクティベーションコマンドなどは、互いに読み替えられてもよい。 In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, upper layer parameters, information elements (IEs), settings, etc. may be read interchangeably. In the present disclosure, the terms Medium Access Control Element (CE), update command, activation/deactivation command, etc. may be read interchangeably.
　本開示において、上位レイヤシグナリングは、例えば、Radio　Resource　Control（ＲＲＣ）シグナリング、Medium　Access　Control（ＭＡＣ）シグナリング、ブロードキャスト情報などのいずれか、又はこれらの組み合わせであってもよい。 In the present disclosure, the upper layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof.
　本開示において、ＭＡＣシグナリングは、例えば、ＭＡＣ制御要素（MAC　Control　Element（ＭＡＣ　ＣＥ））、ＭＡＣ　Protocol　Data　Unit（ＰＤＵ）などを用いてもよい。ブロードキャスト情報は、例えば、マスタ情報ブロック（Master　Information　Block（ＭＩＢ））、システム情報ブロック（System　Information　Block（ＳＩＢ））、最低限のシステム情報（Remaining　Minimum　System　Information（ＲＭＳＩ））、その他のシステム情報（Other　System　Information（ＯＳＩ））などであってもよい。 In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), or the like. Broadcast information includes, for example, a master information block (MIB), a system information block (SIB), a minimum system information (RMSI), and other system information ( Other System Information (OSI)) may also be used.
　本開示において、物理レイヤシグナリングは、例えば、下りリンク制御情報（Downlink　Control　Information（ＤＣＩ））、上りリンク制御情報（Uplink　Control　Information（ＵＣＩ））などであってもよい。 In the present disclosure, the physical layer signaling may be, for example, downlink control information (DCI), uplink control information (UCI), etc.
　本開示において、インデックス、識別子（Identifier（ＩＤ））、インディケーター、リソースＩＤなどは、互いに読み替えられてもよい。本開示において、シーケンス、リスト、セット、グループ、群、クラスター、サブセットなどは、互いに読み替えられてもよい。 In this disclosure, an index, an identifier (ID), an indicator, a resource ID, etc. may be read interchangeably. In this disclosure, sequences, lists, sets, groups, groups, clusters, subsets, etc. may be used interchangeably.
　本開示において、パネル、ＵＥパネル、パネルグループ、ビーム、ビームグループ、プリコーダ、Uplink（ＵＬ）送信エンティティ、送受信ポイント（Transmission/Reception　Point（ＴＲＰ））、基地局、空間関係情報（Spatial　Relation　Information（ＳＲＩ））、空間関係、ＳＲＳリソースインディケーター（SRS　Resource　Indicator（ＳＲＩ））、制御リソースセット（COntrol　REsource　SET（ＣＯＲＥＳＥＴ））、Physical　Downlink　Shared　Channel（ＰＤＳＣＨ）、コードワード（Codeword（ＣＷ））、トランスポートブロック（Transport　Block（ＴＢ））、参照信号（Reference　Signal（ＲＳ））、アンテナポート（例えば、復調用参照信号（DeModulation　Reference　Signal（ＤＭＲＳ））ポート）、アンテナポートグループ（例えば、ＤＭＲＳポートグループ）、グループ（例えば、空間関係グループ、符号分割多重（Code　Division　Multiplexing（ＣＤＭ））グループ、参照信号グループ、ＣＯＲＥＳＥＴグループ、Physical　Uplink　Control　Channel（ＰＵＣＣＨ）グループ、ＰＵＣＣＨリソースグループ）、リソース（例えば、参照信号リソース、ＳＲＳリソース）、リソースセット（例えば、参照信号リソースセット）、ＣＯＲＥＳＥＴプール、下りリンクのTransmission　Configuration　Indication　state（ＴＣＩ状態）（ＤＬ　ＴＣＩ状態）、上りリンクのＴＣＩ状態（ＵＬ　ＴＣＩ状態）、統一されたＴＣＩ状態（unified　TCI　state）、共通ＴＣＩ状態（common　TCI　state）、擬似コロケーション（Quasi-Co-Location（ＱＣＬ））、ＱＣＬ想定などは、互いに読み替えられてもよい。 In this disclosure, a panel, a UE panel, a panel group, a beam, a beam group, a precoder, an uplink (UL) transmitting entity, a transmission/reception point (TRP), a base station, and a spatial relation information (SRI) are described. )), spatial relationship, SRS resource indicator (SRI), control resource set (CONtrol REsource SET (CORESET)), Physical Downlink Shared Channel (PDSCH), codeword (CW), transport Block (Transport Block (TB)), reference signal (RS), antenna port (e.g. demodulation reference signal (DMRS) port), antenna port group (e.g. DMRS port group), groups (e.g., spatial relationship groups, Code Division Multiplexing (CDM) groups, reference signal groups, CORESET groups, Physical Uplink Control Channel (PUCCH) groups, PUCCH resource groups), resources (e.g., reference signal resources, 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 Unified TCI state, common TCI state, quasi-co-location (QCL), QCL assumption, etc. may be read interchangeably.
　本開示において、ＳＳＢ／ＣＳＩ－ＲＳのインデックス／インディケータ、ビームインデックス、ＴＣＩ状態、は互いに読み替えられてもよい。 In the present disclosure, the SSB/CSI-RS index/indicator, beam index, and TCI state may be read interchangeably.
（無線通信方法）
　各実施形態において、ＲＡＣＨリソース、ＲＡリソース、ＰＲＡＣＨプリアンブル、オケージョン、ＲＡＣＨオケージョン（ＲＯ）、ＰＲＡＣＨオケージョン、繰り返しリソース、繰り返し設定リソース、ＲＯ／繰り返しのために設定されたリソース、時間インスタンス及び周波数インスタンス、時間リソース及び周波数リソース、ＲＯ／プリアンブルのリソース、繰り返し、は互いに読み替えられてもよい。各実施形態において、期間、周期、フレーム、サブフレーム、スロット、シンボル、オケージョン、ＲＯ、は互いに読み替えられてもよい。 (Wireless communication method)
In each embodiment, RACH resource, RA resource, PRACH preamble, occasion, RACH occasion (RO), PRACH occasion, repetition resource, repetition configuration resource, resource configured for RO/repetition, time instance and frequency instance, time Resources and frequency resources, RO/preamble resources, and repetition may be read interchangeably. In each embodiment, period, period, frame, subframe, slot, symbol, occasion, and RO may be read interchangeably.
　各実施形態において、ＰＤＣＣＨオーダ、ＰＤＣＣＨオーダＤＣＩ、ＤＣＩフォーマット１＿０、メッセージ（Ｍｓｇ）０、は互いに読み替えられてもよい。各実施形態において、ＰＲＡＣＨ、プリアンブル、ＰＲＡＣＨプリアンブル、系列、プリアンブルフォーマット、Ｍｓｇ１、は互いに読み替えられてもよい。各実施形態において、ＰＲＡＣＨに対する応答、ＲＡＲ、Ｍｓｇ２、ＭｓｇＢ、Ｍｓｇ４、ＢＦＲに対する基地局応答、応答をスケジュールするＤＣＩ、は互いに読み替えられてもよい。各実施形態において、ランダムアクセス手順におけるＰＲＡＣＨ以外の送信、Ｍｓｇ３、ＲＡＲによってスケジュールされるＰＵＳＣＨ、Ｍｓｇ４に対するＨＡＲＱ－ＡＣＫ／ＰＵＣＣＨ、ＭｓｇＡ　ＰＵＳＣＨ、は互いに読み替えられてもよい。各実施形態において、Ｍｓｇ３、ＲＡＲ　ＵＬグラントによってスケジュールされるＰＵＳＣＨ、RRC　connection　request、は互いに読み替えられてもよい。各実施形態において、Ｍｓｇ４、contention　resolution、RRC　connection　setup、UE　contention　resolution　identityを伴うＰＤＳＣＨ、は互いに読み替えられてもよい。 In each embodiment, PDCCH order, PDCCH order DCI, DCI format 1_0, and message (Msg) 0 may be read interchangeably. In each embodiment, PRACH, preamble, PRACH preamble, sequence, preamble format, and Msg1 may be read interchangeably. In each embodiment, the response to PRACH, the base station response to RAR, Msg2, MsgB, Msg4, and BFR, and the DCI that schedules the response may be read interchangeably. In each embodiment, transmissions other than PRACH in the random access procedure, Msg3, PUSCH scheduled by RAR, HARQ-ACK/PUCCH for Msg4, and MsgA PUSCH may be interchanged. In each embodiment, Msg3, PUSCH scheduled by RAR UL grant, and RRC connection request may be interchanged. In each embodiment, Msg4, contention resolution, RRC connection setup, and PDSCH with UE contention resolution identity may be interchanged.
　各実施形態において、ビーム、ＳＳＢ、ＳＳＢインデックス、は互いに読み替えられてもよい。各実施形態において、ＤＬパスロス参照、ＰＬ－ＲＳ、ＳＳＢ、ＣＳＩ－ＲＳは互いに読み替えられてもよい。 In each embodiment, beam, SSB, and SSB index may be read interchangeably. In each embodiment, the DL path loss reference, PL-RS, SSB, and CSI-RS may be read interchangeably.
　各実施形態において、繰り返し期間（period）、繰り返し設定（configuration）期間、繰り返し周期（periodicity）、繰り返しサイクル、は互いに読み替えられてもよい。 In each embodiment, the terms repeat period, repeat configuration period, repeat period, and repeat cycle may be interchanged.
　各実施形態において、ランダムアクセス（ＲＡ）手順、ＣＦＲＡ／ＣＢＲＡ、４ステップＲＡＣＨ／２ステップＲＡＣＨ、特定種類のランダムアクセス手順、特定のＰＲＡＣＨフォーマットを用いるランダムアクセス手順、ＰＤＣＣＨオーダによって開始されるランダムアクセス手順、ＰＤＣＣＨオーダによって開始されないランダムアクセス手順、上位レイヤによって開始されるランダムアクセス手順、は互いに読み替えられてもよい。 In each embodiment, a random access (RA) procedure, CFRA/CBRA, 4-step RACH/2-step RACH, a specific type of random access procedure, a random access procedure using a specific PRACH format, a random access procedure initiated by a PDCCH order. , a random access procedure not initiated by a PDCCH order, and a random access procedure initiated by an upper layer may be interchanged.
　各実施形態は、以下のケース１及び２（前述のケース１及びケース２）を想定してもよい。
［ケース１］
　Ｍｓｇ１の複数繰り返しに対し、１つのＲＡＲが送信されてもよい（図４Ａ）。
［ケース２］
　Ｍｓｇ１の複数繰り返しの各繰り返しに対し、１つのＲＡＲが送信されてもよい（図４Ｂ）。 Each embodiment may assume the following cases 1 and 2 (case 1 and case 2 described above).
[Case 1]
One RAR may be sent for multiple repetitions of Msg1 (FIG. 4A).
[Case 2]
One RAR may be sent for each iteration of multiple iterations of Msg1 (FIG. 4B).
＜実施形態＃１＞
　ＵＥは、Ｍｓｇ１の繰り返しの能力に関する第１能力情報と、Ｍｓｇ３の繰り返しの能力に関する第２能力情報と、を送信してもよい。ＵＥは、前記第１能力情報及び前記第２能力情報に基づいて、前記Ｍｓｇ１の繰り返し及び前記Ｍｓｇ３の繰り返しを含む第１ランダムアクセス手順を行うか、前記メッセージ１の繰り返し及び前記メッセージ３の繰り返しの少なくとも１つを含まない第２ランダムアクセス手順を行うか、を決定してもよい。 <Embodiment #1>
The UE may transmit first capability information regarding the repeat capability of Msg1 and second capability information regarding the repeat capability of Msg3. Based on the first capability information and the second capability information, the UE performs a first random access procedure including repeating Msg1 and repeating Msg3, or performs a first random access procedure including repeating Message 1 and repeating Message 3. It may be determined whether to perform a second random access procedure that does not include at least one.
《実施形態＃１ａ》
　この実施形態は、Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しの２つの機能が共に働くかに関する。 《Embodiment #1a》
This embodiment concerns how the two functions of Msg1 repeat and Msg3 repeat work together.
《実施形態＃１ａ－１》
　Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しの合同動作（joint　operation）が、サポートされなくてもよい。 《Embodiment #1a-1》
A joint operation of Msg1 and Msg3 repetitions may not be supported.
　ＲＡＣＨリソースのタイプとして、以下のいくつかのタイプの内の少なくとも１つのタイプがあってもよい。
・Ｍｓｇ１繰り返しもＭｓｇ３繰り返しも伴わないＲＡＣＨ手順のためのＲＡＣＨリソースの１つ以上のセット。
・Ｍｓｇ３繰り返しを伴いＭｓｇ１繰り返しを伴わないＲＡＣＨ手順のためのＲＡＣＨリソースの１つ以上のセット。
・Ｍｓｇ１繰り返しを伴いＭｓｇ３繰り返しを伴わないＲＡＣＨ手順のためのＲＡＣＨリソースの１つ以上のセット。 The type of RACH resource may be at least one of the following types.
- One or more sets of RACH resources for RACH procedures without Msg1 or Msg3 repetitions.
- One or more sets of RACH resources for RACH procedures with Msg3 repetitions and without Msg1 repetitions.
- One or more sets of RACH resources for RACH procedures with Msg1 repetitions and without Msg3 repetitions.
　Ｍｓｇ１／Ｍｓｇ３の繰り返しを伴うＲＡＣＨ手順のためのＲＡＣＨリソースの複数のセットの間において、Ｍｓｇ１／Ｍｓｇ３の繰り返しの数が異なってもよい。 The number of Msg1/Msg3 repetitions may be different between multiple sets of RACH resources for RACH procedures with Msg1/Msg3 repetitions.
［例１］
　ＵＥは、Ｍｓｇ１繰り返しの能力と、Ｍｓｇ３繰り返しの能力と、を同時に報告すると想定しない、と規定されてもよい。 [Example 1]
It may be specified that the UE is not assumed to report Msg1 repeat capability and Msg3 repeat capability at the same time.
［例２］
　Ｍｓｇ１繰り返しの能力と、Ｍｓｇ３繰り返しの能力と、の両方を報告するＵＥは、ある条件に基づいて、１つのＲＡＣＨ手順内において、Ｍｓｇ１繰り返しのみを行うか、Ｍｓｇ３繰り返しのみを行うか、を決定してもよい。例えば、その条件は、ＳＳＢのＲＳＲＰの条件であってもよい。この場合、ＵＥは、以下のいくつかのＵＥ動作の内の少なくとも１つのＵＥ動作に従ってもよい。 [Example 2]
A UE that reports both Msg1 repetition capability and Msg3 repetition capability determines whether to perform only Msg1 repetition or only Msg3 repetition within one RACH procedure based on a certain condition. You can. For example, the condition may be an RSRP condition of SSB. In this case, the UE may follow at least one of the following several UE actions:
［ＵＥ動作１］
　選択されたＳＳＢのＲＳＲＰが、範囲１内である場合、ＵＥは、その後のＲＡＣＨ手順に対して、Ｍｓｇ１繰り返しのみが適用される、と判定する。例えば、範囲１は、そのＲＳＲＰが、閾値１よりも小さいことと、閾値２よりも大きいことと、の少なくとも１つであってもよい。 [UE operation 1]
If the RSRP of the selected SSB is within range 1, the UE determines that only Msg1 repetitions are applied for subsequent RACH procedures. For example, range 1 may have an RSRP of at least one of smaller than threshold 1 and larger than threshold 2.
［ＵＥ動作２］
　選択されたＳＳＢのＲＳＲＰが、範囲２内である場合、ＵＥは、その後のＲＡＣＨ手順に対して、Ｍｓｇ３繰り返しのみが適用される、と判定する。例えば、範囲２は、そのＲＳＲＰが、閾値３よりも小さいことと、閾値４よりも大きいことと、の少なくとも１つであってもよい。 [UE operation 2]
If the RSRP of the selected SSB is within range 2, the UE determines that only Msg3 repetitions are applied for subsequent RACH procedures. For example, range 2 may have an RSRP of at least one of smaller than threshold 3 and larger than threshold 4.
［ＵＥ動作３］
　選択されたＳＳＢのＲＳＲＰが、範囲３内である場合、ＵＥは、その後のＲＡＣＨ手順に対して、Ｍｓｇ１繰り返しもＭｓｇ３繰り返しも適用されない、と判定する。例えば、範囲３は、そのＲＳＲＰが、閾値５よりも大きいこと、であってもよい。
・範囲１／２／３／閾値１／２／３／４／５は、仕様において定義されてもよいし、ＰＢＣＨ／ＳＩＢ１　ＰＤＳＣＨ／ＲＲＣ　ＩＥを介し、基地局によって指示されてもよい。 [UE operation 3]
If the RSRP of the selected SSB is within range 3, the UE determines that neither Msg1 nor Msg3 repetitions are applied for subsequent RACH procedures. For example, range 3 may be that the RSRP is greater than threshold 5.
- Range 1/2/3/threshold 1/2/3/4/5 may be defined in the specification or may be indicated by the base station via the PBCH/SIB1 PDSCH/RRC IE.
　図５は、実施形態＃１ａ－１に係るＤＬパスロス参照のＲＳＲＰに対するＲＡＣＨ手順を一例を示す。Ｒｅｌ．１６の２ステップＲＡＣＨの能力を有するＵＥは、ＲＳＲＰがrsrp-ThresholdMsgA以上である場合、２ステップＲＡＣＨを適用する。 FIG. 5 shows an example of the RACH procedure for RSRP with DL path loss reference according to embodiment #1a-1. Rel. 16 UEs with two-step RACH capability apply two-step RACH if RSRP is greater than or equal to rsrp-ThresholdMsgA.
　Ｒｅｌ．１６の２ステップＲＡＣＨの能力を有するＵＥは、ＲＳＲＰがrsrp-ThresholdMsgAよりも低い場合、４ステップＲＡＣＨを適用する。２ステップＲＡＣＨ、４ステップＲＡＣＨのためのＲＡリソースは、プール＃１から選択されてもよい。 Rel. 16 UEs with 2-step RACH capability apply 4-step RACH if RSRP is lower than rsrp-ThresholdMsgA. RA resources for 2-step RACH and 4-step RACH may be selected from pool #1.
　Ｒｅｌ．１７のＭｓｇ３繰り返しの能力を有するＵＥは、ＲＳＲＰが閾値rsrp-ThresholdMsg3以上である場合、Ｍｓｇ３繰り返しを伴わない４ステップＲＡＣＨを適用し、ＲＳＲＰが閾値rsrp-ThresholdMsg3よりも低い場合、Ｍｓｇ３繰り返しを伴う４ステップＲＡＣＨを適用する。２ステップＲＡＣＨ、Ｍｓｇ３繰り返しを伴わない４ステップＲＡＣＨのためのＲＡリソースは、プール＃１から選択されてもよい。Ｍｓｇ３繰り返しを伴う４ステップＲＡＣＨのためのＲＡリソースは、プール＃２から選択されてもよい。 Rel. A UE with a capability of 17 Msg3 repetitions applies a 4-step RACH without Msg3 repetitions if the RSRP is above the threshold rsrp-ThresholdMsg3, and 4 steps with Msg3 repetitions if the RSRP is lower than the threshold rsrp-ThresholdMsg3. Apply step RACH. RA resources for 2-step RACH, 4-step RACH without Msg3 repetition may be selected from pool #1. RA resources for 4-step RACH with Msg3 repetition may be selected from pool #2.
　Ｒｅｌ．１８のＭｓｇ１繰り返しの能力を有するＵＥは、ＲＳＲＰが閾値rsrp-ThresholdMsg1以上である場合、Ｍｓｇ１繰り返しを伴わない４ステップＲＡＣＨを適用し、ＲＳＲＰが閾値rsrp-ThresholdMsg1よりも低い場合、Ｍｓｇ１繰り返しを伴う４ステップＲＡＣＨを適用してもよい。２ステップＲＡＣＨ、Ｍｓｇ１繰り返しを伴わない４ステップＲＡＣＨのためのＲＡリソースは、プール＃１から選択されてもよい。Ｍｓｇ１繰り返しを伴う４ステップＲＡＣＨのためのＲＡリソースは、プール＃３から選択されてもよい。 Rel. A UE with a capability of 18 Msg1 repetitions applies a 4-step RACH without Msg1 repetitions if the RSRP is above the threshold rsrp-ThresholdMsg1 and 4 steps with Msg1 repetitions if the RSRP is lower than the threshold rsrp-ThresholdMsg1. Step RACH may be applied. RA resources for 2-step RACH, 4-step RACH without Msg1 repetition may be selected from pool #1. RA resources for 4-step RACH with Msg1 repetition may be selected from pool #3.
　Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しをサポートするＵＥは、ＲＳＲＰがrsrp-ThresholdMsgA以上である場合、２ステップＲＡＣＨを適用してもよい。ＲＳＲＰがrsrp-ThresholdMsgAよりも低く閾値rsrp-ThresholdMsg3以上である場合、そのＵＥは、Ｍｓｇ１繰り返しもＭｓｇ３繰り返しも伴わない４ステップＲＡＣＨを適用してもよい。ＲＳＲＰが閾値rsrp-ThresholdMsg3よりも低く閾値rsrp-ThresholdMsg1以上である場合、そのＵＥは、Ｍｓｇ３繰り返しを伴いＭｓｇ１繰り返しを伴わない４ステップＲＡＣＨを適用してもよい。ＲＳＲＰが閾値rsrp-ThresholdMsg1よりも低い場合、そのＵＥは、Ｍｓｇ１繰り返しを伴いＭｓｇ３繰り返しを伴わない４ステップＲＡＣＨを適用してもよい。２ステップＲＡＣＨ、Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しを伴わない４ステップＲＡＣＨのためのＲＡリソースは、プール＃１から選択されてもよい。Ｍｓｇ３繰り返しを伴いＭｓｇ１繰り返しを伴わない４ステップＲＡＣＨのためのＲＡリソースは、プール＃２から選択されてもよい。Ｍｓｇ１繰り返しを伴いＭｓｇ３繰り返しを伴わない４ステップＲＡＣＨのためのＲＡリソースは、プール＃３から選択されてもよい。 A UE that supports Msg1 repetition and Msg3 repetition may apply 2-step RACH if RSRP is greater than or equal to rsrp-ThresholdMsgA. If RSRP is lower than rsrp-ThresholdMsgA and greater than or equal to threshold rsrp-ThresholdMsg3, the UE may apply 4-step RACH without Msg1 or Msg3 repetitions. If the RSRP is lower than the threshold rsrp-ThresholdMsg3 and greater than or equal to the threshold rsrp-ThresholdMsg1, the UE may apply 4-step RACH with Msg3 repetitions and without Msg1 repetitions. If the RSRP is lower than the threshold rsrp-ThresholdMsg1, the UE may apply 4-step RACH with Msg1 repetitions and without Msg3 repetitions. RA resources for 2-step RACH, 4-step RACH without Msg1 repetition and Msg3 repetition may be selected from pool #1. RA resources for 4-step RACH with Msg3 repetitions and without Msg1 repetitions may be selected from pool #2. RA resources for 4-step RACH with Msg1 repetition and without Msg3 repetition may be selected from pool #3.
《実施形態＃１ａ－２》
　Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しの合同動作（joint　operation）が、サポートされてもよい。 《Embodiment #1a-2》
A joint operation of Msg1 and Msg3 repetitions may be supported.
　ＲＡＣＨリソースのタイプとして、以下のいくつかのタイプの内の少なくとも１つのタイプがあってもよい。
・Ｍｓｇ１繰り返しもＭｓｇ３繰り返しも伴わないＲＡＣＨ手順のためのＲＡＣＨリソースの１つ以上のセット。
・Ｍｓｇ３繰り返しを伴いＭｓｇ１繰り返しを伴わないＲＡＣＨ手順のためのＲＡＣＨリソースの１つ以上のセット。
・Ｍｓｇ１繰り返しを伴いＭｓｇ３繰り返しを伴わないＲＡＣＨ手順のためのＲＡＣＨリソースの１つ以上のセット。
・Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しの両方を伴うＲＡＣＨ手順のためのＲＡＣＨリソースの１つ以上のセット。 The type of RACH resource may be at least one of the following types.
- One or more sets of RACH resources for RACH procedures without Msg1 or Msg3 repetitions.
- One or more sets of RACH resources for RACH procedures with Msg3 repetitions and without Msg1 repetitions.
- One or more sets of RACH resources for RACH procedures with Msg1 repetitions and without Msg3 repetitions.
- One or more sets of RACH resources for RACH procedures with both Msg1 and Msg3 repetitions.
　Ｍｓｇ１／Ｍｓｇ３の繰り返しを伴うＲＡＣＨ手順のためのＲＡＣＨリソースの複数のセットの間において、Ｍｓｇ１／Ｍｓｇ３の繰り返しの数が異なってもよい。 The number of Msg1/Msg3 repetitions may be different between multiple sets of RACH resources for RACH procedures with Msg1/Msg3 repetitions.
　もしＵＥが、Ｍｓｇ１繰り返しの能力と、Ｍｓｇ３繰り返しの能力と、の両方を報告する場合、ＵＥ動作は、ある条件に基づいてもよい。例えば、その条件は、ＳＳＢのＲＳＲＰの条件であってもよい。 If the UE reports both Msg1 repeat capability and Msg3 repeat capability, UE behavior may be based on certain conditions. For example, the condition may be an RSRP condition of SSB.
［例１］
　Ｍｓｇ１／Ｍｓｇ３の繰り返しに対し、以下のいくつかのＵＥ動作の内の少なくとも１つが適用可能であってもよい。各ＵＥ動作は、ＳＳＢ　ＲＳＲＰの範囲に対応してもよい。 [Example 1]
For Msg1/Msg3 repetitions, at least one of the following several UE actions may be applicable: Each UE operation may correspond to a range of SSB RSRPs.
［［ＵＥ動作１］］
　その後のＲＡＣＨ手順内において、Ｍｓｇ１繰り返しもＭｓｇ３繰り返しも適用されない。その条件は、ＳＳＢ　ＲＳＲＰが、閾値１以上であることと、閾値２よりも低いことと、の少なくとも１つであってもよい。閾値１は、rsrp-Threshold-NoRepであってもよい。 [[UE operation 1]]
Within the subsequent RACH procedure, neither Msg1 nor Msg3 repetitions are applied. The condition may be at least one of SSB RSRP being equal to or greater than threshold 1 and lower than threshold 2. Threshold 1 may be rsrp-Threshold-NoRep.
［［ＵＥ動作２］］
　その後のＲＡＣＨ手順内において、Ｍｓｇ３繰り返しのみが適用される。その条件は、ＳＳＢ　ＲＳＲＰが、閾値３以上であることと、閾値４よりも低いことと、の少なくとも１つであってもよい。閾値３は、rsrp-Threshold-NoRepであってもよい。閾値４は、rsrp-ThresholdMsg3であってもよい。 [[UE operation 2]]
Within the subsequent RACH procedure, only Msg3 repetitions are applied. The condition may be at least one of the following: the SSB RSRP is equal to or greater than the threshold value 3, or lower than the threshold value 4. Threshold 3 may be rsrp-Threshold-NoRep. Threshold 4 may be rsrp-ThresholdMsg3.
［［ＵＥ動作３］］
　その後のＲＡＣＨ手順内において、Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しの両方が適用される。その条件は、ＳＳＢ　ＲＳＲＰが、閾値５以上であることと、閾値６よりも低いことと、の少なくとも１つであってもよい。閾値６は、rsrp-ThresholdMsg1であってもよい。 [[UE operation 3]]
Within the subsequent RACH procedure, both Msg1 and Msg3 repetitions are applied. The condition may be at least one of SSB RSRP being equal to or greater than the threshold value 5 and lower than the threshold value 6. Threshold 6 may be rsrp-ThresholdMsg1.
　閾値１／２／３／４／５／６は、仕様において定義されてもよいし、ＰＢＣＨ／ＳＩＢ１　ＰＤＳＣＨ／ＲＲＣ　ＩＥを介し、基地局によって指示されてもよい。 The threshold values 1/2/3/4/5/6 may be defined in the specifications or may be instructed by the base station via the PBCH/SIB1 PDSCH/RRC IE.
［例２］
　Ｍｓｇ１／Ｍｓｇ３の繰り返しに対し、以下のいくつかのＵＥ動作の内の少なくとも１つが適用可能であってもよい。各ＵＥ動作は、ＳＳＢ　ＲＳＲＰの範囲に対応してもよい。 [Example 2]
For Msg1/Msg3 repetitions, at least one of the following several UE actions may be applicable: Each UE operation may correspond to a range of SSB RSRPs.
［［ＵＥ動作１］］
　その後のＲＡＣＨ手順内において、Ｍｓｇ１繰り返しもＭｓｇ３繰り返しも適用されない。その条件は、ＳＳＢ　ＲＳＲＰが、閾値１以上であることと、閾値２よりも低いことと、の少なくとも１つであってもよい。閾値１は、rsrp-ThresholdMsg3であってもよい。 [[UE operation 1]]
Within the subsequent RACH procedure, neither Msg1 nor Msg3 repetitions are applied. The condition may be at least one of SSB RSRP being equal to or greater than threshold 1 and lower than threshold 2. Threshold 1 may be rsrp-ThresholdMsg3.
［［ＵＥ動作２］］
　その後のＲＡＣＨ手順内において、Ｍｓｇ３繰り返しのみが適用される。その条件は、ＳＳＢ　ＲＳＲＰが、閾値５以上であることと、閾値６よりも低いことと、の少なくとも１つであってもよい。閾値５は、rsrp-ThresholdMsg1であってもよい。閾値６は、rsrp-ThresholdMsg3であってもよい。 [[UE operation 2]]
Within the subsequent RACH procedure, only Msg3 repetitions are applied. The condition may be at least one of SSB RSRP being equal to or greater than the threshold value 5 and lower than the threshold value 6. Threshold 5 may be rsrp-ThresholdMsg1. Threshold 6 may be rsrp-ThresholdMsg3.
［［ＵＥ動作３］］
　その後のＲＡＣＨ手順内において、Ｍｓｇ１繰り返しのみが適用される。その条件は、ＳＳＢ　ＲＳＲＰが、閾値３以上であることと、閾値４よりも低いことと、の少なくとも１つであってもよい。閾値３は、rsrp-ThresholdMsg3であってもよい。閾値４は、rsrp-ThresholdMsg1であってもよい。 [[UE operation 3]]
Within the subsequent RACH procedure, only Msg1 repeats are applied. The condition may be at least one of the following: the SSB RSRP is equal to or greater than the threshold value 3, or lower than the threshold value 4. Threshold 3 may be rsrp-ThresholdMsg3. Threshold 4 may be rsrp-ThresholdMsg1.
［［ＵＥ動作４］］
　その後のＲＡＣＨ手順内において、Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しの両方が適用される。その条件は、ＳＳＢ　ＲＳＲＰが、閾値７以上であることと、閾値８よりも低いことと、の少なくとも１つであってもよい。閾値８は、rsrp-ThresholdMsg1Msg3であってもよい。 [[UE operation 4]]
Within the subsequent RACH procedure, both Msg1 and Msg3 repetitions are applied. The condition may be at least one of the following: the SSB RSRP is equal to or greater than the threshold value 7, or lower than the threshold value 8. The threshold 8 may be rsrp-ThresholdMsg1Msg3.
　閾値１／２／３／４／５／６／７／８は、仕様において定義されてもよいし、ＰＢＣＨ／ＳＩＢ１　ＰＤＳＣＨ／ＲＲＣ　ＩＥを介し、基地局によって指示されてもよい。 The threshold values 1/2/3/4/5/6/7/8 may be defined in the specifications, or may be instructed by the base station via the PBCH/SIB1 PDSCH/RRC IE.
　Ｒｅｌ．１７　coverage　enhancement（CovEnh）におけるカバレッジ評価結果によれば、Ｍｓｇ３は、Ｍｓｇ１よりもボトルネックになる。したがって、Ｍｓｇ１繰り返しが必要である場合、Ｍｓｇ３繰り返しも必要であることが好ましい。これによって、例１は、例２よりも好ましい。 Rel. According to the coverage evaluation results in 17 Coverage Enhancement (CovEnh), Msg3 becomes more of a bottleneck than Msg1. Therefore, if Msg1 repeats are required, it is preferred that Msg3 repeats are also required. This makes Example 1 more preferred than Example 2.
　図６は、実施形態＃１ａ－２の例１に係るＤＬパスロス参照のＲＳＲＰに対するＲＡＣＨ手順を一例を示す。Ｒｅｌ．１６の２ステップＲＡＣＨの能力を有するＵＥ、Ｒｅｌ．１７のＭｓｇ３繰り返しの能力を有するＵＥ、Ｒｅｌ．１８のＭｓｇ１繰り返しの能力を有するＵＥ、については、実施形態＃１ａ－１で述べた動作と同様である。 FIG. 6 shows an example of the RACH procedure for RSRP with DL path loss reference according to Example 1 of Embodiment #1a-2. Rel. 16 two-step RACH capable UEs, Rel. A UE with a capability of 17 Msg3 repetitions, Rel. For a UE with a capability of 18 Msg1 repetitions, the operation is similar to that described in embodiment #1a-1.
　Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しをサポートするＵＥは、ＲＳＲＰがrsrp-ThresholdMsgA以上である場合、２ステップＲＡＣＨを適用してもよい。ＲＳＲＰがrsrp-ThresholdMsgAよりも低く閾値rsrp-ThresholdMsg3以上である場合、そのＵＥは、Ｍｓｇ１繰り返しもＭｓｇ３繰り返しも伴わない４ステップＲＡＣＨを適用してもよい。ＲＳＲＰが閾値rsrp-ThresholdMsg3よりも低く閾値rsrp-ThresholdMsg1以上である場合、そのＵＥは、Ｍｓｇ３繰り返しを伴いＭｓｇ１繰り返しを伴わない４ステップＲＡＣＨを適用してもよい。ＲＳＲＰが閾値rsrp-ThresholdMsg1よりも低い場合、そのＵＥは、Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しを伴う４ステップＲＡＣＨを適用してもよい。２ステップＲＡＣＨ、Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しを伴わない４ステップＲＡＣＨのためのＲＡリソースは、プール＃１から選択されてもよい。Ｍｓｇ３繰り返しを伴いＭｓｇ１繰り返しを伴わない４ステップＲＡＣＨのためのＲＡリソースは、プール＃２から選択されてもよい。Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しを伴う４ステップＲＡＣＨのためのＲＡリソースは、プール＃３から選択されてもよい。 A UE that supports Msg1 repetition and Msg3 repetition may apply 2-step RACH if RSRP is greater than or equal to rsrp-ThresholdMsgA. If RSRP is lower than rsrp-ThresholdMsgA and greater than or equal to threshold rsrp-ThresholdMsg3, the UE may apply 4-step RACH without Msg1 or Msg3 repetitions. If the RSRP is lower than the threshold rsrp-ThresholdMsg3 and greater than or equal to the threshold rsrp-ThresholdMsg1, the UE may apply 4-step RACH with Msg3 repetitions and without Msg1 repetitions. If the RSRP is lower than the threshold rsrp-ThresholdMsg1, the UE may apply 4-step RACH with Msg1 and Msg3 repetitions. RA resources for 2-step RACH, 4-step RACH without Msg1 repetition and Msg3 repetition may be selected from pool #1. RA resources for 4-step RACH with Msg3 repetitions and without Msg1 repetitions may be selected from pool #2. RA resources for 4-step RACH with Msg1 repeat and Msg3 repeat may be selected from pool #3.
　図７は、実施形態＃１ａ－２の例２に係るＤＬパスロス参照のＲＳＲＰに対するＲＡＣＨ手順を一例を示す。Ｒｅｌ．１６の２ステップＲＡＣＨの能力を有するＵＥ、Ｒｅｌ．１７のＭｓｇ３繰り返しの能力を有するＵＥ、Ｒｅｌ．１８のＭｓｇ１繰り返しの能力を有するＵＥ、については、実施形態＃１ａ－１で述べた動作と同様である。 FIG. 7 shows an example of the RACH procedure for RSRP with DL path loss reference according to Example 2 of Embodiment #1a-2. Rel. 16 two-step RACH capable UEs, Rel. A UE with a capability of 17 Msg3 repetitions, Rel. For a UE with a capability of 18 Msg1 repetitions, the operation is similar to that described in embodiment #1a-1.
　Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しをサポートするＵＥは、ＲＳＲＰがrsrp-ThresholdMsgA以上である場合、２ステップＲＡＣＨを適用してもよい。ＲＳＲＰがrsrp-ThresholdMsgAよりも低く閾値rsrp-ThresholdMsg3以上である場合、そのＵＥは、Ｍｓｇ１繰り返しもＭｓｇ３繰り返しも伴わない４ステップＲＡＣＨを適用してもよい。ＲＳＲＰが閾値rsrp-ThresholdMsg3よりも低く閾値rsrp-ThresholdMsg1以上である場合、そのＵＥは、Ｍｓｇ３繰り返しを伴いＭｓｇ１繰り返しを伴わない４ステップＲＡＣＨを適用してもよい。ＲＳＲＰが閾値rsrp-ThresholdMsg1よりも低く閾値rsrp-ThresholdMsg1Msg3以上である場合、そのＵＥは、Ｍｓｇ１繰り返しを伴いＭｓｇ３繰り返しを伴わない４ステップＲＡＣＨを適用してもよい。ＲＳＲＰが閾値rsrp-ThresholdMsg1Msg3よりも低い場合、そのＵＥは、Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しを伴う４ステップＲＡＣＨを適用してもよい。２ステップＲＡＣＨ、Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しを伴わない４ステップＲＡＣＨのためのＲＡリソースは、プール＃１から選択されてもよい。Ｍｓｇ３繰り返しを伴いＭｓｇ１繰り返しを伴わない４ステップＲＡＣＨのためのＲＡリソースは、プール＃２から選択されてもよい。Ｍｓｇ１繰り返しを伴いＭｓｇ３繰り返しを伴わない４ステップＲＡＣＨのためのＲＡリソースは、プール＃３から選択されてもよい。Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しを伴う４ステップＲＡＣＨのためのＲＡリソースは、プール＃４から選択されてもよい。 A UE that supports Msg1 repetition and Msg3 repetition may apply 2-step RACH if RSRP is greater than or equal to rsrp-ThresholdMsgA. If RSRP is lower than rsrp-ThresholdMsgA and greater than or equal to threshold rsrp-ThresholdMsg3, the UE may apply 4-step RACH without Msg1 or Msg3 repetitions. If the RSRP is lower than the threshold rsrp-ThresholdMsg3 and greater than or equal to the threshold rsrp-ThresholdMsg1, the UE may apply 4-step RACH with Msg3 repetitions and without Msg1 repetitions. If the RSRP is lower than the threshold rsrp-ThresholdMsg1 and greater than or equal to the threshold rsrp-ThresholdMsg1Msg3, the UE may apply 4-step RACH with Msg1 repetitions and without Msg3 repetitions. If the RSRP is lower than the threshold rsrp-ThresholdMsg1Msg3, the UE may apply 4-step RACH with Msg1 and Msg3 repetitions. RA resources for 2-step RACH, 4-step RACH without Msg1 repetition and Msg3 repetition may be selected from pool #1. RA resources for 4-step RACH with Msg3 repetitions and without Msg1 repetitions may be selected from pool #2. RA resources for 4-step RACH with Msg1 repetition and without Msg3 repetition may be selected from pool #3. RA resources for 4-step RACH with Msg1 repeat and Msg3 repeat may be selected from pool #4.
《実施形態＃１ａ－３》
　Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しの合同動作（joint　operation）が、サポートされ、Ｍｓｇ３繰り返しの能力は、Ｍｓｇ１繰り返しの能力に対する前提（prerequisite）能力（必要条件）であってもよい。 《Embodiment #1a-3》
A joint operation of Msg1 repeat and Msg3 repeat is supported, and the capability of Msg3 repeat may be a prerequisite capability to the capability of Msg1 repeat.
　Ｍｓｇ１繰り返しの能力を報告するＵＥは、Ｍｓｇ３繰り返しの能力を有するように規定されてもよい。 A UE reporting Msg1 repetition capability may be defined as having Msg3 repetition capability.
　ＲＡＣＨリソースのタイプとして、以下のいくつかのタイプの内の少なくとも１つのタイプがあってもよい。
・Ｍｓｇ１繰り返しもＭｓｇ３繰り返しも伴わないＲＡＣＨ手順のためのＲＡＣＨリソースの１つ以上のセット。
・Ｍｓｇ３繰り返しを伴いＭｓｇ１繰り返しを伴わないＲＡＣＨ手順のためのＲＡＣＨリソースの１つ以上のセット。
・Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しの両方を伴うＲＡＣＨ手順のためのＲＡＣＨリソースの１つ以上のセット。 The type of RACH resource may be at least one of the following types.
- One or more sets of RACH resources for RACH procedures without Msg1 or Msg3 repetitions.
- One or more sets of RACH resources for RACH procedures with Msg3 repetitions and without Msg1 repetitions.
- One or more sets of RACH resources for RACH procedures with both Msg1 and Msg3 repetitions.
　Ｍｓｇ１／Ｍｓｇ３の繰り返しを伴うＲＡＣＨ手順のためのＲＡＣＨリソースの複数のセットの間において、Ｍｓｇ１／Ｍｓｇ３の繰り返しの数が異なってもよい。 The number of Msg1/Msg3 repetitions may be different between multiple sets of RACH resources for RACH procedures with Msg1/Msg3 repetitions.
　もしＵＥが、Ｍｓｇ１繰り返しの能力と、Ｍｓｇ３繰り返しの能力と、の両方を報告する場合、ＵＥ動作は、ある条件に基づいてもよい。例えば、その条件は、ＳＳＢのＲＳＲＰの条件であってもよい。 If the UE reports both Msg1 repeat capability and Msg3 repeat capability, UE behavior may be based on certain conditions. For example, the condition may be an RSRP condition of SSB.
　Ｍｓｇ１／Ｍｓｇ３の繰り返しに対し、以下のいくつかのＵＥ動作の内の少なくとも１つが適用可能であってもよい。各ＵＥ動作は、ＳＳＢ　ＲＳＲＰの範囲に対応してもよい。 For the Msg1/Msg3 repetition, at least one of the following several UE actions may be applicable. Each UE operation may correspond to a range of SSB RSRP.
［［ＵＥ動作１］］
　その後のＲＡＣＨ手順内において、Ｍｓｇ１繰り返しもＭｓｇ３繰り返しも適用されない。その条件は、ＳＳＢ　ＲＳＲＰが、閾値１以上であることと、閾値２よりも低いことと、の少なくとも１つであってもよい。閾値１は、rsrp-Threshold-NoRepであってもよい。 [[UE operation 1]]
Within the subsequent RACH procedure, neither Msg1 nor Msg3 repetitions are applied. The condition may be at least one of SSB RSRP being equal to or greater than threshold 1 and lower than threshold 2. Threshold 1 may be rsrp-Threshold-NoRep.
［［ＵＥ動作２］］
　その後のＲＡＣＨ手順内において、Ｍｓｇ３繰り返しのみが適用される。その条件は、ＳＳＢ　ＲＳＲＰが、閾値３以上であることと、閾値４よりも低いことと、の少なくとも１つであってもよい。閾値３は、rsrp-Threshold-NoRepであってもよい。閾値４は、rsrp-ThresholdMsg3であってもよい。 [[UE operation 2]]
Within the subsequent RACH procedure, only Msg3 repetitions are applied. The condition may be at least one of the following: the SSB RSRP is equal to or greater than the threshold value 3, or lower than the threshold value 4. Threshold 3 may be rsrp-Threshold-NoRep. Threshold 4 may be rsrp-ThresholdMsg3.
［［ＵＥ動作３］］
　その後のＲＡＣＨ手順内において、Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しの両方が適用される。その条件は、ＳＳＢ　ＲＳＲＰが、閾値５以上であることと、閾値６よりも低いことと、の少なくとも１つであってもよい。閾値６は、rsrp-ThresholdMsg1であってもよい。 [[UE operation 3]]
Within the subsequent RACH procedure, both Msg1 and Msg3 repetitions are applied. The condition may be at least one of SSB RSRP being equal to or greater than the threshold value 5 and lower than the threshold value 6. Threshold 6 may be rsrp-ThresholdMsg1.
　閾値１／２／３／４／５／６は、仕様において定義されてもよいし、ＰＢＣＨ／ＳＩＢ１　ＰＤＳＣＨ／ＲＲＣ　ＩＥを介し、基地局によって指示されてもよい。 The threshold values 1/2/3/4/5/6 may be defined in the specifications or may be instructed by the base station via the PBCH/SIB1 PDSCH/RRC IE.
　図８は、実施形態＃１ａ－３に係るＤＬパスロス参照のＲＳＲＰに対するＲＡＣＨ手順を一例を示す。Ｒｅｌ．１６の２ステップＲＡＣＨの能力を有するＵＥ、Ｒｅｌ．１７のＭｓｇ３繰り返しの能力を有するＵＥ、については、実施形態＃１ａ－１で述べた動作と同様である。 FIG. 8 shows an example of the RACH procedure for RSRP with DL path loss reference according to embodiment #1a-3. Rel. 16 two-step RACH capable UEs, Rel. For a UE with a capability of 17 Msg3 repetitions, the operation is similar to that described in embodiment #1a-1.
　Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しをサポートするＵＥは、ＲＳＲＰがrsrp-ThresholdMsgA以上である場合、２ステップＲＡＣＨを適用してもよい。ＲＳＲＰがrsrp-ThresholdMsgAよりも低く閾値rsrp-ThresholdMsg3以上である場合、そのＵＥは、Ｍｓｇ１繰り返しもＭｓｇ３繰り返しも伴わない４ステップＲＡＣＨを適用してもよい。ＲＳＲＰが閾値rsrp-ThresholdMsg3よりも低く閾値rsrp-ThresholdMsg1以上である場合、そのＵＥは、Ｍｓｇ３繰り返しを伴いＭｓｇ１繰り返しを伴わない４ステップＲＡＣＨを適用してもよい。ＲＳＲＰが閾値rsrp-ThresholdMsg1よりも低い場合、そのＵＥは、Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しを伴う４ステップＲＡＣＨを適用してもよい。２ステップＲＡＣＨ、Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しを伴わない４ステップＲＡＣＨのためのＲＡリソースは、プール＃１から選択されてもよい。Ｍｓｇ３繰り返しを伴いＭｓｇ１繰り返しを伴わない４ステップＲＡＣＨのためのＲＡリソースは、プール＃２から選択されてもよい。Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しを伴う４ステップＲＡＣＨのためのＲＡリソースは、プール＃３から選択されてもよい。 A UE that supports Msg1 repetition and Msg3 repetition may apply 2-step RACH if RSRP is greater than or equal to rsrp-ThresholdMsgA. If RSRP is lower than rsrp-ThresholdMsgA and greater than or equal to threshold rsrp-ThresholdMsg3, the UE may apply 4-step RACH without Msg1 or Msg3 repetitions. If the RSRP is lower than the threshold rsrp-ThresholdMsg3 and greater than or equal to the threshold rsrp-ThresholdMsg1, the UE may apply 4-step RACH with Msg3 repetitions and without Msg1 repetitions. If the RSRP is lower than the threshold rsrp-ThresholdMsg1, the UE may apply 4-step RACH with Msg1 and Msg3 repetitions. RA resources for 2-step RACH, 4-step RACH without Msg1 repetition and Msg3 repetition may be selected from pool #1. RA resources for 4-step RACH with Msg3 repetitions and without Msg1 repetitions may be selected from pool #2. RA resources for 4-step RACH with Msg1 repeat and Msg3 repeat may be selected from pool #3.
《実施形態＃１ａ－４》
　実施形態＃１ａ－１から＃１ａ－３の内のいくつかが組み合わせられてもよい。以下のいくつかの適用条件の内の少なくとも１つの適用条件が満たされる場合に、実施形態＃１ａ－２／＃１ａ－３が適用されてもよい。 《Embodiment #1a-4》
Some of embodiments #1a-1 to #1a-3 may be combined. Embodiment #1a-2/#1a-3 may be applied when at least one of the following application conditions is met.
［適用条件１］
　複数のＭｓｇ１繰り返しに対して１つのＲＡＲが送信されるケースに対し、１つのＲＡＣＨ手順内のＭｓｇ１繰り返し及びＭｓｇ３繰り返しの合同動作（joint　operation）がサポートされてもよい。 [Applicable condition 1]
For the case where one RAR is sent for multiple Msg1 repetitions, joint operation of Msg1 and Msg3 repetitions within one RACH procedure may be supported.
［適用条件２］
　複数のＭｓｇ１繰り返しに対して複数のＲＡＲが送信されるケースに対し、１つのＲＡＣＨ手順内のＭｓｇ１繰り返し及びＭｓｇ３繰り返しの合同動作（joint　operation）がサポートされてもよい。 [Applicable condition 2]
For the case where multiple RARs are sent for multiple Msg1 repetitions, joint operation of Msg1 repetition and Msg3 repetition within one RACH procedure may be supported.
［適用条件３］
　複数のＭｓｇ１繰り返しに対して同じ送信ビームが用いられるケースに対し、１つのＲＡＣＨ手順内のＭｓｇ１繰り返し及びＭｓｇ３繰り返しの合同動作（joint　operation）がサポートされてもよい。 [Applicable condition 3]
For the case where the same transmit beam is used for multiple Msg1 repetitions, joint operation of Msg1 and Msg3 repetitions within one RACH procedure may be supported.
［適用条件４］
　複数のＭｓｇ１繰り返しに対して異なる送信ビームが用いられるケースに対し、１つのＲＡＣＨ手順内のＭｓｇ１繰り返し及びＭｓｇ３繰り返しの合同動作（joint　operation）がサポートされてもよい。 [Applicable condition 4]
For the case where different transmit beams are used for multiple Msg1 repetitions, joint operation of Msg1 and Msg3 repetitions within one RACH procedure may be supported.
　図９Ａの例において、適用条件は適用条件１及び適用条件４である。図９Ｂの例において、適用条件は適用条件２及び適用条件３である。 In the example of FIG. 9A, the applicable conditions are applicable condition 1 and applicable condition 4. In the example of FIG. 9B, the applicable conditions are applicable condition 2 and applicable condition 3.
　この実施形態によれば、ＵＥは、Ｍｓｇ１／Ｍｓｇ３の繰り返しを適切に決定できる。 According to this embodiment, the UE can appropriately determine the repetition of Msg1/Msg3.
《実施形態＃１ｂ》
　ＰＲＡＣＨ繰り返しの数と、ＰＲＡＣＨ用リソースの数と、の間にはトレードオフがある。基地局にとって、ＰＲＡＣＨ繰り返しが行われるか否かと、ＰＲＡＣＨ繰り返しの最大数と、の少なくとも１つを制御できることが好ましい。 《Embodiment #1b》
There is a trade-off between the number of PRACH repetitions and the number of resources for PRACH. It is preferable for the base station to be able to control at least one of whether PRACH repetitions are performed and the maximum number of PRACH repetitions.
　ＵＥは、ＰＲＡＣＨ繰り返しを行うかに関する情報に関する設定／指示を受信してもよい。 The UE may receive settings/instructions regarding information regarding whether to perform PRACH repetition.
《実施形態＃１ｂ－１》
　ＰＲＡＣＨ繰り返しを行うかに関する情報は、以下のいくつかの情報の内の少なくとも１つであってもよい。 《Embodiment #1b-1》
The information regarding whether to perform PRACH repetition may be at least one of the following information.
［情報１］
　その情報は、ＰＲＡＣＨ繰り返し機能をオンにするかオフにするかを示す。その情報は、別の設定に基づいて暗示されてもよい。例えば、ＲＯ／ＲＡリソース設定が、ＰＲＡＣＨ繰り返しをオンにするかオフにするかを暗示してもよい。例えば、ＲＳＲＰ閾値に関する設定が存在するか否かが、ＰＲＡＣＨ繰り返しをオンにするかオフにするかを暗示してもよい。 [Information 1]
The information indicates whether to turn on or turn off the PRACH repeat function. That information may be implied based on another setting. For example, the RO/RA resource configuration may imply whether PRACH repetition is on or off. For example, the presence or absence of a configuration regarding the RSRP threshold may imply whether PRACH repetition is turned on or off.
［情報２］
　その情報は、ＰＲＡＣＨ繰り返しの数を示す。その候補値は、｛１，２，４，８，１６，３２｝の少なくとも１つを含んでもよい。値１は、ＰＲＡＣＨ繰り返しをオフにすることと等価であってもよい。 [Information 2]
The information indicates the number of PRACH repetitions. The candidate value may include at least one of {1, 2, 4, 8, 16, 32}. A value of 1 may be equivalent to turning off PRACH repetition.
［情報３］
　その情報は、ＲＳＲＰ閾値であってもよい。図１０の例のように、ＰＲＡＣＨ繰り返しを行うかを決定するためのＲＳＲＰ閾値は、エントリごとに定義されてもよい。例えば、ＲＳＲＰ閾値が十分に小さい値（例えば－∞）である場合、ＵＥ動作は、ＰＲＡＣＨ繰り返しが行われないことであってもよい。例えば、ＲＳＲＰ閾値が小さい値である場合、ＵＥ動作は、少ないＵＥがＰＲＡＣＨ繰り返しを行うことであってもよい。例えば、ＲＳＲＰ閾値が大きい値である場合、ＵＥ動作は、より多いＵＥがＰＲＡＣＨ繰り返しを行うことであってもよい。例えば、ＲＳＲＰ閾値が十分に大きい値である場合、ＵＥ動作は、さらに多いＵＥがＰＲＡＣＨ繰り返しを行うことであってもよい。ＲＳＲＰ閾値は、仕様において定義されてもよいし、ＲＲＣによって設定されてもよいし、ＭＡＣ　ＣＥ／ＤＣＩを介して指示されてもよい。 [Information 3]
The information may be an RSRP threshold. As in the example of FIG. 10, the RSRP threshold for determining whether to perform PRACH repetition may be defined for each entry. For example, if the RSRP threshold is a sufficiently small value (eg -∞), the UE behavior may be that no PRACH repetition occurs. For example, if the RSRP threshold is a small value, the UE behavior may be that fewer UEs perform PRACH repetitions. For example, if the RSRP threshold is a large value, the UE behavior may be that more UEs perform PRACH repetitions. For example, if the RSRP threshold is a sufficiently large value, the UE behavior may be that more UEs perform PRACH repetitions. The RSRP threshold may be defined in the specification, set by RRC, or indicated via MAC CE/DCI.
《実施形態＃１ｂ－２》
　ＰＲＡＣＨ繰り返しを行うかに関する情報は、以下のいくつかの設定／指示方法の内の少なくとも１つによって設定／指示されてもよい。
［設定／指示方法１］
　その情報は、ＳＩＢ１　ＰＤＳＣＨを介して設定される。
［設定／指示方法２］
　その情報は、ＲＲＣ　ＩＥを介して設定される。
［設定／指示方法３］
　その情報は、ＭＡＣ　ＣＥを介して指示される。
［設定／指示方法４］
　その情報は、ＤＣＩを介して指示される。 《Embodiment #1b-2》
Information regarding whether to perform PRACH repetition may be configured/instructed by at least one of the following several configuration/instruction methods.
[Setting/instruction method 1]
The information is configured via the SIB1 PDSCH.
[Settings/Instruction method 2]
That information is configured via the RRC IE.
[Setting/instruction method 3]
That information is directed via the MAC CE.
[Setting/instruction method 4]
That information is directed via the DCI.
　これらのいくつかの設定／指示方法の組み合わせがサポートされてもよい。例えば、その情報が、ＳＩＢ１　ＰＤＳＣＨ及びＲＲＣ　ＩＥを介して設定されることがサポートされてもよい。 Combinations of some of these settings/instruction methods may be supported. For example, it may be supported that the information is configured via the SIB1 PDSCH and RRC IE.
　異なる設定／指示方法の間において、設定／指示のビット幅が異なってもよい。例えば、設定／指示方法１において１ビットが用いられ、設定／指示方法２において２ビットが用いられてもよい。 The bit width of the setting/instruction may differ between different setting/instruction methods. For example, 1 bit may be used in setting/ instruction method 1 and 2 bits may be used in setting/instruction method 2.
　初期アクセス中のＰＲＡＣＨ繰り返しをサポートするために、少なくとも設定／指示方法１がサポートされることが好ましい。 Preferably, at least configuration/instruction method 1 is supported to support PRACH repetition during initial access.
《実施形態＃１ｂ－３》
　ＰＲＡＣＨ繰り返しを行うかに関する情報の設定／指示は、以下のいくつかの必要条件の内の少なくとも１つの必要条件が満たされることを必要としてもよい。
［必要条件１］
　Ｍｓｇ３繰り返しがサポートされる。
［必要条件２］
　Ｍｓｇ３繰り返しが利用可能であるＲＯ／ＲＡリソースが設定される。
［必要条件３］
　Ｍｓｇ１繰り返しがサポートされる。
［必要条件４］
　Ｍｓｇ１繰り返しが利用可能であるＲＯ／ＲＡリソースが設定される。 《Embodiment #1b-3》
Setting/instructing information regarding whether to perform PRACH repetition may require that at least one of the following several requirements be met.
[Requirement 1]
Msg3 repeats are supported.
[Requirement 2]
The RO/RA resources that are available for Msg3 repetition are configured.
[Requirement 3]
Msg1 repeats are supported.
[Requirement 4]
The RO/RA resources that are available for Msg1 iteration are configured.
　この実施形態によれば、ＵＥは、Ｍｓｇ１／Ｍｓｇ３の繰り返しを適切に決定できる。 According to this embodiment, the UE can appropriately determine the repetition of Msg1/Msg3.
＜実施形態＃Ｘ＞
　この実施形態は、ＲＡＣＨリソースに関する。 <Embodiment #X>
This embodiment relates to RACH resources.
　ＵＥは、Ｍｓｇ１の繰り返しを含む第１ランダムアクセス手順に関する情報を受信してもよい。ＵＥは、前記情報に基づいて、第１ランダムアクセスリソースを、前記第１ランダムアクセス手順に用い、前記第１ランダムアクセスリソースと異なる第２ランダムアクセスリソースを、前記Ｍｓｇ１の繰り返しを含まない第２ランダムアクセス手順に用いてもよい。 The UE may receive information regarding the first random access procedure including the repetition of Msg1. Based on the information, the UE uses a first random access resource for the first random access procedure, and uses a second random access resource different from the first random access resource to perform a second random access procedure that does not include the repetition of Msg1. May be used for access procedures.
《実施形態＃Ｘａ》
　ＰＲＡＣＨ繰り返しは、特定のＲＡリソース内のみにおいて、行われてもよい。 《Embodiment #Xa》
PRACH repetition may be performed only within specific RA resources.
《《実施形態＃Ｘａ－１》》
　特定ＲＡリソースは、以下のいくつかのＲＡリソースの内の少なくとも１つであってもよい。
［ＲＡリソース１］少なくともＭｓｇ３繰り返しの機能が利用可能であるＲＡリソース。
［ＲＡリソース２］Ｍｓｇ３繰り返し、ＲｅｄＣａｐ、ＲＡＮ　Slicing、ＳＤＴのいずれの機能も利用可能でないＲＡリソース。
［ＲＡリソース３］少なくともＰＲＡＣＨ繰り返しの機能が利用可能であるＲＡリソース。この場合、ＰＲＡＣＨ繰り返しの機能が導入される。
［ＲＡリソース４］ＲＡリソース１から３のいくつかの組み合わせ。ＲＡリソース１＋ＲＡリソース３、又は、ＲＡリソース２＋ＲＡリソース３。 《《Embodiment #Xa-1》》
The specific RA resource may be at least one of the following several RA resources.
[RA resource 1] RA resource for which at least the function of repeating Msg3 can be used.
[RA resource 2] RA resource in which none of the functions of Msg3 repetition, RedCap, RAN Slicing, and SDT can be used.
[RA resource 3] RA resource for which at least the function of PRACH repetition can be used. In this case, a function of PRACH repetition is introduced.
[RA resource 4] Some combinations of RA resources 1 to 3. RA resource 1+RA resource 3, or RA resource 2+RA resource 3.
《《実施形態＃Ｘａ－２》》
　ＰＲＡＣＨ（Ｍｓｇ１）繰り返しは、以下のいくつかのＰＲＡＣＨ繰り返し定義の内の少なくとも１つに従ってもよい。
［ＰＲＡＣＨ繰り返し定義１］同じビームを伴う複数ＰＲＡＣＨ送信。
［ＰＲＡＣＨ繰り返し定義２］異なるビームを伴う複数ＰＲＡＣＨ送信。
［ＰＲＡＣＨ繰り返し定義３］ＲＡＲウィンドウの満了の前の（同じビーム又は異なるビームを伴う）複数ＰＲＡＣＨ送信。
［ＰＲＡＣＨ繰り返し定義４］最初のＰＲＡＣＨ送信を含む複数ＰＲＡＣＨ送信。
［ＰＲＡＣＨ繰り返し定義５］最初のＰＲＡＣＨ送信を含まない複数ＰＲＡＣＨ送信。この場合、最初のＰＲＡＣＨ送信は、Ｒｅｌ．１５／１６のＰＲＡＣＨ送信のＲＡリソースと同じＲＡリソースにおいて送信されてもよい。後続のＰＲＡＣＨ送信は、実施形態＃Ｘａ－１におけるＲＡリソース内において送信されてもよい。 《《Embodiment #Xa-2》》
The PRACH (Msg1) repeat may follow at least one of several PRACH repeat definitions:
[PRACH Repetition Definition 1] Multiple PRACH transmissions with the same beam.
[PRACH Repetition Definition 2] Multiple PRACH transmissions with different beams.
[PRACH Repetition Definition 3] Multiple PRACH transmissions (with the same beam or different beams) before expiration of the RAR window.
[PRACH Repetition Definition 4] Multiple PRACH transmissions including the first PRACH transmission.
[PRACH repetition definition 5] Multiple PRACH transmissions that do not include the first PRACH transmission. In this case, the first PRACH transmission is Rel. It may be transmitted using the same RA resource as the RA resource for 15/16 PRACH transmission. Subsequent PRACH transmissions may be transmitted within the RA resources in embodiment #Xa-1.
　ＲＡリソース、ＰＲＡＣＨプリアンブル、ＰＲＡＣＨプリアンブルインデックス、は互いに読み替えられてもよい。 The RA resource, PRACH preamble, and PRACH preamble index may be read interchangeably.
《《実施形態＃Ｘａ－３》》
　ＰＲＡＣＨ繰り返しのためのＲＡリソースは、以下のいくつかの区分方法の内の少なくとも１つに従ってもよい。 《《Embodiment #Xa-3》》
RA resources for PRACH repetition may follow at least one of several partitioning methods:
［区分方法１］
　前述のＲＡリソース１が適用されることが想定されてもよい。少なくともＭｓｇ３繰り返しが利用可能であるＲＡリソースに対して、以下のいくつかのＲＡリソース設定の内の少なくとも１つが設定されてもよい。
［［ＲＡリソース設定１－１］］ＰＲＡＣＨ繰り返しに利用可能なプリアンブルインデックスの数。
　そのプリアンブルインデックスの数の設定のみが存在する場合、ＰＲＡＣＨ繰り返しに利用可能な最初のプリアンブルインデックスは、特定ルールごとに決定されてもよい。例えば、その最初のプリアンブルインデックスは、Ｍｓｇ３繰り返しを設定された最初のプリアンブルインデックスであってもよい。ＰＲＡＣＨ繰り返しを設定された利用可能な全てのプリアンブルインデックスは、決定されたプリアンブルインデックスを起点に、Ｍｓｇ３繰り返しに適用可能なプリアンブルインデックス内に収容されてもよい。
［［ＲＡリソース設定１－２］］ＰＲＡＣＨ繰り返しに利用可能な最初のプリアンブルインデックス。
　その最初のプリアンブルインデックスの設定のみが存在する場合、ＰＲＡＣＨ繰り返しに利用可能なプリアンブルインデックスの総数は、特定ルールごとに決定されてもよい。例えば、その総数は、設定された最初のプリアンブルインデックスを起点とし、Ｍｓｇ３繰り返しを設定された全てのプリアンブルインデックスの数であってもよい。 [Classification method 1]
It may be assumed that the above-mentioned RA resource 1 is applied. At least one of the following several RA resource configurations may be configured for RA resources for which at least Msg3 repeats are available:
[[RA resource setting 1-1]] Number of preamble indexes available for PRACH repetition.
If there is only a configuration for the number of preamble indexes, the first preamble index available for PRACH repetition may be determined for each specific rule. For example, the first preamble index may be the first preamble index configured with Msg3 repetition. All available preamble indexes configured for PRACH repetition may be accommodated in the preamble index applicable to Msg3 repetition starting from the determined preamble index.
[[RA resource configuration 1-2]] The first preamble index available for PRACH repetition.
If only that initial preamble index configuration exists, the total number of preamble indexes available for PRACH repetition may be determined for each specific rule. For example, the total number may be the number of all preamble indexes for which Msg3 repetition is set, starting from the first preamble index set.
［区分方法２］
　前述のＲＡリソース２が適用されることが想定されてもよい。ＰＲＡＣＨ繰り返しのためのＲＡリソースは、Ｍｓｇ３繰り返し、ＲｅｄＣａｐ、ＲＡＮ　slicing、ＳＤＴの機能のいずれも利用可能でないＲＡリソース以外のＲＡリソースであってもよい。 [Classification method 2]
It may be assumed that the above-mentioned RA resource 2 is applied. The RA resources for PRACH repetition may be RA resources other than RA resources in which none of the functions of Msg3 repetition, RedCap, RAN slicing, and SDT are available.
［区分方法３］
　前述のＲＡリソース３が適用されることが想定されてもよい。少なくともＭｓｇ３繰り返しが利用可能であるＲＡリソースに対して、以下のいくつかのＲＡリソース設定の内の少なくとも１つが設定されてもよい。
［［ＲＡリソース設定３－１］］ＰＲＡＣＨ繰り返しに利用可能な最初のプリアンブルインデックス。
［［ＲＡリソース設定３－２］］ＰＲＡＣＨ繰り返しに利用可能なプリアンブルインデックスの数。 [Classification method 3]
It may be assumed that the above-mentioned RA resource 3 is applied. At least one of the following several RA resource configurations may be configured for RA resources for which at least Msg3 repeats are available:
[[RA Resource Settings 3-1]] First preamble index available for PRACH repetition.
[[RA resource setting 3-2]] Number of preamble indexes available for PRACH repetition.
　実施形態＃Ｘａ－１と同様、区分方法１から３のいくつかの組み合わせが、考慮されてもよい。 Similar to embodiment #Xa-1, several combinations of partitioning methods 1 to 3 may be considered.
《実施形態＃Ｘｂ》
　ＰＲＡＣＨ繰り返しは、特定ＲＡＣＨオケージョン（ＲＯ）内のみにおいて、行われてもよい。 《Embodiment #Xb》
PRACH repetition may be performed only within a specific RACH occasion (RO).
《《実施形態＃Ｘｂ－１》》
　特定ＲＯは、以下のいくつかのＲＯの内の少なくとも１つであってもよい。
［ＲＯ１］少なくともＭｓｇ３繰り返しの機能が利用可能であるＲＯ。
［ＲＯ２］Ｍｓｇ３繰り返し、ＲｅｄＣａｐ、ＲＡＮ　Slicing、ＳＤＴのいずれの機能も利用可能でないＲＯ。
［ＲＯ３］少なくともＰＲＡＣＨ繰り返しの機能が利用可能であるＲＯ。この場合、ＰＲＡＣＨ繰り返しの機能が導入される。
［ＲＯ４］ＲＯ１から３のいくつかの組み合わせ。ＲＯ１＋ＲＯ３、又は、ＲＯ２＋ＲＯ３。 《《Embodiment #Xb-1》》
The specific RO may be at least one of the following several ROs.
[RO1] An RO for which at least the Msg3 repeat function is available.
[RO2] RO where none of the Msg3 repeat, RedCap, RAN Slicing, and SDT functions are available.
[RO3] An RO for which at least the function of PRACH repetition can be used. In this case, a function of PRACH repetition is introduced.
[RO4] Some combinations of RO1 to 3. RO1+RO3 or RO2+RO3.
《《実施形態＃Ｘｂ－２》》
　ＰＲＡＣＨ繰り返しは、以下のいくつかのＰＲＡＣＨ繰り返し定義の内の少なくとも１つに従ってもよい。
［ＰＲＡＣＨ繰り返し定義１］同じビームを伴う複数ＰＲＡＣＨ送信。
［ＰＲＡＣＨ繰り返し定義２］異なるビームを伴う複数ＰＲＡＣＨ送信。
［ＰＲＡＣＨ繰り返し定義３］ＲＡＲウィンドウの満了の前の（同じビーム又は異なるビームを伴う）複数ＰＲＡＣＨ送信。
［ＰＲＡＣＨ繰り返し定義４］最初のＰＲＡＣＨ送信を含む複数ＰＲＡＣＨ送信。
［ＰＲＡＣＨ繰り返し定義５］最初のＰＲＡＣＨ送信を含まない複数ＰＲＡＣＨ送信。この場合、最初のＰＲＡＣＨ送信は、Ｒｅｌ．１５／１６のＰＲＡＣＨ送信のＲＡリソースと同じＲＡリソースにおいて送信されてもよい。後続のＰＲＡＣＨ送信は、実施形態＃Ｘｂ－１におけるＲＯ内において送信されてもよい。 《《Embodiment #Xb-2》》
A PRACH repetition may follow at least one of several PRACH repetition definitions:
[PRACH Repetition Definition 1] Multiple PRACH transmissions with the same beam.
[PRACH Repetition Definition 2] Multiple PRACH transmissions with different beams.
[PRACH Repetition Definition 3] Multiple PRACH transmissions (with the same beam or different beams) before expiration of the RAR window.
[PRACH Repetition Definition 4] Multiple PRACH transmissions including the first PRACH transmission.
[PRACH repetition definition 5] Multiple PRACH transmissions that do not include the first PRACH transmission. In this case, the first PRACH transmission is Rel. It may be transmitted using the same RA resource as the RA resource for 15/16 PRACH transmission. Subsequent PRACH transmissions may be transmitted within the RO in embodiment #Xb-1.
《《実施形態＃Ｘｂ－３》》
　ＰＲＡＣＨ繰り返しのためのＲＯは、以下のいくつかの区分方法の内の少なくとも１つに従ってもよい。 《《Embodiment #Xb-3》》
The RO for PRACH repetition may follow at least one of several partitioning methods:
［区分方法１］
　前述のＲＯ１が適用されることが想定されてもよい。ＰＲＡＣＨ繰り返しに利用可能なＲＯを決定するために、少なくともＭｓｇ３繰り返しのためのＲＯを決定することを設定する明示的設定が考慮されてもよい。 [Classification method 1]
It may be envisaged that the aforementioned RO1 is applied. To determine the available ROs for PRACH repetitions, an explicit configuration to configure determining ROs for at least Msg3 repetitions may be considered.
［区分方法２］
　前述のＲＯ２が適用されることが想定されてもよい。ＰＲＡＣＨ繰り返しに利用可能なＲＯを決定するために、対応するマスクインデックスによって他の機能を伴って設定されないＲＯが考慮されてもよい。 [Classification method 2]
It may be envisaged that the aforementioned RO2 applies. To determine the ROs available for PRACH repetition, ROs that are not configured with other functions by the corresponding mask index may be considered.
［区分方法３］
　前述のＲＯ３が適用されることが想定されてもよい。ＰＲＡＣＨ繰り返しに利用可能なＲＯを決定するために、少なくともＰＲＡＣＨ繰り返しのためのＲＯを決定することを設定する明示的設定が考慮されてもよい。 [Classification method 3]
It may be envisaged that the aforementioned RO3 applies. In order to determine the available ROs for PRACH repetitions, an explicit configuration configuring at least determining ROs for PRACH repetitions may be considered.
　実施形態＃Ｘｂ－１と同様、区分方法１から３のいくつかの組み合わせが、考慮されてもよい。 Similar to embodiment #Xb-1, several combinations of classification methods 1 to 3 may be considered.
《《実施形態＃Ｘｂ－４》》
　マスクインデックスの制約／拡張は、以下のいくつかの制約／拡張の内の少なくとも１つに従ってもよい。 《《Embodiment #Xb-4》》
The mask index constraints/extensions may be subject to at least one of the following several constraints/extensions.
［制約／拡張１］
　ＰＲＡＣＨ繰り返しのために設定されるＰＲＡＣＨマスクインデックスは、他の機能／用途のために設定されるＰＲＡＣＨマスクインデックスと異なる。その機能／用途は、以下のいくつかの機能／用途の少なくとも１つを含んでもよい。
・Ｍｓｇ３繰り返し
・ＲｅｄＣａｐ
・ＳＤＴ
・ＲＡＮ　slicing
・２ステップＲＡ
・なし（すなわち、既存の４ステップＲＡ） [Constraint/Extension 1]
The PRACH mask index configured for PRACH repetition is different from the PRACH mask index configured for other functions/uses. The functionality/applications may include at least one of the following several functionality/applications:
・Msg3 repeat ・RedCap
・SDT
・RAN slicing
・2 step RA
- None (i.e. existing 4-step RA)
［制約／拡張２］
　利用可能なＰＲＡＣＨマスクインデックスエントリは、以下のいくつかの拡張方法の少なくとも１つに基づいて拡張されてもよい。
［［拡張方法１］］ＰＲＡＣＨオケージョンインデックスＸのためのエントリを追加すること。ここで、Ｘは、８よりも大きい整数であってもよい。
［［拡張方法２］］Ｘ個のＰＲＡＣＨオケージョン内の第１／第２／第３／...／第ＸのＰＲＡＣＨオケージョンのためのエントリを追加すること。ここで、Ｘは、２よりも大きい整数であってもよい。例えば、Ｘは３、４、又は、５であってもよい。 [Constraints/Expansion 2]
The available PRACH mask index entries may be expanded based on at least one of several expansion methods below.
[[Extension method 1]] Add an entry for PRACH occasion index X. Here, X may be an integer greater than 8.
[[Extension method 2]] Adding entries for the first/second/third/.../Xth PRACH occasion in the X PRACH occasions. Here, X may be an integer greater than 2. For example, X may be 3, 4, or 5.
［制約／拡張３］
　ＰＲＡＣＨマスクインデックス設定のためのビット幅は、１６よりも多いエントリをカバーするように拡張されてもよい。 [Constraints/Expansion 3]
The bit width for PRACH mask index configuration may be expanded to cover more than 16 entries.
　この実施形態によれば、ＵＥは、ＰＲＡＣＨ繰り返しのためのＲＡＣＨリソースを適切に決定できる。 According to this embodiment, the UE can appropriately determine RACH resources for PRACH repetition.
＜実施形態＃２＞
　この実施形態は、Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しの合同動作に関する。 <Embodiment #2>
This embodiment relates to the joint operation of Msg1 repeat and Msg3 repeat.
　ＵＥは、Ｍｓｇ１の複数の繰り返し及びＭｓｇ３の複数の繰り返しを含むランダムアクセス手順に関する情報を受信してもよい。ＵＥは、前記情報に基づいて、前記Ｍｓｇ１の複数の繰り返しに用いられる１つ以上の第１ビームに基づいて、前記Ｍｓｇ３の複数の繰り返しに用いられる１つ以上の第２ビームを決定してもよい。 The UE may receive information regarding a random access procedure including multiple repetitions of Msg1 and multiple repetitions of Msg3. The UE may determine one or more second beams to be used for the plurality of repetitions of the Msg3 based on the one or more first beams to be used for the plurality of repetitions of the Msg1 based on the information. good.
《ケース１》
　１つのＲＡＣＨ手順内におけるＭｓｇ３繰り返しを伴うＭｓｇ１繰り返しの合同動作において、複数のＭｓｇ１繰り返しに対して１つのＲＡＲが送信されるケース。 《Case 1》
Case where one RAR is sent for multiple Msg1 repetitions in joint operation of Msg1 repetitions with Msg3 repetitions within one RACH procedure.
　Ｍｓｇ３繰り返しの送信ビームは、Ｍｓｇ１繰り返しと、検出されたＲＡＲと、の少なくとも１つのビームに依存してもよい。 The transmission beam of the Msg3 repetition may depend on at least one beam of the Msg1 repetition and the detected RAR.
　Ｍｓｇ３繰り返しの送信ビームは、以下のいくつかの送信ビームのいずれかであってもよい。 The transmission beam for Msg3 repetition may be any of the following several transmission beams.
［送信ビーム１－１］
　全てのＭｓｇ３繰り返しに対して同じビームが用いられてもよい。 [Transmission beam 1-1]
The same beam may be used for all Msg3 repetitions.
［［送信ビーム１－１Ａ］］
　全てのＭｓｇ３繰り返しに対する同じビームは、Ｍｓｇ１繰り返しのビームによって決定されてもよい。
・例：もし複数のＭｓｇ１繰り返しが同じビームを用いる場合、Ｍｓｇ３繰り返しのビームは、Ｍｓｇ１繰り返しのビームと同じであってもよい（図１１）。
・例：もし複数のＭｓｇ１繰り返しが異なるビームを用いる場合、Ｍｓｇ３繰り返しのビームは、最初／最後／ランダム番目のＭｓｇ１繰り返しのビームに従ってもよい。図１２の例において、Ｍｓｇ３の４つの繰り返しは、Ｍｓｇ１の４つの繰り返しの内の１番目の繰り返しに用いられたビームを用いる。 [[Transmission beam 1-1A]]
The same beam for all Msg3 repetitions may be determined by the beam of Msg1 repetition.
- Example: If multiple Msg1 repetitions use the same beam, the beam for Msg3 repetitions may be the same as the beam for Msg1 repetitions (Figure 11).
- Example: If multiple Msg1 repetitions use different beams, the beam of Msg3 repetition may follow the beam of the first/last/random Msg1 repetition. In the example of FIG. 12, the four repetitions of Msg3 use the beam used in the first repetition of the four repetitions of Msg1.
［［送信ビーム１－１Ｂ］］
　全てのＭｓｇ３繰り返しに対する同じビームは、検出されたＲＡＲによって決定されてもよい。
・例：そのビームは、ＲＡＲ内の明示的指示によって決定されてもよい。ＲＡＲ内の１つのフィールドがＭｓｇ３繰り返しに対するビームを指示してもよい。ＵＥは、その指示されたビームが、Ｍｓｇ１繰り返しのビームから得られると想定する、と規定されてもよい。図１３の例において、ＲＡＲは、Ｍｓｇ３の４つの繰り返しに用いられるビームを指示する。そのビームは、Ｍｓｇ１の４つの繰り返しの内の１つに用いられたビームである。
・例：そのビームは、ＲＡ－ＲＮＴＩのような暗示的指示によって決定されてもよい。例えば、検出されたＲＡＲに用いられたＲＡ－ＲＮＴＩに対応するＲＯによって、そのビームが決定されてもよい。 [[Transmission beam 1-1B]]
The same beam for all Msg3 repetitions may be determined by the detected RAR.
- Example: the beam may be determined by explicit instructions within the RAR. One field within the RAR may direct the beam for Msg3 repetitions. It may be specified that the UE assumes that its indicated beam is obtained from Msg1 repeat beams. In the example of FIG. 13, the RAR indicates the beam used for four repetitions of Msg3. That beam is the one used in one of the four iterations of Msg1.
- Example: the beam may be determined by an implicit indication such as RA-RNTI. For example, the beam may be determined by the RO corresponding to the RA-RNTI used for the detected RAR.
［送信ビーム１－２］
　全てのＭｓｇ３繰り返しに対して異なるビームが用いられてもよい。 [Transmission beam 1-2]
A different beam may be used for every Msg3 repetition.
［［送信ビーム１－２Ａ］］
　複数のＭｓｇ３繰り返しのビームは、Ｍｓｇ１繰り返しのビームによって決定されてもよい。もし複数のＭｓｇ１繰り返しが異なるビームを用いる場合、複数のＭｓｇ３繰り返しのビームは、複数のＭｓｇ１繰り返しのビームに従ってもよい。
・例：もしＭｓｇ１繰り返しの数がＭｓｇ３繰り返しの数に等しい場合、複数のＭｓｇ１繰り返しのビームと、複数のＭｓｇ３繰り返しのビームと、のマッピングは、１対１マッピングであってもよい。図１４の例において、Ｍｓｇ３の４つの繰り返しに用いられる４つのビームは、Ｍｓｇ１の４つの繰り返しに用いられた４つのビームである。
・例：もしＭｓｇ１繰り返しの数がＭｓｇ３繰り返しの数よりも少ない場合、複数のＭｓｇ１繰り返しのビームと、複数のＭｓｇ３繰り返しのビームと、のマッピングは、シーケンシャルマッピング又はサイクリックマッピングであってもよい。図１５の例において、Ｍｓｇ３の４つの繰り返しに用いられる４つのビームに対し、Ｍｓｇ１の２つの繰り返しに用いられた２つのビームが巡回的に適用される（サイクリックマッピング）。図１６の例において、Ｍｓｇ３の４つの繰り返しに用いられる４つのビームに対し、Ｍｓｇ１の２つの繰り返しに用いられた各ビームが連続して２回ずつ適用される（シーケンシャルマッピング）。
・例：もしＭｓｇ１繰り返しの数がＭｓｇ３繰り返しの数Ｎよりも多い場合、Ｎ個のＭｓｇ３繰り返しのビームは、最初から／最後から／ランダムなＮ個のＭｓｇ１繰り返しのビームであってもよい。図１７の例において、Ｍｓｇ３の２つの繰り返しに用いられる２つのビームは、Ｍｓｇ１の４つの繰り返しの内の最初の２つの繰り返しに用いられた２つのビームである。 [[Transmission beam 1-2A]]
The beams of multiple Msg3 repetitions may be determined by the beams of Msg1 repetitions. If the Msg1 repeats use different beams, the Msg3 repeat beams may follow the Msg1 repeat beams.
- Example: If the number of Msg1 repeats is equal to the number of Msg3 repeats, the mapping between the beams of Msg1 repeats and the beams of Msg3 repeats may be a one-to-one mapping. In the example of FIG. 14, the four beams used for the four repetitions of Msg3 are the four beams used for the four repetitions of Msg1.
- Example: If the number of Msg1 repeats is less than the number of Msg3 repeats, the mapping of multiple Msg1 repeat beams and multiple Msg3 repeat beams may be sequential mapping or cyclic mapping. In the example of FIG. 15, the two beams used for the two repetitions of Msg1 are cyclically applied to the four beams used for the four repetitions of Msg3 (cyclic mapping). In the example of FIG. 16, each beam used in the two repetitions of Msg1 is applied twice in succession to the four beams used in the four repetitions of Msg3 (sequential mapping).
- Example: If the number of Msg1 repeats is greater than the number N of Msg3 repeats, the beam of N Msg3 repeats may be a beam of N Msg1 repeats from the beginning/from the end/randomly. In the example of FIG. 17, the two beams used for the two repetitions of Msg3 are the two beams used for the first two of the four repetitions of Msg1.
［［送信ビーム１－２Ｂ］］
　複数のＭｓｇ３繰り返しのビームは、検出されたＲＡＲによって決定されてもよい。
・例：そのビームは、ＲＡＲ内の明示的指示によって決定されてもよい。ＵＥは、その指示されたビームが、Ｍｓｇ１繰り返しのビームから得られると想定する、と規定されてもよい。 [[Transmission beam 1-2B]]
The beam of multiple Msg3 repetitions may be determined by the detected RAR.
- Example: the beam may be determined by explicit instructions within the RAR. It may be specified that the UE assumes that its indicated beam is obtained from Msg1 repeat beams.
《ケース２》
　１つのＲＡＣＨ手順内におけるＭｓｇ３繰り返しを伴うＭｓｇ１繰り返しの合同動作において、複数のＭｓｇ１繰り返しに対して複数のＲＡＲが送信されるケース。 《Case 2》
Case where multiple RARs are sent for multiple Msg1 repetitions in joint operation of Msg1 repetitions with Msg3 repetitions within one RACH procedure.
　各ＲＡＲによってスケジュールされる各Ｍｓｇ３において、Ｍｓｇ３に対する複数繰り返しのビームは、対応するＭｓｇ１繰り返しと、対応するＲＡＲと、全てのＭｓｇ１繰り返しのビームと、の少なくとも１つのビームに依存してもよい。 For each Msg3 scheduled by each RAR, the beam of multiple repetitions for Msg3 may depend on at least one of the beams of the corresponding Msg1 repetition, the corresponding RAR, and all Msg1 repetitions.
　ＵＥは、以下のいくつかの動作の少なくとも１つに従ってもよい。
・ＵＥは、複数のＭｓｇ３ＰＵＳＣＨに対する異なる繰り返し数を想定しない。
・ＵＥは、複数のＭｓｇ３ＰＵＳＣＨに対する繰り返し数の合計がある値を超えるとを想定しない。
・ＵＥは、以前のＭｓｇ３ＰＵＳＣＨの任意の繰り返しが、その後のＭｓｇ３ＰＵＳＣＨの任意の繰り返しと衝突すると想定しない。
・ＵＥは、以前のＭｓｇ３ＰＵＳＣＨの任意の繰り返しが、その後のＭｓｇ３ＰＵＳＣＨの任意の繰り返しよりも後に開始／終了すると想定しない。 The UE may follow at least one of the following several actions.
- The UE does not assume different repetition numbers for multiple Msg3PUSCHs.
- The UE does not assume that the total number of repetitions for multiple Msg3PUSCHs exceeds a certain value.
- The UE does not assume that any previous repetition of Msg3PUSCH will collide with any subsequent repetition of Msg3PUSCH.
- The UE does not assume that any previous Msg3PUSCH repetition starts/ends later than any subsequent Msg3PUSCH repetition.
　Ｍｓｇ３繰り返しの送信ビームは、以下のいくつかの送信ビームのいずれかであってもよい。 The transmission beam for Msg3 repetition may be any of the following several transmission beams.
［送信ビーム２－１］
　全てのＭｓｇ３繰り返しに対して同じビームが用いられてもよい。 [Transmission beam 2-1]
The same beam may be used for all Msg3 repetitions.
［［送信ビーム２－１Ａ］］
　全てのＭｓｇ３繰り返しに対する同じビームは、対応するＭｓｇ１繰り返しのビームによって決定されてもよい。図１８の例において、複数のＭｓｇ１繰り返しは同じビームを用い、Ｍｓｇ３の４つの繰り返しに用いられる１つのビームは、対応するＭｓｇ１繰り返しに用いられたビームである。図１９の例において、複数のＭｓｇ１繰り返しは異なるビームを用い、Ｍｓｇ３の４つの繰り返しに用いられる１つのビームは、対応するＭｓｇ１繰り返しに用いられたビームである。 [[Transmission beam 2-1A]]
The same beam for all Msg3 repetitions may be determined by the beam of the corresponding Msg1 repetition. In the example of FIG. 18, multiple Msg1 repetitions use the same beam, and the one beam used in the four Msg3 repetitions is the beam used in the corresponding Msg1 repetition. In the example of FIG. 19, the multiple Msg1 repetitions use different beams, and the one beam used in the four Msg3 repetitions is the beam used in the corresponding Msg1 repetition.
［［送信ビーム２－１Ｂ］］
　全てのＭｓｇ３繰り返しに対する同じビームは、対応するＲＡＲによって決定されてもよい。
・例：そのビームは、ＲＡＲ内の明示的指示によって決定されてもよい。ＲＡＲ内の１つのフィールドがＭｓｇ３繰り返しに対するビームを指示してもよい。ＵＥは、その指示されたビームが、Ｍｓｇ１繰り返しのビームから得られると想定する、と規定されてもよい。
・例：そのビームは、ＲＡ－ＲＮＴＩのような暗示的指示によって決定されてもよい。例えば、検出されたＲＡＲに用いられたＲＡ－ＲＮＴＩに対応するＲＯによって、そのビームが決定されてもよい。
［［送信ビーム２－１Ｃ］］
　全てのＭｓｇ３繰り返しに対する同じビームは、全てのＭｓｇ１繰り返しのビームによって決定されてもよい。
・例：もし複数のＭｓｇ１繰り返しが同じビームを用いる場合、Ｍｓｇ３繰り返しのビームは、送信ビーム２－１Ａと同じであってもよい。
・例：もし複数のＭｓｇ１繰り返しが異なるビームを用いる場合、Ｍｓｇ３繰り返しのビームは、最初／最後／ランダム番目のＭｓｇ１繰り返しのビームに従ってもよい。 [[Transmission beam 2-1B]]
The same beam for all Msg3 repetitions may be determined by the corresponding RAR.
- Example: the beam may be determined by explicit instructions within the RAR. One field within the RAR may direct the beam for Msg3 repetitions. It may be specified that the UE assumes that its indicated beam is obtained from Msg1 repeat beams.
- Example: the beam may be determined by an implicit indication such as RA-RNTI. For example, the beam may be determined by the RO corresponding to the RA-RNTI used for the detected RAR.
[[Transmission beam 2-1C]]
The same beam for all Msg3 repetitions may be determined by the beam for all Msg1 repetitions.
- Example: If multiple Msg1 repetitions use the same beam, the beam of Msg3 repetition may be the same as transmit beam 2-1A.
- Example: If multiple Msg1 repetitions use different beams, the beam of Msg3 repetition may follow the beam of the first/last/random Msg1 repetition.
［送信ビーム２－２］
　全てのＭｓｇ３繰り返しに対して異なるビームが用いられてもよい。 [Transmission beam 2-2]
A different beam may be used for every Msg3 repetition.
［［送信ビーム２－２Ａ］］
　複数のＭｓｇ３繰り返しのビームは、全てのＭｓｇ１繰り返しのビームによって決定されてもよい。もし複数のＭｓｇ１繰り返しが異なるビームを用いる場合、複数のＭｓｇ３繰り返しのビームは、複数のＭｓｇ１繰り返しのビームに従ってもよい。
・例：もしＭｓｇ１繰り返しの数がＭｓｇ３繰り返しの数に等しい場合、複数のＭｓｇ１繰り返しのビームと、複数のＭｓｇ３繰り返しのビームと、のマッピングは、１対１マッピングであってもよい。
・例：もしＭｓｇ１繰り返しの数がＭｓｇ３繰り返しの数よりも少ない場合、複数のＭｓｇ１繰り返しのビームと、複数のＭｓｇ３繰り返しのビームと、のマッピングは、シーケンシャルマッピング又はサイクリックマッピングであってもよい。図２０の例において、Ｍｓｇ３の４つの繰り返しに用いられる４つのビームに対し、Ｍｓｇ１の２つの繰り返しに用いられた２つのビームが巡回的に適用される（サイクリックマッピング）。図２１の例において、Ｍｓｇ３の４つの繰り返しに用いられる４つのビームに対し、Ｍｓｇ１の２つの繰り返しに用いられた各ビームが連続して２回ずつ適用される（シーケンシャルマッピング）。
・例：もしＭｓｇ１繰り返しの数がＭｓｇ３繰り返しの数Ｎよりも多い場合、Ｎ個のＭｓｇ３繰り返しのビームは、最初から／最後から／ランダムなＮ個のＭｓｇ１繰り返しのビームであってもよい。 [[Transmission beam 2-2A]]
The beams of multiple Msg3 repetitions may be determined by the beams of all Msg1 repetitions. If the Msg1 repeats use different beams, the Msg3 repeat beams may follow the Msg1 repeat beams.
- Example: If the number of Msg1 repeats is equal to the number of Msg3 repeats, the mapping between the beams of Msg1 repeats and the beams of Msg3 repeats may be a one-to-one mapping.
- Example: If the number of Msg1 repeats is less than the number of Msg3 repeats, the mapping of multiple Msg1 repeat beams and multiple Msg3 repeat beams may be sequential mapping or cyclic mapping. In the example of FIG. 20, the two beams used for the two repetitions of Msg1 are cyclically applied to the four beams used for the four repetitions of Msg3 (cyclic mapping). In the example of FIG. 21, each beam used in the two repetitions of Msg1 is applied twice in succession to the four beams used in the four repetitions of Msg3 (sequential mapping).
- Example: If the number of Msg1 repeats is greater than the number N of Msg3 repeats, the beam of N Msg3 repeats may be a beam of N Msg1 repeats from the beginning/from the end/randomly.
［［送信ビーム２－２Ｂ］］
　複数のＭｓｇ３繰り返しのビームは、対応するＲＡＲによって決定されてもよい。
・例：そのビームは、ＲＡＲ内の明示的指示によって決定されてもよい。ＲＡＲ内の１つのフィールドが、Ｍｓｇ３繰り返しに対する１つまたは複数のビームを指示してもよい。ＵＥは、その指示されたビームが、Ｍｓｇ１繰り返しのビームから得られると想定する、と規定されてもよい。 [[Transmission beam 2-2B]]
The beams of multiple Msg3 repetitions may be determined by the corresponding RAR.
- Example: the beam may be determined by explicit instructions within the RAR. One field within the RAR may direct one or more beams for Msg3 repetitions. It may be specified that the UE assumes that its indicated beam is obtained from Msg1 repeat beams.
　この実施形態によれば、ＵＥは、Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しを行う場合に、Ｍｓｇ３繰り返しのビームを適切に決定できる。 According to this embodiment, when performing Msg1 repetition and Msg3 repetition, the UE can appropriately determine the beam for Msg3 repetition.
＜実施形態＃３＞
　この実施形態は、Ｍｓｇ３繰り返しの数に関する。 <Embodiment #3>
This embodiment concerns the number of Msg3 repeats.
　ＵＥは、Ｍｓｇ３の繰り返しの数に関する指示情報を受信してもよい。ＵＥは、前記指示情報と、前記Ｍｓｇ３の繰り返しを含むランダムアクセス手順内のＭｓｇ１の繰り返しに関する情報と、に基づいて、前記Ｍｓｇ３の繰り返しの数を決定してもよい。 The UE may receive instruction information regarding the number of repetitions of Msg3. The UE may determine the number of repetitions of Msg3 based on the instruction information and information regarding the repetition of Msg1 within a random access procedure including the repetition of Msg3.
　ＲＡＲによって指示されるＭｓｇ３繰り返しの数の解釈は、以下の実施形態＃３－１から＃３－５の少なくとも１つに依存してもよい。 Interpretation of the number of Msg3 repeats indicated by RAR may depend on at least one of the following embodiments #3-1 to #3-5.
《実施形態＃３－１》
　ＲＡＲによって指示されるＭｓｇ３繰り返しの数の解釈は、現在のＲＡＣＨ手順内において、１つ以上のＭｓｇ１繰り返しが行われるか否か、に依存してもよい。 《Embodiment #3-1》
The interpretation of the number of Msg3 repeats indicated by the RAR may depend on whether one or more Msg1 repeats are performed within the current RACH procedure.
　現在のＲＡＣＨ手順内において、Ｍｓｇ１繰り返しがない場合、ＲＡＲによって指示されるＭｓｇ３繰り返しの数の解釈は、Ｒｅｌ．１７ルールに従ってもよい。すなわち、ＭＣＳフィールドからの２ビットが、４つの候補値に基づいて、その解釈に再利用されてもよい。図２２Ａの例において、ＭＣＳフィールドからの２ビットは、Ｍｓｇ３繰り返しの数の４つの候補値からの１つの値を指示する。 Within the current RACH procedure, if there is no Msg1 repeat, the interpretation of the number of Msg3 repeats indicated by RAR is Rel. You may follow the 17 rules. That is, two bits from the MCS field may be reused for its interpretation based on the four candidate values. In the example of FIG. 22A, two bits from the MCS field indicate one value out of four candidate values for the number of Msg3 repeats.
　現在のＲＡＣＨ手順内において、Ｍｓｇ１繰り返しがある場合、ＲＡＲによって指示されるＭｓｇ３繰り返しの数のための、指示のビットの数と、候補値と、の少なくとも１つが、Ｒｅｌ．１７ルールと異なってもよい。例えば、ＭＣＳフィールドからのＸビットが、Ｍｓｇ３繰り返しの数の２Ｘ個までの候補値からの１つの値の指示に用いられてもよい。Ｘは、２に等しくてもよいし、２より少なくてもよいし、２より多くてもよい。２Ｘ個までの候補値は、仕様において定義されてもよいし、ＰＢＣＨ／ＳＩＢ１　ＰＤＳＣＨ／ＲＲＣ　ＩＥによって設定されてもよい。候補値は、４／８／１６／３２／６４などの上限を超えなくてもよい。図２２Ｂの例において、ＭＣＳフィールドからの２ビットは、Ｍｓｇ３繰り返しの数の４つの候補値からの１つの値を指示する。図２２Ｃの例において、ＭＣＳフィールドからの１ビットは、Ｍｓｇ３繰り返しの数の２つの候補値からの１つの値を指示する。 Within the current RACH procedure, if there is a Msg1 repetition, at least one of the number of bits of the indication and the candidate value for the number of Msg3 repetitions indicated by the RAR is Rel. It may be different from the 17 rules. For example, X bits from the MCS field may be used to indicate one value from up to 2X candidate values for the number of Msg3 repeats. X may be equal to 2, less than 2, or more than 2. Up to 2X candidate values may be defined in the specification or configured by the PBCH/SIB1 PDSCH/RRC IE. Candidate values do not have to exceed upper limits such as 4/8/16/32/64. In the example of FIG. 22B, two bits from the MCS field indicate one value out of four candidate values for the number of Msg3 repeats. In the example of FIG. 22C, one bit from the MCS field indicates one value from two candidate values for the number of Msg3 repeats.
　Ｍｓｇ１繰り返しがある場合、Ｍｓｇ３繰り返しの必要とされる数の値／範囲は、Ｒｅｌ．１７の値よりも大きくてもよい。したがって、Ｍｓｇ１繰り返しを伴うケースに対して、Ｍｓｇ３繰り返しの数の定義／設定される値は、Ｍｓｇ１繰り返しを伴わないケースに対する値と異なってもよい。 If there is Msg1 repeat, the value/range of the required number of Msg3 repeats is Rel. The value may be greater than 17. Therefore, for the case with Msg1 repetition, the value defined/set for the number of Msg3 repetitions may be different from the value for the case without Msg1 repetition.
《実施形態＃３－２》
　現在のＲＡＣＨ手順内において複数のＭｓｇ１繰り返しが行われる場合、ＲＡＲによって指示されるＭｓｇ３繰り返しの数の解釈は、１つのＲＡＲが送信されるか複数のＲＡＲが送信されるか、に依存してもよい。 《Embodiment #3-2》
If multiple Msg1 repetitions occur within the current RACH procedure, the interpretation of the number of Msg3 repetitions indicated by the RAR may depend on whether one RAR or multiple RARs are sent. good.
　現在のＲＡＣＨ手順内において複数のＭｓｇ１繰り返しがある場合、Ｍｓｇ３繰り返しの数のための、指示のビットの数と、候補値と、の少なくとも１つが、複数のＭｓｇ１繰り返しに対して１つのみのＲＡＲが送信されるケース（ケース１）と、複数のＭｓｇ１繰り返しに対して複数のＲＡＲが送信されるケース（ケース２）と、の間において異なってもよい。 If there are multiple Msg1 repeats within the current RACH procedure, at least one of the number of bits of the indication and the candidate value for the number of Msg3 repeats is RAR for only one Msg1 repeat for multiple Msg1 repeats. may be different between the case where RARs are sent (case 1) and the case where multiple RARs are sent for multiple Msg1 repetitions (case 2).
　例えば、もし複数のＭｓｇ１繰り返しに対して１つのみのＲＡＲが送信される場合（ケース１）、ＭＣＳフィールドからのＸビットが、Ｍｓｇ３繰り返しの数の２Ｘ個までの候補値からの１つの値の指示に用いられてもよい。Ｘは、２に等しくてもよいし、２より少なくてもよいし、２より多くてもよい。２Ｘ個までの候補値は、仕様において定義されてもよいし、ＰＢＣＨ／ＳＩＢ１　ＰＤＳＣＨ／ＲＲＣ　ＩＥによって設定されてもよい。２Ｘ個までの候補値は、Ｒｅｌ．１７のＭｓｇ３繰り返しをサポートするＵＥに対して設定される候補値と同じであってもよい。候補値は、４／８／１６／３２／６４などの上限を超えなくてもよい。 For example, if only one RAR is sent for multiple Msg1 repetitions (case 1), then It may be used for instructions. X may be equal to 2, less than 2, or more than 2. Up to 2X candidate values may be defined in the specification or configured by the PBCH/SIB1 PDSCH/RRC IE. Up to 2X candidate values are Rel. It may be the same as the candidate value set for a UE that supports 17 Msg3 repetitions. Candidate values do not have to exceed upper limits such as 4/8/16/32/64.
　ＲＡＲ内のＸビットの新規フィールドが、Ｍｓｇ３繰り返しの数の２Ｘ個までの候補値からの１つの値の指示に用いられてもよい。 A new field of X bits in the RAR may be used to indicate one value from up to 2X candidate values for the number of Msg3 repeats.
　例えば、もし複数のＭｓｇ１繰り返しに対して複数のＲＡＲが送信される場合（ケース２）、ＭＣＳフィールドからのＹビットが、Ｍｓｇ３繰り返しの数の２Ｙ個までの候補値からの１つの値の指示に用いられてもよい。Ｙは、２に等しくてもよいし、２より少なくてもよいし、２より多くてもよい。２Ｙ個までの候補値は、仕様において定義されてもよいし、ＰＢＣＨ／ＳＩＢ１　ＰＤＳＣＨ／ＲＲＣ　ＩＥによって設定されてもよい。２Ｘ個までの候補値は、Ｒｅｌ．１７のＭｓｇ３繰り返しをサポートするＵＥに対して設定される候補値と同じであってもよい。候補値は、４／８／１６／３２／６４などの上限を超えなくてもよい。 For example, if multiple RARs are sent for multiple Msg1 repetitions (case 2), then the Y bits from the MCS field are 2 times the number of Msg3 repetitions, indicating one value from up to Y candidate values. May be used for. Y may be equal to 2, less than 2, or more than 2. Up to 2 Y candidate values may be defined in the specification or configured by the PBCH/SIB1 PDSCH/RRC IE. Up to 2X candidate values are Rel. It may be the same as the candidate value set for a UE that supports 17 Msg3 repetitions. Candidate values do not have to exceed upper limits such as 4/8/16/32/64.
　ＲＡＲ内のＹビットの新規フィールドが、Ｍｓｇ３繰り返しの数の２Ｙ個までの候補値からの１つの値の指示に用いられてもよい。１番目のＲＡＲ内のＭＣＳフィールドからの２ビットが、Ｍｓｇ３繰り返しの数の４個までの候補値からの１つの値の指示に用いられてもよい（Ｒｅｌ．１７と同様）。２番目以降のＲＡＲ内のＹビットの新規フィールドが、Ｍｓｇ３繰り返しの数の２Ｙ個までの候補値からの１つの値の指示に用いられてもよい。 A new field of Y bits in the RAR may be used to indicate one value from up to 2 Y candidate values for the number of Msg3 repeats. Two bits from the MCS field in the first RAR may be used to indicate one value from up to four candidate values for the number of Msg3 repeats (similar to Rel.17). A new field of Y bits in the second and subsequent RARs may be used to indicate one value from up to 2 Y candidate values for the number of Msg3 repeats.
《実施形態＃３－３》
　（基地局がＭｓｇ１繰り返しの数を知り得る場合において、）ＲＡＲによって指示されるＭｓｇ３繰り返しの数の解釈は、現在のＲＡＣＨ手順内におけるＭｓｇ１繰り返しの数に依存してもよい。例えば、基地局がＭｓｇ１繰り返しの数を知り得る場合は、ＲＡＣＨリソースプールが、Ｍｓｇ１繰り返しの数に関連付けられている場合であってもよいし、Ｍｓｇ１に対して繰り返しの１つのみの数がある場合であってもよい。 《Embodiment #3-3》
The interpretation of the number of Msg3 repetitions indicated by the RAR (in case the base station can know the number of Msg1 repetitions) may depend on the number of Msg1 repetitions within the current RACH procedure. For example, if the base station can know the number of Msg1 repetitions, the RACH resource pool may be associated with the number of Msg1 repetitions, or there is only one number of repetitions for Msg1. It may be a case.
　現在のＲＡＣＨ手順内において複数のＭｓｇ１繰り返しがある場合、Ｍｓｇ３繰り返しの数のための、指示のビットの数と、候補値と、の少なくとも１つが、Ｍｓｇ１繰り返しの異なる数のケースの間において異なってもよい。 If there are multiple Msg1 repetitions within the current RACH procedure, at least one of the number of indication bits and the candidate value for the number of Msg3 repetitions is different between cases of different numbers of Msg1 repetitions. Good too.
　例えば、もしＭｓｇ１の４つの繰り返しがある場合、ＭＣＳフィールドからのＸビットが、Ｍｓｇ３繰り返しの数の２Ｘ個までの候補値からの１つの値の指示に用いられてもよい。Ｘは、２に等しくてもよいし、２より少なくてもよいし、２より多くてもよい。２Ｘ個までの候補値は、仕様において定義されてもよいし、ＰＢＣＨ／ＳＩＢ１　ＰＤＳＣＨ／ＲＲＣ　ＩＥによって設定されてもよい。２Ｘ個までの候補値は、Ｒｅｌ．１７のＭｓｇ３繰り返しをサポートするＵＥに対して設定される候補値と同じであってもよい。候補値は、４／８／１６／３２／６４などの上限を超えなくてもよい。 For example, if there are four repetitions of Msg1, then X bits from the MCS field may be used to indicate one value from up to 2X candidate values for the number of Msg3 repetitions. X may be equal to 2, less than 2, or more than 2. Up to 2X candidate values may be defined in the specification or configured by the PBCH/SIB1 PDSCH/RRC IE. Up to 2X candidate values are Rel. It may be the same as the candidate value set for a UE that supports 17 Msg3 repetitions. Candidate values do not have to exceed upper limits such as 4/8/16/32/64.
　ＲＡＲ内のＸビットの新規フィールドが、Ｍｓｇ３繰り返しの数の２Ｘ個までの候補値からの１つの値の指示に用いられてもよい。１番目のＲＡＲ内のＭＣＳフィールドからの２ビットが、Ｍｓｇ３繰り返しの数の４個までの候補値からの１つの値の指示に用いられてもよい（Ｒｅｌ．１７と同様）。２番目以降のＲＡＲ内のＸビットの新規フィールドが、Ｍｓｇ３繰り返しの数の２Ｘ個までの候補値からの１つの値の指示に用いられてもよい。 A new field of X bits in the RAR may be used to indicate one value from up to 2X candidate values for the number of Msg3 repeats. Two bits from the MCS field in the first RAR may be used to indicate one value from up to four candidate values for the number of Msg3 repeats (similar to Rel.17). A new field of X bits in the second and subsequent RARs may be used to indicate one value from up to 2X candidate values for the number of Msg3 repeats.
　例えば、もしＭｓｇ１の８つの繰り返しがある場合、ＭＣＳフィールドからのＹビットが、Ｍｓｇ３繰り返しの数の２Ｙ個までの候補値からの１つの値の指示に用いられてもよい。Ｙは、２に等しくてもよいし、２より少なくてもよいし、２より多くてもよい。２Ｙ個までの候補値は、仕様において定義されてもよいし、ＰＢＣＨ／ＳＩＢ１　ＰＤＳＣＨ／ＲＲＣ　ＩＥによって設定されてもよい。２Ｘ個までの候補値は、Ｒｅｌ．１７のＭｓｇ３繰り返しをサポートするＵＥに対して設定される候補値と同じであってもよい。候補値は、４／８／１６／３２／６４などの上限を超えなくてもよい。 For example, if there are 8 repetitions of Msg1, Y bits from the MCS field may be used to indicate one value from up to 2 Y candidate values for the number of Msg3 repetitions. Y may be equal to 2, less than 2, or more than 2. Up to 2 Y candidate values may be defined in the specification or configured by the PBCH/SIB1 PDSCH/RRC IE. Up to 2X candidate values are Rel. It may be the same as the candidate value set for a UE that supports 17 Msg3 repetitions. Candidate values do not have to exceed upper limits such as 4/8/16/32/64.
　ＲＡＲ内のＹビットの新規フィールドが、Ｍｓｇ３繰り返しの数の２Ｙ個までの候補値からの１つの値の指示に用いられてもよい。１番目のＲＡＲ内のＭＣＳフィールドからの２ビットが、Ｍｓｇ３繰り返しの数の４個までの候補値からの１つの値の指示に用いられてもよい（Ｒｅｌ．１７と同様）。２番目以降のＲＡＲ内のＹビットの新規フィールドが、Ｍｓｇ３繰り返しの数の２Ｙ個までの候補値からの１つの値の指示に用いられてもよい。 A new field of Y bits in the RAR may be used to indicate one value from up to 2 Y candidate values for the number of Msg3 repeats. Two bits from the MCS field in the first RAR may be used to indicate one value from up to four candidate values for the number of Msg3 repeats (similar to Rel.17). A new field of Y bits in the second and subsequent RARs may be used to indicate one value from up to 2 Y candidate values for the number of Msg3 repeats.
《実施形態＃３－４》
　現在のＲＡＣＨ手順内において複数のＭｓｇ１繰り返しが行われる場合、ＲＡＲによって指示されるＭｓｇ３繰り返しの数の解釈は、その複数のＭｓｇ１繰り返しに対して、同じビームが用いられるか異なるビームが用いられるか、に依存してもよい。 《Embodiment #3-4》
If multiple Msg1 repetitions occur within the current RACH procedure, the interpretation of the number of Msg3 repetitions indicated by the RAR depends on whether the same beam or different beams are used for the multiple Msg1 repetitions; may depend on.
　現在のＲＡＣＨ手順内において複数のＭｓｇ１繰り返しがある場合、Ｍｓｇ３繰り返しの数のための、指示のビットの数と、候補値と、の少なくとも１つが、複数のＭｓｇ１繰り返しが同じビームを用いるケースと、複数のＭｓｇ１繰り返しが異なるビームを用いるケースと、の間において異なってもよい。 If there are multiple Msg1 repetitions within the current RACH procedure, at least one of the number of bits of the indication and the candidate value for the number of Msg3 repetitions is the case where multiple Msg1 repetitions use the same beam; The Msg1 repetitions may differ between cases using different beams.
　例えば、もし複数のＭｓｇ１繰り返しが同じビームを用いる場合、ＭＣＳフィールドからのＸビットが、Ｍｓｇ３繰り返しの数の２Ｘ個までの候補値からの１つの値の指示に用いられてもよい。Ｘは、２に等しくてもよいし、２より少なくてもよいし、２より多くてもよい。２Ｘ個までの候補値は、仕様において定義されてもよいし、ＰＢＣＨ／ＳＩＢ１　ＰＤＳＣＨ／ＲＲＣ　ＩＥによって設定されてもよい。２Ｘ個までの候補値は、Ｒｅｌ．１７のＭｓｇ３繰り返しをサポートするＵＥに対して設定される候補値と同じであってもよい。候補値は、４／８／１６／３２／６４などの上限を超えなくてもよい。 For example, if multiple Msg1 repetitions use the same beam, X bits from the MCS field may be used to indicate one value from up to 2X candidate values for the number of Msg3 repetitions. X may be equal to 2, less than 2, or more than 2. Up to 2X candidate values may be defined in the specification or configured by the PBCH/SIB1 PDSCH/RRC IE. Up to 2X candidate values are Rel. It may be the same as the candidate value set for a UE that supports 17 Msg3 repetitions. Candidate values do not have to exceed upper limits such as 4/8/16/32/64.
　ＲＡＲ内のＸビットの新規フィールドが、Ｍｓｇ３繰り返しの数の２Ｘ個までの候補値からの１つの値の指示に用いられてもよい。１番目のＲＡＲ内のＭＣＳフィールドからの２ビットが、Ｍｓｇ３繰り返しの数の４個までの候補値からの１つの値の指示に用いられてもよい（Ｒｅｌ．１７と同様）。２番目以降のＲＡＲ内のＸビットの新規フィールドが、Ｍｓｇ３繰り返しの数の２Ｘ個までの候補値からの１つの値の指示に用いられてもよい。 A new field of X bits in the RAR may be used to indicate one value from up to 2X candidate values for the number of Msg3 repeats. Two bits from the MCS field in the first RAR may be used to indicate one value from up to four candidate values for the number of Msg3 repeats (similar to Rel.17). A new field of X bits in the second and subsequent RARs may be used to indicate one value from up to 2X candidate values for the number of Msg3 repeats.
　例えば、もし複数のＭｓｇ１繰り返しが異なるビームを用いる場合、ＭＣＳフィールドからのＹビットが、Ｍｓｇ３繰り返しの数の２Ｙ個までの候補値からの１つの値の指示に用いられてもよい。Ｙは、２に等しくてもよいし、２より少なくてもよいし、２より多くてもよい。２Ｙ個までの候補値は、仕様において定義されてもよいし、ＰＢＣＨ／ＳＩＢ１　ＰＤＳＣＨ／ＲＲＣ　ＩＥによって設定されてもよい。２Ｘ個までの候補値は、Ｒｅｌ．１７のＭｓｇ３繰り返しをサポートするＵＥに対して設定される候補値と同じであってもよい。候補値は、４／８／１６／３２／６４などの上限を超えなくてもよい。 For example, if multiple Msg1 repetitions use different beams, Y bits from the MCS field may be used to indicate one value from up to 2 Y candidate values for the number of Msg3 repetitions. Y may be equal to 2, less than 2, or more than 2. Up to 2 Y candidate values may be defined in the specification or configured by the PBCH/SIB1 PDSCH/RRC IE. Up to 2X candidate values are Rel. It may be the same as the candidate value set for a UE that supports 17 Msg3 repetitions. Candidate values do not have to exceed upper limits such as 4/8/16/32/64.
　ＲＡＲ内のＹビットの新規フィールドが、Ｍｓｇ３繰り返しの数の２Ｙ個までの候補値からの１つの値の指示に用いられてもよい。１番目のＲＡＲ内のＭＣＳフィールドからの２ビットが、Ｍｓｇ３繰り返しの数の４個までの候補値からの１つの値の指示に用いられてもよい（Ｒｅｌ．１７と同様）。２番目以降のＲＡＲ内のＹビットの新規フィールドが、Ｍｓｇ３繰り返しの数の２Ｙ個までの候補値からの１つの値の指示に用いられてもよい。 A new field of Y bits in the RAR may be used to indicate one value from up to 2 Y candidate values for the number of Msg3 repeats. Two bits from the MCS field in the first RAR may be used to indicate one value from up to four candidate values for the number of Msg3 repeats (similar to Rel.17). A new field of Y bits in the second and subsequent RARs may be used to indicate one value from up to 2 Y candidate values for the number of Msg3 repeats.
《実施形態＃３－５》
　ＲＡＲによって指示されるＭｓｇ３繰り返しの数の解釈は、実施形態＃３－２、＃３－３、＃３－４の内のいくつかの組み合わせに依存してもよい。
・例えば、その解釈は、実施形態＃３－２、＃３－３の組み合わせに依存してもよい。
・例えば、その解釈は、実施形態＃３－２、＃３－４の組み合わせに依存してもよい。
・例えば、その解釈は、実施形態＃３－３、＃３－４の組み合わせに依存してもよい。
・例えば、その解釈は、実施形態＃３－２、＃３－３、＃３－４の組み合わせに依存してもよい。 《Embodiment #3-5》
Interpretation of the number of Msg3 repeats indicated by RAR may depend on some combination of embodiments #3-2, #3-3, #3-4.
- For example, the interpretation may depend on the combination of embodiments #3-2 and #3-3.
- For example, the interpretation may depend on the combination of embodiments #3-2 and #3-4.
- For example, the interpretation may depend on the combination of embodiments #3-3 and #3-4.
- For example, the interpretation may depend on the combination of embodiments #3-2, #3-3, and #3-4.
　この実施形態によれば、ＵＥは、Ｍｓｇ３の繰り返しの数を適切に決定できる。 According to this embodiment, the UE can appropriately determine the number of repetitions of Msg3.
＜補足＞
　上述の実施形態の少なくとも１つの動作は、特定のＵＥ能力（UE　capability）を報告した又は当該特定のＵＥ能力をサポートするＵＥに対してのみ適用されてもよい。 <Supplement>
The operations of at least one of the embodiments described above may apply only to UEs that have reported or support a particular UE capability.
　当該特定のＵＥ能力は、以下の少なくとも１つを示してもよい：
・上記実施形態の少なくとも１つについての特定の処理／動作／制御／情報をサポートすること。
・同時のＭｓｇ１繰り返し及びＭｓｇ３繰り返し（Ｍｓｇ１繰り返し及びＭｓｇ３繰り返しの組み合わせ／合同動作）をサポートすること。
・複数のＭｓｇ１繰り返しに対する１つのＲＡＲが送信されるケース（ケース１）において、１つのＲＡＣＨ手順内におけるＭｓｇ１繰り返し及びＭｓｇ３繰り返しの両方をサポートすること。
・複数のＭｓｇ１繰り返しに対する複数のＲＡＲが送信されるケース（ケース２）において、１つのＲＡＣＨ手順内におけるＭｓｇ１繰り返し及びＭｓｇ３繰り返しの両方をサポートすること。
・複数のＭｓｇ１繰り返しに同じ送信ビームが用いられるケースにおいて、１つのＲＡＣＨ手順内におけるＭｓｇ１繰り返し及びＭｓｇ３繰り返しの両方をサポートすること。
・複数のＭｓｇ１繰り返しに異なる送信ビームが用いられるケースにおいて、１つのＲＡＣＨ手順内におけるＭｓｇ１繰り返し及びＭｓｇ３繰り返しの両方をサポートすること。
・Ｍｓｇ１の１つ以上の繰り返しの１つ以上のビームに依存する、Ｍｓｇ３の１つ以上の繰り返しのビームを決定をサポートすること。
・Ｍｓｇ１の１つ以上の繰り返しに依存する、Ｍｓｇ３の繰り返しの数の再利用／解釈をサポートすること。 The particular UE capability may indicate at least one of the following:
- Supporting specific processing/operation/control/information for at least one of the above embodiments.
- Support simultaneous Msg1 repetition and Msg3 repetition (combination/joint operation of Msg1 repetition and Msg3 repetition).
- Support both Msg1 and Msg3 repetitions within one RACH procedure in the case where one RAR for multiple Msg1 repetitions is sent (case 1).
- Supporting both Msg1 and Msg3 repetitions within one RACH procedure in the case where multiple RARs for multiple Msg1 repetitions are sent (Case 2).
- Supporting both Msg1 and Msg3 repetitions within one RACH procedure in the case where the same transmit beam is used for multiple Msg1 repetitions.
- Supporting both Msg1 and Msg3 repetitions within one RACH procedure in the case where different transmit beams are used for multiple Msg1 repetitions.
- Supporting determining beams of one or more repetitions of Msg3 depending on one or more beams of one or more repetitions of Msg1.
- Support reuse/interpretation of the number of repeats of Msg3 depending on one or more repeats of Msg1.
　また、上記特定のＵＥ能力は、全周波数にわたって（周波数に関わらず共通に）適用される能力であってもよいし、周波数（例えば、セル、バンド、ＢＷＰ）ごとの能力であってもよいし、周波数レンジ（例えば、Frequency　Range　1（ＦＲ１）、ＦＲ２、ＦＲ３、ＦＲ４、ＦＲ５、ＦＲ２－１、ＦＲ２－２）ごとの能力であってもよいし、サブキャリア間隔（SubCarrier　Spacing（ＳＣＳ））ごとの能力であってもよい。 Further, the above-mentioned specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (for example, cell, band, BWP). , capability for each frequency range (for example, Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or for each subcarrier spacing (SCS). It may be the ability of
　また、上記特定のＵＥ能力は、全複信方式にわたって（複信方式に関わらず共通に）適用される能力であってもよいし、複信方式（例えば、時分割複信（Time　Division　Duplex（ＴＤＤ））、周波数分割複信（Frequency　Division　Duplex（ＦＤＤ）））ごとの能力であってもよい。 Furthermore, the above-mentioned specific UE capability may be a capability that is applied across all duplex schemes (commonly regardless of the duplex scheme), or may be a capability that is applied across all duplex schemes (for example, Time Division Duplex). The capability may be for each frequency division duplex (TDD)) or frequency division duplex (FDD)).
　また、上述の実施形態の少なくとも１つの動作は、ＵＥが上位レイヤシグナリングによって上述の実施形態に関連する特定の情報を設定された場合に適用されてもよい。例えば、当該特定の情報は、上述の実施形態の少なくとも１つの動作を有効化することを示す情報、特定のリリース（例えば、Ｒｅｌ．１８）向けの任意のＲＲＣパラメータなどであってもよい。 Furthermore, at least one operation of the above-described embodiments may be applied when the UE is configured with specific information related to the above-described embodiments by upper layer signaling. For example, the specific information may be information indicating enabling at least one operation of the embodiments described above, any RRC parameters for a specific release (eg, Rel. 18), and the like.
　ＵＥは、上記特定のＵＥ能力の少なくとも１つの動作をサポートしない又は上記特定の情報を設定されない場合、例えばＲｅｌ．１５／１６／１７の動作を適用してもよい。 If the UE does not support at least one operation of the specific UE capabilities or is not configured with the specific information, for example, Rel. 15/16/17 operations may be applied.
（付記Ａ）
　本開示の一実施形態に関して、以下の発明を付記する。
［付記１］
　メッセージ１の繰り返しの能力に関する第１能力情報と、メッセージ３の繰り返しの能力に関する第２能力情報と、を送信する送信部と、
　前記第１能力情報及び前記第２能力情報に基づいて、前記メッセージ１の繰り返し及び前記メッセージ３の繰り返しを含む第１ランダムアクセス手順を行うか、前記メッセージ１の繰り返し及び前記メッセージ３の繰り返しの少なくとも１つを含まない第２ランダムアクセス手順を行うか、を決定する制御部と、を有する端末。
［付記２］
　前記制御部は、第１ランダムアクセスリソースを前記第１ランダムアクセス手順に用い、前記第１ランダムアクセスリソースと異なる第２ランダムアクセスリソースを前記第２ランダムアクセス手順に用いる、付記１に記載の端末。
［付記３］
　前記制御部は、参照信号受信電力と閾値の比較に基づいて、前記第１ランダムアクセス手順を行うか、前記第２ランダムアクセス手順を行うか、を決定する、付記１又は付記２に記載の端末。
［付記４］
　前記制御部は、前記メッセージ１の繰り返しの最大数と、参照信号受信電力に対する閾値と、の少なくとも１つに関する情報の受信を制御する、付記１から付記３のいずれかに記載の端末。 (Appendix A)
Regarding one embodiment of the present disclosure, the following invention will be added.
[Additional note 1]
a transmitter that transmits first capability information regarding the ability to repeat message 1 and second capability information regarding the ability to repeat message 3;
Based on the first capability information and the second capability information, a first random access procedure including repeating the message 1 and repeating the message 3 is performed, or at least repeating the message 1 and repeating the message 3. a control unit that determines whether to perform a second random access procedure that does not include one.
[Additional note 2]
The terminal according to supplementary note 1, wherein the control unit uses a first random access resource for the first random access procedure and uses a second random access resource different from the first random access resource for the second random access procedure.
[Additional note 3]
The terminal according to supplementary note 1 or supplementary note 2, wherein the control unit determines whether to perform the first random access procedure or the second random access procedure based on a comparison between reference signal reception power and a threshold value. .
[Additional note 4]
The terminal according to any one of appendices 1 to 3, wherein the control unit controls reception of information regarding at least one of a maximum number of repetitions of the message 1 and a threshold for reference signal reception power.
（付記Ｂ）
　本開示の一実施形態に関して、以下の発明を付記する。
［付記１］
　メッセージ１の繰り返しを含む第１ランダムアクセス手順に関する情報を受信する受信部と、
　前記情報に基づいて、第１ランダムアクセスリソースを、前記第１ランダムアクセス手順に用い、前記第１ランダムアクセスリソースと異なる第２ランダムアクセスリソースを、前記メッセージ１の繰り返しを含まない第２ランダムアクセス手順に用いる制御部と、を有する端末。
［付記２］
　前記情報は、前記第１ランダムアクセスリソースのためのプリアンブルインデックスの数と、前記第１ランダムアクセスリソースのための最初のプリアンブルインデックスと、の少なくとも１つを含む、付記１に記載の端末。
［付記３］
　前記制御部は、第１ランダムアクセスチャネルオケージョンを、前記第１ランダムアクセス手順に用い、前記第１ランダムアクセスチャネルオケージョンと異なる第２ランダムアクセスチャネルオケージョンを、前記第２ランダムアクセス手順に用いる、付記１又は付記２に記載の端末。
［付記４］
　前記制御部は、マスクインデックスと、前記第２ランダムアクセス手順のための第２ランダムアクセスチャネルオケージョンと、の少なくとも１つに基づいて、前記第１ランダムアクセス手順のための第１ランダムアクセスチャネルオケージョンを決定する、付記１から付記３のいずれかに記載の端末。 (Appendix B)
Regarding one embodiment of the present disclosure, the following invention will be added.
[Additional note 1]
a receiving unit for receiving information regarding a first random access procedure including repetition of message 1;
Based on the information, a first random access resource is used for the first random access procedure, and a second random access resource different from the first random access resource is used for the second random access procedure that does not involve repeating the message 1. A terminal having a control unit used for.
[Additional note 2]
The terminal according to supplementary note 1, wherein the information includes at least one of a number of preamble indexes for the first random access resource and a first preamble index for the first random access resource.
[Additional note 3]
Supplementary Note 1, wherein the control unit uses a first random access channel occasion for the first random access procedure, and uses a second random access channel occasion different from the first random access channel occasion for the second random access procedure. Or the terminal described in Appendix 2.
[Additional note 4]
The control unit determines a first random access channel occasion for the first random access procedure based on at least one of a mask index and a second random access channel occasion for the second random access procedure. The terminal according to any one of Supplementary Notes 1 to 3 to be determined.
（付記Ｃ）
　本開示の一実施形態に関して、以下の発明を付記する。
［付記１］
　メッセージ１の複数の繰り返し及びメッセージ３の複数の繰り返しを含むランダムアクセス手順に関する情報を受信する受信部と、
　前記情報に基づいて、前記メッセージ１の複数の繰り返しに用いられる１つ以上の第１ビームに基づいて、前記メッセージ３の複数の繰り返しに用いられる１つ以上の第２ビームを決定する制御部と、を有する端末。
［付記２］
　前記制御部は、前記１つ以上の第１ビームの中から、前記１つ以上の第２ビームを決定する、付記１に記載の端末。
［付記３］
　前記メッセージ１の複数の繰り返しに対して１つのランダムアクセスレスポンスが送信される、付記１又は付記２に記載の端末。
［付記４］
　前記メッセージ１の複数の繰り返しのそれぞれに対して１つのランダムアクセスレスポンスが送信される、付記１から付記３のいずれかに記載の端末。 (Appendix C)
Regarding one embodiment of the present disclosure, the following invention will be added.
[Additional note 1]
a receiving unit for receiving information regarding a random access procedure comprising multiple repetitions of message 1 and multiple repetitions of message 3;
a controller that determines one or more second beams to be used for the plurality of repetitions of the message 3 based on the one or more first beams used for the plurality of repetitions of the message 1 based on the information; , a terminal with.
[Additional note 2]
The terminal according to supplementary note 1, wherein the control unit determines the one or more second beams from among the one or more first beams.
[Additional note 3]
The terminal according to appendix 1 or 2, wherein one random access response is sent for multiple repetitions of message 1.
[Additional note 4]
3. The terminal according to any one of appendices 1 to 3, wherein one random access response is sent for each of a plurality of repetitions of message 1.
（付記Ｄ）
　本開示の一実施形態に関して、以下の発明を付記する。
［付記１］
　メッセージ３の繰り返しの数に関する指示情報を受信する受信部と、
　前記指示情報と、前記メッセージ３の繰り返しを含むランダムアクセス手順内のメッセージ１の繰り返しに関する情報と、に基づいて、前記メッセージ３の繰り返しの数を決定する制御部と、を有する端末。
［付記２］
　前記情報は、前記メッセージ１の繰り返しの数に関する、付記１に記載の端末。
［付記３］
　前記情報は、前記メッセージ１に対するランダムアクセスレスポンスの数に関する、付記１又は付記２に記載の端末。
［付記４］
　前記情報は、前記メッセージ１の繰り返しに用いられるビームの数に関する、付記１から付記３のいずれかに記載の端末。 (Appendix D)
Regarding one embodiment of the present disclosure, the following invention will be added.
[Additional note 1]
a receiver for receiving instruction information regarding the number of repetitions of message 3;
A terminal comprising: a control unit that determines the number of repetitions of the message 3 based on the instruction information and information regarding the repetition of the message 1 in a random access procedure including the repetition of the message 3.
[Additional note 2]
The terminal according to supplementary note 1, wherein the information relates to the number of repetitions of the message 1.
[Additional note 3]
The terminal according to supplementary note 1 or supplementary note 2, wherein the information relates to the number of random access responses to the message 1.
[Additional note 4]
The terminal according to any one of appendices 1 to 3, wherein the information relates to the number of beams used to repeat the message 1.
（無線通信システム）
　以下、本開示の一実施形態に係る無線通信システムの構成について説明する。この無線通信システムでは、本開示の上記各実施形態に係る無線通信方法のいずれか又はこれらの組み合わせを用いて通信が行われる。 (wireless communication system)
The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above-described embodiments of the present disclosure.
　図２３は、一実施形態に係る無線通信システムの概略構成の一例を示す図である。無線通信システム１は、Third　Generation　Partnership　Project（３ＧＰＰ）によって仕様化されるLong　Term　Evolution（ＬＴＥ）、5th　generation　mobile　communication　system　New　Radio（５Ｇ　ＮＲ）などを用いて通信を実現するシステムであってもよい。 FIG. 23 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an 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). .
　また、無線通信システム１は、複数のRadio　Access　Technology（ＲＡＴ）間のデュアルコネクティビティ（マルチＲＡＴデュアルコネクティビティ（Multi-RAT　Dual　Connectivity（ＭＲ－ＤＣ）））をサポートしてもよい。ＭＲ－ＤＣは、ＬＴＥ（Evolved　Universal　Terrestrial　Radio　Access（Ｅ－ＵＴＲＡ））とＮＲとのデュアルコネクティビティ（E-UTRA-NR　Dual　Connectivity（ＥＮ－ＤＣ））、ＮＲとＬＴＥとのデュアルコネクティビティ（NR-E-UTRA　Dual　Connectivity（ＮＥ－ＤＣ））などを含んでもよい。 Additionally, the wireless communication system 1 may support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC has dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), and dual connectivity between NR and LTE (NR-E -UTRA Dual Connectivity (NE-DC)).
　ＥＮ－ＤＣでは、ＬＴＥ（Ｅ－ＵＴＲＡ）の基地局（ｅＮＢ）がマスタノード（Master　Node（ＭＮ））であり、ＮＲの基地局（ｇＮＢ）がセカンダリノード（Secondary　Node（ＳＮ））である。ＮＥ－ＤＣでは、ＮＲの基地局（ｇＮＢ）がＭＮであり、ＬＴＥ（Ｅ－ＵＴＲＡ）の基地局（ｅＮＢ）がＳＮである。 In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (Secondary Node (SN)). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.
　無線通信システム１は、同一のＲＡＴ内の複数の基地局間のデュアルコネクティビティ（例えば、ＭＮ及びＳＮの双方がＮＲの基地局（ｇＮＢ）であるデュアルコネクティビティ（NR-NR　Dual　Connectivity（ＮＮ－ＤＣ）））をサポートしてもよい。 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) where both the MN and SN are NR base stations (gNB)). )) may be supported.
　無線通信システム１は、比較的カバレッジの広いマクロセルＣ１を形成する基地局１１と、マクロセルＣ１内に配置され、マクロセルＣ１よりも狭いスモールセルＣ２を形成する基地局１２（１２ａ－１２ｃ）と、を備えてもよい。ユーザ端末２０は、少なくとも１つのセル内に位置してもよい。各セル及びユーザ端末２０の配置、数などは、図に示す態様に限定されない。以下、基地局１１及び１２を区別しない場合は、基地局１０と総称する。 The wireless communication system 1 includes a base station 11 that forms a macro cell C1 with relatively wide coverage, and base stations 12 (12a-12c) that are located within the macro cell C1 and form a small cell C2 that is narrower than the macro cell C1. You may prepare. User terminal 20 may be located within at least one cell. The arrangement, number, etc. of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.
　ユーザ端末２０は、複数の基地局１０のうち、少なくとも１つに接続してもよい。ユーザ端末２０は、複数のコンポーネントキャリア（Component　Carrier（ＣＣ））を用いたキャリアアグリゲーション（Carrier　Aggregation（ＣＡ））及びデュアルコネクティビティ（ＤＣ）の少なくとも一方を利用してもよい。 The user terminal 20 may be connected to at least one of the plurality of base stations 10. The user terminal 20 may use at least one of carrier aggregation (CA) using a plurality of component carriers (CC) and dual connectivity (DC).
　各ＣＣは、第１の周波数帯（Frequency　Range　1（ＦＲ１））及び第２の周波数帯（Frequency　Range　2（ＦＲ２））の少なくとも１つに含まれてもよい。マクロセルＣ１はＦＲ１に含まれてもよいし、スモールセルＣ２はＦＲ２に含まれてもよい。例えば、ＦＲ１は、６ＧＨｚ以下の周波数帯（サブ６ＧＨｚ（sub-6GHz））であってもよいし、ＦＲ２は、２４ＧＨｚよりも高い周波数帯（above-24GHz）であってもよい。なお、ＦＲ１及びＦＲ２の周波数帯、定義などはこれらに限られず、例えばＦＲ１がＦＲ２よりも高い周波数帯に該当してもよい。 Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). Macro cell C1 may be included in FR1, and small cell C2 may be included in FR2. For example, FR1 may be a frequency band below 6 GHz (sub-6 GHz), and FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and FR1 may correspond to a higher frequency band than FR2, for example.
　また、ユーザ端末２０は、各ＣＣにおいて、時分割複信（Time　Division　Duplex（ＴＤＤ））及び周波数分割複信（Frequency　Division　Duplex（ＦＤＤ））の少なくとも１つを用いて通信を行ってもよい。 Further, the user terminal 20 may communicate using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.
　複数の基地局１０は、有線（例えば、Common　Public　Radio　Interface（ＣＰＲＩ）に準拠した光ファイバ、Ｘ２インターフェースなど）又は無線（例えば、ＮＲ通信）によって接続されてもよい。例えば、基地局１１及び１２間においてＮＲ通信がバックホールとして利用される場合、上位局に該当する基地局１１はIntegrated　Access　Backhaul（ＩＡＢ）ドナー、中継局（リレー）に該当する基地局１２はＩＡＢノードと呼ばれてもよい。 The plurality of base stations 10 may be connected by wire (for example, optical fiber, X2 interface, etc. compliant with Common Public Radio Interface (CPRI)) or wirelessly (for example, NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is an upper station, is an Integrated Access Backhaul (IAB) donor, and base station 12, which is a relay station, is an IAB donor. May also be called a node.
　基地局１０は、他の基地局１０を介して、又は直接コアネットワーク３０に接続されてもよい。コアネットワーク３０は、例えば、Evolved　Packet　Core（ＥＰＣ）、5G　Core　Network（５ＧＣＮ）、Next　Generation　Core（ＮＧＣ）などの少なくとも１つを含んでもよい。 The base station 10 may be connected to the core network 30 via another base station 10 or directly. 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.
　ユーザ端末２０は、ＬＴＥ、ＬＴＥ－Ａ、５Ｇなどの通信方式の少なくとも１つに対応した端末であってもよい。 The user terminal 20 may be a terminal compatible with at least one of communication systems such as LTE, LTE-A, and 5G.
　無線通信システム１においては、直交周波数分割多重（Orthogonal　Frequency　Division　Multiplexing（ＯＦＤＭ））ベースの無線アクセス方式が利用されてもよい。例えば、下りリンク（Downlink（ＤＬ））及び上りリンク（Uplink（ＵＬ））の少なくとも一方において、Cyclic　Prefix　OFDM（ＣＰ－ＯＦＤＭ）、Discrete　Fourier　Transform　Spread　OFDM（ＤＦＴ－ｓ－ＯＦＤＭ）、Orthogonal　Frequency　Division　Multiple　Access（ＯＦＤＭＡ）、Single　Carrier　Frequency　Division　Multiple　Access（ＳＣ－ＦＤＭＡ）などが利用されてもよい。 In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access method may be used. For example, in at least one of the downlink (DL) and uplink (UL), Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc. may be used.
　無線アクセス方式は、波形（waveform）と呼ばれてもよい。なお、無線通信システム１においては、ＵＬ及びＤＬの無線アクセス方式には、他の無線アクセス方式（例えば、他のシングルキャリア伝送方式、他のマルチキャリア伝送方式）が用いられてもよい。 A wireless access method may also be called a waveform. Note that in the wireless communication system 1, other wireless access methods (for example, other single carrier transmission methods, other multicarrier transmission methods) may be used as the UL and DL radio access methods.
　無線通信システム１では、下りリンクチャネルとして、各ユーザ端末２０で共有される下り共有チャネル（Physical　Downlink　Shared　Channel（ＰＤＳＣＨ））、ブロードキャストチャネル（Physical　Broadcast　Channel（ＰＢＣＨ））、下り制御チャネル（Physical　Downlink　Control　Channel（ＰＤＣＣＨ））などが用いられてもよい。 In the wireless communication system 1, the downlink channels include a physical downlink shared channel (PDSCH) shared by each user terminal 20, a broadcast channel (physical broadcast channel (PBCH)), and a downlink control channel (physical downlink control). Channel (PDCCH)) or the like may be used.
　また、無線通信システム１では、上りリンクチャネルとして、各ユーザ端末２０で共有される上り共有チャネル（Physical　Uplink　Shared　Channel（ＰＵＳＣＨ））、上り制御チャネル（Physical　Uplink　Control　Channel（ＰＵＣＣＨ））、ランダムアクセスチャネル（Physical　Random　Access　Channel（ＰＲＡＣＨ））などが用いられてもよい。 In the wireless communication system 1, uplink channels include a physical uplink shared channel (PUSCH) shared by each user terminal 20, an uplink control channel (PUCCH), and a random access channel. (Physical Random Access Channel (PRACH)) or the like may be used.
　ＰＤＳＣＨによって、ユーザデータ、上位レイヤ制御情報、System　Information　Block（ＳＩＢ）などが伝送される。ＰＵＳＣＨによって、ユーザデータ、上位レイヤ制御情報などが伝送されてもよい。また、ＰＢＣＨによって、Master　Information　Block（ＭＩＢ）が伝送されてもよい。 User data, upper layer control information, System Information Block (SIB), etc. are transmitted by the PDSCH. User data, upper layer control information, etc. may be transmitted by PUSCH. Furthermore, a Master Information Block (MIB) may be transmitted via the PBCH.
　ＰＤＣＣＨによって、下位レイヤ制御情報が伝送されてもよい。下位レイヤ制御情報は、例えば、ＰＤＳＣＨ及びＰＵＳＣＨの少なくとも一方のスケジューリング情報を含む下り制御情報（Downlink　Control　Information（ＤＣＩ））を含んでもよい。 Lower layer control information may be transmitted by PDCCH. The lower layer control information may include, for example, downlink control information (DCI) that includes scheduling information for at least one of PDSCH and PUSCH.
　なお、ＰＤＳＣＨをスケジューリングするＤＣＩは、ＤＬアサインメント、ＤＬ　ＤＣＩなどと呼ばれてもよいし、ＰＵＳＣＨをスケジューリングするＤＣＩは、ＵＬグラント、ＵＬ　ＤＣＩなどと呼ばれてもよい。なお、ＰＤＳＣＨはＤＬデータで読み替えられてもよいし、ＰＵＳＣＨはＵＬデータで読み替えられてもよい。 Note that the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Note that PDSCH may be replaced with DL data, and PUSCH may be replaced with UL data.
　ＰＤＣＣＨの検出には、制御リソースセット（COntrol　REsource　SET（ＣＯＲＥＳＥＴ））及びサーチスペース（search　space）が利用されてもよい。ＣＯＲＥＳＥＴは、ＤＣＩをサーチするリソースに対応する。サーチスペースは、ＰＤＣＣＨ候補（PDCCH　candidates）のサーチ領域及びサーチ方法に対応する。１つのＣＯＲＥＳＥＴは、１つ又は複数のサーチスペースに関連付けられてもよい。ＵＥは、サーチスペース設定に基づいて、あるサーチスペースに関連するＣＯＲＥＳＥＴをモニタしてもよい。 A control resource set (CONtrol REsource SET (CORESET)) and a search space may be used to detect the PDCCH. CORESET corresponds to a resource for searching DCI. The search space corresponds to a search area and a search method for PDCCH candidates (PDCCH candidates). One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.
　１つのサーチスペースは、１つ又は複数のアグリゲーションレベル（aggregation　Level）に該当するＰＤＣＣＨ候補に対応してもよい。１つ又は複数のサーチスペースは、サーチスペースセットと呼ばれてもよい。なお、本開示の「サーチスペース」、「サーチスペースセット」、「サーチスペース設定」、「サーチスペースセット設定」、「ＣＯＲＥＳＥＴ」、「ＣＯＲＥＳＥＴ設定」などは、互いに読み替えられてもよい。 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.
　ＰＵＣＣＨによって、チャネル状態情報（Channel　State　Information（ＣＳＩ））、送達確認情報（例えば、Hybrid　Automatic　Repeat　reQuest　ACKnowledgement（ＨＡＲＱ－ＡＣＫ）、ＡＣＫ／ＮＡＣＫなどと呼ばれてもよい）及びスケジューリングリクエスト（Scheduling　Request（ＳＲ））の少なくとも１つを含む上り制御情報（Uplink　Control　Information（ＵＣＩ））が伝送されてもよい。ＰＲＡＣＨによって、セルとの接続確立のためのランダムアクセスプリアンブルが伝送されてもよい。 The PUCCH allows channel state information (CSI), delivery confirmation information (for example, may be called Hybrid Automatic Repeat Request ACKnowledgement (HARQ-ACK), ACK/NACK, etc.), and scheduling request ( Uplink Control Information (UCI) including at least one of SR)) may be transmitted. A random access preamble for establishing a connection with a cell may be transmitted by PRACH.
　なお、本開示において下りリンク、上りリンクなどは「リンク」を付けずに表現されてもよい。また、各種チャネルの先頭に「物理（Physical）」を付けずに表現されてもよい。 Note that in this disclosure, downlinks, uplinks, etc. may be expressed without adding "link". Furthermore, various channels may be expressed without adding "Physical" at the beginning.
　無線通信システム１では、同期信号（Synchronization　Signal（ＳＳ））、下りリンク参照信号（Downlink　Reference　Signal（ＤＬ－ＲＳ））などが伝送されてもよい。無線通信システム１では、ＤＬ－ＲＳとして、セル固有参照信号（Cell-specific　Reference　Signal（ＣＲＳ））、チャネル状態情報参照信号（Channel　State　Information　Reference　Signal（ＣＳＩ－ＲＳ））、復調用参照信号（DeModulation　Reference　Signal（ＤＭＲＳ））、位置決定参照信号（Positioning　Reference　Signal（ＰＲＳ））、位相トラッキング参照信号（Phase　Tracking　Reference　Signal（ＰＴＲＳ））などが伝送されてもよい。 In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), and the like may be transmitted. In the wireless communication system 1, the DL-RS includes a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), and a demodulation reference signal (DeModulation). Reference Signal (DMRS)), Positioning Reference Signal (PRS), Phase Tracking Reference Signal (PTRS), etc. may be transmitted.
　同期信号は、例えば、プライマリ同期信号（Primary　Synchronization　Signal（ＰＳＳ））及びセカンダリ同期信号（Secondary　Synchronization　Signal（ＳＳＳ））の少なくとも１つであってもよい。ＳＳ（ＰＳＳ、ＳＳＳ）及びＰＢＣＨ（及びＰＢＣＨ用のＤＭＲＳ）を含む信号ブロックは、ＳＳ／ＰＢＣＨブロック、SS　Block（ＳＳＢ）などと呼ばれてもよい。なお、ＳＳ、ＳＳＢなども、参照信号と呼ばれてもよい。 The synchronization signal may be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS/PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.
　また、無線通信システム１では、上りリンク参照信号（Uplink　Reference　Signal（ＵＬ－ＲＳ））として、測定用参照信号（Sounding　Reference　Signal（ＳＲＳ））、復調用参照信号（ＤＭＲＳ）などが伝送されてもよい。なお、ＤＭＲＳはユーザ端末固有参照信号（UE-specific　Reference　Signal）と呼ばれてもよい。 In addition, in the wireless communication system 1, measurement reference signals (Sounding Reference Signal (SRS)), demodulation reference signals (DMRS), etc. are transmitted as uplink reference signals (UL-RS). good. Note that DMRS may be called a user terminal-specific reference signal (UE-specific reference signal).
（基地局）
　図２４は、一実施形態に係る基地局の構成の一例を示す図である。基地局１０は、制御部１１０、送受信部１２０、送受信アンテナ１３０及び伝送路インターフェース（transmission　line　interface）１４０を備えている。なお、制御部１１０、送受信部１２０及び送受信アンテナ１３０及び伝送路インターフェース１４０は、それぞれ１つ以上が備えられてもよい。 (base station)
FIG. 24 is a diagram illustrating an example of the configuration of a base station according to an embodiment. The base station 10 includes a control section 110, a transmitting/receiving section 120, a transmitting/receiving antenna 130, and a transmission line interface 140. Note that 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.
　なお、本例では、本実施の形態における特徴部分の機能ブロックを主に示しており、基地局１０は、無線通信に必要な他の機能ブロックも有すると想定されてもよい。以下で説明する各部の処理の一部は、省略されてもよい。 Note that this example mainly shows functional blocks that are characteristic 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 entire base station 10. The control unit 110 can be configured from a controller, a control circuit, etc., which will be explained based on common recognition in the technical field related to the present disclosure.
　制御部１１０は、信号の生成、スケジューリング（例えば、リソース割り当て、マッピング）などを制御してもよい。制御部１１０は、送受信部１２０、送受信アンテナ１３０及び伝送路インターフェース１４０を用いた送受信、測定などを制御してもよい。制御部１１０は、信号として送信するデータ、制御情報、系列（sequence）などを生成し、送受信部１２０に転送してもよい。制御部１１０は、通信チャネルの呼処理（設定、解放など）、基地局１０の状態管理、無線リソースの管理などを行ってもよい。 The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), and the like. The control unit 110 may control transmission and reception, measurement, etc. using the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission path interface 140. The control unit 110 may generate data, control information, a sequence, etc. to be transmitted as a signal, and may transfer the generated data to the transmitting/receiving unit 120. The control unit 110 may perform communication channel call processing (setting, release, etc.), status management of the base station 10, radio resource management, and the like.
　送受信部１２０は、ベースバンド（baseband）部１２１、Radio　Frequency（ＲＦ）部１２２、測定部１２３を含んでもよい。ベースバンド部１２１は、送信処理部１２１１及び受信処理部１２１２を含んでもよい。送受信部１２０は、本開示に係る技術分野での共通認識に基づいて説明されるトランスミッター／レシーバー、ＲＦ回路、ベースバンド回路、フィルタ、位相シフタ（phase　shifter）、測定回路、送受信回路などから構成することができる。 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 transmitter/receiver unit 120 includes a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitter/receiver circuit, etc., which are explained based on common understanding in the technical field related to the present disclosure. be able to.
　送受信部１２０は、一体の送受信部として構成されてもよいし、送信部及び受信部から構成されてもよい。当該送信部は、送信処理部１２１１、ＲＦ部１２２から構成されてもよい。当該受信部は、受信処理部１２１２、ＲＦ部１２２、測定部１２３から構成されてもよい。 The transmitting/receiving section 120 may be configured as an integrated transmitting/receiving section, or may be configured from a transmitting section and a receiving section. The transmitting section may include a transmitting processing section 1211 and an RF section 122. The reception section may include 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 transmitter/receiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitter/receiver 120 may receive the above-mentioned uplink channel, uplink reference signal, and the like.
　送受信部１２０は、デジタルビームフォーミング（例えば、プリコーディング）、アナログビームフォーミング（例えば、位相回転）などを用いて、送信ビーム及び受信ビームの少なくとも一方を形成してもよい。 The transmitting/receiving unit 120 may form at least one of a transmitting beam and a receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.
　送受信部１２０（送信処理部１２１１）は、例えば制御部１１０から取得したデータ、制御情報などに対して、Packet　Data　Convergence　Protocol（ＰＤＣＰ）レイヤの処理、Radio　Link　Control（ＲＬＣ）レイヤの処理（例えば、ＲＬＣ再送制御）、Medium　Access　Control（ＭＡＣ）レイヤの処理（例えば、ＨＡＲＱ再送制御）などを行い、送信するビット列を生成してもよい。 The transmitting/receiving 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.
　送受信部１２０（送信処理部１２１１）は、送信するビット列に対して、チャネル符号化（誤り訂正符号化を含んでもよい）、変調、マッピング、フィルタ処理、離散フーリエ変換（Discrete　Fourier　Transform（ＤＦＴ））処理（必要に応じて）、逆高速フーリエ変換（Inverse　Fast　Fourier　Transform（ＩＦＦＴ））処理、プリコーディング、デジタル－アナログ変換などの送信処理を行い、ベースバンド信号を出力してもよい。 The transmitting/receiving unit 120 (transmission processing unit 1211) performs channel encoding (which may include error correction encoding), modulation, mapping, filter processing, and discrete Fourier transform (DFT) on the bit string to be transmitted. A baseband signal may be output by performing transmission processing such as processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion.
　送受信部１２０（ＲＦ部１２２）は、ベースバンド信号に対して、無線周波数帯への変調、フィルタ処理、増幅などを行い、無線周波数帯の信号を、送受信アンテナ１３０を介して送信してもよい。 The transmitting/receiving unit 120 (RF unit 122) may perform modulation, filter processing, amplification, etc. on the baseband signal in a radio frequency band, and may transmit the signal in the radio frequency band via the transmitting/receiving antenna 130. .
　一方、送受信部１２０（ＲＦ部１２２）は、送受信アンテナ１３０によって受信された無線周波数帯の信号に対して、増幅、フィルタ処理、ベースバンド信号への復調などを行ってもよい。 On the other hand, the transmitting/receiving section 120 (RF section 122) may perform amplification, filter processing, demodulation into a baseband signal, etc. on the radio frequency band signal received by the transmitting/receiving antenna 130.
　送受信部１２０（受信処理部１２１２）は、取得されたベースバンド信号に対して、アナログ－デジタル変換、高速フーリエ変換（Fast　Fourier　Transform（ＦＦＴ））処理、逆離散フーリエ変換（Inverse　Discrete　Fourier　Transform（ＩＤＦＴ））処理（必要に応じて）、フィルタ処理、デマッピング、復調、復号（誤り訂正復号を含んでもよい）、ＭＡＣレイヤ処理、ＲＬＣレイヤの処理及びＰＤＣＰレイヤの処理などの受信処理を適用し、ユーザデータなどを取得してもよい。 The transmitting/receiving unit 120 (reception processing unit 1212) performs analog-to-digital conversion, fast Fourier transform (FFT) processing, and inverse discrete Fourier transform (IDFT) on the acquired baseband signal. )) processing (if necessary), applying reception processing such as filter processing, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing and PDCP layer processing, User data etc. may also be acquired.
　送受信部１２０（測定部１２３）は、受信した信号に関する測定を実施してもよい。例えば、測定部１２３は、受信した信号に基づいて、Radio　Resource　Management（ＲＲＭ）測定、Channel　State　Information（ＣＳＩ）測定などを行ってもよい。測定部１２３は、受信電力（例えば、Reference　Signal　Received　Power（ＲＳＲＰ））、受信品質（例えば、Reference　Signal　Received　Quality（ＲＳＲＱ）、Signal　to　Interference　plus　Noise　Ratio（ＳＩＮＲ）、Signal　to　Noise　Ratio（ＳＮＲ））、信号強度（例えば、Received　Signal　Strength　Indicator（ＲＳＳＩ））、伝搬路情報（例えば、ＣＳＩ）などについて測定してもよい。測定結果は、制御部１１０に出力されてもよい。 The transmitting/receiving unit 120 (measuring unit 123) may perform measurements regarding the received signal. For example, 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 is the receiving power (for example, Reference Signal Received Power (RSRP)), Receive Quality (eg, Reference Signal Received Quality (RSRQ), Signal To InterfERENCE PLUS NOI. SE RATIO (SINR), Signal to Noise Ratio (SNR) , signal strength (for example, Received Signal Strength Indicator (RSSI)), propagation path information (for example, CSI), etc. may be measured. The measurement results may be output to the control unit 110.
　伝送路インターフェース１４０は、コアネットワーク３０に含まれる装置、他の基地局１０などとの間で信号を送受信（バックホールシグナリング）し、ユーザ端末２０のためのユーザデータ（ユーザプレーンデータ）、制御プレーンデータなどを取得、伝送などしてもよい。 The transmission path interface 140 transmits and receives signals (backhaul signaling) between devices included in the core network 30, other base stations 10, etc., and transmits and receives user data (user plane data) for the user terminal 20, control plane It is also possible to acquire and transmit data.
　なお、本開示における基地局１０の送信部及び受信部は、送受信部１２０、送受信アンテナ１３０及び伝送路インターフェース１４０の少なくとも１つによって構成されてもよい。 Note that 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 path interface 140.
　送受信部１２０は、メッセージ１の繰り返しの能力に関する第１能力情報と、メッセージ３の繰り返しの能力に関する第２能力情報と、を受信してもよい。制御部１１０は、前記第１能力情報及び前記第２能力情報に基づいて、前記メッセージ１の繰り返し及び前記メッセージ３の繰り返しを含む第１ランダムアクセス手順を行うか、前記メッセージ１の繰り返し及び前記メッセージ３の繰り返しの少なくとも１つを含まない第２ランダムアクセス手順を行うか、を決定してもよい。 The transmitting/receiving unit 120 may receive first ability information regarding the ability to repeat message 1 and second ability information regarding the ability to repeat message 3. The control unit 110 performs a first random access procedure including repeating the message 1 and repeating the message 3 based on the first capability information and the second capability information, or performs a first random access procedure including repeating the message 1 and repeating the message 3. It may be determined whether to perform a second random access procedure that does not include at least one of the repetitions of 3.
　送受信部１２０は、メッセージ１の繰り返しを含む第１ランダムアクセス手順に関する情報を送信してもよい。制御部１１０は、前記情報に基づいて、第１ランダムアクセスリソースを、前記第１ランダムアクセス手順に用い、前記第１ランダムアクセスリソースと異なる第２ランダムアクセスリソースを、前記メッセージ１の繰り返しを含まない第２ランダムアクセス手順に用いてもよい。 The transmitting/receiving unit 120 may transmit information regarding the first random access procedure including repeating message 1. Based on the information, the control unit 110 uses a first random access resource for the first random access procedure, and uses a second random access resource different from the first random access resource that does not include repetition of the message 1. It may also be used in the second random access procedure.
　送受信部１２０は、メッセージ１の複数の繰り返し及びメッセージ３の複数の繰り返しを含むランダムアクセス手順に関する情報を送信してもよい。制御部１１０は、前記情報に基づいて、前記メッセージ１の複数の繰り返しに用いられる１つ以上の第１ビームに基づいて、前記メッセージ３の複数の繰り返しに用いられる１つ以上の第２ビームを決定してもよい。 The transmitting/receiving unit 120 may transmit information regarding a random access procedure including multiple repetitions of message 1 and multiple repetitions of message 3. Based on the information, the control unit 110 controls one or more second beams used for the plurality of repetitions of the message 3 based on the one or more first beams used for the plurality of repetitions of the message 1. You may decide.
　送受信部１２０は、メッセージ３の繰り返しの数に関する指示情報を送信してもよい。制御部１１０は、前記指示情報と、前記メッセージ３の繰り返しを含むランダムアクセス手順内のメッセージ１の繰り返しに関する情報と、に基づいて、前記メッセージ３の繰り返しの数を決定してもよい。 The transmitting/receiving unit 120 may transmit instruction information regarding the number of repetitions of message 3. The control unit 110 may determine the number of repetitions of the message 3 based on the instruction information and information regarding the repetition of the message 1 in the random access procedure including the repetition of the message 3.
（ユーザ端末）
　図２５は、一実施形態に係るユーザ端末の構成の一例を示す図である。ユーザ端末２０は、制御部２１０、送受信部２２０及び送受信アンテナ２３０を備えている。なお、制御部２１０、送受信部２２０及び送受信アンテナ２３０は、それぞれ１つ以上が備えられてもよい。 (user terminal)
FIG. 25 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 transmitting/receiving section 220, and a transmitting/receiving antenna 230. Note that one or more of each of the control unit 210, the transmitting/receiving unit 220, and the transmitting/receiving antenna 230 may be provided.
　なお、本例では、本実施の形態における特徴部分の機能ブロックを主に示しており、ユーザ端末２０は、無線通信に必要な他の機能ブロックも有すると想定されてもよい。以下で説明する各部の処理の一部は、省略されてもよい。 Note that this example mainly shows functional blocks that are characteristic 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 entire user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which will be explained based on common recognition in the technical field related to the present disclosure.
　制御部２１０は、信号の生成、マッピングなどを制御してもよい。制御部２１０は、送受信部２２０及び送受信アンテナ２３０を用いた送受信、測定などを制御してもよい。制御部２１０は、信号として送信するデータ、制御情報、系列などを生成し、送受信部２２０に転送してもよい。 The control unit 210 may control signal generation, mapping, etc. The control unit 210 may control transmission and reception using the transmitting/receiving unit 220 and the transmitting/receiving antenna 230, measurement, and the like. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as a signal, and may transfer the generated data to the transmitting/receiving unit 220.
　送受信部２２０は、ベースバンド部２２１、ＲＦ部２２２、測定部２２３を含んでもよい。ベースバンド部２２１は、送信処理部２２１１、受信処理部２２１２を含んでもよい。送受信部２２０は、本開示に係る技術分野での共通認識に基づいて説明されるトランスミッター／レシーバー、ＲＦ回路、ベースバンド回路、フィルタ、位相シフタ、測定回路、送受信回路などから構成することができる。 The transmitting/receiving section 220 may include a baseband section 221, an RF section 222, and a measuring 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 related to the present disclosure.
　送受信部２２０は、一体の送受信部として構成されてもよいし、送信部及び受信部から構成されてもよい。当該送信部は、送信処理部２２１１、ＲＦ部２２２から構成されてもよい。当該受信部は、受信処理部２２１２、ＲＦ部２２２、測定部２２３から構成されてもよい。 The transmitting/receiving section 220 may be configured as an integrated transmitting/receiving section, or may be configured from a transmitting section and a receiving section. The transmitting section may include a transmitting processing section 2211 and an RF section 222. The reception 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, such as an array antenna, as described based on common recognition in the technical field related to the present disclosure.
　送受信部２２０は、上述の下りリンクチャネル、同期信号、下りリンク参照信号などを受信してもよい。送受信部２２０は、上述の上りリンクチャネル、上りリンク参照信号などを送信してもよい。 The transmitter/receiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitter/receiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, and the like.
　送受信部２２０は、デジタルビームフォーミング（例えば、プリコーディング）、アナログビームフォーミング（例えば、位相回転）などを用いて、送信ビーム及び受信ビームの少なくとも一方を形成してもよい。 The transmitting/receiving unit 220 may form at least one of a transmitting beam and a receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.
　送受信部２２０（送信処理部２２１１）は、例えば制御部２１０から取得したデータ、制御情報などに対して、ＰＤＣＰレイヤの処理、ＲＬＣレイヤの処理（例えば、ＲＬＣ再送制御）、ＭＡＣレイヤの処理（例えば、ＨＡＲＱ再送制御）などを行い、送信するビット列を生成してもよい。 The transmission/reception unit 220 (transmission processing unit 2211) performs PDCP layer processing, RLC layer processing (e.g. RLC retransmission control), MAC layer processing (e.g. , HARQ retransmission control), etc., to generate a bit string to be transmitted.
　送受信部２２０（送信処理部２２１１）は、送信するビット列に対して、チャネル符号化（誤り訂正符号化を含んでもよい）、変調、マッピング、フィルタ処理、ＤＦＴ処理（必要に応じて）、ＩＦＦＴ処理、プリコーディング、デジタル－アナログ変換などの送信処理を行い、ベースバンド信号を出力してもよい。 The transmitting/receiving unit 220 (transmission processing unit 2211) performs channel encoding (which may include error correction encoding), modulation, mapping, filter processing, DFT processing (as necessary), and IFFT processing on the bit string to be transmitted. , precoding, digital-to-analog conversion, etc., and output a baseband signal.
　なお、ＤＦＴ処理を適用するか否かは、トランスフォームプリコーディングの設定に基づいてもよい。送受信部２２０（送信処理部２２１１）は、あるチャネル（例えば、ＰＵＳＣＨ）について、トランスフォームプリコーディングが有効（enabled）である場合、当該チャネルをＤＦＴ－ｓ－ＯＦＤＭ波形を用いて送信するために上記送信処理としてＤＦＴ処理を行ってもよいし、そうでない場合、上記送信処理としてＤＦＴ処理を行わなくてもよい。 Note that whether or not to apply DFT processing may be based on the settings of transform precoding. When transform precoding is enabled for a certain channel (for example, PUSCH), the transmitting/receiving unit 220 (transmission processing unit 2211) performs the above processing in order to transmit the channel using the DFT-s-OFDM waveform. DFT processing may be performed as the transmission processing, or if not, DFT processing may not be performed as the transmission processing.
　送受信部２２０（ＲＦ部２２２）は、ベースバンド信号に対して、無線周波数帯への変調、フィルタ処理、増幅などを行い、無線周波数帯の信号を、送受信アンテナ２３０を介して送信してもよい。 The transmitting/receiving unit 220 (RF unit 222) may perform modulation, filter processing, amplification, etc. on the baseband signal in a radio frequency band, and may transmit the signal in the radio frequency band via the transmitting/receiving antenna 230. .
　一方、送受信部２２０（ＲＦ部２２２）は、送受信アンテナ２３０によって受信された無線周波数帯の信号に対して、増幅、フィルタ処理、ベースバンド信号への復調などを行ってもよい。 On the other hand, the transmitting/receiving section 220 (RF section 222) may perform amplification, filter processing, demodulation into 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), filter processing, demapping, demodulation, and decoding (error correction) on the acquired baseband signal. (which may include decoding), MAC layer processing, RLC layer processing, and PDCP layer processing may be applied to obtain user data and the like.
　送受信部２２０（測定部２２３）は、受信した信号に関する測定を実施してもよい。例えば、測定部２２３は、受信した信号に基づいて、ＲＲＭ測定、ＣＳＩ測定などを行ってもよい。測定部２２３は、受信電力（例えば、ＲＳＲＰ）、受信品質（例えば、ＲＳＲＱ、ＳＩＮＲ、ＳＮＲ）、信号強度（例えば、ＲＳＳＩ）、伝搬路情報（例えば、ＣＳＩ）などについて測定してもよい。測定結果は、制御部２１０に出力されてもよい。 The transmitting/receiving unit 220 (measuring unit 223) may perform measurements regarding the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal. The measurement unit 223 may measure received power (for example, RSRP), reception quality (for example, RSRQ, SINR, SNR), signal strength (for example, RSSI), propagation path information (for example, CSI), and the like. The measurement results may be output to the control unit 210.
　なお、本開示におけるユーザ端末２０の送信部及び受信部は、送受信部２２０及び送受信アンテナ２３０の少なくとも１つによって構成されてもよい。 Note that the transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting/receiving unit 220 and the transmitting/receiving antenna 230.
　送受信部２２０は、メッセージ１の繰り返しの能力に関する第１能力情報と、メッセージ３の繰り返しの能力に関する第２能力情報と、を送信してもよい。制御部２１０は、前記第１能力情報及び前記第２能力情報に基づいて、前記メッセージ１の繰り返し及び前記メッセージ３の繰り返しを含む第１ランダムアクセス手順を行うか、前記メッセージ１の繰り返し及び前記メッセージ３の繰り返しの少なくとも１つを含まない第２ランダムアクセス手順を行うか、を決定してもよい。 The transmitting/receiving unit 220 may transmit first ability information regarding the ability to repeat message 1 and second ability information regarding the ability to repeat message 3. The control unit 210 performs a first random access procedure including repeating the message 1 and repeating the message 3 based on the first capability information and the second capability information, or performs a first random access procedure including repeating the message 1 and repeating the message 3. It may be determined whether to perform a second random access procedure that does not include at least one of the repetitions of 3.
　前記制御部２１０は、第１ランダムアクセスリソースを前記第１ランダムアクセス手順に用い、前記第１ランダムアクセスリソースと異なる第２ランダムアクセスリソースを前記第２ランダムアクセス手順に用いてもよい。 The control unit 210 may use a first random access resource for the first random access procedure, and may use a second random access resource different from the first random access resource for the second random access procedure.
　前記制御部２１０は、参照信号受信電力と閾値の比較に基づいて、前記第１ランダムアクセス手順を行うか、前記第２ランダムアクセス手順を行うか、を決定してもよい。 The control unit 210 may determine whether to perform the first random access procedure or the second random access procedure based on a comparison between the received reference signal power and a threshold value.
　前記制御部２１０は、前記メッセージ１の繰り返しの最大数と、参照信号受信電力に対する閾値と、の少なくとも１つに関する情報の受信を制御してもよい。 The control unit 210 may control reception of information regarding at least one of the maximum number of repetitions of the message 1 and a threshold for reference signal reception power.
　送受信部２２０は、メッセージ１の繰り返しを含む第１ランダムアクセス手順に関する情報を受信してもよい。制御部２１０は、前記情報に基づいて、第１ランダムアクセスリソースを、前記第１ランダムアクセス手順に用い、前記第１ランダムアクセスリソースと異なる第２ランダムアクセスリソースを、前記メッセージ１の繰り返しを含まない第２ランダムアクセス手順に用いてもよい。 The transmitting/receiving unit 220 may receive information regarding the first random access procedure including repeating message 1. Based on the information, the control unit 210 uses a first random access resource for the first random access procedure, and uses a second random access resource different from the first random access resource that does not include repetition of the message 1. It may also be used in the second random access procedure.
　前記情報は、前記第１ランダムアクセスリソースのためのプリアンブルインデックスの数と、前記第１ランダムアクセスリソースのための最初のプリアンブルインデックスと、の少なくとも１つを含んでもよい。 The information may include at least one of a number of preamble indexes for the first random access resource and a first preamble index for the first random access resource.
　前記制御部２１０は、第１ランダムアクセスチャネルオケージョンを、前記第１ランダムアクセス手順に用い、前記第１ランダムアクセスチャネルオケージョンと異なる第２ランダムアクセスチャネルオケージョンを、前記第２ランダムアクセス手順に用いてもよい。 The control unit 210 may use a first random access channel occasion for the first random access procedure, and use a second random access channel occasion different from the first random access channel occasion for the second random access procedure. good.
　前記制御部２１０は、マスクインデックスと、前記第２ランダムアクセス手順のための第２ランダムアクセスチャネルオケージョンと、の少なくとも１つに基づいて、前記第１ランダムアクセス手順のための第１ランダムアクセスチャネルオケージョンを決定してもよい。 The control unit 210 determines a first random access channel occasion for the first random access procedure based on at least one of a mask index and a second random access channel occasion for the second random access procedure. may be determined.
　送受信部２２０は、メッセージ１の複数の繰り返し及びメッセージ３の複数の繰り返しを含むランダムアクセス手順に関する情報を受信してもよい。制御部２１０は、前記情報に基づいて、前記メッセージ１の複数の繰り返しに用いられる１つ以上の第１ビームに基づいて、前記メッセージ３の複数の繰り返しに用いられる１つ以上の第２ビームを決定してもよい。 The transceiver unit 220 may receive information regarding a random access procedure including multiple repetitions of message 1 and multiple repetitions of message 3. Based on the information, the control unit 210 controls one or more second beams used for the plurality of repetitions of the message 3 based on the one or more first beams used for the plurality of repetitions of the message 1. You may decide.
　前記制御部２１０は、前記１つ以上の第１ビームの中から、前記１つ以上の第２ビームを決定してもよい。 The control unit 210 may determine the one or more second beams from among the one or more first beams.
　前記メッセージ１の複数の繰り返しに対して１つのランダムアクセスレスポンスが送信されてもよい。 One random access response may be sent for multiple repetitions of the message 1.
　前記メッセージ１の複数の繰り返しのそれぞれに対して１つのランダムアクセスレスポンスが送信されてもよい。 One random access response may be sent for each of multiple repetitions of said message 1.
　送受信部２２０は、メッセージ３の繰り返しの数に関する指示情報を受信してもよい。制御部２１０は、前記指示情報と、前記メッセージ３の繰り返しを含むランダムアクセス手順内のメッセージ１の繰り返しに関する情報と、に基づいて、前記メッセージ３の繰り返しの数を決定してもよい。 The transmitting/receiving unit 220 may receive instruction information regarding the number of repetitions of message 3. The control unit 210 may determine the number of repetitions of the message 3 based on the instruction information and information regarding the repetition of the message 1 in the random access procedure including the repetition of the message 3.
　前記情報は、前記メッセージ１の繰り返しの数に関してもよい。 The information may relate to the number of repetitions of the message 1.
　前記情報は、前記メッセージ１に対するランダムアクセスレスポンスの数に関してもよい。 The information may relate to the number of random access responses to the message 1.
　前記情報は、前記メッセージ１の繰り返しに用いられるビームの数に関してもよい。 The information may relate to the number of beams used for repeating the message 1.
（ハードウェア構成）
　なお、上記実施形態の説明に用いたブロック図は、機能単位のブロックを示している。これらの機能ブロック（構成部）は、ハードウェア及びソフトウェアの少なくとも一方の任意の組み合わせによって実現される。また、各機能ブロックの実現方法は特に限定されない。すなわち、各機能ブロックは、物理的又は論理的に結合した１つの装置を用いて実現されてもよいし、物理的又は論理的に分離した２つ以上の装置を直接的又は間接的に（例えば、有線、無線などを用いて）接続し、これら複数の装置を用いて実現されてもよい。機能ブロックは、上記１つの装置又は上記複数の装置にソフトウェアを組み合わせて実現されてもよい。 (Hardware configuration)
It should be noted that the block diagram used to explain the above embodiment shows blocks in functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically coupled device, or may be realized using two or more physically or logically separated devices directly or indirectly (e.g. , wired, wireless, etc.) and may be realized using a plurality of these devices. The functional block may be realized by combining software with the one device or the plurality of devices.
　ここで、機能には、判断、決定、判定、計算、算出、処理、導出、調査、探索、確認、受信、送信、出力、アクセス、解決、選択、選定、確立、比較、想定、期待、みなし、報知（broadcasting）、通知（notifying）、通信（communicating）、転送（forwarding）、構成（configuring）、再構成（reconfiguring）、割り当て（allocating、mapping）、割り振り（assigning）などがあるが、これらに限られない。例えば、送信を機能させる機能ブロック（構成部）は、送信部（transmitting　unit）、送信機（transmitter）などと呼称されてもよい。いずれも、上述したとおり、実現方法は特に限定されない。 Here, functions include judgment, decision, judgement, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, and consideration. , broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. Not limited. For example, a functional block (configuration unit) 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.
　例えば、本開示の一実施形態における基地局、ユーザ端末などは、本開示の無線通信方法の処理を行うコンピュータとして機能してもよい。図２６は、一実施形態に係る基地局及びユーザ端末のハードウェア構成の一例を示す図である。上述の基地局１０及びユーザ端末２０は、物理的には、プロセッサ１００１、メモリ１００２、ストレージ１００３、通信装置１００４、入力装置１００５、出力装置１００６、バス１００７などを含むコンピュータ装置として構成されてもよい。 For example, 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. 26 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal 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, etc. .
　なお、本開示において、装置、回路、デバイス、部（section）、ユニットなどの文言は、互いに読み替えることができる。基地局１０及びユーザ端末２０のハードウェア構成は、図に示した各装置を１つ又は複数含むように構成されてもよいし、一部の装置を含まずに構成されてもよい。 Note that in this disclosure, words such as apparatus, circuit, device, section, unit, etc. can be read interchangeably. 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 not to include some of the devices.
　例えば、プロセッサ１００１は１つだけ図示されているが、複数のプロセッサがあってもよい。また、処理は、１のプロセッサによって実行されてもよいし、処理が同時に、逐次に、又はその他の手法を用いて、２以上のプロセッサによって実行されてもよい。なお、プロセッサ１００１は、１以上のチップによって実装されてもよい。 For example, although only one processor 1001 is illustrated, there may be multiple processors. Also, the processing may be performed by one processor, or the processing may be performed by two or more processors simultaneously, sequentially, or using other techniques. Note that the processor 1001 may be implemented using one or more chips.
　基地局１０及びユーザ端末２０における各機能は、例えば、プロセッサ１００１、メモリ１００２などのハードウェア上に所定のソフトウェア（プログラム）を読み込ませることによって、プロセッサ１００１が演算を行い、通信装置１００４を介する通信を制御したり、メモリ１００２及びストレージ１００３におけるデータの読み出し及び書き込みの少なくとも一方を制御したりすることによって実現される。 Each function in the base station 10 and the user terminal 20 is performed by, for example, loading predetermined software (program) onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations and communicates via the communication device 1004. This is achieved by controlling at least one of reading and writing data in the memory 1002 and storage 1003.
　プロセッサ１００１は、例えば、オペレーティングシステムを動作させてコンピュータ全体を制御する。プロセッサ１００１は、周辺装置とのインターフェース、制御装置、演算装置、レジスタなどを含む中央処理装置（Central　Processing　Unit（ＣＰＵ））によって構成されてもよい。例えば、上述の制御部１１０（２１０）、送受信部１２０（２２０）などの少なくとも一部は、プロセッサ１００１によって実現されてもよい。 The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured by a central processing unit (CPU) that includes interfaces with peripheral devices, a control device, an arithmetic unit, registers, and the like. For example, at least a portion of the above-mentioned control unit 110 (210), transmitting/receiving unit 120 (220), etc. may be realized by the processor 1001.
　また、プロセッサ１００１は、プログラム（プログラムコード）、ソフトウェアモジュール、データなどを、ストレージ１００３及び通信装置１００４の少なくとも一方からメモリ１００２に読み出し、これらに従って各種の処理を実行する。プログラムとしては、上述の実施形態において説明した動作の少なくとも一部をコンピュータに実行させるプログラムが用いられる。例えば、制御部１１０（２１０）は、メモリ１００２に格納され、プロセッサ１００１において動作する制御プログラムによって実現されてもよく、他の機能ブロックについても同様に実現されてもよい。 Furthermore, 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 in accordance with these. As the program, a program that causes a computer to execute at least part of the operations described in the above embodiments is used. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and operated in the processor 1001, and other functional blocks may also be realized in the same way.
　メモリ１００２は、コンピュータ読み取り可能な記録媒体であり、例えば、Read　Only　Memory（ＲＯＭ）、Erasable　Programmable　ROM（ＥＰＲＯＭ）、Electrically　EPROM（ＥＥＰＲＯＭ）、Random　Access　Memory（ＲＡＭ）、その他の適切な記憶媒体の少なくとも１つによって構成されてもよい。メモリ１００２は、レジスタ、キャッシュ、メインメモリ（主記憶装置）などと呼ばれてもよい。メモリ１００２は、本開示の一実施形態に係る無線通信方法を実施するために実行可能なプログラム（プログラムコード）、ソフトウェアモジュールなどを保存することができる。 The memory 1002 is a computer-readable recording medium, and includes at least one of Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), and other suitable storage media. It may be composed of one. Memory 1002 may be called a register, cache, main memory, or the like. The memory 1002 can store executable programs (program codes), software modules, and the like to implement a wireless communication method according to an embodiment of the present disclosure.
　ストレージ１００３は、コンピュータ読み取り可能な記録媒体であり、例えば、フレキシブルディスク、フロッピー（登録商標）ディスク、光磁気ディスク（例えば、コンパクトディスク（Compact　Disc　ROM（ＣＤ－ＲＯＭ）など）、デジタル多用途ディスク、Ｂｌｕ－ｒａｙ（登録商標）ディスク）、リムーバブルディスク、ハードディスクドライブ、スマートカード、フラッシュメモリデバイス（例えば、カード、スティック、キードライブ）、磁気ストライプ、データベース、サーバ、その他の適切な記憶媒体の少なくとも１つによって構成されてもよい。ストレージ１００３は、補助記憶装置と呼ばれてもよい。 The storage 1003 is a computer-readable recording medium, such as a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disk (CD-ROM), etc.), a digital versatile disk, removable disk, hard disk drive, smart card, flash memory device (e.g., card, stick, key drive), magnetic stripe, database, server, or other suitable storage medium. It may be configured by Storage 1003 may also be called an auxiliary storage device.
　通信装置１００４は、有線ネットワーク及び無線ネットワークの少なくとも一方を介してコンピュータ間の通信を行うためのハードウェア（送受信デバイス）であり、例えばネットワークデバイス、ネットワークコントローラ、ネットワークカード、通信モジュールなどともいう。通信装置１００４は、例えば周波数分割複信（Frequency　Division　Duplex（ＦＤＤ））及び時分割複信（Time　Division　Duplex（ＴＤＤ））の少なくとも一方を実現するために、高周波スイッチ、デュプレクサ、フィルタ、周波数シンセサイザなどを含んで構成されてもよい。例えば、上述の送受信部１２０（２２０）、送受信アンテナ１３０（２３０）などは、通信装置１００４によって実現されてもよい。送受信部１２０（２２０）は、送信部１２０ａ（２２０ａ）と受信部１２０ｂ（２２０ｂ）とで、物理的に又は論理的に分離された実装がなされてもよい。 The communication device 1004 is hardware (transmission/reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc., for example. The communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). It may be configured to include. For example, the above-described transmitting/receiving unit 120 (220), transmitting/receiving antenna 130 (230), etc. 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).
　入力装置１００５は、外部からの入力を受け付ける入力デバイス（例えば、キーボード、マウス、マイクロフォン、スイッチ、ボタン、センサなど）である。出力装置１００６は、外部への出力を実施する出力デバイス（例えば、ディスプレイ、スピーカー、Light　Emitting　Diode（ＬＥＤ）ランプなど）である。なお、入力装置１００５及び出力装置１００６は、一体となった構成（例えば、タッチパネル）であってもよい。 The input device 1005 is an input device (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts 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 performs output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).
　また、プロセッサ１００１、メモリ１００２などの各装置は、情報を通信するためのバス１００７によって接続される。バス１００７は、単一のバスを用いて構成されてもよいし、装置間ごとに異なるバスを用いて構成されてもよい。 Further, 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 for each device.
　また、基地局１０及びユーザ端末２０は、マイクロプロセッサ、デジタル信号プロセッサ（Digital　Signal　Processor（ＤＳＰ））、Application　Specific　Integrated　Circuit（ＡＳＩＣ）、Programmable　Logic　Device（ＰＬＤ）、Field　Programmable　Gate　Array（ＦＰＧＡ）などのハードウェアを含んで構成されてもよく、当該ハードウェアを用いて各機能ブロックの一部又は全てが実現されてもよい。例えば、プロセッサ１００１は、これらのハードウェアの少なくとも１つを用いて実装されてもよい。 The base station 10 and user terminal 20 also 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 to include 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 hardwares.
（変形例）
　なお、本開示において説明した用語及び本開示の理解に必要な用語については、同一の又は類似する意味を有する用語と置き換えてもよい。例えば、チャネル、シンボル及び信号（シグナル又はシグナリング）は、互いに読み替えられてもよい。また、信号はメッセージであってもよい。参照信号（reference　signal）は、ＲＳと略称することもでき、適用される標準によってパイロット（Pilot）、パイロット信号などと呼ばれてもよい。また、コンポーネントキャリア（Component　Carrier（ＣＣ））は、セル、周波数キャリア、キャリア周波数などと呼ばれてもよい。 (Modified example)
Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol and signal may be interchanged. Also, the signal may be a message. The reference signal may also be abbreviated as RS, and may be called a pilot, pilot signal, etc. depending on the applicable standard. Further, a component carrier (CC) may be called a cell, a frequency carrier, a carrier frequency, or the like.
　無線フレームは、時間領域において１つ又は複数の期間（フレーム）によって構成されてもよい。無線フレームを構成する当該１つ又は複数の各期間（フレーム）は、サブフレームと呼ばれてもよい。さらに、サブフレームは、時間領域において１つ又は複数のスロットによって構成されてもよい。サブフレームは、ニューメロロジー（numerology）に依存しない固定の時間長（例えば、１ｍｓ）であってもよい。 A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (eg, 1 ms) that does not depend on numerology.
　ここで、ニューメロロジーは、ある信号又はチャネルの送信及び受信の少なくとも一方に適用される通信パラメータであってもよい。ニューメロロジーは、例えば、サブキャリア間隔（SubCarrier　Spacing（ＳＣＳ））、帯域幅、シンボル長、サイクリックプレフィックス長、送信時間間隔（Transmission　Time　Interval（ＴＴＩ））、ＴＴＩあたりのシンボル数、無線フレーム構成、送受信機が周波数領域において行う特定のフィルタリング処理、送受信機が時間領域において行う特定のウィンドウイング処理などの少なくとも１つを示してもよい。 Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. Numerology includes, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, and radio frame configuration. , a specific filtering process performed by the transceiver in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc.
　スロットは、時間領域において１つ又は複数のシンボル（Orthogonal　Frequency　Division　Multiplexing（ＯＦＤＭ）シンボル、Single　Carrier　Frequency　Division　Multiple　Access（ＳＣ－ＦＤＭＡ）シンボルなど）によって構成されてもよい。また、スロットは、ニューメロロジーに基づく時間単位であってもよい。 A slot may be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) in the time domain. Further, a slot may be a time unit based on numerology.
　スロットは、複数のミニスロットを含んでもよい。各ミニスロットは、時間領域において１つ又は複数のシンボルによって構成されてもよい。また、ミニスロットは、サブスロットと呼ばれてもよい。ミニスロットは、スロットよりも少ない数のシンボルによって構成されてもよい。ミニスロットより大きい時間単位で送信されるＰＤＳＣＨ（又はＰＵＳＣＨ）は、ＰＤＳＣＨ（ＰＵＳＣＨ）マッピングタイプＡと呼ばれてもよい。ミニスロットを用いて送信されるＰＤＳＣＨ（又はＰＵＳＣＨ）は、ＰＤＳＣＨ（ＰＵＳＣＨ）マッピングタイプＢと呼ばれてもよい。 A slot may include multiple mini-slots. Each minislot may be made up of one or more symbols in the time domain. Furthermore, a mini-slot may also be called a sub-slot. A minislot may be made up of fewer symbols than a slot. PDSCH (or PUSCH) transmitted in time units larger than minislots 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. Other names may be used for the radio frame, subframe, slot, minislot, and symbol. Note that time units such as frames, subframes, slots, minislots, and symbols in the present disclosure may be read interchangeably.
　例えば、１サブフレームはＴＴＩと呼ばれてもよいし、複数の連続したサブフレームがＴＴＩと呼ばれてよいし、１スロット又は１ミニスロットがＴＴＩと呼ばれてもよい。つまり、サブフレーム及びＴＴＩの少なくとも一方は、既存のＬＴＥにおけるサブフレーム（１ｍｓ）であってもよいし、１ｍｓより短い期間（例えば、１－１３シンボル）であってもよいし、１ｍｓより長い期間であってもよい。なお、ＴＴＩを表す単位は、サブフレームではなくスロット、ミニスロットなどと呼ばれてもよい。 For example, one subframe may be called a TTI, a plurality of consecutive subframes may be called a TTI, and one slot or one minislot may be called a TTI. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (for example, 1-13 symbols), or a period longer than 1ms. It may be. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.
　ここで、ＴＴＩは、例えば、無線通信におけるスケジューリングの最小時間単位のことをいう。例えば、ＬＴＥシステムでは、基地局が各ユーザ端末に対して、無線リソース（各ユーザ端末において使用することが可能な周波数帯域幅、送信電力など）を、ＴＴＩ単位で割り当てるスケジューリングを行う。なお、ＴＴＩの定義はこれに限られない。 Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, 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. Note that the definition of TTI is not limited to this.
　ＴＴＩは、チャネル符号化されたデータパケット（トランスポートブロック）、コードブロック、コードワードなどの送信時間単位であってもよいし、スケジューリング、リンクアダプテーションなどの処理単位となってもよい。なお、ＴＴＩが与えられたとき、実際にトランスポートブロック、コードブロック、コードワードなどがマッピングされる時間区間（例えば、シンボル数）は、当該ＴＴＩよりも短くてもよい。 The TTI may be a transmission time unit of a channel-coded data packet (transport block), a code block, a codeword, etc., or may be a processing unit of scheduling, link adaptation, etc. Note that when a TTI is given, the time interval (for example, the number of symbols) to which transport blocks, code blocks, code words, etc. are actually mapped may be shorter than the TTI.
　なお、１スロット又は１ミニスロットがＴＴＩと呼ばれる場合、１以上のＴＴＩ（すなわち、１以上のスロット又は１以上のミニスロット）が、スケジューリングの最小時間単位となってもよい。また、当該スケジューリングの最小時間単位を構成するスロット数（ミニスロット数）は制御されてもよい。 Note that when one slot or one minislot is called a TTI, one or more TTIs (that is, one or more slots or one or more minislots) may be the minimum time unit for scheduling. Further, the number of slots (minislot number) that constitutes the minimum time unit of the scheduling may be controlled.
　１ｍｓの時間長を有するＴＴＩは、通常ＴＴＩ（３ＧＰＰ　Ｒｅｌ．８－１２におけるＴＴＩ）、ノーマルＴＴＩ、ロングＴＴＩ、通常サブフレーム、ノーマルサブフレーム、ロングサブフレーム、スロットなどと呼ばれてもよい。通常ＴＴＩより短いＴＴＩは、短縮ＴＴＩ、ショートＴＴＩ、部分ＴＴＩ（partial又はfractional　TTI）、短縮サブフレーム、ショートサブフレーム、ミニスロット、サブスロット、スロットなどと呼ばれてもよい。 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, etc. A TTI that is shorter than the normal TTI may be referred to as an abbreviated TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
　なお、ロングＴＴＩ（例えば、通常ＴＴＩ、サブフレームなど）は、１ｍｓを超える時間長を有するＴＴＩで読み替えてもよいし、ショートＴＴＩ（例えば、短縮ＴＴＩなど）は、ロングＴＴＩのＴＴＩ長未満かつ１ｍｓ以上のＴＴＩ長を有するＴＴＩで読み替えてもよい。 Note that long TTI (for example, normal TTI, subframe, etc.) may be read as TTI with a time length exceeding 1 ms, and short TTI (for example, short TTI, etc.) It may also be read as a TTI having the above TTI length.
　リソースブロック（Resource　Block（ＲＢ））は、時間領域及び周波数領域のリソース割当単位であり、周波数領域において、１つ又は複数個の連続した副搬送波（サブキャリア（subcarrier））を含んでもよい。ＲＢに含まれるサブキャリアの数は、ニューメロロジーに関わらず同じであってもよく、例えば１２であってもよい。ＲＢに含まれるサブキャリアの数は、ニューメロロジーに基づいて決定されてもよい。 A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more continuous subcarriers (subcarriers) in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the numerology, and may be 12, for example. The number of subcarriers included in an RB may be determined based on numerology.
　また、ＲＢは、時間領域において、１つ又は複数個のシンボルを含んでもよく、１スロット、１ミニスロット、１サブフレーム又は１ＴＴＩの長さであってもよい。１ＴＴＩ、１サブフレームなどは、それぞれ１つ又は複数のリソースブロックによって構成されてもよい。 Additionally, an RB may include one or more symbols in the time domain, and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.
　なお、１つ又は複数のＲＢは、物理リソースブロック（Physical　RB（ＰＲＢ））、サブキャリアグループ（Sub-Carrier　Group（ＳＣＧ））、リソースエレメントグループ（Resource　Element　Group（ＲＥＧ））、ＰＲＢ／ＲＢのグループ／セット／ペア、などと呼ばれてもよい。 Note that one or more RBs include a physical resource block (Physical RB (PRB)), a sub-carrier group (SCG), a resource element group (REG), and a PRB/RB. It may also be called a group/set/pair.
　また、リソースブロックは、１つ又は複数のリソースエレメント（Resource　Element（ＲＥ））によって構成されてもよい。例えば、１ＲＥは、１サブキャリア及び１シンボルの無線リソース領域であってもよい。 Additionally, a resource block may be configured by one or more resource elements (REs). For example, 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.
　帯域幅部分（Bandwidth　Part（ＢＷＰ））（部分帯域幅などと呼ばれてもよい）は、あるキャリアにおいて、あるニューメロロジー用の連続する共通ＲＢ（common　resource　blocks）のサブセットのことを表してもよい。ここで、共通ＲＢは、当該キャリアの共通参照ポイントを基準としたＲＢのインデックスによって特定されてもよい。ＰＲＢは、あるＢＷＰで定義され、当該ＢＷＰ内で番号付けされてもよい。 Bandwidth Part (BWP) (also called partial bandwidth, etc.) refers to a subset of consecutive common resource blocks (RB) for a certain numerology in a certain carrier. Good too. Here, the common RB may be specified by an RB index based on a 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). One or more BWPs may be configured within one carrier for a UE.
　設定されたＢＷＰの少なくとも１つがアクティブであってもよく、ＵＥは、アクティブなＢＷＰの外で所定の信号／チャネルを送受信することを想定しなくてもよい。なお、本開示における「セル」、「キャリア」などは、「ＢＷＰ」で読み替えられてもよい。 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 of the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be replaced with "BWP".
　なお、上述した無線フレーム、サブフレーム、スロット、ミニスロット及びシンボルなどの構造は例示に過ぎない。例えば、無線フレームに含まれるサブフレームの数、サブフレーム又は無線フレームあたりのスロットの数、スロット内に含まれるミニスロットの数、スロット又はミニスロットに含まれるシンボル及びＲＢの数、ＲＢに含まれるサブキャリアの数、並びにＴＴＩ内のシンボル数、シンボル長、サイクリックプレフィックス（Cyclic　Prefix（ＣＰ））長などの構成は、様々に変更することができる。 Note that the structures of the radio frame, subframe, slot, minislot, symbol, etc. described above are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of symbols included in an RB, The number of subcarriers, the number of symbols within a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.
　また、本開示において説明した情報、パラメータなどは、絶対値を用いて表されてもよいし、所定の値からの相対値を用いて表されてもよいし、対応する別の情報を用いて表されてもよい。例えば、無線リソースは、所定のインデックスによって指示されてもよい。 In addition, the information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values from a predetermined value, or using other corresponding information. may be expressed. For example, radio resources may be indicated by a predetermined index.
　本開示においてパラメータなどに使用する名称は、いかなる点においても限定的な名称ではない。さらに、これらのパラメータを使用する数式などは、本開示において明示的に開示したものと異なってもよい。様々なチャネル（ＰＵＣＣＨ、ＰＤＣＣＨなど）及び情報要素は、あらゆる好適な名称によって識別できるので、これらの様々なチャネル及び情報要素に割り当てている様々な名称は、いかなる点においても限定的な名称ではない。 The names used for parameters and the like in this disclosure are not limiting in any respect. Furthermore, the mathematical formulas etc. using these parameters may differ from those explicitly disclosed in this disclosure. Since the various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable designation, the various names assigned to these various channels and information elements are not in any way exclusive designations. .
　本開示において説明した情報、信号などは、様々な異なる技術のいずれかを使用して表されてもよい。例えば、上記の説明全体に渡って言及され得るデータ、命令、コマンド、情報、信号、ビット、シンボル、チップなどは、電圧、電流、電磁波、磁界若しくは磁性粒子、光場若しくは光子、又はこれらの任意の組み合わせによって表されてもよい。 The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be referred to throughout the above description, may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may also be represented by a combination of
　また、情報、信号などは、上位レイヤから下位レイヤ及び下位レイヤから上位レイヤの少なくとも一方へ出力され得る。情報、信号などは、複数のネットワークノードを介して入出力されてもよい。 Additionally, information, signals, etc. may be output from the upper layer to the lower layer and from the lower layer to at least one of the upper layer. Information, signals, etc. may be input and output via 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. Information, signals, etc. that are input and output can be overwritten, updated, or added. The output information, signals, etc. may be deleted. The input information, signals, etc. may be transmitted to other devices.
　情報の通知は、本開示において説明した態様／実施形態に限られず、他の方法を用いて行われてもよい。例えば、本開示における情報の通知は、物理レイヤシグナリング（例えば、下り制御情報（Downlink　Control　Information（ＤＣＩ））、上り制御情報（Uplink　Control　Information（ＵＣＩ）））、上位レイヤシグナリング（例えば、Radio　Resource　Control（ＲＲＣ）シグナリング、ブロードキャスト情報（マスタ情報ブロック（Master　Information　Block（ＭＩＢ））、システム情報ブロック（System　Information　Block（ＳＩＢ））など）、Medium　Access　Control（ＭＡＣ）シグナリング）、その他の信号又はこれらの組み合わせによって実施されてもよい。 Notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods. For example, the notification of information in this disclosure may be physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals, or a combination thereof It may be carried out by
　なお、物理レイヤシグナリングは、Layer　1／Layer　2（Ｌ１／Ｌ２）制御情報（Ｌ１／Ｌ２制御信号）、Ｌ１制御情報（Ｌ１制御信号）などと呼ばれてもよい。また、ＲＲＣシグナリングは、ＲＲＣメッセージと呼ばれてもよく、例えば、ＲＲＣ接続セットアップ（RRC　Connection　Setup）メッセージ、ＲＲＣ接続再構成（RRC　Connection　Reconfiguration）メッセージなどであってもよい。また、ＭＡＣシグナリングは、例えば、ＭＡＣ制御要素（ＭＡＣ　Control　Element（ＣＥ））を用いて通知されてもよい。 Note that 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), etc. Further, RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like. Further, MAC signaling may be notified using, for example, a MAC Control Element (CE).
　また、所定の情報の通知（例えば、「Ｘであること」の通知）は、明示的な通知に限られず、暗示的に（例えば、当該所定の情報の通知を行わないことによって又は別の情報の通知によって）行われてもよい。 Further, notification of prescribed information (for example, notification of "X") is not limited to explicit notification, but may be made implicitly (for example, by not notifying the prescribed information or by providing other information) (by notification).
　判定は、１ビットで表される値（０か１か）によって行われてもよいし、真（true）又は偽（false）で表される真偽値（boolean）によって行われてもよいし、数値の比較（例えば、所定の値との比較）によって行われてもよい。 The determination may be made by a value expressed by 1 bit (0 or 1), or by a boolean value expressed by true or false. , may be performed by numerical comparison (for example, comparison with a predetermined value).
　ソフトウェアは、ソフトウェア、ファームウェア、ミドルウェア、マイクロコード、ハードウェア記述言語と呼ばれるか、他の名称で呼ばれるかを問わず、命令、命令セット、コード、コードセグメント、プログラムコード、プログラム、サブプログラム、ソフトウェアモジュール、アプリケーション、ソフトウェアアプリケーション、ソフトウェアパッケージ、ルーチン、サブルーチン、オブジェクト、実行可能ファイル、実行スレッド、手順、機能などを意味するよう広く解釈されるべきである。 Software includes instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, whether referred to as software, firmware, middleware, microcode, hardware description language, or by any other name. , should be broadly construed to mean an application, software application, software package, routine, subroutine, object, executable, thread of execution, procedure, function, etc.
　また、ソフトウェア、命令、情報などは、伝送媒体を介して送受信されてもよい。例えば、ソフトウェアが、有線技術（同軸ケーブル、光ファイバケーブル、ツイストペア、デジタル加入者回線（Digital　Subscriber　Line（ＤＳＬ））など）及び無線技術（赤外線、マイクロ波など）の少なくとも一方を使用してウェブサイト、サーバ、又は他のリモートソースから送信される場合、これらの有線技術及び無線技術の少なくとも一方は、伝送媒体の定義内に含まれる。 Additionally, software, instructions, information, etc. may be sent and received via a transmission medium. For example, if the software uses wired technology (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and/or wireless technology (such as infrared, microwave, etc.) to , a server, or other remote source, these wired and/or wireless technologies are included within the definition of a transmission medium.
　本開示において使用する「システム」及び「ネットワーク」という用語は、互換的に使用され得る。「ネットワーク」は、ネットワークに含まれる装置（例えば、基地局）のことを意味してもよい。 The terms "system" and "network" used in this disclosure may be used interchangeably. "Network" may refer to devices (eg, base stations) included in the network.
　本開示において、「プリコーディング」、「プリコーダ」、「ウェイト（プリコーディングウェイト）」、「擬似コロケーション（Quasi-Co-Location（ＱＣＬ））」、「Transmission　Configuration　Indication　state（ＴＣＩ状態）」、「空間関係（spatial　relation）」、「空間ドメインフィルタ（spatial　domain　filter）」、「送信電力」、「位相回転」、「アンテナポート」、「アンテナポートグル－プ」、「レイヤ」、「レイヤ数」、「ランク」、「リソース」、「リソースセット」、「リソースグループ」、「ビーム」、「ビーム幅」、「ビーム角度」、「アンテナ」、「アンテナ素子」、「パネル」などの用語は、互換的に使用され得る。 In this disclosure, "precoding", "precoder", "weight (precoding weight)", "quasi-co-location (QCL)", "Transmission Configuration Indication state (TCI state)", "space "spatial relation", "spatial 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", and "panel" are interchangeable. can be used.
　本開示においては、「基地局（Base　Station（ＢＳ））」、「無線基地局」、「固定局（fixed　station）」、「ＮｏｄｅＢ」、「ｅＮＢ（ｅＮｏｄｅＢ）」、「ｇＮＢ（ｇＮｏｄｅＢ）」、「アクセスポイント（access　point）」、「送信ポイント（Transmission　Point（ＴＰ））」、「受信ポイント（Reception　Point（ＲＰ））」、「送受信ポイント（Transmission/Reception　Point（ＴＲＰ））」、「パネル」、「セル」、「セクタ」、「セルグループ」、「キャリア」、「コンポーネントキャリア」などの用語は、互換的に使用され得る。基地局は、マクロセル、スモールセル、フェムトセル、ピコセルなどの用語で呼ばれる場合もある。 In the present disclosure, "Base Station (BS)", "Wireless base station", "Fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission/Reception Point (TRP)", "Panel" , "cell," "sector," "cell group," "carrier," "component carrier," and the like may be used interchangeably. A base station is sometimes referred to by terms such as macrocell, small cell, femtocell, and picocell.
　基地局は、１つ又は複数（例えば、３つ）のセルを収容することができる。基地局が複数のセルを収容する場合、基地局のカバレッジエリア全体は複数のより小さいエリアに区分でき、各々のより小さいエリアは、基地局サブシステム（例えば、屋内用の小型基地局（Remote　Radio　Head（ＲＲＨ）））によって通信サービスを提供することもできる。「セル」又は「セクタ」という用語は、このカバレッジにおいて通信サービスを行う基地局及び基地局サブシステムの少なくとも一方のカバレッジエリアの一部又は全体を指す。 A base station can accommodate one or more (eg, three) cells. If a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area is connected to a base station subsystem (e.g., an indoor small base station (Remote Radio Communication services can also be provided by the Head (RRH)). The term "cell" or "sector" refers to part or all of the coverage area of a base station and/or base station subsystem that provides communication services in this coverage.
　本開示において、基地局が端末に情報を送信することは、当該基地局が当該端末に対して、当該情報に基づく制御／動作を指示することと、互いに読み替えられてもよい。 In the present disclosure, a base station transmitting information to a terminal may be interchanged with the base station instructing the terminal to control/operate based on the information.
　本開示においては、「移動局（Mobile　Station（ＭＳ））」、「ユーザ端末（user　terminal）」、「ユーザ装置（User　Equipment（ＵＥ））」、「端末」などの用語は、互換的に使用され得る。 In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" are used interchangeably. can be done.
　移動局は、加入者局、モバイルユニット、加入者ユニット、ワイヤレスユニット、リモートユニット、モバイルデバイス、ワイヤレスデバイス、ワイヤレス通信デバイス、リモートデバイス、モバイル加入者局、アクセス端末、モバイル端末、ワイヤレス端末、リモート端末、ハンドセット、ユーザエージェント、モバイルクライアント、クライアント又はいくつかの他の適切な用語で呼ばれる場合もある。 A mobile station is a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal. , handset, user agent, mobile client, client, or some other suitable terminology.
　基地局及び移動局の少なくとも一方は、送信装置、受信装置、無線通信装置などと呼ばれてもよい。なお、基地局及び移動局の少なくとも一方は、移動体（moving　object）に搭載されたデバイス、移動体自体などであってもよい。 At least one of a base station and a mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, or the like.
　当該移動体は、移動可能な物体をいい、移動速度は任意であり、移動体が停止している場合も当然含む。当該移動体は、例えば、車両、輸送車両、自動車、自動二輪車、自転車、コネクテッドカー、ショベルカー、ブルドーザー、ホイールローダー、ダンプトラック、フォークリフト、列車、バス、リヤカー、人力車、船舶（ship　and　other　watercraft）、飛行機、ロケット、人工衛星、ドローン、マルチコプター、クアッドコプター、気球及びこれらに搭載される物を含み、またこれらに限られない。また、当該移動体は、運行指令に基づいて自律走行する移動体であってもよい。 The moving body refers to a movable object, and the moving speed is arbitrary, and naturally includes cases where the moving body is stopped. The mobile objects include, for example, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, carts, rickshaws, and ships (ships and other watercraft). , including, but not limited to, airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, balloons, and items mounted thereon. Furthermore, the mobile object may be a mobile object that autonomously travels based on a travel command.
　当該移動体は、乗り物（例えば、車、飛行機など）であってもよいし、無人で動く移動体（例えば、ドローン、自動運転車など）であってもよいし、ロボット（有人型又は無人型）であってもよい。なお、基地局及び移動局の少なくとも一方は、必ずしも通信動作時に移動しない装置も含む。例えば、基地局及び移動局の少なくとも一方は、センサなどのInternet　of　Things（ＩｏＴ）機器であってもよい。 The moving object may be a vehicle (for example, a car, an airplane, etc.), an unmanned moving object (for example, a drone, a self-driving car, etc.), or a robot (manned or unmanned). ). Note that at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.
　図２７は、一実施形態に係る車両の一例を示す図である。車両４０は、駆動部４１、操舵部４２、アクセルペダル４３、ブレーキペダル４４、シフトレバー４５、左右の前輪４６、左右の後輪４７、車軸４８、電子制御部４９、各種センサ（電流センサ５０、回転数センサ５１、空気圧センサ５２、車速センサ５３、加速度センサ５４、アクセルペダルセンサ５５、ブレーキペダルセンサ５６、シフトレバーセンサ５７、及び物体検知センサ５８を含む）、情報サービス部５９と通信モジュール６０を備える。 FIG. 27 is a diagram illustrating an example of a vehicle according to an embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (current sensor 50, (including a rotation speed sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service section 59, and a communication module 60. Be prepared.
　駆動部４１は、例えば、エンジン、モータ、エンジンとモータのハイブリッドの少なくとも１つで構成される。操舵部４２は、少なくともステアリングホイール（ハンドルとも呼ぶ）を含み、ユーザによって操作されるステアリングホイールの操作に基づいて前輪４６及び後輪４７の少なくとも一方を操舵するように構成される。 The drive 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.
　電子制御部４９は、マイクロプロセッサ６１、メモリ（ＲＯＭ、ＲＡＭ）６２、通信ポート（例えば、入出力（Input/Output（ＩＯ））ポート）６３で構成される。電子制御部４９には、車両に備えられた各種センサ５０－５８からの信号が入力される。電子制御部４９は、Electronic　Control　Unit（ＥＣＵ）と呼ばれてもよい。 The electronic control unit 49 includes a microprocessor 61, a memory (ROM, RAM) 62, and a communication port (for example, an input/output (IO) port) 63. Signals from various sensors 50-58 provided in the vehicle are input to the electronic control unit 49. The electronic control section 49 may be called an electronic control unit (ECU).
　各種センサ５０－５８からの信号としては、モータの電流をセンシングする電流センサ５０からの電流信号、回転数センサ５１によって取得された前輪４６／後輪４７の回転数信号、空気圧センサ５２によって取得された前輪４６／後輪４７の空気圧信号、車速センサ５３によって取得された車速信号、加速度センサ５４によって取得された加速度信号、アクセルペダルセンサ５５によって取得されたアクセルペダル４３の踏み込み量信号、ブレーキペダルセンサ５６によって取得されたブレーキペダル４４の踏み込み量信号、シフトレバーセンサ５７によって取得されたシフトレバー４５の操作信号、物体検知センサ５８によって取得された障害物、車両、歩行者などを検出するための検出信号などがある。 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 wheel 46/rear wheel 47 obtained by the rotation speed sensor 51, and a signal obtained by the air pressure sensor 52. air pressure signals of the front wheels 46/rear wheels 47, a vehicle speed signal acquired by the vehicle speed sensor 53, an acceleration signal acquired by the acceleration sensor 54, a depression amount signal of the accelerator pedal 43 acquired by the accelerator pedal sensor 55, and a brake pedal sensor. 56, a shift lever 45 operation signal obtained by the shift lever sensor 57, and an object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc. There are signals etc.
　情報サービス部５９は、カーナビゲーションシステム、オーディオシステム、スピーカー、ディスプレイ、テレビ、ラジオ、といった、運転情報、交通情報、エンターテイメント情報などの各種情報を提供（出力）するための各種機器と、これらの機器を制御する１つ以上のＥＣＵとから構成される。情報サービス部５９は、外部装置から通信モジュール６０などを介して取得した情報を利用して、車両４０の乗員に各種情報／サービス（例えば、マルチメディア情報／マルチメディアサービス）を提供する。 The information service department 59 includes various devices such as car navigation systems, audio systems, speakers, displays, televisions, and radios that provide (output) various information such as driving information, traffic information, and entertainment information, and these devices. It consists of one or more ECUs that control the 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.
　情報サービス部５９は、外部からの入力を受け付ける入力デバイス（例えば、キーボード、マウス、マイクロフォン、スイッチ、ボタン、センサ、タッチパネルなど）を含んでもよいし、外部への出力を実施する出力デバイス（例えば、ディスプレイ、スピーカー、ＬＥＤランプ、タッチパネルなど）を含んでもよい。 The information service unit 59 may include an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accepts input from the outside, and an output device that performs output to the outside (for example, display, speaker, LED lamp, touch panel, etc.).
　運転支援システム部６４は、ミリ波レーダ、Light　Detection　and　Ranging（ＬｉＤＡＲ）、カメラ、測位ロケータ（例えば、Global　Navigation　Satellite　System（ＧＮＳＳ）など）、地図情報（例えば、高精細（High　Definition（ＨＤ））マップ、自動運転車（Autonomous　Vehicle（ＡＶ））マップなど）、ジャイロシステム（例えば、慣性計測装置（Inertial　Measurement　Unit（ＩＭＵ））、慣性航法装置（Inertial　Navigation　System（ＩＮＳ））など）、人工知能（Artificial　Intelligence（ＡＩ））チップ、ＡＩプロセッサといった、事故を未然に防止したりドライバの運転負荷を軽減したりするための機能を提供するための各種機器と、これらの機器を制御する１つ以上のＥＣＵとから構成される。また、運転支援システム部６４は、通信モジュール６０を介して各種情報を送受信し、運転支援機能又は自動運転機能を実現する。 The driving support system unit 64 includes millimeter wave radar, Light Detection and Ranging (LiDAR), a camera, a positioning locator (for example, Global Navigation Satellite System (GNSS), etc.), and map information (for example, High Definition (HD)). maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., inertial measurement units (IMUs), 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 burden, as well as one or more devices that control these devices. It consists of an ECU. Further, the driving support system section 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. For example, the communication module 60 communicates via the communication port 63 with 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, which are included in the vehicle 40. 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 external devices. For example, various information is transmitted and received with an external device via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10, user terminal 20, etc. described above. Further, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (it 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 that are 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. At least one of the information based on the information may be transmitted to an external device via wireless communication. The electronic control unit 49, various sensors 50-58, information service unit 59, etc. may be called an input unit that receives input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above input.
　通信モジュール６０は、外部装置から送信されてきた種々の情報（交通情報、信号情報、車間情報など）を受信し、車両に備えられた情報サービス部５９へ表示する。情報サービス部５９は、情報を出力する（例えば、通信モジュール６０によって受信されるＰＤＳＣＨ（又は当該ＰＤＳＣＨから復号されるデータ／情報）に基づいてディスプレイ、スピーカーなどの機器に情報を出力する）出力部と呼ばれてもよい。 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 section 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 a display and a speaker based on the PDSCH (or data/information decoded from the PDSCH) received by the communication module 60). may be called.
　また、通信モジュール６０は、外部装置から受信した種々の情報をマイクロプロセッサ６１によって利用可能なメモリ６２へ記憶する。メモリ６２に記憶された情報に基づいて、マイクロプロセッサ６１が車両４０に備えられた駆動部４１、操舵部４２、アクセルペダル４３、ブレーキペダル４４、シフトレバー４５、左右の前輪４６、左右の後輪４７、車軸４８、各種センサ５０－５８などの制御を行ってもよい。 The communication module 60 also stores various information received from external devices into 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, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, and left and right rear wheels provided in the vehicle 40. 47, axle 48, various sensors 50-58, etc. may be controlled.
　また、本開示における基地局は、ユーザ端末で読み替えてもよい。例えば、基地局及びユーザ端末間の通信を、複数のユーザ端末間の通信（例えば、Device-to-Device（Ｄ２Ｄ）、Vehicle-to-Everything（Ｖ２Ｘ）などと呼ばれてもよい）に置き換えた構成について、本開示の各態様／実施形態を適用してもよい。この場合、上述の基地局１０が有する機能をユーザ端末２０が有する構成としてもよい。また、「上りリンク（uplink）」、「下りリンク（downlink）」などの文言は、端末間通信に対応する文言（例えば、「サイドリンク（sidelink）」）で読み替えられてもよい。例えば、上りリンクチャネル、下りリンクチャネルなどは、サイドリンクチャネルで読み替えられてもよい。 Additionally, the base station in the present disclosure may be replaced by a user terminal. For example, communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, it may be called Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.). Regarding the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, the user terminal 20 may have the functions that the base station 10 described above has. Further, words such as "uplink" and "downlink" may be replaced with words corresponding to inter-terminal communication (for example, "sidelink"). For example, uplink channels, downlink channels, etc. may be replaced with sidelink channels.
　同様に、本開示におけるユーザ端末は、基地局で読み替えてもよい。この場合、上述のユーザ端末２０が有する機能を基地局１０が有する構成としてもよい。 Similarly, the user terminal in the present disclosure may be replaced with a base station. In this case, the base station 10 may have the functions that the user terminal 20 described above has.
　本開示において、基地局によって行われるとした動作は、場合によってはその上位ノード（upper　node）によって行われることもある。基地局を有する１つ又は複数のネットワークノード（network　nodes）を含むネットワークにおいて、端末との通信のために行われる様々な動作は、基地局、基地局以外の１つ以上のネットワークノード（例えば、Mobility　Management　Entity（ＭＭＥ）、Serving-Gateway（Ｓ－ＧＷ）などが考えられるが、これらに限られない）又はこれらの組み合わせによって行われ得ることは明らかである。 In this disclosure, the operations performed by the base station may be performed by its upper node in some cases. In a network that includes one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (e.g. It is clear that this can be performed by a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc. (though not limited thereto), or a combination thereof.
　本開示において説明した各態様／実施形態は単独で用いてもよいし、組み合わせて用いてもよいし、実行に伴って切り替えて用いてもよい。また、本開示において説明した各態様／実施形態の処理手順、シーケンス、フローチャートなどは、矛盾の無い限り、順序を入れ替えてもよい。例えば、本開示において説明した方法については、例示的な順序を用いて様々なステップの要素を提示しており、提示した特定の順序に限定されない。 Each aspect/embodiment described in this disclosure may be used alone, in combination, or may be switched and used in accordance with execution. Further, the order of the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this disclosure may be changed as long as there is no contradiction. For example, the methods described in this disclosure use an example order to present elements of the various steps and are not limited to the particular order presented.
　本開示において説明した各態様／実施形態は、Long　Term　Evolution（ＬＴＥ）、LTE-Advanced（ＬＴＥ－Ａ）、LTE-Beyond（ＬＴＥ－Ｂ）、ＳＵＰＥＲ　３Ｇ、ＩＭＴ－Ａｄｖａｎｃｅｄ、4th　generation　mobile　communication　system（４Ｇ）、5th　generation　mobile　communication　system（５Ｇ）、6th　generation　mobile　communication　system（６Ｇ）、xth　generation　mobile　communication　system（ｘＧ（ｘは、例えば整数、小数））、Future　Radio　Access（ＦＲＡ）、Ｎｅｗ－Radio　Access　Technology（ＲＡＴ）、New　Radio（ＮＲ）、New　radio　access（ＮＸ）、Future　generation　radio　access（ＦＸ）、Global　System　for　Mobile　communications（ＧＳＭ（登録商標））、ＣＤＭＡ２０００、Ultra　Mobile　Broadband（ＵＭＢ）、ＩＥＥＥ　８０２．１１（Ｗｉ－Ｆｉ（登録商標））、ＩＥＥＥ　８０２．１６（ＷｉＭＡＸ（登録商標））、ＩＥＥＥ　８０２．２０、Ultra-WideBand（ＵＷＢ）、Ｂｌｕｅｔｏｏｔｈ（登録商標）、その他の適切な無線通信方法を利用するシステム、これらに基づいて拡張、修正、作成又は規定された次世代システムなどに適用されてもよい。また、複数のシステムが組み合わされて（例えば、ＬＴＥ又はＬＴＥ－Ａと、５Ｇとの組み合わせなど）適用されてもよい。 Each aspect/embodiment described in this disclosure includes Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system ( 4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is an integer or decimal number, for example)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802 .11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), and other appropriate wireless communication methods. The present invention may be applied to systems to be used, next-generation systems expanded, modified, created, or defined based on these systems. Furthermore, a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G) may be applied.
　本開示において使用する「に基づいて」という記載は、別段に明記されていない限り、「のみに基づいて」を意味しない。言い換えれば、「に基づいて」という記載は、「のみに基づいて」と「に少なくとも基づいて」の両方を意味する。 As used in this disclosure, the phrase "based on" does not mean "based solely on" unless explicitly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."
　本開示において使用する「第１の」、「第２の」などの呼称を使用した要素へのいかなる参照も、それらの要素の量又は順序を全般的に限定しない。これらの呼称は、２つ以上の要素間を区別する便利な方法として本開示において使用され得る。したがって、第１及び第２の要素の参照は、２つの要素のみが採用され得ること又は何らかの形で第１の要素が第２の要素に先行しなければならないことを意味しない。 As used in this disclosure, any reference to elements using the designations "first," "second," etc. does not generally limit the amount or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, reference to a first and second element does not imply that only two elements may be employed or that the first element must precede the second element in any way.
　本開示において使用する「判断（決定）（determining）」という用語は、多種多様な動作を包含する場合がある。例えば、「判断（決定）」は、判定（judging）、計算（calculating）、算出（computing）、処理（processing）、導出（deriving）、調査（investigating）、探索（looking　up、search、inquiry）（例えば、テーブル、データベース又は別のデータ構造での探索）、確認（ascertaining）などを「判断（決定）」することであるとみなされてもよい。 The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "judgment" can mean judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry ( For example, searching in a table, database, or other data structure), ascertaining, etc. may be considered to be "determining."
　また、「判断（決定）」は、受信（receiving）（例えば、情報を受信すること）、送信（transmitting）（例えば、情報を送信すること）、入力（input）、出力（output）、アクセス（accessing）（例えば、メモリ中のデータにアクセスすること）などを「判断（決定）」することであるとみなされてもよい。 In addition, "judgment (decision)" includes receiving (e.g., receiving information), transmitting (e.g., sending information), input (input), output (output), access ( may be considered to be "determining", such as accessing data in memory (eg, accessing data in memory).
　また、「判断（決定）」は、解決（resolving）、選択（selecting）、選定（choosing）、確立（establishing）、比較（comparing）などを「判断（決定）」することであるとみなされてもよい。つまり、「判断（決定）」は、何らかの動作を「判断（決定）」することであるとみなされてもよい。 In addition, "judgment" is considered to mean "judging" resolving, selecting, choosing, establishing, comparing, etc. Good too. In other words, "judgment (decision)" may be considered to be "judgment (decision)" of some action.
　また、「判断（決定）」は、「想定する（assuming）」、「期待する（expecting）」、「みなす（considering）」などで読み替えられてもよい。 Furthermore, "judgment (decision)" may be read as "assuming", "expecting", "considering", etc.
　本開示に記載の「最大送信電力」は送信電力の最大値を意味してもよいし、公称最大送信電力（the　nominal　UE　maximum　transmit　power）を意味してもよいし、定格最大送信電力（the　rated　UE　maximum　transmit　power）を意味してもよい。 The "maximum transmit power" described in this disclosure may mean the maximum value of transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the It may also mean rated UE maximum transmit power).
　本開示において使用する「接続された（connected）」、「結合された（coupled）」という用語、又はこれらのあらゆる変形は、２又はそれ以上の要素間の直接的又は間接的なあらゆる接続又は結合を意味し、互いに「接続」又は「結合」された２つの要素間に１又はそれ以上の中間要素が存在することを含むことができる。要素間の結合又は接続は、物理的であっても、論理的であっても、あるいはこれらの組み合わせであってもよい。例えば、「接続」は「アクセス」で読み替えられてもよい。 As used in this disclosure, the terms "connected", "coupled", or any variations thereof refer to any connection or coupling, direct or indirect, between two or more elements. can include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connection" may be replaced with "access."
　本開示において、２つの要素が接続される場合、１つ以上の電線、ケーブル、プリント電気接続などを用いて、並びにいくつかの非限定的かつ非包括的な例として、無線周波数領域、マイクロ波領域、光（可視及び不可視の両方）領域の波長を有する電磁エネルギーなどを用いて、互いに「接続」又は「結合」されると考えることができる。 In this disclosure, when two elements are connected, they may be connected using one or more electrical wires, cables, printed electrical connections, etc., as well as in the radio frequency domain, microwave can be considered to be "connected" or "coupled" to each other using electromagnetic energy having wavelengths in the light (both visible and invisible) range.
　本開示において、「ＡとＢが異なる」という用語は、「ＡとＢが互いに異なる」ことを意味してもよい。なお、当該用語は、「ＡとＢがそれぞれＣと異なる」ことを意味してもよい。「離れる」、「結合される」などの用語も、「異なる」と同様に解釈されてもよい。 In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." Note that the term may also mean that "A and B are each different from C". Terms such as "separate" and "coupled" may also be interpreted similarly to "different."
　本開示において、「含む（include）」、「含んでいる（including）」及びこれらの変形が使用されている場合、これらの用語は、用語「備える（comprising）」と同様に、包括的であることが意図される。さらに、本開示において使用されている用語「又は（or）」は、排他的論理和ではないことが意図される。 Where "include", "including" and variations thereof are used in this disclosure, these terms are inclusive, as is the term "comprising". It is intended that Furthermore, the term "or" as used in this disclosure is not intended to be exclusive or.
　本開示において、例えば、英語でのa,　an及びtheのように、翻訳によって冠詞が追加された場合、本開示は、これらの冠詞の後に続く名詞が複数形であることを含んでもよい。 In this disclosure, when articles are added by translation, such as a, an, and the in English, the present disclosure may include that the nouns following these articles are plural.
　本開示において、「以下」、「未満」、「以上」、「より多い」、「と等しい」などは、互いに読み替えられてもよい。また、本開示において、「良い」、「悪い」、「大きい」、「小さい」、「高い」、「低い」、「早い」、「遅い」、「広い」、「狭い」、などを意味する文言は、原級、比較級及び最上級に限らず互いに読み替えられてもよい。また、本開示において、「良い」、「悪い」、「大きい」、「小さい」、「高い」、「低い」、「早い」、「遅い」、「広い」、「狭い」などを意味する文言は、「ｉ番目に」（ｉは任意の整数）を付けた表現として、原級、比較級及び最上級に限らず互いに読み替えられてもよい（例えば、「最高」は「ｉ番目に最高」と互いに読み替えられてもよい）。 In the present disclosure, "less than or equal to", "less than", "more than", "more than", "equal to", etc. may be read interchangeably. In addition, in this disclosure, "good", "bad", "large", "small", "high", "low", "early", "slow", "wide", "narrow", etc. The words are not limited to the original, comparative, and superlative, and may be interpreted interchangeably. In addition, in this disclosure, words meaning "good", "bad", "large", "small", "high", "low", "early", "slow", "wide", "narrow", etc. may be interpreted as an expression with "the i-th" (i is any integer), not only in the elementary, comparative, and superlative, but also interchangeably (for example, "the highest" can be interpreted as "the i-th highest"). may be read interchangeably).
　本開示において、「の（of）」、「のための（for）」、「に関する（regarding）」、「に関係する（related　to）」、「に関連付けられる（associated　with）」などは、互いに読み替えられてもよい。 In this disclosure, "of", "for", "regarding", "related to", "associated with", etc. are used to refer to each other. It may be read differently.
　以上、本開示に係る発明について詳細に説明したが、当業者にとっては、本開示に係る発明が本開示中に説明した実施形態に限定されないということは明らかである。本開示に係る発明は、請求の範囲の記載に基づいて定まる発明の趣旨及び範囲を逸脱することなく修正及び変更態様として実施することができる。したがって、本開示の記載は、例示説明を目的とし、本開示に係る発明に対して何ら制限的な意味をもたらさない。 Although the invention according to the present disclosure has been described in detail above, it is clear for those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the invention as determined based on the claims. Therefore, the description of the present disclosure is for the purpose of illustrative explanation and does not have any limiting meaning on the invention according to the present disclosure.

Claims (6)

  1. 　メッセージ１の繰り返しの能力に関する第１能力情報と、メッセージ３の繰り返しの能力に関する第２能力情報と、を送信する送信部と、
    　前記第１能力情報及び前記第２能力情報に基づいて、前記メッセージ１の繰り返し及び前記メッセージ３の繰り返しを含む第１ランダムアクセス手順を行うか、前記メッセージ１の繰り返し及び前記メッセージ３の繰り返しの少なくとも１つを含まない第２ランダムアクセス手順を行うか、を決定する制御部と、を有する端末。     a transmitter that transmits first capability information regarding the ability to repeat message 1 and second capability information regarding the ability to repeat message 3;
    Based on the first capability information and the second capability information, a first random access procedure including repeating the message 1 and repeating the message 3 is performed, or at least repeating the message 1 and repeating the message 3. a control unit that determines whether to perform a second random access procedure that does not include one.
  2. 　前記制御部は、第１ランダムアクセスリソースを前記第１ランダムアクセス手順に用い、前記第１ランダムアクセスリソースと異なる第２ランダムアクセスリソースを前記第２ランダムアクセス手順に用いる、請求項１に記載の端末。 The terminal according to claim 1, wherein the control unit uses a first random access resource for the first random access procedure and uses a second random access resource different from the first random access resource for the second random access procedure. .
  3. 　前記制御部は、参照信号受信電力と閾値の比較に基づいて、前記第１ランダムアクセス手順を行うか、前記第２ランダムアクセス手順を行うか、を決定する、請求項１に記載の端末。 The terminal according to claim 1, wherein the control unit determines whether to perform the first random access procedure or the second random access procedure based on a comparison between reference signal reception power and a threshold value.
  4. 　前記制御部は、前記メッセージ１の繰り返しの最大数と、参照信号受信電力に対する閾値と、の少なくとも１つに関する情報の受信を制御する、請求項１に記載の端末。 The terminal according to claim 1, wherein the control unit controls reception of information regarding at least one of a maximum number of repetitions of the message 1 and a threshold for reference signal reception power.
  5. 　メッセージ１の繰り返しの能力に関する第１能力情報と、メッセージ３の繰り返しの能力に関する第２能力情報と、を送信するステップと、
    　前記第１能力情報及び前記第２能力情報に基づいて、前記メッセージ１の繰り返し及び前記メッセージ３の繰り返しを含む第１ランダムアクセス手順を行うか、前記メッセージ１の繰り返し及び前記メッセージ３の繰り返しの少なくとも１つを含まない第２ランダムアクセス手順を行うか、を決定するステップと、を有する、端末の無線通信方法。     transmitting first capability information regarding the ability to repeat message 1 and second capability information regarding the ability to repeat message 3;
    Based on the first capability information and the second capability information, a first random access procedure including repeating the message 1 and repeating the message 3 is performed, or at least repeating the message 1 and repeating the message 3. A wireless communication method for a terminal, comprising the step of determining whether to perform a second random access procedure that does not include one.
  6. 　メッセージ１の繰り返しの能力に関する第１能力情報と、メッセージ３の繰り返しの能力に関する第２能力情報と、を受信する受信部と、
    　前記第１能力情報及び前記第２能力情報に基づいて、前記メッセージ１の繰り返し及び前記メッセージ３の繰り返しを含む第１ランダムアクセス手順を行うか、前記メッセージ１の繰り返し及び前記メッセージ３の繰り返しの少なくとも１つを含まない第２ランダムアクセス手順を行うか、を決定する制御部と、を有する基地局。
          a receiving unit that receives first ability information regarding the ability to repeat message 1 and second ability information regarding the ability to repeat message 3;
    Based on the first capability information and the second capability information, a first random access procedure including repeating the message 1 and repeating the message 3 is performed, or at least repeating the message 1 and repeating the message 3. a control unit that determines whether to perform a second random access procedure that does not include one.
PCT/JP2022/026726 2022-07-05 2022-07-05 Terminal, wireless communication method, and base station WO2024009402A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/026726 WO2024009402A1 (en) 2022-07-05 2022-07-05 Terminal, wireless communication method, and base station

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/026726 WO2024009402A1 (en) 2022-07-05 2022-07-05 Terminal, wireless communication method, and base station

Publications (1)

Publication Number Publication Date
WO2024009402A1 true WO2024009402A1 (en) 2024-01-11

Family

ID=89453002

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/026726 WO2024009402A1 (en) 2022-07-05 2022-07-05 Terminal, wireless communication method, and base station

Country Status (1)

Country Link
WO (1) WO2024009402A1 (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017135455A1 (en) * 2016-02-04 2017-08-10 株式会社Ｎｔｔドコモ User equipment, and random access method

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017135455A1 (en) * 2016-02-04 2017-08-10 株式会社Ｎｔｔドコモ User equipment, and random access method

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 17)", 3GPP TS 38.331, no. V17.0.0, 19 April 2022 (2022-04-19), pages 1 - 1221, XP052146036 *
HUAWEI, HISILICON: "Report of [AT118-e][103][CovEnh] RRC CR (Huawei)", 3GPP TSG RAN WG2 #118-E R2-2206193, 27 May 2022 (2022-05-27), XP052156292 *

Similar Documents

Publication Publication Date Title
WO2024009402A1 (en) Terminal, wireless communication method, and base station
WO2024009400A1 (en) Terminal, radio communication method, and base station
WO2024009403A1 (en) Terminal, radio communication method, and base station
WO2024009401A1 (en) Terminal, radio communication method, and base station
WO2024029076A1 (en) Terminal, wireless communication method, and base station
WO2024038516A1 (en) Terminal, wireless communication method, and base station
WO2024038515A1 (en) Terminal, wireless communication method, and base station
WO2024038514A1 (en) Terminal, wireless communication method, and base station
WO2023223551A1 (en) Terminal, radio communication method, and base station
WO2023223552A1 (en) Terminal, wireless communication method, and base station
WO2023105756A1 (en) Terminal, wireless communication method, and base station
WO2023105755A1 (en) Terminal, radio communication method, and base station
WO2023105754A1 (en) Terminal, wireless communication method, and base station
WO2023095272A1 (en) Terminal, radio communication method, and base station
WO2023095273A1 (en) Terminal, wireless communication method, and base station
WO2023095269A1 (en) Terminal, wireless communication method, and base station
WO2023095270A1 (en) Terminal, wireless communication method, and base station
WO2023095271A1 (en) Terminal, radio communication method, and base station
WO2023119647A1 (en) Terminal, wireless communication method, and base station
WO2023119649A1 (en) Terminal, wireless communication method, and base station
WO2023119646A1 (en) Terminal, wireless communication method, and base station
WO2023135754A1 (en) Terminal, wireless communication method, and base station
WO2023135755A1 (en) Terminal, wireless communication method, and base station
WO2023119648A1 (en) Terminal, wireless communication method and base station
WO2024069840A1 (en) Terminal, wireless communication method, and base station

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: 22950196

Country of ref document: EP

Kind code of ref document: A1