WO2022150994A1 - Mécanisme de récupération après défaillance de faisceau - Google Patents

Mécanisme de récupération après défaillance de faisceau Download PDF

Info

Publication number
WO2022150994A1
WO2022150994A1 PCT/CN2021/071344 CN2021071344W WO2022150994A1 WO 2022150994 A1 WO2022150994 A1 WO 2022150994A1 CN 2021071344 W CN2021071344 W CN 2021071344W WO 2022150994 A1 WO2022150994 A1 WO 2022150994A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
resource
index
rrc
network device
Prior art date
Application number
PCT/CN2021/071344
Other languages
English (en)
Inventor
Ran YUE
Lianhai WU
Jing HAN
Haiming Wang
Bingchao LIU
Original Assignee
Lenovo (Beijing) Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo (Beijing) Limited filed Critical Lenovo (Beijing) Limited
Priority to PCT/CN2021/071344 priority Critical patent/WO2022150994A1/fr
Publication of WO2022150994A1 publication Critical patent/WO2022150994A1/fr

Links

Images

Classifications

    • 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
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/004—Transmission of channel access control information in the uplink, i.e. towards network

Definitions

  • the present disclosure relates generally to wireless communications, and more particularly to wireless communications systems, devices, methods, and computer readable medium for beam failure detection or recovery when a terminal device is in a non radio resource control (RRC) connected state.
  • RRC radio resource control
  • beamforming is a particular processing technique for signals that allow for directional transmission or reception.
  • beam based cell sector coverage is used.
  • data transmissions and signaling transmissions are beam-formed and directional.
  • a terminal device connects to a single beam. If a beam failure occurs when there is a change of a surrounding environment, the terminal device can request for a recovery of the beam.
  • example embodiments of the present disclosure provide a solution for beam failure detection or detection when a terminal device, for example, user equipment (UE) , in a non radio resource control (RRC) connected state.
  • UE user equipment
  • RRC radio resource control
  • An exemplary embodiment of the present disclosure provides a method performed by a terminal device in a non RRC_CONNECTED state.
  • the method includes triggering a beam failure recovery (BFR) while the terminal device is in the non RRC_CONNECTED, in response to a presence of a beam failure or the beam failure instance indications up to the configured maximum number.
  • BFR beam failure recovery
  • the method also includes identifying a resource for transmitting information relating to the beam failure to a network device.
  • the method further includes transmitting information relating to the beam failure to the network device via the resource as identified.
  • An exemplary embodiment of the present disclosure provides a method of performed by a network device.
  • the method comprises receiving, from a terminal device, information at least indicating a presence of a beam failure.
  • the method also comprises transmitting, to the terminal device while the terminal device is in the non RRC-CONNECTED state, configuration information relating to a beam failure recovery (BFR) .
  • BFR beam failure recovery
  • the first terminal device includes a processor; and a memory coupled to the processor and storing instructions thereon, the instructions, when executed by the processor, causing the first terminal device to perform the method according to the first aspect.
  • the second terminal device includes a processor; and a memory coupled to the processor and storing instructions thereon, the instructions, when executed by the processor, causing the network device to perform the method according to the second aspect.
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to carry out the method according to the first aspect.
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to carry out the method according to the second aspect.
  • UE can be interchanged in this specification with the broader term “electronic device” and vice versa.
  • Figs. 1A and 1B illustrate schematic diagrams of medium access control (MAC) control element (CE) according to conventional technologies, respectively;
  • MAC medium access control
  • CE control element
  • Fig. 2 illustrates a schematic diagram of a communication system in accordance with an exemplary embodiment
  • Fig. 3 illustrates a signaling chart illustrating an example process in accordance with an exemplary embodiment
  • Fig. 4 illustrates a schematic diagram of MAC CE in accordance with an exemplary embodiment
  • Fig. 5 illustrates a flowchart of an example method in accordance with an exemplary embodiment
  • Fig. 6 illustrates a flowchart of an example method in accordance with an exemplary embodiment
  • Fig. 7 illustrates a simplified block diagram of an apparatus that is suitable for implementing embodiments of the present disclosure.
  • the 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunications network technologies, including radio access, the core transport network, and service capabilities -including work on codecs, security, and quality of service.
  • 3GPP 3 rd Generation Partnership Project UE User Equipment 5G The fifth generation RRC Radio Resource Control NR New Radio RAN Radio Access Network MAC Medium Access Control PHY Physical Layer NAS Non-access Stratum AS Access Stratum UL Uplink DL Downlink AC Access Category AI Access Identity
  • the term “network device” 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 NodeB in new radio access (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, a satellite network device, an aircraft network device, and the like.
  • NodeB Node B
  • eNodeB or eNB Evolved NodeB
  • gNB NodeB in new radio access
  • RRU Remote Radio Unit
  • RH radio head
  • RRH remote radio head
  • a low power node such as a femto node, a pico node, a satellite network
  • 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 or evolved MTC (eMTC) devices, devices 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
  • Communication discussed herein can conform to any suitable wireless interface standards including, but not limited to, New Radio Access (NR) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , cdma2000, and Global System for Mobile Communications (GSM) and the like.
  • NR New Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Evolution
  • WCDMA Wideband Code Division Multiple Access
  • CDMA Code Division Multiple Access
  • GSM Global System for Mobile Communications
  • Such communication can be performed according to any communication protocol either currently known or to be developed in the future. Examples of the communication protocols include, but are 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 techniques described herein can be used for
  • 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.
  • the terminal device when the terminal device is suffering from a poor channel condition, a beam failure can occur on the current beam.
  • the terminal device can request for a recovery of the beam.
  • a beam failure recovery procedure is introduced in the communication system to solve this problem.
  • the beam failure recovery procedure may include a beam failure detection step, a new candidate beam identification step, a beam failure recovery request step, and a beam failure recovery response step.
  • the term “non RRC_CONNECTED state” can refer to a state where the terminal device does not have an established RRC connection with a network device or a state where the terminal device maintains a RRC connection with the network device and minimizes signaling and power consumption at the same time.
  • the terminal device can be in a RRC_IDLE state.
  • the terminal device can be in a RRC_INACTIVE state.
  • small data transmission SDT
  • SDT small data transmission
  • the term “small data transmission” or “SDT” refers to a mechanism which enables small data transmission in RRC_INACTIVE state.
  • BFD beam failure detection
  • BFR recovery
  • the MAC entity may be configured by RRC per Serving Cell with a beam failure recovery procedure which is used for indicating to the serving gNB of a new synchronization signal block (SSB) or channel state information reference signal (CSI-RS) when beam failure is detected on the serving SSB (s) /CSI-RS (s) .
  • Beam failure is detected by counting beam failure instance indication from the lower layers to the MAC entity. If beamFailureRecoveryConfig is reconfigured by upper layers during an ongoing Random Access procedure for beam failure recovery for SpCell, the MAC entity shall stop the ongoing Random Access procedure and initiate a Random Access procedure using the new configuration.
  • Both BFR MAC CE and Truncated BFR MAC CE have a variable size.
  • MAC PDU shall contain at most one BFR MAC CE.
  • Fig. 1A shows a BFR MAC CE with the highest ServingCellIndex of this MAC entity’s SCell configured with BFD is less than 8. As shown in Fig.
  • the bit fields 110-1, 110-2, ...., and 110-7 correspond to configured serving cells.
  • the bit fields 120-1 , ..., 120-P can indicate the presence of the Candidate RS ID field in this octet. and the bit fields 130-1, ..., 130-P can represent reserved bit. For example, if the candidate RS ID is present in this octet, the corresponding bit field 120 can be set to “1” .
  • the bit fields 140-1, .., 140-P can indicate candidate reference signal identities or reserved bits.
  • the number P can be any suitable number less than 64.
  • Fig. 1B shows a BFR MAC CE with the highest ServingCellIndex of this MAC entity’s SCell configured with BFD is equal to or higher than 8.
  • the bit fields 111-1, 111-2, ...., and 111-24 correspond to configured serving cells.
  • the bit fields 121-1 , ..., 120-M can indicate the presence of the Candidate RS ID field in this octet. and the bit fields 131-1, ..., 131-M can represent reserved bit.
  • the bit fields 141-1, .., 141-M can indicate candidate reference signal identities or reserved bits.
  • the number P can be any suitable number.
  • Fig. 2 illustrates a schematic diagram of a communication system 200 in which embodiments of the present disclosure can be implemented.
  • the communication system 200 which is a part of a communication network, comprises a terminal device 210-1, a terminal device 210-2, ..., a terminal device 210-N, which can be collectively referred to as “terminal device (s) 210. ”
  • the number N can be any suitable integer number.
  • the communication system 200 further comprises a network device 220.
  • the network device 220 and the terminal devices 210 can communicate data and control information to each other.
  • the numbers of devices shown in Fig. 2 are given for the purpose of illustration without suggesting any limitations.
  • Communications in the communication system 200 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • s cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • IEEE Institute for Electrical and Electronics Engineers
  • the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Divided Multiple Address (CDMA) , Frequency Divided Multiple Address (FDMA) , Time Divided Multiple Address (TDMA) , Frequency Divided Duplexer (FDD) , Time Divided Duplexer (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Divided Multiple Access (OFDMA) and/or any other technologies currently known or to be developed in the future.
  • CDMA Code Divided Multiple Address
  • FDMA Frequency Divided Multiple Address
  • TDMA Time Divided Multiple Address
  • FDD Frequency Divided Duplexer
  • TDD Time Divided Duplexer
  • MIMO Multiple-Input Multiple-Output
  • OFDMA Orthogonal Frequency Divided Multiple Access
  • Embodiments of the present disclosure can be applied to any suitable scenarios.
  • embodiments of the present disclosure can be implemented at reduced capability NR devices.
  • embodiments of the present disclosure can be implemented in one of the followings: NR multiple-input and multiple-output (MIMO) , NR sidelink enhancements, NR systems with frequency above 52.6GHz, an extending NR operation up to 71GHz, narrow band-Internet of Thing (NB-IOT) /enhanced Machine Type Communication (eMTC) over non-terrestrial networks (NTN) , NTN, UE power saving enhancements, NR coverage enhancement, NB-IoT and LTE-MTC, Integrated Access and Backhaul (IAB) , NR Multicast and Broadcast Services, or enhancements on Multi-Radio Dual-Connectivity.
  • MIMO multiple-input and multiple-output
  • NR sidelink enhancements NR systems with frequency above 52.6GHz, an extending NR operation up to 71GHz
  • NB-IOT narrow band-Internet of
  • Fig. 3 illustrates a signaling chart demonstrating an example process 300 according to some embodiments of the present disclosure.
  • the process 300 will be described with reference to Fig. 2. Only for the purpose of illustrations, the process 300 can involve the terminal device 210-1 and the network device 220 as illustrated in Fig. 2. Embodiments of the present disclosure can also be applied to unlicensed spectrum scenario.
  • the network device 220 can transmit 3005 parameters related to a unified access control (UAC) configuration to the terminal device 210-1.
  • UAC unified access control
  • the term “UAC” used herein refer to a set of mechanism to determine whether to allow the terminal device for a specific service or state change. UAC can get many factors involved at each point of determining whether to allow the terminal device for the specific service or state change.
  • the parameters can be transmitted in a system broadcast message. Alternatively, the parameters can be transmitted in a RRC release message. In other embodiments, the network device 220 can transmit the parameters in a RRC configuration message or a RRC reconfiguration message. It should be noted that embodiments of the present disclosure can be applied to cases where the UAC is not applied.
  • the parameters can comprise an access category (AC) for a report triggered by a layer lower than RRC layer for a data transmission in the non RRC_CONNECTED state.
  • the report can be a BFR for SDT.
  • the report can be a BFR for data transmission in the non RRC_CONNECTED state.
  • the report can be a BFR for sidelink.
  • the report can be a PC5 related indication. For example, if the terminal device 210-1 is configured with SDT in Uu interface and the beam failure takes place in PC5 interface. The terminal device 210-1 can transmit the BFR for sidelink/PC5 in Uu as CG based SDT.
  • the terminal device 210-1 can transmit the BFR for sidelink/PC5 in Uu as RACH based SDT. In other embodiments, terminal device 210-1 can transmit the BFR for sidelink/PC5 in Uu as RACH.
  • the term “access category (AC) ” used herein refers to a number or an index that can represent a type of a traffic for establishing or resuming a connection with the network device, or represent a reason for the access. For example, if the parameters indicate that the AC is “x” , the terminal device 210-1 can select the AC “x” if the BFR is triggered.
  • the parameters can comprise an access identity for the report triggered by a layer lower than RRC layer for a data transmission in the non RRC_CONNECTED state.
  • the term “access identity” used herein refers to a number or an index that can identify an access to the network device or identify the urgency degree for the access. For example, if the parameters indicate that the AI is “k” , the terminal device 210-1 can select the AI “k” if the BFR is triggered or the access attempt is urgent.
  • the parameters can also comprise a barring factor corresponding to the access category or the access identity for the BFR for the data transmission when the terminal device 210-1 is in the non RRC_CONNECTED state.
  • barring factor refers to a factor associated with a probability of successfully establishing or resuming the connection with the network device.
  • the terminal device 210-1 can determine a resume or RRC establishment cause for the BFR for the data transmission when the terminal device 210-1 is in the non RRC_CONNECTED state. For example, the terminal device 210-1 can add a cause value for the BFR to a set of RRC establishment cause values.
  • the terminal device 210-1 can determine a mapping relation between the AC and the cause value. For example, the terminal device 210-1 can determine the mapping relation between the AC “x” and the cause value. Alternatively or in addition, the terminal device 210-1 can determine a mapping relation between the AI and the cause value. For example, the terminal device 210-1 can determine the mapping relation between the AI “k” and the cause value.
  • the terminal device 210-1 triggers 3010 a BFR.
  • beam failure used herein can refer to a situation where a radio link quality between the network device 220 and the terminal device 210-1 is poor.
  • the BFR can be configured per BWP.
  • the BFR can be configured per serving cell.
  • the terminal device 210-1 can receive a reference signal from the network device 220. In this situation, the terminal device 210-1 can determine whether the beam failure has occurred based on the reference signal.
  • a reference signal used to detect a beam failure can be defined as a beam failure detection RS (BFD-RS) . For example, if the received power of the reference signal is below a threshold power, the terminal device 210-1 can determine that the beam failure occurs. Alternatively, if the terminal device 210-1 cannot receive the reference signal, the terminal device 210-1 can determine that the beam failure occurs.
  • the terminal device 210-1 can measure a radio link quality of the channel using the BFD-RS. The radio link quality can be a hypothetical block error rate (BLER) .
  • BLER block error rate
  • the terminal device 210-1 can determine that the radio link of the corresponding beam is disconnected and the beam failure occurs.
  • the threshold Q out_LR may be an out-of-synchronization threshold used in radio link monitoring (RLM) .
  • the reference signal can comprise a channel state information reference signal (CSI-RS) .
  • the reference signal can comprise a demodulation-reference signal (DM-RS) .
  • the reference signal can comprises a phasing tracing reference signal (PT-RS) .
  • the reference signal can also comprise a cell-specific reference signal (CRS) .
  • the terminal device 210-1 can receive a synchronization signal (SS) block from the network device 220. In this situation, the terminal device 210-1 can determine whether the beam failure has occurred based on the SS block. For example, if the received power of the SS block is below a threshold power, the terminal device 210-1 can determine that the beam failure occurs. Alternatively, if the terminal device 210-1 cannot receive the SS block, the terminal device 210-1 can determine that the beam failure occurs. In some embodiments, the terminal device 210-1 can receive a physical broadcast channel (PBCH) block from the network device 220. In this situation, the terminal device 210-1 can determine whether the beam failure has occurred based on the PBCH block.
  • PBCH physical broadcast channel
  • the terminal device 210-1 can determine that the beam failure occurs. Alternatively, if the terminal device 210-1 cannot receive the PBCH block, the terminal device 210-1 can determine that the beam failure occurs.
  • the beam failure can be determined based on several measurement results.
  • the terminal device 210-1 can determine that one beam failure instance has occurred.
  • the occurrence of the beam failure instance can be determined by a physical (PHY) layer or a medium access control (MAC) layer at the terminal device 210-1.
  • the MAC layer can determine that a beam failure has occurred if beam failure instances have occurred more than a preconfigured number of times.
  • the PHY layer can recognize whether the beam failure instance has occurred or not based on the measurement result of the radio link quality, and report to the MAC layer information related to the beam failure instance.
  • the information can indicate that the beam failure instance has occurred.
  • the information can indicate the measurement result of the radio link quality, and/or an index of the beam.
  • the information related to the beam failure instance can be referred to as “instance information” .
  • the instance information can be periodically reported from the PHY layer to the MAC layer. For example, if the beam failure instance has occurred, the PHY layer can transmit the instance information to the MAC layer. When the beam failure instance has not occurred, the PHY layer cannot transmit the instance information to the MAC layer.
  • the MAC layer can have a timer and a counter to determine the occurrence of the beam failure.
  • the timer can be used to reset the counter, and the counter can be used to count the number of beam failure instances. IF the timer expires, the counter can be reset, for example, reset to “0” .
  • the MAC layer can determine that a beam failure has occurred when the incremented counter reaches a preconfigured value.
  • the terminal device 210-1 can search for candidate beam (s) when the beam failure is detected.
  • the candidate beam step can be determined after or before the beam failure detection step.
  • the candidate beam may be determined together with the beam failure detection step.
  • the terminal device 210-1 can determine 3015 whether a RRC resume request for the BFR is allowed.
  • the RRC resume request can be called “access attempt. ”
  • the terminal device 210-1 can select the AC for the BFR.
  • the terminal device 210-1 can determine the barring factor according to the AC and determine that the access attempt is allowed based on the barring factor.
  • the terminal device 210-1 can randomly generate a number associated with the barring factor and if the number is lower than a value configured by the network device 220, the access attempt is allowed. Only as an example, the terminal device 210-1 can draw a random number “rand” which is uniformly distributed in the range from 0 to 1. If the random number “rand” is lower than the value indicated by the barring factor, the terminal device 210-1 can determine that the access attempt is allowed.
  • the NAS of the terminal device 210-1 can determine the AI.
  • the NAS of the terminal device 210-1 can determine one or more AIs.
  • the terminal device 210-1 can select one or more AIs when the BFR is triggered.
  • the terminal device 210-1 can determine the barring factor according to the AI and determine that the access attempt is allowed based on the barring factor or indication for the AI contained in "UAC barring parameter" . For example, if for at least one of these Access Identities the corresponding bit in the uac-BarringForAccessIdentity contained in "UAC barring parameter" is set to zero, the terminal device 210-1 can determine that the access attempt is allowed.
  • the terminal device 210-1 can determine that the access attempt for the BFR is allowed.
  • the terminal device 210-1 is configured with a random access channel (RACH) resource or configured with a resource for the data transmission when the terminal device 210-1 is in the non RRC_CONNECTED state, the terminal device 210-1 can determine that the access attempt for the BFR is allowed.
  • the terminal device 2210-1 is configured with a dedicated RACH resource, the terminal device 210-1 can determine that the access attempt for the BFR is allowed.
  • the terminal device 210-1 can generate 3020 information related to the beam failure.
  • the information can comprise the cause value for the BFR.
  • the information can comprise a beam index of a failed beam on which the beam failure occurs.
  • the information can also comprise a SSB index on the failed beam.
  • the information can comprise a PBCH block index on the failed beam.
  • the information can comprise a CSI-RS index on the failed beam.
  • the information can comprise an index relating to an uplink resource corresponding to the failed beam.
  • the index related to the uplink resource can comprise a bandwidth part (BWP) index.
  • the index related to the uplink resource can comprise a physical random access control (PRACH) configuration index.
  • PRACH physical random access control
  • the index related to the uplink resource can also comprise a RACH occasion index.
  • the index related to the uplink resource can comprise a message A physical uplink shared channel (PUSCH) index.
  • PUSCH physical uplink shared channel
  • the term “message A” refers to a message where the terminal device transmits to the network device during 2 step RACH procedure.
  • the index related to the uplink resource can comprise a message 3 physical uplink shared channel (PUSCH) index.
  • PUSCH physical uplink shared channel
  • the terminal device 210-1 can determine a candidate beam for the BFR.
  • the information related to the beam failure can also indicate the candidate beam for which the beam quality is good enough.
  • the information can comprise a beam index of the candidate beam.
  • the information can also comprise a SSB index on the candidate beam.
  • the information can comprise a PBCH block index on the candidate beam.
  • the information can comprise a CSI-RS index on the candidate beam.
  • the information can comprise an index relating to an uplink resource corresponding to the candidate beam.
  • the index related to the uplink resource can comprise a bandwidth part (BWP) index.
  • BWP bandwidth part
  • the index related to the uplink resource can comprise a physical random access control (PRACH) configuration index.
  • the index related to the uplink resource can also comprise a RACH occasion index.
  • the index related to the uplink resource can comprise a message A physical uplink shared channel (PUSCH) index.
  • PRACH physical random access control
  • PUSCH physical uplink shared channel
  • the terminal device 210-1 identifies 3025 a resource for transmitting the BFR.
  • the resource can be configured for the data transmission when the terminal device 210-1 is in the non RRC_CONNECTED state.
  • the terminal device 210-1 can select the resource from a set of resources configured for the data transmission when the terminal device 210-1 is in the non RRC_CONNECTED state.
  • the terminal device 210-1 can select the resource from the set of CG resources, for example the SDT resources. In this case, the terminal device 210-1 can initialize CG based data transmission.
  • the terminal device 210-1 can select the resource from the set of PRACH resources, for example the SDT resources. In this situation, the terminal device 210-1 can initialize RACH based data transmission.
  • the terminal device 210-1 can select the resource from the set of RACH resources. In this case, the terminal device 210-1 can initialize RACH. For example, if the BFR has been triggered for a while or less than a time duration, the terminal device 210-1 can resume the RRC connection by the RACH procedure.
  • the priority for selecting the resource from the set of CG resources is higher than the priority for selecting the resource from the set of resources for the RACH based data transmission in the non RRC_CONNECTED.
  • the terminal device 210-1 can select the resource from the set of CG resources first. In a situation where the CG based data transmission cannot be initialized, the terminal device 210-1 can select the resource from the set of resources for the RACH based data transmission in the non RRC_CONNECTED or the set of RACH resources.
  • the priority for selecting the resource from the set of resources for the RACH based data transmission in the non RRC_CONNECTED is higher than the priority for selecting the resource from the set of resources for the legacy RACH procedure without data transmission in the UL resource.
  • the terminal device 210-1 can select the resource from the set of resources for the RACH based data transmission in the non RRC_CONNECTED state.
  • the terminal device 210-1 can select the resource from the set of resources for the legacy RACH procedure without data transmission in the UL resource. It should be noted that the terminal device 210-1 can identify the resource which is configured for data transmission when the terminal device 210-1 is in RRC_CONNECTED state.
  • the terminal device 210-1 transmits 3025 the information related to the beam failure to the network device 220 via the resource as identified.
  • the information related to the beam failure can be transmitted with SDT which means it can be transmitted with small data on the resources configure with SDT.
  • the information related to the beam failure can be transmitted without SDT including transmitted on the resources configured to SDT without transmitting the small data and transmitted on the RACH resources which are not configured to SDT.
  • the information related to the beam failure can be transmitted in a RRC message.
  • the information related to the beam failure can be transmitted in an uplink control information indication.
  • the information related to the beam failure can be transmitted in a MAC CE.
  • Each bit of the MAC CE can represent a beam state of a resource which configured for the data transmission in the non RRC_CONNECTED state.
  • Fig. 4 illustrates a schematic diagram of an example of MAC CE or a field of a MAC CE. The number of octet shown in Fig. 4 is only an example. It should be noted that the MAC CE can be extended to multiple octets. As shown in Fig. 4, the MAC CE 400 can comprise bits 410-1, 410-2, 410-3, 410-4, 410-5, 410-6, 410-7 and 410-8.
  • the filed corresponding to the resource can be set to “1. ” Only as an example, if the beam failure occurs on the resource corresponding to the field 410-2, the terminal device 210-1 can set the field 410-2 to be “1” . If there is no beam failure on the resource corresponding to the field 410-3, the terminal device 210-1 can set the field 410-3 to be “0” . If there is no resource mapping to the corresponding field of the MAC CE, the corresponding field can be ignored.
  • the MAC CE can be transmitted with a corresponding logical channel identifier (LCID) .
  • a new LCID can be used to indicate the MAC CE of the beam failure. In this situation, the LCID can comprise a subheader of the MAC CE, which means content of the beam failure may not be included.
  • the information related to the beam failure can be transmitted via a signaling.
  • the terminal device 210-1 can multiplex the information related to the beam failure with other messages into a MAC protocol data unit (PDU) .
  • PDU MAC protocol data unit
  • logical channels for different messages can have different priorities.
  • the BFR for SDT MAC CE and the BFR for SDT signaling have the same priority.
  • the BFR for SDT has the same priority with the BFR MAC CE which is used in RRC_CONNECTED state.
  • the BFR for SDT can have higher priority than Sidelink Configured Grant Confirmation MAC CE or listen-before-talk failure MAC CE.
  • the BFR for SDT can have lower priority than cell radio network temporary identity (C-RNTI) MAC CE or data from uplink common control channel (UL-CCCH) .
  • C-RNTI cell radio network temporary identity
  • UL-CCCH uplink common control channel
  • the priority of the BFR for SDT can be higher than data from UL-CCCH.
  • the network device 220 transmits 3030 configuration information related to the BFR.
  • the network device 220 can reconfigure a beam for the terminal device 210-1.
  • the network device 220 can reconfigure the resource for SDT with the candidate beam indicated the information related in the beam failure.
  • the configuration information can indicate an index of the candidate beam.
  • the index of the candidate beam can be similar as those in the information related to the beam failure.
  • the network device 220 may not reconfigure a beam for the terminal device 210-1.
  • the configuration information can comprise an acknowledgment to the information related to the beam failure. In this case, if the terminal device 210-1 receives the acknowledgment successfully, it means that the failed beam has been recovered.
  • the beam failure for the data transmission in the non RRC_CONNECTED state can be transmitted to the network device. It reduces latency.
  • Fig. 5 illustrates a flowchart of an example method 500 according to some embodiments of the present disclosure.
  • the method 500 can be performed by the terminal device 210-1 as shown in Fig. 2. It is to be understood that the method 500 can include additional blocks not shown and/or can omit some blocks as shown, and the scope of the present disclosure is not limited in this regard. For the purpose of discussion, the method 500 will be described from the perspective of the terminal device 210-1 with reference to Fig. 2.
  • the terminal device 210-2 can receive parameters related to a unified access control (UAC) configuration from the network device 220.
  • UAC unified access control
  • the term “UAC” used herein refer to a set of mechanism to determine whether to allow the terminal device for a specific service or state change. UAC can get many factors involved at each point of determining whether to allow the terminal device for the specific service or state change.
  • the parameters can be transmitted in a system broadcast message. Alternatively, the parameters can be transmitted in a RRC release message.
  • the network device 220 can transmit the parameters in a RRC configuration message or a RRC reconfiguration message. It should be noted that embodiments of the present disclosure can be applied to cases where the UAC is not applied.
  • the parameters can comprise an access category (AC) for the BFR for a data transmission when the terminal device 210-1 is in the non RRC_CONNECTED state.
  • the term “access category (AC) ” used herein refers to a number or an index that can represent a type of traffic for establishing or resuming a connection with the network device, or represent a reason for the access. For example, if the parameters indicate that the AC is “x” , the terminal device 210-1 can select the AC “x” if the BFR is triggered.
  • the parameters can comprise an access identity for the BFR for the data transmission when the terminal device 210-1 is in the non RRC_CONNECTED state.
  • access identity refers to a number or an index that can identify an access to the network device or identify the urgency degree for the access. For example, if the parameters indicate that the AI is “k” , the terminal device 210-1 can select the AI “k” if the BFR is triggered or the access attempt is urgent.
  • the parameters can also comprise a barring factor corresponding to the access category or the access identity for the BFR for the data transmission when the terminal device 210-1 is in the non RRC_CONNECTED state.
  • barring factor refers to a factor associated with a probability of successfully establishing or resuming the connection with the network device.
  • the terminal device 210-1 can determine a resume or RRC establishment cause for the BFR for the data transmission when the terminal device 210-1 is in the non RRC_CONNECTED state. For example, the terminal device 210-1 can add a cause value for the BFR to a set of RRC establishment cause values.
  • the terminal device 210-1 can determine a mapping relation between the AC and the cause value. For example, the terminal device 210-1 can determine the mapping relation between the AC “x” and the cause value. Alternatively or in addition, the terminal device 210-1 can determine a mapping relation between the AI an the cause value. For example, the terminal device 210-1 can determine the mapping relation between the AI “k” and the cause value.
  • the terminal device 210-1 triggers a BFR.
  • beam failure used herein can refer to a situation where a radio link quality between the network device 220 and the terminal device 210-1 is poor.
  • the BFR can be configured per BWP. Alternatively, the BFR can be configured per serving cell.
  • the terminal device 210-1 can receive a reference signal from the network device 220. In this situation, the terminal device 210-1 can determine whether the beam failure has occurred based on the reference signal.
  • a reference signal used to detect a beam failure can be defined as a beam failure detection RS (BFD-RS) . For example, if the received power of the reference signal is below a threshold power, the terminal device 210-1 can determine that the beam failure occurs. Alternatively, if the terminal device 210-1 cannot receive the reference signal, the terminal device 210-1 can determine that the beam failure occurs.
  • the terminal device 210-1 can measure a radio link quality of the channel using the BFD-RS. The radio link quality can be a hypothetical block error rate (BLER) .
  • BLER block error rate
  • the terminal device 210-1 can determine that the radio link of the corresponding beam is disconnected and the beam failure occurs.
  • the threshold Q out_LR may be an out-of-synchronization threshold used in radio link monitoring (RLM) .
  • the reference signal can comprise a channel state information reference signal (CSI-RS) .
  • the reference signal can comprise a demodulation-reference signal (DM-RS) .
  • the reference signal can comprises a phasing tracing reference signal (PT-RS) .
  • the reference signal can also comprise a cell-specific reference signal (CRS) .
  • the terminal device 210-1 can receive a synchronization signal (SS) block from the network device 220. In this situation, the terminal device 210-1 can determine whether the beam failure has occurred based on the SS block. For example, if the received power of the SS block is below a threshold power, the terminal device 210-1 can determine that the beam failure occurs. Alternatively, if the terminal device 210-1 cannot receive the SS block, the terminal device 210-1 can determine that the beam failure occurs. In some embodiments, the terminal device 210-1 can receive a physical broadcast channel (PBCH) block from the network device 220. In this situation, the terminal device 210-1 can determine whether the beam failure has occurred based on the PBCH block.
  • PBCH physical broadcast channel
  • the terminal device 210-1 can determine that the beam failure occurs. Alternatively, if the terminal device 210-1 cannot receive the PBCH block, the terminal device 210-1 can determine that the beam failure occurs.
  • the beam failure can be determined based on several measurement results.
  • the terminal device 210-1 can determine that one beam failure instance has occurred.
  • the occurrence of the beam failure instance can be determined by a physical (PHY) layer or a medium access control (MAC) layer at the terminal device 210-1.
  • the MAC layer can determine that a beam failure has occurred if beam failure instances have occurred more than a preconfigured number of times.
  • the PHY layer can recognize whether the beam failure instance has occurred or not based on the measurement result of the radio link quality, and report to the MAC layer information related to the beam failure instance.
  • the information can indicate that the beam failure instance has occurred, indicate the measurement result of the radio link quality, and/or indicate an index of the beam.
  • the information related to the beam failure instance can be referred to as “instance information” .
  • the instance information can be periodically reported from the PHY layer to the MAC layer. For example, if the beam failure instance has occurred, the PHY layer can transmit the instance information to the MAC layer. When the beam failure instance has not occurred, the PHY layer cannot transmit the instance information to the MAC layer.
  • the MAC layer can have a timer and a counter to determine the occurrence of the beam failure.
  • the timer can be used to reset the counter, and the counter can be used to count the number of beam failure instances. If the timer expires, the counter can be reset, for example, reset to “0” .
  • the MAC layer can determine that a beam failure has occurred when the incremented counter reaches a preconfigured value.
  • the terminal device 210-1 can search for candidate beam (s) when the beam failure is detected.
  • the candidate beam step can be determined after or before the beam failure detection step.
  • the candidate beam may be determined together with the beam failure detection step.
  • the terminal device 210-1 can determine whether a RRC resume request for the BFR is allowed.
  • the RRC resume request can be called “access attempt. ”
  • the terminal device 210-1 can select the AC for the BFR.
  • the terminal device 210-1 can determine the barring factor according to the AC and determine that the access attempt is allowed based on the barring factor.
  • the terminal device 210-1 can randomly generate a number associated with the barring factor and if the number is lower than a value configured by the network device 220, the access attempt is allowed. Only as an example, the terminal device 210-1 can draw a random number “rand” which is uniformly distributed in the range from 0 to 1. If the random number “rand” is lower than the value indicated by the barring factor, the terminal device 210-1 can determine that the access attempt is allowed.
  • the NAS of the terminal device 210-1 can determine the AI.
  • the NAS of the terminal device 210-1 can determine one or more AIs.
  • the terminal device 210-1 can select one or more AIs when the BFR is triggered.
  • the terminal device 210-1 can determine the barring factor according to the AI and determine that the access attempt is allowed based on the barring factor or indication for the AI contained in "UAC barring parameter" . For example, if for at least one of these Access Identities the corresponding bit in the uac-BarringForAccessIdentity contained in "UAC barring parameter" is set to zero, the terminal device 210-1 can determine that the access attempt is allowed.
  • the terminal device 210-1 can determine that the access attempt for the BFR is allowed.
  • the terminal device 210-1 is configured with a random access channel (RACH) resource for the data transmission when the terminal device 210-1 is in the non RRC_CONNECTED state, the terminal device 210-1 can determine that the access attempt for the BFR is allowed.
  • RACH random access channel
  • the terminal device 2210-1 is configured with a dedicated RACH resource, the terminal device 210-1 can determine that the access attempt for the BFR is allowed.
  • the terminal device 210-1 can generate information related to the beam failure.
  • the information can comprise the cause value for the BFR.
  • the information can comprise a beam index of a failed beam on which the beam failure occurs.
  • the information can also comprise a SSB index on the failed beam.
  • the information can comprise a PBCH block index on the failed beam.
  • the information can comprise a CSI-RS index on the failed beam.
  • the information can comprise an index relating to an uplink resource corresponding to the failed beam.
  • the index related to the uplink resource can comprise a bandwidth part (BWP) index.
  • the index related to the uplink resource can comprise a physical random access control (PRACH) configuration index.
  • PRACH physical random access control
  • the index related to the uplink resource can also comprise a RACH occasion index.
  • the index related to the uplink resource can comprise a random access message physical uplink shared channel (PUSCH) index.
  • PUSCH physical uplink shared channel
  • the index related to the uplink resource can comprise a message A PUSCH index.
  • messages A refers to a message where the terminal device transmits to the network device during 2 step RACH procedure.
  • the index related to the uplink resource can comprise a message 3 PUSCH index.
  • the term “message 3” refers to a message where the terminal device transmits to the network device during 4 step RACH procedure.
  • the terminal device 210-1 can determine a candidate beam for the BFR.
  • the information related to the beam failure can also indicate the candidate beam for the BFR which the beam quality is good enough.
  • the information can comprise a beam index of the candidate beam.
  • the information can also comprise a SSB index on the candidate beam.
  • the information can comprise a PBCH block index on the candidate beam.
  • the information can comprise a CSI-RS index on the candidate beam.
  • the information can comprise an index relating to an uplink resource corresponding to the candidate beam.
  • the index related to the uplink resource can comprise a bandwidth part (BWP) index.
  • BWP bandwidth part
  • the index related to the uplink resource can comprise a physical random access control (PRACH) configuration index.
  • the index related to the uplink resource can also comprise a RACH occasion index.
  • the index related to the uplink resource can comprise a MsgA physical uplink shared channel (PUSCH) index for the data transmission in the non RRC_CONNECTED state.
  • the MsgA PUSCH index can indicate MsgA PUSCH group A.
  • the MsgA PUSCH index can indicate MsgA PUSCH group B.
  • the term “MsgA PUSCH group A” and the term “MsgA PUSCH group B” can refer to two groups of random preamble for contention.
  • the Msg A PUSCH index can indicate the MsgA PUSCH group A.
  • the Msg A PUSCH index can indicate the MsgA PUSCH group B.
  • the terminal device 210-1 identifies a resource for transmitting the BFR.
  • the resource can be configured for the data transmission when the terminal device 210-1 is in the non RRC_CONNECTED state.
  • the terminal device 210-1 can select the resource from a set of resources configured for the data transmission when the terminal device 210-1 is in the non RRC_CONNECTED state.
  • the terminal device 210-1 can select the resource from the set of CG resources, for example the SDT resources. In this case, the terminal device 210-1 can initialize CG based data transmission.
  • the terminal device 210-1 can select the resource from the set of PRACH resources, for example the SDT resources. In this situation, the terminal device 210-1 can initialize RACH based data transmission.
  • the terminal device 210-1 can select the resource from the set of RACH resources. In this case, the terminal device 210-1 can initialize RACH. For example, if the BFR has been triggered for a while or less than a time duration, the terminal device 210-1 can resume the RRC connection by the RACH procedure.
  • the priority for selecting the resource from the set of CG resources is higher than the priority for selecting the resource from the set of resources for the RACH based data transmission in the non RRC_CONNECTED.
  • the terminal device 210-1 can select the resource from the set of CG resources first. In a situation where the CG based data transmission cannot be initialized, the terminal device 210-1 can select the resource from the set of resources for the RACH based data transmission in the non RRC_CONNECTED or the set of RACH resources.
  • the priority for selecting the resource from the set of resources for the RACH based data transmission in the non RRC_CONNECTED is higher than the priority for selecting the resource from the set of resources for the legacy RACH procedure without data transmission in the UL resource.
  • the terminal device 210-1 can select the resource from the set of resources for the RACH based data transmission in the non RRC_CONNECTED state.
  • the terminal device 210-1 can select the resource from the set of resources for the legacy RACH procedure without data transmission in the UL resource. It should be noted that the terminal device 210-1 can identify the resource which is configured for data transmission when the terminal device 210-1 is in RRC_CONNECTED state.
  • the terminal device 210-1 transmits the information related to the beam failure to the network device 220 via the resource as identified.
  • the information related to the beam failure can be transmitted with SDT.
  • the information related to the beam failure can be transmitted without SDT including transmitted on the resources configured to SDT without transmitting the small data and transmitted on the RACH resources which are not configured to SDT.
  • the information related to the beam failure can be transmitted in a MAC CE.
  • Each bit of the MAC CE can represent a beam state of a resource which configured for the data transmission in the non RRC_CONNECTED state. If there is no resource mapping to the corresponding field of the MAC CE, the corresponding field can be ignored.
  • the MAC CE can be transmitted with a corresponding logical channel identifier (LCID) .
  • LCID logical channel identifier
  • a new LCID can be used to indicate the MAC CE of the beam failure.
  • the LCID can comprise a subheader of the MAC CE, which means content of the beam failure may not be included.
  • the information related to the beam failure can be transmitted via a signaling.
  • the terminal device 210-1 can multiplex the information related to the beam failure with other messages into a MAC protocol data unit (PDU) .
  • PDU MAC protocol data unit
  • logical channels for different messages can have different priorities.
  • the BFR for SDT MAC CE and the BFR for SDT signaling have the same priority.
  • the BFR for SDT has the same priority with the BFR MAC CE which is used in RRC_CONNECTED state.
  • the BFR for SDT can have higher priority than Sidelink Configured Grant Confirmation MAC CE or listen-before-talk failure MAC CE.
  • the BFR for SDT can have lower priority than cell radio network temporary identity (C-RNTI) MAC CE or data from uplink common control channel (UL-CCCH) .
  • C-RNTI cell radio network temporary identity
  • UL-CCCH uplink common control channel
  • the priority of the BFR for SDT can be higher than data from UL-CCCH
  • Fig. 6 illustrates a flowchart of an example method 600 according to some embodiments of the present disclosure.
  • the method 500 can be performed by the network device 220-1 shown in Fig. 2. It is to be understood that the method 600 can include additional blocks not shown and/or can omit some blocks as shown, and the scope of the present disclosure is not limited in this regard. For the purpose of discussion, the method 600 will be described from the perspective of the network device 220-1 with reference to Fig. 2.
  • the network device 220 can transmit 3005 parameters related to a unified access control (UAC) configuration to the terminal device 210-1.
  • UAC unified access control
  • the term “UAC” used herein refer to a set of mechanism to determine whether to allow the terminal device for a specific service or state change. UAC can get many factors involved at each point of determining whether to allow the terminal device for the specific service or state change.
  • the parameters can be transmitted in a system broadcast message. Alternatively, the parameters can be transmitted in a RRC release message. In other embodiments, the network device 220 can transmit the parameters in a RRC configuration message or a RRC reconfiguration message. It should be noted that embodiments of the present disclosure can be applied to cases where the UAC is not applied.
  • the parameters can comprise an access category (AC) for a report triggered by a layer lower than RRC layer for a data transmission in the non RRC_CONNECTED state.
  • access category (AC) used herein refers to a number or an index that can represent a type of traffic for establishing or resuming a connection with the network device, or represent a reason for the access.
  • the parameters can comprise an access identity for the report triggered by a layer lower than RRC layer for a data transmission in the non RRC_CONNECTED state.
  • access identity refers to a number or an index that can identify an access to the network device or identify the urgency degree for the access.
  • the parameters can also comprise a barring factor corresponding to the access category or the access identity for the BFR for the data transmission when the terminal device 210-1 is in the non RRC_CONNECTED state.
  • barring factor refers to a factor associated with a probability of successfully establishing or resuming the connection with the network device.
  • the network device 220 receives information at least indicating a presence of a beam failure in a non RRC_CONNECTED state, from the terminal device 210-1.
  • the information can comprise the cause value for the BFR.
  • the information can comprise a beam index of a failed beam on which the beam failure occurs.
  • the information can also comprise a SSB index on the failed beam.
  • the information can comprise a PBCH block index on the failed beam.
  • the information can comprise a CSI-RS index on the failed beam.
  • the information can comprise an index relating to an uplink resource corresponding to the failed beam.
  • the index related to the uplink resource can comprise a bandwidth part (BWP) index.
  • BWP bandwidth part
  • the index related to the uplink resource can comprise a physical random access control (PRACH) configuration index.
  • the index related to the uplink resource can also comprise a RACH occasion index.
  • the index related to the uplink resource can comprise a MsgA physical uplink shared channel (PUSCH) index.
  • Msg A refers to a message where the terminal device transmits to the network device during 2 step RACH procedure.
  • the MsgA PUSCH index can indicate MsgA PUSCH group A.
  • the MsgA PUSCH index can indicate MsgA PUSCH group B.
  • MsgA PUSCH group A and the term “MsgA PUSCH group B” can refer to two groups of random preamble for contention. If the size of the Msage A is below a threshold size, the Msg A PUSCH index can indicate the MsgA PUSCH group A. Alternatively, if the he size of the Msage A exceeds the threshold size, the Msg A PUSCH index can indicate the MsgA PUSCH group B. In other embodiments, the index related to the uplink resource can comprise a message 3 physical uplink shared channel (PUSCH) index.
  • PUSCH physical uplink shared channel
  • the terminal device 210-1 can determine a candidate beam for the BFR.
  • the information related to the beam failure can also indicate the candidate beam for the BFR.
  • the information can comprise a beam index of the candidate beam.
  • the information can also comprise a SSB index on the candidate beam.
  • the information can comprise a PBCH block index on the candidate beam.
  • the information can comprise a CSI-RS index on the candidate beam.
  • the information can comprise an index relating to an uplink resource corresponding to the candidate beam.
  • the index related to the uplink resource can comprise a bandwidth part (BWP) index.
  • the index related to the uplink resource can comprise a physical random access control (PRACH) configuration index.
  • PRACH physical random access control
  • the index related to the uplink resource can also comprise a RACH occasion index.
  • the index related to the uplink resource can comprise a message A physical uplink shared channel (PUSCH) index.
  • the network device 220 transmits configuration information related to the BFR.
  • the network device 220 can reconfigure a beam for the terminal device 210-1.
  • the network device 220 can reconfigure the resource for SDT with the candidate beam indicated the information related in the beam failure.
  • the configuration information can indicate an index of the candidate beam.
  • the index of the candidate beam can be similar as those in the information related to the beam failure.
  • the network device 220 may not reconfigure a beam for the terminal device 210-1.
  • the configuration information can comprise an acknowledgment to the information related to the beam failure. In this case, if the terminal device 210-1 receives the acknowledgment successfully, it means that the failed beam has been recovered.
  • Fig. 7 is a simplified block diagram of an apparatus 700 that is suitable for implementing embodiments of the present disclosure.
  • the apparatus 700 can be considered as a further example implementation of the terminal device 210 as shown in Fig. 2. Accordingly, the apparatus 700 can be implemented at or as at least a part of the terminal device 210.
  • the apparatus 700 includes a processor 710, a memory 720 coupled to the processor 710, a suitable transmitter (TX) and receiver (RX) 740 coupled to the processor 710.
  • the memory 710 stores at least a part of a program 730.
  • the TX/RX 740 is for bidirectional communications.
  • the TX/RX 740 is coupled to at least one antenna to facilitate communication, though, in practice, an Access Node mentioned in this application can have several antennas.
  • the communication interface can 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.
  • a program 730 is assumed to include program instructions that, when executed by the associated processor 710, enable the apparatus 700 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to Figs. 3-6.
  • the embodiments herein can be implemented by computer software executable by the processor 710 of the apparatus 700, or by hardware, or by a combination of software and hardware.
  • the processor 710 can be configured to implement various embodiments of the present disclosure.
  • a combination of the processor 710 and memory 710 can form processing means 750 adapted to implement various embodiments of the present disclosure.
  • the memory 710 can be of any type suitable to the local technical network and can 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 710 is shown in the apparatus 700, there can be several physically distinct memory modules in the apparatus 700.
  • the processor 710 can be of any type suitable to the local technical network, and can 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 apparatus 700 can have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • a method performed by a terminal device, a non Radio Resource Control (RRC) _CONNECTED state with a network device comprising: triggering a beam failure recovery (BFR) while the terminal device is in the non RRC_CONNECTED state with a network device, in response to a presence of a beam failure; identifying a resource for transmitting information relating to the beam failure to the network device; and transmitting information relating to the beam failure to the network device via the resource as identified.
  • RRC Radio Resource Control
  • the method further comprises receiving, from the network device, parameters related to a unified access control configuration comprising at least one of: an access category for a report triggered by a layer lower than RRC layer for data transmission in the non RRC_CONNECTED state with the network device, an access identity for the report triggered by a layer lower than RRC layer for data transmission in the non RRC_CONNECTED state with the network device, or a barring factor corresponding to at least one of: the access category or the access identity.
  • parameters related to a unified access control configuration comprising at least one of: an access category for a report triggered by a layer lower than RRC layer for data transmission in the non RRC_CONNECTED state with the network device, an access identity for the report triggered by a layer lower than RRC layer for data transmission in the non RRC_CONNECTED state with the network device, or a barring factor corresponding to at least one of: the access category or the access identity.
  • the method further comprises determining an access category for the BFR for the data transmission in the non RRC_CONNECTED state with the network device; determining a resume cause value for the BFR for the data transmission in the non RRC_CONNECTED state with the network device based on the access category; and adding the resume cause value to the information relating to the beam failure.
  • the method further comprises determining an access identity for the BFR for the data transmission in the non RRC_CONNECTED state with the network device; determining a resume cause value for the BFR for the data transmission in the non RRC_CONNECTED state with the network device based on the access identity; and adding the resume cause value to the information relating to the beam failure.
  • the method further comprises in accordance with a determination that the unified access control configuration indicates that the terminal device is configured with a configured grant (CG) uplink resource, determining an access attempt for the BFR for the data transmission in the non RRC_CONNECTED state as allowed.
  • CG configured grant
  • the method further comprises in accordance with a determination that the unified access control configuration indicates that the terminal device is configured with a random access channel (RACH) resource for the small data transmission or a dedicated RACH resource, determining an access attempt for the BFR for the data transmission in the non RRC_CONNECTED state with the network device as allowed.
  • RACH random access channel
  • the method further comprises generating the information comprising at least one of the following to indicate the failed beam: a beam index of the failed beam, a synchronization signal and physical broadcast channel (PBCH) block (SSB) index on the failed beam, a channel state information reference signal (CSI-RS) index on the failed beam, a reference signal identity on the failed beam, or an index relating to an uplink resource corresponding to the failed beam.
  • PBCH physical broadcast channel
  • SSB physical broadcast channel
  • CSI-RS channel state information reference signal
  • the index of the uplink resource comprises one of: a bandwidth part (BWP) index, a physical random access control (PRACH) configuration index, a RACH occasion index, or a random access message physical uplink shared channel index.
  • BWP bandwidth part
  • PRACH physical random access control
  • the method further comprises generating the information comprising at least one of the following to indicate a candidate beam for the BFR: a beam index of the candidate beam, a synchronization signal and physical broadcast channel (PBCH) block (SSB) index on the candidate beam, a channel state information reference signal (CSI-RS) index on the candidate beam, a reference signal identity on the candidate beam, or an index of an uplink resource corresponding to the candidate beam.
  • PBCH physical broadcast channel
  • CSI-RS channel state information reference signal
  • identifying the resource for transmitting the information comprises: selecting the resource from a set of resources configured for the small data transmission.
  • transmitting the information comprises: generating a medium access control (MAC) packet data unit (PDU) ; and transmitting the information in the MAC PDU.
  • MAC medium access control
  • PDU packet data unit
  • transmitting the information comprises: transmitting the information on the resource without small data transmission.
  • identifying the resource for transmitting the information comprises: selecting the resource from one of: a first set of configured grant (CG) resources configured for the small data transmission, a second set of resources configured for random access channel (RACH) based data transmission in the non RRC_CONNECTED state with the network device, or a third set of resources for RACH procedure without data transmission.
  • CG configured grant
  • RACH random access channel
  • a first priority for selecting the resource from the first set of CG resources is higher than a second priority for selecting the resource from the second set of resources, and the second priority is higher than a third priority for selecting the resource from the third set of resources.
  • selecting the resource comprises: randomly selecting the resource from one of: the first set of CG resources, he second set of RACH resources, or the third set of RACH resources; or selecting an earliest available resource from one of the following to be the resource: the first set of CG resources, the second set of RACH resources, or the third set of RACH resources.
  • transmitting the information comprises: transmitting the information in one of: a medium access control (MAC) control element (CE) , a radio resource control (RRC) message, or an uplink control information (UCI) indication.
  • MAC medium access control
  • CE control element
  • RRC radio resource control
  • UCI uplink control information
  • a method performed by a network device comprising: receiving, from a terminal device, information at least indicating a presence of a beam failure for data transmission in a non RRC_CONNECTED state with the network device; and transmitting, to the terminal device while the terminal device is in the non RRC-CONNECTED state with the network device, configuration information relating to a beam failure recovery (BFR) .
  • BFR beam failure recovery
  • the method further comprises transmitting, to the terminal device, parameters related to a unified access control configuration comprising at least one of: an access category for a report triggered by a layer lower than RRC layer for data transmission in the non RRC_CONNECTED state with the network device, an access identity for the report triggered by a layer lower than RRC layer for the data transmission in the non RRC_CONNECTED state with the network device, or a barring factor corresponding to at least one of: the access category or the access identity.
  • parameters related to a unified access control configuration comprising at least one of: an access category for a report triggered by a layer lower than RRC layer for data transmission in the non RRC_CONNECTED state with the network device, an access identity for the report triggered by a layer lower than RRC layer for the data transmission in the non RRC_CONNECTED state with the network device, or a barring factor corresponding to at least one of: the access category or the access identity.
  • receiving the information comprise: receiving the information comprising at least one of the following to indicate the failed beam: a beam index of the failed beam, a synchronization signal and physical broadcast channel (PBCH) block (SSB) index on the failed beam, a channel state information reference signal (CSI-RS) index on the failed beam, a reference signal identity on the failed beam, or an index relating to an uplink resource corresponding to the failed beam.
  • PBCH physical broadcast channel
  • SSB physical broadcast channel
  • CSI-RS channel state information reference signal
  • the index of the uplink resource comprises one of: a bandwidth part (BWP) index, a physical random access control (PRACH) configuration index, a RACH occasion index, or an random access message physical uplink shared channel index.
  • BWP bandwidth part
  • PRACH physical random access control
  • receiving the information comprise: receiving the information comprising at least one of the following to indicate a candidate beam for the BFR: a beam index of the candidate beam, a synchronization signal and physical broadcast channel (PBCH) block (SSB) index on the candidate beam, a channel state information reference signal (CSI-RS) index on the candidate beam, a reference signal identity on the candidate beam, or an index of an uplink resource corresponding to the candidate beam.
  • PBCH physical broadcast channel
  • CSI-RS channel state information reference signal
  • receiving the information comprises: receiving the information in a medium access control (MAC) packet data unit (PDU) .
  • MAC medium access control
  • PDU packet data unit
  • receiving the information comprises: receiving the information without small data transmission.
  • receiving the information comprises: receiving the information in one of: a medium access control (MAC) control element (CE) , a radio resource control (RRC) message, or an uplink control information (UCI) indication.
  • MAC medium access control
  • CE control element
  • RRC radio resource control
  • UCI uplink control information
  • various embodiments of the present disclosure can be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software which can 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 can 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. 3-6.
  • 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 can be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules can be executed within a local or distributed device. In a distributed device, program modules can be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure can be written in any combination of one or more programming languages. These program codes can 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 can 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 can be embodied on a machine readable medium, which can be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • the machine readable medium can be a machine readable signal medium or a machine readable storage medium.
  • a machine readable medium can 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.
  • any combination of A, B, C includes the combinations of: A and B, A and C, B and C, and A and B and C can each be present in an embodiment.

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 la détection de défaillance de faisceau ou la récupération après défaillance de faisceau lorsqu'un dispositif terminal est dans un état non connecté de commande de ressources radio (RRC). Le procédé comporte le déclenchement d'une récupération après défaillance de faisceau (BFR) pendant que le dispositif terminal est dans l'état non RRC_CONNECTÉ, en réponse à la présence d'une défaillance de faisceau. Le procédé comporte également l'identification d'une ressource pour transmettre des informations concernant la défaillance de faisceau à un dispositif de réseau. Le procédé comporte en outre la transmission d'informations concernant la défaillance de faisceau au dispositif de réseau par l'intermédiaire de la ressource identifiée.
PCT/CN2021/071344 2021-01-12 2021-01-12 Mécanisme de récupération après défaillance de faisceau WO2022150994A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/071344 WO2022150994A1 (fr) 2021-01-12 2021-01-12 Mécanisme de récupération après défaillance de faisceau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/071344 WO2022150994A1 (fr) 2021-01-12 2021-01-12 Mécanisme de récupération après défaillance de faisceau

Publications (1)

Publication Number Publication Date
WO2022150994A1 true WO2022150994A1 (fr) 2022-07-21

Family

ID=82446407

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/071344 WO2022150994A1 (fr) 2021-01-12 2021-01-12 Mécanisme de récupération après défaillance de faisceau

Country Status (1)

Country Link
WO (1) WO2022150994A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110999444A (zh) * 2017-07-25 2020-04-10 Lg电子株式会社 用于选择载波的方法和支持该方法的设备
US20200196216A1 (en) * 2017-07-24 2020-06-18 Electronics And Telecommunications Research Institute Method and device for triggering beam failure recovery procedure of multibeam system
WO2020132284A1 (fr) * 2018-12-21 2020-06-25 Idac Holdings, Inc. Procédures pour permettre une transmission simultanée de différents types

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200196216A1 (en) * 2017-07-24 2020-06-18 Electronics And Telecommunications Research Institute Method and device for triggering beam failure recovery procedure of multibeam system
CN110999444A (zh) * 2017-07-25 2020-04-10 Lg电子株式会社 用于选择载波的方法和支持该方法的设备
WO2020132284A1 (fr) * 2018-12-21 2020-06-25 Idac Holdings, Inc. Procédures pour permettre une transmission simultanée de différents types

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LENOVO, MOTOROLA MOBILITY: "Discussion of beam recovery procedure", 3GPP DRAFT; R1-1710596, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Qingdao, P.R. China; 20170627 - 20170630, 26 June 2017 (2017-06-26), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051299803 *

Similar Documents

Publication Publication Date Title
CN112119597B (zh) 波束失败确定方法、装置、设备及存储介质
KR101642896B1 (ko) ＴＡ（Ｔｉｍｉｎｇ Ａｄｖａｎｃｅ） 그룹의 결정
RU2759701C2 (ru) Способ и устройство для отчёта о результатах измерений
US11252688B2 (en) Beam-specific and non-beam-specific synchronization signal block positions for wireless networks
US20120275390A1 (en) Cross-Carrier Preamble Responses
US20150146635A1 (en) Timing Advance Management in the Presence of Repeaters and Remote Radio Heads
WO2020029173A1 (fr) Procédé, dispositif et support lisible par ordinateur destiné à un accès aléatoire
EP4098068B1 (fr) Indication précoce pour dispositifs à capacité réduite
US20220279395A1 (en) Early data transmission for dual connectivity or carrier aggregation
EP4175397A1 (fr) Demande de planification et déclenchement d'accès aléatoire pour sdt
US20240064801A1 (en) Methods, apparatuses, and media for indicating listen before talk failure
WO2022226741A1 (fr) Mécanisme de distribution d'informations de faisceau
US20210136833A1 (en) Random access method and data reception method, apparatuses thereof and communication system
WO2022150994A1 (fr) Mécanisme de récupération après défaillance de faisceau
WO2021102837A1 (fr) Procédés, dispositifs et support pour la communication
KR20230110620A (ko) 비활성 모드의 장치에 대한 빔 관리
CN116508391A (zh) 失败取消记录
WO2020154855A1 (fr) Amélioration de la mobilité d'un dispositif terminal
WO2021203386A1 (fr) Rapport d'événement pour reprise après défaillance de faisceau
WO2023240484A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2023205996A1 (fr) Communication pour relais de liaison latérale
WO2022205282A1 (fr) Procédés, dispositifs et supports de stockage informatiques pour la communication
WO2023044822A1 (fr) Mise à jour de paramètre en vue d'une tentative de reprise de connexion
WO2021243708A1 (fr) Optimisation de mesure de csi-rs
WO2019192011A1 (fr) Configuration de sauvegarde dans une procédure d'accès aléatoire

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 31.10.2023)

122 Ep: pct application non-entry in european phase

Ref document number: 21918212

Country of ref document: EP

Kind code of ref document: A1