WO2023031791A1

WO2023031791A1 - Methods and apparatus of beam status detection

Info

Publication number: WO2023031791A1
Application number: PCT/IB2022/058123
Authority: WO
Inventors: Li Guo
Original assignee: Guangdong Oppo Mobile Telecommunications Corp., Ltd.
Priority date: 2021-09-01
Filing date: 2022-08-30
Publication date: 2023-03-09

Abstract

Methods and apparatus of beam status detection. A communication system (100) can use a media access control message to indicate a terminal device (120) one or more channel state information reference signal resource as beam failure detection reference signals. The terminal device (120) can derive the beam failure detection reference signal(s) according to the transmission configuration indicator states configured to a control resource set.

Description

METHODS AND APPARATUS OF BEAM STATUS DETECTION

CROSS-REFERENCE TO RELATED APPLICATION(S)

[0001] This application claims the benefit of U.S. Provisional Patent Application Serial No. 63/239,740, filed September 1 , 2022, which is incorporated by reference herein in its entirety.

TECHNICAL FIELD

[0002] This application relates to the communications field, and more specifically, to a wireless communications method and device.

BACKGROUND

[0003] Rapid growth in computing technology is creating a greater demand for data communication. The increasing demand in turn drives further growth in communication technology. One such technological advance corresponds to multipoint point communications that leverage multiple points/devices to communicate with one device. However, the rapid growth is further increasing demands for higher throughput, which requires additional coordination between the multiple communication points and the corresponding complications.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] To describe the technical solutions in the implementations of the present technology more clearly, the following briefly describes the accompanying drawings. The accompanying drawings show merely some aspects or implementations of the present technology, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts.

[0005] FIG. 1 illustrates a wireless communication system in accordance with one or more implementations of the present technology. [0006] FIG. 2 illustrates an example multipoint communication scheme in accordance with one or more implementations of the present technology.

[0007] FIGS. 3A and 3B illustrate example multipoint coordination schemes in accordance with one or more implementations of the present technology.

[0008] FIG. 4A illustrates a flowchart of an example method of deriving a beam failure detection reference signal, in accordance with one or more implementations of the present technology.

[0009] FIG. 4B illustrates a flowchart of an example method of providing a beam failure detection reference signal, in accordance with one or more implementations of the present technology.

[0010] FIG. 5 illustrates a schematic block diagram of a terminal device in accordance with one or more implementations of the present disclosure.

[0011] FIG. 6 illustrates is a schematic block diagram of a system chip in accordance with one or more implementations of the present disclosure.

[0012] FIG. 7 illustrates a schematic block diagram of a communications device in accordance with one or more implementations of the present disclosure.

DETAILED DESCRIPTION

[0013] The following describes the technical solutions in the one or more implementations of the present technology. A wireless communication system can coordinate and configure multipoint joint communications to/from terminal devices. For example, the system can include multiple transmission-reception points (TRPs) that are connected to each other through backhaul links (e.g., ideal type or non-ideal type) for coordination. A TRP can communicate with a terminal device regarding a beam status (e.g., failure) detection and response (e.g., recovery).

[0014] Conventional methods only support a beam failure recovery function for a single TRP case. Beam failure is only detected when all the physical downlink control channels (PDCCHs) meet a beam failure threshold. Conventional systems use radio resource control (RRC) signaling to provide a beam failure detection reference signal. However, conventional schemes cannot overcome the challenges caused by the transmission configuration indicator (TCI) state of a PDCCH being switched through a media access control (MAC) control element (CE) message. Additionally, the TCI state of a PDCCH can be switched by DCI signaling. As such, conventional systems cannot update the beam failure detection reference signal in sufficient time, which results in the user equipment (UE) using the wrong reference signal to detect beam failure. Thus, the UE can identify the erroneous beam failure.

[0015] In contrast to the conventional methods, implementations of the present technology include one or more mechanisms for configuring or indicating a beam failure detection reference signal. The system, via a TRP, can use a MAC CE message to indicate, to a terminal device, one or more faster/lower-level signals (e.g., channel state information reference signal (CSI-RS) resources) as beam failure detection reference signals. The TRP can use a MAC CE message to provide a set of periodic CSI-RS resource configuration indexes as the beam failure detection reference signals.

[0016] The system can configure a terminal device with one or more control resource sets (CORESETs) in the active bandwidth part (BWP) of a serving cell. The terminal device can operate beam failure recovery in the active BWP of the serving cell. For a CORESET, a TRP can provide the terminal device with two TCI states. In some implementations, a TRP does not provide the configuration of a beam failure detection reference signal set to the terminal device. The terminal device can derive the beam failure detection reference signal(s) according to the TCI states configured to the CORESETs in the active BWP of the serving cell.

