WO2023010580A1 - Procédés et dispositifs de communication - Google Patents

Procédés et dispositifs de communication Download PDF

Info

Publication number
WO2023010580A1
WO2023010580A1 PCT/CN2021/111353 CN2021111353W WO2023010580A1 WO 2023010580 A1 WO2023010580 A1 WO 2023010580A1 CN 2021111353 W CN2021111353 W CN 2021111353W WO 2023010580 A1 WO2023010580 A1 WO 2023010580A1
Authority
WO
WIPO (PCT)
Prior art keywords
procedure
beam failure
timer
trp
bwp
Prior art date
Application number
PCT/CN2021/111353
Other languages
English (en)
Inventor
Yukai GAO
Gang Wang
Original Assignee
Nec Corporation
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 Nec Corporation filed Critical Nec Corporation
Priority to PCT/CN2021/111353 priority Critical patent/WO2023010580A1/fr
Publication of WO2023010580A1 publication Critical patent/WO2023010580A1/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
    • 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/08—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the receiving station
    • H04B7/0868—Hybrid systems, i.e. switching and combining
    • H04B7/088—Hybrid systems, i.e. switching and combining using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0032—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0078—Timing of allocation
    • H04L5/0087—Timing of allocation when data requirements change
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J11/00—Orthogonal multiplex systems, e.g. using WALSH codes
    • H04J11/0023—Interference mitigation or co-ordination
    • H04J11/005—Interference mitigation or co-ordination of intercell interference
    • H04J11/0053—Interference mitigation or co-ordination of intercell interference using co-ordinated multipoint transmission/reception
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to methods, devices and computer storage media for communication.
  • multi-transmission and reception point multi-transmission and reception point
  • PDCCH Physical Downlink Control Channel
  • PUSCH Physical Uplink Shared Channel
  • PUCCH Physical Uplink Control Channel
  • TCI transmission configuration indicator
  • example embodiments of the present disclosure provide methods, devices and computer storage media for communication.
  • a method of communication comprises receiving, at a terminal device, from a network device, a first set of reference signals (RSs) and a second set of RSs; receiving, one or more configurations of a first timer and a second timer; performing a beam failure detection related to the a first procedure based on the first set and the first timer; performing a beam failure detection related to the a second procedure based on the second set and the second timer; and performing a third procedure based on a first condition and/or a first parameter related to at least one of the first procedure and the second procedure
  • a method of communication comprises transmitting, at a network device, to a terminal device, a first set of reference signals (RSs) for a first procedure and a second set of RSs for a second procedure; transmitting, one or more configurations of a first timer and a second timer for the first procedure and the second procedure; and receiving, from the terminal device, a beam failure recovery request or a random access preamble.
  • RSs reference signals
  • a terminal device comprising circuitry configured to perform the method according to the above first aspect of the present disclosure.
  • a network device comprising circuitry configured to perform the method according to the above second aspect of the present disclosure.
  • a computer program product comprising machine-executable instructions.
  • the machine-executable instructions when being executed, cause a machine to perform the method according to the above first or second aspect of the present disclosure.
  • a computer readable medium having instructions stored thereon. The instructions, when executed on at least one processor, causing the at least one processor to perform the method according to the above first or second aspect of the present disclosure.
  • FIG. 1 illustrates an example communication network in which embodiments of the present disclosure can be implemented
  • FIG. 2 illustrates an example signaling chart in accordance with some embodiments of the present disclosure
  • FIGs. 3A-3C illustrate examples of embodiments of the present disclosure
  • FIGs. 4A-4B illustrate examples of embodiments of the present disclosure
  • FIG. 5 illustrates an example of embodiments of the present disclosure
  • FIG. 6A-6D illustrate examples of embodiments of the present disclosure
  • FIG. 7A-7B illustrate examples of embodiments of the present disclosure
  • FIG. 8 illustrates a flowchart of an example method in accordance with some embodiments of the present disclosure
  • FIG. 9 illustrates a flowchart of an example method in accordance with some embodiments of the present disclosure.
  • FIG. 10 is a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.
  • the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’
  • the term ‘based on’ is to be read as ‘at least in part based on. ’
  • the term ‘some embodiments’ and ‘an embodiment’ are to be read as ‘at least some embodiments. ’
  • the term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’
  • the terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
  • values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
  • circuitry used herein may refer to hardware circuits and/or combinations of hardware circuits and software.
  • the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware.
  • the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions.
  • the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not needed for operation.
  • the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.
  • Embodiments of the present disclosure provide a solution to solve the above problem and/or one or more of other potential problems.
  • the terminal device may transmit a beam failure recovery request (BFRQ) to a network device, where the BFRQ comprises TRP information related to the beam failure detected on the cell.
  • the TRP information may indicate at least one of the following: the number of TRPs related to the beam failure detected on the cell, a TRP index related to the beam failure detected on the cell, whether a new candidate beam is identified on a failed TRP, information about the new candidate beam if it is identified on the failed TRP, and so on.
  • this solution can support multi-TRP based BFRQ.
  • FIG. 1 shows an example communication network 100 in which embodiments of the present disclosure can be implemented.
  • the network 100 includes a network device 110 and a terminal device 120 served by the network device 110.
  • the network 100 may provide one or more serving cells to serve the terminal device 120.
  • terminal device refers to any device having wireless or wired communication capabilities.
  • Examples of the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, or image capture devices such as digital cameras, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like.
  • UE user equipment
  • PDAs personal digital assistants
  • IoT internet of things
  • IoE Internet of Everything
  • MTC machine type communication
  • X means pedestrian, vehicle, or infrastructure/network
  • image capture devices such as digital cameras, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like.
  • the term ‘network device’ or ‘base station’ (BS) refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate.
  • a network device include, but not limited to, a Node B (NodeB or NB) , an Evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a Remote Radio Unit (RRU) , a radio head (RH) , a remote radio head (RRH) , a low power node such as a femto node, a pico node, and the like.
  • NodeB Node B
  • eNodeB or eNB Evolved NodeB
  • gNB next generation NodeB
  • RRU Remote Radio Unit
  • RH radio head
  • RRH remote radio head
  • a low power node such as a femto node, a pico node, and the like.
  • carrier aggregation can be supported in the network 100, in which two or more CCs are aggregated in order to support a broader bandwidth.
  • the network device 110 may provide to the terminal device 120 a plurality of serving cells including one primary cell (Pcell) 101 corresponding to a primary CC and at least one secondary cell (Scell) 102 corresponding to at least one secondary CC.
  • Pcell primary cell
  • Scell secondary cell
  • the network 100 may include any suitable number of network devices, terminal devices and/or serving cells adapted for implementing implementations of the present disclosure.
  • the terminal device 120 may establish connections with two different network devices (not shown in FIG. 1) and thus can utilize radio resources of the two network devices.
  • the two network devices may be respectively defined as a master network device and a secondary network device.
  • the master network device may provide a group of serving cells, which are also referred to as “Master Cell Group (MCG) ” .
  • the secondary network device may also provide a group of serving cells, which are also referred to as “Secondary Cell Group (SCG) ” .
  • SCG Secondary Cell Group
  • a term “Special Cell (Spcell) ” may refer to the Pcell of the MCG or the primary Scell (Pscell) of the SCG depending on if the terminal device 120 is associated to the MCG or the SCG, respectively.
  • the term “SpCell” may also refer to the PCell.
  • the terminal device 120 may be connected with a first network device and a second network device (not shown in FIG. 1) .
  • One of the first network device and the second network device may be in a master node and the other one may be in a secondary node.
  • the first network device and the second network device may use different radio access technologies (RATs) .
  • the first network device may be a first RAT device and the second network device may be a second RAT device.
  • the first RAT device may be an eNB and the second RAT device is a gNB.
  • Information related to different RATs may be transmitted to the terminal device 120 from at least one of the first network device and the second network device.
  • first information may be transmitted to the terminal device 120 from the first network device and second information may be transmitted to the terminal device 120 from the second network device directly or via the first network device.
  • information related to configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device.
  • Information related to reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
  • the information may be transmitted via any of the following: Radio Resource Control (RRC) signaling, Medium Access Control (MAC) control element (CE) or Downlink Control Information (DCI) .
  • RRC Radio Resource Control
  • MAC Medium Access Control
  • CE Control element
  • DCI Downlink Control Information
  • the network device 110 can communicate data and control information to the terminal device 120 and the terminal device 120 can also communication data and control information to the network device 110.
  • a link from the network device 110 to the terminal device 120 is referred to as a downlink (DL)
  • a link from the terminal device 120 to the network device 110 is referred to as an uplink (UL) .
  • the network device 110 may transmit control information via a PDCCH and/or transmit data via a PDSCH to the terminal device 120. Additionally, the network device 110 may transmit one or more reference signals (RSs) to the terminal device 120.
  • the RS transmitted from the network device 110 to the terminal device 120 may also referred to as a “DL RS” .
  • Examples of the DL RS may include but are not limited to Demodulation Reference Signal (DMRS) , Channel State Information-Reference Signal (CSI-RS) , Sounding Reference Signal (SRS) , Phase Tracking Reference Signal (PTRS) , fine time and frequency Tracking Reference Signal (TRS) and so on.
  • DMRS Demodulation Reference Signal
  • CSI-RS Channel State Information-Reference Signal
  • SRS Sounding Reference Signal
  • PTRS Phase Tracking Reference Signal
  • TRS fine time and frequency Tracking Reference Signal
  • the terminal device 120 may transmit control information via a PUCCH and/or transmit data via a PUSCH to the network device 110. Additionally, the terminal device 120 may transmit one or more RSs to the network device 110.
  • the RS transmitted from the terminal device 120 to the network device 110 may also referred to as a “UL RS” . Examples of the UL RS may include but are not limited to DMRS, CSI-RS, SRS, PTRS, fine time and frequency TRS and so on.
  • the communications in the network 100 may conform to any suitable standards including, but not limited to, Global System for Mobile Communications (GSM) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , GSM EDGE Radio Access Network (GERAN) , Machine Type Communication (MTC) and the like.
  • GSM Global System for Mobile Communications
  • LTE Long Term Evolution
  • LTE-Evolution LTE-Advanced
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • CDMA Code Division Multiple Access
  • GERAN GSM EDGE Radio Access Network
  • MTC Machine Type Communication
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols.
  • the network device 110 may be equipped with one or more TRPs or antenna panels.
  • TRP refers to an antenna array (with one or more antenna elements) available to the network device located at a specific geographical location.
  • a network device may be coupled with multiple TRPs in different geographical locations to achieve better coverage.
  • the one or more TRPs may be included in a same serving cell or different serving cells.
  • the TRP can also be a panel, and the panel can also refer to an antenna array (with one or more antenna elements) .
  • the present disclosure described with reference to multiple TRPs for example, these embodiments are only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitations as to the scope of the present disclosure. It is to be understood that the present disclosure described herein can be implemented in various manners other than the ones described below.
  • FR2 FR2
  • FR1 FR2
  • a. Identify and specify features to facilitate more efficient (lower latency and overhead) DL/UL beam management to support higher intra-and L1/L2-centric inter-cell mobility and/or a larger number of configured TCI states: i. Common beam for data and control transmission/reception for DL and UL, especially for intra-band CA; ii. Unified TCI framework for DL and UL beam indication; iii. Enhancement on signaling mechanisms for the above features to improve latency and efficiency with more usage of dynamic control signaling (as opposed to RRC) .
  • the existing DCI formats 1_1 and 1_2 are reused for beam indication and it supports a mechanism for UE to acknowledge successful decoding of beam indication.
  • the ACK/NACK of the PDSCH scheduled by the DCI carrying the beam indication can be used as an ACK also for the DCI.
  • MAC medium access control
  • CE control element
  • acknowledgement/negative acknowledgement (ACK/NACK) mechanism is used analogously to that for semi-persistent scheduling (SPS) PDSCH release with both type-1 and type-2 HARQ-ACK codebook.
  • SPS semi-persistent scheduling
  • a location for the ACK information in the HARQ-ACK codebook is determined based on a virtual PDSCH indicated by the TDRA field in the beam indication DCI, based on the time domain allocation list configured for PDSCH.
  • a location for the ACK information in the HARQ-ACK codebook is determined according to the same rule for SPS release.
  • the ACK is reported in a PUCCH k slots after the end of the PDCCH reception where k is indicated by the PDSCH-to-HARQ_feedback timing indicator field in the DCI format, or provided dl-DataToUL-ACK or dl-DataToUL-ACK-ForDCI-Format1-2-r16 if the PDSCH-to-HARQ_feedback timing indicator field is not present in the DCI.
  • configured scheduling-radio network temporary identifier (CS-RNTI) is used to scramble the CRC for the DCI.
  • CS-RNTI configured scheduling-radio network temporary identifier
  • the TCI field can be used to signal the following: 1) Joint DL/UL TCI state, 2) DL-only TCI state (for separate DL/UL TCI) , 3) UL-only TCI state (for separate DL/UL TCI) .
  • DCI fields are being used in Rel-16: identifier for DCI formats; carrier indicator; bandwidth part indicator; time domain resource assignment (TDRA) ; downlink assignment index (if configured) ; transmit power control (TPC) command for scheduled PUCCH; PUCCH resource indicator; PDSCH-to-HARQ_feedback timing indicator (if present) .
  • TDRA time domain resource assignment
  • TPC transmit power control
  • the remaining unused DCI fields and codepoints are reserved in Release 17.
  • the first slot that is at least X ms or Y symbols after the last symbol of the acknowledgment of the joint or separate DL/UL beam indication.
  • the network device 110 may communicate with the terminal device 120 via TRPs 130-1 and 130-2 (collectively referred to as “TRPs 130” or individually referred to as “TRP 130” in the following) .
  • TRPs 130 may be also referred to as the first TRP
  • TRP 130-2 may be also referred to as the second TRP.
  • the network device 110 may provide a group of cells to serve the terminal device 120.
  • the group of cells may be divided into a first subset of cells associated with the first TRP 130-1 and a second subset of cells associated with the second TRP 130-2.
  • the first subset of cells and the second subset of cells may include one or more overlapping cells or may not overlap each other.
  • FIG. 2 illustrates a singling chart 200 in accordance with embodiments of the present disclosure.
  • the network device 110 may transmit 210 a configuration to the terminal device 120.
  • the configuration may indicate that each of a group of cells serving the terminal device 120 is associated with at least one of TRPs 130 coupled with the network device 110.
  • the configuration may be transmitted from the network device 110 to the terminal device 120 via at least one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) control element (CE) or Downlink Control Information (DCI) .
  • RRC Radio Resource Control
  • MAC Medium Access Control
  • CE Control element
  • DCI Downlink Control Information
  • the terminal device 120 may perform 220 beam failure detection.
  • the terminal device 120 may transmit a BFRQ to the network device 110 based on the configuration.
  • the BFRQ may comprise TRP information related to the beam failure detected on the cell.
  • each TRP in the M TRPs may be represented by or associated with at least one of the following: a control resource set (CORESET) pool index; a CORESET group identifier (ID) ; a group of CORESETs; a CORESET set ID; a set of CORESETs; a SRS resource set; a SRS resource set ID; a TCI state; a group of TCI states; an ID of a set of reference signals (RSs) for beam failure detection; an ID of a set of RSs for new/candidate beam identification; spatial relation information; a group of spatial relation information; a set of QCL parameters; a group of RSs for beam failure detection; a group of RSs for new/candidate beam identification; and so on
  • CORESET control resource
  • the first TRP 130-1 may be represented by or associated with at least one of the following: a first CORESET pool index (for example, with a value of 0. For another example, CORESET (s) without configuration of the parameter “CORESET pool index” ) ; a first CORESET group/set/subset ID; a first group/set/subset of CORESETs (For example, CORESET (s) configured with the first CORESET pool index or the first CORESET group/set/subset ID.
  • CORESET (s) not configured with the parameter “CORESET pool index” or the parameter “CORESET group/set/subset ID” ) ; a first SRS resource set; a first SRS resource set ID; a first TCI state; a first group of TCI states; an ID of a first set of reference signals (RSs) for beam failure detection; the first set of reference signals (RSs) for beam failure detection; an ID of a first set of RSs for new/candidate beam identification; the first set of RSs for new/candidate beam identification; first spatial relation information; a first group of spatial relation information; a first set of QCL parameters; a first group of RSs for beam failure detection; a first group of RSs for new/candidate beam identification; and so on.
  • RSs reference signals
  • RSs reference signals
  • the second TRP 130-2 may be represented by at least one of the following: a second CORESET pool index (for example, with a value of 1) ; a second CORESET group/set/subset ID; a second group/set/subset of CORESETs (For example, CORESET (s) configured with the second CORESET pool index or the second CORESET group/set/subset ID.
  • a second SRS resource set ; a second SRS resource set ID; a second TCI state; a second group of TCI states; an ID of a second set of reference signals (RSs) for beam failure detection; the second set of reference signals (RSs) for beam failure detection; an ID of a second set of RSs for new/candidate beam identification; the second set of RSs for new/candidate beam identification; second spatial relation information; a second group of spatial relation information; a second set of QCL parameters; a second group of RSs for beam failure detection; a second group of RSs for new/candidate beam identification; and so on.
  • RSs reference signals
  • RSs reference signals
  • the terminal device 120 may be configured with a first TRP (for example, the first TRP 130-1) and a second TRP (for example, the second TRP 130-2) in a BWP for a cell.
  • a first TRP for example, the first TRP 130-1
  • a second TRP for example, the second TRP 130-2
  • the terminal device 120 may be configured with a first procedure, a second procedure and a third procedure for the cell and/or for the BWP.
  • the first procedure is a TRP-specific beam failure detection and recovery procedure related to the first TRP.
  • the second procedure is a TRP-specific beam failure detection and recovery procedure related to the second TRP.
  • the third procedure is a cell specific beam failure detection and recovery procedure or a random access procedure related to the BWP and/or the cell. It needs to be designed the relationship between the first procedure, the second procedure and the third procedure. For example, when a beam failure recovery is triggered for the first TRP or the second TRP, whether to increase a counter for beam failure detection related to the third procedure.
  • the terminal device 120 may receive a configuration or an activation command, and the configuration or the activation command is used to map up to 8 combinations of one or two TCI states to a set of TCI codepoints.
  • the number of TCI codepoints in the set of TCI may be at least one of ⁇ 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16 ⁇ .
  • the set of TCI codepoints are indicated in a DCI field “transmission configuration indication” .
  • the terminal device 120 may be served with two TRPs (for example, a first TRP and a second TRP) .
  • the first TCI state is associated with the first TRP
  • the second TCI state is associated with the second TRP.
  • TRP Time Division Multiple Access
  • CORESET pool index CORESET group/set/subset ID
  • group/set/subset of CORESETs SRS resource set
  • SRS resource set ID SRS resource set ID
  • TCI state TCI state
  • group of TCI states TCI state
  • group of TCI states TCI states
  • ID of a set of RSs for beam failure detection , “ID of a set of RSs for new/candidate beam identification”
  • spatial relation information , “group of spatial relation information” , “set of QCL parameters” , “group of RSs for beam failure detection” and “group of RSs for new/candidate beam identification”
  • first TRP “first CORESET pool index” , “first CORESET group/set/subset ID” , “first group/set/subset of CORESETs” , “first SRS resource set” , “first SRS resource set ID” , “first TCI state” , “first TCI state of two TCI states corresponding to a TCI codepoint” , “first group of TCI states” , “ID of a first set of RSs for beam failure detection” , “first set of RSs for beam failure detection” , “ID of a first set of RSs for new/candidate beam identification” , “first set of RSs for new/candidate beam identification” , “first spatial relation information” , “first group of spatial relation information” , “first set of QCL parameters” , “first group of RSs for beam failure detection” and “first group of RSs for new/candidate beam identification” can be used interchangeably.
  • second TRP “second CORESET pool index” , “second CORESET group/set/subset ID” , “second group/set/subset of CORESETs” , “second SRS resource set” , “second SRS resource set ID” , “second TCI state” , “secondTCI state of two TCI states corresponding to a TCI codepoint” , “second group of TCI states” , “ID of a second set of RSs for beam failure detection” , “second set of RSs for beam failure detection” ; “ID of a second set of RSs for new/candidate beam identification” , “second set of RSs for new/candidate beam identification” , “second spatial relation information” , “second group of spatial relation information” , “second set of QCL parameters” , “second group of RSs for beam failure detection” and “second group of RSs for new/candidate beam identification” can be used interchangeably.
  • Figs. 3A –3C illustrate examples in accordance with some embodiments of the present disclosure.
  • the terminal device 120 may be configured with a set of RSs for beam failure detection (RS 0_0 and RS 0_1 ) , and a set of RSs for new/candidate beam identification (RS 1_0 and RS 1_1 ) .
  • the terminal device may search new beam based on RS 1_0 and RS 1_1 .
  • the terminal device 120 may be configured with a timer (BeamFailureDetectionTimer) , and if a beam failure instance indication is indicated or received from the lower layers of the terminal device, the value of BFI_COUNTER is increased by 1, and the timer may be started or restarted. For example, if the timer doesn’t expire, and if a beam failure instance indication is indicated or received from the lower layers of the terminal device, the value of BFI_COUNTER is increased by 1, and the timer may be started or restarted. For another example, if the timer expires, the value of BFI_COUNTER is set to 0.
  • BeamFailureDetectionTimer BeamFailureDetectionTimer
  • the beam failure recovery procedure is triggered. For example, if beamFailureDetectionTimer expires or if beamFailureDetectionTimer, beamFailureInstanceMaxCount, or any of the RSs used for beam failure detection is reconfigured, the value of BFI_COUNTER is set to 0.
  • Figs. 4A –4B illustrate examples in accordance with some embodiments of the present disclosure.
  • the terminal device 120 may be configured with a first TRP (TRP1) and a second TRP (TRP2) for communication with the network device 110.
  • TRP1 TRP
  • TRP2 TRP2
  • a first set of RSs for beam failure detection BFD_set_1
  • BFD_set_2 RSs for beam failure detection
  • BFD_set_2 RSs for beam failure detection
  • the terminal device 120 may search or select a new beam. For example, based on a set of RSs for new/candidate beam identification, wherein the new/candidate beam identification may be configured. For example, associated with the first TRP.
  • the beam failure recovery procedure is triggered. For example, related to the first procedure. For example, if the beam failure recovery is successfully completed related to the first procedure, the third procedure may be restarted or the value of the third counter (e.g. BFI_COUNTER_0) may be set to 0.
  • the first maximum value for example, beamFailureInstanceMaxCount_1
  • Fig. 5 illustrates an example in accordance with some embodiments of the present disclosure.
  • the terminal device 120 may be configured with a first timer (Time_1) in a first procedure (beam failure procedure 1) .
  • the first procedure is for the first TRP (TRP1) .
  • the beam failure detection is based on the first set of RSs for beam failure detection (BFD_set_1) .
  • BFI_COUNTER_1 the value of a first counter (BFI_COUNTER_1) is increased by 1.
  • BFI_COUNTER_1 is larger than or equal to the first maximum value (beamFailureInstanceMaxCount_1) , a BFR is triggered for the first procedure.
  • the first TRP (TRP1) is failed.
  • the terminal device 120 may be configured with a second timer (Time_2) in a second procedure (beam failure procedure 2) .
  • the second procedure is for the second TRP (TRP2) .
  • the beam failure detection is based on the second set of RSs for beam failure detection (BFD_set_2) .
  • BFI_COUNTER_2 the value of a second counter
  • BFI_COUNTER_2 is larger than or equal to the second maximum value (beamFailureInstanceMaxCount_2)
  • a BFR is triggered for the second procedure.
  • the second TRP (TRP2) is failed.
  • it may be hard to meet the condition that both the first TRP and the second TRP are failed simultaneously or within a short duration.
  • the terminal device 120 may be configured with a first procedure.
  • the first procedure is a procedure for beam failure detection and recovery.
  • the first procedure is a TRP specific beam failure detection and recovery procedure.
  • the first procedure is related to the first TRP.
  • the terminal device 120 may be configured with a second procedure.
  • the second procedure is a procedure for beam failure detection and recovery.
  • the second procedure is a TRP specific beam failure detection and recovery procedure.
  • the second procedure is related to the second TRP.
  • the terminal device 120 may be configured with a third procedure.
  • the third procedure is a procedure for beam failure detection and recovery.
  • the third procedure is a cell specific or random access channel (RACH) based beam failure detection and recovery procedure.
  • the third procedure is related to the cell.
  • the first TRP and the second TRP are configured in a BWP in the cell.
  • the first procedure, the second procedure and the third procedure are performed on the same BWP and/or on the same cell.
  • the terminal device 120 may receive at least one configuration, wherein the at least one configuration may include at least one of: a first maximum value (For example, the first maximum value may be for beam failure instance count. For another example, the first maximum value may be beamFailureInstanceMaxCount_1) , a first timer (For example, the first timer may be a timer for beam failure detection. For another example, the first timer may be beamFailureDetectionTimer_1) , the first set of RSs for beam failure detection, the first set of RSs for new/candidate beam identification (For example, candidateBeamRSList_1) , and a first threshold (For example, the first threshold may be an RSRP threshold. For another example, the first threshold may be rsrp_Threshold_1) . In some embodiments, the at least one configuration may be for the first procedure.
  • a first maximum value For example, the first maximum value may be for beam failure instance count.
  • the first maximum value may be beamFailureInstance
  • the terminal device 120 may receive at least one configuration, wherein the at least one configuration may include at least one of: a second maximum value (For example, the second maximum value may be for beam failure instance count. For another example, the second maximum value may be beamFailureInstanceMaxCount_2) , a second timer (For example, the second timer may be a timer for beam failure detection. For another example, the second timer may be beamFailureDetectionTimer_2) , the second set of RSs for new/candidate beam identification (For example, candidateBeamRSList_2) , and a second threshold (For example, the second threshold may be an RSRP threshold. For another example, the second threshold may be rsrp_Threshold_2) . In some embodiments, the at least one configuration may be for the second procedure.
  • a second maximum value For example, the second maximum value may be for beam failure instance count.
  • the second maximum value may be beamFailureInstanceMaxCount_2)
  • a second timer
  • the terminal device 120 may receive at least one configuration, wherein the at least one configuration may include at least one of: a third maximum value (For example, the third maximum value may be for beam failure instance count. For another example, the third maximum value may be beamFailureInstanceMaxCount_0) , a third timer (For example, the third timer may be a timer for beam failure detection. For another example, the third timer may be beamFailureDetectionTimer_0) , a third set of RSs for new/candidate beam identification (For example, candidateBeamRSList_3) , and a third threshold (For example, the third threshold may be an RSRP threshold. For another example, the third threshold may be rsrp_Threshold_0) . In some embodiments, the at least one configuration may be for the third procedure.
  • a third maximum value may be for beam failure instance count.
  • the third maximum value may be beamFailureInstanceMaxCount_0
  • a third timer For example, the
  • the terminal device 120 may receive a first set of RSs for beam failure detection and a second set of RSs for beam failure detection.
  • the RS may be a CSI-RS.
  • the terminal device 120 may receive a configuration for the first set of RSs.
  • the terminal device 120 may determine the first set of RSs based on one or more RSs indicated by one or more TCI states for the first set of CORESETs.
  • the terminal device 120 may receive a configuration for the second set of RSs.
  • the terminal device 120 may determine the second set of RSs based on one or more RSs indicated by one or more TCI states for the second set of CORESETs.
  • the terminal device 120 may receive one or more configurations of the first set of CORESETs and the second set of CORESETs for the BWP in the cell.
  • the first set of CORESETs may be associated with the first TRP.
  • the second set of CORESETs may be associated with the second TRP.
  • the terminal device 120 may perform a beam failure detection related to the first procedure based on the first set of RSs and the first timer. In some embodiments, the terminal device 120 may perform a beam failure detection related to the second procedure based on the second set of RSs and the second timer.
  • the terminal device 120 may perform the third procedure based on a first condition and/or a first parameter related to at least one of the first procedure and the second procedure.
  • the beam failure instance indication may be received at higher layers and from lower layers of the terminal device 120.
  • the beam failure instance indication may be based on the first set of RSs.
  • there may be a second counter for beam failure detection related to the first procedure wherein the second counter may be increased by 1 in case of a beam failure instance indication related to the second procedure.
  • the beam failure instance indication may be received at higher layers and from lower layers of the terminal device 120.
  • the beam failure instance indication may be based on the second set of RSs.
  • the terminal device 120 may perform a beam failure detection related to the third procedure based on a third set of RSs and a third timer.
  • the RS may be a CSI-RS.
  • the terminal device 120 may receive a configuration of the third set of RSs from the network device.
  • the terminal device 120 may determine the third set of RSs based on the first set of RSs and the second set of RSs.
  • the third set of RSs may be a union set of the first set of RSs and the second set of RSs.
  • the third set of RSs may comprise at least one RS from the first set of RSs and at least one RS from the second set of RSs.
  • the terminal device 120 may determine the third set of RSs based on one or more RSs indicated by one or more TCI states for the first set of CORESETs and/or one or more RSs indicated by one or more TCI states for the second set of CORESETs.
  • the third timer may be determined based on the first timer and the second timer.
  • the value of the third timer may be the larger or maximum value between the value of the first timer and the value of the second timer.
  • the third timer may be max (the first timer, the second timer) .
  • the value of the third timer may be max (the value of the first timer, the value of the second timer) .
  • the value of the third timer may be same with the value of the first timer, if the value of the first timer is larger than and/or equal to the value of the second timer.
  • the value of the third timer may be same with the value of the second timer, if the value of the first timer is less than and/or equal to the value of the second timer.
  • the third timer may be same with the first timer, if the value of the first timer is larger than and/or equal to the value of the second timer.
  • the third timer may be same with the second timer, if the value of the first timer is less than and/or equal to the value of the second timer.
  • the terminal device 120 may receive a configuration of the third timer from the network device.
  • the third counter may be increased by 1 in case of a beam failure instance indication related to the third procedure.
  • the beam failure instance indication may be received at higher layers and from lower layers of the terminal device 120.
  • the beam failure instance indication may be based on a third set of RSs.
  • the third counter may be increased by 1 based on at least one of the first counter, the second counter, the first timer, the second timer, the third timer and a first duration.
  • the terminal device 120 may set the third counter to 0 based on the first condition.
  • the first condition may comprise at least one of: a beam failure recovery (BFR) related to the first procedure is triggered; a BFR related to the second procedure is triggered; the first counter for beam failure detection related to the first procedure is larger than or equal to the first maximum value; the second counter for beam failure detection related to the second procedure is larger than or equal to the second maximum value; the first timer expires; the second timer expires; the first timer is reconfigured; the second timer is reconfigured; the first maximum value is reconfigured; the second maximum value is reconfigured; any of the RS in the first set of RSs is reconfigured or changed or replaced or updated; any of the RS in the second set of RSs is reconfigured or changed or replaced or updated; a TCI state for any of the RS in the first set of RSs is reconfigured or changed or updated; a TCI state for any of the RS in the second set of RSs is reconfigured or changed or
  • the terminal device 120 may perform a beam failure detection related to the third procedure based on the first set of RSs and/or the first timer in case of a second condition is satisfied. In some embodiments, the terminal device 120 may perform a beam failure detection related to the third procedure based on the third set of RSs and/or the third timer in case of the second condition is not satisfied.
  • the second condition may comprise at least one of: a BFR related to the second procedure is triggered; a BFR related to the second procedure is triggered and a BFR related to the first procedure is not triggered; a duration between a BFR related to the second procedure is triggered and the BFR related to the second procedure is successfully completed; a duration starting from a BFR related to the second procedure is triggered to the BFR related to the second procedure is successfully completed; a duration starting from the BFR related to the second procedure is triggered to a BFR related to the first procedure or related to the third procedure is triggered; and a duration between the BFR related to the second procedure is triggered and a BFR related to the first procedure or related to the third procedure is triggered.
  • the value of the third timer for beam failure detection related to the third procedure may be determined based on the first counter for beam failure detection related to the first procedure, the second counter for beam failure detection related to the second procedure and the third timer.
  • the terminal device 120 may start or restart the third timer, in case of a beam failure instance indication related to the first procedure is indicated or received. For example from the lower layers of the terminal device. In some embodiments, the beam failure instance indication may be based on the first set of RSs. In some embodiments, the terminal device 120 may start or restart the third timer, in case of the first counter is increased by 1. In some embodiments, the terminal device 120 may increase the third counter by 1, within a duration before the third timer expires (or the third timer doesn’t expire) , and in case of a beam failure instance indication related to the second procedure is indicated or received. For example, from the lower layers of the terminal device.
  • the beam failure instance indication may be based on the second set of RSs.
  • the terminal device 120 may increase the third counter by 1, within a duration before the third timer expires (or the third timer doesn’t expire) , and in case of the second counter is increased by 1.
  • the third timer may be set to 0, in case of the third timer expires.
  • the terminal device 120 may start or restart the third timer, in case of a beam failure instance indication related to the second procedure is indicated or received. For example from the lower layers of the terminal device. In some embodiments, the beam failure instance indication may be based on the second set of RSs. In some embodiments, the terminal device 120 may start or restart the third timer, in case of the second counter is increased by 1. In some embodiments, the terminal device 120 may increase the third counter by 1, within a duration before the third timer expires (or the third timer doesn’t expire) , and in case of a beam failure instance indication related to the first procedure is indicated or received. For example, from the lower layers of the terminal device.
  • the beam failure instance indication may be based on the first set of RSs.
  • the terminal device 120 may increase the third counter by 1, within a duration before the third timer expires (or the third timer doesn’t expire) , and in case of the first counter is increased by 1.
  • the third timer may be set to 0, in case of the third timer expires.
  • the third timer may be started or restarted based on at least one of: a beam failure instance indication is indicated or received related to either the first procedure or the second procedure, in case of the value of the first counter is 0, in case of the value of the second counter is 0, and a beam failure instance indication is indicated or received related to one of the first procedure or the second procedure, wherein the first procedure or the second procedure is configured with a smaller value between the first timer and the second timer or configured with a higher priority.
  • the terminal device 120 may cancel all triggered BFRs related to any one of the first procedure and the second procedure, in case of a BFR or a random access procedure related to the third procedure is triggered or initiated.
  • the terminal device 120 may stop the first procedure and the second procedure, in case of a BFR or a random access procedure related to the third procedure is triggered or initiated.
  • a BFR or a random access procedure related to the third procedure is triggered or initiated before a timing, wherein the timing comprises at least one of:a beam failure recovery related to the first procedure is successfully completed; and a beam failure recovery related to the second procedure is successfully completed.
  • a BFR related to the third procedure is triggered is same with a random access procedure is initiated.
  • the terminal device 120 may transmit a random access preamble to the network device, in case of a random access procedure related to the third procedure is initiated or in case of a beam failure recovery related to the third procedure is triggered.
  • the terminal device 120 may determine a power for the random access preamble transmission related to the third procedure, based on at least one of a power parameter and number of beam failure recovery request transmissions related to at least one of the first procedure and the second procedure.
  • the terminal device 120 may communicate with the network device 110 based on the first TRP and the second TRP of the cell. In some embodiments, the terminal device 120 may communicate with the network device 110 based on a single TRP of the cell after a timing, wherein the timing may be at least one of: a BFR related to the third procedure is triggered; a random access procedure related to the third procedure is initiated; and a beam failure recovery related to the third procedure is successfully completed.
  • the terminal device 120 may receive one or more configurations of the third set of RSs for new/candidate beam identification from the network device 110. In some embodiments, the terminal device 120 may determine the third set of RSs for new/candidate beam identification based on the first set of RSs for new/candidate beam identification and the second set of RSs for new/candidate beam identification.
  • the third set of RSs for new/candidate beam identification may be a union set of the first set of RSs for new/candidate beam identification and the second set of RSs for new/candidate beam identification.
  • NBI_set_0 candidateBeamRSList_1 ⁇ candidateBeamRSList_2.
  • at least one RS in the third set of RSs for new/candidate beam identification is different from any one of RS in the first set of RSs for new/candidate beam identification and the second set of RSs for new/candidate beam identification.
  • Figs. 6A –6D illustrate examples in accordance with some embodiments of the present disclosure.
  • the terminal device 120 may be configured with a first timer (Time_1) in a first procedure (beam failure procedure 1) .
  • the first procedure is for the first TRP (TRP1) .
  • the beam failure detection is based on the first set of RSs for beam failure detection (BFD_set_1) .
  • BFI_COUNTER_1 the value of a first counter (BFI_COUNTER_1) is increased by 1.
  • BFI_COUNTER_1 is larger than or equal to the first maximum value (beamFailureInstanceMaxCount_1) , a BFR is triggered for the first procedure.
  • the first TRP (TRP1) is failed.
  • the terminal device 120 may be configured with a second timer (Time_2) in a second procedure (beam failure procedure 2) .
  • the second procedure is for the second TRP (TRP2) .
  • the beam failure detection is based on the second set of RSs for beam failure detection (BFD_set_2) .
  • BFI_COUNTER_2 the value of a second counter
  • BFI_COUNTER_2 is larger than or equal to the second maximum value (beamFailureInstanceMaxCount_2)
  • a BFR is triggered for the second procedure.
  • the second TRP (TRP2) is failed.
  • the terminal device 120 may be configured with a third timer (Time_0) in a third procedure (beam failure procedure 0) .
  • the third procedure is for the cell, and the first TRP and the second TRP are configured in the cell.
  • the value of a third counter (BFI_COUNTER_0) is increased by 1.
  • BFI_COUNTER_0 is larger than or equal to the third maximum value (beamFailureInstanceMaxCount_0)
  • a BFR is triggered for the third procedure. For example, the cell is failed.
  • the set of RSs for beam failure detection and/or the timer for beam failure detection related to the third procedure may depend on a first condition in the first procedure and/or in the second procedure.
  • the first condition may be at least one of: a BFR is triggered in the first procedure, a BFR is triggered in the second procedure, before beam failure recovery is successfully completed in the first procedure, and before beam failure recovery is successfully completed in the second procedure.
  • beam failure detection related to the third procedure may be based on the second set of RSs for beam failure detection and/or the second timer. For example, if the first condition is satisfied, and if a beam failure instance indication is indicated or received from the lower layers of the terminal device, the terminal device may start or restart the second timer.
  • beam failure detection related to the third procedure may be based on the third set of RSs for beam failure detection and/or the third timer. For example, if the first condition is not satisfied, and if a beam failure instance indication is indicated or received from the lower layers of the terminal device, the terminal device may start or restart the third timer.
  • the terminal device 120 may be configured with a first timer (Time_1) in a first procedure (beam failure procedure 1) .
  • the first procedure is for the first TRP (TRP1) .
  • the beam failure detection is based on the first set of RSs for beam failure detection (BFD_set_1) .
  • BFI_COUNTER_1 the value of a first counter (BFI_COUNTER_1) is increased by 1.
  • BFI_COUNTER_1 is larger than or equal to the first maximum value (beamFailureInstanceMaxCount_1) , a BFR is triggered for the first procedure.
  • the first TRP (TRP1) is failed.
  • the terminal device 120 may be configured with a second timer (Time_2) in a second procedure (beam failure procedure 2) .
  • the second procedure is for the second TRP (TRP2) .
  • the beam failure detection is based on the second set of RSs for beam failure detection (BFD_set_2) .
  • BFI_COUNTER_2 the value of a second counter
  • BFI_COUNTER_2 is larger than or equal to the second maximum value (beamFailureInstanceMaxCount_2)
  • a BFR is triggered for the second procedure.
  • the second TRP (TRP2) is failed.
  • the terminal device 120 may be configured with a third timer (Time_0) in a third procedure (beam failure procedure 0) .
  • the third procedure is for the cell, and the first TRP and the second TRP are configured in the cell.
  • beam failure detection in the third procedure may be based on the second set of RSs for beam failure detection (BFD_set_2) .
  • beam failure detection in the third procedure may be based on the third set of RSs for beam failure detection (BFD_set_0) .
  • BFI_COUNTER_0 the value of a third counter
  • the terminal device may start or restart the second timer (Timer_2) .
  • the terminal device may start or restart the third timer (Timer_0) .
  • At least one of the following terminal device variables may be used for the beam failure detection procedures:
  • the MAC entity of the terminal device shall for each for each Serving Cell configured for beam failure detection and configured with TRP-specific BFR and cell-specific BFR:
  • beamFailureDetectionTimer_1, beamFailureInstanceMaxCount_1, or any of the reference signals used for beam failure detection is reconfigured (For example, by upper layers or by lower layers or by physical layer) associated with for the first TRP of this Serving Cell:
  • the terminal device 120 may be configured with a first timer (Time_1) in a first procedure (beam failure procedure 1) .
  • the first procedure is for the first TRP (TRP1) .
  • the beam failure detection is based on the first set of RSs for beam failure detection (BFD_set_1) .
  • BFI_COUNTER_1 the value of a first counter (BFI_COUNTER_1) is increased by 1.
  • BFI_COUNTER_1 is larger than or equal to the first maximum value (beamFailureInstanceMaxCount_1) , a BFR is triggered for the first procedure.
  • the first TRP (TRP1) is failed.
  • the terminal device 120 may be configured with a third timer (Time_0) in a third procedure (beam failure procedure 0) .
  • the third procedure is for the cell, and the first TRP and the second TRP are configured in the cell.
  • beam failure recovery procedure 1 is performed.
  • the value of BFI_COUNTER_0 is set to 0 related to the third procedure.
  • the terminal device may perform beam failure recovery related to the third procedure. For example, the terminal device may select a new candidate RS from the third set of RS for new/candidate beam identification.
  • a BFR or a random access procedure may be triggered related to the third procedure.
  • the first procedure or the second procedure is cancelled or the value of BFI_COUNTER_1 is set to 0 or the value of the BFI_COUNTER_2 is set to 0.
  • the terminal device may perform beam failure recovery related to the third procedure.
  • the terminal device may select a new candidate RS from the third set of RS for new/candidate beam identification.
  • the value of BFI_COUNTER_0 is set to 0.
  • the terminal device may start or restart the third timer, and before the third timer expires, if a BFR or a random access procedure is triggered related to the third procedure, the first procedure or the second procedure is cancelled or the value of BFI_COUNTER_1 is set to 0 or the value of the BFI_COUNTER_2 is set to 0.
  • the terminal device may perform beam failure recovery related to the third procedure. For example, the terminal device may select a new candidate RS from the third set of RS for new/candidate beam identification.
  • the terminal device 120 may receive a configuration of the first duration from the network device 110.
  • the first duration may be between a timing when a BFR is triggered related to either the first procedure or the second procedure and a timing when the beam failure recovery procedure is successfully completed related to either the first procedure or the second procedure.
  • the first duration may be from a timing when a BFR is triggered related to either the first procedure or the second procedure to a timing when the beam failure recovery procedure is successfully completed related to either the first procedure or the second procedure.
  • the terminal device may start or restart the third timer, and before the third timer expires, if the value of BFI_COUNTER_0 is larger than or equal to the third maximum value, a BFR or a random access procedure may be triggered related to the third procedure.
  • the first procedure or the second procedure is cancelled or the value of BFI_COUNTER_0 is set to 0 or the value of the BFI_COUNTER_1 is set to 0.
  • the terminal device may perform beam failure recovery related to the third procedure.
  • the terminal device may select a new candidate RS from the third set of RS for new/candidate beam identification.
  • the value of BFI_COUNTER_0 is set to 0. In some embodiments, before the third timer expires, and if a BFR or a random access procedure is not triggered related to the third procedure or if the value of BFI_COUNTER_0 is less than the third maximum value, the value of BFI_COUNTER_0 is set to 0.
  • the terminal device 120 may be configured with a first timer (Time_1) in a first procedure (beam failure procedure 1) .
  • the first procedure is for the first TRP (TRP1) .
  • the beam failure detection is based on the first set of RSs for beam failure detection (BFD_set_1) .
  • BFI_COUNTER_1 the value of a first counter (BFI_COUNTER_1) is increased by 1.
  • BFI_COUNTER_1 is larger than or equal to the first maximum value (beamFailureInstanceMaxCount_1) , a BFR is triggered for the first procedure.
  • the first TRP (TRP1) is failed.
  • the terminal device 120 may be configured with a second timer (Time_2) in a second procedure (beam failure procedure 2) .
  • the second procedure is for the second TRP (TRP2) .
  • the beam failure detection is based on the second set of RSs for beam failure detection (BFD_set_2) .
  • BFI_COUNTER_2 the value of a second counter
  • BFI_COUNTER_2 is larger than or equal to the second maximum value (beamFailureInstanceMaxCount_2)
  • a BFR is triggered for the second procedure.
  • the second TRP (TRP2) is failed.
  • the terminal device 120 may be configured with a third timer (Time_0) in a third procedure (beam failure procedure 0) .
  • the third procedure is for the cell, and the first TRP and the second TRP are configured in the cell.
  • the terminal device 120 may start or restart the third timer (Timer_0) .
  • the third timer (Timer_0) expires, if beam failure instance indication 2 is indicated or received related to the second procedure, then the value of BFI_COUNTER_0 is increased by 1.
  • the third timer (Timer_0) expires, the value of BFI_COUNTER_0 is set to 0.
  • the first timer related to the first procedure may be smaller than or no larger than the second timer related to the second procedure.
  • the terminal device may receive one or more configurations of priority for at least one of the first procedure and the second procedure.
  • the first procedure may be configured with a priority higher than the second procedure.
  • the first procedure may be configured with a priority lower than the second procedure.
  • the terminal device may perform a TRP specific BFR procedure. For example, no BFR is triggered related to the first procedure. In some embodiments, if a BFR is triggered related to the first procedure or if the value of the first counter is larger than or equal to the first maximum value related to the first procedure, the terminal device may perform a random access procedure or a cell specific BFR procedure. In some embodiments, the terminal device may be configured with the first procedure and the second procedure on a BWP of the cell. For example, the first procedure may be a cell specific BFR procedure or a random access based procedure. For example, the second procedure may be a TRP specific BFR procedure. In some embodiments, the first procedure may be configured with a higher priority than the second procedure.
  • the terminal device may start to perform the second procedure. For example, if within a duration, the value of the second counter is larger than or equal to the second maximum value related to the second procedure, then a random access procedure may be initiated or a cell specific BFR related to the third procedure may be triggered, otherwise, a BFR related to the first procedure may be triggered.
  • the terminal device may start or restart the third timer, and the value of the second counter may be set to 0, and beam failure detection may be based on the second set of RSs for beam failure detection related to the second procedure.
  • the terminal device may initiate a random access procedure or a cell specific BFR procedure, otherwise, the terminal device may trigger a BFR related to the first procedure.
  • the new candidate beam/RS for the random access procedure or the cell specific BFR procedure is same with the new candidate beam/RS related to the first procedure. In some embodiments, the new candidate beam/RS for the random access procedure or the cell specific BFR procedure is selected based on the first set of RSs for new/candidate beam identification.
  • a BFR if a BFR is triggered or a random access procedure is triggered related to the third procedure, then multi-TRP transmission (based on the first TRP and the second TRP) falls back to single-TRP transmission between the network device and the terminal device.
  • a BFR if a BFR is triggered or a random access procedure is triggered related to the third procedure, then communication between the network device and the terminal device changes from based on the first TRP and the second TRP to based on a single TRP.
  • the power for a random access preamble transmission related to the third procedure may be determined based on one or more power parameters and/or a number of beam failure recovery request (BFRQ) transmissions related to at least one of the first procedure and the second procedure.
  • BFRQ beam failure recovery request
  • the initial power for the random access preamble transmission related to the third procedure may be determined based on the maximum one of a reference power for scheduling request (SR) or beam failure request (BFR) or BFRQ transmission between the first procedure and the second procedure.
  • SR reference power for scheduling request
  • BFR beam failure request
  • BfrqTrans_COUNTER_1 there may be a parameter (For example, BfrqTrans_COUNTER_1) for counting a number of BFRQ transmissions within a duration related to the first procedure.
  • BfrqTrans_MaxCount_1 may be configured by the network device.
  • BfrqTrans_COUNTER_2 there may be a parameter (For example, BfrqTrans_COUNTER_2) for counting a number of BFRQ transmissions within a duration related to the second procedure.
  • BfrqTrans_MaxCount_2 may be configured by the network device.
  • the duration may be between a timing when a BFR is triggered in the first procedure or the second procedure, and a timing when beam failure recovery is successfully completed in the first procedure or the second procedure. In some embodiments, the duration may be between a timing when a BFR is triggered in the first procedure or the second procedure, and a timing when a BFR is triggered or a random access procedure is initiated related to the third procedure. For example, the timing when a BFR is triggered or a random access procedure is initiated related to the third procedure is earlier than or no later than the timing when beam failure recovery is successfully completed in the first procedure or the second procedure. In some embodiments, the duration may be between the first BFRQ transmission and the BFRQ transmission with an index of BfrqTrans_COUNTER_1 or BfrqTrans_COUNTER_2 related to the first procedure or the second procedure.
  • the power for the random access preamble transmission related to the third procedure may be determined based on BfrqTrans_COUNTER_1 and/or BfrqTrans_COUNTER_2.
  • the value of PREAMBLE_POWER_RAMPING_COUNTER may be set to the maximum value between BfrqTrans_COUNTER_1 and BfrqTrans_COUNTER_2.
  • PREAMBLE_POWER_RAMPING_COUNTER max(BfrqTrans_COUNTER_1, BfrqTrans_COUNTER_2) or max (BfrqTrans_MaxCount_1, BfrqTrans_MaxCount_2 ) .
  • PREAMBLE_POWER_RAMPING_COUNTER max(BfrqTrans_COUNTER_1, BfrqTrans_COUNTER_2) or max (BfrqTrans_MaxCount_1, BfrqTrans_MaxCount_2 ) .
  • PREAMBLE_RECEIVED_TARGET_POWER may be determined based on (PREAMBLE_POWER_RAMPING_COUNTER + max (BfrqTrans_COUNTER_1, BfrqTrans_COUNTER_2) –1) ⁇ PREAMBLE_POWER_RAMPING_STEP or (PREAMBLE_POWER_RAMPING_COUNTER + max (BfrqTrans_MaxCount_1, BfrqTrans_MaxCount_2 ) –1) ⁇ PREAMBLE_POWER_RAMPING_STEP. For example, for the first random access preamble transmission.
  • the power for the random access preamble transmission related to the third procedure may be determined based on a power offset (For example, POWER_OFFSET_BFRQ) , wherein the power offset may be determined based on the BFRQ transmission (s) in the first procedure and/or the second procedure.
  • a power offset For example, POWER_OFFSET_BFRQ
  • the power offset may be determined based on the BFRQ transmission (s) in the first procedure and/or the second procedure.
  • PREAMBLE_RECEIVED_TARGET_POWER may be determined based on preambleReceivedTargetPower + POWER_OFFSET_BFRQ. For example, for the first random access preamble transmission.
  • the power offset may be determined based on the offset between the power for a first BFRQ transmission and a maximum value of power for BFRQ transmission within the duration related to the first procedure and/or the second procedure.
  • the power offset may be determined based on an offset between the power caused by transmission power control (TPC) for the first BFRQ transmission and the maximum/peak value of (accumulated) TPC within the duration related to the first procedure and/or the second procedure.
  • TPC transmission power control
  • the power offset may be max (TPC_1, TPC_2) or max (max (TPC_1, TPC_2) , 0) .
  • TPC_1 may be related to the first procedure.
  • TPC_2 may be related to the second procedure.
  • the first procedure, the second procedure and the third procedure may be configured simultaneously for the cell. In some embodiments, the first procedure and the second procedure may be configured simultaneously for a BWP for the cell. In some embodiments, the first procedure/the second procedure and the third procedure may not be configured simultaneously for a same BWP for the cell.
  • the first procedure and the second procedure may be configured for a first BWP.
  • the first BWP is configured with the first TRP and the second TRP.
  • the third procedure may not be configured for the first BWP.
  • the third procedure may be configured for a second BWP.
  • the second BWP may be configured with a single TRP.
  • the first procedure and the second procedure may be stopped or cancelled, and the third procedure may be performed.
  • beam failure detection related to the third procedure may be based on the first set of RSs and/or the first timer for beam failure detection.
  • the first procedure may be stopped or cancelled, and the third procedure and the second procedure may be performed.
  • a BFR is triggered related to the second procedure, a BFRQ is transmitted and no PDCCH monitoring based on the beam/RS related to the second procedure.
  • the third procedure may be stopped or cancelled, and the first procedure and the second procedure may be performed.
  • the first procedure and the second procedure may be started to be performed.
  • the terminal device 120 may receive a detected downlink control information (DCI) , and the detected DCI may indicate a BWP switching and a TCI state. And the detected DCI may schedule a PDSCH transmission. The terminal device may applied the indicated TCI state to the scheduled PDSCH after BWP switching.
  • DCI downlink control information
  • the terminal device may receive a first detected DCI on a first BWP, wherein the first detected DCI may indicate a second BWP.
  • the terminal device may receive an indication of a combination of a first TCI state and a second TCI state.
  • the terminal device may discard the second TCI state for a communication between the terminal device and the network device based on a configuration of the second BWP.
  • the communication may be receiving a set of CORESETs, PDSCH and RS from the network device.
  • the communication may be transmitting a set of PUCCHs, PUSCH and RS to the network device.
  • the indication of the combination may be received in the first detected DCI or in a second detected DCI.
  • the second detected DCI may be received later than or no earlier than the first detected DCI.
  • the terminal device may receive a first set of CORESETs with the first TCI state after a timing on the second BWP, and the terminal device may transmit a first set of PUCCHs with the first TCI state after the timing on a first uplink BWP, and the terminal device may transmit a second set of PUCCHs with the second TCI state after the timing on the first uplink BWP.
  • the second TCI state may not be applied for a downlink reception on the second BWP.
  • the second BWP is a downlink BWP.
  • the terminal device may receive a configuration of the first set of CORESETs for the second BWP, wherein the second BWP is a downlink BWP. In some embodiments, the terminal device may receive one or more configurations of the first set of PUCCHs and the second set of PUCCHs for the first uplink BWP.
  • the terminal device may receive the second set of CORESETs with the first TCI state after the timing on the first BWP, and the terminal device may receive the third set of CORESETs with the second TCI state after the timing, and the terminal device may transmit a third set of PUCCHs with the first TCI state after the timing on the second BWP.
  • the second TCI state may not be applied for an uplink transmission on the second BWP, wherein the second BWP may be an uplink BWP.
  • the terminal device may receive a configuration of the third set of PUCCHs for the second BWP, wherein the second BWP is an uplink BWP.
  • the terminal device may receive one or more configurations of the first BWP and the second BWP for the cell. In some embodiments, the terminal device may receive a configuration of the first uplink BWP for the cell.
  • the terminal device may receive an activation command, wherein the activation command is used to map a set of combinations of one or two TCI states to a set of codepoints, wherein the set comprises the combination of the first TCI state and the second TCI state.
  • the terminal device may be configured with a first downlink BWP, and the first downlink BWP may be configured with two TRPs. For example, the first TRP and the second TRP.
  • the terminal device may be configured with a first uplink BWP, wherein the first uplink BWP may be configured with two TRPs. For example, the first TRP and the second TRP.
  • the terminal device may be configured with a first subset of CORESETs and a second subset of CORESETs on the first downlink BWP.
  • a first TCI state (for example, a first joint TCI) may be applied for the first subset of CORESETs.
  • a second TCI state (for example, a second joint TCI) may be applied for the second subset of CORESETs.
  • the terminal device may be configured with a third subset of CORESETs on a second downlink BWP.
  • the second downlink BWP may be configured with a single TRP.
  • the first TRP For example, the first TRP.
  • a third TCI state (for example, a third joint TCI) may be indicated or applied for the third subset of CORESETs.
  • the third subset of CORESETs may be same with either one of the first subset of CORESETs or the second subset of CORESETs.
  • the terminal device may receive a first detected DCI, wherein the first detected DCI may indicate a downlink BWP switching. For example, from the first downlink BWP to the second downlink BWP.
  • the terminal device may receive an indication of a combination of a third TCI state and a fourth TCI state. In some embodiments, only one of the third TCI state and the fourth TCI state which is associated with the third subset of CORESETs is applied for downlink reception and/or uplink transmission. For example, applied for the third subset of CORESETs.
  • the third TCI state is applied for downlink reception (for example, applied for the third subset of CORESETs) on the second downlink BWP
  • the fourth TCI state is not applied for downlink reception (for example, not applied to any one of CORESET or PDSCH) on the second downlink BWP.
  • both the third TCI state and the fourth TCI state may be applied for uplink transmission on the first uplink BWP.
  • Figs. 7A –7B illustrate examples in accordance with some embodiments of the present disclosure.
  • the terminal device 120 may be configured with a first downlink BWP (DL BWP 1) and an uplink BWP (UL BWP 1) .
  • the terminal device 120 may be configured with a second downlink BWP (DL BWP 2) .
  • the DL BWP 1 and the UL BWP 1 may be configured with two TRPs (TRP1 and TRP2) .
  • the second downlink BWP may be configured with one TRP (TRP1) .
  • joint TCI 1 may be applied for uplink and downlink communication between the terminal device and the network device with TRP1.
  • joint TCI 2 may be applied for uplink and downlink communication between the terminal device and the network device with TRP2.
  • the terminal device may receive a downlink BWP switching (from DL BWP 1 to DL BWP 2) .
  • the terminal device may receive a TCI codepoint corresponding to joint TCI 3 and joint TCI 4.
  • the joint TCI 4 may be ignored or discarded for uplink and downlink communication between the terminal device and the network device. For example, based on TRP2.
  • the terminal device 120 may be configured with a first downlink BWP (DL BWP 1) and an uplink BWP (UL BWP 1) .
  • the terminal device 120 may be configured with a second downlink BWP (DL BWP 2) .
  • the DL BWP 1 and the UL BWP 1 may be configured with two TRPs (TRP1 and TRP2) .
  • the second downlink BWP may be configured with one TRP (TRP1) .
  • joint TCI 1 may be applied for uplink and downlink communication between the terminal device and the network device with TRP1.
  • joint TCI 2 may be applied for uplink and downlink communication between the terminal device and the network device with TRP2.
  • the terminal device may receive a downlink BWP switching (from DL BWP 1 to DL BWP 2) .
  • the terminal device may receive a TCI codepoint corresponding to joint TCI 3 and joint TCI 4.
  • the joint TCI 4 may be ignored or discarded for downlink communication between the terminal device and the network device.
  • the joint TCI 4 may be applied for uplink communication between the terminal device and the network device. For example, based on TRP2.
  • the timing may be a beam application timing.
  • the timing may be the first slot or first subslot that is at least X ms or Y symbols after the last symbol of the acknowledge of the first detected DCI or the second detected DCI.
  • the network device 110 may transmit to the terminal device 120, a first DCI on a first BWP, wherein the first DCI indicates a second BWP, and transmit an indication of a combination of a first TCI state and a second TCI state, and the network device 110 may discard the second TCI state for a communication between the network device 110 and the terminal device 120 based on a configuration of the second BWP.
  • the network device 110 may transmit the indication of the combination in the first DCI or in a second DCI.
  • the second DCI is transmitted later than or no earlier than the first DCI.
  • the network device 110 may transmit a first set of control resource sets (CORESETs) with the first TCI state after a timing on the second BWP; and receive a first set of physical uplink control channels (PUCCHs) with the first TCI state after the timing on a first uplink BWP; and receive a second set of PUCCHs with the second TCI state after the timing on the first uplink BWP; and the second TCI state is not applied for a downlink transmission on the second BWP, wherein the second BWP is a downlink BWP.
  • CORESETs control resource sets
  • PUCCHs physical uplink control channels
  • the network device 110 may transmit a configuration of the first set of CORESETs for the second BWP, wherein the second BWP is a downlink BWP; and transmit one or more configurations of the first set of PUCCHs and the second set of PUCCHs for the first uplink BWP.
  • the network device 110 may transmit one or more configurations of a second set of CORESETs and a third set of CORESETs for the first BWP, wherein the first BWP is a downlink BWP.
  • the network device 110 may transmit the second set of CORESETs with the first TCI state after the timing on the first BWP; and transmit the third set of CORESETs with the second TCI state after the timing on the first BWP; and receive a third set of physical uplink control channels (PUCCHs) with the first TCI state after the timing on the second BWP; and the second TCI state is not applied for an uplink reception on the second BWP, wherein the second BWP is an uplink BWP.
  • PUCCHs physical uplink control channels
  • the network device 110 may transmit a configuration of the third set of PUCCHs for the second BWP, wherein the second BWP is an uplink BWP.
  • the network device 110 may transmit one or more configurations of the first BWP and the second BWP for a cell.
  • the network device 110 may transmit a configuration of the first uplink BWP for the cell.
  • the network device 110 may transmit an activation command to map a set of combinations of one or two TCI states to a set of codepoints, wherein the set comprises the combination of the first TCI state and the second TCI state.
  • FIG. 8 illustrates a flowchart of an example method 800 in accordance with some embodiments of the present disclosure.
  • the method 800 can be implemented at the terminal device 120 as shown in FIG. 1.
  • the terminal device 120 receives a configuration from a network device (for example, the network device 110 as shown in FIG. 1) , where the configuration indicates that each of a group of cells serving the terminal device is associated with at least one of a plurality of TRPs (for example, the TRPs 130-1 and 130-2 as shown in FIG. 1) coupled with the network device.
  • a network device for example, the network device 110 as shown in FIG. 1
  • the configuration indicates that each of a group of cells serving the terminal device is associated with at least one of a plurality of TRPs (for example, the TRPs 130-1 and 130-2 as shown in FIG. 1) coupled with the network device.
  • the terminal device 120 transmits a beam failure recovery request to the network device, where the beam failure recovery request comprises TRP information related to the beam failure detected on the cell.
  • each of the plurality of TRPs may be represented by at least one of the following: a CORESET pool index; a CORESET group identifier; an identifier of a set of RSs for beam failure detection; an identifier of a set of RSs for new/candidate beam identification; spatial relation information; a SRS resource set; a TCI state; and a set of QCL parameters.
  • the plurality of TRPs may comprise a first TRP and a second TRP
  • the group of cells may comprise a first subset of cells associated with the first TRP and a second subset of cells associated with the second TRP
  • the first subset of cells may be configured with a first set of RSs for beam failure detection and a first set of RSs for new/candidate beam identification
  • the second subset of cells may be configured with a second set of RSs for beam failure detection and a second set of RSs for new/candidate beam identification.
  • the terminal device 120 may transmit a first beam failure recovery request to the network device, where the first beam failure recovery request at least comprises an indication of the first TRP or the first subset of cells.
  • the terminal device 120 may transmit a second beam failure recovery request to the network device, where the second beam failure recovery request at least comprises an indication of the second TRP or the second subset of cells.
  • the cell may be associated with the plurality of TRPs and the TRP information may indicate one of the plurality of TRPs related to the beam failure detected on the cell.
  • the TRP information may comprise an indication of a TRP index common to all cells indicated in the beam failure recovery request.
  • the TRP information may comprise an indication of a respective TRP index for each of cells indicated in the beam failure recovery request.
  • the cell may be associated with the plurality of TRPs and the TRP information may comprise at least one of the following: first information indicating the number of TRPs related to the beam failure detected on the cell; second information indicating an index of one of the plurality of TRPs related to the beam failure detected on the cell; and third information indicating on which one of the plurality of TRPs a new beam is identified.
  • the cell may be associated with the plurality of TRPs and the TRP information may comprise: first information indicating the number of TRPs related to the beam failure detected on the cell; and second information indicating a RS index for a new beam identified on one TRP of the plurality of TRPs, where the RS index indicates an index of the one TRP.
  • FIG. 9 illustrates a flowchart of an example method 900 in accordance with some embodiments of the present disclosure.
  • the method 900 can be implemented at the network device 110 as shown in FIG. 1.
  • the network device 110 transmits a configuration to a terminal device (for example, the terminal device 120 as shown in FIG. 1) , where the configuration indicates that each of a group of cells serving the terminal device is associated with at least one of a plurality of TRPs (for example, the TRPs 130-1 and 130-2 as shown in FIG. 1) coupled with the network device 110.
  • a terminal device for example, the terminal device 120 as shown in FIG. 1
  • the configuration indicates that each of a group of cells serving the terminal device is associated with at least one of a plurality of TRPs (for example, the TRPs 130-1 and 130-2 as shown in FIG. 1) coupled with the network device 110.
  • the network device 110 receives a beam failure recovery request from the terminal device, where the beam failure recovery request comprises TRP information related to the beam failure detected on the cell.
  • each of the plurality of TRPs may be represented by at least one of the following: a CORESET pool index; a CORESET group identifier; an identifier of a set of RSs for beam failure detection; an identifier of a set of RSs for new/candidate beam identification; spatial relation information; a SRS resource set; a TCI state; and a set of QCL parameters.
  • the plurality of TRPs may comprise a first TRP and a second TRP
  • the group of cells may comprise a first subset of cells associated with the first TRP and a second subset of cells associated with the second TRP
  • the first subset of cells may be configured with a first set of RSs for beam failure detection and a first set of RSs for new/candidate beam identification
  • the second subset of cells may be configured with a second set of RSs for beam failure detection and a second set of RSs for new/candidate beam identification.
  • the network device 110 may receive a first beam failure recovery request from the terminal device, where the first beam failure recovery request at least comprises an indication of the first TRP or the first subset of cells.
  • the network device 110 may receive a second beam failure recovery request from the terminal device, where the second beam failure recovery request at least comprises an indication of the second TRP or the second subset of cells.
  • the cell may be associated with the plurality of TRPs and the TRP information may indicate one of the plurality of TRPs related to the beam failure detected on the cell.
  • the TRP information may comprise an indication of a TRP index common to all cells indicated in the beam failure recovery request.
  • the TRP information may comprise an indication of a respective TRP index for each of cells indicated in the beam failure recovery request.
  • the cell may be associated with the plurality of TRPs and the TRP information may comprise at least one of the following: first information indicating the number of TRPs related to the beam failure detected on the cell; second information indicating an index of one of the plurality of TRPs related to the beam failure detected on the cell; and third information indicating on which one of the plurality of TRPs a new beam is identified.
  • the cell may be associated with the plurality of TRPs and the TRP information may comprise: first information indicating the number of TRPs related to the beam failure detected on the cell; and second information indicating a RS index for a new beam identified on one TRP of the plurality of TRPs, where the RS index indicates an index of the one TRP.
  • a terminal device comprises circuitry configured to: receive a configuration from a network device, wherein the configuration indicates that each of a group of cells serving the terminal device is associated with at least one of a plurality of transmission and reception points (TRPs) coupled with the network device; and in response to a beam failure being detected on a cell in the group of cells, transmit a beam failure recovery request to the network device, wherein the beam failure recovery request comprises TRP information related to the beam failure detected on the cell.
  • TRPs transmission and reception points
  • each of the plurality of TRPs is represented by at least one of the following: a control resource set (CORESET) pool index; a CORESET group identifier; an identifier of a set of reference signals (RSs) for beam failure detection; an identifier of a set of RSs for new/candidate beam identification; spatial relation information; a sounding reference signal (SRS) resource set; a transmission configuration indicator (TCI) state; and a set of quasi co-location parameters.
  • CORESET control resource set
  • RSs reference signals
  • TCI transmission configuration indicator
  • the plurality of TRPs comprise a first TRP and a second TRP
  • the group of cells comprise a first subset of cells associated with the first TRP and a second subset of cells associated with the second TRP
  • the first subset of cells are configured with a first set of RSs for beam failure detection and a first set of RSs for new/candidate beam identification
  • the second subset of cells are configured with a second set of RSs for beam failure detection and a second set of RSs for new/candidate beam identification.
  • the terminal device comprises circuitry configured to: in response to a beam failure being detected based on the first set of RSs, transmit a first beam failure recovery request to the network device, wherein the first beam failure recovery request at least comprises an indication of the first TRP or the first subset of cells; and in response to a beam failure being detected based on the second set of RSs for beam failure detection, transmit a second beam failure recovery request to the network device, wherein the second beam failure recovery request at least comprises an indication of the second TRP or the second subset of cells.
  • the cell is associated with the plurality of TRPs and the TRP information indicates one of the plurality of TRPs related to the beam failure detected on the cell.
  • the TRP information comprises an indication of a TRP index common to all cells indicated in the beam failure recovery request.
  • the TRP information comprises an indication of a respective TRP index for each of cells indicated in the beam failure recovery request.
  • the cell is associated with the plurality of TRPs and the TRP information comprises at least one of the following: first information indicating the number of TRPs related to the beam failure detected on the cell; second information indicating an index of one of the plurality of TRPs related to the beam failure detected on the cell; and third information indicating on which one of the plurality of TRPs a new beam is identified.
  • the cell is associated with the plurality of TRPs and the TRP information comprises: first information indicating the number of TRPs related to the beam failure detected on the cell; and second information indicating a RS index for a new beam identified on one TRP of the plurality of TRPs, wherein the RS index indicates an index of the one TRP.
  • a network device comprises circuitry configured to: transmit a configuration from to a terminal device, wherein the configuration indicates that each of a group of cells serving the terminal device is associated with at least one of a plurality of transmission and reception points (TRPs) coupled with the network device; and in response to a beam failure being detected on a cell in the group of cells, receive a beam failure recovery request from the terminal device, wherein the beam failure recovery request comprises TRP information related to the beam failure detected on the cell.
  • TRPs transmission and reception points
  • each of the plurality of TRPs is represented by at least one of the following: a control resource set (CORESET) pool index; a CORESET group identifier; an identifier of a set of reference signals (RSs) for beam failure detection; an identifier of a set of RSs for new/candidate beam identification; spatial relation information; a sounding reference signal (SRS) resource set; a transmission configuration indicator (TCI) state; and a set of quasi co-location parameters.
  • CORESET control resource set
  • RSs reference signals
  • TCI transmission configuration indicator
  • the plurality of TRPs comprise a first TRP and a second TRP
  • the group of cells comprise a first subset of cells associated with the first TRP and a second subset of cells associated with the second TRP
  • the first subset of cells are configured with a first set of RSs for beam failure detection and a first set of RSs for new/candidate beam identification
  • the second subset of cells are configured with a second set of RSs for beam failure detection and a second set of RSs for new/candidate beam identification.
  • the network device comprises circuitry configured to: in response to a beam failure being detected based on the first set of RSs, receive a first beam failure recovery request from the terminal device, wherein the first beam failure recovery request at least comprises an indication of the first TRP or the first subset of cells; and in response to a beam failure being detected based on the second set of RSs for beam failure detection, receive a second beam failure recovery request from the terminal device, wherein the second beam failure recovery request at least comprises an indication of the second TRP or the second subset of cells.
  • the cell is associated with the plurality of TRPs and the TRP information indicates one of the plurality of TRPs related to the beam failure detected on the cell.
  • the TRP information comprises an indication of a TRP index common to all cells indicated in the beam failure recovery request.
  • the TRP information comprises an indication of a respective TRP index for each of cells indicated in the beam failure recovery request.
  • the cell is associated with the plurality of TRPs and the TRP information comprises at least one of the following: first information indicating the number of TRPs related to the beam failure detected on the cell; second information indicating an index of one of the plurality of TRPs related to the beam failure detected on the cell; and third information indicating on which one of the plurality of TRPs a new beam is identified.
  • the cell is associated with the plurality of TRPs and the TRP information comprises: first information indicating the number of TRPs related to the beam failure detected on the cell; and second information indicating a RS index for a new beam identified on one TRP of the plurality of TRPs, wherein the RS index indicates an index of the one TRP.
  • FIG. 10 is a simplified block diagram of a device 1000 that is suitable for implementing embodiments of the present disclosure.
  • the device 1000 can be considered as a further example implementation of the network device 110, the TRP 130 and/or the terminal device 120 as shown in FIG. 1. Accordingly, the device 1000 can be implemented at or as at least a part of the network device 110, the TRP 130 and/or the terminal device 120 as shown in FIG. 1.
  • the device 1000 includes a processor 1010, a memory 1020 coupled to the processor 1010, a suitable transmitter (TX) and receiver (RX) 1040 coupled to the processor 1010, and a communication interface coupled to the TX/RX 1040.
  • the memory 1010 stores at least a part of a program 1030.
  • the TX/RX 1040 is for bidirectional communications.
  • the TX/RX 1040 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones.
  • the communication interface may represent any interface that is necessary for communication with other network elements, such as X2 interface for bidirectional communications between eNBs, S1 interface for communication between a Mobility Management Entity (MME) /Serving Gateway (S-GW) and the eNB, Un interface for communication between the eNB and a relay node (RN) , or Uu interface for communication between the eNB and a terminal device.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • Un interface for communication between the eNB and a relay node (RN)
  • Uu interface for communication between the eNB and a terminal device.
  • the program 1030 is assumed to include program instructions that, when executed by the associated processor 1010, enable the device 1000 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIG. 1 to FIG. 9.
  • the embodiments herein may be implemented by computer software executable by the processor 1010 of the device 1000, or by hardware, or by a combination of software and hardware.
  • the processor 1010 may be configured to implement various embodiments of the present disclosure.
  • a combination of the processor 1010 and memory 1020 may form processing means 1050 adapted to implement various embodiments of the present disclosure.
  • the memory 1020 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 1020 is shown in the device 1000, there may be several physically distinct memory modules in the device 1000.
  • the processor 1010 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 1000 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to FIGs 10 and 11.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • the machine readable medium may be a machine readable signal medium or a machine readable storage medium.
  • a machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • machine readable storage medium More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM portable compact disc read-only memory
  • magnetic storage device or any suitable combination of the foregoing.

