Nothing Special   »   [go: up one dir, main page]

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

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

Info

Publication number
WO2024154342A1
WO2024154342A1 PCT/JP2023/001733 JP2023001733W WO2024154342A1 WO 2024154342 A1 WO2024154342 A1 WO 2024154342A1 JP 2023001733 W JP2023001733 W JP 2023001733W WO 2024154342 A1 WO2024154342 A1 WO 2024154342A1
Authority
WO
WIPO (PCT)
Prior art keywords
prach
random access
pdcch
tci
transmission
Prior art date
Application number
PCT/JP2023/001733
Other languages
English (en)
Japanese (ja)
Inventor
尚哉 芝池
祐輝 松村
聡 永田
チーピン ピ
ジン ワン
ラン チン
Original Assignee
株式会社Ｎｔｔドコモ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社Ｎｔｔドコモ filed Critical 株式会社Ｎｔｔドコモ
Priority to PCT/JP2023/001733 priority Critical patent/WO2024154342A1/fr
Publication of WO2024154342A1 publication Critical patent/WO2024154342A1/fr

Links

Images

Classifications

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

Definitions

  • This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems.
  • LTE Long Term Evolution
  • UMTS Universal Mobile Telecommunications System
  • Non-Patent Document 1 LTE-Advanced (3GPP Rel. 10-14) was specified for the purpose of achieving higher capacity and greater sophistication over LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).
  • LTE 5th generation mobile communication system
  • 5G+ 5th generation mobile communication system
  • 6G 6th generation mobile communication system
  • NR New Radio
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • Improvements to coverage are being considered for future wireless communication systems (e.g., NR).
  • one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that improve the coverage of the random access procedure.
  • a terminal has a receiving unit that receives transmission settings of a plurality of physical random access channels (PRACHs) that respectively correspond to a plurality of spatial domain transmission filters, and a control unit that determines a pseudo-co-location assumption for downlink reception based on a specific PRACH among the plurality of PRACHs, a random access response, a physical uplink shared channel (PUSCH) scheduled by the random access response, or a physical downlink shared channel (PDSCH) with a contention resolution identifier.
  • PRACHs physical random access channels
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • FIG. 1 shows an example of a RACH configuration information element.
  • 2A and 2B show an example of PRACH occasion and beam association.
  • FIG. 3 shows an example of multiple PUCCH resource sets before individual PUCCH resource configuration.
  • FIG. 4 shows an example of case 1.
  • FIG. 5 shows an example of case 2.
  • FIG. 6 shows an example of case 3.
  • FIG. 7 shows an example of case 4.
  • FIG. 8 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment.
  • FIG. 9 is a diagram illustrating an example of the configuration of a base station according to an embodiment.
  • FIG. 10 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment.
  • FIG. 11 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment.
  • FIG. 12 is a diagram illustrating an example of a vehicle according to an embodiment.
  • TCI transmission configuration indication state
  • the TCI state may represent that which applies to the downlink signal/channel.
  • the equivalent of the TCI state which applies to the uplink signal/channel may be expressed as a spatial relation.
  • TCI state is information about the Quasi-Co-Location (QCL) of signals/channels and may also be called spatial reception parameters, spatial relation information, etc. TCI state may be set in the UE on a per channel or per signal basis.
  • QCL Quasi-Co-Location
  • QCL is an index that indicates the statistical properties of a signal/channel. For example, if a signal/channel has a QCL relationship with another signal/channel, it may mean that it can be assumed that at least one of the Doppler shift, Doppler spread, average delay, delay spread, and spatial parameters (e.g., spatial Rx parameters) is identical between these different signals/channels (i.e., it is QCL with respect to at least one of these).
  • spatial parameters e.g., spatial Rx parameters
  • the spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be identified based on a spatial QCL.
  • the QCL (or at least one element of the QCL) in this disclosure may be interpreted as sQCL (spatial QCL).
  • QCL types QCL types
  • QCL types A to D QCL types A to D
  • the parameters (which may be called QCL parameters) are as follows: QCL Type A (QCL-A): Doppler shift, Doppler spread, mean delay and delay spread, QCL type B (QCL-B): Doppler shift and Doppler spread, QCL type C (QCL-C): Doppler shift and mean delay; QCL Type D (QCL-D): Spatial reception parameters.
  • QCL Type A QCL-A
  • QCL-B Doppler shift and Doppler spread
  • QCL type C QCL type C
  • QCL Type D QCL Type D
  • the UE's assumption that a 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 may be referred to as a QCL assumption.
  • CORESET Control Resource Set
  • QCL QCL type D
  • the UE may determine at least one of a transmit beam (Tx beam) and a receive beam (Rx beam) for a signal/channel based on the TCI condition 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 the target channel (in other words, the reference signal (RS) for that channel) and another signal (e.g., another RS).
  • the TCI state may be set (indicated) by higher layer signaling, physical layer signaling, or a combination of these.
  • the physical layer signaling may be, for example, Downlink Control Information (DCI).
  • DCI Downlink Control Information
  • the channel for which the TCI state or spatial relationship is set (specified) may be, for example, at least one of the downlink shared channel (Physical Downlink Shared Channel (PDSCH)), the downlink control channel (Physical Downlink Control Channel (PDCCH)), the uplink shared channel (Physical Uplink Shared Channel (PUSCH)), and the uplink control channel (Physical Uplink Control Channel (PUCCH)).
  • PDSCH Physical Downlink Shared Channel
  • PDCCH Physical Downlink Control Channel
  • PUSCH Physical Uplink Shared Channel
  • PUCCH Physical Uplink Control Channel
  • the RS that has a QCL relationship with the channel may be, for example, at least one of a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a sounding reference signal (SRS), a tracking CSI-RS (also called a tracking reference signal (TRS)), and a QCL detection reference signal (also called a QRS).
  • SSB synchronization signal block
  • CSI-RS channel state information reference signal
  • SRS sounding reference signal
  • TRS tracking CSI-RS
  • QRS QCL detection reference signal
  • An SSB is a signal block that includes at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • PBCH Physical Broadcast Channel
  • An SSB may also be referred to as an SS/PBCH block.
  • An RS of QCL type X in a TCI state may refer to an RS that has a QCL type X relationship with a certain channel/signal (DMRS), and this RS may be called a QCL source of QCL type X in that TCI state.
  • DMRS channel/signal
  • the unified TCI framework does not specify the TCI state or spatial relationship for each channel as in Rel. 15, but instead specifies a common beam (common TCI state) and may apply it to all UL and DL channels, or a common beam for UL may apply to all UL channels and a common beam for DL may apply to all DL channels.
  • a common beam common TCI state
  • One common beam for both DL and UL, or one common beam for DL and one common beam for UL (total of two common beams) are being considered.
  • the UE may assume the same TCI state for UL and DL (joint TCI state, joint TCI pool, joint common TCI pool, joint TCI state set).
  • the UE may assume different TCI states for UL and DL respectively (separate TCI state, separate TCI pool, UL separate TCI pool and DL separate TCI pool, separate common TCI pool, UL common TCI pool and DL common TCI pool).
  • the UL and DL default beams may be aligned via MAC CE based beam management (MAC CE level beam instructions).
  • the PDSCH default TCI state may be updated to match the default UL beam (spatial relationship).
  • DCI based beam management may indicate a common beam/unified TCI state from the same TCI pool (joint common TCI pool, joint TCI pool, set) for both UL and DL.
  • X (>1) TCI states may be activated by the MAC CE.
  • the UL/DL DCI may select one out of the X active TCI states.
  • the selected TCI state may be applied to both UL and DL channels/RS.
  • the TCI pool (set) may be multiple TCI states set by RRC parameters, or multiple TCI states (active TCI states, active TCI pool, set) activated by the MAC CE among multiple TCI states set by RRC parameters.
  • Each TCI state may be a QCL type A/D RS.
  • SSB, CSI-RS, or SRS may be set as the QCL type A/D RS.
  • the number of TCI states corresponding to each of one or more TRPs may be specified.
  • the number N ( ⁇ 1) of TCI states (UL TCI states) applied to UL channels/RS and the number M ( ⁇ 1) of TCI states (DL TCI states) applied to DL channels/RS may be specified.
  • At least one of N and M may be notified/configured/instructed to the UE via higher layer signaling/physical layer signaling.
  • this may mean that one UL TCI state and one DL TCI state for a single TRP are notified/configured/instructed separately to the UE (separate TCI states for a single TRP).
  • this may mean that multiple (two) UL TCI states and multiple (two) DL TCI states for multiple (two) TRPs are notified/configured/instructed to the UE (separate TCI states for multiple TRPs).
  • N and M are 1 or 2, but the values of N and M may be 3 or more, and N and M may be different.
  • it may be supported to indicate one common beam (e.g., a common beam) by RRC/MAC CE/DCI, and the one common beam may be applied to multiple DL/UL channels/reference signals.
  • Other cases may be supported in Rel. 18 and later.
  • RRC parameters configure multiple TCI states for both DL and UL.
  • the TCI states configured by the RRC parameters may be referred to as configured TCI states.
  • the MAC CE may activate multiple TCI states among the configured TCI states.
  • the DCI may indicate one of the activated TCI states.
  • the TCI state indicated by the DCI may be referred to as indicated TCI state.
  • the DCI may be a UL DCI (e.g., a DCI used for scheduling a PUSCH) or a DL DCI (e.g., a DCI used for scheduling a PDSCH).
  • the indicated TCI state may apply to at least one (or all) of the UL/DL channels/RS.
  • One DCI may indicate both UL TCI and DL TCI.
  • the indicated TCI state ID may be one TCI state that applies to both UL and DL, or it may be two TCI states that apply to UL and DL, respectively.
  • At least one of the multiple TCI states configured by the RRC parameters and the multiple TCI states activated by the MAC CE may be referred to as a TCI pool (common TCI pool, joint TCI pool, TCI state pool).
  • the multiple TCI states activated by the MAC CE may be referred to as an active TCI pool (active common TCI pool).
  • the higher layer parameters (RRC parameters) that set multiple TCI states may be referred to as configuration information that sets multiple TCI states, or simply as “configuration information.” Also, in this disclosure, being instructed to set one of multiple TCI states using DCI may mean receiving indication information that indicates one of the multiple TCI states included in DCI, or may simply mean receiving "instruction information.”
  • the RRC parameters configure multiple TCI states (joint common TCI pools) for both DL and UL.
  • the MAC CE may activate multiple TCI states (active TCI pools) among the configured multiple TCI states. Separate active TCI pools for each of the UL and DL may be configured/activated.
  • the DL DCI or new DCI format may select (indicate) one or more (e.g., one) TCI states.
  • the selected TCI state may apply to one or more (or all) DL channels/RS.
  • the DL channels may be PDCCH/PDSCH/CSI-RS.
  • the UE may determine the TCI state of each DL channel/RS using the TCI state behavior (TCI framework) of Rel. 16.
  • the UL DCI or new DCI format may select (indicate) one or more (e.g., one) TCI states.
  • the selected TCI state may apply to one or more (or all) UL channels/RS.
  • the UL channels may be PUSCH/SRS/PUCCH. In this way, different DCIs may indicate UL TCI and DL DCI separately.
  • the MAC CE/DCI will support beam activation/indication to a TCI state associated with a different physical cell identifier (PCI). Also, in Rel. 18 NR and later, it is assumed that the MAC CE/DCI will support indicative serving cell change to a cell with a different PCI.
  • PCI physical cell identifier
  • the joint TCI state and the separate (DL/UL) TCI state may be switched. Whether the joint TCI state or the separate TCI state is applied may be set by the base station to the UE by a higher layer parameter, or may be switched by the TCI field (TCI state ID) in the DCI.
  • Antenna Port QCL Physical Layer Procedure for Data
  • the UE can configure a list of up to 128 DLorJointTCIState configurations in PDSCH-Config.
  • the UE may apply the DLorJointTCIState or UL-TCIState setting from the reference BWP of the reference CC. If the UE has DLorJointTCIState or UL-TCIState set in any CC in the same band, it is not assumed that TCI-State, SpatialRelationInfo (spatial relation information), or PUCCH-SpatialRelationInfo (PUCCH spatial relation information) in that band is set, except for SpatialRelationInfoPos (spatial relation information for position).
  • SpatialRelationInfo spatial relation information
  • PUCCH-SpatialRelationInfo PUCCH spatial relation information
  • the UE assumes that if the UE has TCI-State in any CC in the CC list configured by simultaneousTCI-UpdateList1-r16, simultaneousTCI-UpdateList2-r16, simultaneousSpatial-UpdatedList1-r16, or simultaneousSpatial-UpdatedList2-r16, the UE does not configure DLorJointTCIState or UL-TCIState in any CC in the CC list.
  • the UE receives an activation command that is used to map up to eight TCI states and/or TCI state pairs, with one TCI state for DL channels/signals and one TCI state for UL channels/signals, to code points of the DCI field 'Transmission Configuration Indication' (TCI) for one of the CC/DL BWPs or for a set of CC/DL BWPs, if available.
  • TCI Transmission Configuration Indication
  • a set of TCI state IDs is activated for a set of CC/DL BWPs and, if available, for one of the CC/DL BWPs, the same set of TCI state IDs applies to all DL and/or UL BWPs in the indicated CC, where the applicable list of CCs is determined by the CCs indicated in the activation command.
  • the UE applies the indicated DLorJointTCIState and/or UL-TCIState to one or a set of CC/DL BWPs, and if the indicated mapping to a single TCI code point applies, the UE applies the indicated DLorJointTCIState and/or UL-TCIState to one or a set of CC/DL BWPs.
  • the UE shall assume that the QCL type A/D source RS is set in the CC/DL BWP to which the TCI state applies.
  • Unified TCI Framework supports the following modes 1 to 3: [Mode 1] MAC CE based TCI state indication [Mode 2] DCI based TCI state indication by DCI format 1_1/1_2 with DL assignment [Mode 3] DCI based TCI state indication by DCI format 1_1/1_2 without DL assignment
  • TCI State ID receives DCI format 1_1/1_2 providing indicated TCI state with Rel.
  • DCI format 1_1/1_2 may or may not be accompanied by DL assignment if one is available.
  • DCI format 1_1/1_2 does not carry a DL assignment
  • the UE can assume (verify) the following for that DCI: -
  • the CS-RNTI is used to scramble the CRC for the DCI.
  • the values of the following DCI fields are set as follows: -
  • the redundancy version (RV) field is all '1's.
  • the modulation and coding scheme (MCS) field is all '1's.
  • NDI new data indicator
  • the frequency domain resource assignment (FDRA) field is all '0's for FDRA type 0 or all '1's for FDRA type 1 or all '0's for Dynamic Switch (similar to PDCCH validation for release of DL semi-persistent scheduling (SPS) or UL grant type 2 scheduling).
  • DCI in the above Mode 2/Mode 3 may be called beam instruction DCI.
  • Rel. 15/16 if the UE does not support active BWP change via DCI, the UE will ignore the BWP indicator field.
  • a similar behavior is considered for the relationship between Rel. 17 TCI state support and the interpretation of the TCI field. If the UE is configured with Rel. 17 TCI state, the TCI field will always be present in DCI format 1_1/1_2, and if the UE does not support TCI update via DCI, the UE will ignore the TCI field.
  • the presence or absence of a TCI field (TCI presence information in DCI, tci-PresentInDCI) is set for each CORESET.
  • the TCI field in DCI format 1_1 is 0 bits if the higher layer parameter tci-PresentInDCI is not enabled, and 3 bits otherwise. If the BWP indicator field indicates a BWP other than the active BWP, the UE shall follow the following actions: [Operation] If the higher layer parameter tci-PresentInDCI is not enabled for the CORESET used for the PDCCH carrying that DCI format 1_1, the UE shall assume that tci-PresentInDCI is not enabled for all CORESETs in the indicated BWP, otherwise the UE shall assume that tci-PresentInDCI is enabled for all CORESETs in the indicated BWP.
  • the TCI field in DCI format 1_2 is 0 bit if the higher layer parameter tci-PresentInDCI-1-2 is not set, otherwise it is 1, 2 or 3 bits determined by the higher layer parameter tci-PresentInDCI-1-2. If the BWP indicator field indicates a BWP other than the active BWP, the UE shall follow the following actions.
  • the UE shall assume that tci-PresentInDCI is not enabled for all CORESETs in the indicated BWP, otherwise the UE shall assume that tci-PresentInDCI-1-2 for all CORESETs in the indicated BWP is set with the same value as tci-PresentInDCI-1-2 set for the CORESET used for the PDCCH carrying that DCI format 1_2.
  • the value of the TCI field for indicating the joint DL/UL TCI status is associated with a TCI status ID indicating the joint DL/UL TCI status.
  • the value of the TCI field for separate DL/UL TCI status indication is associated with at least one TCI status ID, a TCI status ID indicating a DL-only TCI status and a TCI status ID indicating a UL-only TCI status.
  • the TCI field values 000 to 001 are associated with only one TCI status ID for DL
  • the TCI field values 010 to 011 are associated with only one TCI status ID for UL
  • the TCI field values 100 to 111 are associated with both one TCI status ID for DL and one TCI status ID for UL.
  • the unified/common TCI state may mean the Rel. 17 TCI state indicated using (Rel. 17) DCI/MAC CE/RRC (indicated Rel. 17 TCI state).
  • TCI state indicates whether or not TCI is mapped to multiple types of signals (channels/RS).
  • unified/common TCI state TCI state applicable to multiple types of signals (channels/RS)
  • TCI state for multiple types of signals channels/RS
  • the indicated Rel. 17 TCI state may be shared with at least one of the UE-specific reception on PDSCH/PDCC (updated using Rel. 17 DCI/MAC CE/RRC), PUSCH of dynamic grant (DCI)/configured grant, and multiple (e.g., all) dedicated PUCCH resources.
  • the TCI state indicated by the DCI/MAC CE/RRC may be referred to as the indicated TCI state, the unified TCI state.
  • a TCI state other than the unified TCI state may refer to a Rel. 17 TCI state configured using the (Rel. 17) MAC CE/RRC (configured Rel. 17 TCI state).
  • the configured Rel. 17 TCI state, the configured TCI state, a TCI state other than the unified TCI state, and a TCI state applied to a specific type of signal (channel/RS) may be interpreted as being mutually interchangeable.
  • the configured Rel. 17 TCI state may not be shared with at least one of the UE-specific reception in the PDSCH/PDCC (updated using Rel. 17 DCI/MAC CE/RRC), the PUSCH of the dynamic grant (DCI)/configured grant, and multiple (e.g., all) dedicated PUCCH resources.
  • the configured Rel. 17 TCI state may be configured by the RRC/MAC CE for each CORESET/resource/resource set, and may not be updated even if the indicated Rel. 17 TCI state (common TCI state) described above is updated.
  • the indicated Rel. 17 TCI state will be applied to UE-specific channels/signals (RS). It is also being considered that the UE will be notified using higher layer signaling (RRC signaling) as to whether the indicated Rel. 17 TCI state or the configured Rel. 17 TCI state will be applied to non-UE-specific channels/signals.
  • RS UE-specific channels/signals
  • RRC signaling higher layer signaling
  • the RRC parameters for the configured Rel. 17 TCI state (TCI state ID) will have the same configuration as the RRC parameters for the TCI state in Rel. 15/16. It is being considered that the configured Rel. 17 TCI state will be configured/instructed for each CORESET/resource/resource set using RRC/MAC CE. It is also being considered that the UE will make decisions regarding the configuration/instruction based on specific parameters.
  • the UE will update the indicated TCI state and the configured TCI state separately. For example, if the unified TCI state for the indicated TCI state is updated for the UE, the configured TCI state may not need to be updated. It is also being considered that the UE will make a decision about the update based on a specific parameter.
  • RRC/MAC CE higher layer signaling
  • TCI state indication for intra-cell beam indication (TCI state indication), it is being considered to support Rel. 17 TCI state indication for UE-specific CORESET and PDSCH associated with that CORESET, and non-UE-specific CORESET and PDSCH associated with that CORESET.
  • inter-cell beam indication e.g., L1/L2 inter-cell mobility
  • support for indicating Rel. 17 TCI states for UE-specific CORESETs and PDSCHs associated with the CORESETs is under consideration.
  • the legacy MAC CE/RACH signaling mechanism may be used.
  • the CSI-RS related to the Rel. 17 TCI state applied to CORESET#0 may be QCL'd with the SSB related to the serving cell PCI (physical cell ID) (similar to Rel. 15).
  • CORESETs with a common search space (CSS), and CORESETs with a CSS and a UE-specific search space (USS), whether to follow the indicated Rel. 17 TCI state may be configured for each CORESET by an RRC parameter. If the indicated Rel. 17 TCI state is not configured for that CORESET, the configured Rel. 17 TCI state may be applied to that CORESET.
  • CCS common search space
  • USS UE-specific search space
  • RRC parameters may be configured for each channel/resource/resource set to follow or not follow the indicated Rel. 17 TCI state. If the indicated Rel. 17 TCI state is not configured for that channel/resource/resource set, the configured Rel. 17 TCI state may be applied to that channel/resource/resource set.
  • the indicated TCI state by the MAC CE/DCI may apply to the following channels/RS:
  • CORESET0 follows the TCI state activated by the MAC CE or is QCL'd with SSB.
  • the indicated TCI state For a CORESET with index other than 0 with USS/CSS type 3, the indicated TCI state always applies.
  • the indicated TCI state applies. Otherwise, the configured TCI state for that CORESET applies to that CORESET.
  • [PDSCH] - The indicated TCI state always applies for all UE-dedicated PDSCHs.
  • a non-UE-dedicated PDSCH PDSCH scheduled by a DCI in the CSS
  • followUnifiedTCIState is set (for the CORESET of the PDCCH that schedules the PDSCH)
  • the indicated TCI state may apply. Otherwise, the configured TCI state for the PDSCH applies to the PDSCH.
  • followUnifiedTCIState is not set for a PDSCH, whether a non-UE-dedicated PDSCH follows the indicated TCI state may depend on whether followUnifiedTCIState is set for the CORESET used to schedule the PDSCH.
  • CSI-RS For an A-CSI-RS for CSI acquisition or beam management, if followUnifiedTCIState is set (for the CORESET of the PDCCH that triggers that A-CSI-RS), the indicated TCI state applies. For other CSI-RSs, the configured TCI state for that CSI-RS applies.
  • Beam application time (BAT) Regarding the DCI-based beam indication in Rel. 17, the following studies 1 and 2 are being considered regarding the application time of the indication of the beam/unified TCI state (beam application time (BAT) conditions). .
  • the first slot to apply the indicated TCI is at least Y symbols after the last symbol of the acknowledgement (ACK) for the joint or separate DL/UL beam indication. It is contemplated that the first slot to apply the indicated TCI is at least Y symbols after the last symbol of the ACK/negative acknowledgement (NACK) for the joint or separate DL/UL beam indication.
  • Y symbols may be set by the base station based on the UE capabilities reported by the UE. The UE capabilities may be reported on a symbol-by-symbol basis.
  • the ACK may be an ACK for a PDSCH scheduled by the beam instruction DCI.
  • the PDSCH may not be transmitted.
  • the ACK in this case may be an ACK for the beam instruction DCI.
  • the value of the Y symbol will also be different, so the application time may differ between multiple CCs.
  • the application timing/BAT of the beam instruction may follow any of the following options 1 to 3.
  • Both the first slot and the Y symbol are determined on the carrier with the smallest SCS among the one or more carriers to which the beam direction applies.
  • Both the first slot and the Y symbol are determined on the carrier with the smallest SCS among the one or more carriers to which the beam instruction applies and the UL carrier carrying the ACK.
  • Both the first slot and the Y symbol are determined on the UL carrier that carries the ACK.
  • the application time (Y symbols) of beam direction for CA may be determined on the carrier with the smallest SCS among the carriers to which beam direction applies.
  • Rel. 17 MAC CE based beam direction (when only a single TCI codepoint is activated) may follow the Rel. 16 application timeline for MAC CE activation.
  • the indicated TCI state with Rel. 17 TCI state may start to apply from the first slot that is at least Y symbols after the last symbol of the PUCCH, where Y may be a higher layer parameter (e.g., BeamAppTime_r17[symbols]). Both the first slot and Y symbols may be determined on the carrier with the smallest SCS among the carriers for which the beam indication applies.
  • the UE may assume one indicated TCI state with Rel17 TCI state for DL and UL, or one indicated TCI state with Rel17 TCI state for UL (separate from DL) at a given time.
  • X [ms] may be used instead of Y [symbol].
  • the UE reports at least one of the following UE capabilities 1 and 2.
  • UE Capability 1 Minimum application time per SCS (minimum of Y symbols between the last symbol of the PUCCH carrying ACK and the first slot in which the beam is applied).
  • UE Capability 2 Minimum time gap between the last symbol of the beam instruction PDCCH (DCI) and the first slot where the beam is applied. The gap between the last symbol of the beam instruction PDCCH (DCI) and the first slot where the beam is applied may meet the UE capability (minimum time gap).
  • UE capability 2 may be an existing UE capability (e.g., timeDurationForQCL).
  • the relationship between the beam instruction and the channel/RS to which the beam is applied may satisfy at least one of UE capabilities 1 and 2.
  • the parameters set by the base station regarding the application time may be optional fields.
  • the UE receives the SS/PBCH block (SSB), transmits Msg. 1 (PRACH/random access preamble/preamble), receives Msg. 2 (PDCCH, PDSCH including random access response (RAR)), transmits Msg. 3 (PUSCH scheduled by RAR UL grant), and receives Msg. 4 (PDCCH, PDSCH including UE contention resolution identity).
  • Msg. 1 PRACH/random access preamble/preamble
  • RAR random access response
  • 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 includes detection of part of the physical cell ID (PCI), detection (synchronization) of the OFDM symbol timing, and (coarse) frequency synchronization.
  • SSS detection includes detection of the physical cell ID.
  • PBCH-DMRS detection includes detection of (part of) the SSB index within a half radio frame (5 ms).
  • PBCH reception includes detection of the system frame number (SFN) and radio frame timing (SSB index), reception of configuration information for remaining minimum system information (RMSI, SIB1) reception, and recognition of whether the UE can camp on that cell (carrier).
  • SFN system frame number
  • SSB index radio frame timing
  • SSB has a bandwidth of 20RB and a time of 4 symbols.
  • the transmission period of SSB can be set from ⁇ 5, 10, 20, 40, 80, 160 ⁇ ms.
  • multiple symbol positions of SSB are specified based on the frequency range (FR1, FR2).
  • the PBCH has a payload of 56 bits. N repetitions of the PBCH are transmitted within a period of 80 ms, where N depends on the SSB transmission period.
  • the system information consists of the MIB, RMSI (SIB1), and other system information (OSI) carried by the PBCH.
  • SIB1 contains information for RACH configuration and RACH procedures.
  • the time/frequency resource relationship between the SSB and the PDCCH monitoring resources for SIB1 is set by the PBCH.
  • a base station using beam correspondence transmits multiple SSBs using multiple beams for each SSB transmission period.
  • the multiple SSBs each have multiple SSB indices.
  • a UE that detects an SSB transmits a PRACH in the RACH occasion associated with that SSB index and receives an 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 find 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 a specific direction, but the signal will be even more difficult to reach in other directions. If the direction in which the UE exists is unknown in the base station before the UE is connected, it is impossible to transmit the synchronization signal/reference signal using a beam only in the appropriate direction. A method is considered in which the base station transmits multiple synchronization signals/reference signals each having a beam in a different direction, and the UE recognizes which beam it has found. If a thin (narrow) beam is used for coverage, it is necessary to transmit many synchronization signals/reference signals, which may increase overhead and reduce frequency utilization efficiency.
  • PRACH extensions for frequency range (FR) 2.
  • PRACH repetition multiple PRACH transmissions
  • This PRACH extension may be applied to the 4-step RACH procedure or to FR1.
  • PRACH extensions may be applied to short PRACH formats or other formats.
  • one RAR window may be used for each PRACH transmission.
  • the RAR window may follow existing designs.
  • only one RAR window may be used for all of the multiple PRACH transmissions.
  • the UE may use different transmit (Tx) beams for transmitting multiple PRACHs across multiple ROs associated with the same SSB/CSI-RS.
  • Tx transmit
  • the common RACH configuration may include a generic RACH configuration (rach-ConfigGeneric), a total number of RA preambles (totalNumberOfRA-Preambles), and SSB per RACH occasion and contention-based (CB) preambles per SSB (ssb-perRACH-OccasionAndCB-PreamblesPerSSB).
  • the rach-ConfigGeneric may include a PRACH configuration index (prach-ConfigurationIndex) and a message 1 FDM (msg1-FDM, the number of PRACH occasions FDMed in one time instance).
  • ssb-perRACH-OccasionAndCB-PreamblesPerSSB may contain the number of CB preambles per SSB for oneEighth (one SSB associated with eight RACH occasions) of SSBs per RACH occasion.
  • the UE may apply the number N of SS/PBCH blocks associated with one PRACH occasion and the number R of CB preambles per SS/PBCH block per valid PRACH occasion via ssb-perRACH-OccasionAndCB-PreamblesPerSSB.
  • N_preamble ⁇ total is given by totalNumberOfRA-Preambles for type 1 random access procedures, and by msgA-TotalNumberOfRA-Preambles for type 2 random access procedures involving the configuration of a PRACH occasion independent of the type 1 random access procedure.
  • N_preamble ⁇ total is a multiple of N.
  • the association period for mapping SS/PBCH blocks to PRACH occasions 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) such that N Tx SSB SS/PBCH block indices are mapped to a PRACH occasion at least once in the association period, where the UE derives N Tx SSB from the value of ssb-PositionsInBurst in SIB1 or in the ServingCellConfigCommon.
  • An association pattern period includes one or more association periods and is determined such that the pattern between PRACH occasions and SS/PBCH block indices repeats at most every 160 ms. If there is a PRACH occasion that is not associated to a SS/PBCH block index after an integer number of association periods, then that PRACH occasion is not used for PRACH.
  • the PRACH mask index is indicated by ra-ssb-OccasionMaskIndex, which indicates the PRACH occasion for which the PRACH occasion is associated with the selected SS/PBCH block index.
  • the PRACH occasions are mapped consecutively for each corresponding SS/PBCH block index.
  • the indexing of the PRACH occasions indicated by the mask index value is reset for each SS/PBCH block index and for each successive PRACH occasion mapping cycle.
  • the UE selects for PRACH transmission the PRACH occasion indicated by the PRACH mask index value for the indicated SS/PBCH block index in the first available mapping cycle.
  • the order of the PRACH occasions is as follows: First, in increasing order of frequency resource index for frequency multiplexed PRACH occasions. Second, in 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 the PRACH transmission, where the PRACH occasions are associated with the selected CSI-RS index indicated by csi-RS.
  • the indexing of the PRACH occasions indicated by ra-OccasionList is reset every association pattern period.
  • the association periods are ⁇ 1, 2, 4, 8, 16 ⁇ , ⁇ 1, 2, 4, 8 ⁇ , ⁇ 1, 2, 4 ⁇ , ⁇ 1, 2 ⁇ , and ⁇ 1 ⁇ , respectively.
  • the value of the PRACH mask index value (msgA-SSB-SharedRO-MaskIndex) is associated with the allowed PRACH occasions (PRACH occasion index values) of the SSB.
  • 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
  • preamble indexes 48 to 63 are associated with SSB3.
  • the same RO is associated with different SS/PBCH block indices
  • different preambles use different SS/PBCH block indices.
  • the base station can distinguish the associated SS/PBCH block indexes by the received PRACH.
  • the random access preamble can only be transmitted in time resources specified in the random access configuration of the specification, depending on FR1 or FR2 and spectrum type (paired spectrum/supplementary uplink (SUL)/unpaired spectrum).
  • the PRACH configuration index is given by the higher layer parameter prach-ConfigurationIndex or, if configured, by msgA-PRACH-ConfigurationIndex.
  • the type of RACH procedure triggered by different purposes is 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 a PDCCH order), CFRA for beam failure recovery (BFR), CFRA for system information (SI) request, CFRA for reconfiguration with sync, etc.
  • CFRA contention-free random access
  • PDCCH ordered RA PDCCH ordered RA
  • CFRA for beam failure recovery
  • SI system information
  • CFRA for reconfiguration with sync
  • CBRA contention-based random access
  • RA triggered by MAC entity RA triggered by RRC with event
  • CBRA for BFR etc.
  • - 4 step RACH - Two-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 the C-RNTI and the frequency domain resource assignment field is all 1, then the DCI format 1_0 is for a random access procedure initiated by a PDCCH order, and the remaining fields are a random access preamble, a UL/supplementary uplink (SUL) indicator, a SS/PBCH index (SSB index), a PRACH mask index, and reserved bits (12 bits).
  • CRC cyclic redundancy check
  • the PRACH mask index field indicates the PRACH occasion of the PRACH transmission that is associated with the SS/PBCH block index indicated by the SS/PBCH block index field of the PDCCH order if the value of the random access preamble index field is not zero.
  • the random access procedure is initiated by a PDCCH order, by the MAC entity itself, or by RRC for specification compliant events. Within a MAC entity, there can only be one random access procedure in progress at any time.
  • the random access procedure for an SCell is only initiated by a PDCCH order with ra-PreambleIndex different from 0b000000.
  • the MAC entity When a random access procedure is initiated on the serving cell, the MAC entity does the following: - If the random access procedure is initiated by a PDCCH order and the ra-PreambleIndex explicitly provided by the PDCCH is not 0b000000, or if the random access procedure is initiated for a reconfiguration with synchronization and a 4-step RA type contention-free random access resource is explicitly provided by rach-ConfigDedicated for the BWP selected for the random access procedure, set RA_TYPE to 4-stepRA.
  • the MAC entity shall do the following: - If ra-PreambleIndex is explicitly provided by the PDCCH and ra-PreambleIndex is not 0b000000, set PREAMBLE_INDEX to the notified ra-PreambleIndex and select the SSB notified by the PDCCH. - If an SSB is selected as above, determine the next available PRACH occasion from the PRACH occasions allowed by the restrictions given by ra-ssb-OccasionMaskIndex and corresponding to the selected SSB (the MAC entity selects a PRACH occasion randomly with equal probability from among consecutive PRACH occasions corresponding to the selected SSB according to the specifications. The MAC entity may take into account possible occurrence of measurement gaps when determining the next available PRACH occasion corresponding to the selected SSB).
  • the UE if requested by higher layers, transmits PRACH within the selected PRACH occasion as described in the specification if the time between the last symbol of the PDCCH order reception and the first symbol of the PRACH transmission is greater than or equal to N_(T,2)+ ⁇ _BWPSwitching+ ⁇ _Delay+T_switch [msec] (time condition), where N_(T,2) is the duration of N_2 symbols corresponding to the PUSCH preparation time of UE processing capability 1.
  • N_(T,2) is the duration of N_2 symbols corresponding to the PUSCH preparation time of UE processing capability 1.
  • ⁇ corresponds to the minimum subcarrier spacing (SCS) setting between the SCS setting of the PDCCH order and the SCS setting of the corresponding PRACH transmission.
  • SCS subcarrier spacing
  • ⁇ _BWPSwitching 0, otherwise ⁇ _BWPSwitching is defined in the specification.
  • T_switch is the switching gap duration defined 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.
  • a PRACH occasion within a PRACH slot is valid if: The PRACH occasion is within a UL symbol, or The PRACH occasion does not precede an SS/PBCH block in the PRACH slot and starts at least N_gap symbols after the last DL symbol and at least N_gap symbols after the last SS/PBCH block symbol, where N_gap is defined in the specification.
  • the PRACH occasion does not overlap with the set of consecutive symbols before the start of the next channel occupancy period during which there should not be any transmission, as described 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.
  • RA-ResponseWindow is the time window for monitoring RA Response (RAR) (special cell (SpCell) only).
  • RA-ContentionResolutionTimer is the timer for RA contention resolution (SpCell only).
  • Msg. B ResponseWindow is the time window for monitoring RA Response (RAR) for 2-step RA type (SpCell only).
  • SpCell primary cell
  • PCell primary cell
  • PSCell primary secondary cell
  • the MAC entity When an RA preamble is transmitted, the MAC entity performs the following actions 1 to 3, regardless of the possibility that a measurement gap may occur.
  • the MAC entity performs the following operations 2-1 and 2-2.
  • the MAC entity starts the ra-ResponseWindow configured in the common RACH configuration (RACH-ConfigCommon) on the first PDCCH occasion after the end of the RA preamble transmission.
  • the MAC entity monitors the PDCCH transmission of the SpCell for the RAR identified by the RA-RNTI while the ra-ResponseWindow is running.
  • the MAC entity may stop the ra-ResponseWindow (or stop monitoring for the RAR) after successful reception of an RAR 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 the base station's response to BFR and PDCCH for RAR. The following may apply to both cases.
  • the MAC entity When the MSGA (Msg. A) preamble is transmitted, the MAC entity performs the following actions 4 to 6, regardless of whether a measurement gap may occur.
  • the MAC entity starts the Msg. B response window (msgB-ResponseWindow) in the PDCCH monitoring window defined in the specification.
  • the msgB-ResponseWindow may start at the first symbol of the earliest CORESET for which the UE is configured to receive a PDCCH for a Type 1-PDCCH CSS set that is at least one symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission.
  • the length of the msgB-ResponseWindow may correspond to the SCS for the Type 1-PDCCH CSS set.
  • the MAC entity monitors the PDCCH transmission of the SpCell for the RAR identified by the MSGB-RNTI while the msgB-ResponseWindow is running.
  • RA-RNTI 1+s_id+14 ⁇ t_id+14 ⁇ 80 ⁇ f_id+14 ⁇ 80 ⁇ 8 ⁇ ul_carrier_id
  • 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) carrier, 1 for supplementary uplink (SUL) carrier).
  • RA-RNTI is calculated according to the specification.
  • RA-RNTI is the RNTI for 4-step RACH.
  • MSGB-RNTI 1+s_id+14 ⁇ t_id+14 ⁇ 80 ⁇ f_id+14 ⁇ 80 ⁇ 8 ⁇ ul_carrier_id+14 ⁇ 80 ⁇ 8 ⁇ 2
  • 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) carrier, 1 for supplementary uplink (SUL) carrier).
  • MSGB-RNTI is the RNTI for 2-step RACH.
  • the UE In response to a PRACH transmission, the UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI during the aforementioned higher layer controlled window.
  • the window starts at the first symbol of the earliest CORESET for which the UE is configured to receive a PDCCH for the Type 1-PDCCH CSS set, i.e. at least one symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission.
  • the symbol period corresponds to the SCS for the Type 1-PDCCH CSS set.
  • the length of the window is based on the SCS for the Type 1-PDCCH CSS set and is given by ra-responseWindow as number of slots.
  • the UE may assume the same DMRS antenna port QCL properties for the SS/PBCH block or CSI-RS resource that the UE uses to associate the PRACH, regardless of whether the UE is provided with a TCI-State for the CORESET in which it receives the PDCCH with that DCI format 1_0.
  • the UE may assume that the PDCCH containing that DCI format 1_0 and the PDCCH order have the same DMRS antenna port QCL properties.
  • the UE may assume the DMRS antenna port QCL properties of the CORESET associated to the type 1-PDCCH CSS set for reception of the PDCCH containing that DCI format 1_0.
  • the RAR UL grant may include at least one of a frequency hopping flag field, a PUSCH frequency resource allocation field, a PUSCH time resource allocation field, a modulation and coding scheme (MCS) field, a TPC command field for PUSCH, a CSI request field, and a channel access-cyclic prefix extension (CPext) field.
  • MCS modulation and coding scheme
  • CPext channel access-cyclic prefix extension
  • the UE In single-cell operation or operation with carrier aggregation in the same frequency band, if the qcl-Type set in the 'typeD' properties of a DMRS for monitoring a PDCCH in a type 1-PDCCH CSS set is not set to the same as the qcl-Type set in the 'typeD' properties of a DMRS for monitoring a PDCCH in a type 0/0A/0B/2/3-PDCCH CSS set or in a USS set, and that PDCCH or associated PDSCH overlaps with a PDCCH or associated PDSCH that the UE monitors in the type 1-PDCCH CSS set by at least one symbol, the UE shall not assume to monitor a PDCCH in a type 0/0A/0B/2/3-PDCCH CSS set or in a USS set.
  • the UE If the UE is provided with one or more search space sets by PDCCH-Config with corresponding one or more of searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, peiSearchSpace, ra-SearchSpace, and CSS sets, and is provided with SI-RNTI, P-RNTI, PEI-RNTI, RA-RNTI, MsgB-RNTI, SFI-RNTI, INT-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI, for any RNTI from these RNTIs, the UE shall not assume that it processes information from more than one DCI format with CRC scrambled using that RNTI per slot.
  • the UE transmits a transport block on the PUSCH scheduled by the RAR UL grant in the corresponding RAR message.
  • the UE transmits the PUSCH in slot n+k 2 + ⁇ +2 ⁇ ⁇ K cell,offset .
  • k2 is a slot offset, determined based on the allocation table row index m+1 provided by the PUSCH time resource allocation field value m of the RAR UL grant and the PUSCH subcarrier spacing ⁇ PUSCH.
  • ⁇ is an additional subcarrier spacing-specific slot delay time value for the first transmission of the PUSCH scheduled by the RAR, specific to the PUSCH subcarrier spacing ⁇ PUSCH, and is applied in addition to K2 .
  • the UE transmits PUSCH over N PUSCH repeat slots, where N PUSCH repeat is indicated by the 2 MSBs of the MCS field in the RAR UL grant or DCI format 0_0 from a set of four values provided by numberOfMsg3Repetitions, or from ⁇ 1, 2, 3, 4 ⁇ if numberOfMsg3Repetitions is not provided.
  • the UE decides whether to apply Msg3 repetition based on the RSRP. If Msg repetition is configured and the RSRP of the DL pathloss reference is less than rsrp-ThresholdMsg3 (threshold), the MAC entity assumes that Msg3 repetition is applicable to the current random access (RA) procedure.
  • RA random access
  • the UE can request Msg3 PUSCH repetition via a separate PRACH resource.
  • the MAC entity selects an RA resource if there are one or more sets of available RA resources, one of which is used to indicate all functions that trigger this RA procedure, or if there are one or more sets of available RA resources configured with indications for a subset of all functions that trigger this RA procedure. 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 as not available for the RACH procedure.
  • RA resources may be partitioned for each function.
  • the functions may include at least one of Msg3 repetition, reduced capacity (RedCap), small data transmission (SDT), and RAN slicing.
  • Priority of each feature (priority, featurePriorities-r17). This priority is used to determine which FeatureCombinationPreambles the UE should use when a feature is mapped to more than one FeatureCombinationPreamble. Additional RO configuration, including available capabilities (which may be associated with multiple capabilities), RA resources (e.g., preamble index), and mask index to differentiate ROs.
  • the UE decides which RO to use depending on its capabilities.
  • SIB1 contains ServingCellConfigCommonSIB, which contains UplinkConfigCommonSIB, which contains BWP-UplinkCommon (UL BWP common configuration).
  • BWP-UplinkCommon may include RACH common configuration (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 setting may include FeatureCombinationPreambles.
  • FeatureCombinationPreambles associates one set of preambles (partition) 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 number of preambles.
  • the available RO is explicitly set by the PRACH mask index.
  • At least one of the PRACH occasion indexes 1 to 8 can be set using the relationship between the PRACH mask index and the allowed PRACH occasions (ROs) of the SSB (MAC protocol specification/table of PRACH mask index values).
  • the number of Msg3 repetitions is indicated by the 2 most significant bits (MSBs) of the modulation and coding scheme (MCS) field in the RAR UL grant.
  • MSBs most significant bits
  • MCS modulation and coding scheme
  • the 2 MSBs of the MCS information field of the RAR UL grant provide a code point for determining the number of repetitions K, according to the relationship (table) between the value (code point) of the 2 MSBs of the MCS information field and the number of repetitions K, based on whether the upper layer parameter numberOfMsg3Repetitions is set or not.
  • the number of slots N used to determine the transport block size (TBS) is equal to 1.
  • the 2 MSBs of the MCS information field of that DCI format provide a code point for determining the number of repetitions K, according to the relationship (table) between the value (code point) of the 2 MSBs of the MCS information field and the number of repetitions K, based on whether the upper layer parameter numberOfMsg3Repetitions is set or not.
  • the number of slots N used for TBS determination is equal to 1.
  • the MAC entity follows actions 1 to 4 below. [Action 1] If Msg3 is transmitted over a non-terrestrial network, the MAC entity starts the ra-ContentionResolutionTimer and restarts it at each HARQ retransmission within the first symbol after the end of Msg3 plus the UE estimate of the UE-gNB RTT. [Action 2] Otherwise, if the Msg3 transmission (initial transmission or HARQ retransmission) is scheduled with Type A PUSCH repetitions, the MAC entity starts or restarts the ra-ContentionResolutionTimer within the first symbol after the end of all repetitions of the Msg3 transmission.
  • the MAC entity If not, the MAC entity starts or restarts the ra-ContentionResolutionTimer within the first symbol after the end of the Msg3 transmission. [Operation 4] The MAC entity monitors the PDCCH while the ra-ContentionResolutionTimer is running, regardless of the possibility of a measurement gap occurring.
  • Step 4 (Msg4) in the Rel. 16 NR RA procedure follows the step 4 operations below.
  • Step 4 Operation If the UE is not provided with a C-RNTI, in response to a PUSCH transmission scheduled by an RAR UL grant, the UE schedules a PDSCH containing the UE contention resolution identity and attempts to detect DCI format 1_0 with CRC scrambled by the corresponding TCI-RNTI. In response to receiving a PDSCH containing the UE contention resolution identity, the UE transmits HARQ-ACK information in the PUCCH.
  • the PUCCH transmission is in the same active UL BWP as the PUSCH transmission.
  • N_T,1 is the duration of N_T,1 symbols, which corresponds to the PDSCH processing time of UE processing capability 1 when additional PDSCH DM-RS is configured.
  • N_T,1 is the duration of N_T,1 symbols, which corresponds to the PDSCH processing time of UE processing capability 1 when additional PDSCH DM-RS is configured.
  • the UE may assume that the PDCCH carrying that DCI format has the same DM-RS antenna port quasi co-location (QCL) properties for the SS/PBCH block used by the UE for PRACH association, regardless of whether the UE is provided with a TCI state for the CORESET in which the UE received the PDCCH with that DCI format.
  • QCL quasi co-location
  • the PUCCH resource set for transmission of HARQ-ACK information on PUCCH within the initial UL BWP of N BWP size PRBs is provided by pucch-ResourceCommon through an index to a row of a table of multiple PUCCH resource sets before the dedicated PUCCH resource configuration specified in the specification (default PUCCH resource table, Figure 3).
  • pucch-ResourceCommon included in SIB1 indicates index values 0 to 15.
  • the default PUCCH resource table associates an index with a PUCCH resource set.
  • Each PUCCH resource set includes PUCCH format 0/1, the first symbol of the PUCCH, the number of symbols of the PUCCH, the PRB offset of the PUCCH, and a set of initial cyclic shift indexes.
  • the UE determines the PUCCH resource in the PUCCH resource set indicated by the index based on the PDCCH that schedules the PDSCH (the first CCE of that PDCCH, the PUCCH resource indicator field in the DCI).
  • the UE transmits the PUSCH using the same spatial domain transmit filter as the PUSCH transmission scheduled by the RAR UL grant.
  • the UE shall generate at most one HARQ-ACK information bit.
  • Provision 1a For any CORESET other than the CORESET with index 0, the UE shall follow the following: If the UE is not provided with the configuration of one or more TCI states for its CORESET via the TCI state lists for PDCCH (tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList) or is provided with the initial configuration of more than one TCI state for its CORESET via tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList but has not received a MAC CE activation command for one of the more than one TCI states, the UE shall assume that the DM-RS antenna port associated to PDCCH reception is quasi co-located (QCL) with the SS/PBCH block identified by the UE during the initial access procedure or with the SS/PBCH block for the most recently configured grant PUSCH for the same HARQ process.
  • QCL quasi co-located
  • the UE shall assume that the DM-RS antenna port associated to PDCCH reception is QCL'd with the SS/PBCH block or CSI-RS resource that the UE identified during the random access procedure initiated by the Reconfiguration with sync procedure.
  • Provision 1b For CORESET with index 0, the UE shall follow the following: - If a UE is provided with a DL or joint-TCI state (DLorJoint-TCIState, dl-OrJoint-TCIStateList) and the unified TCI state is enabled for the CORESET (followUnifiedTCIstate 'enabled'), the UE shall assume that the DM-RS antenna port associated to PDCCH reception is QCL'd with the reference signal provided by the indicated DLorJoint-TCIState.
  • the UE shall assume that the DM-RS antenna port associated to PDCCH reception in the CORESET is QCL'd with one of the following reference signals: -- if there is one or more DL RSs configured with a TCI state and that TCI state is indicated by a MAC CE Activation Command for that CORESET, then that DL RS, or - if no MAC CE Activation Command indicating a TCI state for the CORESET has been received after the most recent random access procedure not initiated by a PDCCH order triggering a contention-free random access (CFRA) procedure, the SS/PBCH blocks identified by the UE during the most recent random access procedure, or -- SS/PBCH blocks identified by the UE during the most recent configuration grant PUSCH transmission.
  • CFRA contention-free random access
  • Provision 2a After a UE receives an initial higher layer configuration of more than one DLorJoint-TCIState and before application of an indicated TCI state from the configured TCI states, the UE assumes that the DM-RS of the PDSCH, the DM-RS of the PDCCH, and the CSI-RS to which the indicated TCI state applies are QCL'd with the SS/PBCH blocks identified by the UE during the initial access procedure.
  • Provision 2b After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL TCI state (UL-TCIState) and before application of an indicated TCI state from the configured multiple TCI states, the UE assumes that the UL transmission (TX) spatial filter for dynamic or configured grant based PUSCH and PUCCH and SRS to which the indicated TCI state applies is the same as the UL TX spatial filter for PUSCH transmission scheduled by the RAR UL grant during the initial access procedure.
  • TX UL transmission
  • Provision 2c After a UE receives an initial higher layer configuration of more than one DLorJoint-TCIState as part of a reconfiguration with synchronization procedure, and before application of an indicated TCI state from the configured TCI states, the UE assumes that the DM-RS of the PDSCH, the DM-RS of the PDCCH and the CSI-RS to which the indicated TCI state applies are QCL'd with the SS/PBCH blocks or CSI-RS resources identified by the UE during the random access procedure initiated by the reconfiguration with synchronization procedure.
  • the UE After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState as part of a reconfiguration with synchronization procedure and before application of an indicated TCI state from the configured TCI states, the UE shall assume that the UL TX spatial filter for dynamic or configured grant based PUSCH and PUCCH and SRS, to which the indicated TCI state applies, is the same as the UL TX spatial filter for PUSCH transmission scheduled by a RAR UL grant during the random access procedure initiated by the reconfiguration with synchronization procedure.
  • TCI presence in DCI (tci-PresentInDCI) is set to 'enabled' or the TCI presence in DCI1-2 (tci-PresentDCI-1-2) is configured for the CORESET scheduling the PDSCH, and if the time for QCL (timeDurationForQCL) is available, then if the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than timeDurationForQCL, after the UE receives the initial higher layer configuration of the multiple TCI state and before the reception of the activation command, the UE shall assume that the DM-RS port of the PDSCH of the serving cell is QCL-linked with the SS/PBCH block determined in the initial access procedure for QCL type (qcl-Type) set to 'typeA' and, if qcl-Type set to 'typeD' is available, for qcl-Type set to 'typeD'.
  • QCL type qcl-Type
  • the UE For a PUSCH scheduled by fallback DCI (DCI format 0_0), the UE shall follow the following: For a PUSCH scheduled by DCI format 0_0 on a cell, if the spatial relationship corresponding to the dedicated PUCCH resource with the lowest ID in the active UL BWP of the cell is applicable, the UE shall transmit the PUSCH according to the spatial relationship. If the dedicated PUCCH resource with the lowest ID in the active UL BWP of the cell corresponds to two spatial relationships, the UE shall transmit the PUSCH according to the spatial relationship with the lowest ID.
  • the UE shall transmit PUSCH according to the spatial relationship for the RS configured with qcl-Type set to 'typeD' corresponding to the QCL assumption of the CORESET with the lowest ID on the active DL BWP of the cell, if that spatial relationship is applicable.
  • the UE shall use the first TCI state (of the two TCI states) as the QCL assumption.
  • the UE shall transmit the PUSCH according to the spatial relationship.
  • the UE shall use the first TCI state (of the two TCI states) as the QCL assumption.
  • the UE For PUSCH scheduled by non-fallback DCI (UL DCI other than DCI format 0_0), the UE follows the SRS resource indicator (SRI) indication, i.e., SRS configuration is assumed.
  • SRI SRS resource indicator
  • the beam (spatial relationship) for PUCCH before individual configuration (e.g., HARQ-ACK for Msg4) follows Msg3 PUSCH.
  • pucch-SpatialRelationInfo indicates the ID of the SSB, CSI-RS, or SRS.
  • the SSB or CSI-RS identified during the initial access procedure or random access procedure is considered as the QCL source RS.
  • the UL TX spatial filter of Msg3 PUSCH is considered as the UL TX spatial filter before proper configuration/indication of beams for UL PUSCH/PUCCH/SRS.
  • the beams for UL PUSCH/PUCCH/SRS follow the following: -
  • the UL TX spatial filter for PUSCH scheduled by fallback DCI follows the PUCCH resource with the lowest ID or the CORESET with the lowest ID.
  • - UL TX spatial filter for PUSCH scheduled by non-fallback DCI follows SRI indication.
  • the UL TX spatial filter for PUCCH before dedicated configuration follows the UL TX spatial filter of Msg3 PUSCH.
  • - UL TX spatial filter for PUCCH after dedicated configuration follows pucch-SpatialRelationInfo.
  • the UE can be provided with a configuration for PRACH transmission by the dedicated PRACH resource configuration for BFR (PRACH-ResourceDedicatedBFR).
  • BFR Physical Layer Procedure for Control
  • the UE shall assume the same antenna port QCL parameters associated with q new until the UE receives activation for a TCI state or for any of the parameters of the TCI state list for PDCCH (at least one of tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList) by higher layers.
  • the UE After the UE detects a DCI format with CRC scrambled by the C-RNTI or MCS-C-RNTI in the search space set provided by recoverySearchSpaceId, the UE continues to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceId until the UE receives a MAC CE activation command for a TCI state or for any of the parameters of the TCI state list for PDCCH (at least one of tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList).
  • Provision 3c After 28 symbols from the last symbol of the first PDCCH reception in the search space set provided by recoverySearchSpaceId for the PCell or PSCell and for q0 and q1 , for which the UE detects a DCI format with CRC scrambled by the C-RNTI or MCS-C-RNTI, the UE assumes the same antenna port quasi-co-location (QCL) parameters in PDCCH monitoring in the CORESET with index 0 as the antenna port QCL parameters associated with index qnew .
  • QCL quasi-co-location
  • q 0 bar may be represented by placing an overline over "q 0 "
  • q 1 bar may be represented by placing an overline over "q 1 ".
  • Provision 3d If the UE is provided with TCI-State_r17 indicating a unified TCI state for the PCell or PSCell, then after X symbols from the last symbol of the first PDCCH reception in the search space set provided by recoverySearchSpaceId and in which the UE detects a DCI format with CRC scrambled by the C-RNTI or MCS-C-RNTI, the UE shall follow the following provisions.
  • the UE shall monitor the PDCCHs in the entire CORESET using the same antenna port QCL parameters as the antenna port QCL parameters associated with the corresponding index q new , if any, and receive the PDSCH and aperiodic CSI-RS from the CSI-RS resource set with the same TCI state as the indicated TCI state for the PDCCH and the PDSCH.
  • - Transmit the PUCCH, the PUSCH, and the SRS using the same spatial domain filters with the same TCI state as the indicated TCI state for PUCCH and PUSCH using the same spatial domain filters as for the latest PRACH transmission.
  • a PDCCH reception includes two PDCCH candidates from two linked search space sets based on the searchSpaceLinking configuration, the last symbol of the PDCCH reception is the last symbol of the later ending PDCCH candidate (of the two PDCCH candidates). If the UE is required to monitor one of the two PDCCH candidates, the PDCCH reception includes the two PDCCH candidates.
  • CBRA contention based random access
  • the UE shall monitor the PDCCH in the entire CORESET using the same antenna port QCL parameter as the antenna port QCL parameter and receive the PDSCH and aperiodic CSI-RS from the CSI-RS resource set with the same TCI state as the PDCCH and the indicated TCI state for the PDSCH.
  • - Transmit the PUCCH, the PUSCH, and the SRS using the same spatial domain filters with the same TCI state as the indicated TCI state for PUCCH and PUSCH using the same spatial domain filters as for the latest PRACH transmission.
  • the inventors therefore came up with a method for determining the beam.
  • A/B and “at least one of A and B” may be interpreted as interchangeable. Also, in this disclosure, “A/B/C” may mean “at least one of A, B, and C.”
  • Radio Resource Control RRC
  • RRC parameters RRC parameters
  • RRC messages higher layer parameters, fields, information elements (IEs), settings, etc.
  • IEs information elements
  • CE Medium Access Control
  • update commands activation/deactivation commands, etc.
  • the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., messages from the core network such as positioning protocols (e.g., NR Positioning Protocol A (NRPPa)/LTE Positioning Protocol (LPP)) messages), or a combination of these.
  • RRC Radio Resource Control
  • MAC Medium Access Control
  • LPP LTE Positioning Protocol
  • the MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc.
  • the broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.
  • MIB Master Information Block
  • SIB System Information Block
  • RMSI Remaining Minimum System Information
  • OSI System Information
  • the physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), etc.
  • DCI Downlink Control Information
  • UCI Uplink Control Information
  • the SSB/CSI-RS index/indicator, beam index, TCI state, spatial domain transmit filter, and spatial domain receive filter may be interchangeable.
  • the RAR window, ra-ResponseWindow, time window, RAR timer, and timer operation period may be read as interchangeable.
  • the contention resolution window, contention window, contention resolution timer, ra-ContentionResolutionTimer, and contention resolution timer operation period may be read as interchangeable.
  • the contention resolution identity, contention resolution identifier, contention resolution ID, and UE contention resolution identity may be read as interchangeable.
  • port antenna port, DMRS port, and DMRS antenna port may be interchangeable.
  • port being QCLed with RS reception and port using the same spatial domain (transmit/receive) filter as RS reception may be interchangeable.
  • DCI (format)/PDCCH (candidate) with CRC scrambled by a specific RNTI, DCI (format)/PDCCH (candidate) using a specific RNTI, and DCI (format)/PDCCH (candidate) monitored using a specific RNTI may be interpreted as interchangeable.
  • RACH resource, RA resource, PRACH preamble, occasion, RACH occasion (RO), PRACH occasion, repetition resource, repetition setting resource, resource set for RO/repetition, time instance and frequency instance, time resource and frequency resource, RO/preamble resource, repetition may be read as interchangeable.
  • period, cycle, frame, subframe, slot, symbol, occasion, RO may be read as interchangeable.
  • the PDCCH order, PDCCH order DCI, DCI format 1_0, and message (Msg) 0 may be read as interchangeable.
  • the PRACH, preamble, PRACH preamble, sequence, preamble format, and Msg1 may be read as interchangeable.
  • the response to the PRACH, the RAR, Msg2, MsgB, Msg4, the base station response to the BFR, and the DCI that schedules the response (RAR) may be read as interchangeable.
  • transmissions other than the PRACH in the random access procedure Msg3, the PUSCH scheduled by the RAR, the HARQ-ACK/PUCCH for Msg4, and MsgA PUSCH may be read as interchangeable.
  • the Msg3, the PUSCH scheduled by the RAR UL grant, and the RRC connection request may be read as interchangeable.
  • Msg4, contention resolution, RRC connection setup, and PDSCH with UE contention resolution identity may be interpreted as interchangeable.
  • the RAR, the DCI (PDCCH) that schedules the RAR, the PDSCH with the UE contention resolution identifier, and the DCI that schedules the PDSCH with the UE contention resolution identifier may be interpreted as interchangeable.
  • beam, SSB, SSB index, CSI-RS, CSI-RS resource, CSI-RS resource index, RS, QCL assumption, TCI state, unified TCI state, DL or joint TCI state, UL TCI state, UL Tx spatial filter, spatial domain filter, spatial domain transmit filter, spatial domain receive filter, antenna port QCL parameter, QCL parameter may be interpreted as interchangeable.
  • 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 a higher layer may be interchangeable.
  • the time resource, Msg1, Msg2, Msg3, Msg4, HARQ-ACK information, RAR window, contention resolution window, DCI for scheduling Msg2, and DCI for scheduling Msg4 may be interchangeable.
  • the earlier time resource may be a time resource that is earlier than the operation among multiple time resources corresponding to multiple repetitions of PRACH, or a time resource that has a smaller index (time domain index) corresponding to the repetition than the index of the operation.
  • the later time resource may be a time resource that is later than the operation among multiple time resources corresponding to multiple repetitions of PRACH, or a time resource that has a larger index (time domain index) corresponding to the repetition than the index of the operation.
  • default beam “beam applied for reception/transmission before receiving a beam setting/MAC CE,” “beam applied when no beam setting is provided,” “beam applied after receiving a multiple beam setting and before applying one of the multiple beams,” and “beam applied until a specific time has elapsed since receiving a beam instruction” may be interpreted interchangeably.
  • monitored/received/detected RAR and monitored/received/detected PDCCH that schedules RAR may be read as interchangeable.
  • RAR monitoring and monitoring of PDCCH that schedules RAR may be read as interchangeable.
  • RAR monitoring and monitoring of PDCCH that schedules RAR may be read as interchangeable.
  • Msg4 monitoring and monitoring of DCI format_0 with CRC scrambled by corresponding TC-RNTI that schedules PDSCH that includes UE contention resolution identifier may be read as interchangeable.
  • receiving/detecting an RAR and successfully receiving/detecting/monitoring an RAR may be interpreted as interchangeable.
  • receiving/detecting Msg4, successfully receiving/detecting/monitoring Msg4, and sending an ARQ/ACK in response to receiving Msg4 may be interpreted as interchangeable.
  • Case 1 The UE transmits multiple PRACHs using different transmission beams corresponding to different SSBs/CSI-RSs, each of which may be a wide transmission beam.
  • a separate RAR/Msg3/Msg4 is transmitted/received for each PRACH transmission (FIG. 4).
  • the UE transmits multiple PRACHs using different transmission beams corresponding to different SSBs/CSI-RSs, each of which may be a wide transmission beam, and a single RAR is transmitted/received for the multiple PRACH transmissions (FIG. 5).
  • the UE transmits multiple PRACHs using different transmit beams corresponding to the same SSB/CSI-RS, each of which may be a narrow transmit beam, and a separate RAR/Msg3/Msg4 is transmitted/received for each PRACH transmission (FIG. 6).
  • the UE transmits multiple PRACHs using different transmit beams corresponding to the same SSB/CSI-RS, each of which may be a narrow transmit beam, and a single RAR is transmitted/received for the multiple PRACH transmissions (FIG. 7).
  • a UE transmits multiple PRACHs using different beams corresponding to different SSB/CSI-RS within one RACH attempt during the initial access procedure and receives multiple Msg4s for the multiple PRACH transmissions, the UE may follow at least one of the following options:
  • the UE determines the first/last/randomly determined (any) received beam among multiple receptions of SSBs or CSI-RS associated with multiple PRACHs for multiple received Msg4s as the default beam for the PDCCH/PDSCH/CSI-RS.
  • the default beam in the example of Figure 4 above is the beam of SSB#1.
  • the default beam in the example of Figure 4 above is the beam of SSB#4.
  • the default beam in the example of Figure 4 above is any one of the beams of SSB#1/#2/#3/#4.
  • Provision 1a For CORESETs other than CORESET with index 0, the UE shall follow at least one of the following rules: - If the UE is not provided with the configuration of one or more TCI states for its CORESET via the TCI state lists for PDCCH (tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList) or is provided with the initial configuration of more than one TCI state for its CORESET via tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList but has not received a MAC CE activation command for one of the more than one TCI states, the UE shall assume that the DM-RS antenna port associated to PDCCH reception is QCL'd with the following SS/PBCH blocks: the SS/PBCH block identified by the UE during the initial access procedure (SS/PBCH block A), or -- if the UE transmits PRACHs corresponding to SS/PBCH blocks in
  • the UE shall assume that the DM-RS antenna port associated to PDCCH reception is QCL'd with the following SS/PBCH blocks or CSI-RS resources: SS/PBCH blocks or CSI-RS resources identified by the UE during a random access procedure initiated by a reconfiguration involving the synchronization procedure, or -- If the UE transmits multiple PRACHs corresponding to multiple SS/PBCH blocks or multiple CSI-RSs in the last random access attempt during the most recent random access procedure initiated by reconfiguration involving the synchronization procedure, the first/last/any SS/PBCH block or CSI-RS among the multiple SS/PBCH blocks or multiple
  • Provision 1b For a CORESET with index 0, the UE shall follow at least one of the following actions: - If a UE is provided with DLorJoint-TCIState and followUnifiedTCIstate 'enabled' for its CORESET, the UE shall assume that the DM-RS antenna port associated to PDCCH reception is QCL'd with the reference signal provided by the indicated DLorJoint-TCIState.
  • the UE shall assume that the DM-RS antenna ports associated to PDCCH reception in its CORESET are QCL'd with the following reference signals: -- if there is one or more DL RSs configured with a TCI state and that TCI state is indicated by a MAC CE Activation Command for that CORESET, then that DL RS, or - if no MAC CE Activation Command indicating a TCI state for the CORESET has been received after the most recent random access procedure not initiated by a PDCCH order triggering a CFRA procedure, the SS/PBCH blocks identified by the UE during the most recent random access procedure, or -- if no MAC CE Activation Command indicating a TCI state for the CORESET has been received after the latest random access procedure not initiated by a PDCCH order triggering a CFRA procedure, if the UE transmits PRACHs corresponding to SS/PBCH blocks in the last random access attempt during the latest random access procedure, the first/last/any of the SS/PB
  • Provision 2a After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState and before the application of an indicated TCI state from the configured TCI states, the UE shall assume that the DM-RS of PDSCH, the DM-RS of PDCCH, and the CSI-RS for which the indicated TCI state applies are QCL'd with the following SS/PBCH blocks: - SS/PBCH blocks identified by the UE during the initial access procedure, or - If the UE transmits multiple PRACHs corresponding to multiple SS/PBCH blocks in the last random access attempt during the latest initial access procedure, the first/last/any of the multiple SS/PBCH blocks corresponding to the PRACHs corresponding to the PDSCH with contention resolution identifier received by the UE during the latest initial access procedure.
  • Provision 2b After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState and before application of one indicated TCI state from the configured multiple TCI states, the UE shall assume that the UL TX spatial filter for dynamic or configured grant based PUSCH and PUCCH and SRS to which the indicated TCI state applies is the same as the UL TX spatial filter for PUSCH transmission scheduled by the RAR UL grant during the initial access procedure.
  • the UE After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState as part of a reconfiguration with synchronization procedure, and before the application of an indication TCI state from the configured TCI states, the UE shall assume that the DM-RS of PDSCH, DM-RS of PDCCH and CSI-RS, for which the indication TCI state applies, are QCL'd with the following SS/PBCH blocks or CSI-RS resources: - SS/PBCH blocks or CSI-RS resources identified by the UE during a random access procedure initiated by a reconfiguration involving the synchronization procedure, or - If the UE transmits multiple PRACHs corresponding to multiple SS/PBCH blocks or multiple CSI-RSs in the last random access attempt during the latest random access procedure initiated by reconfiguration involving the synchronization procedure, the first/last/any of the SS/PBCH blocks or CSI-RSs corresponding to the PRACHs corresponding to the PDSCH with contention resolution identifier
  • the UE After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState as part of a reconfiguration with synchronization procedure and before application of an indicated TCI state from the configured TCI states, the UE shall assume that the UL TX spatial filter for dynamic or configured grant based PUSCH and PUCCH and SRS, to which the indicated TCI state applies, is the same as the UL TX spatial filter for PUSCH transmission scheduled by a RAR UL grant during the random access procedure initiated by the reconfiguration with synchronization procedure.
  • tci-PresentInDCI is set to 'enabled' or tci-PresentDCI-1-2 is configured for the CORESET scheduling the PDSCH, and if timeDurationForQCL is available, then if the time offset between the reception of the DL DCI and the corresponding PDSCH is greater than or equal to timeDurationForQCL, after the UE receives the initial higher layer configuration of the multiple TCI state and before receiving the activation command, the UE shall assume that the DM-RS port of the PDSCH of the serving cell is QCLed with the following SS/PBCH blocks, for qcl-Type set to 'typeA' and, if qcl-Type set to 'typeD' is available, for qcl-Type set to 'typeD': - SS/PBCH blocks determined within the initial access procedure, or - If the UE transmits multiple PRACHs corresponding to multiple SS/PBCH blocks in the last random access attempt during the latest initial access procedure, the first
  • Provision 3d If the UE is provided with TCI-State_r17 indicating the unified TCI state for the PCell or PSCell, then after X symbols from the last symbol of the first PDCCH reception in the search space set provided by recoverySearchSpaceId and in which the UE detects a DCI format with CRC scrambled by the C-RNTI or MCS-C-RNTI, the UE shall follow the following provisions.
  • the UE shall monitor PDCCH in the entire CORESET and receive PDSCH and aperiodic CSI-RS from the CSI-RS resource set with the same TCI state as the PDCCH and the indicated TCI state for the PDSCH with the following antenna port QCL parameters: -- if there is an antenna port QCL parameter associated with the corresponding index q new , the same antenna port QCL parameter (antenna port QCL parameter A) as that antenna port QCL parameter, or --When the UE transmits multiple PRACHs corresponding to multiple indexes q new in the last random access attempt during the latest random access procedure triggered for beam failure recovery purposes, the same antenna port QCL parameter (antenna port QCL parameter B) as the antenna port QCL parameter associated with the first/last/any periodic CSI-RS resource or SS/PBCH block among the multiple periodic CSI-RS resources or multiple SS/PBCH blocks corresponding to the multiple PRACHs corresponding to the DCI format with CRC scrambled by
  • a PDCCH reception includes two PDCCH candidates from two linked search space sets based on searchSpaceLinking, the last symbol of the PDCCH reception is the last symbol of the later ending PDCCH candidate (of the two PDCCH candidates). If the UE is required to monitor one of the two PDCCH candidates, the PDCCH reception includes the two PDCCH candidates.
  • the UE shall monitor the PDCCH in the entire CORESET using the same antenna port QCL parameter as the antenna port QCL parameter and receive the PDSCH and aperiodic CSI-RS from the CSI-RS resource set with the same TCI state as the PDCCH and the indicated TCI state for the PDSCH.
  • - Transmit the PUCCH, the PUSCH, and the SRS using the same spatial domain filters with the same TCI state as the indicated TCI state for PUCCH and PUSCH using the same spatial domain filters as for the latest PRACH transmission.
  • the UE can use antenna port QCL parameter B (SS/PBCH block B) to receive the PDCCH after BFR is completed.
  • the UE can use antenna port QCL parameter A (SS/PBCH block A) to receive the PDCCH after BFR is completed.
  • the UE determines the beam of the SSB/CSI-RS corresponding to the first/last/randomly determined (any) reception among the multiple Msg4 receptions received as the default beam for the PDCCH/PDSCH/CSI-RS.
  • the default beam in the example of FIG. 4 above is the beam of SSB#2.
  • the default beam in the example of FIG. 4 above is the beam of SSB#3.
  • the default beam in the example of FIG. 4 above is any one of SSB#1/#2/#3/#4. Multiple Msg4 reception may be interpreted as multiple RAR reception.
  • Provision 1a For CORESETs other than CORESET with index 0, the UE shall follow at least one of the following rules: - If the UE is not provided with the configuration of one or more TCI states for its CORESET via the TCI state lists for PDCCH (tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList) or is provided with the initial configuration of more than one TCI state for its CORESET via tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList but has not received a MAC CE activation command for one of the more than one TCI states, the UE shall assume that the DM-RS antenna port associated to PDCCH reception is QCL'd with the following SS/PBCH blocks: the SS/PBCH block identified by the UE during the initial access procedure (SS/PBCH block A), or If the UE transmits PRACHs corresponding to SS/PBCH blocks in the last
  • the UE shall assume that the DM-RS antenna port associated to PDCCH reception is QCL'd with the following SS/PBCH blocks or CSI-RS resources: SS/PBCH blocks or CSI-RS resources identified by the UE during a random access procedure initiated by a reconfiguration involving the synchronization procedure, or -- If the UE transmits multiple PRACHs corresponding to multiple SS/PBCH blocks or multiple CSI-RSs in the last random access attempt during the most recent random access procedure initiated by reconfiguration involving the synchronization procedure, the SS/PBCH block or CSI-RS for the first/last/any of the multiple PDSCHs with a
  • Provision 1b For a CORESET with index 0, the UE shall follow at least one of the following actions: - If a UE is provided with DLorJoint-TCIState and followUnifiedTCIstate 'enabled' for its CORESET, the UE shall assume that the DM-RS antenna port associated to PDCCH reception is QCL'd with the reference signal provided by the indicated DLorJoint-TCIState.
  • the UE shall assume that the DM-RS antenna ports associated to PDCCH reception in its CORESET are QCL'd with the following reference signals: -- if there is one or more DL RSs configured with a TCI state and that TCI state is indicated by a MAC CE Activation Command for that CORESET, then that DL RS, or - if no MAC CE Activation Command indicating a TCI state for the CORESET has been received after the most recent random access procedure not initiated by a PDCCH order triggering a CFRA procedure, the SS/PBCH blocks identified by the UE during the most recent random access procedure, or If no MAC CE Activation Command indicating a TCI state for the CORESET has been received after the latest random access procedure not initiated by a PDCCH order triggering a CFRA procedure, if the UE transmits PRACHs corresponding to SS/PBCH blocks in the last random access attempt during the latest random access procedure, the SS/PBCH block for the first/last/any
  • Provision 2a After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState and before the application of an indicated TCI state from the configured TCI states, the UE shall assume that the DM-RS of PDSCH, the DM-RS of PDCCH, and the CSI-RS for which the indicated TCI state applies are QCL'd with the following SS/PBCH blocks: - SS/PBCH blocks identified by the UE during the initial access procedure, or - If the UE transmits multiple PRACHs corresponding to multiple SS/PBCH blocks in the last random access attempt during the latest initial access procedure, the SS/PBCH block for the first/last/any of the PDSCHs with contention resolution identifiers received by the UE during the latest initial access procedure.
  • Provision 2b After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL TCI state (UL-TCIState) and before application of an indicated TCI state from the configured multiple TCI states, the UE shall assume that the UL TX spatial filter for dynamic or configured grant based PUSCH and PUCCH and SRS to which the indicated TCI state applies is the same as the UL TX spatial filter for PUSCH transmission scheduled by the RAR UL grant during the initial access procedure.
  • the UE After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState as part of a reconfiguration with synchronization procedure, and before the application of an indication TCI state from the configured TCI states, the UE shall assume that the DM-RS of PDSCH, DM-RS of PDCCH and CSI-RS, for which the indication TCI state applies, are QCL'd with the following SS/PBCH blocks or CSI-RS resources: SS/PBCH blocks or CSI-RS resources identified by the UE during a random access procedure initiated by a reconfiguration involving the synchronization procedure, or - If the UE transmits multiple PRACHs corresponding to multiple SS/PBCH blocks or multiple CSI-RSs in the last random access attempt during the latest random access procedure initiated by reconfiguration involving the synchronization procedure, the SS/PBCH block or CSI-RS for the first/last/any of the PDSCHs with a contention resolution identifier received by the UE during the latest random
  • the UE After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState as part of a reconfiguration with synchronization procedure and before application of an indicated TCI state from the configured TCI states, the UE shall assume that the UL TX spatial filter for dynamic or configured grant based PUSCH and PUCCH and SRS, to which the indicated TCI state applies, is the same as the UL TX spatial filter for PUSCH transmission scheduled by a RAR UL grant during the random access procedure initiated by the reconfiguration with synchronization procedure.
  • tci-PresentInDCI is set to 'enabled' or tci-PresentDCI-1-2 is configured for the CORESET scheduling the PDSCH, and if timeDurationForQCL is available, then if the time offset between the reception of the DL DCI and the corresponding PDSCH is greater than or equal to timeDurationForQCL, after the UE receives the initial higher layer configuration of the multiple TCI state and before receiving the activation command, the UE shall assume that the DM-RS port of the PDSCH of the serving cell is QCLed with the following SS/PBCH blocks, for qcl-Type set to 'typeA' and, if qcl-Type set to 'typeD' is available, for qcl-Type set to 'typeD': - SS/PBCH blocks determined within the initial access procedure, or - If the UE transmits multiple PRACHs corresponding to multiple SS/PBCH blocks in the last random access attempt during the latest initial access procedure, the
  • Provision 3d If the UE is provided with TCI-State_r17 indicating the unified TCI state for the PCell or PSCell, then after X symbols from the last symbol of the first PDCCH reception in the search space set provided by recoverySearchSpaceId and in which the UE detects a DCI format with CRC scrambled by the C-RNTI or MCS-C-RNTI, the UE shall follow the following provisions.
  • the UE shall monitor PDCCH in the entire CORESET and receive PDSCH and aperiodic CSI-RS from the CSI-RS resource set with the same TCI state as the PDCCH and the indicated TCI state for the PDSCH with the following antenna port QCL parameters: -- if there is an antenna port QCL parameter associated with the corresponding index q new , the same antenna port QCL parameter (antenna port QCL parameter A) as that antenna port QCL parameter, or --When the UE transmits multiple PRACHs corresponding to multiple indexes q new in the last random access attempt in the latest random access procedure triggered for beam failure recovery purposes, the same antenna port QCL parameter (antenna port QCL parameter B) as the antenna port QCL parameter corresponding to the multiple PRACHs corresponding to the first/last/any of the multiple DCI formats with CRC scrambled by the C-RNTI or MCS-C-RNTI detected by the UE within the search space set provided by recoverySearchSpaceId
  • a PDCCH reception includes two PDCCH candidates from two linked search space sets based on searchSpaceLinking, the last symbol of the PDCCH reception is the last symbol of the later ending PDCCH candidate (of the two PDCCH candidates). If the UE is required to monitor one of the two PDCCH candidates, the PDCCH reception includes the two PDCCH candidates.
  • the UE shall monitor the PDCCH in the entire CORESET using the same antenna port QCL parameter as the antenna port QCL parameter and receive the PDSCH and aperiodic CSI-RS from the CSI-RS resource set with the same TCI state as the PDCCH and the indicated TCI state for the PDSCH.
  • - Transmit the PUCCH, the PUSCH, and the SRS using the same spatial domain filters with the same TCI state as the indicated TCI state for PUCCH and PUSCH using the same spatial domain filters as for the latest PRACH transmission.
  • the UE can use antenna port QCL parameter B (SS/PBCH block B) to receive the PDCCH after BFR is completed.
  • the UE can use antenna port QCL parameter A (SS/PBCH block A) to receive the PDCCH after BFR is completed.
  • a UE transmits multiple PRACHs using different beams corresponding to different SSBs/CSI-RSs within one RACH attempt during the initial access procedure and receives multiple Msg4s for the multiple PRACH transmissions, the UE may follow at least one of the following options:
  • the UE determines a beam that is the same as at least one of the beams for the first/last/randomly determined (any) PRACH transmission among the multiple PRACH transmissions corresponding to the received multiple Msg4s and the first/last/randomly determined (any) Msg3 PUSCH among the multiple Msg3 PUSCHs corresponding to the received multiple Msg4s as a default beam for the PUCCH/PUSCH.
  • the default beam in the example of Figure 4 above is the beam of SSB#1.
  • the default beam in the example of Figure 4 above is the beam of SSB#4.
  • the default beam in the example of Figure 4 above is any one of the beams of SSB#1/#2/#3/#4.
  • Provision 2a After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState and before the application of an indicated TCI state from the configured TCI states, the UE shall assume that the DM-RS of PDSCH, the DM-RS of PDCCH, and the CSI-RS for which the indicated TCI state applies are QCL'd with the following SS/PBCH blocks: - SS/PBCH blocks identified by the UE during the initial access procedure.
  • the UE shall assume that the UL TX spatial filters for dynamic grant or configured grant based PUSCH and PUCCH and SRS, for which the indicated TCI state applies, are the same as the following UL TX spatial filters: - UL TX spatial filter for PUSCH transmissions scheduled by an RAR UL grant during the initial access procedure, or - The UL TX spatial filter for the first/last/any of the PRACH transmissions corresponding to the PDSCH with contention resolution identifier received by the UE, if the UE transmits multiple PRACHs with different spatial filter assumptions in the last random access attempt during the latest initial access procedure.
  • the UE After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState as part of a reconfiguration with synchronization procedure, and before the application of an indication TCI state from the configured TCI states, the UE shall assume that the DM-RS of PDSCH, DM-RS of PDCCH and CSI-RS, for which the indication TCI state applies, are QCL'd with the following SS/PBCH blocks or CSI-RS resources: - SS/PBCH blocks or CSI-RS resources identified by the UE during a random access procedure initiated by a reconfiguration accompanied by the synchronization procedure.
  • the UE After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState as part of a reconfiguration with synchronization procedure, and before the application of an indicated TCI state from the configured TCI states, the UE shall assume that the UL TX spatial filter for dynamic or configured grant based PUSCH and PUCCH and SRS, for which the indicated TCI state applies, is the same as the following UL TX spatial filter: - UL TX spatial filter for PUSCH transmissions scheduled by an RAR UL grant during a random access procedure initiated by a reconfiguration accompanied by its synchronization procedure, or - The UL TX spatial filter for the first/last/any of the PRACH transmissions corresponding to the PDSCH with contention resolution identifier received by the UE, if the UE transmits multiple PRACHs with different spatial filter assumptions within the last random access attempt during the latest random access procedure initiated by the reconfiguration with the synchronization procedure.
  • the UE can be provided with a configuration for PRACH transmission by PRACH-ResourceDedicatedBFR.
  • the UE shall assume the same antenna port QCL parameters associated with q new until the UE receives activation for a TCI state or for at least one of the parameters tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList by higher layers.
  • the UE After the UE detects a DCI format with CRC scrambled by the C-RNTI or MCS-C-RNTI in the search space set provided by recoverySearchSpaceId, the UE continues to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceId until the UE receives a MAC CE activation command for a TCI state or for at least one of the parameters tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList.
  • Provision 3c After 28 symbols from the last symbol of the first PDCCH reception in the search space set provided by recoverySearchSpaceId for the UE to detect a DCI format with CRC scrambled by the C-RNTI or MCS-C-RNTI for the PCell or PSCell and for q0 and q1, the UE shall assume the same antenna port QCL parameters in PDCCH monitoring in the CORESET with index 0 as the antenna port QCL parameters associated with index qnew .
  • Provision 3d If the UE is provided with TCI-State_r17 indicating the unified TCI state for the PCell or PSCell, then after X symbols from the last symbol of the first PDCCH reception in the search space set provided by recoverySearchSpaceId and in which the UE detects a DCI format with CRC scrambled by the C-RNTI or MCS-C-RNTI, the UE shall follow the following provisions.
  • the UE shall monitor PDCCH in the entire CORESET and receive PDSCH and aperiodic CSI-RS from the CSI-RS resource set with the same TCI state as the PDCCH and the indicated TCI state for the PDSCH with the following antenna port QCL parameters: -- the same antenna port QCL parameter as the antenna port QCL parameter associated with the corresponding index q new , if there is one; or -- In the case of transmitting multiple PRACHs using different spatial filter assumptions within the last random access attempt in the latest random access procedure triggered for beam obstruction recovery purposes, the same spatial domain filter as the spatial domain filter for the first/last/any of the multiple PRACH transmissions for PDSCH with a contention resolution identifier or a PDCCH indicating successful random access received by the UE.
  • a PDCCH reception includes two PDCCH candidates from two linked search space sets based on searchSpaceLinking, the last symbol of the PDCCH reception is the last symbol of the later ending PDCCH candidate (of the two PDCCH candidates). If the UE is required to monitor one of the two PDCCH candidates, the PDCCH reception includes the two PDCCH candidates.
  • the UE shall monitor the PDCCH in the entire CORESET using the same antenna port QCL parameter as the antenna port QCL parameter and receive the PDSCH and aperiodic CSI-RS from the CSI-RS resource set with the same TCI state as the PDCCH and the indicated TCI state for the PDSCH.
  • the UE transmits its PUCCH, its PUSCH, and SRS using the same spatial domain filters with the same TCI state as the indicated TCI state for PUCCH and PUSCH using the following spatial domain filters: --the same spatial domain filter as the spatial domain filter for the most recent PRACH transmission, or -- If the UE transmits multiple PRACHs using different spatial filter assumptions within the last random access attempt in the latest random access procedure triggered for beam obstruction recovery purposes, the same spatial domain filter as the spatial domain filter for the first/last/any of the multiple PRACH transmissions for PDSCH with a contention resolution identifier or a PDCCH indicating random access success received by the UE.
  • the UE determines a beam that is the same as at least one of the beams for the PRACH transmission corresponding to the first/last/randomly determined (any) Msg 4 received and the Msg 3 PUSCH corresponding to the first/last/randomly determined (any) Msg 4 received as the default beam for the PUCCH/PUSCH.
  • the default beam in the example of Figure 4 above is the beam of SSB#2.
  • the default beam in the example of Figure 4 above is the beam of SSB#3.
  • the default beam in the example of Figure 4 above is any one of the beams of SSB#1/#2/#3/#4.
  • Provision 2a After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState and before the application of an indicated TCI state from the configured TCI states, the UE shall assume that the DM-RS of PDSCH, the DM-RS of PDCCH, and the CSI-RS for which the indicated TCI state applies are QCL'd with the following SS/PBCH blocks: - SS/PBCH blocks identified by the UE during the initial access procedure.
  • the UE shall assume that the UL TX spatial filters for dynamic grant or configured grant based PUSCH and PUCCH and SRS, for which the indicated TCI state applies, are the same as the following UL TX spatial filters: - UL TX spatial filter for PUSCH transmissions scheduled by an RAR UL grant during the initial access procedure, or - UL TX spatial filter for PRACH transmission (or PUSCH transmission scheduled by RAR UL grant) corresponding to the first/last/any of the PDSCHs with contention resolution identifiers received by the UE, if the UE transmitted multiple PRACHs with different spatial filter assumptions in the last random access attempt during the latest initial access procedure.
  • the UE After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState as part of a reconfiguration with synchronization procedure, and before the application of an indication TCI state from the configured TCI states, the UE shall assume that the DM-RS of PDSCH, DM-RS of PDCCH and CSI-RS, for which the indication TCI state applies, are QCL'd with the following SS/PBCH blocks or CSI-RS resources: - SS/PBCH blocks or CSI-RS resources identified by the UE during a random access procedure initiated by a reconfiguration accompanied by the synchronization procedure.
  • the UE After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState as part of a reconfiguration with synchronization procedure, and before the application of an indicated TCI state from the configured TCI states, the UE shall assume that the UL TX spatial filter for dynamic or configured grant based PUSCH and PUCCH and SRS, for which the indicated TCI state applies, is the same as the following UL TX spatial filter: - UL TX spatial filter for PUSCH transmissions scheduled by an RAR UL grant during a random access procedure initiated by a reconfiguration accompanied by its synchronization procedure, or - If the UE transmits multiple PRACHs with different spatial filter assumptions within the last random access attempt during the latest random access procedure initiated by reconfiguration with the synchronization procedure, the UL TX spatial filter for the PRACH transmission (or PUSCH transmission scheduled by the RAR UL grant) corresponding to the first/last/any PDSCH among the multiple PDSCHs with contention resolution
  • the UE can be provided with a configuration for PRACH transmission by PRACH-ResourceDedicatedBFR.
  • the UE shall assume the same antenna port QCL parameters associated with q new until the UE receives activation for a TCI state or for at least one of the parameters tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList by higher layers.
  • the UE After the UE detects a DCI format with CRC scrambled by the C-RNTI or MCS-C-RNTI in the search space set provided by recoverySearchSpaceId, the UE continues to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceId until the UE receives a MAC CE activation command for a TCI state or for at least one of the parameters tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList.
  • Provision 3b 28 symbols after the last symbol of the first PDCCH reception in the PCell or PSCell within the search space set provided by recoverySearchSpaceId for the UE to detect a DCI format with CRC scrambled by the C-RNTI or MCS-C-RNTI, and until the UE receives an Activation Command for PUCCH-SpatialRelationInfo or is provided with PUCCH-SpatialRelationInfo for a PUCCH resource, the UE shall transmit PUCCH on the same cell as the PRACH transmission with the following parameters: The same spatial filter as for the latest PRACH transmission, or the spatial filter for the PRACH transmission (or PUSCH transmission scheduled by the RAR UL grant) corresponding to the first/last/any PDSCH among the multiple PDSCHs with a contention resolution indicator or a PDCCH indicating random access success received by the UE, if the UE transmits multiple PRACHs with different spatial filter assumptions within the last random access attempt during the latest random access procedure triggered for beam obstruction recovery purposes; - The powers
  • Provision 3c After 28 symbols from the last symbol of the first PDCCH reception in the search space set provided by recoverySearchSpaceId for the UE to detect a DCI format with CRC scrambled by the C-RNTI or MCS-C-RNTI for the PCell or PSCell and for q0 and q1, the UE shall assume the same antenna port QCL parameters in PDCCH monitoring in the CORESET with index 0 as the antenna port QCL parameters associated with index qnew .
  • Provision 3d If the UE is provided with TCI-State_r17 indicating the unified TCI state for the PCell or PSCell, then after X symbols from the last symbol of the first PDCCH reception in the search space set provided by recoverySearchSpaceId and in which the UE detects a DCI format with CRC scrambled by the C-RNTI or MCS-C-RNTI, the UE shall follow the following provisions.
  • the UE shall monitor PDCCH in the entire CORESET and receive PDSCH and aperiodic CSI-RS from the CSI-RS resource set with the same TCI state as the PDCCH and the indicated TCI state for the PDSCH with the following antenna port QCL parameters: -- the same antenna port QCL parameter as the antenna port QCL parameter associated with the corresponding index q new , if there is one; or -- In the case of transmitting multiple PRACHs using different spatial filter assumptions within the last random access attempt in the latest random access procedure triggered for beam obstruction recovery purposes, the same spatial domain filter as the spatial domain filter for the PRACH transmission (or the PUSCH transmission scheduled by the RAR UL grant) corresponding to the first/last/any PDSCH among the multiple PDSCHs received by the UE with a contention resolution identifier or a PDCCH indicating random access success.
  • a PDCCH reception includes two PDCCH candidates from two linked search space sets based on searchSpaceLinking, the last symbol of the PDCCH reception is the last symbol of the later ending PDCCH candidate (of the two PDCCH candidates). If the UE is required to monitor one of the two PDCCH candidates, the PDCCH reception includes the two PDCCH candidates.
  • the UE shall monitor the PDCCH in the entire CORESET using the same antenna port QCL parameter as the antenna port QCL parameter and receive the PDSCH and aperiodic CSI-RS from the CSI-RS resource set with the same TCI state as the PDCCH and the indicated TCI state for the PDSCH.
  • the UE transmits its PUCCH, its PUSCH, and SRS using the same spatial domain filters with the same TCI state as the indicated TCI state for PUCCH and PUSCH using the following spatial domain filters: --the same spatial domain filter as the spatial domain filter for the most recent PRACH transmission, or -- If the UE transmits multiple PRACHs using different spatial filter assumptions within the last random access attempt in the latest random access procedure triggered for beam failure recovery purposes, the same spatial domain filter as the spatial domain filter for the PRACH transmission (or the PUSCH transmission scheduled by the RAR UL grant) corresponding to the first/last/any PDSCH among the multiple PDSCHs received by the UE with a contention resolution identifier or a PDCCH indicating random access success.
  • the UE determines a beam that is the same as at least one of the beams for the PUCCH/PUSCH scheduled by the first/last/randomly determined (any) RAR UL grant among the multiple RAR UL grants (multiple RARs) corresponding to the received multiple Msg 4s and the PRACH transmission corresponding to the first/last/randomly determined (any) RAR UL grant among the multiple RAR UL grants (multiple RARs) corresponding to the received multiple Msg 4s as a default beam for the PUCCH/PUSCH.
  • Provision 2a After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState and before the application of an indicated TCI state from the configured TCI states, the UE shall assume that the DM-RS of PDSCH, the DM-RS of PDCCH, and the CSI-RS for which the indicated TCI state applies are QCL'd with the following SS/PBCH blocks: - SS/PBCH blocks identified by the UE during the initial access procedure.
  • the UE shall assume that the UL TX spatial filters for dynamic grant or configured grant based PUSCH and PUCCH and SRS, for which the indicated TCI state applies, are the same as the following UL TX spatial filters: - UL TX spatial filter for PUSCH transmissions scheduled by an RAR UL grant during the initial access procedure, or - UL TX spatial filter for a PUSCH transmission (or a PRACH transmission corresponding to that RAR UL grant) scheduled by the first/last/any of the RAR UL grants corresponding to the PDSCHs with contention resolution identifiers received by the UE, if the UE transmits multiple PRACHs using different spatial filter assumptions within the last random access attempt during the latest initial access procedure.
  • the UE After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState as part of a reconfiguration with synchronization procedure, and before the application of an indication TCI state from the configured TCI states, the UE shall assume that the DM-RS of PDSCH, DM-RS of PDCCH and CSI-RS, for which the indication TCI state applies, are QCL'd with the following SS/PBCH blocks or CSI-RS resources: - SS/PBCH blocks or CSI-RS resources identified by the UE during a random access procedure initiated by a reconfiguration accompanied by the synchronization procedure.
  • the UE After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState as part of a reconfiguration with synchronization procedure, and before the application of an indicated TCI state from the configured TCI states, the UE shall assume that the UL TX spatial filter for dynamic or configured grant based PUSCH and PUCCH and SRS, for which the indicated TCI state applies, is the same as the following UL TX spatial filter: - UL TX spatial filter for PUSCH transmissions scheduled by an RAR UL grant during a random access procedure initiated by a reconfiguration accompanied by its synchronization procedure, or - If the UE transmits multiple PRACHs using different spatial filter assumptions within the last random access attempt during the latest random access procedure initiated by reconfiguration with the synchronization procedure, the UL TX spatial filter for a PUSCH transmission (or a PRACH transmission corresponding to that RAR UL grant) scheduled by the first/last/any of the RAR UL grants corresponding to
  • the UE can be provided with a configuration for PRACH transmission by PRACH-ResourceDedicatedBFR.
  • the UE shall assume the same antenna port QCL parameters associated with q new until the UE receives activation for a TCI state or for at least one of the parameters tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList by higher layers.
  • the UE After the UE detects a DCI format with CRC scrambled by the C-RNTI or MCS-C-RNTI in the search space set provided by recoverySearchSpaceId, the UE continues to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceId until the UE receives a MAC CE activation command for a TCI state or for at least one of the parameters tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList.
  • Provision 3c After 28 symbols from the last symbol of the first PDCCH reception in the search space set provided by recoverySearchSpaceId for the UE to detect a DCI format with CRC scrambled by the C-RNTI or MCS-C-RNTI for the PCell or PSCell and for q0 and q1, the UE shall assume the same antenna port QCL parameters in PDCCH monitoring in the CORESET with index 0 as the antenna port QCL parameters associated with index qnew .
  • Provision 3d If the UE is provided with TCI-State_r17 indicating the unified TCI state for the PCell or PSCell, then after X symbols from the last symbol of the first PDCCH reception in the search space set provided by recoverySearchSpaceId and in which the UE detects a DCI format with CRC scrambled by the C-RNTI or MCS-C-RNTI, the UE shall follow the following provisions.
  • the UE shall monitor PDCCH in the entire CORESET and receive PDSCH and aperiodic CSI-RS from the CSI-RS resource set with the same TCI state as the PDCCH and the indicated TCI state for the PDSCH with the following antenna port QCL parameters: -- the same antenna port QCL parameter as the antenna port QCL parameter associated with the corresponding index q new , if there is one; or -- In the case of transmitting multiple PRACHs using different spatial filter assumptions within the last random access attempt in the latest random access procedure triggered for beam failure recovery purposes, the same spatial domain filter as the spatial domain filter for the PUSH transmission (or the PRACH transmission corresponding to that RAR UL grant) scheduled by the first/last/any RAR UL grant among the multiple RAR UL grants corresponding to multiple PDSCHs received by the UE, accompanied by a contention resolution identifier or a PDCCH indicating successful random access.
  • a PDCCH reception includes two PDCCH candidates from two linked search space sets based on searchSpaceLinking, the last symbol of the PDCCH reception is the last symbol of the later ending PDCCH candidate (of the two PDCCH candidates). If the UE is required to monitor one of the two PDCCH candidates, the PDCCH reception includes the two PDCCH candidates.
  • the UE shall monitor the PDCCH in the entire CORESET using the same antenna port QCL parameter as the antenna port QCL parameter and receive the PDSCH and aperiodic CSI-RS from the CSI-RS resource set with the same TCI state as the PDCCH and the indicated TCI state for the PDSCH.
  • the UE transmits its PUCCH, its PUSCH, and SRS using the same spatial domain filters with the same TCI state as the indicated TCI state for PUCCH and PUSCH using the following spatial domain filters: --the same spatial domain filter as the spatial domain filter for the most recent PRACH transmission, or -- If the UE transmits multiple PRACHs using different spatial filter assumptions within the last random access attempt in the latest random access procedure triggered for beam failure recovery purposes, the same spatial domain filter as the spatial domain filter for the PUSH transmission (or the PRACH transmission corresponding to that RAR UL grant) scheduled by the first/last/any RAR UL grant among the multiple RAR UL grants corresponding to multiple PDSCHs received by the UE, accompanied by a contention resolution identifier or a PDCCH indicating successful random access.
  • the UE can appropriately determine the default beam in case 1.
  • a UE may follow at least one of the following options.
  • the UE monitors the RAR within the determined RAR window using the same beam as the first/last received beam among the multiple SSB/CSI-RS receptions associated with the multiple PRACH transmissions.
  • the RAR monitoring beam in the example of Figure 5 above is the beam of SSB #1.
  • the RAR monitoring beam in the example of Figure 5 above is the beam of SSB #4.
  • the UE monitors the RAR using different beams in different monitoring occasions (MOs) within the determined RAR window according to a rule.
  • MOs monitoring occasions
  • a UE may follow at least one of the following options.
  • the Msg3 transmission beam may be specified by a new field or a reserved bit in the RAR, which is explicitly specified by the RAR UL grant, to specify one of multiple PRACH transmission beams.
  • '00' may indicate the UL transmission beam for the first PRACH transmission
  • '01' may indicate the UL transmission beam for the second PRACH transmission
  • '10' may indicate the UL transmission beam for the third PRACH transmission
  • '11' may indicate the UL transmission beam for the fourth PRACH transmission
  • the specified beam may be used for the Msg3 transmission.
  • the Msg3 transmission beam is implicitly determined based on the beam of the monitored/received RAR. If the UE successfully monitors the RAR using the beam of the SSB/CSI-RS corresponding to the 1st/2nd/3rd/4th PRACH transmission, the UE may transmit Msg3 using the same UL transmission beam as the UL transmission beam of that PRACH transmission.
  • the Msg3 transmission beam is implicitly determined based on the RA-RNTI of the monitored/received RAR. If the UE successfully monitors the RAR using the RA-RNTI calculated based on the 1st/2nd/3rd/4th PRACH transmission, the UE may transmit Msg3 using the same UL transmission beam as the UL transmission beam of that PRACH transmission.
  • a UE may follow at least one of the following options.
  • the Msg4 monitoring beam is the same beam used for monitoring the (detected) RAR.
  • the beam on which the UE successfully monitors/detects the RAR may be used for monitoring Msg4.
  • the Msg4 monitoring beam is explicitly indicated by the RAR.
  • a new field or reserved bit in the RAR may indicate monitoring beams for multiple Msg4s.
  • a new field or reserved bit in the RAR may indicate one beam of multiple SSB/CSI-RSs for multiple PRACH transmissions. For example, '00' indicates SSB/CSI-RS for the first PRACH transmission, '01' indicates SSB/CSI-RS for the second PRACH transmission, '10' indicates SSB/CSI-RS for the third PRACH transmission, and '11' indicates SSB/CSI-RS for the fourth PRACH transmission, and the beam of the indicated SSB/CSI-RS may be used for Msg4 monitoring.
  • the Msg4 monitoring beam is implicitly determined based on the RA-RNTI of the monitored/received RAR. If the UE successfully monitors the RAR using the RA-RNTI calculated based on the 1st/2nd/3rd/4th PRACH transmission, the UE may monitor Msg4 using the beam of SSB/CSI-RS for that PRACH transmission.
  • -Embodiment #2-4 DL default beam after RA If a UE is expected to transmit multiple PRACHs using different beams corresponding to different SSB/CSI-RS within one RACH attempt during an initial access procedure and to receive only one RAR for the multiple PRACH transmissions, the UE may follow at least one of the following options.
  • the UE determines the default beam for PDCCH/PDSCH/CSI-RS (DL default beam) to be the same beam used for monitoring the (detected) RA.
  • the UE determines the default beam for PDCCH/PDSCH/CSI-RS as the beam explicitly or implicitly indicated by the RAR.
  • the indication may follow several options:
  • a new field or reserved bit in the RAR may indicate a default beam for PDCCH/PDSCH/CSI-RS after RA completion.
  • a new field or reserved bit in the RAR may indicate one beam of multiple SSB/CSI-RS for multiple PRACH transmissions.
  • '00' represents the SSB/CSI-RS for the first PRACH transmission
  • '01' represents the SSB/CSI-RS for the second PRACH transmission
  • '10' represents the SSB/CSI-RS for the third PRACH transmission
  • '11' represents the SSB/CSI-RS for the fourth PRACH transmission
  • the beam of the indicated SSB/CSI-RS may be used as the default beam for the PDCCH/PDSCH/CSI-RS after RA completion.
  • the field/bit for indicating the default beam for PDCCH/PDSCH/CSI-RS after RA completion may be the same as the field/bit for at least one of the Msg3 transmission beam in option 1 of embodiment #2-2 and the Msg4 monitoring beam in embodiment #2-3.
  • Option 2-2 Implicit indication based on RA-RNTI for detected RAR If the UE successfully monitors an RAR using the RA-RNTI calculated based on the first/second/third/fourth PRACH transmission, the beam of the SSB/CSI-RS for that PRACH transmission may be used as the default beam for the PDCCH/PDSCH/CSI-RS after RA completion.
  • the UE determines the default beam for PDCCH/PDSCH/CSI-RS to be the same beam used for monitoring the (detected) Msg4.
  • the UE determines the default beam for PDCCH/PDSCH/CSI-RS to be the beam explicitly indicated by Msg 4.
  • the indication of the default beam for PDCCH/PDSCH/CSI-RS after RA completion may follow several options:
  • the indication may be a new field or an existing field (reinterpretation of an existing field) of DCI format 1_0 with CRC scrambled by the TC-RNTI, DCI scheduling a PDSCH including a UE contention resolution identifier.
  • the indication may be a PDSCH including a UE contention resolution identifier and a default beam indication.
  • the DCI format 1_0 or the PDSCH may indicate the beam of one of the multiple SSB/CSI-RS for multiple PRACH transmissions. For example, '00' indicates the SSB/CSI-RS for the first PRACH transmission, '01' indicates the SSB/CSI-RS for the second PRACH transmission, '10' indicates the SSB/CSI-RS for the third PRACH transmission, and '11' indicates the SSB/CSI-RS for the fourth PRACH transmission, and the beam of the indicated SSB/CSI-RS may be used as the default beam for the PDCCH/PDSCH/CSI-RS after RA completion.
  • -Embodiment #2-5 UL default beam after RA If a UE is expected to transmit multiple PRACHs using different beams corresponding to different SSBs/CSI-RS within one RACH attempt during an initial access procedure and to receive only one RAR for the multiple PRACH transmissions, the UE may follow at least one of the following options.
  • the UE determines the default beam for PUCCH/PUSCH (UL default beam) to be the same beam as the beam for Msg3 transmission.
  • the UL TX spatial filter for a PRACH transmission (or a PUSCH transmission scheduled by an RAR UL grant) corresponding to the first/last/any of the multiple PDSCHs with a contention resolution identifier received by the UE" may be read as "the same spatial transmit filter as the spatial transmit filter for a PUSCH transmission scheduled by an RAR UL grant during the initial access procedure/random access procedure.”
  • the UE determines the default beam for PUCCH/PUSCH as the beam explicitly or implicitly indicated by the RAR.
  • the indication may follow several options:
  • a new field or reserved bit in the RAR may indicate a default beam for PUCCH/PUSCH after RA completion.
  • a new field or reserved bit in the RAR may indicate one beam of multiple SSB/CSI-RS for multiple PRACH transmissions. For example, '00' represents SSB/CSI-RS for the first PRACH transmission, '01' represents SSB/CSI-RS for the second PRACH transmission, '10' represents SSB/CSI-RS for the third PRACH transmission, and '11' represents SSB/CSI-RS for the fourth PRACH transmission, and the beam of the indicated SSB/CSI-RS may be used as the default beam for PUCCH/PUSCH after RA completion.
  • Option 2-2 Implicit indication based on RA-RNTI for detected RAR If the UE successfully monitors the RAR using the RA-RNTI calculated based on the first/second/third/fourth PRACH transmission, the SSB/CSI-RS beam for that PRACH transmission may be used as the default beam for PUCCH/PUSCH after RA completion.
  • the UE determines the default beam for PUCCH/PUSCH to be the beam explicitly indicated by Msg 4.
  • the indication of the default beam for PUCCH/PUSCH after RA completion may follow several options:
  • the indication may be a new field or an existing field (reinterpretation of an existing field) of DCI format 1_0 with CRC scrambled by the TC-RNTI, DCI scheduling a PDSCH including a UE contention resolution identifier.
  • the indication may be a PDSCH including a UE contention resolution identifier and a default beam indication.
  • the DCI format 1_0 or the PDSCH may indicate one of multiple UL transmission beams for multiple PRACH transmissions. For example, '00' indicates the UL transmission beam for the first PRACH transmission, '01' indicates the UL transmission beam for the second PRACH transmission, '10' indicates the SSB/CSI-RS for the third PRACH transmission, and '11' indicates the UL transmission beam for the fourth PRACH transmission, and the beam of the indicated SSB/CSI-RS may be used as the default beam for PUCCH/PUSCH after RA completion.
  • the UE determines the default beam for PUCCH/PUSCH to be the same beam used for monitoring the (detected) RAR or Msg4.
  • the beam on which the UE successfully monitors/detects RAR/Msg4 may be used to determine the default beam for PUCCH/PUSCH. If the UE successfully monitors/detects RAR/Msg4 using the same UL transmission beam corresponding to the first/second/third/fourth PRACH transmission, the UL transmission beam for that PRACH transmission may be used as the default beam for PUCCH/PUSCH after RA completion.
  • the UE can appropriately determine the default beam in case 2.
  • -Embodiment #3-1 UL default beam after RA If a UE transmits multiple PRACHs using different beams corresponding to the same SSB/CSI-RS within one RACH attempt during the initial access procedure and receives multiple Msg 4s for the multiple PRACH transmissions, the UE may follow at least one of options 1 to 3 in embodiment #1-2.
  • the UE can appropriately determine the default beam in case 3.
  • -Embodiment #4-1 Msg3 transmission beam during RA If a UE is expected to transmit multiple PRACHs using different beams corresponding to the same SSB/CSI-RS within one RACH attempt during the initial access procedure and to receive only one RAR for the multiple PRACH transmissions, the UE may follow at least one of options 1 and 3 in embodiment #2-2.
  • -Embodiment #4-2 UL default beam after RA If a UE is expected to transmit multiple PRACHs using different beams corresponding to the same SSB/CSI-RS within one RACH attempt during the initial access procedure and to receive only one RAR for the multiple PRACH transmissions, the UE may follow at least one of options 1 to 3 in embodiment #2-5.
  • the UE can appropriately determine the default beam in case 4.
  • any information may be notified to the UE (from a network (NW) (e.g., a base station (BS))) (in other words, any information is received from the BS by the UE) using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal/channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.
  • NW network
  • BS base station
  • the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader that is not specified in existing standards.
  • LCID Logical Channel ID
  • the notification When the notification is made by a DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.
  • RNTI Radio Network Temporary Identifier
  • CRC Cyclic Redundancy Check
  • notification of any information to the UE in the above-mentioned embodiments may be performed periodically, semi-persistently, or aperiodically.
  • notification of any information from the UE (to the NW) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal/channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.
  • physical layer signaling e.g., UCI
  • higher layer signaling e.g., RRC signaling, MAC CE
  • a specific signal/channel e.g., PUCCH, PUSCH, PRACH, reference signal
  • the MAC CE may be identified by including a new LCID in the MAC subheader that is not specified in existing standards.
  • the notification may be transmitted using PUCCH or PUSCH.
  • notification of any information from the UE may be performed periodically, semi-persistently, or aperiodically.
  • At least one of the above-mentioned embodiments may be applied when a specific condition is satisfied, which may be specified in a standard or may be notified to a UE/BS using higher layer signaling/physical layer signaling.
  • At least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.
  • the specific UE capabilities may indicate at least one of the following: - Supporting specific processing/operations/control/information for at least one of the above embodiments.
  • the UE supports multiple PRACH transmissions using different transmission beams corresponding to different SSBs/CSI-RS.
  • the UE supports multiple PRACH transmissions using different transmission beams corresponding to the same SSB/CSI-RS.
  • the UE supports separate RAR/Msg3/Msg4 for multiple PRACH transmissions using different transmission beams corresponding to different SSBs/CSI-RS.
  • the UE supports a single RAR for multiple PRACH transmissions using different transmission beams corresponding to different SSBs/CSI-RS.
  • the UE supports separate RAR/Msg3/Msg4 for multiple PRACH transmissions using different transmission beams corresponding to the same SSB/CSI-RS.
  • the UE supports a single RAR for multiple PRACH transmissions using different transmission beams corresponding to the same SSB/CSI-RS.
  • the UE supports RAR to indicate Msg3 transmission beam (or Msg4 monitoring beam) for the case of multiple PRACH transmissions using different transmission beams.
  • the UE supports RAR/Msg4 to indicate the default beam for PDCCH/PDSCH/CSI-RS for the case of multiple PRACH transmissions using different transmission beams corresponding to different SSBs/CSI-RS.
  • the UE supports RAR/Msg4 to indicate the default beam for PUCCH/PUSCH for the case of multiple PRACH transmissions using different transmission beams.
  • the above-mentioned specific UE capabilities may be capabilities that are applied across all frequencies (commonly regardless of frequency), capabilities per frequency (e.g., one or a combination of a cell, band, band combination, BWP, component carrier, etc.), capabilities per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities per subcarrier spacing (SubCarrier Spacing (SCS)), or capabilities per Feature Set (FS) or Feature Set Per Component-carrier (FSPC).
  • FR1 Frequency Range 1
  • FR2 FR2, FR3, FR4, FR5, FR2-1, FR2-2
  • SCS subcarrier Spacing
  • FS Feature Set
  • FSPC Feature Set Per Component-carrier
  • the specific UE capabilities may be capabilities that are applied across all duplexing methods (commonly regardless of the duplexing method), or may be capabilities for each duplexing method (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).
  • TDD Time Division Duplex
  • FDD Frequency Division Duplex
  • At least one of the above-mentioned embodiments may be applied when the UE configures/activates/triggers specific information related to the above-mentioned embodiments (or performs the operations of the above-mentioned embodiments) by higher layer signaling/physical layer signaling.
  • the specific information may be information indicating that the operations of the above-mentioned embodiments are enabled, any RRC parameters for a specific release (e.g., Rel. 18/19), etc.
  • the UE may, for example, apply Rel. 15/16 operations.
  • PRACH Physical Random Access Channel
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • Appendix 4 The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein the controller receives one or more random access responses to the transmission of the plurality of PRACHs, and determines the spatial domain transmit filter based on a particular random access response among the one or more random access responses.
  • a receiver for receiving a beam obstruction recovery setting A terminal having a control unit that determines antenna port pseudo co-location parameters for monitoring a physical downlink control channel (PDCCH) for at least one of a plurality of PRACHs corresponding to a plurality of spatial domain transmit filters for the beam failure recovery, based on any one of a specific PRACH in a specific random access procedure, a downlink control information (DCI) format detected in a search space for the beam failure recovery, a random access response in the specific random access procedure, a physical uplink shared channel (PUSCH) scheduled by the random access response, and a physical downlink shared channel (PDSCH) with a contention resolution identifier in the specific random access procedure.
  • DCI downlink control information
  • [Appendix 2] 2. The terminal of claim 1, wherein the control unit monitors one or more random access responses for the transmission of the plurality of PRACHs.
  • [Appendix 3] 3. The terminal according to claim 1, wherein the control unit monitors one random access response for the plurality of PRACH transmissions.
  • [Appendix 4] The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein the control unit determines the antenna port quasi-co-location parameter based on either a specific reference signal among a plurality of reference signals for reception of a DCI format for the transmission of the plurality of PRACHs or a DCI format among one or more DCI formats for the transmission of the plurality of PRACHs.
  • PRACH Physical Random Access Channel
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • the terminal monitors one random access response for the plurality of PRACH transmissions.
  • the control unit determines the quasi-co-location assumption based on either a specific reference signal among a plurality of reference signals for one PDSCH with a contention resolution identifier for the transmission of the plurality of PRACHs, or a specific PDSCH among one or more PDSCHs with a contention resolution identifier for the transmission of the plurality of PRACHs.
  • the terminal according to any one of Supplementary Note 1 to Supplementary Note 3.
  • Wired communication system A configuration of a wireless communication system according to an embodiment of the present disclosure will be described below.
  • communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination of these.
  • FIG. 8 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment.
  • the wireless communication system 1 (which may simply be referred to as system 1) may be a system that realizes communication using Long Term Evolution (LTE) specified by the Third Generation Partnership Project (3GPP), 5th generation mobile communication system New Radio (5G NR), or the like.
  • LTE Long Term Evolution
  • 3GPP Third Generation Partnership Project
  • 5G NR 5th generation mobile communication system New Radio
  • the wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)).
  • MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.
  • RATs Radio Access Technologies
  • MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.
  • 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 (MN), and the NR base station (gNB) is the secondary node (SN).
  • the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.
  • the wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (e.g., dual connectivity in which both the MN and SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).
  • dual connectivity in which both the MN and SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).
  • gNBs NR base stations
  • N-DC Dual Connectivity
  • the wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are arranged within the macrocell C1 and form a small cell C2 that is narrower than the macrocell C1.
  • a user terminal 20 may be located within at least one of the cells. The arrangement and number of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.
  • the user terminal 20 may be connected to at least one of the multiple base stations 10.
  • the user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).
  • 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 for example, FR1 may correspond to a higher frequency band than FR2.
  • the user terminal 20 may communicate using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.
  • TDD Time Division Duplex
  • FDD Frequency Division Duplex
  • the multiple base stations 10 may be connected by wire (e.g., optical fiber conforming to the Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (e.g., NR communication).
  • wire e.g., optical fiber conforming to the Common Public Radio Interface (CPRI), X2 interface, etc.
  • NR communication e.g., NR communication
  • base station 11 which corresponds to the upper station
  • IAB Integrated Access Backhaul
  • base station 12 which corresponds to a relay station
  • the base station 10 may be connected to the core network 30 directly or via another base station 10.
  • the core network 30 may include at least one of, for example, an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), etc.
  • EPC Evolved Packet Core
  • 5GCN 5G Core Network
  • NGC Next Generation Core
  • the core network 30 may include network functions (Network Functions (NF)) such as, for example, a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM).
  • NF Network Functions
  • UPF User Plane Function
  • AMF Access and Mobility management Function
  • SMF Session Management Function
  • UDM Unified Data Management
  • AF Application Function
  • DN Data Network
  • LMF Location Management Function
  • OAM Operation, Administration and Maintenance
  • the user terminal 20 may be a terminal that supports at least one of the communication methods such as LTE, LTE-A, and 5G.
  • a wireless access method based on Orthogonal Frequency Division Multiplexing may be used.
  • OFDM Orthogonal Frequency Division Multiplexing
  • CP-OFDM Cyclic Prefix OFDM
  • DFT-s-OFDM Discrete Fourier Transform Spread OFDM
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • the radio access method may also be called a waveform.
  • other radio access methods e.g., other single-carrier transmission methods, other multi-carrier transmission methods
  • a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as the downlink channel.
  • PDSCH Physical Downlink Shared Channel
  • PBCH Physical Broadcast Channel
  • PDCCH Physical Downlink Control Channel
  • an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), etc. may be used as an uplink channel.
  • PUSCH Physical Uplink Shared Channel
  • PUCCH Physical Uplink Control Channel
  • PRACH Physical Random Access Channel
  • SIB System Information Block
  • PDSCH User data, upper layer control information, System Information Block (SIB), etc.
  • SIB System Information Block
  • PUSCH User data, upper layer control information, etc.
  • MIB Master Information Block
  • PBCH Physical Broadcast Channel
  • Lower layer control information may be transmitted by the PDCCH.
  • the lower layer control information may include, for example, downlink control information (Downlink Control Information (DCI)) including scheduling information for at least one of the PDSCH and the PUSCH.
  • DCI Downlink Control Information
  • the DCI for scheduling the PDSCH may be called a DL assignment or DL DCI
  • the DCI for scheduling the PUSCH may be called a UL grant or UL DCI.
  • the PDSCH may be interpreted as DL data
  • the PUSCH may be interpreted as UL data.
  • a control resource set (COntrol REsource SET (CORESET)) and a search space may be used to detect the PDCCH.
  • the CORESET corresponds to the resources to search for DCI.
  • the search space corresponds to the search region and search method of PDCCH candidates.
  • One CORESET may be associated with one or multiple search spaces. The UE may monitor the CORESET associated with a search space based on the search space configuration.
  • a 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 the terms “search space,” “search space set,” “search space setting,” “search space set setting,” “CORESET,” “CORESET setting,” etc. in this disclosure may be read as interchangeable.
  • the PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK/NACK, etc.), and a scheduling request (SR).
  • UCI uplink control information
  • CSI channel state information
  • HARQ-ACK Hybrid Automatic Repeat reQuest ACKnowledgement
  • ACK/NACK ACK/NACK
  • SR scheduling request
  • the PRACH may transmit a random access preamble for establishing a connection with a cell.
  • downlink, uplink, etc. may be expressed without adding "link.”
  • various channels may be expressed without adding "Physical” to the beginning.
  • a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted.
  • a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.
  • 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 an SS (PSS, SSS) and a PBCH (and a DMRS for PBCH) may be called an SS/PBCH block, an SS Block (SSB), etc.
  • the SS, SSB, etc. may also be called a reference signal.
  • a measurement reference signal Sounding Reference Signal (SRS)
  • a demodulation reference signal DMRS
  • UL-RS uplink reference signal
  • DMRS may also be called a user equipment-specific reference signal (UE-specific Reference Signal).
  • the base station 9 is a diagram showing an example of a configuration of a base station according to an embodiment.
  • the base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140 may be provided.
  • this example mainly shows the functional blocks of the characteristic parts of this embodiment, and the base station 10 may also be assumed to have other functional blocks necessary for wireless communication. Some of the processing of each part 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 are described based on a common understanding in the technical field to which this disclosure pertains.
  • the control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc.
  • the control unit 110 may control transmission and reception using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurement, etc.
  • the control unit 110 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 120.
  • the control unit 110 may perform call processing of communication channels (setting, release, etc.), status management of the base station 10, management of radio resources, etc.
  • the transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123.
  • the baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212.
  • the transceiver unit 120 may be composed of a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on a common understanding in the technical field to which the present disclosure relates.
  • the transceiver unit 120 may be configured as an integrated transceiver unit, or may be composed of a transmission unit and a reception unit.
  • the transmission unit may be composed of a transmission processing unit 1211 and an RF unit 122.
  • the reception unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.
  • the transmitting/receiving antenna 130 can be configured as an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.
  • the transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc.
  • the transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.
  • the transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.
  • digital beamforming e.g., precoding
  • analog beamforming e.g., phase rotation
  • the transceiver 120 may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc., on data and control information obtained from the control unit 110, and generate a bit string to be transmitted.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • HARQ retransmission control HARQ retransmission control
  • the transceiver 120 may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
  • transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
  • channel coding which may include error correction coding
  • DFT Discrete Fourier Transform
  • IFFT Inverse Fast Fourier Transform
  • the transceiver unit 120 may perform modulation, filtering, amplification, etc., on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 130.
  • the transceiver unit 120 may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 130.
  • the transceiver 120 may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.
  • reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.
  • FFT Fast Fourier Transform
  • IDFT Inverse Discrete Fourier Transform
  • the transceiver 120 may perform measurements on the received signal.
  • the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal.
  • the measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc.
  • RSRP Reference Signal Received Power
  • RSSI Received Signal Strength Indicator
  • the measurement results may be output to the control unit 110.
  • the transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30 (e.g., network nodes providing NF), other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.
  • devices included in the core network 30 e.g., network nodes providing NF
  • other base stations 10, etc. may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.
  • the transmitter and receiver of the base station 10 in this disclosure may be configured with at least one of the transmitter/receiver 120, the transmitter/receiver antenna 130, and the transmission path interface 140.
  • the transceiver 120 may transmit a transmission configuration for a plurality of physical random access channels (PRACHs) corresponding to the plurality of spatial domain transmission filters, respectively.
  • the controller 110 may determine a spatial domain transmission filter for uplink transmission based on a specific PRACH among the plurality of PRACHs, a random access response, a physical uplink shared channel (PUSCH) scheduled by the random access response, or a physical downlink shared channel (PDSCH) with a contention resolution identifier.
  • PRACHs physical random access channels
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • the transceiver 120 may transmit a beam failure recovery setting.
  • the control unit 110 may determine an antenna port pseudo-co-location parameter for monitoring a physical downlink control channel (PDCCH) for at least one of a plurality of PRACHs corresponding to a plurality of spatial domain transmission filters for the beam failure recovery, based on any one of a specific PRACH in a specific random access procedure, a downlink control information (DCI) format detected in a search space for the beam failure recovery, a random access response in the specific random access procedure, a physical uplink shared channel (PUSCH) scheduled by the random access response, and a physical downlink shared channel (PDSCH) with a contention resolution identifier in the specific random access procedure.
  • PDCCH physical downlink control channel
  • DCI downlink control information
  • the transceiver 120 may transmit a transmission configuration for a plurality of physical random access channels (PRACHs) corresponding to the plurality of spatial domain transmission filters, respectively.
  • the controller 110 may determine a quasi-co-location assumption for downlink reception based on a specific PRACH among the plurality of PRACHs, a random access response, a physical uplink shared channel (PUSCH) scheduled by the random access response, or a physical downlink shared channel (PDSCH) with a contention resolution identifier.
  • PRACHs physical random access channels
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • the user terminal 10 is a diagram showing an example of the configuration of a user terminal according to an embodiment.
  • the user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the control unit 210, the transceiver unit 220, and the transceiver antenna 230 may each include one or more.
  • this example mainly shows the functional blocks of the characteristic parts of this embodiment, and the user terminal 20 may also be assumed to have other functional blocks necessary for wireless communication. Some of the processing of each part 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 are described based on a common understanding in the technical field to which this disclosure pertains.
  • the control unit 210 may control signal generation, mapping, etc.
  • the control unit 210 may control transmission and reception using the transceiver unit 220 and the transceiver antenna 230, measurement, etc.
  • the control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 220.
  • the transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223.
  • the baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212.
  • the transceiver unit 220 may be composed of a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on a common understanding in the technical field to which the present disclosure relates.
  • the transceiver unit 220 may be configured as an integrated transceiver unit, or may be composed of a transmission unit and a reception unit.
  • the transmission unit may be composed of a transmission processing unit 2211 and an RF unit 222.
  • the reception unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.
  • the transmitting/receiving antenna 230 can be configured as an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.
  • the transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc.
  • the transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.
  • the transceiver 220 may form at least one of the transmit beam and receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.
  • digital beamforming e.g., precoding
  • analog beamforming e.g., phase rotation
  • the transceiver 220 may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on the data and control information acquired from the controller 210, and generate a bit string to be transmitted.
  • RLC layer processing e.g., RLC retransmission control
  • MAC layer processing e.g., HARQ retransmission control
  • the transceiver 220 may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
  • transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
  • Whether or not to apply DFT processing may be based on the settings of transform precoding.
  • the transceiver unit 220 transmission processing unit 2211
  • the transceiver unit 220 may perform DFT processing as the above-mentioned transmission processing in order to transmit the channel using a DFT-s-OFDM waveform, and when transform precoding is not enabled, it is not necessary to perform DFT processing as the above-mentioned transmission processing.
  • the transceiver unit 220 may perform modulation, filtering, amplification, etc., on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 230.
  • the transceiver unit 220 may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 230.
  • the transceiver 220 may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.
  • reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.
  • the transceiver 220 may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal.
  • the measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc.
  • the measurement results may be output to the control unit 210.
  • the measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources.
  • the channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources.
  • the measurement unit 223 may derive interference measurements for CSI calculation based on interference measurement resources.
  • the interference measurement resources may be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc.
  • CSI-IM may be called CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS.
  • CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be read as interchangeable.
  • the transmitting unit and receiving unit of the user terminal 20 in this disclosure may be configured by at least one of the transmitting/receiving unit 220 and the transmitting/receiving antenna 230.
  • the transceiver 220 may receive transmission settings for a plurality of physical random access channels (PRACHs) corresponding to the plurality of spatial domain transmission filters, respectively.
  • the controller 210 may determine a spatial domain transmission filter for uplink transmission based on a specific PRACH among the plurality of PRACHs, a random access response, a physical uplink shared channel (PUSCH) scheduled by the random access response, or a physical downlink shared channel (PDSCH) with a contention resolution identifier.
  • PRACHs physical random access channels
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • the control unit 210 may monitor one or more random access responses for the multiple PRACH transmissions.
  • the control unit 210 may monitor one random access response for each of the multiple PRACH transmissions.
  • the control unit 210 may receive one or more random access responses to the transmission of the multiple PRACHs, and determine the spatial domain transmit filter based on a specific random access response from the one or more random access responses.
  • the transceiver unit 220 may receive a beam failure recovery setting.
  • the control unit 210 may determine an antenna port pseudo-co-location parameter for monitoring a physical downlink control channel (PDCCH) for at least one of a plurality of PRACHs corresponding to a plurality of spatial domain transmission filters for the beam failure recovery, based on any one of a specific PRACH in a specific random access procedure, a downlink control information (DCI) format detected in a search space for the beam failure recovery, a random access response in the specific random access procedure, a physical uplink shared channel (PUSCH) scheduled by the random access response, and a physical downlink shared channel (PDSCH) with a contention resolution identifier in the specific random access procedure.
  • PDCCH physical downlink control channel
  • DCI downlink control information
  • the control unit 210 may monitor one or more random access responses for the multiple PRACH transmissions.
  • the control unit 210 may monitor one random access response for each of the multiple PRACH transmissions.
  • the control unit 210 may determine the antenna port quasi-colocation parameters based on either a specific reference signal among a plurality of reference signals for receiving a DCI format for the transmission of the plurality of PRACHs, or a DCI format among one or more DCI formats for the transmission of the plurality of PRACHs.
  • the transceiver unit 220 may receive transmission settings for a plurality of physical random access channels (PRACHs) corresponding to a plurality of spatial domain transmission filters, respectively.
  • the control unit 210 may determine a quasi-co-location assumption for downlink reception based on a specific PRACH among the plurality of PRACHs, a random access response, a physical uplink shared channel (PUSCH) scheduled by the random access response, or a physical downlink shared channel (PDSCH) with a contention resolution identifier.
  • PRACHs physical random access channels
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • the control unit 210 may monitor one or more random access responses for the multiple PRACH transmissions.
  • the control unit 210 may monitor one random access response for each of the multiple PRACH transmissions.
  • the control unit 210 may determine the pseudo-co-location assumption based on either a specific reference signal among multiple reference signals for one PDSCH with a contention resolution identifier for the transmission of the multiple PRACHs, or a specific PDSCH among one or more PDSCHs with a contention resolution identifier for the transmission of the multiple PRACHs.
  • each functional block may be realized using one device that is physically or logically coupled, or may be realized using two or more devices that are physically or logically separated and directly or indirectly connected (for example, using wires, wirelessly, etc.).
  • the functional blocks may be realized by combining the one device or the multiple devices with software.
  • the functions include, but are not limited to, judgement, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment.
  • a functional block (component) that performs the transmission function may be called a transmitting unit, a transmitter, and the like. In either case, as mentioned above, there are no particular limitations on the method of realization.
  • a base station, a user terminal, etc. in one embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure.
  • FIG. 11 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to one embodiment.
  • the above-mentioned base station 10 and user terminal 20 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 terms apparatus, circuit, device, section, unit, etc. may be interpreted as interchangeable.
  • the hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the figures, or may be configured to exclude some of the devices.
  • processor 1001 may be implemented by one or more chips.
  • the functions of the base station 10 and the user terminal 20 are realized, for example, by loading specific software (programs) onto hardware such as the processor 1001 and memory 1002, causing the processor 1001 to perform calculations, control communications via the communication device 1004, and control at least one of the reading and writing of data in the memory 1002 and storage 1003.
  • the processor 1001 for example, runs an operating system to control the entire computer.
  • the processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, registers, etc.
  • CPU central processing unit
  • control unit 110 210
  • transmission/reception unit 120 220
  • etc. may be realized by the processor 1001.
  • the processor 1001 also reads out programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these.
  • the programs used are those that cause a computer to execute at least some of the operations described in the above embodiments.
  • the control unit 110 (210) may be realized by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks.
  • Memory 1002 is a computer-readable recording medium and may be composed of at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), and other suitable storage media. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to one embodiment of the present disclosure.
  • ROM Read Only Memory
  • EPROM Erasable Programmable ROM
  • EEPROM Electrically EPROM
  • RAM Random Access Memory
  • Memory 1002 may also be called a register, cache, main memory, etc.
  • Memory 1002 can store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to one embodiment of the present disclosure.
  • Storage 1003 is a computer-readable recording medium and may be composed of at least one of a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM)), a digital versatile disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium.
  • Storage 1003 may also be referred to as an auxiliary storage device.
  • the communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.
  • the communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., to realize at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • the above-mentioned transmitting/receiving unit 120 (220), transmitting/receiving antenna 130 (230), etc. may be realized by the communication device 1004.
  • the transmitting/receiving unit 120 (220) may be implemented as a transmitting unit 120a (220a) and a receiving unit 120b (220b) that are physically or logically separated.
  • the input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside.
  • the output device 1006 is an output device (e.g., a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that outputs to the outside.
  • the input device 1005 and the output device 1006 may be integrated into one structure (e.g., a touch panel).
  • each device such as the processor 1001 and memory 1002 is connected by a bus 1007 for communicating information.
  • the bus 1007 may be configured using a single bus, or may be configured using different buses between each device.
  • the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using the hardware.
  • the processor 1001 may be implemented using at least one of these pieces of hardware.
  • a channel, a symbol, and a signal may be read as mutually interchangeable.
  • a signal may also be a message.
  • a reference signal may be abbreviated as RS, and may be called a pilot, a pilot signal, or the like depending on the applied standard.
  • a component carrier may also 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 (e.g., 1 ms) that is independent of numerology.
  • the numerology may be a communication parameter that is applied to at least one of the transmission and reception of a signal or channel.
  • the numerology may indicate, for example, at least one of the following: SubCarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame configuration, 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.
  • SCS SubCarrier Spacing
  • TTI Transmission Time Interval
  • 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 consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.).
  • OFDM Orthogonal Frequency Division Multiplexing
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • a slot may also be a time unit based on numerology.
  • a slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot.
  • a PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A.
  • a PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.
  • a radio frame, a subframe, a slot, a minislot, and a symbol all represent time units when transmitting a signal.
  • a different name may be used for a radio frame, a subframe, a slot, a minislot, and a symbol, respectively.
  • the time units such as a frame, a subframe, a slot, a minislot, and a symbol in this disclosure may be read as interchangeable.
  • one subframe may be called a TTI
  • multiple consecutive subframes may be called a TTI
  • one slot or one minislot may be called a TTI.
  • at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms.
  • the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.
  • TTI refers to, for example, the smallest time unit for scheduling in wireless communication.
  • a base station schedules each user terminal by allocating radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) in TTI units.
  • radio resources such as frequency bandwidth and transmission power that can be used by each user terminal
  • the TTI may be a transmission time unit for a channel-coded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc.
  • the time interval e.g., the number of symbols
  • the time interval in which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.
  • one or more TTIs may be the minimum time unit of scheduling.
  • the number of slots (minislots) that constitute the minimum time unit of 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.
  • a TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
  • a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms
  • a short TTI e.g., a shortened TTI, etc.
  • TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.
  • a resource block is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain.
  • the number of subcarriers included in an RB may be the same regardless of numerology, and may be, for example, 12.
  • 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 be one slot, one minislot, one subframe, or one TTI in length.
  • One TTI, one subframe, etc. may each be composed of one or more resource blocks.
  • one or more RBs may be referred to as a physical resource block (Physical RB (PRB)), a sub-carrier group (Sub-Carrier Group (SCG)), a resource element group (Resource Element Group (REG)), a PRB pair, an RB pair, etc.
  • PRB Physical RB
  • SCG sub-carrier Group
  • REG resource element group
  • PRB pair an RB pair, etc.
  • a resource block may be composed of one or more resource elements (REs).
  • REs resource elements
  • one RE may be a radio resource area of one subcarrier and one symbol.
  • a Bandwidth Part which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by an index of the RB relative to a common reference point of the carrier.
  • PRBs may be defined in a BWP and numbered within the BWP.
  • the BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL).
  • BWP UL BWP
  • BWP for DL DL BWP
  • One or more BWPs may be configured for a UE within one carrier.
  • At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal/channel outside the active BWP.
  • BWP bitmap
  • radio frames, subframes, slots, minislots, and symbols 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 subcarriers included in an RB, as well as the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length can be changed in various ways.
  • the information, parameters, etc. described in this disclosure may be represented using absolute values, may be represented using relative values from a predetermined value, or may be represented using other corresponding information.
  • a radio resource 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 formulas and the like using these parameters may differ from those explicitly disclosed in this disclosure.
  • the various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any respect.
  • the information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies.
  • the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
  • information, signals, etc. may be output from a higher layer to a lower layer and/or from a lower layer to a higher layer.
  • Information, signals, etc. may be input/output via multiple network nodes.
  • Input/output information, signals, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. Input/output information, signals, etc. may be overwritten, updated, or added to. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.
  • a specific location e.g., memory
  • Input/output information, signals, etc. may be overwritten, updated, or added to.
  • Output information, signals, etc. may be deleted.
  • Input information, signals, etc. may be transmitted to another device.
  • the 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 performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), etc.), Medium Access Control (MAC) signaling), other signals, or a combination of these.
  • DCI Downlink Control Information
  • UCI Uplink Control Information
  • RRC Radio Resource Control
  • MIB Master Information Block
  • SIB System Information Block
  • MAC Medium Access Control
  • the physical layer signaling may be called Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal), L1 control information (L1 control signal), etc.
  • the RRC signaling may be called an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.
  • the MAC signaling may be notified, for example, using a MAC Control Element (CE).
  • CE MAC Control Element
  • notification of specified information is not limited to explicit notification, but may be implicit (e.g., by not notifying the specified information or by notifying other information).
  • the determination may be based on a value represented by a single bit (0 or 1), a Boolean value represented by true or false, or a comparison of numerical values (e.g., with a predetermined value).
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • Software, instructions, information, etc. may also be transmitted and received via a transmission medium.
  • a transmission medium For example, if the software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and/or wireless technologies (such as infrared, microwave, etc.), then at least one of these wired and wireless technologies is included within the definition of a transmission medium.
  • wired technologies such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)
  • wireless technologies such as infrared, microwave, etc.
  • Network may refer to the devices included in the network (e.g., base stations).
  • the antenna port may be interchangeably read as an antenna port for any signal/channel (e.g., a demodulation reference signal (DMRS) port).
  • the resource may be interchangeably read as a resource for any signal/channel (e.g., a reference signal resource, an SRS resource, etc.).
  • the resource may include time/frequency/code/space/power resources.
  • the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.
  • the above groups may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, a Reference Signal (RS) group, a Control Resource Set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, etc.
  • CDM Code Division Multiplexing
  • RS Reference Signal
  • CORESET Control Resource Set
  • beam SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable.
  • SRI SRS Resource Indicator
  • CORESET CORESET pool
  • PDSCH PUSCH
  • codeword CW
  • TB transport block
  • RS etc.
  • TCI state downlink TCI state
  • DL TCI state downlink TCI state
  • UL TCI state uplink TCI state
  • unified TCI state common TCI state
  • joint TCI state etc.
  • QCL QCL
  • QCL assumptions QCL relationship
  • QCL type information QCL property/properties
  • specific QCL type e.g., Type A, Type D
  • specific QCL type e.g., Type A, Type D
  • index identifier
  • indicator indication, resource ID, etc.
  • sequence list, set, group, cluster, subset, etc.
  • TCI state ID the spatial relationship information identifier
  • TCI state ID the spatial relationship information
  • TCI state the spatial relationship information
  • TCI state the spatial relationship information
  • TCI state the spatial relationship information
  • Base Station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.
  • a base station can accommodate one or more (e.g., three) cells.
  • a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services by a base station subsystem (e.g., a small base station for indoor use (Remote Radio Head (RRH))).
  • RRH Remote Radio Head
  • the term "cell” or “sector” refers to a part or the entire coverage area of at least one of the base station and base station subsystems that provide communication services in this coverage.
  • a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control/operate based on the information.
  • MS Mobile Station
  • UE User Equipment
  • a mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.
  • At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc.
  • at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.
  • the moving body in question refers to an object that can move, and the moving speed is arbitrary, and of course includes the case where the moving body is stationary.
  • the moving body in question includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, balloons, and objects mounted on these.
  • the moving body in question may also be a moving body that moves autonomously based on an operating command.
  • the moving object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned).
  • a vehicle e.g., a car, an airplane, etc.
  • an unmanned moving object e.g., a drone, an autonomous vehicle, etc.
  • a robot manned or unmanned
  • at least one of the base station and the mobile station may also include 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. 12 is a diagram showing an example of a vehicle according to an embodiment.
  • the vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.
  • various sensors including a current sensor 50, a rotation speed sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58
  • an information service unit 59 including a communication module 60.
  • the drive unit 41 is composed of at least one of an engine, a motor, and a hybrid of an engine and a motor, for example.
  • the steering unit 42 includes at least a steering wheel (also called a handlebar), and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by the user.
  • the electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (e.g., an Input/Output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle.
  • the electronic control unit 49 may also be called an Electronic Control Unit (ECU).
  • ECU Electronic Control Unit
  • Signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the motor current, a rotation speed signal of the front wheels 46/rear wheels 47 acquired by a rotation speed sensor 51, an air pressure signal of the front wheels 46/rear wheels 47 acquired by an air pressure sensor 52, a vehicle speed signal acquired by a vehicle speed sensor 53, an acceleration signal acquired by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 acquired by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 acquired by a brake pedal sensor 56, an operation signal of the shift lever 45 acquired by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 58.
  • the information service unit 59 is composed of various devices, such as a car navigation system, audio system, speakers, displays, televisions, and radios, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices.
  • the information service unit 59 uses information acquired from external devices via the communication module 60, etc., to provide various information/services (e.g., multimedia information/multimedia services) to the occupants of the vehicle 40.
  • various information/services e.g., multimedia information/multimedia services
  • the information service unit 59 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that perform output to the outside.
  • input devices e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.
  • output devices e.g., a display, a speaker, an LED lamp, a touch panel, etc.
  • the driving assistance system unit 64 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving load, such as a millimeter wave radar, a Light Detection and Ranging (LiDAR), a camera, a positioning locator (e.g., a Global Navigation Satellite System (GNSS)), map information (e.g., a High Definition (HD) map, an Autonomous Vehicle (AV) map, etc.), a gyro system (e.g., an Inertial Measurement Unit (IMU), an Inertial Navigation System (INS), etc.), an Artificial Intelligence (AI) chip, and an AI processor, and one or more ECUs that control these devices.
  • the driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize a driving assistance function or an autonomous driving function.
  • the communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63.
  • the communication module 60 transmits and receives data (information) via the communication port 63 between the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58 that are provided on the vehicle 40.
  • the communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with an external device. For example, it transmits and receives various information to and from the 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 above-mentioned base station 10 or user terminal 20.
  • the communication module 60 may also be, for example, at least one of the above-mentioned base station 10 and user terminal 20 (it may function as at least one of the base station 10 and user terminal 20).
  • the communication module 60 may transmit at least one of the signals from the various sensors 50-58 described above input to the electronic control unit 49, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 59 to an external device via wireless communication.
  • the electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be referred to as input units that accept 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, vehicle distance information, etc.) transmitted from an external device and displays it on an information service unit 59 provided in the vehicle.
  • the information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data/information decoded from the PDSCH) received by the communication module 60).
  • the communication module 60 also stores various information received from external devices in memory 62 that can be used by the microprocessor 61. Based on the information stored in memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, various sensors 50-58, and the like provided on the vehicle 40.
  • the base station in the present disclosure may be read as a user terminal.
  • each aspect/embodiment of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.).
  • the user terminal 20 may be configured to have the functions of the base station 10 described above.
  • terms such as "uplink” and "downlink” may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink").
  • the uplink channel, downlink channel, etc. may be read as the sidelink channel.
  • the user terminal in this disclosure may be interpreted as a base station.
  • the base station 10 may be configured to have the functions of the user terminal 20 described above.
  • operations that are described as being performed by a base station may in some cases be performed by its upper node.
  • a network that includes one or more network nodes having base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME) or a Serving-Gateway (S-GW)), or a combination of these.
  • MME Mobility Management Entity
  • S-GW Serving-Gateway
  • each aspect/embodiment described in this disclosure may be used alone, in combination, or switched between depending on the implementation.
  • the processing procedures, sequences, flow charts, etc. of each aspect/embodiment described in this disclosure may be rearranged as long as there is no inconsistency.
  • the methods described in this disclosure present elements of various steps using an exemplary order, 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
  • 4th generation mobile communication system 4th generation mobile communication system
  • 5G 5th generation mobile communication system
  • 6G 6th generation mobile communication system
  • xG x is, for example, an integer or decimal
  • Future Radio Access FX
  • GSM Global System for Mobile communications
  • CDMA2000 Code Division Multiple Access
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • IEEE 802.16 WiMAX (registered trademark)
  • IEEE 802.20 Ultra-WideBand (UWB), Bluetooth (registered trademark), and other appropriate wireless communication methods, as well as next-generation systems that are expanded, modified,
  • the phrase “based on” does not mean “based only on,” unless expressly stated otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”
  • any reference to elements using designations such as “first,” “second,” etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a 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 some way.
  • determining may encompass a wide variety of actions. For example, “determining” may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking in a table, database, or other data structure), ascertaining, etc.
  • Determining may also be considered to mean “determining” receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), etc.
  • judgment (decision) may be considered to mean “judging (deciding)” resolving, selecting, choosing, establishing, comparing, etc.
  • judgment (decision) may be considered to mean “judging (deciding)” some kind of action.
  • judgment (decision) may be interpreted interchangeably with the actions described above.
  • expect may be read as “be expected”.
  • "expect(s)" ("" may be expressed, for example, as a that clause, a to infinitive, etc.) may be read as “be expected".
  • "does not expect" may be read as "be not expected".
  • "An apparatus A is not expected" may be read as "An apparatus B other than apparatus A does not expect" (for example, if apparatus A is a UE, apparatus B may be a base station).
  • the "maximum transmit power" referred to in this disclosure may mean the maximum value of transmit power, may mean the nominal UE maximum transmit power, or may mean the rated UE maximum transmit power.
  • connection and “coupled,” or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may 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 the elements may be physical, logical, or a combination thereof. For example, "connected” may be read as "accessed.”
  • a and B are different may mean “A and B are different from each other.”
  • the term may also mean “A and B are each different from C.”
  • Terms such as “separate” and “combined” may also be interpreted in the same way as “different.”
  • timing, time, duration, time instance, any time unit e.g., slot, subslot, symbol, subframe
  • period occasion, resource, etc.

Landscapes

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

Abstract

Un terminal selon un aspect de la présente divulgation comprend : une unité de réception qui reçoit un réglage pour la transmission d'une pluralité de canaux physiques d'accès aléatoire (PRACH) correspondant respectivement à une pluralité de filtres de transmission de domaine spatial ; et une unité de commande qui détermine une hypothèse de quasi-colocalisation pour une réception de liaison descendante, en fonction d'un PRACH spécifique dans la pluralité de PRACH, d'une réponse d'accès aléatoire, d'un canal partagé physique de liaison montante (PUSCH) programmé par la réponse d'accès aléatoire, et d'un canal physique partagé de liaison descendante (PDSCH) doté d'un identifiant de résolution de contention. Selon un aspect de la présente divulgation, la couverture d'une procédure d'accès aléatoire peut être améliorée.
PCT/JP2023/001733 2023-01-20 2023-01-20 Terminal, procédé de communication sans fil et station de base WO2024154342A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2023/001733 WO2024154342A1 (fr) 2023-01-20 2023-01-20 Terminal, procédé de communication sans fil et station de base

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2023/001733 WO2024154342A1 (fr) 2023-01-20 2023-01-20 Terminal, procédé de communication sans fil et station de base

Publications (1)

Publication Number Publication Date
WO2024154342A1 true WO2024154342A1 (fr) 2024-07-25