[0017] Accordingly, the various implementations of the present technology can enable the communication system to update the beam failure detection reference signal with low latency so that the terminal device can use the correct CSI-RS resource to detect a beam failure of the PDCCH link. Thus, the performance of beam failure recovery function is improved over conventional systems.

[0018] In the following description, numerous specific details are set forth to provide a thorough understanding of the presently described technology. In other implementations, the techniques introduced here can be practiced without these specific details. In other instances, well-known features, such as specific functions or routines, are not described in detail in order to avoid unnecessarily obscuring the present technology. References in this description to "an implementation," "one implementation," or the like mean that a particular feature, structure, material, or characteristic being described is included in at least one implementation of the described technology. Thus, the appearances of such phrases in this specification do not necessarily all refer to the same implementation. On the other hand, such references are not necessarily mutually exclusive either. Furthermore, the particular features, structures, materials, or characteristics can be combined in any suitable manner in one or more implementations. It is to be understood that the various implementations shown in the figures are merely illustrative representations and are not necessarily drawn to scale.

[0019] Several details describing structures or processes that are well-known and often associated with communication systems and subsystems, but that can unnecessarily obscure some significant aspects of the disclosed techniques, are not set forth in the following description for purposes of clarity. Moreover, although the following disclosure sets forth several implementations of different aspects of the present technology, several other implementations can have different configurations or different components than those described in this section. Accordingly, the disclosed techniques can have other implementations with additional elements or without several of the elements described below.

[0020] Many implementations or aspects of the technology described below can take the form of computer- or processor-executable instructions, including routines executed by a programmable computer or processor. Those skilled in the relevant art will appreciate that the described techniques can be practiced on computer or processor systems other than those shown and described below. The techniques described herein can be implemented in a special-purpose computer or data processor that is specifically programmed, configured, or constructed to execute one or more of the computer-executable instructions described below. Accordingly, the terms "computer" and "processor" as generally used herein refer to any data processor. Information handled by these computers and processors can be presented at any suitable display medium, including a liquid crystal display (LCD). Instructions for executing computer- or processor-executable tasks can be stored in or on any suitable computer-readable medium, including hardware, firmware, or a combination of hardware and firmware. Instructions can be contained in any suitable memory device, including, for example, a flash drive and/or other suitable medium.

[0021] The terms "coupled" and "connected," along with their derivatives, can be used herein to describe structural relationships between components. It should be understood that these terms are not intended as synonyms for each other. Rather, in particular implementations, "connected" can be used to indicate that two or more elements are in direct contact with each other. Unless otherwise made apparent in the context, the term "coupled" can be used to indicate that two or more elements are in either direct or indirect (with other intervening elements between them) contact with each other, or that the two or more elements cooperate or interact with each other (e.g., as in a cause-and-effect relationship, such as for signal transmission/reception or for function calls), or both. The term "and/or" in this specification is only an association relationship for describing the associated objects, and indicates that three relationships may exist, for example, A and/or B may indicate the following three cases: A exists separately, both A and B exist, and B exists separately. In addition, the character "/" in this specification generally indicates an "or" relationship between the associated objects.

Suitable Environments

[0022] FIG. 1 illustrates a wireless communication system 100 in accordance with one or more implementations of the present technology. As shown in FIG. 1 , the wireless communication system 100 can include a network device 110. The network device 110 can include circuitry configured to provide communication coverage for a specific geographic area. Some examples of the network device 110 can include: a base transceiver station (Base Transceiver Station, BTS), a NodeB (NodeB, NB), an evolved Node B (eNB or eNodeB), a Next Generation NodeB (gNB or gNode B), a Wireless Fidelity (Wi-Fi) access point (AP). Additional examples of the network device 110 can include a relay station, an access point, an in-vehicle device, a wearable device, and the like. The network device 110 can include other wireless connection devices for communications networks such as: a Global System for Mobile Communications (GSM) network, a Code Division Multiple Access (CDMA) network, a Wideband CDMA (WCDMA) network, a Long-Term Evolution (LTE) network, a cloud radio access network (Cloud Radio Access Network, CRAN), an Institute of Electrical and Electronics Engineers (IEEE) 802.11-based networks (e.g., a WiFi network), an Internet of Things (loT) network, a device-to-device (D2D) network, a next-generation network (e.g., a Fifth Generation (5G) network), a future evolved public land mobile network (Public Land Mobile Network, PLMN), or the like. Optionally, a 5G system or network may be further referred to as a new radio (New Radio, NR) system or network. The network device 110 can further include the TRP.