Landscapes

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

Abstract

Des modes de réalisation de la présente divulgation concernent des procédés, des dispositifs et des supports de stockage informatiques pour des communications. Un procédé consiste à : recevoir sur un dispositif terminal, en provenance d'un dispositif réseau, un premier ensemble de signaux de référence (RS) et un second ensemble de RS ; recevoir une ou plusieurs configurations d'un premier temporisateur et d'un second temporisateur ; effectuer une détection de défaillance de faisceau associée à une première procédure d'après le premier ensemble et le premier temporisateur ; effectuer une détection de défaillance de faisceau associée à une deuxième procédure d'après le second ensemble et le second temporisateur ; et exécuter une troisième procédure d'après une première condition et/ou un premier paramètre associé à la première procédure et/ou à la deuxième procédure.
PCT/CN2021/111353 2021-08-06 2021-08-06 Procédés et dispositifs de communication WO2023010580A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/111353 WO2023010580A1 (fr) 2021-08-06 2021-08-06 Procédés et dispositifs de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/111353 WO2023010580A1 (fr) 2021-08-06 2021-08-06 Procédés et dispositifs de communication

Publications (1)

Publication Number Publication Date
WO2023010580A1 true WO2023010580A1 (fr) 2023-02-09

Family

ID=85154212

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/111353 WO2023010580A1 (fr) 2021-08-06 2021-08-06 Procédés et dispositifs de communication

