EP4280659A1 - Procédé et appareil de détection de défaillance de faisceau - Google Patents

Procédé et appareil de détection de défaillance de faisceau Download PDF

Info

Publication number
EP4280659A1
EP4280659A1 EP21918324.1A EP21918324A EP4280659A1 EP 4280659 A1 EP4280659 A1 EP 4280659A1 EP 21918324 A EP21918324 A EP 21918324A EP 4280659 A1 EP4280659 A1 EP 4280659A1
Authority
EP
European Patent Office
Prior art keywords
beam failure
transmission reception
reception point
failure recovery
trp
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
EP21918324.1A
Other languages
German (de)
English (en)
Other versions
EP4280659A4 (fr
Inventor
Meiyi JIA
Xin Wang
Yang Lu
Su YI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
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 Fujitsu Ltd filed Critical Fujitsu Ltd
Publication of EP4280659A1 publication Critical patent/EP4280659A1/fr
Publication of EP4280659A4 publication Critical patent/EP4280659A4/fr
Pending legal-status Critical Current

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
    • H04B7/06952—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping
    • H04B7/06964—Re-selection of one or more beams after beam failure
    • 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/022—Site diversity; Macro-diversity
    • H04B7/024—Co-operative use of antennas of several sites, e.g. in co-ordinated multipoint or co-operative multiple-input multiple-output [MIMO] systems
    • 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
    • H04B7/06952—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping
    • H04B7/06954—Sidelink beam training with support from third instance, e.g. the third instance being a base station
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • 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 application relate to the field of communication technology.
  • a terminal equipment may perform a beam failure detection (BFD) procedure and a beam failure recovery (BFR) procedure.
  • BFD beam failure detection
  • BFR beam failure recovery
  • a medium access control (MAC) entity may be configured by radio resource control (RRC) per serving cell with a beam failure recovery procedure.
  • RRC radio resource control
  • SSB serving synchronization signal block
  • CSI-RS channel state information reference signals
  • a new SSB or CSI-RS is indicated to a serving network device (e.g., gNB).
  • the terminal equipment When a MAC protocol data unit (PDU) is transmitted by the terminal equipment to the network device, and the MAC PDU includes a BFR MAC control element (CE) or a truncated BFR MAC CE which contains beam failure information of a secondary cell, the terminal equipment shall cancel all BFRs triggered for beam failure recovery in the secondary cell before the MAC PDU assembly.
  • PDU MAC protocol data unit
  • CE BFR MAC control element
  • truncated BFR MAC CE which contains beam failure information of a secondary cell
  • the MAC entity will execute the following operation: If the beam failure recovery procedure determines that at least one BFR has been triggered and not cancelled, an evaluation of its candidate beams has been completed according to the requirements:
  • the beam failure information of the secondary cell may be carried by the BFR MAC CE or the truncated BFR MAC CE and transmitted by the terminal equipment to the network device.
  • the inventor has found that in multiple transmission reception points (TRP) operation, if only part of the beams fails, the terminal equipment may not trigger beam failure detection; in addition, if the beam failure detection is not distinguished between a cell level or a TRP level, resources may be wasted.
  • TRP transmission reception points
  • embodiments of the present application provide a method and an apparatus for detecting beam failure.
  • an apparatus for detecting beam failure including:
  • a method for detecting beam failure including:
  • a communication system including: a terminal equipment, configured to receive a beam failure instance indication by a medium access control (MAC) entity, increment a transmission reception point (TRP)-specific beam failure indication count by 1, and in a case where the TRP-specific beam failure indication count is greater than or equal to a TRP-specific beam failure instance maximum count, determine that a beam failure occurs in a transmission reception point or beam failure recovery (BFR) of the transmission reception point is triggered or a beam failure indication of the transmission reception point is triggered.
  • MAC medium access control
  • TRP transmission reception point
  • BFR beam failure recovery
  • the MAC entity of the terminal equipment receives a beam failure instance indication, increments a transmission reception point (TRP)-specific beam failure indication count by 1, and in a case where the TRP-specific beam failure indication count is greater than or equal to a TRP-specific beam failure instance maximum count, determines that a beam failure occurs in a transmission reception point or beam failure recovery (BFR) of the transmission reception point is triggered or a beam failure indication of the transmission reception point is triggered.
  • TRP transmission reception point
  • BFR beam failure recovery
  • terms “first”, and “second”, etc. are used to differentiate different elements with respect to names, and do not indicate spatial arrangement or temporal orders of these elements, and these elements should not be limited by these terms.
  • Terms “and/or” include any one and all combinations of one or more relevantly listed terms.
  • Terms “contain”, “include” and “have” refer to existence of stated features, elements, components, or assemblies, but do not exclude existence or addition of one or more other features, elements, components, or assemblies.
  • single forms “a”, and “the”, etc. include plural forms, and should be understood as “a kind of” or “a type of” in a broad sense, but should not defined as a meaning of "one”; and the term “the” should be understood as including both a single form and a plural form, except specified otherwise.
  • the term “according to” should be understood as “at least partially according to”, the term “based on” should be understood as “at least partially based on”, except specified otherwise.
  • the term “communication network” or “wireless communication network” may refer to a network satisfying any one of the following communication standards: long term evolution (LTE), long term evolution-advanced (LTE-A), wideband code division multiple access (WCDMA), and high-speed packet access (HSPA), etc.
  • LTE long term evolution
  • LTE-A long term evolution-advanced
  • WCDMA wideband code division multiple access
  • HSPA high-speed packet access
  • communication between devices in a communication system may be performed according to communication protocols at any stage, which may, for example, include but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and 5G and new radio (NR) in the future, etc., and/or other communication protocols that are currently known or will be developed in the future.
  • 1G generation
  • 2G 2.5G, 2.75G
  • NR new radio
  • the term "network device”, for example, refers to an equipment in a communication system that accesses a terminal equipment to the communication network and provides services for the terminal equipment.
  • the network device may include but not limited to the following equipment: a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobile management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), etc.
  • the base station may include but not limited to a node B (NodeB or NB), an evolved node B (eNodeB or eNB), and a 5G base station (gNB), etc. Furthermore, it may include a remote radio head (RRH), a remote radio unit (RRU), a relay, or a low-power node (such as a femto, and a pico, etc.), IAB (Integrated Access and Backhaul) node or IAB-DU or IAB-donor.
  • the term "base station” may include some or all of its functions, and each base station may provide communication coverage for a specific geographical area.
  • a term "cell” may refer to a base station and/or its coverage area, which may be expressed as a serving cell, and may be a macro cell or a pico cell, depending on a context of the term.
  • the term "user equipment (UE)” or “terminal equipment (TE) or terminal device” refers to, for example, equipment accessing to a communication network and receiving network services via a network device.
  • the terminal equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), or a station, etc.
  • the terminal equipment may include but not limited to the following devices: a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a hand-held device, a machine-type communication device, a lap-top, a cordless telephone, a smart cell phone, a smart watch, and a digital camera, etc.
  • PDA personal digital assistant
  • wireless modem a wireless communication device
  • hand-held device a machine-type communication device
  • a machine-type communication device a lap-top
  • a cordless telephone a smart cell phone, a smart watch, and a digital camera, etc.
  • the user equipment may also be a machine or a device performing monitoring or measurement.
  • the user equipment may include but not limited to a machine-type communication (MTC) terminal, a vehicle mounted communication terminal, a device to device (D2D) terminal, and a machine to machine (M2M) terminal, etc.
  • MTC machine-type communication
  • D2D device to device
  • M2M machine to machine
  • network side or “network device side” refers to a side of a network, which may be a base station, and may include one or more network devices described above.
  • user side or “terminal side” or “terminal equipment side” refers to a side of a user or a terminal, which may be a UE, and may include one or more terminal equipments described above.
  • a “device” may refer to both a network device and a terminal device unless otherwise specified.
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a case where a terminal device and a network device are taken as examples.
  • the communication system 100 may include a network device 101 and a terminal device 102.
  • FIG. 1 gives illustration by taking only one terminal device and one network device as examples, but the embodiment of the present application is not limited thereto, and there may be a plurality of terminal devices, for example.
  • eMBB enhanced Mobile Broadband
  • mMTC massive Machine Type Communication
  • URLLC Ultra-Reliable and Low-Latency Communication
  • the MAC entity of the medium access control (MAC) layer of the terminal equipment detects a beam failure by counting beam failure instance indication from lower layers (e.g. a physical layer) to the MAC entity.
  • lower layers e.g. a physical layer
  • the beam failure detection procedure uses the UE variable BFI _ COUNTER, which is a counter for the beam failure instance indication, initially set to 0, with one BFI _ COUNTER per serving cell.
  • BFI _ COUNTER is a counter for the beam failure instance indication, initially set to 0, with one BFI _ COUNTER per serving cell.
  • the MAC entity will execute the following operation: If beam failure instance indication has been received from the lower layers, a beam FailureDetectionTimer is started or restarted; and the terminal equipment variable BFI _ COUNTER is incremented by 1; in a case that BFI _ COUNTER is greater than or equal to a beamFailureInstanceMaxCount : if the serving cell is a secondary cell (SCell), one beam failure recovery (BFR) of the serving cell is triggered, otherwise, a random access procedure is initiated on the special cell (SpCell).
  • SCell secondary cell
  • BFR beam failure recovery
  • the BFI _ COUNTER is set to 0 if the beamFailureDetectionTimer expires, or if beamFailureDetectionTimer, beamFailurelnstance MaxCount, or any of reference signals for beam failure detection is reconfigured by upper layers associated with this serving cell.
  • beam failure information of a secondary cell may be carried by a BFR MAC CE or a truncated BFR MAC CE, and transmitted by the terminal equipment to the network device.
  • FIG. 2 is a schematic diagram of a BFR MAC CE or a truncated BFR MAC CE in a first format (called Format 1).
  • FIG. 3 is a schematic diagram of a BFR MAC CE or a truncated BFR MAC CE in a second format (called Format 2).
  • the field definitions for Format 1 and Format 2 are as follows:
  • the Ci field indicates beam failure detection of the secondary cell with ServCellIndex i, whether evaluation of the candidate beam is completed and presence of an octet containing an AC field
  • the AC field indicates the presence of a Candidate RS ID field in this octet
  • the Candidate RS ID field is set to the index of SSB or CSI-RS.
  • the Ci field set to 1 indicates that beam failure is detected, the evaluation of the candidate beams according to requirements has been completed, and the octet containing the AC field is present for the secondary cell with ServCellIndex i.
  • the Ci field set to 0 indicates that the beam failure is not detected, or the beam failure is detected but the evaluation of the candidate beams according to requirements has not been completed, and the octet containing the AC field is not present for the secondary cell with ServCellIndex i.
  • the octets containing the AC field are present in an ascending order based on ServCellIndex.
  • the Ci field indicates beam failure detection of the secondary cell with ServCellIndex i, whether evaluation of the candidate beam is completed and presence of an octet containing an AC field, the AC field indicates the presence of a Candidate RS ID field in this octet, and the Candidate RS ID field is set to the index of SSB or CSI-RS.
  • the Ci field set to 1 indicates that beam failure is detected, the evaluation of the candidate beams according to requirements has been completed, and the oct containing the AC field is present for the secondary cell with ServCellIndex i.
  • the Ci field set to 0 indicates that beam failure is not detected, or beam failure is detected but the evaluation of the candidate beams according to requirements has not been completed, and the octet containing the AC field is not present for the secondary cell with ServCellIndex i. If present, the octets containing the AC field are included in ascending order based on ServCellIndex. The number of the octets containing the AC field may be 0, while not exceeding the size of the available grant.
  • the beam may be replaced by a reference signal (RS), and may be represented by SSB or CSI-RS, for example.
  • RS reference signal
  • FIG. 4 is a schematic diagram of a multi-TRP scenario according to an embodiment of the present application.
  • the TRP may be part of a network device (e.g., gNB) that receives signals from the terminal equipment, or part of a network device (gNB) that transmits signals to the terminal equipment.
  • the TRP may also represent a set of downlink control information (DCI) or a set of reference signals, etc.
  • DCI downlink control information
  • the terminal equipment may have a panel 1 (panel-1) and a panel 2 (panel-2); one serving cell may schedule the terminal equipment from 2 TRPs, provide better physical downlink shared channel (PDSCH) coverage, reliability, and/or data rate.
  • PDSCH physical downlink shared channel
  • the multi-TRP operation there may be two different modes of operation: single DCI and multiple DCI.
  • control of the uplink and downlink operations is performed by the physical layer and medium access control (MAC).
  • MAC medium access control
  • the terminal equipment is scheduled by two TRPs through the same DCI; and in the multi-DCI mode, the terminal equipment is scheduled by a separate DCI of each TRP.
  • the physical layer does not indicate a beam failure instance to the MAC layer and does not trigger the beam failure detection procedure of the MAC layer.
  • the beam failure detection is not distinguished between the cell level and the TRP level, resources may be wasted.
  • the physical layer indicates a beam failure instance to the MAC layer; the terminal equipment and the network device believe that a cell-level beam failure has occurred, a cell handover procedure may be performed, another TRP on the cell where failure has not occurred is not fully utilized and thus resource utilization is low.
  • the terminal equipment may not trigger the BFR but may trigger random access (RA). In this case, the random access is unnecessary, resulting in waste of random access resources and longer service interruption.
  • RA random access
  • the embodiments of the present application are further described below.
  • the embodiments of the present application are described from the MAC layer of the terminal equipment and implemented by the MAC entity, wherein the MAC entity includes a beam failure detection procedure, a beam failure recovery procedure, and a multiplexing and assembly entity (hereinafter also referred to as a multiplexing and assembly procedure), etc.
  • the lower layers of the embodiments of the present application are, for example, physical layers, antenna units, measurement procedures, etc.
  • cell-specific may be understood as cell-level or all beam, with cell as granularity
  • TRP-specific may be understood as TRP-level or part of the beams, with TRP as granularity.
  • the cell-specific MAC CE may be a BFR MAC CE of Rel-15/Rel-16 or a truncated BFR MAC CE of Rel-15/Rel-16, etc.
  • detected beam failure may be interchanged with "triggered beam failure recovery” or "triggered beam failure indication”.
  • An embodiment of the present application provides a method for detecting beam failure, which is described from a terminal equipment.
  • FIG. 5 is a schematic diagram of a method for detecting beam failure according to an embodiment of the present application, as shown in FIG. 5 , the method including:
  • FIG. 5 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order between the operations may be appropriately adjusted, and some other operations may be added or some of the operations may be reduced.
  • appropriate variants may be made by those skilled in the art according to the above contents, which are not limited to the description of FIG. 5 described above.
  • FIG. 6 is a schematic diagram of beam failure detection (BFD) or beam failure recovery (BFR) according to an embodiment of the present application.
  • the network device provides service for the terminal equipment by using TRP-1 and TRP-2.
  • the link 1 (link-1) between the TRP-1 and the terminal equipment operates normally, but the link 2 (link-2) between the TRP-2 and the terminal equipment is blocked.
  • the terminal equipment may configure the BFD of the TRP level or trigger the BFR of the TRP level independently of the BFD procedure of the cell level.
  • the terminal equipment may configure the BFD of the TRP level or trigger the BFR of the TRP level independently of the BFD procedure of the cell level.
  • FIG. 7 is another schematic diagram of a method for detecting beam failure according to an embodiment of the present application, schematically illustrating an operation of an MAC entity of a terminal equipment for a TRP configured with beam failure detection. As shown in FIG. 7 , the operation of the MAC entity includes:
  • the operation of the MAC entity further includes:
  • the TRP-specific beam failure indication count (e.g., BFI_COUNTER-perTRP ) is also reset or set to 0 in one or any combination of the following cases:
  • FIG. 7 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order between the operations may be appropriately adjusted, and some other operations may be added or some of the operations may be reduced.
  • appropriate variants may be made by those skilled in the art according to the above contents, which are not limited to the description of FIG. 7 described above.
  • the MAC entity of the terminal equipment instructs the multiplexing and assembly entity to generate a TRP-specific beam failure recovery MAC CE or a TRP-specific beam failure MAC CE.
  • the content of generating the MAC CE reference may also be made to an embodiment of the third aspect described later.
  • the MAC entity of the terminal equipment determines whether the evaluation of the candidate beam is completed when the candidate beam is configured.
  • the MAC entity of the terminal equipment instructs the multiplexing and assemble entity to generate the TRP-specific beam failure recovery MAC CE or the TRP-specific beam failure MAC CE.
  • the MAC entity of the terminal equipment does not determine whether the evaluation of the candidate beam is completed.
  • the TRP is configured with beam failure recovery or with beam failure recovery parameters, and/or is configured with beam failure detection or with beam failure detection parameters; for each TRP configured with beam failure recovery or with beam failure recovery parameters, and/or configured with beam failure detection or with beam failure detection parameters, the MAC entity will determine whether to instruct generation of an MAC CE or trigger a scheduling request (SR).
  • SR scheduling request
  • the MAC entity executes the following operations:
  • the TRP is configured with beam failure recovery or with beam failure recovery parameters, and/or is configured with beam failure detection or with beam failure detection parameters; for each TRP configured with beam failure recovery or with beam failure recovery parameters, and/or configured with beam failure detection or with beam failure detection parameters, the MAC entity will perform beam failure detection to trigger the BFR.
  • the MAC entity receives a beam failure instance indication, starts or restarts a transmission reception point (TRP)-specific beam failure detection timer, increments a transmission reception point (TRP)-specific beam failure indication count by 1, and in a case where the TRP-specific beam failure indication count is greater than or equal to a TRP-specific beam failure instance maximum count, determines that a beam failure occurs in a transmission reception point or beam failure recovery (BFR) of the transmission reception point is triggered or a beam failure indication of the transmission reception point is triggered.
  • TRP transmission reception point
  • BFR beam failure recovery
  • the MAC entity of the terminal equipment determines that the evaluation of the candidate beam has been completed if the candidate beam is not configured in the case where at least one beam failure recovery is triggered.
  • the physical layer of the terminal equipment upon receiving the higher layer request, determines that the evaluation of the candidate beam has been completed in a case where the candidate beam is not configured.
  • a candidate reference signal is configured in a case where a reference signal for beam failure detection is configured. For example, if a reference signal for beam failure detection is configured, a candidate reference signal should be configured.
  • the TRP-specific beam failure recovery MAC CE or the TRP-specific beam failure MAC CE is schematically described above, and the Fallback mechanism of the embodiment of the present application is described below.
  • some or all of the serving cells in the MAC entity of the terminal equipment are configured with TRP-specific beam failure detection, and/or, a special cell in the MAC entity of the terminal equipment is configured with the TRP-specific beam failure detection.
  • the Fallback mechanism is supported if beam failure detection at the TRP level is configured while beam failure detection at the cell level is not configured.
  • the "beam failure detection at the cell level is not configured" includes that all the serving cells configured in the MAC entity are not configured with Rel-15/16 beam failure detection, or the special cell in this MAC entity is not configured with Rel-15/16 beam failure detection.
  • all the serving cells configured in the MAC entity are not configured with beam failure detection, or are not configured with RadioLinkMonitoringConfig, or parameters of beam failure detection are not configured/not included in RadioLink MonitoringConfig.
  • the special cell in the MAC entity is not configured with beam failure detection, or is not configured with RadioLink MonitoringConfig, or parameters of beam failure detection are not configured/not included in RadioLinkMonitoringConfig.
  • the Fallback mechanism is supported if beam failure recovery at the TRP level is configured while beam failure recovery at the cell level is not configured.
  • the "beam failure recovery at the cell level is not configured" includes that all the serving cells configured in the MAC entity are not configured with Rel-15/16 beam failure recovery, or the special cell in this MAC entity is not configured with Rel-15/16 beam failure recovery.
  • all the serving cells configured in the MAC entity are not configured with beam failure recovery, or are not configured with BeamFailureRecoverySCell Config, or parameters (e.g., candidateBeamRSSCellList ) of the secondary cell beam failure recovery procedure is not configured/not included in BeamFailureRecoverySCellConfig.
  • the special cell in the MAC entity is not configured with beam failure recovery, or is not configured with BeamFailureRecoveryConfig, or parameters (e.g., candidateBeamRS List ) of the secondary cell beam failure recovery procedure is not configured/not included in BeamFailureRecoveryConfig.
  • the MAC entity of the terminal equipment determines whether the transmission reception point belongs to a secondary cell, and in a case where the transmission reception point belongs to a secondary cell, determines that a beam failure occurs in the transmission reception point or beam failure recovery of the transmission reception point is triggered or a beam failure indication of the transmission reception point is triggered.
  • the MAC entity of the terminal equipment determines whether all TRPs configured with TRP-specific beam failure detection are triggered for beam failure recovery; in the case where all TRPs configured with TRP-specific beam failure detection are triggered for beam failure recovery, the MAC entity of the terminal equipment initiates a random access procedure in the special cell.
  • FIG. 8A is another schematic diagram of a method for detecting beam failure according to an embodiment of the present application, schematically illustrating an operation of an MAC entity of a terminal equipment for a TRP configured with beam failure detection. As shown in FIG. 8A , the operation of the MAC entity includes:
  • the operation of the MAC entity further includes:
  • the operation of the MAC entity further includes:
  • FIG. 8A only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order between the operations may be appropriately adjusted, and some other operations may be added or some of the operations may be reduced.
  • Those skilled in the art may make appropriate modifications according to the above content, which are not limited to the description of FIG. 8A described above.
  • the UE variable e.g., BFI_COUNTER-perTRP
  • the UE variable e.g., BFI_COUNTER-perTRP
  • the beam failure instance maximum count value If the TRP belong to a secondary cell, or if the TRP belongs to a special cell and another TRP of this cell has not triggered a BFR, a BFR is triggered for this TRP.
  • all of the serving cells in the MAC entity of the terminal equipment do not configured with cell-specific beam failure detection, or, a special cell in the MAC entity of the terminal equipment does not configured with the cell-specific beam failure detection.
  • the MAC entity of the terminal equipment initiates a random access procedure on the special cell.
  • the Fallback mechanism includes initiating a random access procedure on a special cell when the TRP-specific beam failure is detected or the TRP-specific beam failure recovery is triggered at multiple TRPs.
  • the multiple TRPs include all TRPs configured with TRP-specific beam detection of all serving cells configured in a MAC entity, or all TRPs configured with TRP-specific beam detection of a special cell in a MAC entity.
  • the multiple TRPs include all TRPs configured with TRP-specific beam failure detection of all serving cells in a MAC entity, or all TRPs configured with TRP-specific beam failure detection of a special cell in a MAC entity.
  • FIG. 8B is another schematic diagram of a method for detecting beam failure according to an embodiment of the present application, schematically illustrating an operation of an MAC entity of a terminal equipment for a TRP configured with beam failure detection. As shown in FIG. 8B , the operation of the MAC entity includes:
  • BFR beam failure recovery
  • the operation of the MAC entity further includes:
  • the operation of the MAC entity further includes: 809B, initiating a random access procedure on the special cell (SpCell).
  • FIG. 8B only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order between the operations may be appropriately adjusted, and some other operations may be added or some of the operations may be reduced.
  • appropriate variants may be made by those skilled in the art according to the above contents, which are not limited to the description of FIG. 8B described above.
  • the terminal equipment may trigger the BFR; and random access (RA) is triggered only if beam failure is detected on all TRPs (configured with the TRP-specific beam failure detection) of the special cell. Unnecessary random access can be avoided, thereby avoiding waste of random access resources and longer service interruption.
  • a cell-specific BFD on a specific cell should be configured, or a cell-specific BFD on a belonging cell should be configured or a cell-specific BFD on at least one cell should be configured, this may eliminate the need for the fallback mechanism described above.
  • the terminal equipment may perform one or any combination of the following:
  • the terminal equipment triggers a scheduling request (SR) for the TRP-specific beam failure recovery or the TRP-specific beam failure, for a TRP that has triggered a BFR and has not been cancelled.
  • SR scheduling request
  • the scheduling request configures a SR ID or a set of SR IDs.
  • SchedulingRequestId (0...7); the present application is not limited to this.
  • the configuration value of the TRP-specific beam failure recovery SR ID (e.g., SchedulingRequestId ) is the same as the configuration value of the cell-specific beam failure recovery SR ID, or the configuration value of the TRP-specific beam failure recovery SR ID is different from configuration value of the cell-specific beam failure recovery SR ID.
  • the configuration of the SR may be included in IE MAC-CellGroupConfig or in IE CellGroupConfig.
  • an SR ID is configured and included in IEMAC-CellGroupConfig.
  • Tables 1 and 2 below: Table 2 MAC-CellGroupConfig field descriptions usePreBSR If set to true, the MAC entity of the IAB-MT may use the Pre-emptive BSR, see TS 38.321 [3]. csi-Mask If set to true, the UE limits CSI reports to the on-duration period of the DRX cycle, see TS 38.321 [3].
  • dataInactivityTimer Releases the RRC connection upon data inactivity as specified in clause 5.3.8.5 and in TS 38.321 [3]. Value s1 corresponds to 1 second, value s2 corresponds to 2 seconds, and so on.
  • drx-Config Used to configure DRX as specified in TS 38.321 [3].
  • drx-ConfigSecondaryGroup Used to configure DRX related parameters for the second DRX group as specified in TS 38.321 [3].
  • the network does not configure secondary DRX group with DCP simultaneously nor secondary DRX group with a dormant BWP simultaneously. Ich-BasedPrioritization If this field is present, the corresponding MAC entity of the UE is configured with prioritization between overlapping grants and between scheduling request and overlapping grants based on LCH priority, see TS 38.321 [3].
  • schedulingRequestID-BFR-SCell Indicates the scheduling request configuration applicable for BFR on SCell, as specified in TS 38.321 [3].
  • schedulingRequestID-LBT-SCell Indicates the scheduling request configuration applicable for consistent uplink LBT recovery on SCell, as specified in TS 38.321 [3].
  • schedulingRequestID-BFR-TRP Indicates the scheduling request configuration applicable for TRP specific BFR, as specified in TS 38.321 [3] . skipUplinkTxDynamic If set to true, the UE skips UL transmissions as described in TS 38.321 [3].
  • tag-Config The field is used to configure parameters for a time-alignment group. The field is not present if any DAPS bearer is configured.
  • a set of SR IDs are configured and included in IE MAC-CellGroup Config.
  • Table 4 MAC-CellGroupConfig field descriptions usePreBSR If set to true, the MAC entity of the IAB-MT may use the Pre-emptive BSR, see TS 38.321 [3].
  • csi-Mask If set to true, the UE limits CSI reports to the on-duration period of the DRX cycle, see TS 38.321 [3].
  • datalnactivity Timer Releases the RRC connection upon data inactivity as specified in clause 5.3.8.5 and in TS 38.321 [3]. Value s1 corresponds to 1 second, value s2 corresponds to 2 seconds, and so on.
  • drx-Config Used to configure DRX as specified in TS 38.321 [3].
  • drx-ConfigSecondaryGroup Used to configure DRX related parameters for the second DRX group as specified in TS 38.321 [3].
  • the network does not configure secondary DRX group with DCP simultaneously nor secondary DRX group with a dormant BWP simultaneously. Ich-BasedPrioritization If this field is present, the corresponding MAC entity of the UE is configured with prioritization between overlapping grants and between scheduling request and overlapping grants based on LCH priority, see TS 38.321 [3].
  • schedulingRequestID-BFR-SCell Indicates the scheduling request configuration applicable for BFR on SCell, as specified in TS 38.321 [3].
  • schedulingRequestID-LBT-SCell Indicates the scheduling request configuration applicable for consistent uplink LBT recovery on SCell, as specified in TS 38.321 [3].
  • schedulingRequestIDList-BFR-TRP List of the scheduling request configuration applicable for TRP specific BFR, as specified in TS 38.321 [3].
  • skipUplinkTxDynamic If set to true, the UE skips UL transmissions as described in TS 38.321 [3].
  • tag-Config The field is used to configure parameters for a time-alignment group. The field is not present if any DAPS bearer is configured .
  • an SR ID is configured and included in IE CellGroupConfig. As shown in Tables 5 and 6: Table 6 CellGroupConfig field descriptions bap-Address BAP address of the parent node in cell group. bh- RLC-Channel IoAddModList Configuration of the backhaul RLC entities and the corresponding MAC Logical Channels to be added and modified. bh-RLC-ChannelToReleaseList List of the backhaul RLC entities and the corresponding MAC Logical Channels to be released. f1 c-TransferPath The F1-C transfer path that an EN-DC IAB-MT should use for transferring F1-C packets to the IAB-donor-CU.
  • IAB-MT can only use LTE leg for F1-C transfer. If IAB-MT is configured with nr, IAB-MT can only use NR leg for F1-C transfer. If IAB-MT is configured with both, it is up to IAB-MT to select an LTE leg or a NR leg for F1-C transfer. If the field is not configured, the IAB node uses the NR leg as the default one. mac-CellGroupConfig MAC parameters applicable for the entire cell group. rlc-BearerToAddModList Configuration of the MAC Logical Channel, the corresponding RLC entities and association with radio bearers.
  • reportUplinkTxDirectCurrent Enables reporting of uplink and supplementary uplink Direct Current location information upon BWP configuration and reconfiguration. This field is only present when the BWP configuration is modified or any serving cell is added or removed. This field is absent in the IE CellGroupConfig when provided as part of RRCSetup message. If UE is configured with SUL carrier, UE reports both UL and SUL Direct Current locations. rlmInSyncOutOfSyncThreshold BLER threshold pair index for IS/OOS indication generation, see TS 38.133 [14], table 8.1.1-1 . n1 corresponds to the value 1. When the field is absent, the UE applies the value 0. Whenever this is reconfigured, UE resets N310 and N311, and stops 1310, if running.
  • sCellState Indicates whether the SCell shall be considered to be in activated state upon SCell configuration.
  • sCellToAddModList List of secondary serving cells (SCells) to be added or modified.
  • sCellToReleaseList List of secondary serving cells (SCells) to be released.
  • schedulingRequestID-BFR-TRP Indicates the scheduling request configuration applicable for TRP specific BFR, as specified in TS 38.321 [3].
  • secondaryDRX-GroupConfig The field is used to indicate whether the SCell belongs to the secondary DRX group. All serving cells in the secondary DRX group shall belong to one Frequency Range and all serving cells in the legacy DRX group shall belong to another Frequency Range.
  • the simultaneousTCI-UpdateList1 and simultaneousTCI-UpdateList2 shall not contain same serving cells.
  • Network should not configure serving cells that are configured with a BWP with two different values for the coresetPoolIndex in these lists.
  • the simultaneousSpatial-UpdatedList1 and simultaneousSpatial-UpdatedList2 shall not contain same serving cells.
  • Network should not configure serving cells that are configured with a BWP with two different values for the coresetPoolIndex in these lists.
  • uplinkTxSwitchingOption Indicates which option is configured for dynamic UL Tx switching for inter-band UL CA or (NG)EN-DC.
  • the field is set to switchedUL if network configures option 1 as specified in TS 38.214 [19], or dualUL if network configures option 2 as specified in TS 38.214 [19].
  • Network always configures UE with a value for this field in inter-band UL CA case and (NG)EN-DC case where UE supports dynamic UL Tx switching.
  • uplinkTxSwitchingPowerBoosting Indicates whether the UE is allowed to enable 3dB boosting on the maximum output power for transmission on carrier2 under the operation state in which 2-port transmission can be supported on carrier2 for inter-band UL CA case with dynamic UL Tx switching as defined in TS 38.101-1 [15].
  • Network can only configure this field for dynamic UL Tx switching in inter-band UL CA case with power Class 3 as defined in TS 38.101-1 [15].
  • a set of SR IDs are configured and included in IE CellGroupConfig. As shown in Tables 7 and 8: Table 8 CellGroupConfig field descriptions bap-Address BAP address of the parent node in cell group. bh-RLC-ChannelIoAddModList Configuration of the backhaul RLC entities and the corresponding MAC Logical Channels to be added and modified. bh-RLC-ChannelToReleaseList List of the backhaul RLC entities and the corresponding MAC Logical Channels to be released. f1 c-TransferPath The F1-C transfer path that an EN-DC IAB-MT should use for transferring F1-C packets to the IAB-donor-CU.
  • IAB-MT can only use LTE leg for F1-C transfer. If IAB-MT is configured with nr, IAB-MT can only use NR leg for F1-C transfer. If IAB-MT is configured with both, it is up to IAB-MT to select an LTE leg or a NR leg for F1-C transfer. If the field is not configured, the IAB node uses the NR leg as the default one. mac-CellGroupConfig MAC parameters applicable for the entire cell group. rlc-BearerToAddModList Configuration of the MAC Logical Channel, the corresponding RLC entities and association with radio bearers.
  • reportUplinkTxDirectCurrent Enables reporting of uplink and supplementary uplink Direct Current location information upon BWP configuration and reconfiguration. This field is only present when the BWP configuration is modified or any serving cell is added or removed. This field is absent in the IE CellGroupConfig when provided as part of RRCSetup message. If UE is configured with SUL carrier, UE reports both UL and SUL Direct Current locations. rlmInSyncOutOfSyncThreshold BLER threshold pair index for IS/OOS indication generation, see TS 38.133 [14], table 8.1.1-1 . n1 corresponds to the value 1. When the field is absent, the UE applies the value 0. Whenever this is reconfigured, UE resets N310 and N311, and stops 1310, if running.
  • sCellState Indicates whether the SCell shall be considered to be in activated state upon SCell configuration.
  • sCellToAddModList List of secondary serving cells (SCells) to be added or modified.
  • sCellToReleaseList List of secondary serving cells (SCells) to be released.
  • schedulingRequestIDList-BFR-TRP List of the scheduling request configuration applicable for TRP specific BFR, as specified in TS 38.321 [3].
  • secondaryDRX-GroupConfig The field is used to indicate whether the SCell belongs to the secondary DRX group. All serving cells in the secondary DRX group shall belong to one Frequency Range and all serving cells in the legacy DRX group shall belong to another Frequency Range.
  • the simultaneousTCI-UpdateList1 and simultaneousTCI-UpdateList2 shall not contain same serving cells.
  • Network should not configure serving cells that are configured with a BWP with two different values for the coresetPoolIndex in these lists.
  • the simultaneousSpatial-UpdatedList1 and simultaneousSpatial-UpdatedList2 shall not contain same serving cells.
  • Network should not configure serving cells that are configured with a BWP with two different values for the coresetPoolIndex in these lists.
  • uplinkTxSwitchingOption Indicates which option is configured for dynamic UL Tx switching for inter-band UL CA or (NG)EN-DC.
  • the field is set to switchedUL if network configures option 1 as specified in TS 38.214 [19], or dualUL if network configures option 2 as specified in TS 38.214 [19].
  • Network always configures UE with a value for this field in inter-band UL CA case and (NG)EN-DC case where UE supports dynamic UL Tx switching.
  • uplinkTxSwitchingPowerBoosting Indicates whether the UE is allowed to enable 3dB boosting on the maximum output power for transmission on carrier2 under the operation state in which 2-port transmission can be supported on carrier2 for inter-band UL CA case with dynamic UL Tx switching as defined in TS 38.101-1 [15].
  • Network can only configure this field for dynamic UL Tx switching in inter-band UL CA case with power Class 3 as defined in TS 38.101-1 [15].
  • the configuration values of the TRP-specific beam failure recovery SR ID and the control resource pool index are the same as the configuration value of the cell-specific beam failure recovery SR ID, or the configuration values of the TRP-specific beam failure recovery SR ID and the control resource pool index are different from the configuration value of the cell-specific beam failure recovery SR ID.
  • an SR ID is configured and included in IEMAC-CellGroupConfig.
  • Table 10 MAC-CellGroupConfig field descriptions usePreBSR If set to true, the MAC entity of the IAB-MT may use the Pre-emptive BSR, see TS 38.321 [3].
  • csi-Mask If set to true, the UE limits CSI reports to the on-duration period of the DRX cycle, see TS 38.321 [3].
  • datalnactivity Timer Releases the RRC connection upon data inactivity as specified in clause 5.3.8.5 and in TS 38.321 [3]. Value s1 corresponds to 1 second, value s2 corresponds to 2 seconds, and so on.
  • drx-Config Used to configure DRX as specified in TS 38.321 [3].
  • drx-ConfigSecondaryGroup Used to configure DRX related parameters for the second DRX group as specified in TS 38.321 [3].
  • the network does not configure secondary DRX group with DCP simultaneously nor secondary DRX group with a dormant BWP simultaneously. Ich-BasedPrioritization If this field is present, the corresponding MAC entity of the UE is configured with prioritization between overlapping grants and between scheduling request and overlapping grants based on LCH priority, see TS 38.321 [3].
  • schedulingRequestID-BFR-SCell Indicates the scheduling request configuration applicable for BFR on SCell, as specified in TS 38.321 [3].
  • schedulingRequestID-LBT-SCell Indicates the scheduling request configuration applicable for consistent uplink LBT recovery on SCell, as specified in TS 38.321 [3].
  • schedulingRequestID-BFR-TRP Indicates the scheduling request configuration applicable for TRP specific BFR, as specified in TS 38.321 [3] . skipUplinkTxDynamic If set to true, the UE skips UL transmissions as described in TS 38.321 [3].
  • tag-Config The field is used to configure parameters for a time-alignment group. The field is not present if any DAPS bearer is configured.
  • Table 11 schedulingRequestID-BFR-TRP field descriptions coresetPoolIndex-r17 The index of the CORESET pool for which this scheduling request configuration is applicable. If the field is absent, the UE applies the value 0
  • an SR ID is configured and included in IE CellGroupConfig. As shown in Tables 12 to 14: Table 13 CellGroupConfig field descriptions bap-Address BAP address of the parent node in cell group. bh- RLC-Channel IoAddModList Configuration of the backhaul RLC entities and the corresponding MAC Logical Channels to be added and modified. bh-RLC-ChannelToReleaseList List of the backhaul RLC entities and the corresponding MAC Logical Channels to be released. flc-TransferPath The F1-C transfer path that an EN-DC IAB-MT should use for transferring F1-C packets to the IAB-donor-CU.
  • IAB-MT can only use LTE leg for F1-C transfer. If IAB-MT is configured with nr, IAB-MT can only use NR leg for F1-C transfer. If IAB-MT is configured with both, it is up to IAB-MT to select an LTE leg or a NR leg for F1-C transfer. If the field is not configured, the IAB node uses the NR leg as the default one. mac-CellGroupConfig MAC parameters applicable for the entire cell group. rlc-BearerToAddModList Configuration of the MAC Logical Channel, the corresponding RLC entities and association with radio bearers.
  • reportUplinkTxDirectCurrent Enables reporting of uplink and supplementary uplink Direct Current location information upon BWP configuration and reconfiguration. This field is only present when the BWP configuration is modified or any serving cell is added or removed. This field is absent in the IE CellGroupConfig when provided as part of RRCSetup message. If UE is configured with SUL carrier, UE reports both UL and SUL Direct Current locations. rlmInSyncOutOfSyncThreshold BLER threshold pair index for IS/OOS indication generation, see TS 38.133 [14], table 8.1.1-1. n1 corresponds to the value 1. When the field is absent, the UE applies the value 0. Whenever this is reconfigured, UE resets N310 and N311, and stops 1310, if running.
  • sCellState Indicates whether the SCell shall be considered to be in activated state upon SCell configuration.
  • sCellToAddModList List of secondary serving cells (SCells) to be added or modified.
  • sCellToReleaseList List of secondary serving cells (SCells) to be released.
  • schedulingRequestID-BFR-TRP Indicates the scheduling request configuration applicable for TRP specific BFR, as specified in TS 38.321 [3] .
  • secondaryDRX-GroupConfig The field is used to indicate whether the SCell belongs to the secondary DRX group. All serving cells in the secondary DRX group shall belong to one Frequency Range and all serving cells in the legacy DRX group shall belong to another Frequency Range.
  • the simultaneousTCI-UpdateList1 and simultaneousTCI-UpdateList2 shall not contain same serving cells.
  • Network should not configure serving cells that are configured with a BWP with two different values for the coresetPoolIndex in these lists.
  • the simultaneousSpatial-UpdatedList1 and simultaneousSpatial-UpdatedList2 shall not contain same serving cells.
  • Network should not configure serving cells that are configured with a BWP with two different values for the coresetPoolIndex in these lists.
  • uplinkTxSwitchingOption Indicates which option is configured for dynamic UL Tx switching for inter-band UL CA or (NG)EN-DC.
  • the field is set to switchedUL if network configures option 1 as specified in TS 38.214 [19], or dualUL if network configures option 2 as specified in TS 38.214 [19].
  • Network always configures UE with a value for this field in inter-band UL CA case and (NG)EN-DC case where UE supports dynamic UL Tx switching.
  • uplinkTxSwitchingPowerBoosting Indicates whether the UE is allowed to enable 3dB boosting on the maximum output power for transmission on carrier2 under the operation state in which 2-port transmission can be supported on carrier2 for inter-band UL CA case with dynamic UL Tx switching as defined in TS 38.101-1 [15].
  • Network can only configure this field for dynamic UL Tx switching in inter-band UL CA case with power Class 3 as defined in TS 38.101-1 [15].
  • Table 14 schedulingRequestID-BFR-TRP field descriptions coresetPoolIndex-r17 The index of the CORESET pool for which this scheduling request configuration is applicable. If the field is absent, the UE applies the value 0
  • the MAC entity when an MAC entity of a terminal equipment has a pending SR for a TRP-specific BFR, and for an SR transmission occasion, the MAC entity has one or more PUCCH resources overlapping with PUCCH resources of the TRP-specific BFR, the MAC entity determines (deems) that the PUCCH resources of the TRP-specific BFR are valid.
  • the MAC entity when an MAC entity of a terminal equipment has a pending SR for a secondary cell/TRP-specific BFR, and for an SR transmission occasion, the MAC entity has one or more PUCCH resources overlapping with PUCCH resources of the secondary cell/TRP-specific BFR, the MAC entity determines (deems) that the PUCCH resources of the secondary cell/TRP-specific BFR are valid.
  • the MAC entity only deems that PUCCH resources of the secondary cell/TRP-specific BFR is valid.
  • the MAC entity has a pending SR for the secondary cell BFR and a pending SR for the TRP-specific BFR, and for the SR transmission occasion, the MAC entity has one or more PUCCH resources overlapping with PUCCH resources of the secondary cell BFR and/or PUCCH resources of the TRP-specific BFR, which PUCCH resource is valid depends on the implementation of the terminal equipment.
  • the beam failure recovery MAC CE or the truncated beam failure recovery MAC CE includes beam failure information of a cell
  • the MAC entity of the terminal equipment cancels the pending SR triggered for the BFR of the TRP included in the cell and stops the respective prohibiting timer; e.g., sr-ProhibitTimer.
  • the MAC entity of the terminal equipment cancels the pending SR triggered for the BFR of the TRP and stops the respective prohibiting timer; e.g., sr-ProhibitTimer.
  • the MAC entity of the terminal equipment cancels the pending SR triggered for the BFR of the TRP included in the secondary cell.
  • the MAC entity of the terminal equipment cancels the triggered pending SR.
  • the MAC entity of the terminal equipment cancels the pending SR.
  • an MAC PDU performs transmission using an uplink grant except an uplink grant provided by random access response (RAR) or an uplink grant determined from the transmission of the message A payload (MSGA payload)
  • the MAC PDU includes an MAC CE including beam failure information of a TRP
  • the MAC entity of the terminal equipment stops the ongoing random access procedure due to the pending SR by the BFR of the TRP.
  • the MAC entity of the terminal equipment receives a beam failure instance indication, increments a transmission reception point (TRP)-specific beam failure indication count by 1, and in a case where the TRP-specific beam failure indication count is greater than or equal to a TRP-specific beam failure instance maximum count, determines that a beam failure occurs in a transmission reception point or beam failure recovery (BFR) of the transmission reception point is triggered or a beam failure indication of the transmission reception point is triggered.
  • BFR beam failure recovery
  • An embodiment of the present application provides a method for detecting beam failure, which is described from a terminal equipment.
  • the embodiments of the second aspect combine the TRP-specific beam failure detection and the cell-specific beam failure detection, and the same content as those of the embodiments of the first aspect is not repeated.
  • the MAC entity of the terminal equipment determines whether the beam failure instance indication is cell specific or cell level; and in the case where the beam failure instance indication is not cell specific or cell level, starts or restarts a transmission reception point (TRP)-specific beam failure detection timer.
  • TRP transmission reception point
  • the MAC entity of the terminal equipment determines whether the beam failure instance indication is TRP specific or TRP level; and in the case where the beam failure instance indication is TRP specific or TRP level, starts or restarts the transmission reception point (TRP)-specific beam failure detection timer.
  • FIG. 9 is another schematic diagram of a method for detecting beam failure according to an embodiment of the present application, schematically illustrating an operation of an MAC entity of a terminal equipment. As shown in FIG. 9 , the operation of the MAC entity includes:
  • the operation of the MAC entity further includes:
  • FIG. 9 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order between the operations may be appropriately adjusted, and some other operations may be added or some of the operations may be reduced.
  • appropriate variants may be made by those skilled in the art according to the above contents, which are not limited to the description of FIG. 9 described above.
  • FIG. 10 is another schematic diagram of a method for detecting beam failure according to an embodiment of the present application, schematically illustrating an operation of an MAC entity of a terminal equipment. As shown in FIG. 10 , the operation of the MAC entity includes:
  • the operation of the MAC entity further includes:
  • FIG. 10 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order between the operations may be appropriately adjusted, and some other operations may be added or some of the operations may be reduced.
  • appropriate variants may be made by those skilled in the art according to the above contents, which are not limited to the description of FIG. 10 described above.
  • FIG. 11A is another schematic diagram of a method for detecting beam failure according to an embodiment of the present application, schematically illustrating an operation of an MAC entity of a terminal equipment. As shown in FIG. 11A , the operation of the MAC entity includes:
  • the operation of the MAC entity further includes:
  • the operation of the MAC entity further includes:
  • FIG. 11A only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order between the operations may be appropriately adjusted, and some other operations may be added or some of the operations may be reduced.
  • appropriate variants may be made by those skilled in the art according to the above contents, which are not limited to the description of FIG. 11A described above.
  • FIG. 11B is another schematic diagram of a method for detecting beam failure according to an embodiment of the present application, schematically illustrating an operation of an MAC entity of a terminal equipment. As shown in FIG. 11B , the operation of the MAC entity includes:
  • the multiple TRPs include all TRPs configured with TRP-specific beam failure detection of all serving cells in the MAC entity, or all TRPs configured with TRP-specific beam failure detection of a special cell in the MAC entity.
  • BFR beam failure recovery
  • the operation of the MAC entity further includes:
  • the operation of the MAC entity further includes: 1110B, initiating a random access procedure on the special cell (SpCell).
  • FIG. 11B only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order between the operations may be appropriately adjusted, and some other operations may be added or some of the operations may be reduced.
  • appropriate variants may be made by those skilled in the art according to the above contents, which are not limited to the description of FIG. 11B described above.
  • a cell-specific BFD on a specific cell should be configured, or a cell-specific BFD on a belonging cell should be configured or a cell-specific BFD on at least one cell should be configured.
  • the MAC entity of the terminal equipment receives a beam failure instance indication, increments a transmission reception point (TRP)-specific beam failure indication count by 1, and in a case where the TRP-specific beam failure indication count is greater than or equal to a TRP-specific beam failure instance maximum count, determines that a beam failure occurs in a transmission reception point or beam failure recovery (BFR) of the transmission reception point is triggered or a beam failure indication of the transmission reception point is triggered.
  • BFR beam failure recovery
  • the following description is based on the embodiments of the first and second aspects, and the same contents as the embodiments of the first and second aspects are not repeated.
  • the embodiments of the third aspect may be performed separately or in combination with the embodiments of the first and second aspects; and in addition, the embodiments of the third aspect may be applicable to TRP-specific BFR/BFD as well as cell-specific BFR/BFD, such as Rel-16 BFR/BFD.
  • a medium access control (MAC) entity of a terminal equipment detects that a beam failure occurs in a transmission reception point or a cell, or that the beam failure recovery (BFR) of the transmission reception point or the cell is triggered, or that beam failure indication of the transmission reception point or the cell is triggered; and the MAC entity of the terminal equipment instructs the multiplexing and assembly entity to generate a beam failure recovery MAC CE or a beam failure MAC CE.
  • MAC medium access control
  • the MAC entity of the terminal equipment determines whether the evaluation of the candidate beam is completed when the candidate beam is configured. For example, completion of subsequent beam evaluation is considered only when candidate beams are configured and the MAC entity indicates generation (Truncated) BFR MAC CE.
  • the MAC entity of the terminal equipment instructs the multiplexing and assemble entity to generate the beam failure recovery MAC CE or the beam failure MAC CE.
  • the MAC entity of the terminal equipment does not determine whether the evaluation of the candidate beam is completed.
  • the MAC entity of the terminal equipment determines that the evaluation of the candidate beam has been completed if the candidate beam is not configured in the case where at least one beam failure recovery is triggered.
  • the physical layer of the terminal equipment upon receiving the higher layer request, determines that the evaluation of the candidate beam has been completed in the case where the candidate beam is not configured.
  • a candidate reference signal is configured in a case where a reference signal for beam failure detection is configured. For example, if a reference signal for beam failure detection is configured, a candidate reference signal should be configured.
  • candidateBeamConfig Indicates the resource (i.e. SSB or CSI-RS) defining this beam resource.
  • candidateBeamRSSCellList A list of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery.
  • the network always configures this parameter in every instance of this IE.
  • rsrp-ThresholdBFR L1-RSRP threshold used for determining whether a candidate beam may be included by the UE be in BFR MAC CE (see TS 38.213 [13], clause X).
  • the network always configures this parameter in every instance of this IE.
  • the RS belongs to the serving cell in which this BeamFailureSCellRecoveryConfig is configured Table 21 Conditional Presence Explanation BFD-RS
  • the field is mandatory present if the radioLinkMonitoringRS-Id associated purpose is "beamFailure" or "both" is configured in the RadioLinkMonitoringConfig; else, the field is absent.
  • the MAC entity will determine whether to instruct generation of an MAC CE or trigger an SR.
  • the MAC entity For example, for each cell/TRP configured with beam failure recovery or with beam failure recovery parameters, and/or configured with beam failure detection or with beam failure detection parameters, the MAC entity will,
  • the MAC entity will perform beam failure detection to trigger the BFR.
  • a cell-specific beam failure detection is taken as an example: for each serving cell configured with beam failure detection (or configured with beam failure detection parameters), and/or configured with beam failure recovery (or configured with beam failure recovery parameters), the MAC entity will:
  • a cell-specific beam failure detection is taken as an example: for each serving cell configured with beam failure detection (or configured with beam failure detection parameters), and/or configured with beam failure recovery (or configured with beam failure recovery parameters), the MAC entity will:
  • the operation of the MAC entity is schematically described above, and embodiments of the present application are not limited thereto.
  • the beam failure recovery parameters described above may be replaced with specific parameters, such as one or more of the following parameters:
  • the embodiments of the present application provide an apparatus for detecting beam failure.
  • the apparatus may be, for example, a terminal device or may be a certain or some parts or components configured in the terminal device, and the same content as the embodiments of the first to third aspects will not be described in detail.
  • FIG. 12 is a schematic diagram of an apparatus for detecting beam failure according to an embodiment of the present application. As shown in FIG. 12 , the apparatus 1200 for detecting beam failure includes:
  • the apparatus 1200 for detecting beam failure further includes:
  • the MAC entity of the terminal equipment instructs the multiplexing and assembly entity to generate a TRP-specific beam failure recovery MAC CE or a TRP-specific beam failure MAC CE.
  • the MAC entity of the terminal equipment determines whether the evaluation of the candidate beam is completed when the candidate beam is configured.
  • the MAC entity of the terminal equipment instructs the multiplexing and assemble entity to generate the TRP-specific beam failure recovery MAC CE or the TRP-specific beam failure MAC CE.
  • the MAC entity of the terminal equipment does not determine whether the evaluation of the candidate beam is completed.
  • the MAC entity of the terminal equipment determines that the evaluation of the candidate beam has been completed if the candidate beam is not configured in the case where at least one beam failure recovery is triggered.
  • the physical layer of the terminal equipment upon receiving the higher layer request, determines that the evaluation of the candidate beam has been completed in the case where the candidate beam is not configured.
  • a candidate reference signal is configured.
  • some or all of the serving cells in the MAC entity of the terminal equipment are configure with TRP-specific beam failure detection, and/or, a special cell in the MAC entity of the terminal equipment is configured with the TRP-specific beam failure detection.
  • all of the serving cells in the MAC entity of the terminal equipment do not configured with cell-specific beam failure detection, or, a special cell in the MAC entity of the terminal equipment does not configured with the cell-specific beam failure detection.
  • the MAC entity of the terminal equipment initiates a random access procedure in the special cell.
  • the multiple TRPs include all TRPs configured with TRP-specific beam failure detection of all serving cells in an MAC entity, or all TRPs configured with TRP-specific beam failure detection of a special cell in an MAC entity.
  • the MAC entity of the terminal equipment determines whether the transmission reception point belongs to a secondary cell; and in a case where the transmission reception point belongs to a secondary cell, determines that a beam failure occurs in the transmission reception point or beam failure recovery of the transmission reception point is triggered or a beam failure indication of the transmission reception point is triggered.
  • the MAC entity of the terminal equipment determines whether all TRPs configured with TRP-specific beam failure detection are triggered for beam failure recovery; in the case where all TRPs configured with TRP-specific beam failure detection are triggered for beam failure recovery, the MAC entity of the terminal equipment initiates a random access procedure in the special cell.
  • the terminal equipment performs one or any combination of the following:
  • the terminal equipment triggers a scheduling request (SR) for the TRP-specific beam failure recovery or the TRP-specific beam failure, for a TRP that has triggered a BFR and has not been cancelled.
  • SR scheduling request
  • the scheduling request configures a SR ID or a set of SR IDs.
  • the configuration value of the TRP-specific beam failure recovery SR ID is the same as the configuration value of the cell-specific beam failure recovery SR ID, or the configuration value of the TRP-specific beam failure recovery SR ID is different from the configuration valueof the cell-specific beam failure recovery SR ID.
  • the configuration values of the TRP-specific beam failure recovery SR ID and the control resource pool index are the same as the configuration value of the cell-specific beam failure recovery SR ID, or the configuration values of the TRP-specific beam failure recovery SR ID and the control resource pool index are different from the configuration value of the cell-specific beam failure recovery SR ID.
  • the MAC entity when an MAC entity of a terminal equipment has a pending SR for a TRP-specific BFR, and for an SR transmission occasion, the MAC entity has one or more PUCCH resources overlapping with PUCCH resources of the TRP-specific BFR, the MAC entity determines (deems) that the PUCCH resources of the TRP-specific BFR are valid; or
  • the MAC entity determines (deems) that the PUCCH resources of the secondary cell/TRP-specific BFR are valid.
  • an MAC PDU performs transmission using an uplink grant except an uplink grant provided by random access response (RAR) or an uplink grant determined from the transmission of the message A payload (MSGA payload)
  • the MAC PDU includes an MAC CE including beam failure information of a TRP
  • the MAC entity of the terminal equipment stops the ongoing random access procedure due to the pending SR for the BFR of the TRP.
  • the MAC entity of the terminal equipment determines whether the beam failure instance indication is cell specific or cell level; and in the case where the beam failure instance indication is not cell specific or cell level, starts or restarts a transmission reception point (TRP)-specific beam failure detection timer.
  • TRP transmission reception point
  • the MAC entity of the terminal equipment determines whether the beam failure instance indication is TRP specific or TRP level; and in the case where the beam failure instance indication is TRP specific or TRP level, starts or restarts the transmission reception point (TRP)-specific beam failure detection timer.
  • a cell-specific beam failure detection timer is started or restarted
  • the cell-specific beam failure indication count is reset or the cell-specific beam failure indication count is set to 0 in the case where the TRP-specific beam failure detection timer has expired.
  • the apparatus 1200 for detecting beam failure may further include other components or modules, and related art may be referred to for details of these components or modules.
  • Fig. 12 exemplarily shows only the connection relationship or signal trend between the various components or modules, however, it should be clear to a person skilled in the art that various related techniques such as bus connection may be used.
  • the various components or modules described above may be implemented by hardware facilities such as a processor, a memory, a transmitter, a receiver, etc.; implementation of the present application is not limited thereto.
  • the MAC entity of the terminal equipment receives a beam failure instance indication, increments a transmission reception point (TRP)-specific beam failure indication count by 1, and in a case where the TRP-specific beam failure indication count is greater than or equal to a TRP-specific beam failure instance maximum count, determines that a beam failure occurs in a transmission reception point or beam failure recovery (BFR) of the transmission reception point is triggered or a beam failure indication of the transmission reception point is triggered.
  • BFR beam failure recovery
  • An embodiment of the present application further provides a communication system, which can refer to FIG. 1 , and the same content as the embodiments of the first to fourth aspects will not be described in detail.
  • the communication system may include:
  • An embodiment of the present application further provides a network device, which may be, for example, a base station, but the present application is not limited thereto, and may also be other network devices.
  • a network device which may be, for example, a base station, but the present application is not limited thereto, and may also be other network devices.
  • FIG. 13 is a configuration diagram of a network device according to an embodiment of the present application.
  • the network device 1300 may include a processor 1300 (such as a central processing unit (CPU)) and a memory 1320; the memory 1320 is coupled to the processor 1310.
  • the memory 1320 can store various data; a program 1330 for information processing is also stored and the program 1330 is executed under the control of the processor 1310.
  • the network device 1300 may further include a transceiver 1340 and an antenna 1350, etc.; the functions of the above-mentioned components are similar to those of the relevant art, and will not be described again here. It is worth noting that the network device 1300 is not necessarily required to include all of the components shown in FIG. 13 ; in addition, the network device 1300 may further include components not shown in FIG. 13 , with reference to the relevant art.
  • An embodiment of the present application further provides a terminal device, but the present application is not limited thereto, and may also be other devices.
  • FIG. 14 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 1400 may include a processor 1410 and a memory 1420; the memory 1420 stores data and program and is coupled to the processor 1410. It is worth noting that this figure is exemplary; other types of structures may also be used in addition to or instead of the structure to implement telecommunications functions or other functions.
  • the processor 1410 may be configured to execute a program to implement the method for detecting beam failure as described in the embodiment of the first aspect.
  • the processor 1410 may be configured to perform the following controls: receiving a beam failure instance indication by a medium access control (MAC) entity; incrementing a transmission reception point (TRP)-specific beam failure indication count by 1; and in a case where the TRP-specific beam failure indication count is greater than or equal to a TRP-specific beam failure instance maximum count, determining that a beam failure occurs in a transmission reception point or beam failure recovery (BFR) of the transmission reception point is triggered or a beam failure indication of the transmission reception point is triggered.
  • MAC medium access control
  • BFR beam failure recovery
  • the processor 1410 may be configured to execute a program to implement the method for detecting beam failure as described in the embodiment of the second aspect.
  • the processor 1410 may be configured to perform the following controls: receiving a beam failure instance indication by a medium access control (MAC) entity; determining whether the beam failure instance indication is TRP specific or TRP level; incrementing 1 to the TRP-specific beam failure indication count in the case where the beam failure instance indication is TRP specific or TRP level; and in a case where the TRP-specific beam failure indication count is greater than or equal to a maximum count of a TRP-specific beam failure instance, determining that a beam failure occurs in a transmission reception point or beam failure recovery (BFR) of the transmission reception point is triggered or a beam failure indication of the transmission reception point is triggered.
  • MAC medium access control
  • the processor 1410 may be configured to execute a program to implement the method for detecting beam failure as described in the embodiment of the third aspect.
  • the processor 1410 may be configured to perform the following controls: detecting, by a medium access control (MAC) entity, that a beam failure occurs at a transmission reception point or in a cell or that the beam failure recovery (BFR) at the transmission reception point or in the cell is triggered or that beam failure indication of the transmission reception point or the cell is triggered; and instructing, by the MAC entity, the multiplexing and assembly entity to generate a beam failure recovery MAC CE or a beam failure MAC CE.
  • MAC medium access control
  • BFR beam failure recovery
  • the terminal device 1400 may further include a communication module 1430, an input unit 1440, a display 1450, and a power supply 1460.
  • the functions of the above-mentioned components are similar to those of the relevant art, and will not be described again here. It is worth noting that the terminal device 1400 is not necessarily required to include all of the components shown in FIG. 14 , and the above components are not necessary; in addition, the terminal device 1400 may further include components not shown in FIG. 14 , with reference to the relevant art.
  • Embodiments of the present application further provide a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method for detecting beam failure as described in the embodiments of the first to third aspects.
  • Embodiments of the present application further provide a storage medium in which a computer program is stored, wherein the computer program causes the terminal device to execute the method for detecting beam failure as described in the embodiments of the first to third aspects.
  • the above apparatus and method of the present application may be implemented by hardware, or may be implemented by hardware in combination with software.
  • the present application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or constituent components described above, or enables the logic component to implement the various methods or steps described above.
  • the present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.
  • the method/apparatus described in connection with embodiments of the present application may be embodied directly in hardware, a software module executed by a processor, or a combination of both.
  • one or more of the functional blocks and/or one or more combinations of the functional blocks shown in the drawings may correspond to each software module or each hardware module of a computer program flow.
  • These software modules may correspond to the respective steps shown in the drawings.
  • the hardware modules may be implemented, for example, by solidifying the software modules using a field programmable gate array (FPGA).
  • FPGA field programmable gate array
  • a software module may be located in an RAM memory, a flash memory, an ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • a storage medium may be coupled to the processor to enable the processor to read information from and write information to the storage medium, or the storage medium may be an integral part of the processor.
  • the processor and the storage medium may reside in an ASIC.
  • the software module may be stored in a memory of the mobile terminal or in a memory card insertable into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or the large-capacity flash memory device.
  • One or more of the functional blocks and/or one or more combinations of the functional blocks depicted in the accompanying drawings may be implemented as a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, a discrete gate or a transistor logic device, a discrete hardware component, or any suitable combination thereof designed to perform the functions described in the present application.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • One or more of the functional blocks and/or one or more combinations of the functional blocks depicted in the accompanying drawings may also be implemented as combination of computing devices, e.g., combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in communication with the DSP, or any other such configuration.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
EP21918324.1A 2021-01-13 2021-01-13 Procédé et appareil de détection de défaillance de faisceau Pending EP4280659A4 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/071617 WO2022151109A1 (fr) 2021-01-13 2021-01-13 Procédé et appareil de détection de défaillance de faisceau

Publications (2)

Publication Number Publication Date
EP4280659A1 true EP4280659A1 (fr) 2023-11-22
EP4280659A4 EP4280659A4 (fr) 2024-03-20

Family

ID=82446643

Family Applications (1)

Application Number Title Priority Date Filing Date
EP21918324.1A Pending EP4280659A4 (fr) 2021-01-13 2021-01-13 Procédé et appareil de détection de défaillance de faisceau

Country Status (6)

Country Link
US (1) US20230353223A1 (fr)
EP (1) EP4280659A4 (fr)
JP (1) JP2024502137A (fr)
KR (1) KR20230113385A (fr)
CN (1) CN116746192A (fr)
WO (1) WO2022151109A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
BR112022002360A2 (pt) * 2019-08-15 2022-04-26 Guangdong Oppo Mobile Telecommunications Corp Ltd Método de comunicação sem fio e dispositivo terminal
US20230118940A1 (en) * 2021-10-19 2023-04-20 Qualcomm Incorporated Beam failure detection per beam for multi-beam communications

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110708714B (zh) * 2018-07-10 2022-01-25 维沃移动通信有限公司 波束失败检测方法、终端和网络设备
CN110896546B (zh) * 2018-09-13 2022-04-22 展讯通信（上海）有限公司 波束失败恢复方法及装置、存储介质、用户设备
CN111278122B (zh) * 2019-01-25 2023-03-24 维沃移动通信有限公司 波束失败恢复方法、处理方法、终端及网络侧设备
US11211990B2 (en) * 2019-05-01 2021-12-28 Ofinno, Llc Beam failure recovery in multi-TRP scenarios