[0023] Additionally or alternatively, the wireless communication system 100 can include a terminal device 120. The terminal device 120 can be an end-user device configured to facilitate wireless communication. The terminal device 120 can be configured to wirelessly connect to the network device 110 (via, e.g., a wireless channel) according to one or more corresponding communication protocols/standards. The terminal device 120 may be mobile or fixed. The terminal device 120 can be an access terminal, a UE, a user unit, a user station, a mobile site, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communications device, a user agent, or a user apparatus. Some examples of the terminal device 120 can include: a cellular phone, a smart phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (PDA), a handheld device having a wireless communication function, a computing device or another processing device connected to a wireless modem, an in-vehicle device, a wearable device, an loT device, a terminal device in a future 5G network, a terminal device in a future evolved PLMN, or the like.

[0024] Communications between the network device 110 and the terminal device 120 can experience changes as the corresponding signals travel through a medium or a channel between the devices. In other words, a received signal (Y) may be different than a transmitted signal (X) due to the effects (e.g., fading, interferences, Doppler effects, delays, noises, and/or the like) of traversing through a channel (H). [0025] For illustrative purposes, FIG. 1 illustrates the wireless communication system 100 via the network device 110 and the terminal device 120. However, it is understood that the wireless communication system 100 can include additional/other devices, such as additional instances of the network device 110 and/or the terminal device 120, a network controller, a mobility management entity, etc.

Multipoint Joint Communication

[0026] FIG. 2 illustrates an example multipoint communication scheme 200 in accordance with one or more implementations of the present technology. The communication system 100 can use multiple TRPs (e.g., instances of the network device 110, such as gNBs) to communicate with one terminal device 120. For example, a first TRP 202 and a second TRP 204 can be coupled to the terminal device. The first TRP 202 and the second TRP 204 can be coupled to each other via a backhaul link. Accordingly, the multiple TRPs can communicate with each other to coordinate the joint communications with the terminal device 120.

[0027] For context, the backhaul link can be ideal or non-ideal. When the TRPs are connected via an ideal backhaul link, the TRPs can exchange dynamic scheduling information (e.g., regarding physical downlink shared channel (PDSCH) communications) with short latency. As such, the TRPs can leverage the ideal backhaul link to coordinate the downlink transmissions per each transmission. In contrast, when the TRPs are connected via a non-ideal backhaul link, the information exchanged between the TRPs can have a relatively greater latency. As such, the TRPs may coordinate the communications using a semi-static or a static scheme.

[0028] In non-coherent joint transmission, different TRPs can independently use different PDCCHs to schedule the PDSCH transmissions. Each TRP can send one DCI to schedule one PDSCH transmission. Accordingly, the different TRPs can schedule the corresponding PDSCHs in same or different slots. As a result, two different PDSCH transmission from different TRPs can be fully overlapped or partially overlapped in PDSCH resource allocation. To support multi TRP based non-coherent joint transmission, the communication system 100 may request the terminal device 120 to receive PDCCH from multiple TRPs. For each PDSCH transmission, the terminal device 120 can provide feedback information (e.g., a Hybrid ARQ acknowledge (HARQ-ACK)) to the network. In multi TRP transmissions, the terminal device 120 can provide the feedback for each PDSCH transmission to the corresponding TRP. The terminal device 120 may also receive the PDSCH transmission from one TRP and provide the corresponding feedback to another TRP (e.g., a designated TRP).

[0029] FIGS. 3A and 3B illustrate example multipoint coordination schemes 300a and 300b, respectively, in accordance with one or more implementations of the present technology. The coordination schemes 300a and 300b can represent different combinations for the feedbacks described above.

[0030] For the coordination schemes 300a and 300b, the terminal device 120 can receive or establish PDSCHs based on non-coherent joint transmission from the first TRP 202 and the second TRP 204. For example, the first TRP 202 can send a first configuration command (e.g., a DCI1) to schedule the transmission of a first communication (PDSCH1) to the terminal device 120. Also, the second TRP 204 can send a second configuration command (e.g., a DCI2) to schedule the transmission of a second communication (PDSCH2) to the terminal device 120.

[0031] Accordingly, the terminal device 120 can receive and decode the separate configuration commands (e.g., DCI1 and DCI2). The terminal device 120 can use the separate decoding results of the separate configuration commands to receive and decode the corresponding communications (e.g., PDSCH1 and PDSCH2, respectively). In other words, the terminal device 120 can (1) use the decoding results of DCI1 to receive and decode PDSCH1 and (2) use the decoding results of DCI2 to receive and decode PDSCH2.

[0032] In some implementations, the multiple TRPs can use different CORESETs and search spaces to transmit the configuration commands (DCI) for scheduling the communication, such as the PDSCH transmission. As such, the communication system 100 or the network can configure multiple CORESETs and search spaces. Each TRP can be associated with one or more CORESETs and the related search spaces, which can be used to transmit the corresponding configuration command to the terminal device 120. The terminal device 120 can be requested to decode the configuration command in the CORESETs associated with one or more (e.g., either, any, or all) TRPs to obtain the scheduling information.