Family

ID=91955553

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/001733 WO2024154342A1 (fr) 2023-01-20 2023-01-20 Terminal, procédé de communication sans fil et station de base

Country Status (1)

Country Link
WO (1) WO2024154342A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019064229A1 (fr) * 2017-09-28 2019-04-04 Telefonaktiebolaget Lm Ericsson (Publ) Procédure d'accès aléatoire à faisceaux multiples dans l'exécution d'un transfert intercellulaire
US20200373969A1 (en) * 2017-05-12 2020-11-26 Mediatek Inc. Apparatuses and methods for a physical random access channel (prach) retransmission
WO2021064959A1 (fr) * 2019-10-03 2021-04-08 株式会社Ｎｔｔドコモ Terminal et procédé de communication sans fil

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200373969A1 (en) * 2017-05-12 2020-11-26 Mediatek Inc. Apparatuses and methods for a physical random access channel (prach) retransmission
WO2019064229A1 (fr) * 2017-09-28 2019-04-04 Telefonaktiebolaget Lm Ericsson (Publ) Procédure d'accès aléatoire à faisceaux multiples dans l'exécution d'un transfert intercellulaire
WO2021064959A1 (fr) * 2019-10-03 2021-04-08 株式会社Ｎｔｔドコモ Terminal et procédé de communication sans fil

Similar Documents

Publication Publication Date Title
WO2024154342A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024154344A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024154343A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024171428A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024209507A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024209673A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024214182A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024181396A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024219411A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024219412A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024225240A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024219452A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024219453A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024176336A1 (fr) Terminal et procédé de communication sans fil
WO2024069840A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024176337A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024100696A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024218837A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024219482A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024209672A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024171390A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024171389A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024225242A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024038514A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024095480A1 (fr) Terminal, procédé de communication sans fil et station de base

Legal Events

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

Ref document number: 23917555

Country of ref document: EP

Kind code of ref document: A1