Also Published As

Publication number Publication date
KR20230113385A (ko) 2023-07-28
JP2024502137A (ja) 2024-01-17
WO2022151109A1 (fr) 2022-07-21
CN116746192A (zh) 2023-09-12
EP4280659A4 (fr) 2024-03-20
US20230353223A1 (en) 2023-11-02

Similar Documents

Publication Publication Date Title
US11743817B2 (en) Communication system and base station
US11937331B2 (en) Technologies for controlling discontinuous reception operation
US20210400567A1 (en) Preconfiguring dedicated resource information in idle mode
EP2774282B1 (fr) L'enregistrement d'informations sur l'échec d'une procédure d'accès aléatoire
EP3437422B1 (fr) Procédés permettant de limiter une interruption dans une opération de prose à porteuses multiples, noeud de réseau, dispositif sans fil et mémoire non transitoire lisible par ordinateur
US11564255B2 (en) Method and apparatus for processing LBT monitoring failures and system
US20230353223A1 (en) Method and apparatus for detecting beam failure
US10231239B2 (en) Method and apparatus for resolving time domain conflict in device-to-device communication
US20230025873A1 (en) Method and apparatus for consistent lbt failure detection and recovery
WO2022027437A1 (fr) Commutation de partie de bande passante dormante de cellule spéciale
WO2022027420A1 (fr) Dormance cellulaire spéciale pour nouvelle radio
KR20230146656A (ko) 사이드링크 불연속 수신 커맨드 트리거 방법, 장치, 및 시스템
WO2024081216A1 (fr) Support d'ancrage pour économie d'énergie de réseau
KR20150109964A (ko) 이동 단말기 및 그 제어방법

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20230706

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Free format text: PREVIOUS MAIN CLASS: H04W0024040000

Ipc: H04B0007060000

A4 Supplementary search report drawn up and despatched

Effective date: 20240215

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 16/28 20090101ALI20240209BHEP

Ipc: H04B 7/024 20170101ALI20240209BHEP

Ipc: H04B 7/06 20060101AFI20240209BHEP

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)