[0033] The terminal device 120 can provide feedback information, such as using HARQ-ACK/NACK, back to one or more TRPs. The feedback information can describe a quality of the received information (e.g., the PDSCH communication), the corresponding channel, and/or a processing success/failure associated with the received information. For the example scheme 300a, the terminal device 120 can report separate feedback information to each TRP. In other words, the terminal device 120 can report (1 ) a first feedback (ACK/NACK1) to the first TRP 202 and (2) a second feedback (ACK/NACK2) to the second TRP 204. For the example scheme 300b, the terminal device 120 report a common feedback information for both or all communications (e.g., PDSCH1 and PDSCH2) to one/designated TRP. The example scheme 300b can correspond to an ideal backhaul link between the first TRP 202 and the second TRP 204.

[0034] Conventional systems support beam failure recovery function for a single TRP case, where the beam failure occurs when the PDCCHs meet a beam failure metric. This requires the UE to monitor a set of beam failure detection reference signals (e.g., CSI-RS resources or synchronization signal I physical broadcast channel (SS/PBCH) blocks) that correspond to all downlink channels corresponding to one control channel. If all the beam failure detection reference signals meet a beam failure metric, the UE determines a beam failure event for that control channel. The UE reports this event to the TRP through a MAC CE (e.g., for beam failure in a secondary cell (SCell)) or RACH procedure (e.g., for primary secondary cell (PSCell)), which is referred to as a beam failure recovery request (BFRQ). The UE can also report one new beam to the TRP in the BFRQ. If the TRP receives the BFRQ correctly under the conventional methods, the TRP sends a corresponding response to the UE. The TRP switches the beam of the failed PDCCH to the new beam reported by the UE to complete the beam failure recovery procedure. In doing so, the conventional system performs the link recovery. Additionally, conventional systems use RRC signaling (e.g., a signal processed at a relatively higher layer) to provide a beam failure detection reference signal. However, conventional schemes for addressing beam failure experience degraded performances because the TCI state of PDCCH can be switched through MAC CE message and/or DCI signaling (e.g., a relatively lower layer signal. As a result, conventional systems cannot update the beam failure detection reference signal in time due to the higher layer processing delay and/or the mismatch in the processing speeds for the RRC signaling and the lower layer signaling. The untimely update further causes the terminal device to use the wrong reference signal to detect beam failure, resulting in the terminal device reporting an erroneous beam failure.

[0035] In contrast, the communication system 100 (via, e.g., the multipoint communication scheme 200) can use a MAC CE message to indicate a limited and designated set of one or more CSI-RS resources as beam failure detection reference signals. For each CORESET, as an illustrative example, the first TRP 202 and/or the second TRP 204 can indicate, to a terminal device, a TCI state through a MAC CE. The first TRP 202 and/or the second TRP 204 can use the MAC CE to activate one or more TCI states. For each activated TCI state, the first TRP 202 and/or the second TRP 204 can indicate a CSI- RS resource as the beam failure detection reference signal. Accordingly, the first TRP 202 and/or the second TRP 204 can associate a TCI state with a CSI-RS resource for a beam failure detection reference signal, thereby allowing the communication system to update the TCI state for a periodic CSI-RS resource.

Example Operational Flow

[0036] FIG. 4A is a flowchart of an example method 400 of deriving a beam failure detection reference signal, in accordance with one or more implementations of the present technology. The method 400 can be implemented by a system (e.g., the communication system 100 of FIG. 1 and/or one or more devices therein, such as the terminal device 120 of FIG. 1 , the network device 110 of FIG. 1 , the first TRP 202 of FIG. 2, and/or the second TRP 204 of FIG. 2). The method 400 can correspond to one or more of aspects of beam failure detection for the present technology described herein.

[0037] The communication system 100 can configure a terminal device (e.g., terminal device 120 of FIG. 1) with one or more CORESETs in an active BWP of a serving cell. The communication system 100 can configure the terminal device to implement or perform the beam failure recovery in that active BWP in the serving cell. For a CORESET, the communication system 100 can provide the terminal device with two TCI states. In some implementations, the communication system 100 can use a device (e.g., a system/node device) different than a TRP (e.g., the first TRP 202 and/or the second TRP 204) to source or provide the configuration of a beam failure detection reference signal set to the terminal device. At block 402, the terminal device can derive the beam failure detection reference signal(s) according to the TCI state configured to the CORESETs in the active BWP of the serving cell. For a CORESET with two configured TCI states, the terminal device can derive a beam failure detection reference signal according to the TCI states configured to the CORESET.

[0038] In some implementations, the terminal device includes the periodic CSI-RS resource(s) configured as QCL-TypeD reference signals in the TCI states configured to the CORESET. If two periodic CSI-RS resources are included for the CORESET, at block 404, the terminal device can determine a block error rate (BLER) for the CORESET and a beam failure of the CORESET. At block 406, the terminal device can determine the BLER for each of the two CSI-RS resources. The terminal device can determine the BLER for each of the two CSI-RS resources based on the two CSI-RS resources being transmitted with a single frequency network (SFN) mode. In a first example, if the BLER value for each of the two CSI-RS resources is above a threshold, the terminal device can claim beam failure of the CORESET. In a second example, if the BLER value for either of the two CSI-RS resources is above a threshold, the terminal device can claim beam failure of the CORESET.

[0039] FIG. 4B is a flowchart of an example method 450 for providing a beam failure detection reference signal, in accordance with one or more implementations of the present technology. The method 450 can be implemented by a system (e.g., the communication system 100 of FIG. 1 and/or one or more devices therein, such as the terminal device 120 of FIG. 1 , the network device 110 of FIG. 1 , the first TRP 202 of FIG. 2, and/or the second TRP 204 of FIG. 2). The method 450 can correspond to one or more of aspects of beam failure detection described herein. [0040] The communication system 100 can configure a terminal device (e.g., terminal device 120 of FIG. 1) with one or more CORESETs in an active BWP of a serving cell. The communication system 100 can configure the terminal device to operate a beam failure recovery in the active BWP of the serving cell. For a CORESET, the communication system 100 can provide the terminal device with two TCI states.

[0041] The communication system 100 can provide the terminal device with a beam failure detection reference signal set, which includes CSI-RS resources (e.g., K CSI-RS resources) as the beam failure detection reference signal. The configuration of the beam failure detection reference signal set can indicate to the terminal device that a first CSI-RS resource and a second CSI-RS resource, contained in the beam failure detection reference signal set, are associated with each other for beam failure detection. The terminal device can determine the BLER for each of the two CSI-RS resources based on the two CSI-RS resources being transmitted with a SFN mode. Additionally or alternatively, the terminal device can determine the BLER for each of the two CSI-RS resources. In a first example, if the BLER value for each of the two CSI-RS resources is above a threshold, the terminal device can claim beam failure of the CORESET. In a second example, if the BLER value for either of the two CSI-RS resources is above a threshold, the terminal device can claim beam failure of the CORESET.

[0042] The communication system 100 can configure a terminal device to operate a beam failure recovery in one BWP of a serving cell. At block 452, a TRP (e.g., the first TRP 202 and/or the second TRP 204 of FIG. 2) can use a MAC CE message to provide to the terminal device a set of periodic CSI-RS resource configuration indexes as the beam failure detection reference signals. For a primary cell (PCell) or primary and secondary cells (PSCell), the TRP can use a MAC CE message to indicate, to the terminal device, a set of periodic CSI-RS resource configuration indexes as the beam failure detection reference signals. In the MAC CE message, the TRP can indicate a service cell ID, a BWP ID, and/or one or more CSI-RS resource configuration indexes that are used as the beam failure detection reference signal. [0043] For a secondary cell (SCell), the TRP can use a MAC CE message to indicate, to the terminal device, a set of periodic CSI-RS resource configuration indexes as the beam failure detection reference signals. In the MAC CE message, the gNB can indicate a service cell ID, a BWP ID, and/or one or more CSI-RS resource configuration indexes that are used as the beam failure detection reference signal.

[0044] In a serving cell configured with per-TRP beam failure recovery, the TRP can use a MAC CE message to indicate, to the terminal device, a set of periodic CSI-RS resource configuration indexes as the beam failure detection reference signals for a particular TRP. In the MAC CE message, the TRP can indicate a serving cell ID, a BWP ID, an ID (e.g., ID of beam failure detection reference signal set, value of CORESETPoolindex that is associated with the TRP, TRP ID, etc.) to indicate a TRP, and/or one or more CSI-RS resource configuration indexes that are used as the beam failure detection reference signal for beam failure detection of the TRP beam failure recovery.

[0045] At block 454, the TRP can indicate a TCI state for a CORESET and the TCI state can provide a QCL configuration for receiving a PDCCH associated with the CORESET. The TRP can indicate a TCI state to the CORESET and one CSI-RS resource as the beam failure detection reference signal for the corresponding CORESET. The benefit of indicating the TCI state is that the beam failure reference signal for a CORESET can be updated whenever the TCI state of the CORESET is changed. Thus, the beam failure detection reference signal, the TCI state, the QCL configuration, and Tx beam of the CORESET are aligned.

[0046] In a MAC CE command, the TRP can indicate a TCI state to a CORESET and a CSI-RS resource index. The CSI-RS resource index can indicate a CSI-RS resource as the beam failure detection reference signal for the TCI state. If the CSI-RS resource for beam failure detection reference signal is provided, the terminal device can use the indicated CSI-RS resource as beam failure detection reference signal. If the CSI-RS resource for a beam failure detection reference signal is not provided in the MAC CE, the terminal device can use the CSI-RS included in the indicated TCI state as the QCL source for the CORESET as the beam failure detection reference signal. [0047] At block 456, the TRP can provide the terminal device with one or more TCI states that can provide QCL configurations for PDCCH and PDSCH communications. In RRC, the TRP can associate a TCI state with a CSI-RS resource which indicates that the CSI-RS resource is the beam failure detection reference signal associated with the TCI state. If a TCI state is indicated to a CORESET, the terminal device can use the beam failure detection reference signal associated with the indicated TCI state to detect beam failure. In a TCI state, the TRP can provide a CSI-RS resource as the beam failure detection reference signal. In some implementations, the TRP can configure an association between a TCI state and a beam failure detection reference signal (e.g., a CSI-RS resource).

[0048] At block 458, the TRP can activate one or more TCI states for a PDCCH communication through a MAC CE. For each activated TCI state, the TRP can provide a CSI-RS resource as the beam failure detection reference signal corresponding to the TCI state. If a first TCI state is indicated for the reception of a PDCCH, the terminal device can be requested to use the associated beam failure detection reference signal to detect beam failure. In a MAC CE activating TCI state, the TRP can provide a list of TCI states to the terminal device. For each TCI state included in the MAC CE, the TRP can provide a CSI-RS resource index. The CSI-RS resource index can indicate a CSI-RS resource as the beam failure detection reference signal for the TCI state.

[0049] At block 460, the TRP can use a MAC CE to update the TCI state for a periodic CSI-RS resource. The TRP can provide the TCI state for a periodic CSI-RS resource in a RRC. In conventional schemes, if the system needs to update a TCI state for a periodic CSI- RS resource, the TRP uses RRC signaling to reconfigure it, which results in large signaling overhead and large latency. In contrast, in the communication system 100, the TRP can use a MAC CE to indicate a periodic CSI-RS resource and a TCI state. The terminal device can apply the indicated TCI state on the indicated periodic CSI-RS resource 3ms after the ACK communication to the PDSCH carrying that MAC CE. In some implementations, the TRP can use a MAC CE to indicate a periodic CSI-RS resource, a TCI state, and a time length. The time length can indicate the time duration where the terminal devices can apply the indicated TCI state on the indicated periodic CSI-RS resource. Example Devices and Systems

[0050] FIGS. 5-7 illustrate example devices and systems that include or incorporate the dynamic power control mechanism described above. FIG. 5 is a schematic block diagram of a terminal device 500 (e.g., an instance of the terminal device 120 of FIG. 1 ) in accordance with one or more implementations of the present technology. As shown in FIG. 5, the terminal device 500 includes a processing unit 510 (e.g., a DSP, a CPU, a GPU, etc.) and a memory 520. The processing unit 510 can be configured to implement instructions that correspond to the method 400 of FIG. 4A, the method 450 of FIG. 4B, and/or other aspects of the implementations described above.

[0051] FIG. 6 is a schematic block diagram of a system chip 600 (e.g., a component within the terminal device 120 of FIG. 1 and/or the network device 110 of FIG. 1) in accordance with one or more implementations of the present technology. The system chip 600 in FIG. 6 includes an input interface 601 , an output interface 602, a processor 603, and a memory 604 (e.g., a non-transitory, computer-readable medium) that may be connected through an internal communication connection line, where the processor 603 is configured to execute code in the memory 604. The memory 604 can include code that corresponds to the method 400 of FIG. 4A and/or other aspects of the implementations described above. Accordingly, the processor 603 can implement the method 400 of FIG. 4A, the method 450 of FIG. 4B, and/or other aspects of the implementations described above.

[0052] FIG. 7 is a schematic block diagram of a communications device 700 (e.g., an instance of the terminal device 120 of FIG. 1 and/or the network device 110 of FIG. 1 ) in accordance with one or more implementations of the present technology. The communications device 700 may include a processor 710, a memory 720, and transceiver 730. The memory 720 may store program code, and the processor 710 may execute the program code stored in the memory 720. The memory 720 can include code that corresponds to the method 400 of FIG. 4A and/or other aspects of the implementations described above. Accordingly, the processor 710 can implement the method 400 of FIG. 4A, the method 450 of FIG. 4B, and/or other aspects of the implementations described above. [0053] It should be understood that the processor in the implementations of this technology may be an integrated circuit chip and has a signal processing capability. During implementation, the steps in the foregoing method may be implemented by using an integrated logic circuit of hardware in the processor or an instruction in the form of software. The processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or another programmable logic device, a discrete gate or transistor logic device, and a discrete hardware component. The methods, steps, and logic block diagrams disclosed in the implementations of this technology may be implemented or performed. The general-purpose processor may be a microprocessor, or the processor may be alternatively any conventional processor or the like. The steps in the methods disclosed with reference to the implementations of this technology may be directly performed or completed by a decoding processor implemented as hardware or performed or completed by using a combination of hardware and software modules in a decoding processor. The software module may be located at a random-access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, or another mature storage medium in this field. The storage medium is located at a memory, and the processor reads information in the memory and completes the steps in the foregoing methods in combination with the hardware thereof.

[0054] It may be understood that the memory in the implementations of this technology may be a volatile memory or a non-volatile memory, or may include both a volatile memory and a non-volatile memory. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM) or a flash memory. The volatile memory may be a random-access memory (RAM) and is used as an external cache. For exemplary rather than limitative description, many forms of RAMs can be used, and are, for example, a static random-access memory (SRAM), a dynamic randomaccess memory (DRAM), a synchronous dynamic random-access memory (SDRAM), a double data rate synchronous dynamic random-access memory (DDR SDRAM), an enhanced synchronous dynamic random-access memory (ESDRAM), a synchronous link dynamic random-access memory (SLDRAM), and a direct Rambus random-access memory (DR RAM). It should be noted that the memories in the systems and methods described herein are intended to include, but are not limited to, these memories and memories of any other suitable type.

Examples

[0055] 1. A method for operating a communications device, the method comprising: receiving, at a terminal device, a downlink message that includes a set of configuration indexes that identify one or more channel state information reference signal (CSI-RS) resources configured for a beam failure detection reference signal; determining, at the terminal device, at least one CSI-RS resource identified in the set of configuration indexes for the beam failure detection reference signal; and performing, at the terminal device, beam failure detection with the at least one CSI- RS resource.

2. The of example 1 or a combination of portions thereof, further comprising: identifying, at the terminal device, the beam failure detection reference signal according to a transmission configuration indicator (TCI) state configured to a control resource set (CORESET).

3. The method of any one or a combination of examples 1 or 2, further comprising: determining, at the terminal device, a block error rate (BLER) for the at least one CSI-

RS resource; and in response to the BLER for the at least one CSI-RS resource being above a threshold value, determining, at the terminal device, beam failure for a CORESET associated with the at least one CSI-RS resource. 4. The method of any one or a combination of examples 1 -3, wherein the CORESET is configured with two or more TCI states.

5. The method of any one or a combination of examples 1 -4, wherein the downlink message indicates a serving cell identifier, a bandwidth part identifier, or a transmission-reception point (TRP) identifier.

6. The method of any one or a combination of examples 1 -5, wherein the terminal device is configured to operate beam failure recovery in a bandwidth part of a serving cell.