Country Status (1)

Country Link
WO (1) WO2023010580A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190281480A1 (en) * 2018-03-09 2019-09-12 FG Innovation Company Limited Beam failure detection and recovery
US20190349060A1 (en) * 2018-05-11 2019-11-14 Mediatek Inc. Methods of Efficient Bandwidth Part Switching in a Wideband Carrier
US20200059285A1 (en) * 2017-05-05 2020-02-20 Mediatek Singapore Pte. Ltd. Methods and apparatus supporting beam failure recovery in system with multiple-beam operation
CN111278122A (zh) * 2019-01-25 2020-06-12 维沃移动通信有限公司 波束失败恢复方法、处理方法、终端及网络侧设备
US20200266919A1 (en) * 2019-02-14 2020-08-20 Qualcomm Incorporated Dynamic switching between different multi-transmission/reception point schemes
US20200314881A1 (en) * 2019-03-27 2020-10-01 Lenovo (Singapore) Pte. Ltd. Method and Apparatus for Downlink Resource Allocation for Multi-Transmission and Reception Point Transmission

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200059285A1 (en) * 2017-05-05 2020-02-20 Mediatek Singapore Pte. Ltd. Methods and apparatus supporting beam failure recovery in system with multiple-beam operation
US20190281480A1 (en) * 2018-03-09 2019-09-12 FG Innovation Company Limited Beam failure detection and recovery
US20190349060A1 (en) * 2018-05-11 2019-11-14 Mediatek Inc. Methods of Efficient Bandwidth Part Switching in a Wideband Carrier
CN111278122A (zh) * 2019-01-25 2020-06-12 维沃移动通信有限公司 波束失败恢复方法、处理方法、终端及网络侧设备
US20200266919A1 (en) * 2019-02-14 2020-08-20 Qualcomm Incorporated Dynamic switching between different multi-transmission/reception point schemes
US20200314881A1 (en) * 2019-03-27 2020-10-01 Lenovo (Singapore) Pte. Ltd. Method and Apparatus for Downlink Resource Allocation for Multi-Transmission and Reception Point Transmission

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Reset of BFR timers and counters with RLM reconfiguration", 3GPP DRAFT; R2-1808416 RESET OF BFR TIMERS AND COUNTERS WITH RLM-CONFIG RECONFIGURATION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Busan, South Korea; 20180521 - 20180525, 11 May 2018 (2018-05-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051519812 *
VIVO: "Remaining issues on physical downlink control channel", 3GPP DRAFT; R1-1812288 REMAINING ISSUES ON PHYSICAL DOWNLINK CONTROL CHANNEL, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Spokane, USA; 20181112 - 20181116, 11 November 2018 (2018-11-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051554189 *

Similar Documents

Publication Publication Date Title
US20210409094A1 (en) Beam failure recovery
WO2021007862A1 (fr) Rapport de rétroaction harq dans une transmission de liaison latérale
US20230284221A1 (en) Method, device and computer storage medium for communication
WO2020029203A1 (fr) Procédé, dispositif et support lisible par ordinateur pour reprise sur défaillance de faisceau pour cellule secondaire
WO2022067677A1 (fr) Procédé, dispositif et support de stockage informatique pour la communication
US20240098782A1 (en) Methods and apparatus for handling listen before talk (lbt) failure for sidelink transmission
US20220321306A1 (en) Report of harq feedback in sidelink transmission
JP2023065547A (ja) 端末装置、ネットワークデバイス、及び方法
WO2021189320A1 (fr) Procédé, dispositif et support de stockage informatique de communication
US20240031067A1 (en) Method, device and computer storage medium for communication
US20220022232A1 (en) Multi-trp transmission
WO2023010580A1 (fr) Procédés et dispositifs de communication
US20240080774A1 (en) Method, device and computer storage medium of communication
US20230091084A1 (en) Methods, devices and computer readable media for communications
WO2021022422A1 (fr) Transmission d'ack/nack de couche supérieure
WO2020014833A1 (fr) Rétablissement après défaillance de faisceau
WO2023077315A1 (fr) Procédés et dispositifs de communication
WO2023044865A1 (fr) Procédé, dispositif et support lisible par ordinateur pour la communication
WO2023115277A1 (fr) Procédés et dispositifs de communication
WO2023283959A1 (fr) Procédé, dispositif et support lisible par ordinateur pour la communication
WO2023272723A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2023010395A1 (fr) Procédé, dispositif et support lisible par ordinateur pour la communication
WO2024007164A1 (fr) Procédés, dispositifs et supports de stockage informatiques pour une communication
US20240187199A1 (en) Method, device and computer storage medium for communication
WO2022205282A1 (fr) Procédés, dispositifs et supports de stockage informatiques pour la communication

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2024507110

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE