WO2022083771A1 - Procédé et équipement utilisateur permettant de rétablir des liaisons relatives à un faisceau dans un système de communication sans fil - Google Patents

Procédé et équipement utilisateur permettant de rétablir des liaisons relatives à un faisceau dans un système de communication sans fil Download PDF

Info

Publication number
WO2022083771A1
WO2022083771A1 PCT/CN2021/125908 CN2021125908W WO2022083771A1 WO 2022083771 A1 WO2022083771 A1 WO 2022083771A1 CN 2021125908 W CN2021125908 W CN 2021125908W WO 2022083771 A1 WO2022083771 A1 WO 2022083771A1
Authority
WO
WIPO (PCT)
Prior art keywords
mac
bfrq
tci
implementations
trp
Prior art date
Application number
PCT/CN2021/125908
Other languages
English (en)
Inventor
Jiahong LIOU
Chiahao YU
Original Assignee
FG Innovation Company Limited
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 FG Innovation Company Limited filed Critical FG Innovation Company Limited
Publication of WO2022083771A1 publication Critical patent/WO2022083771A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection

Definitions

  • the present disclosure generally relates to wireless communication, and more particularly, to a method (s) and a user equipment (UE) for recovering beam-related link (s) in a wireless communication system.
  • next-generation wireless communication system such as the fifth-generation (5G) New Radio (NR)
  • 5G fifth-generation
  • NR New Radio
  • the 5G NR system is designed to provide flexibility and configurability to optimize the network services and types, accommodating various use cases such as enhanced Mobile Broadband (eMBB) , massive Machine-Type Communication (mMTC) , and Ultra-Reliable and Low-Latency Communication (URLLC) .
  • eMBB enhanced Mobile Broadband
  • mMTC massive Machine-Type Communication
  • URLLC Ultra-Reliable and Low-Latency Communication
  • the present disclosure is directed to a method (s) and a UE for recovering beam-related link (s) in a wireless communication system.
  • a method performed by a User Equipment (UE) communicating with a network in a serving cell for wireless communications includes measuring a first Reference Signal (RS) set and a second RS set in the serving cell; transmitting a first Beam Failure Recovery reQuest (BFRQ) via a first Medium Access Control (MAC) -Control Element (CE) (MAC-CE) on a first Uplink (UL) grant scheduled by a first Physical Downlink Control Channel (PDCCH) or by a first Radio Resource Control (RRC) configuration, in a case that an accumulated number of times where a quality of the first RS set is determined to be less than a first threshold reaches a first number; transmitting a second BFRQ via a second MAC-CE on a second UL grant scheduled by a second PDCCH or a second RRC configuration, in a case that an accumulated number of times where a quality of the second RS set is determined to be less than a second threshold reaches
  • the method further includes terminating an ongoing procedure for transmitting one of the first BFRQ and the second BFRQ in a case that the third BFRQ is triggered to be transmitted.
  • a MAC-CE format of the third MAC-CE is the same as one of a MAC-CE format of the first MAC-CE and a MAC-CE format of the second MAC-CE.
  • the third BFRQ is transmitted in a case that a first occurrence and a second occurrence occur in a same time duration, the first occurrence is that the accumulated number of times where the quality of the first RS set is determined to be less than the first threshold reaches the first number, and the second occurrence is that the accumulated number of times where the quality of the second RS set is determined to be less than the second threshold reaches the second number.
  • the time duration is pre-determined or pre-configured as one or more time units, and the one or more time units are in unit of one of at least one symbol, at least one sub-slot, at least one slot, at least one subframe, and at least one millisecond.
  • the serving cell is a Special Cell (SpCell) .
  • a User Equipment for communicating with a network in a serving cell for wireless communications.
  • the UE includes a memory storing at least one executable instructions and at least one processor coupled to the memory.
  • the at least one processor is configured to execute the at least one executable instructions to: measure a first Reference Signal (RS) set and a second RS set in the serving cell; transmit a first Beam Failure Recovery reQuest (BFRQ) via a first Medium Access Control (MAC) -Control Element (CE) (MAC-CE) on a first Uplink (UL) grant scheduled by a first Physical Downlink Control Channel (PDCCH) or by a first Radio Resource Control (RRC) configuration, in a case that an accumulated number of times where a quality of the first RS set is determined to be less than a first threshold reaches a first number; transmit a second BFRQ via a second MAC-CE on a second UL grant scheduled by a second PDCCH or a second RRC configuration,
  • the at least one processor is further configured to execute the at least one executable instructions to terminate an ongoing procedure for transmitting one of the first BFRQ and the second BFRQ in a case that the third BFRQ is triggered to be transmitted.
  • a MAC-CE format of the third MAC-CE is the same as one of a MAC-CE format of the first MAC-CE and a MAC-CE format of the second MAC-CE.
  • the third BFRQ is transmitted in a case that a first occurrence and a second occurrence occur in a same time duration, the first occurrence is that the accumulated number of times where the quality of the first RS set is determined to be less than the first threshold reaches the first number, and the second occurrence is that the accumulated number of times where the quality of the second RS set is determined to be less than the second threshold reaches the second number.
  • the time duration is pre-determined or pre-configured as one or more time units, and the one or more time units are in unit of one of at least one symbol, at least one sub-slot, at least one slot, at least one subframe, and at least one millisecond.
  • the serving cell is a Special Cell (SpCell) .
  • a method performed by a base station communicating with a User Equipment (UE) in a serving cell for wireless communications includes configuring the UE with a first Beam Failure Recovery (BFR) configuration and a second BFR configuration; preventing from not indicating a Radio Resource Control (RRC) configuration for at least one of a first Reference Signal (RS) set and a second RS set in a case that the base station transmits, to the UE, a first Medium Access Control (MAC) -Control Element (CE) (MAC-CE) that activates two Transmission Configuration Indicator (TCI) states and maps the two TCI states to a TCI codepoint in a TCI field; transmitting the first RS set and the second RS set in the serving cell; receiving a first Beam Failure Recovery reQuest (BFRQ) from the UE in a case that an accumulated number of times where a quality of the first RS set is less than a first threshold reaches a first number; and
  • BFRQ Beam Failure Recovery reQuest
  • the method further includes preventing from configuring the UE with at least two Control Resource Sets (CORESETs) having a same CORESET pool index (CORESETPoolIndex) .
  • CORESETs Control Resource Sets
  • CORESETPoolIndex CORESET Pool index
  • the first BFRQ is a second MAC-CE on an Uplink (UL) grant that is scheduled by a Physical Downlink Control Channel (PDCCH) or RRC signaling.
  • UL Uplink
  • PDCCH Physical Downlink Control Channel
  • RRC Radio Resource Control
  • the second BFRQ is a third MAC-CE on an Uplink (UL) grant that is scheduled by a Physical Downlink Control Channel (PDCCH) or RRC signaling.
  • UL Uplink
  • PDCH Physical Downlink Control Channel
  • RRC Radio Resource Control
  • Figure 1 illustrates an example data structure of a BFR MAC-CE according to an implementation of the present disclosure.
  • Figure 2 illustrates an example data structure of a BFR MAC-CE according to an implementation of the present disclosure.
  • Figure 3 illustrates an overview of UE RRC state machine and state transitions in NR.
  • Figure 4 illustrates an overview of UE state machine and state transitions in NR as well as the mobility procedures supported between NR/5GC E-UTRA/EPC and E-UTRA/5GC.
  • Figure 5 illustrates a flowchart for a method performed by a UE communicating with a network in a serving cell for wireless communications according to an implementation of the present disclosure.
  • Figure 6 illustrates a flowchart for a method performed by a BS communicating with a network in a serving cell for wireless communications according to an implementation of the present disclosure.
  • Figure 7 is a block diagram illustrating a node for wireless communication according to an implementation of the present disclosure.
  • the phrases “in one implementation, ” or “in some implementations, ” may each refer to one or more of the same or different implementations.
  • the term “coupled” is defined as connected whether directly or indirectly via intervening components and is not necessarily limited to physical connections.
  • the term “comprising” means “including, but not necessarily limited to” and specifically indicates open-ended inclusion or membership in the disclosed combination, group, series or equivalent.
  • the expression “at least one of A, B and C” or “at least one of the following: A, B and C” means “only A, or only B, or only C, or any combination of A, B and C. ”
  • system and “network” may be used interchangeably.
  • the term “and/or” is only an association relationship for disclosing associated objects and represents that three relationships may exist such that A and/or B may indicate that A exists alone, A and B exist at the same time, or B exists alone. “A and/or B and/or C” may represent that at least one of A, B, and C exists.
  • the character “/” generally represents that the associated objects are in an “or” relationship.
  • any disclosed network function (s) or algorithm (s) may be implemented by hardware, software, or a combination of software and hardware.
  • Disclosed functions may correspond to modules which may be software, hardware, firmware, or any combination thereof.
  • a software implementation may include computer-executable instructions stored on a computer-readable medium such as memory or other type of storage devices.
  • a computer-readable medium such as memory or other type of storage devices.
  • One or more microprocessors or general-purpose computers with communication processing capability may be programmed with corresponding computer-executable instructions and perform the disclosed network function (s) or algorithm (s) .
  • the microprocessors or general-purpose computers may include Application-Specific Integrated Circuitry (ASIC) , programmable logic arrays, and/or using one or more Digital Signal Processors (DSPs) .
  • ASIC Application-Specific Integrated Circuitry
  • DSP Digital Signal Processors
  • the computer-readable medium may include, but is not limited to, Random Access Memory (RAM) , Read-Only Memory (ROM) , Erasable Programmable Read-Only Memory (EPROM) , Electrically Erasable Programmable Read-Only Memory (EEPROM) , flash memory, Compact Disc Read-Only Memory (CD-ROM) , magnetic cassettes, magnetic tape, magnetic disk storage, or any other equivalent medium capable of storing computer-readable instructions.
  • RAM Random Access Memory
  • ROM Read-Only Memory
  • EPROM Erasable Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory Compact Disc Read-Only Memory
  • CD-ROM Compact Disc Read-Only Memory
  • magnetic cassettes magnetic tape
  • magnetic disk storage or any other equivalent medium capable of storing computer-readable instructions.
  • a radio communication network architecture such as a Long Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, an LTE-Advanced Pro system, or a 5G NR Radio Access Network (RAN) may typically include at least one base station (BS) , at least one UE, and one or more optional network elements that provide connection within a network.
  • the UE may communicate with the network such as a Core Network (CN) , an Evolved Packet Core (EPC) network, an Evolved Universal Terrestrial RAN (E-UTRAN) , a Next-Generation Core (NGC) , a 5G Core (5GC) , or an internet via a RAN established by one or more BSs.
  • Base station may be referred to as network, network node, gNodeB (gNB) , eNodeB (eNB) .
  • a UE may include, but is not limited to, a mobile station, a mobile terminal or device, or a user communication radio terminal.
  • the UE may be a portable radio equipment that includes, but is not limited to, a mobile phone, a tablet, a wearable device, a sensor, a vehicle, or a Personal Digital Assistant (PDA) with wireless communication capability.
  • PDA Personal Digital Assistant
  • the UE may be configured to receive and transmit signals over an air interface to one or more cells in a RAN.
  • the BS may be configured to provide communication services according to at least a Radio Access Technology (RAT) such as Worldwide Interoperability for Microwave Access (WiMAX) , Global System for Mobile communications (GSM) that is often referred to as 2G, GSM Enhanced Data rates for GSM Evolution (EDGE) RAN (GERAN) , General Packet Radio Service (GPRS) , Universal Mobile Telecommunication System (UMTS) that is often referred to as 3G based on basic Wideband-Code Division Multiple Access (W-CDMA) , High-Speed Packet Access (HSPA) , LTE, LTE-A, evolved/enhanced LTE (eLTE) that is LTE connected to 5GC, NR (often referred to as 5G) , and/or LTE-A Pro.
  • RAT Radio Access Technology
  • WiMAX Worldwide Interoperability for Microwave Access
  • GSM Global System for Mobile communications
  • EDGE GSM Enhanced Data rates for GSM Evolution
  • GERAN GSM Enhanced Data rates for
  • the BS may include, but is not limited to, a node B (NB) in the UMTS, an evolved node B (eNB) in LTE or LTE-A, a radio network controller (RNC) in UMTS, a BS controller (BSC) in the GSM/GERAN, a next-generation eNB (ng-eNB) in an Evolved Universal Terrestrial Radio Access (E-UTRA) BS in connection with 5GC, a next-generation Node B (gNB) in the 5G-RAN (or in the 5G Access Network (5G-AN) ) , or any other apparatus capable of controlling radio communication and managing radio resources within a cell.
  • the BS may serve one or more UEs via a radio interface.
  • the BS may provide radio coverage to a specific geographical area using a plurality of cells included in the RAN.
  • the BS may support the operations of the cells.
  • Each cell may be operable to provide services to at least one UE within its radio coverage.
  • Each cell may provide services to serve one or more UEs within its radio coverage such that each cell schedules the downlink (DL) and optionally uplink (UL) resources to at least one UE within its radio coverage for DL and optionally UL packet transmissions.
  • the BS may communicate with one or more UEs in the radio communication system via the plurality of cells.
  • a cell may allocate Sidelink (SL) resources for supporting Proximity Service (ProSe) , LTE SL services, and/or LTE/NR Vehicle-to-Everything (V2X) services.
  • SL Sidelink
  • Proximity Service Proximity Service
  • LTE SL services LTE SL services
  • V2X Vehicle-to-Everything
  • Each cell may have overlapped coverage areas with other cells.
  • the primary cell of a Master Cell Group (MCG) or a Secondary Cell Group (SCG) may be called a Special Cell (SpCell) .
  • a Primary Cell (PCell) may refer to the SpCell of an MCG.
  • a Primary SCG Cell (PSCell) may refer to the SpCell of an SCG.
  • An MCG may refer to a group of serving cells associated with the Master Node (MN) , comprising the SpCell and optionally one or more Secondary Cells (SCells) .
  • An SCG may refer to a group of serving cells associated with the Secondary Node (SN) , comprising the SpCell and optionally one or more SCells.
  • any sentence, paragraph, (sub) -bullet, point, action, or claim described in each of the following embodiment (s) /implementation (s) /concept (s) may be implemented independently and separately to form a specific method.
  • Dependency e.g., “based on” , “more specifically” , “where” or etc., in the following embodiment (s) /implementation (s) /concept (s) is just one possible embodiment which would not restrict the specific method.
  • BS a network central unit or a network node in NR which is used to control one or multiple TRPs which are associated with one or multiple cells. Communication between BS and TRP (s) is via fronthaul.
  • BS may be referred to as central unit (CU) , eNB, gNB, or NodeB.
  • TRP a transmission and reception point provides network coverage and directly communicates with UEs.
  • TRP may be referred to as distributed unit (DU) or network node.
  • DU distributed unit
  • a cell is composed of one or multiple associated TRPs, i.e. coverage of the cell is composed of coverage of all associated TRP (s) .
  • One cell is controlled by one BS.
  • Cell may be referred to as TRP group (TRPG) .
  • serving beam for a UE is a beam generated by a network node, e.g., TRP, which is configured to be used to communicate with the UE, e.g., for transmission and/or reception.
  • TRP network node
  • candidate beam for a UE is a candidate of a serving beam.
  • Serving beam may or may not be candidate beam.
  • Early Data Transmission Allows one uplink data transmission optionally followed by one downlink data transmission during the random access procedure as specified in TS 36.300.
  • the S1 connection is established or resumed upon reception of the uplink data and may be released or suspended along with the transmission of the downlink data.
  • Early data transmission refers to both CP-EDT and UP-EDT.
  • Transmission using PUR Allows one uplink data transmission using preconfigured uplink resource from RRC_IDLE mode as specified in TS 36.300. Transmission using PUR refers to both CP transmission using PUR and UP transmission using PUR.
  • BFR procedure may include: beam failure detection, beam failure recovery request transmission, and beam failure recovery response reception.
  • UE may update control and/or data beams automatically.
  • mechanisms, implementation or embodiments are provided to complete the TRP-specific BFR procedure and to solve the above-mentioned issues.
  • the mechanisms could be applied to issues or procedures with a similar consideration.
  • a UE may have at least one of the following features: the UE may be configured with and/or served by a network in a serving cell; the UE may (be configured to) communicate with the network in the serving cell; the UE may be configured with one or more serving cells, which may include the serving cell; the UE may be activated or be indicated to activate one or more serving cells, which may include the serving cell; the UE may be configured and/or indicated one or more BWP; a UE may be indicated and/or configured a BWP (in the serving cell) ; and the UE may operate in one of RRC_CONNECTED state, RRC_INACTIVE state and RRC_IDLE state.
  • a BWP described herein may refer to at least one of the followings: the BWP may be activated as an active BWP; the BWP may be referred to an active BWP; the BWP may be an active DL BWP; the BWP may be an active UL BWP; the BWP may be an initial BWP; the BWP may be a default BWP; and the BWP may be a dormant BWP.
  • a UE may communicate with the network via at least a first TRP and/or a second TRP.
  • the UE may perform DL reception from and/or UL transmission to a first TRP.
  • the UE may perform DL reception from and/or UL transmission to a second TRP.
  • the first TRP may be located in the serving cell.
  • the second TRP may be located in the serving cell.
  • the second TRP may be located in a neighboring or non-serving cell.
  • a UE may include or be equipped with one or more panels.
  • some or all of the one or more panels may be used and/or activated for DL reception (performed at the same time or same time interval) . In some implementations, some or all of the one or more panels may be used and/or activated for UL transmission (performed at the same time or same time interval) .
  • the set of used and/or activated panels for DL reception may be (partially) the same as the set of used and/or activated panels for UL transmission. In some implementations, the set of used and/or activated panels for DL reception may be (partially) different from the set of used and/or activated panels for UL transmission.
  • the UE may be configured/indicated with, or derive by the UE itself, one or more (value of) TRP identifier.
  • a TRP identifier may be associated with a TRP.
  • a DL transmission associated with a TRP identifier may mean that the DL transmission may be transmitted form a TRP associated with the TRP identifier.
  • a UL transmission associated with a TRP identifier may mean that the UL transmission may be transmitted to a TRP associated with the TRP identifier.
  • a TRP identifier may be associated with a CORESETPoolIndex, or a value (candidate) of a CORESETPoolIndex.
  • the UE may be configured/indicated with, or derive, one or more panel identifier (s) .
  • Each panel identifier may be associated with a panel (of the UE) .
  • a DL transmission associated with a panel identifier may mean that the DL transmission may be received by a (DL) panel associated with the panel identifier.
  • a UL transmission associated with a panel identifier may mean the UL transmission may be transmitted by a (UL) panel associated with the panel identifier.
  • a panel identifier may be associated with a SRS resource set index, or a (candidate) value of a SRS resource set index.
  • the UE may be configured/indicated with, or derive, at least one of a first TRP identifier for identifying the first TRP, a second TRP identifier for identifying the second TRP, a first panel identifier for identifying a first panel of the UE, and a second panel identifier for identifying a second panel of the UE.
  • a UE may receive one or more BFR-related configurations from the network. For example, a UE may receive a first BFR configuration, a second BFR configuration, and/or a third BFR configuration from the network, where the first BFR configuration may be used for or associated with a first BFR procedure, the second BFR configuration may be used for or associated with a second BFR procedure, and the third BFR configuration may be used for or associated with a third BFR procedure.
  • the first BFR configuration may be associated with BeamFailureRecoveryTRPConfig IE and/or PartialBeamFailureRecoveryConfig IE.
  • the second BFR configuration may be associated with BeamFailureRecoveryTRPConfig IE and/or PartialBeamFailureRecoveryConfig IE.
  • the third BFR configuration may be associated with BeamFailureRecoveryConfig IE and/or BeamFailureRecoverySCellConfig IE.
  • the first BFR procedure may be associated with beam failure recovery (or link recovery) for one or more of TRPs in a serving cell (e.g., the first TRP) .
  • the second BFR procedure may be associated with beam failure recovery (or link recovery) for one or more of TRPs in a serving cell (e.g., the second TRP) .
  • the third BFR procedure may be associated with beam failure recovery (or link recovery) for a whole serving cell, e.g., PCell and/or PSCell and/or SCell.
  • the first and/or second BFR procedure may be associated with beam failure recovery (or link recovery) for one of TRPs in a serving cell, where not all beam-related links are failed in the serving cell.
  • the first and/or second BFR procedure may be associated with beam failure recovery (or link recovery) for one of TRPs in a serving cell, where not all beam-related links of all TRPs in the serving cell are failed.
  • the first and/or second BFR procedure may be associated with beam failure recovery (or link recovery) may not be the link recovery procedure used in NR Rel-15/16 (e.g., TS 38.213 V16.3.0)
  • a UE may measure one or more sets of BFD RS. For example, the UE may measure a first set of BFD RS, a second set of BFD RS, and/or a third set of BFD RS.
  • the first set of BFD RS may be associated with the first TRP (and/or the first TRP identifier) .
  • the first set of BFD RS may be selected from CSI-RS resource (set) or SSB associated with the first TRP (and/or the first TRP identifier) .
  • the first set of BFD RS may be used for beam failure detection for the first TRP.
  • the second set of BFD RS may be associated with the second TRP and/or the second TRP identifier.
  • the second set of BFD RS may be selected from CSI-RS resource (set) or SSB associated with the second TRP and/or the second TRP identifier.
  • the second set of BFD RS may be used for beam failure detection for the second TRP.
  • the third set of BFD RS may be associated with a whole serving cell or the BWP.
  • the third set of BFD RS may be a RS set q 0 used in link recovery in NR Rel-15/16.
  • the third set of BFD RS may be used for beam failure detection for the whole serving cell or the BWP.
  • Each set of BFD RS may be configured in a BFR configuration.
  • the first set of BFD RS may be configured in the first BFR configuration
  • the second set of BFD RS may be configured in the second BFR configuration
  • the third set of BFD RS may be configured in the third BFR configuration.
  • the third set of BFD RS may be a combination of the first set of BFD RS and the second set of BFD RS.
  • (maximum number of) cardinality of the third set of BFD RS may be increased when (or if) the UE is configured/indicated with, or derives by itself, one or more (value of) TRP identifier. For example, increasing from 2 to 4 (or 5) .
  • the (maximum number of) cardinality of the third set of BFD RS may be increased when (or if) the UE is configured or indicated (e.g., by MAC-CE) that at least one TCI field codepoint in a DL scheduling DCI with TCI field present may indicate two TCI states (increasing from 2 to 4 (or 5) ) .
  • the third set of BFD RS may not be a (direct or full) combination of the first set of BFD RS and the second set of BFD RS.
  • the UE may further determine whether a beam-related (or link-related) failure event happens.
  • the UE may determine or detect whether or not (pre-determined) beam (s) /links (s) related to the first TRP in the serving cell is failed. In some implementations, the UE may determine or detect, based on measuring result of the first set of BFD RS, whether or not (pre-determined) beam (s) /links (s) related to the first TRP in the serving cell is failed.
  • the UE may determine or detect (pre-determined) beam (s) /links (s) related to the first TRP in the serving cell is failed, when (or if) detecting all (or some) qualities of the first set of BFD RS are below/above a first threshold.
  • the UE may determine or detect whether or not (pre-determined) beam (s) /links (s) related to the second TRP in the serving cell is failed.
  • the UE may determine or detect, based on measuring result of the second set of BFD RS, whether or not (pre-determined) beam (s) /links (s) related to the second TRP in the serving cell is failed.
  • the UE may determine or detect (pre-determined) beam (s) /links (s) related to the second TRP in the serving cell is failed, when (or if) detecting all (or some) qualities of the second set of BFD RS are below/above a second threshold.
  • the UE may determine or detect whether or not all (pre-determined) beam (s) /links (s) related to (the BWP in) the serving cell is failed.
  • the UE may determine or detect, based on measuring result of the third set of BFD RS, whether or not (pre-determined) beam (s) /links (s) related to (the BWP in) the serving cell is failed.
  • the UE may determine or detect (pre-determined) beam (s) /links (s) related to (the BWP in) the serving cell is failed, when (or if) detecting all (or some) qualities of the third set of BFD RS are lower than (or larger than) a third threshold.
  • the first threshold may be the same as the third threshold or the default value of rlmInSyncOutOfSyncThreshold IE.
  • the second threshold may be the same as the third threshold or the default value of rlmInSyncOutOfSyncThreshold IE.
  • the third threshold may be the default value of rlmInSyncOutOfSyncThreshold IE.
  • the first threshold may be different from the third threshold and/or the second threshold.
  • the second threshold may be different from the third threshold and/or the first threshold.
  • the first and/or the second threshold may be derived or indicated by the third threshold multiplying with a configured/indicated value.
  • Beam failure indicator (s) and beam failure indicator counter (s) may also be used in the procedure of beam failure detection.
  • the UE may be configured or indicated with one or more parameters for beam recovery or link recovery for the first TRP.
  • the one or more parameters may include at least one of the following:
  • a parameter for the beam failure detection e.g., beamFailureInstanceMaxCount
  • a parameter for the beam failure detection e.g., beamFailureDetectionTimer
  • a parameter for the beam failure recovery procedure e.g., beamFailureRecoveryTimer
  • an RSRP threshold for the beam failure recovery e.g., rsrp-ThresholdSSB
  • a parameter for power ramping step for beam failure recovery (e.g., powerRampingStep) ;
  • a parameter for power ramping step high priority for beam failure recovery e.g., powerRampingStepHighPriority
  • preambleReceivedTargetPower a parameter for preamble received target power for beam failure recovery (e.g., preambleReceivedTargetPower) ;
  • preambleTransMax a parameter for preamble trans maximum for beam failure recovery
  • scalingFactorBI a parameter for scaling factor BI for beam failure recovery
  • a parameter for indicating SSB per RACH-Occasion for beam failure recovery (e.g., ssb-perRACH-Occasion) ;
  • ra-ResponseWindow a parameter for the time window to monitor response (s) for beam failure recovery using contention-free Random Access Preamble (e.g., ra-ResponseWindow) ;
  • prach configuration index for beam failure recovery e.g., prach-ConfigurationIndex
  • ra/ssb occasion mask index for beam failure recovery e.g., ra-ssb-OccasionMaskIndex
  • ra occasion list for beam failure recovery e.g., ra-OccasionList
  • the UE may be configured or indicated one or more the following parameters for beam recovery or link recovery for the second TRP:
  • a parameter for the beam failure detection e.g., beamFailureInstanceMaxCount
  • a parameter for the beam failure detection e.g., beamFailureDetectionTimer
  • a parameter for the beam failure recovery procedure e.g., beamFailureRecoveryTimer
  • an RSRP threshold for the beam failure recovery e.g., rsrp-ThresholdSSB
  • a parameter for power ramping step high priority for the SpCell beam failure recovery e.g., powerRampingStepHighPriority
  • preambleReceivedTargetPower a parameter for preamble received target power for the SpCell beam failure recovery
  • preambleTransMax a parameter for preamble trans maximum for the SpCell beam failure recovery
  • scalingFactorBI a parameter for scaling factor BI for the SpCell beam failure recovery
  • a parameter for indicating SSB per RACH-Occasion for the SpCell beam failure recovery (e.g., ssb-perRACH-Occasion) ;
  • prach configuration index for the SpCell beam failure recovery e.g., prach-ConfigurationIndex
  • ra/ssb occasion mask index for the SpCell beam failure recovery e.g., ra-ssb-OccasionMaskIndex
  • ra occasion list for the SpCell beam failure recovery e.g., ra-OccasionList
  • the UE may be configured or indicated one or more the following parameters for beam recovery or link recovery for the serving cell or active (DL/UL) BWP:
  • a parameter for the beam failure detection e.g., beamFailureInstanceMaxCount
  • a parameter for the beam failure detection e.g., beamFailureDetectionTimer
  • a parameter for the beam failure recovery procedure e.g., beamFailureRecoveryTimer
  • an RSRP threshold for the beam failure recovery e.g., rsrp-ThresholdSSB
  • a parameter for power ramping step high priority for the SpCell beam failure recovery e.g., powerRampingStepHighPriority
  • preambleReceivedTargetPower a parameter for preamble received target power for the SpCell beam failure recovery
  • preambleTransMax a parameter for preamble trans maximum for the SpCell beam failure recovery
  • scalingFactorBI a parameter for scaling factor BI for the SpCell beam failure recovery
  • a parameter for indicating SSB per RACH-Occasion for the SpCell beam failure recovery (e.g., ssb-perRACH-Occasion) ;
  • prach configuration index for the SpCell beam failure recovery e.g., prach-ConfigurationIndex
  • ra/ssb occasion mask index for the SpCell beam failure recovery e.g., ra-ssb-OccasionMaskIndex
  • ra occasion list for the SpCell beam failure recovery e.g., ra-OccasionList
  • the BFI counting procedure may be performed per TRP (e.g., performed respectively for the first TRP and/or the second TRP) .
  • the BFI counting procedure for the serving cell may be different from or be performed independently from those for TRP (s) .
  • the UE may be configured/indicated with, or derive, a first set of NBI RS, a second set of NBI RS, and/or a third set of NBI RS.
  • the first set of NBI RS may be associated with the first TRP and/or the first TRP identifier.
  • the first set of NBI RS may be associated with the first TRP and/or the first TRP identifier.
  • the first set of NBI RS may be selected from CSI-RS resource (set) or SSB associated with the first TRP and/or the first TRP identifier.
  • the first set of NBI RS may be used for new beam identification for the first TRP.
  • the second set of NBI RS may be associated with the second TRP and/or the second TRP identifier.
  • the second set of NBI RS may be selected from CSI-RS resource (set) or SSB associated with the second TRP and/or the second TRP identifier.
  • the second set of NBI RS may be used for new beam identification for the second TRP.
  • the third set of NBI RS may be associated with a whole serving cell or the BWP.
  • the third set of NBI RS may be a RS set q 1 used in link recovery in NR Rel-15/16 (e.g., TS 38.213 V16.3.0) .
  • the third set of NBI RS may be used for new beam identification for the whole serving cell or the BWP
  • the UE may measure the first set of NBI RS, the second set of NBI RS, and/or the third set of NBI RS.
  • the UE may select a first NCB RS.
  • the first NCB RS may be used for beam recovery or link recovery for the first TRP.
  • the first NCB RS may be selected from measuring result of the first set of NBI RS.
  • the first NCB RS may be a RS with measuring quality higher than or equal to a first NCB threshold.
  • the UE may select a second NCB RS.
  • the second NCB RS may be used for beam recovery or link recovery for the second TRP.
  • the second NCB RS may be selected from measuring result of the second set of NBI RS.
  • the second NCB RS may be a RS with measuring quality higher than or equal to a second NCB threshold.
  • the UE may select a third NCB RS.
  • the third NCB RS may be used for beam recovery or link recovery for the serving cell.
  • the third NCB RS may be selected from measuring result of the third set of NBI RS.
  • the third NCB RS may be a RS with measuring quality higher than or equal to a third NCB threshold.
  • the third NCB RS may be a parameter q new used in link recovery in NR Rel-15/16 (e.g., TS 38.213 V16.3.0) .
  • the first, second, or third NCB threshold may be rsrp-ThresholdSSB IE or rsrp-ThresholdBFR-r16 IE.
  • the first and/or second NCB threshold may be the third NCB threshold multiplying with a configured or indicated value.
  • a UE may transmit a beam failure recovery request (BFRQ) during a procedure of beam failure recovery.
  • BFRQ beam failure recovery request
  • the UE may transmit a first BFRQ, a second BFRQ, and/or a third BFRQ.
  • the UE may transmit the first BFRQ, when (or if) determining or detecting (pre-determined) beam (s) /links (s) related to the first TRP in the serving cell is failed.
  • the UE may transmit the first BFRQ, when (or if) detecting all (or some) qualities of the first set of BFD RS are below the first threshold.
  • the UE may transmit the first BFRQ to notify failure of beam relate links of the first TRP.
  • the UE may transmit the first NCB RS via the first BFRQ explicitly/implicitly.
  • the UE may transmit the second BFRQ, when (or if) determining or detecting (pre-determined) beam (s) /links (s) related to the first TRP in the serving cell is failed.
  • the UE may transmit the second BFRQ, when (or if) detecting all (or some) qualities of the second set of BFD RS are below the second threshold.
  • the UE may transmit the second BFRQ to notify failure of beam relate links of the second TRP.
  • the UE may transmit the second NCB RS via the second BFRQ explicitly/implicitly.
  • the UE may transmit the third BFRQ or transmit a PRACH or perform a RA procedure, when (or if) determining or detecting (pre-determined) beam (s) /links (s) related to the serving cell is failed.
  • the UE may transmit the third BFRQ or transmit a PRACH or perform a RA procedure, when (or if) detecting all (or some) qualities of the third set of BFD RS are below the third threshold.
  • the UE may transmit the third BFRQ or transmit a PRACH or perform a RA procedure to notify failure of beam relate links of the third TRP.
  • the UE may transmit the third NCB RS via a third BFRQ explicitly/implicitly.
  • the UE may not (be required to) transmit a PRACH or perform a RA procedure, when (or if) determining or detecting (pre-determined) beam (s) /links (s) related to the first/second TRP in the serving cell is failed.
  • the UE may not (be required to) transmit a PRACH or perform a RA procedure, when (or if) detecting all (or some) qualities of the first/second set of BFD RS are below the first/second threshold.
  • the UE may not (be required to) transmit a PRACH or perform a RA procedure to notify failure of beam relate links of the first/second TRP.
  • the first BFRQ and the second BFRQ may be the same.
  • the first BFRQ and the second BFRQ may be transmitted via the same physical channel.
  • the first BFRQ and the second BFRQ may be transmitted via the same (type of) MAC-CE.
  • the first BFRQ and/or the second BFRQ may be transmitted via BFR MAC-CE.
  • the first BFRQ and/or the second BFRQ may include BFR MAC-CE.
  • the first BFRQ (or the second BFRQ) and the third BFRQ may be transmitted via the same physical channel.
  • the first BFRQ (or the second BFRQ) and the third BFRQ may be transmitted via the same (type of) MAC-CE.
  • the third BFRQ may be transmitted via a BFR MAC-CE.
  • the third BFRQ may include BFR MAC-CE.
  • the first BFRQ (or the second BFRQ) and the third BFRQ may be transmitted via different physical channel.
  • the third BFRQ may be transmitted via PRACH.
  • the first BFRQ and/or the second BFRQ may not (be required to) be accompanied with a RA procedure.
  • the third BFRQ may be (be required to) be accompanied with a RA procedure.
  • a BFR MAC-CE in SpCell can be transmitted in any type of UL channel when it is for TRP BFR.
  • the UE when performing transmission of the first BFRQ via the MAC-CE, may (be allowed to) transmit the MAC-CE on PUSCH scheduled by one or more type of signaling (e.g., UL scheduling DCI, RRC configuration/configured grant, RAR grant, RAR retransmission grant) .
  • one or more type of signaling e.g., UL scheduling DCI, RRC configuration/configured grant, RAR grant, RAR retransmission grant.
  • the UE when performing transmission of the first BFRQ via the MAC-CE, may (be allowed to) transmit the MAC-CE on the earliest available PUSCH.
  • the UE when performing transmission of the second BFRQ via the MAC-CE, may (be allowed to) transmit the MAC-CE on PUSCH scheduled by one or more type of signaling (e.g., UL scheduling DCI, RRC configuration/configured grant, RAR grant, RAR retransmission grant) .
  • one or more type of signaling e.g., UL scheduling DCI, RRC configuration/configured grant, RAR grant, RAR retransmission grant.
  • the UE when performing transmission of the second BFRQ via the MAC-CE, may (be allowed to) transmit the MAC-CE on the earliest available PUSCH.
  • the UE when performing transmission of the third BFRQ via the MAC-CE, may perform (only) allowed to transmit the MAC-CE, if the MAC-CE is to be transmitted in a PUSCH scheduled by a RAR grant.
  • the UE when performing transmission of the third BFRQ via the MAC-CE, may (only) allowed to transmit the MAC-CE, if the third BFRQ is performed by using a contention-based RA procedure or the UE is performing a contention-based RA procedure.
  • the MAC-CE when (or if) the MAC-CE is used for transmitting the first and/or the second BFRQ, the MAC-CE may contain or carry a field indicating that which TRP in the serving cell is detected with (beam related) link failure.
  • the MAC-CE when (or if) the MAC-CE is used for transmitting the first and/or the second BFRQ, the MAC-CE may contain or carry a field indicating that index/information of a TRP in the serving cell, where the TRP is detected with (beam related) link failure.
  • the field in the MAC-CE may (only) be present when the MAC-CE is transmitted for the first and/or the second BFRQ.
  • the field in the MAC-CE may (only) be present when the MAC-CE is transmitted in response to that detecting (pre-determined) beam related to at least one (but not all) TRP (s) in a serving cell is failed.
  • the field in the MAC-CE may not be present or may be reserved when the MAC-CE is transmitted for the third BFRQ.
  • the field in the MAC-CE may not be present or may be reserved when the MAC-CE is transmitted in response to that detecting (pre-determined) beam (s) /links (s) related to all TRPs in a serving cell is failed.
  • the network may transmit a BFRR to the UE in response to receiving the BFRR from the UE.
  • the UE may receive a first BFRR, a second BFRR, and/or a third BFRR from the network.
  • the network may transmit the first BFRR in response to receiving the first BFRQ.
  • the network may transmit the second BFRR in response to receiving the second BFRQ.
  • the network may transmit the third BFRR in response to receiving the third BFRQ.
  • the UE may receive a first BFR CORESET and/or a first BFR search space.
  • the UE may receive a second BFR CORESET or and/or a second BFR search space.
  • the UE may receive a third BFR CORESET and/or a third BFR search space.
  • the third BFR search space may be configured by recoverySearchSpaceId.
  • the first BFRR may be at least one of the following:
  • the second BFRR may be at least one of the following:
  • the third BFRR may be at least one of the following:
  • a UE may perform a TRP-specific BFR procedure when operating in a multiple-DCI M-TRP (Multi-TRP) scenario.
  • Multi-TRP multiple-DCI M-TRP
  • the UE may be configured/indicated with, or derive by the UE itself, one or more (value of) TRP identifier.
  • the TRP identifier may be CORESETPoolIndex IE.
  • the UE may be configured/indicated with, or derive, a first value of TRP identifier and/or a second value of TRP identifier.
  • the UE may be configured/indicated with, or derive, CORESETPoolIndex value 0 for one or more CORESETs.
  • the UE may be configured/indicated with, or derive by itself, CORESETPoolIndex value 1 for (another) one or more CORESETs.
  • the UE may be configured by a higher layer parameter, e.g., PDCCH-Config, that contains two different values of CORESETPoolIndex in different ControlResourceSets.
  • a higher layer parameter e.g., PDCCH-Config
  • the first value of TRP identifier may be CORESETPoolIndex value 0.
  • the second value of TRP identifier may be CORESETPoolIndex value 1.
  • the UE may update beams applied for receiving one or more DL channel/RS and/or transmitting one ore more UL channel/RS associated with the first TRP and/or the first (value of) TRP identifier (may or may not exclude CORESET #0) .
  • the UE may update beams applied for receiving one or more DL channel/RS and/or transmitting one or more UL channel/RS associated with the first TRP and/or the first (value of) TRP identifier (may or may not exclude CORESET #0) .
  • the UE may update beams applied for receiving one or more DL channel/RS and/or transmitting one or more UL channel/RS associated with the first TRP and/or the first (value of) TRP identifier, which updated beams are determined based on the first NCB RS (may or may not exclude CORESET #0) .
  • the UE may not update beams applied for receiving one or more DL channel/RS and/or transmitting one or more UL channel/RS, which is not associated with the first TRP and/or the first (value of) TRP identifier (may or may not exclude CORESET #0) .
  • the UE may update beams applied for receiving one or more DL channel/RS and/or transmitting one or more UL channel/RS associated with the second TRP and/or the second (value of) TRP identifier (may or may not exclude CORESET #0) .
  • the UE may update beams applied for receiving one or more DL channel/RS and/or transmitting one or more UL channel/RS associated with the second TRP and/or the second (value of) TRP identifier (may or may not exclude CORESET #0) .
  • the UE may update beams applied for receiving one or more DL channel/RS and/or transmitting one or more UL channel/RS associated with the second TRP and/or the second (value of) TRP identifier, which updated beams are determined based on the second NCB RS (may or may not exclude CORESET #0) .
  • the UE may not update beams applied for receiving one or more DL channel/RS and/or transmitting one or more UL channel/RS, which is not associated with the second TRP and/or the second (value of) TRP identifier (may or may not exclude CORESET #0) .
  • the UE may update beams applied for receiving DL and/or transmitting UL channel/RS in the serving cell (may or may not exclude CORESET #0) .
  • the UE may update beams applied for receiving DL and/or beams UL channel/RS in the serving cell (may or may not exclude CORESET #0) .
  • the UE may update beams applied for receiving DL and/or transmitting UL channel/RS in the serving cell (may or may not exclude CORESET #0) .
  • the UE may not update beams applied for receiving DL and/or beams UL channel/RS in the serving cell (may or may not exclude CORESET #0) .
  • a UE may perform a TRP-specific BFR procedure when operating in a single-DCI M-TRP (Multi-TRP) scenario.
  • Multi-TRP Multi-TRP
  • the UE is not configured/indicated with, or does not derive by itself, more than one (value of) TRP identifier.
  • the TRP identifier is CORESETPoolIndex.
  • the UE is (only) configured/indicated with, or (only) derives by the UE itself, CORESETPoolIndex value 0 for one or more CORESETs.
  • the UE may not be configured by higher layer parameter PDCCH-Config that contains two different values of CORESETPoolIndex in different ControlResourceSets.
  • the network may prevent from or may not be (allowed to) configure the UE higher layer parameter PDCCH-Config that contains two different values of CORESETPoolIndex in different ControlResourceSets.
  • the UE may receive a PDSCH-beam MAC-CE for activating/indicating a set of TCI states for (receiving) PDSCH.
  • the PDSCH-beam MAC-CE may activate or indicate the set of TCI states to map with each or some codepoints in a TCI field in a DL scheduling DCI.
  • the PDSCH-beam MAC-CE may map two TCI states with one TCI field codepoint.
  • the PDSCH-beam MAC-CE may map one TCI state with one TCI field codepoint.
  • the UE may be configured or indicated (e.g., by MAC-CE) that at least one TCI field codepoint in a DL scheduling DCI with TCI field present may indicate two TCI states.
  • the UE may determine or select the first set of BFD RS based on a pre-determined rule.
  • the UE may not receive configuration of the first set of BFD RS.
  • the UE may determine or select the first set of RS based on a pre-determined rule.
  • the UE may determine or select the second set of BFD RS based on a pre-determined rule. In some implementations, the UE may not receive configuration of the second set of BFD RS. In some implementations, when (or if) the UE does not receive configuration of the second set of BFD RS, the UE may determine or select the second set of RS based on a pre-determined rule.
  • the UE may determine or select the first set of BFD RS based on PDCCH DMRS (s) of some or all monitored CORESET (s) .
  • the UE may determine or select the first set of BFD RS based on PDCCH DMRS (s) of some or all monitored CORESET (s) in active BWP of the serving cell.
  • the UE may determine or select the first set of BFD RS based on source RS (s) associated with TCI state (s) for receiving some or all monitored CORESET (s) .
  • the UE may determine or select the first set of BFD RS based on source RS (s) associated with TCI state (s) for receiving some or all monitored CORESET (s) in active BWP of the serving cell.
  • the UE may determine or select the second set of BFD RS based on at least one of the following:
  • the source RS (s) associated with TCI state (s) activated e.g., by MAC-CE for receiving PDSCH;
  • a MAC-CE for activating TCI states for receiving PDSCH indicates the following TCI state IDs: (0, (2, 3) , (7, 8) , 15, 23, 24) .
  • (2, 3) and (7, 8) may map TCI codepoint 1 and 2 respectively, and TCI state 3 and TCI state 8 are the secondly indicated TCI states.
  • the UE may receive a configuration of a first CSI-RS resource set and/or a configuration of a second CSI-RS resource set.
  • the first CSI-RS resource set may be configured with or associated with the first TRP (identifier) .
  • the second CSI-RS resource set may be configured with or associated with the second TRP (identifier) .
  • the first CSI-RS resource set may contain periodic CSI-RS (s) .
  • the second CSI-RS resource set may contain periodic CSI-RS (s) .
  • the UE may determine or select the first set of BFD RS based on one or more source RS (s) of TCI states (s) for receiving monitored CORESETs, where the one or more source RS (s) are associated with the first CSI-RS resource set.
  • the UE may determine or select the second set of BFD RS based on one or more source RS (s) of TCI states (s) for receiving monitored CORESETs, where the one or more source RS (s) are associated with the second CSI-RS resource set.
  • the network may be required to configure the second set of BFD RS.
  • the network may prevent from not configuring the second set of BFD RS.
  • the network may be required to configure the first set of BFD RS.
  • the network may prevent from not configuring the first set of BFD RS.
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing two TCI states.
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing two TCI states until the UE receives a MAC-CE updating the mapping of TCI field codepoint and TCI states.
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing two TCI states, when (or if) the second BFRR does not include or carry a MAC-CE updating the mapping of TCI field codepoint and TCI states.
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the second TRP (identifier) .
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the second TRP (identifier) , until the UE receives a MAC-CE updating the mapping of TCI field codepoint and TCI state (s) .
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the second TRP (identifier) , when (or if) the second BFRR does not include or carry a MAC-CE updating the mapping of TCI field codepoint and TCI states.
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing two TCI states.
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing two TCI states, until the network transmits a MAC-CE updating the mapping of TCI field codepoint and TCI states (and/or receives acknowledgement from the UE for the MAC-CE, if any) .
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing two TCI states, when (or if) the second BFRR does not include or carry a MAC-CE updating the mapping of TCI field codepoint and TCI states.
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the second TRP (identifier) .
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the second TRP (identifier) , until the network transmits or the UE receives a MAC-CE updating the mapping of TCI field codepoint and TCI state (s) .
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the first TRP (identifier) , when (or if) the second BFRR does not include or carry a MAC-CE updating the mapping of TCI field codepoint and TCI states.
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing two TCI states.
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing two TCI states, until the UE receives a MAC-CE updating the mapping of TCI field codepoint and TCI states.
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing two TCI states, when (or if) the first BFRR does not include or carry a MAC-CE updating the mapping of TCI field codepoint and TCI states.
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the first TRP (identifier) .
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the first TRP (identifier) , until the UE receives a MAC-CE updating the mapping of TCI field codepoint and TCI state (s) .
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the first TRP (identifier) , when (or if) the first BFRR does not include or carry a MAC-CE updating the mapping of TCI field codepoint and TCI states.
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing two TCI states.
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing two TCI states, until the network transmits a MAC-CE updating the mapping of TCI field codepoint and TCI states (and/or receives acknowledgement from the UE for the MAC-CE, if any) .
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing two TCI states, when (or if) the first BFRR does not include or carry a MAC-CE updating the mapping of TCI field codepoint and TCI states.
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the first TRP (identifier) .
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the first TRP (identifier) , until the network transmits or the UE receives a MAC-CE updating the mapping of TCI field codepoint and TCI state (s) .
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the first TRP (identifier) , when (or if) the first BFRR does not include or carry a MAC-CE updating the mapping of TCI field codepoint and TCI states.
  • the first BFRR may be required to contain or indicate information of updating mapping of TCI field codepoint and TCI states.
  • the second BFRR may be required to contain or indicate information of updating mapping of TCI field codepoint and TCI states.
  • the first BFRR may be required to include a MAC-CE for updating mapping of TCI field codepoint and TCI states.
  • the second BFRR may be required to include a MAC-CE for updating mapping of TCI field codepoint and TCI states.
  • a QCL assumption or a TCI state may refer to at least one of a joint DCI, a DL TCI, a DL TCI associated with QCL type-D, a DL beam, a spatial transmission filter, one or more spatial parameters, a spatial relationship, and a spatial assumption.
  • a spatial relation for transmitting a UL resource may refer to at least one of a UL beam, a joint TCI, a UL TCI, a spatial transmission filter, a transmission precoder, one or more spatial parameters, and a spatial relationship.
  • a panel may mean that an antenna (port) group or an antenna (port) set. There may be more than one DL/UL beams associated with one panel.
  • UE or NW transmitting node
  • UE or NW transmitting node
  • a transmitter comprising more than one panels, e.g., two panels, it may happen that two beams associated with the two panels respectively are used to perform a transmission.
  • a TRP identifier may refer to a (candidate) value of a TRP identifier.
  • a first TRP identifier could be a first candidate value of a TRP identifier or a first TRP identifier value
  • a second TRP identifier could be a second candidate value of a TRP identifier or a second TRP identifier value.
  • a panel identifier may refer to a (candidate) value of a panel identifier.
  • a first panel identifier could be a first candidate value of a panel identifier or a first panel identifier value
  • a second panel identifier could be a second candidate value of a panel identifier or a second panel identifier value.
  • a UE detecting and/or determining that the (pre-determined) beam (s) /links (s) in a serving cell is failed may mean that some or all configured or selected reference signal (s) associated with beam (s) /link (s) in the serving cell are measured with quality below a certain threshold (e.g., RSRP) .
  • a certain threshold e.g., RSRP
  • a UE detecting and/or determining that the (pre-determined) beam (s) /links (s) in a serving cell is failed may mean that some or all configured or selected reference signal (s) associated with beam (s) /link (s) in the serving cell are measured with quality above a certain threshold (e.g., BLER) .
  • a certain threshold e.g., BLER
  • a UE detecting and/or determining that the (pre-determined) beam (s) /links (s) of a TRP is failed may mean that some or all configured or selected reference signal (s) associated with beam (s) /link (s) of the TRP are measured with quality below a certain threshold (e.g., RSRP) .
  • a certain threshold e.g., RSRP
  • a UE detecting and/or determining the (pre-determined) beam (s) /links (s) of a TRP is failed may mean that some or all configured or selected reference signal (s) associated with beam (s) /link (s) of the TRP are measured with quality above a certain threshold (e.g., BLER) .
  • a certain threshold e.g., BLER
  • a BFR procedure may refer to as a link recovery procedure.
  • a BFR procedure may not be a recovery or re-establishment procedure for RLF.
  • a procedure or description is related to a serving cell, it may mean the procedure or description is related to an active (DL/UL) BWP in the serving cell.
  • a UE may send a BFR MAC-CE on any PSUCH.
  • a UE may only send a BFR MAC-CE on a PUSCH scheduled by an RAR grant (i.e., MSG3) or MSGA.
  • a UE may (be configured to) communicate with one or more TRPs (e.g., a first TRP and/or a second TRP) at least within a serving cell and/or on a component carrier.
  • the UE may communicate with a network via the first TRP and the second TRP.
  • the serving cell may be a primary cell or a secondary cell.
  • the UE may receive a first BFR configuration, a second BFR configuration, and/or a third BFR configuration, where the first BFR configuration may be associated with a first BFR procedure, the second BFR configuration may be associated with a second BFR procedure, and the third BFR configuration may be associated with a third BFR procedure.
  • the UE may transmit a first BFRQ, a second BFRQ, and/or a third BFRQ.
  • Each BFRQ (e.g., the first BFRQ, the second BFRQ, or the third BFRQ) may mean a link recovery request.
  • the third BFR procedure may be referred to or associated with link recovery procedure defined in NR Rel-15/16 as in, for example, TS 38.213 V16.3.0.
  • the first and/or the second BFRQ may be transmitted, when detecting (pre-determined) beam (s) /links (s) in a serving cell is failed.
  • the first BFRQ may be transmitted, when detecting (pre-determined) beam (s) /links (s) related to all TRPs in a serving cell is failed (e.g., the first and/or the second TRP) .
  • the third BFRQ may be transmitted, when detecting (pre-determined) beam (s) /links (s) related to at least one (but not all) TRP (s) in a serving cell is failed.
  • the third BFRQ may be transmitted, when detecting (pre-determined) beam (s) /links (s) related to only one TRP in a serving cell is failed.
  • the UE may transmit the first and/or the second BFRQ via a MAC-CE to notify the network of occurrence of beam failure.
  • the UE may transmit the third BFRQ via the MAC-CE to notify the network of occurrence of beam failure.
  • the UE When performing transmission of the first and/or the second BFRQ via the MAC-CE, the UE may (be allowed to) transmit the MAC-CE on PUSCH scheduled by any type of signaling (e.g., UL scheduling DCI, RRC configuration/configured grant, RAR grant, RAR retransmission grant) .
  • the UE When performing transmission of the first and/or the second BFRQ via the MAC-CE, the UE may (be allowed to) transmit the MAC-CE on the earliest available PUSCH.
  • the UE When performing transmission of the third BFRQ via the MAC-CE, the UE may be (only) allowed to transmit the MAC-CE, if the MAC-CE is to be transmitted in a PUSCH scheduled by a RAR grant.
  • the UE When performing transmission of the third BFRQ via the MAC-CE, the UE may be (only) allowed to transmit the MAC-CE, if the third BFRQ is performed by using a contention-based RA procedure or the UE is performing a contention-based RA procedure.
  • the MAC-CE may contain or carry a field indicating that which TRP in the serving cell is detected with (beam related) link failure.
  • the MAC-CE may contain or carry a field indicating that index/information of a TRP in the serving cell, where the TRP is detected with (beam related) link failure.
  • the field in the MAC-CE may (only) be present when the MAC-CE is transmitted for the first and/or the second BFRQ.
  • the field in the MAC-CE may (only) be present when the MAC-CE is transmitted in response to the situation that the UE detects that all or some (pre-determined) beam (s) /link (s) related to at least one (but not all) TRP (s) in a serving cell is failed.
  • the field in the MAC-CE may not be present or may be reserved when the MAC-CE is transmitted for the third BFRQ.
  • the field in the MAC-CE may not be present or may be reserved when the MAC-CE is transmitted in response to the situation that the UE detects all or some (pre-determined) beam (s) /links (s) related to all TRPs in a serving cell is failed.
  • the MAC-CE may be a BFR MAC-CE.
  • the first BFRQ may be transmitted via the MAC-CE indicating the first TRP.
  • the second BFRQ may be transmitted via the MAC-CE indicating the second TRP.
  • Figure 1 illustrates an example data structure of a BFR MAC-CE 100 according to an implementation of the present disclosure.
  • the BFR MAC CE 100 with the highest ServCellIndex of this MAC entity’s SCell configured with BFD is less than eight.
  • the BFR MAC-CE 100 includes an SP field, seven cell index fields C i (e.g., C 1 to C 7 ) , one or more candidate RS ID fields (or Reserved bits (R bits) ) each with an AC field, and R bits. Definitions of the field are described in Table 1.
  • Figure 2 illustrates an example data structure of a BFR MAC-CE 200 according to an implementation of the present disclosure.
  • the BFR MAC CE 200 with the highest ServCellIndex of this MAC entity’s SCell configured with BFD is equal to or higher than eight.
  • the BFR MAC-CE 200 includes an SP field, multiple cell index fields C i (e.g., C 1 to C 31 ) , one or more candidate RS ID fields (or R bits) each with an AC field, and R bits. Definitions of the field are described in Table 1.
  • a specific field may be present when the MAC-CE is used to transmit the first and/or second BFRQ.
  • the specific field may not present when the MAC-CE is used to transmit the third BFRQ.
  • the specific field may be present in an octet starting with the ACfield.
  • the specific field may be present in each octet starting with the AC field.
  • the specific field in the BFR MAC-CE 100 or 200 may be present by using/reusing one of the following:
  • the specific field indicates ‘0’ , at least some or all (beam related) links for transmitting PDCCH scheduled by CORESET (s) associated with CORESETPoolIndex value 0 may be failed. If the specific field indicates ‘1’ , at least some or all (beam related) links for transmitting PDCCH scheduled by CORESET (s) associated with CORESETPoolIndex value 1 may be failed.
  • a TRP-specific BFR procedure for single-DCI multiple TRP scenario is provided. Further, a mechanism of enabling an implicit BFD RS selection for single-DCI multiple TRP scenario is provided.
  • a UE may (be configured to) communicate with a first TRP.
  • the UE may (be configured to) communicate with a second TRP.
  • the UE may communicate with the first TRP and the second TRP at least within a serving cell and/or on a component carrier.
  • the UE may communicate with a network via the first TRP and the second TRP.
  • the serving cell may be a primary cell or a secondary cell.
  • the UE may receive a MAC-CE for activating/indicating a set of TCI states for (receiving) PDSCH.
  • the MAC-CE may activate or indicate the set of TCI states to map with each or some codepoints in a TCI field in a DL scheduling DCI.
  • the MAC-CE may map two TCI states with one TCI field codepoint.
  • the MAC-CE may map one TCI state with one TCI field codepoint. At least one TCI field codepoint in a DL scheduling DCI with TCI field present may indicate two TCI states.
  • the UE may not be configured by higher layer parameter PDCCH-Config that contains two different values of CORESETPoolIndex in different ControlResourceSets.
  • the UE may determine or detect whether or not (pre-determined) beam (s) /links (s) related to the first TRP in a serving cell is failed.
  • the UE may determine or detect, based on measure result of a first set of RS, whether or not (pre-determined) beam (s) /links (s) related to the first TRP in a serving cell is failed.
  • the UE may determine or detect (pre-determined) beam (s) /links (s) related to the first TRP in the serving cell is failed when (or if) detecting all (or some) qualities of the first set of RS are below/above a first threshold.
  • the first threshold may be associated with a block error rate (BLER) value.
  • the UE may determine or detect whether or not (pre-determined) beam (s) /links (s) related to the second TRP in a serving cell is failed.
  • the UE may determine or detect, based on measure result of a second set of RS, whether or not (pre-determined) beam (s) /links (s) related to the second TRP in a serving cell is failed.
  • the UE may determine or detect (pre-determined) beam (s) /links (s) related to the second TRP in the serving cell is failed when (or if) detecting all (or some) qualities of the second set of RS are below/above a second threshold.
  • the second threshold may be associated with a BLER value.
  • the first set of RS and/or the second set of RS may be a RS set used for beam failure detection.
  • the UE may receive configuration of the first set of RS.
  • the UE may receive configuration of the second set of RS.
  • the UE may determine or select the first set of RS based on a pre-determined rule.
  • the UE may determine or select the second set of RS based on a pre-determined rule.
  • the UE may determine or select the first set of RS based on PDCCH DMRS (s) of some or all monitored CORESET (s) .
  • the UE may determine or select the first set of RS based on PDCCH DMRS (s) of some or all monitored CORESET (s) in active BWP of the serving cell.
  • the UE may determine or select the first set of RS based on source RS (s) associated with TCI state (s) for receiving some or all monitored CORESET (s) .
  • the UE may determine or select the first set of RS based on source RS (s) associated with TCI state (s) for receiving some or all monitored CORESET (s) in active BWP of the serving cell.
  • the UE may determine or select the second set of RS based on at least one of the following:
  • the source RS (s) associated with TCI state (s) activated e.g., by MAC-CE for receiving PDSCH;
  • a MAC-CE for activating TCI states for receiving PDSCH indicates the following TCI state IDs: (0, (2, 3) , (7, 8) , 15, 23, 24) .
  • (2, 3) and (7, 8) are mapped with TCI codepoint 1 and 2 respectively.
  • TCI state 3 and TCI state 8 are the second-positioned TCI states.
  • the UE may receive configuration of a first CSI-RS resource set.
  • the UE may receive configuration of a second CSI-RS resource set.
  • the first CSI-RS resource set may be configured with or associated with a first value of an index.
  • the second CSI-RS resource set may be configured with or associated with a second value of the index.
  • the first CSI-RS resource set may contain periodic CSI-RS (s) .
  • the second CSI-RS resource set may contain periodic CSI-RS (s) .
  • the index may be an TRP-related identifier.
  • the first value of the index may be related to the first TRP.
  • the second value of the index may be related to the second TRP.
  • the UE may determine or select the first set of RS based on one or more source RS (s) of TCI states (s) for receiving monitored CORESETs, where the one or more source RS (s) are associated with the first CSI-RS resource set.
  • the UE may determine or select the second set of RS based on one or more source RS (s) of TCI states (s) for receiving monitored CORESETs, where the one or more source RS (s) are associated with the second CSI-RS resource set.
  • the network may be required to configure the second set of RS.
  • the network may prevent from not configuring the second set of RS.
  • the network may be required to configure the first set of RS.
  • the network may prevent from not configuring the first set of RS.
  • the UE may transmit a first BFRQ to the network.
  • the UE may transmit a second BFRQ to the network.
  • the UE may transmit the first BFRQ when (or if) detecting all (or some) qualities of the first set of RS are below/above a first threshold.
  • the UE may transmit the second BFRQ when (or if) detecting all (or some) qualities of the second set of RS are below/above a second threshold.
  • the first BFRQ may be a MAC-CE.
  • the second BFRQ may be a MAC-CE.
  • the first BFRQ and the second BFRQ may be transmitted by the same type of MAC-CE.
  • the UE may perform at least one of the following operations:
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing two TCI states;
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing two TCI states, until the UE receives a MAC-CE updating the mapping of TCI field codepoint and TCI states;
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing two TCI states, when (or if) the second BFRR does not include or carry a MAC-CE updating the mapping of TCI field codepoint and TCI states;
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the second TRP (identifier) ;
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the second TRP (identifier) , until the UE receives a MAC-CE updating the mapping of TCI field codepoint and TCI state (s) ;
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the second TRP (identifier) , when (or if) the second BFRR does not include or carry a MAC-CE updating the mapping of TCI field codepoint and TCI states.
  • the network may perform at least one of the following operations:
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing two TCI states;
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing two TCI states, until the network transmits a MAC-CE updating the mapping of TCI field codepoint and TCI states (and/or receives acknowledgement from the UE for the MAC-CE, if any) ;
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing two TCI states, when (or if) the second BFRR does not include or carry a MAC-CE updating the mapping of TCI field codepoint and TCI states;
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the second TRP (identifier) ;
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the second TRP (identifier) , until the network transmits or the UE receives a MAC-CE updating the mapping of TCI field codepoint and TCI state (s) ;
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the first TRP (identifier) , when (or if) the second BFRR does not include or carry a MAC-CE updating the mapping of TCI field codepoint and TCI states.
  • the UE may perform at least one of the following operations:
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing two TCI states;
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing two TCI states, until the UE receives a MAC-CE updating the mapping of TCI field codepoint and TCI states;
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing two TCI states, when (or if) the first BFRR does not include or carry a MAC-CE updating the mapping of TCI field codepoint and TCI states;
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the first TRP (identifier) ;
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the first TRP (identifier) , until the UE receives a MAC-CE updating the mapping of TCI field codepoint and TCI state (s) ;
  • the UE may not expect to be indicated to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the first TRP (identifier) , when (or if) the first BFRR does not include or carry a MAC-CE updating the mapping of TCI field codepoint and TCI states.
  • the network may perform at least one of the following operations:
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing two TCI states;
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing two TCI states, until the network transmits a MAC-CE updating the mapping of TCI field codepoint and TCI states (and/or receives acknowledgement from the UE for the MAC-CE, if any) ;
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing two TCI states, when (or if) the first BFRR does not include or carry a MAC-CE updating the mapping of TCI field codepoint and TCI states;
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the first TRP (identifier) ;
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the first TRP (identifier) , until the network transmits or the UE receives a MAC-CE updating the mapping of TCI field codepoint and TCI state (s) ;
  • the network may prevent from or may not be allowed to indicate the UE to receive a PDSCH by a TCI field codepoint containing TCI state (s) associated with the first TRP (identifier) , when (or if) the first BFRR does not include or carry a MAC-CE updating the mapping of TCI field codepoint and TCI states.
  • the first BFRR may be required to contain or indicate information of updating mapping of TCI field codepoint and TCI states.
  • the second BFRR may be required to contain or indicate information of updating mapping of TCI field codepoint and TCI states.
  • the first BFRR may be required to include a MAC-CE for updating mapping of TCI field codepoint and TCI states.
  • the second BFRR may be required to include a MAC-CE for updating mapping of TCI field codepoint and TCI states.
  • the procedure (s) /mechanism (s) for recovering beam related link (s) with one or some of the transmission (and/or reception) node (s) in at least one serving cell or component carrier are provided.
  • FIG 3 illustrates an overview of UE RRC state machine and state transitions in NR.
  • different RRC states such as the NR RRC_CONNECTED state 302, the NR RRC_IDLE 304, and the NR RRC_INACTIVE 306 are illustrated.
  • a UE has only one RRC state in NR at one time.
  • Figure 4 illustrates an overview of UE state machine and state transitions in NR as well as the mobility procedures supported between NR/5GC E-UTRA/EPC and E-UTRA/5GC.
  • a UE may be in an RRC_CONNECTED state or an RRC_INACTIVE state, where the RRC_CONNECTED state may be the EUTRA RRC_CONNECTED state 402 or the NR RRC_CONNECTED state 404, and the RRC_INACTIVE state may be the EUTRA RRC_INACTIVE state 406 or the NR RRC_INACTIVE state 408.
  • the UE may be in the RRC_IDLE state, for example, the EUTRA RRC_IDLE state 410 or the NR RRC_IDLE state 412.
  • the BeamFailureRecoveryConfig IE may be used to configure the UE with RACH resources and candidate beams for beam failure recovery in case of beam failure detection.
  • An example data structure of the BeamFailureRecoveryConfig IE represented by Abstract Syntax Notation One (ASN. 1) is in Table 2.
  • the BeamFailureRecoverySCellConfig IE is used to configure the UE with candidate beams for beam failure recovery in case of beam failure detection in SCell.
  • An example data structure of the BeamFailureRecoverySCellConfig IE represented by ASN. 1 is in Table 3.
  • DCI transports downlink control information for one or more cells with one RNTI.
  • the following coding steps can be identified:
  • Each field is mapped in the order in which it appears in the description, including the zero-padding bit (s) , if any, with the first field mapped to the lowest order information bit a 0 and each successive field mapped to higher order information bits.
  • the most significant bit of each field is mapped to the lowest order information bit for that field, e.g., the most significant bit of the first field is mapped to a 0 .
  • each DCI format is determined by the configuration of the corresponding active bandwidth part of the scheduled cell and shall be adjusted if necessary.
  • a UE can be provided, for each BWP of a serving cell, a set of periodic CSI-RS resource configuration indexes by failureDetectionResources and a set of periodic CSI-RS resource configuration indexes and/or SS/PBCH block indexes by candidateBeamRSList or candidateBeamRSListExt-r16 or candidateBeamRSSCellList-r16 for radio link quality measurements on the BWP of the serving cell.
  • the UE determines the set to include periodic CSI-RS resource configuration indexes with same values as the RS indexes in the RS sets indicated by TCI-State for respective CORESETs that the UE uses for monitoring PDCCH and, if there are two RS indexes in a TCI state, the set includes RS indexes with QCL-TypeD configuration for the corresponding TCI states.
  • the UE expects the set to include up to two RS indexes.
  • the UE expects single port RS in the set
  • the UE expects single-port or two-port CSI-RS with frequency density equal to 1 or 3 REs per RB in the set
  • the thresholds Qout, LR and Qin, LR correspond to the default value of rlmInSyncOutOfSyncThreshold for Qout, and to the value provided by rsrp-ThresholdSSB or rsrp-ThresholdBFR-r16, respectively.
  • the physical layer in the UE assesses the radio link quality according to the set of resource configurations against the threshold Qout, LR.
  • the UE assesses the radio link quality only according to periodic CSI-RS resource configurations, or SS/PBCH blocks on the PCell or the PSCell, that are quasi co-located with the DM-RS of PDCCH receptions monitored by the UE.
  • the UE applies the Qin, LR threshold to the L1-RSRP measurement obtained from a SS/PBCH block.
  • the UE applies the Qin, LR threshold to the L1-RSRP measurement obtained for a CSI-RS resource after scaling a respective CSI-RS reception power with a value provided by powerControlOffsetSS.
  • the physical layer in the UE provides an indication to higher layers when the radio link quality for all corresponding resource configurations in the set that the UE uses to assess the radio link quality is worse than the threshold Qout, LR.
  • the physical layer informs the higher layers when the radio link quality is worse than the threshold Qout, LR with a periodicity determined by the maximum between the shortest periodicity among the periodic CSI-RS configurations, and/or SS/PBCH blocks on the PCell or the PSCell, in the set that the UE uses to assess the radio link quality and 2 msec.
  • the physical layer provides an indication to higher layers when the radio link quality is worse than the threshold Qout, LR with a periodicity determined.
  • the UE upon request from higher layers, the UE provides to higher layers the periodic CSI-RS configuration indexes and/or SS/PBCH block indexes from the set and the corresponding L1-RSRP measurements that are larger than or equal to the Qin, LR threshold.
  • the UE upon request from higher layers, the UE indicates to higher layers whether there is at least one periodic CSI-RS configuration index and/or SS/PBCH block index from the set with corresponding L1-RSRP measurements that are larger than or equal to the Qin, LR threshold, and provides the periodic CSI-RS configuration indexes and/or SS/PBCH block indexes from the set and the corresponding L1-RSRP measurements that are larger than or equal to the Qin, LR threshold, if any.
  • a UE can be provided a CORESET through a link to a search space set provided by recoverySearchSpaceId, for monitoring PDCCH in the CORESET. If the UE is provided recoverySearchSpaceId, the UE does not expect to be provided another search space set for monitoring PDCCH in the CORESET associated with the search space set provided by recoverySearchSpaceId.
  • the UE can be provided, by PRACH-ResourceDedicatedBFR, a configuration for PRACH transmission.
  • PRACH-ResourceDedicatedBFR a configuration for PRACH transmission.
  • the UE monitors PDCCH in a search space set provided by recoverySearchSpaceId for detection of a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI starting from slot n+4 within a window configured by BeamFailureRecoveryConfig.
  • the UE assumes the same antenna port quasi-collocation parameters as the ones associated with index q new until the UE receives by higher layers an activation for a TCI state or any of the parameters tci-StatesPDCCH-ToAddList and/or tci-StatesPDCCH-ToReleaseList.
  • the UE After the UE detects a DCI format with CRC scrambled by 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 tci-StatesPDCCH-ToAddList and/or tci-StatesPDCCH-ToReleaseList.
  • the UE transmits a PUCCH on a same cell as the PRACH transmission using
  • the UE assumes same antenna port quasi-collocation parameters as the ones associated with index q new for PDCCH monitoring in a CORESET with index 0.
  • a UE can be provided, by schedulingRequestID-BFR-SCell-r16, a configuration for PUCCH transmission with a link recovery request (LRR) .
  • the UE can transmit in a first PUSCH MAC CE providing index (es) for at least corresponding SCell (s) with radio link quality worse than Qout, LR, indication (s) of presence of q new for corresponding SCell (s) , and index (es) q new for a periodic CSI-RS configuration or for a SS/PBCH block provided by higher layers, if any, for corresponding SCell (s) .
  • Layer 1 Prior to initiation of the physical random access procedure, Layer 1 receives from higher layers a set of SS/PBCH block indexes and provides to higher layers a corresponding set of RSRP measurements.
  • Layer 1 may receive from higher layers an indication to perform a Type-1 random access procedure, or a Type-2 random access procedure.
  • Layer 1 Prior to initiation of the physical random access procedure, Layer 1 receives the following information from the higher layers:
  • PRACH physical random access channel
  • the Type-1 L1 random access procedure includes the transmission of random access preamble (Msg1) in a PRACH, random access response (RAR) message with a PDCCH/PDSCH (Msg2) , and when applicable, the transmission of a PUSCH scheduled by a RAR UL grant, and PDSCH for contention resolution.
  • Msg1 random access preamble
  • RAR random access response
  • Msg2 PDCCH/PDSCH
  • the Type-2 L1 random access procedure includes the transmission of random access preamble in a PRACH and of a PUSCH (MsgA) and the reception of a RAR message with a PDCCH/PDSCH (MsgB) , and when applicable, the transmission of a PUSCH scheduled by a fallback RAR UL grant, and PDSCH for contention resolution.
  • MsgA random access preamble in a PRACH and of a PUSCH
  • MsgB PDCCH/PDSCH
  • a PRACH transmission is with a same SCS as a PRACH transmission initiated by higher layers.
  • a UE is configured with two UL carriers for a serving cell and the UE detects a PDCCH order, the UE uses the UL/SUL indicator field value from the detected PDCCH order to determine the UL carrier for the corresponding PRACH transmission.
  • Physical random access procedure is triggered upon request of a PRACH transmission by higher layers or by a PDCCH order.
  • a configuration by higher layers for a PRACH transmission includes the following:
  • a preamble index, a preamble SCS, P PRACH, target , a corresponding RA-RNTI, and a PRACH resource is included in the preamble index.
  • a PRACH is transmitted using the selected PRACH format with transmission power P PRACH, b, f, c (i) on the indicated PRACH resource.
  • a UE For Type-1 random access procedure, a UE is provided a number N of SS/PBCH block indexes associated with one PRACH occasion and a number R of contention based preambles per SS/PBCH block index per valid PRACH occasion by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.
  • a UE For Type-2 random access procedure with common configuration of PRACH occasions with Type-1 random access procedure, a UE is provided a number N of SS/PBCH block indexes associated with one PRACH occasion by ssb-perRACH-OccasionAndCB-PreamblesPerSSB and a number Q of contention based preambles per SS/PBCH block index per valid PRACH occasion by msgA-CB-PreamblesPerSSB.
  • the PRACH transmission can be on a subset of PRACH occasions associated with a same SS/PBCH block index for a UE provided with a PRACH mask index by msgA-ssb-sharedRO-MaskIndex.
  • a UE For Type-2 random access procedure with separate configuration of PRACH occasions with Type-1 random access procedure, a UE is provided a number N of SS/PBCH block indexes associated with one PRACH occasion and a number R of contention based preambles per SS/PBCH block index per valid PRACH occasion by ssb-perRACH-OccasionAndCB-PreamblesPerSSB-msgA when provided; otherwise, by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.
  • Type-1 random access procedure or for Type-2 random access procedure with separate configuration of PRACH occasions from Type 1 random access procedure, if N ⁇ 1, one SS/PBCH block index is mapped to 1/N consecutive valid PRACH occasions and R contention based preambles with consecutive indexes associated with the SS/PBCH block index per valid PRACH occasion start from preamble index 0.
  • R contention based preambles with consecutive indexes associated with SS/PBCH block index n, 0 ⁇ n ⁇ N-1, per valid PRACH occasion start from preamble index where is provided by totalNumberOfRA-Preambles for Type-1 random access procedure, or by msgA-totalNumberOfRA-Preambles for Type-2 random access procedure with separate configuration of PRACH occasions from a Type 1 random access procedure, and is an integer multiple of N.
  • Type-2 random access procedure with common configuration of PRACH occasions with Type-1 random access procedure if N ⁇ 1, one SS/PBCH block index is mapped to 1/N consecutive valid PRACH occasions and Q contention based preambles with consecutive indexes associated with the SS/PBCH block index per valid PRACH occasion start from preamble index R. If N ⁇ 1, Q contention based preambles with consecutive indexes associated with SS/PBCH block index n, 0 ⁇ n ⁇ N-1, per valid PRACH occasion start from preamble index where is provided by totalNumberOfRA-Preambles for Type-1 random access procedure.
  • a UE For link recovery, a UE is provided N SS/PBCH block indexes associated with one PRACH occasion by ssb-perRACH-Occasion in BeamFailureRecoveryConfig.
  • N SS/PBCH block indexes associated with one PRACH occasion by ssb-perRACH-Occasion in BeamFailureRecoveryConfig.
  • RACH-ConfigDedicated if cfra is provided, a UE is provided N SS/PBCH block indexes associated with one PRACH occasion by ssb-perRACH-Occasion in occasions. If N ⁇ 1, one SS/PBCH block index is mapped to 1/N consecutive valid PRACH occasions. If N ⁇ 1, all consecutive N SS/PBCH block indexes are associated with one PRACH occasion.
  • SS/PBCH block indexes provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon are mapped to valid PRACH occasions in the following order:
  • An association period, starting from frame 0, for mapping SS/PBCH block indexes to PRACH occasions is the smallest value in the set determined by the PRACH configuration period according Table 5 such that SS/PBCH block indexes are mapped at least once to the PRACH occasions within the association period, where a UE obtains from the value of ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon. If after an integer number of SS/PBCH block indexes to PRACH occasions mapping cycles within the association period there is a set of PRACH occasions or PRACH preambles that are not mapped to SS/PBCH block indexes, no SS/PBCH block indexes are mapped to the set of PRACH occasions or PRACH preambles.
  • An association pattern period includes one or more association periods and is determined so that a pattern between PRACH occasions and SS/PBCH block indexes repeats at most every 160 msec. PRACH occasions not associated with SS/PBCH block indexes after an integer number of association periods, if any, are not used for PRACH transmissions.
  • the PRACH mask index field indicates the PRACH occasion for the PRACH transmission where the PRACH occasions are associated with the SS/PBCH block index indicated by the SS/PBCH block index field of the PDCCH order.
  • the PRACH mask index is indicated by ra-ssb-OccasionMaskIndex which indicates the PRACH occasions for the PRACH transmission where the PRACH occasions are associated with the selected SS/PBCH block index.
  • the PRACH occasions are mapped consecutively per corresponding SS/PBCH block index.
  • the indexing of the PRACH occasion indicated by the mask index value is reset per mapping cycle of consecutive PRACH occasions per SS/PBCH block index.
  • the UE selects for a PRACH transmission the PRACH occasion indicated by PRACH mask index value for the indicated SS/PBCH block index in the first available mapping cycle.
  • the ordering of the PRACH occasions is described as follows:
  • a value of ra-OccasionList indicates a 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 per association pattern period.
  • the candidate SS/PBCH block index of the SS/PBCH block may correspond to the SS/PBCH block index provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon.
  • the candidate SS/PBCH block index of the SS/PBCH block may correspond to the SS/PBCH block index provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon.
  • the N gap values for different preamble SCS ⁇ are provided in Table 6.
  • the UE If a random access procedure is initiated by a PDCCH order, the UE, if requested by higher layers, transmits a PRACH in the selected PRACH occasion for which a time between the last symbol of the PDCCH order reception and the first symbol of the PRACH transmission is larger than or equal to N T, 2 + ⁇ BWPSwitching + ⁇ Delay +T switch msec, where
  • N T, 2 is a time duration of N 2 symbols corresponding to a PUSCH preparation time for UE processing capability 1 assuming ⁇ corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH order and the SCS configuration of the corresponding PRACH transmission;
  • ⁇ BWPSwitching 0 if the active UL BWP does not change and ⁇ BWPSwitching is defined in TS 38.133, otherwise
  • - T switch is a switching gap duration as defined in TS 38.214.
  • a UE transmits a PUSCH, when applicable, after transmitting a PRACH.
  • the UE encodes a transport block provided for the PUSCH transmission using redundancy version number 0.
  • a UE does not transmit a PUSCH in a PUSCH occasion if the PUSCH occasion associated with a DMRS resource is not mapped to a preamble of valid PRACH occasions or if the associated PRACH preamble is not transmitted, UE can transmit a PRACH preamble in a valid PRACH occasion if the PRACH preamble is not mapped to a valid PUSCH occasion.
  • a mapping between one or multiple PRACH preambles and a PUSCH occasion associated with a DMRS resource is per PUSCH configuration.
  • a UE determines time resources and frequency resources for PUSCH occasions in an active UL BWP from msgA-PUSCH-Config for the active UL BWP. If the active UL BWP is not the initial UL BWP and msgA-PUSCH-Config is not provided for the active UL BWP, the UE uses the msgA-PUSCH-Config provided for the initial UL BWP.
  • a UE determines a first interlace or first RB for a first PUSCH occasion in an active UL BWP respectively from interlaceIndexFirstPO-MsgA-PUSCH or from frequencyStartMsgA-PUSCH that provides an offset, in number of RBs in the active UL BWP, from a first RB of the active UL BWP.
  • a PUSCH occasion includes a number of interlaces or a number of RBs provided by nrofInterlacesPerMsgA-PO or by nrofPRBs-perMsgA-PO, respectively.
  • Consecutive PUSCH occasions in the frequency domain of an UL BWP are separated by a number of RBs provided by guardBandMsgA-PUSCH.
  • a number N f of PUSCH occasions in the frequency domain of an UL BWP is provided by nrMsgA-PO-FDM.
  • msgA-PUSCH-timeDomainAllocation provides a SLIV and a PUSCH mapping type for a PUSCH transmission by indicating first maxNrofUL-Allocations values from PUSCH-TimeDomainResourceAllocationList, if PUSCH-TimeDomainResourceAllocationList is provided in PUSCH-ConfigCommon; and/or entries from table 6.1.2.1.1-2 in TS 38.214, if PUSCH-TimeDomainResourceAllocationList is not provided in PUSCH-ConfigCommon.
  • the msgA-PUSCH-timeDomainAllocation provides a SLIV by startSymbolAndLengthMsgA-PO, and a PUSCH mapping type by mappingTypeMsgA-PUSCH for a PUSCH transmission.
  • a UE For mapping one or multiple preambles of a PRACH slot to a PUSCH occasion associated with a DMRS resource, determines a first slot for a first PUSCH occasion in an active UL BWP from msgA-PUSCH-TimeDomainOffset that provides an offset, in number of slots in the active UL BWP, relative to the start of a PUSCH slot including the start of each PRACH slot.
  • the UE does not expect to have a PRACH preamble transmission and a PUSCH transmission with a msgA in a PRACH slot or in a PUSCH slot, or to have overlapping msgA PUSCH occasions for a MsgA PUSCH configuration.
  • the UE expects that a first PUSCH occasion in each slot has a same SLIV for a PUSCH transmission that is provided by startSymbolAndLengthMsgA-PO.
  • Consecutive PUSCH occasions within each slot are separated by guardPeriodMsgA-PUSCH symbols and have same duration.
  • a number N t of time domain PUSCH occasions in each slot is provided by nrofMsgA-PO-perSlot and a number N s of consecutive slots that include PUSCH occasions is provided by nrofSlotsMsgA-PUSCH.
  • a UE is provided a DMRS configuration for a PUSCH transmission in a PUSCH occasion in an active UL BWP by msgA-DMRS-Configuration.
  • a UE is provided an MCS for data information in a PUSCH transmission for a PUSCH occasion by msgA-MCS.
  • the frequency offset for the second hop is determined using msgA-HoppingBits instead of N UL, hop . If guardPeriodMsgA-PUSCH is provided, a first symbol of the second hop is separated by guardPeriodMsgA-PUSCH symbols from the end of a last symbol of the first hop; otherwise, there is no time separation of the PUSCH transmission before and after frequency hopping. If a UE is provided with useInterlacePUCCH-PUSCH in BWP-UplinkCommon, the UE shall transmit PUSCH without frequency hopping.
  • a PUSCH transmission uses a same spatial filter as an associated PRACH transmission.
  • a UE determines whether or not to apply transform precoding for a PUSCH transmission.
  • a PUSCH occasion for PUSCH transmission is defined by a frequency resource and a time resource, and is associated with a DMRS resource.
  • the DMRS resources are provided by msgA-DMRS-Configuration.
  • a DMRS resource index DMRS id is determined first in an ascending order of a DMRS port index and second in an ascending order of a DMRS sequence index;
  • N preamble ceil (T preamble /T PUSCH )
  • T preamble is a total number of valid PRACH occasions per association pattern period multiplied by the number of preambles per valid PRACH occasion provided by msgA-PUSCH-PreambleGroup
  • T PUSCH is a total number of valid PUSCH occasions per PUSCH configuration per association pattern period multiplied by the number of DMRS resource indexes per valid PUSCH occasion provided by msgA-DMRS-Configuration.
  • a PUSCH occasion is valid if it does not overlap in time and frequency with any PRACH occasion associated with either a Type-1 random access procedure or a Type-2 random access procedure. Additionally, for unpaired spectrum and for SS/PBCH blocks with indexes provided by ssb-PositionsInBurst in SIB1 or by ServingCellConfigCommon
  • a PUSCH occasion is valid if the PUSCH occasion does not precede a SS/PBCH block in the PUSCH slot and starts at least N gap symbols after a last SS/PBCH block symbol, where N gap is provided in Table 6.
  • a UE In response to a PRACH transmission, a UE attempts to detect a DCI format 1_0 with CRC scrambled by a corresponding RA-RNTI during a window controlled by higher layers.
  • the window starts at the first symbol of the earliest CORESET the UE is configured to receive PDCCH for Type1-PDCCH CSS set that is at least one symbol, after the last symbol of the PRACH occasion corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for Type1-PDCCH CSS set.
  • the length of the window in number of slots, based on the SCS for Type1-PDCCH CSS set, is provided by ra-ResponseWindow.
  • the UE If the UE detects the DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI and LSBs of a SFN field in the DCI format 1_0, if included and applicable, are same as corresponding LSBs of the SFN where the UE transmitted PRACH, and the UE receives a transport block in a corresponding PDSCH within the window, the UE passes the transport block to higher layers.
  • the higher layers parse the transport block for a random access preamble identity (RAPID) associated with the PRACH transmission. If the higher layers identify the RAPID in RAR message (s) of the transport block, the higher layers indicate an uplink grant to the physical layer. This is referred to as random access response (RAR) UL grant in the physical layer.
  • RAPID random access preamble identity
  • the UE does not detect the DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI within the window, or if the UE detects the DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI within the window and LSBs of a SFN field in the DCI format 1_0, if included and applicable, are not same as corresponding LSBs of the SFN where the UE transmitted PRACH, or if the UE does not correctly receive the transport block in the corresponding PDSCH within the window, or if the higher layers do not identify the RAPID associated with the PRACH transmission from the UE, the higher layers can indicate to the physical layer to transmit a PRACH.
  • the UE is expected to transmit a PRACH no later than N T, 1 +0.75 msec after the last symbol of the window, or the last symbol of the PDSCH reception, where N T, 1 is a time duration of N 1 symbols corresponding to a PDSCH processing time for UE processing capability 1 assuming ⁇ corresponds to the smallest SCS configuration among the SCS configurations for the PDCCH carrying the DCI format 1_0, the corresponding PDSCH when additional PDSCH DM-RS is configured, and the corresponding PRACH.
  • N 1, 0 14.
  • the UE may assume same DM-RS antenna port quasi co-location properties as for a SS/PBCH block or a CSI-RS resource the UE used for PRACH association, regardless of whether or not the UE is provided TCI-State for the CORESET where the UE receives the PDCCH with the DCI format 1_0.
  • the UE may assume that the PDCCH that includes the DCI format 1_0 and the PDCCH order have same DM-RS antenna port quasi co-location properties.
  • the UE may assume the DM-RS antenna port quasi co-location properties of the CORESET associated with the Type1-PDCCH CSS set for receiving the PDCCH that includes the DCI format 1_0.
  • a RAR UL grant schedules a PUSCH transmission from the UE.
  • the contents of the RAR UL grant, starting with the MSB and ending with the LSB, are given in Table 7.
  • the UE transmits the PUSCH without frequency hopping; otherwise, the UE transmits the PUSCH with frequency hopping.
  • the UE determines the MCS of the PUSCH transmission from the first sixteen indexes of the applicable MCS index table for PUSCH.
  • the TPC command value ⁇ msg2, b, f, c is used for setting the power of the PUSCH transmission, and is interpreted.
  • the CSI request field is reserved.
  • the ChannelAccess-CPext field indicates a channel access type and CP extension for operation with shared spectrum channel access.
  • Random Access Response Grant Content field size is shown in Table 7.
  • TPC Command ⁇ msg2, b, f, c for PUSCH is shown in Table 8.
  • the UE receives subsequent PDSCH using same SCS as for the PDSCH reception providing the RAR message.
  • the UE procedure is as described in TS 38.321.
  • a UE In response to a transmission of a PRACH and a PUSCH, or to a transmission of only a PRACH if the PRACH preamble is mapped to a valid PUSCH occasion, a UE attempts to detect a DCI format 1_0 with CRC scrambled by a corresponding MsgB-RNTI during a window controlled by higher layers.
  • the window starts at the first symbol of the earliest CORESET the UE is configured to receive PDCCH for Type1-PDCCH CSS set that is at least one symbol, after the last symbol of the PUSCH occasion corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for Type1-PDCCH CSS set.
  • the length of the window in number of slots, based on the SCS for Type1-PDCCH CSS set, is provided by msgB-ResponseWindow.
  • a UE In response to a transmission of a PRACH, if the PRACH preamble is not mapped to a valid PUSCH occasion, a UE attempts to detect a DCI format 1_0 with CRC scrambled by a corresponding MsgB-RNTI during a window controlled by higher layers.
  • the window starts at the first symbol of the earliest CORESET the UE is configured to receive PDCCH for Type1-PDCCH CSS set that is at least one symbol, after the last symbol of the PRACH occasion corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for Type1-PDCCH CSS set.
  • the length of the window in number of slots, based on the SCS for Type1-PDCCH CSS set, is provided by msgB-ResponseWindow.
  • the UE If the UE detects the DCI format 1_0, with CRC scrambled by the corresponding MsgB-RNTI and LSBs of a SFN field in the DCI format 1_0, if applicable, are same as corresponding LSBs of the SFN where the UE transmitted PRACH, and the UE receives a transport block in a corresponding PDSCH within the window, the UE passes the transport block to higher layers.
  • the higher layers indicate to the physical layer
  • RAR message (s) is for fallbackRAR and a random access preamble identity (RAPID) associated with the PRACH transmission is identified
  • RAPID random access preamble identity
  • PUCCH resource indicator field 4 bits in the successRAR from a PUCCH resource set that is provided by pucch-ResourceCommon;
  • a slot for the PUCCH transmission is indicated by a PDSCH-to-HARQ_feedback timing indicator field of 3 bits in the successRAR having a value k from ⁇ 1, 2, 3, 4, 5, 6, 7, 8 ⁇ and, with reference to slots for PUCCH transmission having duration T slot , the slot is determined as n+k+ ⁇ , where n is a slot of the PDSCH reception and ⁇ is as defined for PUSCH transmission.
  • the UE does not expect the first symbol of the PUCCH transmission to be after the last symbol of the PDSCH reception by a time smaller than N T, 1 +0.5 msec where N T, 1 is the PDSCH processing time for UE processing capability 1.
  • a channel access type and CP extension for a PUCCH transmission is indicated by a ChannelAccess-CPext field in the successRAR.
  • the PUCCH transmission is with a same spatial domain transmission filter and in a same active UL BWP as a last PUSCH transmission.
  • the UE If the UE detects the DCI format 1_0 with CRC scrambled by a C-RNTI and a transport block in a corresponding PDSCH within the window, the UE transmits a PUCCH with HARQ-ACK information having ACK value if the UE correctly detects the transport block or NACK value if the UE incorrectly detects the transport block and the time alignment timer is running.
  • the UE may assume same DM-RS antenna port quasi co-location properties as for a SS/PBCH block the UE used for PRACH association, regardless of whether or not the UE is provided TCI-State for the CORESET where the UE receives the PDCCH with the DCI format 1_0.
  • the UE does not expect to be indicated to transmit the PUCCH with the HARQ-ACK information at a time that is prior to a time when the UE applies a TA command that is provided by the transport block. If the UE does not detect the DCI format 1_0 with CRC scrambled by the corresponding MsgB-RNTI within the window, or if the UE detects the DCI format 1_0 with CRC scrambled by the corresponding MsgB-RNTI within the window and LSBs of a SFN field in the DCI format 1_0, if applicable, are not same as corresponding LSBs of the SFN where the UE transmitted the PRACH, or if the UE does not correctly receive the transport block in the corresponding PDSCH within the window, or if the higher layers do not identify the RAPID associated with the PRACH transmission from the UE, the higher layers can indicate to the physical layer to transmit only PRACH according to Type-1 random access procedure or to transmit both PRACH and PUSCH according to Type-2
  • the UE is expected to transmit a PRACH no later than N T, 1 +0.75 msec after the last symbol of the window, or the last symbol of the PDSCH reception, where N T, 1 is a time duration of N 1 symbols corresponding to a PDSCH processing time for UE processing capability 1 when additional PDSCH DM-RS is configured.
  • N T, 1 is a time duration of N 1 symbols corresponding to a PDSCH processing time for UE processing capability 1 when additional PDSCH DM-RS is configured.
  • N 1, 0 14.
  • the UE receives subsequent PDSCH using same SCS as for the PDSCH reception providing the RAR message.
  • the UE does not detect the DCI format 1_0 with CRC scrambled by the corresponding MsgB-RNTI within the window, or if the UE detects the 1_0 with CRC scrambled by the corresponding MsgB-RNTI within the window and LSBs of a SFN field in the DCI format 1_0, if applicable, are not same as corresponding LSBs of the SFN where the UE transmitted the PRACH, or the UE does not correctly receive a corresponding transport block within the window.
  • An active UL BWP for a PUSCH transmission scheduled by a RAR UL grant is indicated by higher layers.
  • the frequency domain resource allocation is by uplink resource allocation type 1.
  • a UE processes the frequency domain resource assignment field as the behavior described in Table 9:
  • the frequency domain resource allocation is by uplink resource allocation type 2.
  • a UE processes the frequency domain resource assignment field as follows:
  • the UE interprets the X MSBs of the truncated frequency domain resource assignment field for the active UL BWP as for the X MSBs of the frequency domain resource assignment field in DCI format 0_0.
  • the RB set of the active UL BWP is the RB set of the PRACH transmission associated with the RAR UL grant.
  • a UE determines whether or not to apply transform precoding.
  • the frequency offset for the second hop is given in Table 10.
  • a SCS for the PUSCH transmission is provided by subcarrierSpacing in BWP-UplinkCommon.
  • a UE transmits PRACH and the PUSCH on a same uplink carrier of a same serving cell.
  • a UE transmits a transport block in a PUSCH scheduled by a RAR UL grant in a corresponding RAR message using redundancy version number 0. If a TC-RNTI is provided by higher layers, the scrambling initialization of the PUSCH corresponding to the RAR UL grant is by TC-RNTI. Otherwise, the scrambling initialization of the PUSCH corresponding to the RAR UL grant is by C-RNTI. Msg3 PUSCH retransmissions, if any, of the transport block, are scheduled by a DCI format 0_0 with CRC scrambled by a TC-RNTI provided in the corresponding RAR message. The UE always transmits the PUSCH scheduled by a RAR UL grant without repetitions.
  • a UE With reference to slots for a PUSCH transmission scheduled by a RAR UL grant, if a UE receives a PDSCH with a RAR message ending in slot n for a corresponding PRACH transmission from the UE, the UE transmits the PUSCH in slot n+k 2 + ⁇ , where k 2 and ⁇ are provided in TS 38.214.
  • the UE In response to a PUSCH transmission scheduled by a RAR UL grant when a UE has not been provided a C-RNTI, the UE attempts to detect a DCI format 1_0 with CRC scrambled by a corresponding TC-RNTI scheduling a PDSCH that includes a UE contention resolution identity. In response to the PDSCH reception with the UE contention resolution identity, the UE transmits HARQ-ACK information in a PUCCH.
  • the PUCCH transmission is within a same active UL BWP as the PUSCH transmission.
  • a minimum time between the last symbol of the PDSCH reception and the first symbol of the corresponding PUCCH transmission with the HARQ-ACK information is equal to N T, 1 +0.5 msec.
  • the UE may assume the PDCCH carrying the DCI format has the same DM-RS antenna port quasi co-location properties as for a SS/PBCH block the UE used for PRACH association regardless of whether or not the UE is provided TCI-State for the CORESET where the UE receives the PDCCH with the DCI format.
  • a UE procedure for determining physical downlink control channel assignment is provided in Table 11.
  • the UE can be configured with a list of up to M TCI-State configurations within the higher layer parameter PDSCH-Config to decode PDSCH according to a detected PDCCH with DCI intended for the UE and the given serving cell, where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC.
  • Each TCI-State contains parameters for configuring a quasi co-location relationship between one or two downlink reference signals and the DM-RS ports of the PDSCH, the DM-RS port of PDCCH or the CSI-RS port (s) of a CSI-RS resource.
  • the quasi co-location relationship is configured by the higher layer parameter qcl-Type1 for the first DL RS, and qcl-Type2 for the second DL RS (if configured) .
  • the QCL types shall not be the same, regardless of whether the references are to the same DL RS or different DL RSs.
  • the quasi co-location types corresponding to each DL RS are given by the higher layer parameter qcl-Type in QCL-Info and may take one of the following values:
  • the UE receives an activation command used to map up to 8 TCI states to the codepoints of the DCI field 'Transmission Configuration Indication' in one CC/DL BWP or in a set of CCs/DL BWPs, respectively.
  • an activation command used to map up to 8 TCI states to the codepoints of the DCI field 'Transmission Configuration Indication' in one CC/DL BWP or in a set of CCs/DL BWPs, respectively.
  • the UE may receive an activation command the activation command is used to map up to 8 combinations of one or two TCI states to the codepoints of the DCI field 'Transmission Configuration Indication' .
  • the UE is not expected to receive more than 8 TCI states in the activation command.
  • the indicated mapping between TCI states and codepoints of the DCI field 'Transmission Configuration Indication' should be applied starting from the first slot that is after slot where m is the SCS configuration for the PUCCH.
  • tci-PresentInDCI is set to "enabled” or tci-PresentInDCI-ForFormat1_2 is configured for the CORESET scheduling the PDSCH, and the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than timeDurationForQCL if applicable
  • the UE may assume that the DM-RS ports of PDSCH of a serving cell are quasi co-located with the SS/PBCH block determined in the initial access procedure with respect to 'QCL-TypeA' , and when applicable, also with respect to'QCL-TypeD' .
  • a UE If a UE is configured with the higher layer parameter tci-PresentInDCI that is set as 'enabled' for the CORESET scheduling the PDSCH, the UE assumes that the TCI field is present in the DCI format 1_1 of the PDCCH transmitted on the CORESET. If a UE is configured with the higher layer parameter tci-PresentInDCI-ForFormat1_2 for the CORESET scheduling the PDSCH, the UE assumes that the TCI field with a DCI field size indicated by tci-PresentInDCI-ForFormat1_2 is present in the DCI format 1_2 of the PDCCH transmitted on the CORESET.
  • the UE assumes that the TCI state or the QCL assumption for the PDSCH is identical to the TCI state or QCL assumption whichever is applied for the CORESET used for the PDCCH transmission.
  • the UE shall use the TCI-State according to the value of the 'Transmission Configuration Indication' field in the detected PDCCH with DCI for determining PDSCH antenna port quasi co-location.
  • the UE may assume that the DM-RS ports of PDSCH of a serving cell are quasi co-located with the RS (s) in the TCI state with respect to the QCL type parameter (s) given by the indicated TCI state if the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than a threshold timeDurationForQCL, where the threshold is based on reported UE capability.
  • the indicated TCI state should be based on the activated TCI states in the slot with the scheduled PDSCH.
  • the indicated TCI state should be based on the activated TCI states in the first slot with the scheduled PDSCH, and UE shall expect the activated TCI states are the same across the slots with the scheduled PDSCH.
  • the UE When the UE is configured with CORESET associated with a search space set for cross-carrier scheduling and the UE is not configured with [enableDefaultBeamForCSS] , the UE expects tci-PresentInDCI is set as 'enabled' or tci-PresentInDCI-ForFormat1_2 is configured for the CORESET, and if one or more of the TCI states configured for the serving cell scheduled by the search space set contains 'QCL-TypeD' , the UE expects the time offset between the reception of the detected PDCCH in the search space set and the corresponding PDSCH is larger than or equal to the threshold timeDurationForQCL.
  • the UE may assume that the DM-RS ports of PDSCH of a serving cell are quasi co-located with the RS (s) with respect to the QCL parameter (s) used for PDCCH quasi co-location indication of the CORESET associated with a monitored search space with the lowest controlResourceSetId in the latest slot in which one or more CORESETs within the active BWP of the serving cell are monitored by the UE.
  • the UE is expected to prioritize the reception of PDCCH associated with that CORESET.
  • This also applies to the intra-band CA case (when PDSCH and the CORESET are in different component carriers) . If none of configured TCI states for the serving cell of scheduled PDSCH contains 'QCL-TypeD' , the UE shall obtain the other QCL assumptions from the indicated TCI states for its scheduled PDSCH irrespective of the time offset between the reception of the DL DCI and the corresponding PDSCH.
  • a UE is configured with enableDefaultTCIStatePerCoresetPoolIndex and the UE is configured by higher layer parameter PDCCH-Config that contains two different values of CORESETPoolIndex in ControlResourceSet, for both cases, when tci-PresentInDCI is set to 'enabled' and tci-PresentInDCI is not configured in RRC connected mode, if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL, the UE may assume that the DM-RS ports of PDSCH associated with a value of CORESETPoolIndex of a serving cell are quasi co-located with the RS (s) with respect to the QCL parameter (s) used for PDCCH quasi co-location indication of the CORESET associated with a monitored search space with the lowest controlResourceSetId among CORESETs, which are configured with the same value of CORESETPoolIndex as the PDCCH scheduling
  • the UE may assume that the DM-RS ports of PDSCH or PDSCH transmission occasions of a serving cell are quasi co-located with the RS (s) with respect to the QCL parameter (s) associated with the TCI states corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states.
  • the mapping of the TCI states to PDSCH transmission occasions is determined by replacing the indicated TCI states with the TCI states corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states.
  • the timeDurationForQCL is determined based on the subcarrier spacing of the scheduled PDSCH. If ⁇ PDCCH ⁇ ⁇ PDSCH an additional timing delay is added to the timeDurationForQCL, where d is defined in 5.2.1.5.1a-1 of TS 38.214, otherwise d is zero;
  • the UE obtains its QCL assumption for the scheduled PDSCH from the activated TCI state with the lowest ID applicable to PDSCH in the active BWP of the scheduled cell.
  • Figure 5 illustrates a flowchart for a method 500 performed by a UE communicating with a network in a serving cell for wireless communications according to an implementation of the present disclosure.
  • actions 502, 504, 506, and 508 are illustrated as separate actions represented as independent blocks in Figure 5, these separately illustrated actions should not be construed as necessarily order dependent.
  • the order in which the actions are performed in Figure 5 is not intended to be construed as a limitation, and any number of the disclosed blocks may be combined in any order to implement the method, or an alternate method.
  • each of actions 502, 504, 506, and 508 may be performed independent of other actions, and can be omitted in some implementations of the present disclosure.
  • the UE may measure a first RS set and a second RS set in the serving cell.
  • the UE may transmit a first BFRQ via a first MAC-CE on a first UL grant scheduled by a first PDCCH or by a first RRC configuration, in a case that an accumulated number of times where a quality of the first RS set is determined to be less than a first threshold reaches a first number. For example, the UE may count how many times the quality of the first RS set is determined to be less than the first threshold (within a specific time period) . If the result of counting (or “the accumulated number of times” ) reaches the first number, the UE may transmit the first BFRQ. In some implementations, there may be a first counter to count or accumulate the times where the quality of the first RS set is determined to be less than the first threshold. The first counter may be set or maintained by the UE.
  • the UE may transmit a second BFRQ via a second MAC-CE on a second UL grant scheduled by a second PDCCH or a second RRC configuration, in a case that an accumulated number of times where a quality of the second RS set is determined to be less than a second threshold reaches a second number. For example, the UE may count how many times the quality of the second RS set is determined to be less than the second threshold (within a specific time period) . If the result of counting reaches the second number, the UE may transmit the second BFRQ. In some implementations, there may be a second counter to count or accumulate the times where the quality of the second RS set is determined to be less than the second threshold. The second counter may be set or maintained by the UE.
  • the UE may transmit a third BFRQ via a PRACH or via a third MAC-CE on an RAR grant, in a case that the accumulated number of times where the quality of the first RS set is determined to be less than the first threshold reaches the first number and the accumulated number of times where the quality of the second RS set is determined to be less than the second threshold reaches the second number.
  • the UE may further terminate an ongoing procedure for transmitting one of the first BFRQ and the second BFRQ in a case that the third BFRQ is triggered to be transmitted.
  • a MAC-CE format of the third MAC-CE may be the same as one of a MAC-CE format of the first MAC-CE and a MAC-CE format of the second MAC-CE.
  • the third BFRQ may be transmitted in a case that a first occurrence and a second occurrence occur in a same time duration, where the first occurrence is (the situation) that the accumulated number of times where the quality of the first RS set is determined to be less than the first threshold reaches the first number, and the second occurrence is (the situation) that the accumulated number of times where the quality of the second RS set is determined to be less than the second threshold reaches the second number.
  • the time duration may be pre-determined or pre-configured as one or more time units.
  • the one or more time units may be in unit of one of at least one symbol, at least one sub-slot, at least one slot, at least one subframe, and at least one millisecond.
  • the serving cell may be an SpCell.
  • Figure 6 illustrates a flowchart for a method 600 performed by a network (e.g., a base station) communicating with a UE in a serving cell for wireless communications according to an implementation of the present disclosure.
  • a network e.g., a base station
  • actions 602, 604, 606, 608, and 610 are illustrated as separate actions represented as independent blocks in Figure 6, these separately illustrated actions should not be construed as necessarily order dependent.
  • the order in which the actions are performed in Figure 6 is not intended to be construed as a limitation, and any number of the disclosed blocks may be combined in any order to implement the method, or an alternate method.
  • each of actions 602, 604, 606, 608, and 610 may be performed independent of other actions, and can be omitted in some implementations of the present disclosure.
  • the network may configure the UE with a first BFR configuration and a second BFR configuration.
  • the network may prevent from not indicating an RRC configuration for at least one of a first RS set and a second RS set in a case that the base station apparatus transmits, to the UE, a first MAC-CE that activates two TCI states and maps the two TCI states to a TCI codepoint in a TCI field.
  • the network may transmit the first RS set and the second RS set in the serving cell.
  • the network may receive a first BFRQ from the UE in a case that an accumulated number of times where a quality of the first RS set is less than a first threshold reaches a first number.
  • the network may receive a second BFRQ from the UE in a case that an accumulated number of times where a quality of the second RS set is less than a second threshold reaches a second number.
  • the network may further prevent from configuring the UE with at least two CORESETs having a same CORESET pool index (CORESETPoolIndex) . In some implementations, the network may further prevent from configuring the UE with at least two CORESETs having a same CORESET pool index (CORESETPoolIndex) , when the network configures the UE with per-TRP BFR procedure.
  • CORESETPoolIndex CORESETPoolIndex
  • the network may further prevent from configuring the UE with at least two CORESETs having a same CORESET pool index (CORESETPoolIndex) , when the network configures the UE with more than one specific parameter or configuration in a BWP or a serving cell, where the specific parameter or configuration may be one of the followings: beam failure indication counter, candidate beam list, beam failure detection timer.
  • CORESETPoolIndex CORESETPoolIndex
  • the first BFRQ may be a second MAC-CE on an UL grant that is scheduled by a PDCCH or RRC signaling.
  • the second BFRQ may be a third MAC-CE on an UL grant that is scheduled by a PDCCH or RRC signaling.
  • FIG. 7 is a block diagram illustrating a node 700 for wireless communication according to an implementation of the present disclosure.
  • a node 700 may include a transceiver 720, a processor 728, a memory 734, one or more presentation components 738, and at least one antenna 736.
  • the node 700 may also include a radio frequency (RF) spectrum band module, a BS communications module, a network communications module, and a system communications management module, Input /Output (I/O) ports, I/O components, and a power supply (not illustrated in Figure 7) .
  • RF radio frequency
  • the node 700 may be a UE or a BS that performs various functions disclosed with reference to Figures 1 through 6.
  • the transceiver 720 has a transmitter 722 (e.g., transmitting/transmission circuitry) and a receiver 724 (e.g., receiving/reception circuitry) and may be configured to transmit and/or receive time and/or frequency resource partitioning information.
  • the transceiver 720 may be configured to transmit in different types of subframes and slots including but not limited to usable, non-usable and flexibly usable subframes and slot formats.
  • the transceiver 720 may be configured to receive data and control channels.
  • the node 700 may include a variety of computer-readable media.
  • Computer-readable media may be any available media that may be accessed by the node 700 and include volatile (and/or non-volatile) media and removable (and/or non-removable) media.
  • the computer-readable media may include computer-storage media and communication media.
  • Computer-storage media may include both volatile (and/or non-volatile media) , and removable (and/or non-removable) media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or data.
  • Computer-storage media may include RAM, ROM, EPROM, EEPROM, flash memory (or other memory technology) , CD-ROM, Digital Versatile Disks (DVD) (or other optical disk storage) , magnetic cassettes, magnetic tape, magnetic disk storage (or other magnetic storage devices) , etc.
  • Computer-storage media may not include a propagated data signal.
  • Communication media may typically embody computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanisms and include any information delivery media.
  • modulated data signal may mean a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
  • Communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the previously listed components should also be included within the scope of computer-readable media.
  • the memory 734 may include computer-storage media in the form of volatile and/or non-volatile memory.
  • the memory 734 may be removable, non-removable, or a combination thereof.
  • Example memory may include solid-state memory, hard drives, optical-disc drives, etc.
  • the memory 734 may store a computer-readable and/or computer-executable program 732 (e.g., software codes) that are configured to, when executed, cause the processor 728 to perform various functions disclosed herein, for example, with reference to Figures 1 through 6.
  • the program 732 may not be directly executable by the processor 728 but may be configured to cause the node 700 (e.g., when compiled and executed) to perform various functions disclosed herein.
  • the processor 728 may include an intelligent hardware device, e.g., a Central Processing Unit (CPU) , a microcontroller, an ASIC, etc.
  • the processor 728 may include memory.
  • the processor 728 may process the data 730 and the program 732 received from the memory 734, and information transmitted and received via the transceiver 720, the base band communications module, and/or the network communications module.
  • the processor 728 may also process information to send to the transceiver 720 for transmission via the antenna 736 to the network communications module for transmission to a CN.
  • One or more presentation components 738 may present data indications to a person or another device.
  • Examples of presentation components 738 may include a display device, a speaker, a printing component, a vibrating component, etc.

Landscapes

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

Abstract

Procédé(s) et équipement utilisateur (UE) permettant de rétablir une ou plusieurs liaisons relatives à un faisceau dans un système de communication sans fil. Un procédé mis en œuvre par un UE consiste à mesurer un premier ensemble de RS et un second ensemble de RS dans la cellule de desserte ; à transmettre une première demande de récupération de défaillance de faisceau (BFRQ) par l'intermédiaire d'un premier MAC-CE sur une première autorisation UL, dans le cas où un nombre cumulé de fois où une qualité du premier ensemble de RS est déterminée comme étant inférieure à un premier seuil atteint un premier nombre ; à transmettre une deuxième BFRQ par l'intermédiaire d'un deuxième MAC-CE sur une seconde autorisation UL, dans le cas où un nombre cumulé de fois où une qualité du second ensemble de RS est déterminée comme étant inférieure à un second seuil atteint un second nombre ; et à transmettre une troisième BFRQ par l'intermédiaire d'un PRACH ou par l'intermédiaire d'un troisième MAC-CE sur une autorisation RAR, dans le cas où le nombre cumulé de fois où la qualité du premier ensemble de RS est déterminée comme étant inférieure au premier seuil atteint le premier nombre et le nombre cumulé de fois où la qualité du second ensemble de RS est déterminée comme étant inférieure au second seuil atteint le second nombre.
PCT/CN2021/125908 2020-10-23 2021-10-22 Procédé et équipement utilisateur permettant de rétablir des liaisons relatives à un faisceau dans un système de communication sans fil WO2022083771A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063104934P 2020-10-23 2020-10-23
US63/104,934 2020-10-23

Publications (1)

Publication Number Publication Date
WO2022083771A1 true WO2022083771A1 (fr) 2022-04-28

Family

ID=81291640

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/125908 WO2022083771A1 (fr) 2020-10-23 2021-10-22 Procédé et équipement utilisateur permettant de rétablir des liaisons relatives à un faisceau dans un système de communication sans fil

Country Status (1)

Country Link
WO (1) WO2022083771A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110933695A (zh) * 2019-04-24 2020-03-27 华为技术有限公司 波束故障恢复请求发送方法及终端设备
CN111132204A (zh) * 2018-10-31 2020-05-08 成都华为技术有限公司 检测波束失败的方法和装置
US10798622B2 (en) * 2018-02-09 2020-10-06 Comcast Cable Communications, Llc Beam failure recovery in carrier aggregation
CN111756458A (zh) * 2019-03-26 2020-10-09 华为技术有限公司 波束失败恢复方法和通信装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10798622B2 (en) * 2018-02-09 2020-10-06 Comcast Cable Communications, Llc Beam failure recovery in carrier aggregation
CN111132204A (zh) * 2018-10-31 2020-05-08 成都华为技术有限公司 检测波束失败的方法和装置
CN111756458A (zh) * 2019-03-26 2020-10-09 华为技术有限公司 波束失败恢复方法和通信装置
CN110933695A (zh) * 2019-04-24 2020-03-27 华为技术有限公司 波束故障恢复请求发送方法及终端设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Beam failure recovery for SCell", 3GPP DRAFT; R1-1903977, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Xi’an, China; 20190408 - 20190412, 7 April 2019 (2019-04-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051699390 *
HUAWEI, HISILICON: "Summary of remaining issues on beam failure recovery", 3GPP DRAFT; R1-1803637, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Sanya, China; 20180416 - 20180420, 15 April 2018 (2018-04-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051425934 *
MEDIATEK INC.: "Summary on Beam Failure Recovery", 3GPP DRAFT; R1-1811867_SUMMARY_BFR_CR_V06, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Chengdu, China; 20181015 - 20181019, 9 October 2018 (2018-10-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051519191 *

Similar Documents

Publication Publication Date Title
US20220295428A1 (en) Operation method of terminal and base station in wireless communication system supporting unlicensed band, and apparatus supporting same
US20200068511A1 (en) Method and user equipment for transmitting uplink signal
EP3211942B1 (fr) Procédé d'émission/réception de signal d2d dans un système de communication sans fil et appareil associé
US20170289965A1 (en) Method and user equipment for receiving downlink signal, and method and base station for transmitting downlink signal
WO2021155853A1 (fr) Procédé de communication sans fil et équipement utilisateur permettant de gérer des opérations d'accès aléatoire
US20220232639A1 (en) Method related to pusch repetitions, user equipment, and network device
US11805524B2 (en) Applying spatial relations to UL transmission occasions
US11791888B2 (en) Method and user equipment for wireless communication in wireless communication system
US11381300B2 (en) Method and apparatus for performing random access procedure for beam failure recovery
WO2021063263A1 (fr) Procédés et appareils pour opérations de réception discontinue pour procédure de reprise après défaillance de faisceau
WO2021228263A1 (fr) Équipement utilisateur et procédé pour un fonctionnement fbe dans une bande sans licence
US20220061117A1 (en) Method of updating spatial parameters and related device
EP4099784A1 (fr) Dispositif terminal et procédé de communication
US20230309093A1 (en) Method, user equipment and base station for performing multiple receptions or transmission on multiple serving cells
US11696341B2 (en) Methods and apparatuses for random access procedure in medium access control layer
WO2022083771A1 (fr) Procédé et équipement utilisateur permettant de rétablir des liaisons relatives à un faisceau dans un système de communication sans fil
WO2023005886A1 (fr) Procédé et équipement utilisateur pour indication de faisceau dans un mtrp
WO2023143259A1 (fr) Procédé et équipement utilisateur pour effectuer des transmissions de liaison montante pour accès aléatoire et station de base associée
US20230292373A1 (en) Method and user equipment for performing uplink repetitions and related base station
US20230247682A1 (en) Method and user equipment for performing uplink transmissions and related base station
WO2022017427A1 (fr) Procédé de d'émissions et de réceptions dans un fonctionnement de duplexage par répartition en fréquence semi-duplex et dispositif associé
US12035164B2 (en) Method for reporting beam failure of terminal in wireless communication system, and terminal and base station for supporting same
WO2022083770A1 (fr) Procédé de surveillance d'un canal physique de commande de liaison descendante et dispositif associé
WO2023051363A1 (fr) Procédé et appareil pour économiser de l'énergie dans des systèmes de communication sans fil
US20230120155A1 (en) Method related to random access and user equipment

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21882183

Country of ref document: EP

Kind code of ref document: A1