7. The method of any one or a combination of examples 1 -6, wherein the downlink message is a media access control (MAC) control element (CE) message.

8. A system, comprising: a terminal device configured to perform a method of any one of examples 1-7, any complementary processes of examples 1-7, any portions of examples 1-7, or a combination thereof.

9. A wireless communications terminal device comprising: an antenna configured to wirelessly communicate information with a wireless communications network, wherein the terminal device performs a method of any one of examples 1 -7, any complementary processes of examples 1 -7, any portions of examples 1-7, or a combination thereof.

Conclusion

[0056] The above Detailed Description of examples of the disclosed technology is not intended to be exhaustive or to limit the disclosed technology to the precise form disclosed above. While specific examples for the disclosed technology are described above for illustrative purposes, various equivalent modifications are possible within the scope of the described technology, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative implementations may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or sub-combinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed or implemented in parallel, or may be performed at different times. Further, any specific numbers noted herein are only examples; alternative implementations may employ differing values or ranges.

[0057] These and other changes can be made to the disclosed technology in light of the above Detailed Description. While the Detailed Description describes certain examples of the disclosed technology, as well as the best mode contemplated, the disclosed technology can be practiced in many ways, no matter how detailed the above description appears in text. Details of the system may vary considerably in its specific implementation, while still being encompassed by the technology disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the disclosed technology should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the disclosed technology with which that terminology is associated. Accordingly, the invention is not limited, except as by the appended claims. In general, the terms used in the following claims should not be construed to limit the disclosed technology to the specific examples disclosed in the specification, unless the above Detailed Description section explicitly defines such terms.

[0058] A person of ordinary skill in the art may be aware that, in combination with the examples described in the implementations disclosed in this specification, units and algorithm steps may be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software depends on particular applications and design constraint conditions of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of this application. [0059] Although certain aspects of the invention are presented below in certain claim forms, the applicant contemplates the various aspects of the invention in any number of claim forms. Accordingly, the applicant reserves the right to pursue additional claims after filing this application to pursue such additional claim forms, in either this application or in a continuing application.

Claims

CLAIMS l/We claim:

1 . A method for operating a communications device, the method comprising: receiving, at a terminal device, a downlink message that includes a set of configuration indexes that identify one or more channel state information reference signal (CSI-RS) resources configured for a beam failure detection reference signal, wherein the downlink message indicates a serving cell identifier, a bandwidth part identifier, or a transmission-reception point (TRP) identifier; determining, at the terminal device, at least one CSI-RS resource identified in the set of configuration indexes for the beam failure detection reference signal; and performing, at the terminal device, beam failure detection with the at least one CSI- RS resource.

2. The method of claim 1 , further comprising: identifying, at the terminal device, the beam failure detection reference signal according to a transmission configuration indicator (TCI) state configured to a control resource set (CORESET).

3. The method of claim 1 , further comprising: determining, at the terminal device, a block error rate (BLER) for the at least one CSI- RS resource; and in response to the BLER for the at least one CSI-RS resource being above a threshold value, determining, at the terminal device, beam failure for a CORESET associated with the at least one CSI-RS resource.

4. The method of claim 3, wherein the CORESET is configured with two or more TCI states.

5. The method of claim 3, wherein the BLER is determined based on the at least one CSI-RS resource being transmitted with a single frequency network mode.

6. The method of claim 1 , wherein the terminal device is configured to operate beam failure recovery in a bandwidth part of a serving cell.

7. The method of claim 1 , wherein the downlink message is a media access control (MAC) control element (CE) message.

8. A system, comprising: a terminal device configured to perform a process comprising: receiving a downlink message that includes a set of configuration indexes that identify one or more channel state information reference signal (CSI-RS) resources configured for a beam failure detection reference signal, wherein the downlink message indicates a serving cell identifier, a bandwidth part identifier, or a transmission-reception point (TRP) identifier; determining at least one CSI-RS resource identified in the set of configuration indexes for the beam failure detection reference signal; and performing beam failure detection with the at least one CSI-RS resource.

9. The system of claim 8, wherein the process further comprises: identifying the beam failure detection reference signal according to a transmission configuration indicator (TCI) state configured to a control resource set (CORESET).

10. The system of claim 8, wherein the process further comprises: determining a block error rate (BLER) for the at least one CSI-RS resource; and in response to the BLER for the at least one CSI-RS resource being above a threshold value, determining beam failure for a CORESET associated with the at least one CSI-RS resource.

11 . The system of claim 10, wherein the CORESET is configured with two or more TCI states.

12. The system of claim 10, wherein the BLER is determined based on the at least one CSI-RS resource being transmitted with a single frequency network mode.

13. The system of claim 8, wherein the terminal device is configured to operate beam failure recovery in a bandwidth part of a serving cell.

14. The system of claim 8, wherein the downlink message is a media access control (MAC) control element (CE) message.

15. A wireless communications terminal device comprising: an antenna configured to wirelessly communicate information with a wireless communications network, wherein the terminal device performs a process comprising: receiving a downlink message that includes a set of configuration indexes that identify one or more channel state information reference signal (CSI-RS) resources configured for a beam failure detection reference signal, wherein the downlink message indicates a serving cell identifier, a bandwidth part identifier, or a transmission-reception point (TRP) identifier; determining at least one CSI-RS resource identified in the set of configuration indexes for the beam failure detection reference signal; and performing beam failure detection with the at least one CSI-RS resource.

16. The wireless communications terminal device of claim 15, wherein the process further comprises: identifying the beam failure detection reference signal according to a transmission configuration indicator (TCI) state configured to a control resource set (CORESET).

17. The wireless communications terminal device of claim 15, wherein the process further comprises: determining a block error rate (BLER) for the at least one CSI-RS resource; and in response to the BLER for the at least one CSI-RS resource being above a threshold value, determining beam failure for a CORESET associated with the at least one CSI-RS resource.

18. The wireless communications terminal device of claim 17, wherein the CORESET is configured with two or more TCI states.

19. The wireless communications terminal device of claim 17, wherein the BLER is determined based on the at least one CSI-RS resource being transmitted with a single frequency network mode.

20. The wireless communications terminal device of claim 15, wherein: the terminal device is configured to operate beam failure recovery in a bandwidth part of a serving cell, and the downlink message is a media access control (MAC) control element (CE) message.