Terminal device, network device, method for terminal device, and method for network device

Abstract

To provide a communication method, a device, and a computer storage medium that have functionality for beam failure recovery when enhancing the beam management relation of multi-transmission / reception point (multi-TRP) transmission.SOLUTION: A method includes means for performing beam failure detection based on two reference signal (RS) sets, and means for transmitting a medium access control (MAC) control element (CE) for beam failure recovery to a network device. The MAC-CE includes a first field indicating whether beam failure is detected for a cell, a second field indicating whether the beam failure is detected for one of the cell's RS sets or whether the beam failure is detected for both of the RS sets, and a third field indicating the presence of a candidate RS identifier (ID) field.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] TECHNICAL FIELD Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to communication methods, apparatus, and computer storage media. [Background technology]

[0002] Recently, there have been discussions about enhancing support for the introduction of multi-transmission and reception points (multi-TRPs). For example, it has been proposed to identify and specify characteristics that improve the reliability and robustness of physical channels other than the physical downlink shared channel (PDSH), such as the physical downlink control channel (PDCCH), physical uplink shared channel (PUSCH), and / or physical uplink control channel (PUCCH), using multi-TRPs and / or multi-panels based on the Release-16 reliability characteristics as a baseline. It has already been proposed to identify and specify enhancements related to quasi-colocation (QCL) / transmission configuration indicator (TCI) to enable inter-cell multi-TRP operation, assuming multi-PDSCH reception based on multi-downlink control information (multi-DCI). It has also been proposed to evaluate and, if necessary, specify beam management-related enhancements for multi-TRP transmission simultaneously with multi-panel reception. Summary of the Invention [Problem to be solved by the invention]

[0003] Generally, the exemplary embodiments of the present disclosure provide a communication method, apparatus, and computer storage medium. [Means for solving the problem]

[0004] In a first aspect, a communication method is provided, the method including: receiving, in a terminal device, a configuration from a network device indicating that each cell in a cell group serving the terminal device is associated with at least one of a plurality of TRPs coupled to the network device; and, in response to detecting a beam failure on a cell in the cell group, transmitting to the network device a beam failure recovery request including TRP information associated with the beam failure detected on the cell.

[0005] In a second aspect, a communication method is provided, the method including: transmitting, from a network device to a terminal device, a configuration indicating that each cell in a cell group serving the terminal device is associated with at least one of a plurality of TRPs coupled to the network device; and receiving, in response to detecting a beam failure on a cell in the cell group, a beam failure recovery request from the terminal device, the beam failure recovery request including TRP information related to the beam failure detected on the cell.

[0006] In a third aspect, there is provided a terminal device, the terminal device comprising circuitry configured to perform the method according to the first aspect of the present disclosure.

[0007] In a fourth aspect, there is provided a network device, the network device comprising circuitry configured to perform a method according to the second aspect of the present disclosure.

[0008] In a fifth aspect, there is provided a computer program product comprising machine-executable instructions that, when executed, cause a machine to perform a method according to the first or second aspect of the present disclosure.

[0009] In a sixth aspect, there is provided a computer-readable medium having stored thereon instructions that, when executed on at least one processor, cause the at least one processor to perform a method according to the first or second aspect of the present disclosure.

[0010] It should be understood that this Summary of the Invention is not intended to identify key or essential features of the embodiments of the present disclosure, nor to limit the scope of the present disclosure. Other features of the present disclosure will be readily apparent from the following description. [Brief explanation of the drawings]

[0011] The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description of several embodiments of the present disclosure in the drawings.

[0012] [Figure 1] FIG. 1 illustrates an exemplary communication network in which embodiments of the present disclosure may be implemented.

[0013] [Figure 2] FIG. 1 is an exemplary signaling diagram in accordance with some embodiments of the present disclosure.

[0014] [Figure 3] FIG. 1 illustrates an example of an embodiment of the present disclosure.

[0015] [Figure 4] FIG. 1 illustrates an example of an embodiment of the present disclosure.

[0016] [Figure 5] FIG. 1 illustrates an example of an embodiment of the present disclosure.

[0017] [Figure 6] FIG. 1 illustrates an example of an embodiment of the present disclosure.

[0018] [Figure 7] FIG. 1 illustrates an example of an embodiment of the present disclosure.

[0019] [Figure 8] 1 is a flowchart of an exemplary method according to some embodiments of the present disclosure.

[0020] [Figure 9] 1 is a flowchart of an exemplary method according to some embodiments of the present disclosure.

[0021] [Figure 10] FIG. 1 is a schematic block diagram of an apparatus suitable for implementing embodiments of the present disclosure.

[0022] In the drawings, the same or similar reference numbers represent the same or similar elements. DETAILED DESCRIPTION OF THE INVENTION

[0023] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are provided for illustrative purposes only to aid those skilled in the art in understanding and practicing the present disclosure, and do not imply any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various ways different from those described below.

[0024] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0025] As used herein, the singular forms "a," "an," and "said" include the plural forms unless the context clearly indicates otherwise. The term "comprises" and variations thereof should be understood as open-ended, meaning "including, but not limited to." The term "based on" should be understood as "based at least in part on." The terms "some embodiments" and "embodiments" should be understood as "at least some embodiments." The term "another embodiment" should be understood as "at least one other embodiment." Terms such as "first," "second," etc. can refer to different or the same object. The following may include other explicit and implicit definitions.

[0026] In some instances, values, procedures, or devices are referred to as "best," "lowest," "highest," "minimum," "maximum," etc. It will be understood that such descriptions are intended to illustrate that choices may be made from among many functional alternatives used, and that such choices are not necessarily better, smaller, higher, or otherwise more preferred than other choices.

[0027] As used herein, the term "circuitry" can refer to a hardware circuit and / or a combination of a hardware circuit and software. For example, a circuit may be a combination of analog and / or digital hardware circuitry and software / firmware. As yet another example, a circuit may be any portion of a hardware processor with software, including a digital signal processor, software, and one or more memories, that cooperate to cause a device, such as a terminal device or a network device, to perform various functions. In yet another example, a circuit may be a hardware circuit and / or a processor, such as a microprocessor or portion thereof, that requires software / firmware for operation, although the software may not be present if not necessary for operation. As used herein, the term "circuitry" also includes implementations of only a hardware circuit or one or more processors, or a portion of a hardware circuit or one or more processors and its (or their) accompanying software and / or firmware.

[0028] As mentioned above, it is also proposed to evaluate and, if necessary, identify beam management related enhancements for multi-TRP transmissions in conjunction with multi-panel reception. However, there is no detailed design for beam failure recovery based on multi-TRP in the current 3GPP specifications.

[0029] Embodiments of the present disclosure provide a solution for solving the above problem and / or one or more other potential problems. According to this solution, in response to a beam failure detected by a terminal device on a cell in a cell group, the terminal device may transmit a beam failure recovery request (BFRQ) to a network device, the beam failure recovery request including TRP information related to the beam failure detected on the cell. For example, the TRP information may indicate at least one of: a number of TRPs related to the beam failure detected on the cell; a TRP index related to the beam failure detected on the cell; whether a new candidate beam has been identified on the failed TRP; whether a new candidate beam has been identified on the failed TRP; information about the new candidate beam if a new candidate beam has been identified on the failed TRP; etc. Thus, this solution can support multi-TRP-based BFRQ.

[0030] 1 illustrates an exemplary communication network 100 in which embodiments of the present disclosure can be implemented. Network 100 includes a network device 110 and a terminal device 120 served by network device 110. Network 100 may provide one or more serving cells to serve terminal device 120.

[0031] As used herein, the term "terminal device" refers to any device capable of wireless or wired communication. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktop computers, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, any Internet of Things (IoE) device, machine-type communication (MTC) devices, and in-vehicle devices for V2X communications, where the "X" in V2X represents a pedestrian, vehicle, or infrastructure / network, or an image capture device such as a digital camera, a gaming device, a music storage and playback device, or an internet appliance that enables wireless or wired internet access and browsing. For purposes of explanation, some embodiments will be described below with reference to a UE as an example of terminal device 120.

[0032] As used herein, the term "network equipment" or "base station" (BS) refers to equipment capable of providing or hosting a cell or coverage area over which terminal devices can communicate. Examples of network equipment include, but are not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a next generation Node B (gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a low-power node such as a femto node, or a pico node.

[0033] In some scenarios, carrier aggregation (CA), in which two or more CCs are aggregated to support a wider bandwidth, may be supported in network 100. For example, in FIG. 1, network device 110 may provide multiple serving cells to terminal device 120, including one primary cell (Pcell) 101 corresponding to a primary CC and at least one secondary cell (Scell) 102 corresponding to at least one secondary CC. It should be understood that the number of network devices, terminal devices, and / or serving cells in FIG. 1 is provided for illustrative purposes only and does not imply any limitations on the present disclosure. Network 100 may include any appropriate number of network devices, terminal devices, and / or serving cells suitable for implementing embodiments of the present disclosure.

[0034] In some other scenarios, the terminal device 120 may establish connections with two different network devices (not shown in FIG. 1 ) and thus utilize the radio resources of the two network devices. These two network devices may be defined as a master network device and a secondary network device, respectively. The master network device may provide a group of serving cells also referred to as a “Master Cell Group (MCG).” The secondary network device may also provide a group of serving cells also referred to as a “Secondary Cell Group (SCG).” In the case of dual connectivity operation, the term “Special Cell (Spcell)” may refer to a Pcell of an MCG or a Primary Scell ​​(Pscell) of an SCG, depending on whether the terminal device 120 is associated with the MCG or SCG, respectively. In cases other than dual connectivity operation, the term “SpCell” may refer to a PCell.

[0035] In one embodiment, the terminal device 120 may be connected to a first network device and a second network device (not shown in FIG. 1). One of the first network device and the second network device may be in a master node, and the other may be in a secondary node. The first network device and the second network device may use different radio access technologies (RATs). In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device may be an eNB, and the second RAT device may be a gNB. Information regarding the different RATs may be transmitted to the terminal device 120 from at least one of the first network device and the second network device. In one embodiment, the first information may be transmitted from the first network device to the terminal device 120, and the second information may be transmitted from the second network device directly or via the first network device to the terminal device 120. In one embodiment, information regarding the terminal device configuration configured by the second network device may be transmitted from the second network device via the first network device. Information regarding the reconfiguration of the terminal device set by the second network device may be transmitted to the terminal device directly from the second network device or via the first network device, and may be transmitted via any of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) control elements (CEs), or Downlink Control Information (DCIs).

[0036] 1, network device 110 can communicate data and control information to terminal device 120, and terminal device 120 can also communicate data and control information to network device 110. The link from network device 110 to terminal device 120 is called downlink (DL), and the link from terminal device 120 to network device 110 is called uplink (UL).

[0037] In some embodiments, for downlink transmission, network device 110 may transmit control information to terminal device 120 via a PDCCH and / or transmit data to terminal device 120 via a PDSCH. Furthermore, network device 110 may transmit one or more reference signals (RS) to terminal device 120. An RS transmitted from network device 110 to terminal device 120 may be referred to as a "DL RS." Examples of DL RS may include, but are not limited to, a demodulation reference signal (DMRS), a channel state information reference signal (CSI-RS), a sounding reference signal (SRS), a phase tracking reference signal (PTRS), a fractional time and frequency tracking reference signal (TRS), etc.

[0038] In some embodiments, for uplink transmission, terminal device 120 may transmit control information to network device 110 via a PUCCH and / or transmit data to network device 110 via a PUSCH. Furthermore, terminal device 120 may transmit one or more RSs to network device 110. An RS transmitted from terminal device 120 to network device 110 may be referred to as a "UL RS." Examples of UL RSs may include, but are not limited to, a DMRS, a CSI-RS, an SRS, a PTRS, a fractional time and frequency TRS, etc.

[0039] Communications in network 100 may conform to any suitable standard, including, but not limited to, Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communications (MTC), etc. Furthermore, communications may be performed according to any currently known or future-developed generation of communications protocols. Examples of communications protocols include, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, and fifth-generation (5G) communications protocols.

[0040] A network device 110 (e.g., a gNB) can include one or more TRPs or antenna panels. As used herein, the term "TRP" refers to an antenna array (having one or more antenna elements) available to a network device located in a particular geographic location. For example, a network device may be coupled to multiple TRPs in different geographic locations to achieve better coverage. The one or more TRPs can be included in the same serving cell or different serving cells.

[0041] It should be understood that a TRP can be a panel, and a panel can also refer to an antenna array (having one or more antenna elements). Although several embodiments of the present disclosure have been described with reference to multiple TRPs as examples, these embodiments are for illustrative purposes only and are intended to assist those skilled in the art in understanding and practicing the present disclosure, and do not imply any limitation on the scope of the present disclosure. It should be understood that the contents of the present disclosure described herein can be implemented in a variety of ways different from those described below.

[0042] As shown in FIG. 1 , for example, network device 110 can communicate with terminal device 120 via TRPs 130-1 and 130-2 (hereinafter collectively referred to as “TRP 130” or individually as “TRP 130”). For example, TRP 130-1 may be referred to as a first TRP, and TRP 130-2 may be referred to as a second TRP. As described above, network device 110 may provide a group of cells to serve terminal device 120. In some embodiments, the cell group may be divided into a first subset of cells associated with first TRP 130-1 and a second subset of cells associated with second TRP 130-2. For example, the first subset of cells and the second subset of cells may include one or more overlapping cells or may not overlap each other.

[0043] FIG. 2 is a signaling diagram 200 according to an embodiment of the present disclosure. As shown in FIG. 2, network device 110 may transmit 201 a configuration to terminal device 120. In some embodiments, the configuration may indicate that each cell in a cell group serving terminal device 120 is associated with at least one of TRPs 130 coupled to network device 110. For example, the configuration may be transmitted from network device 110 to terminal device 120 via at least one of Radio Resource Control (RRC) signaling, a Medium Access Control (MAC) control element (CE), or Downlink Control Information (DCI). Terminal device 120 may perform 220 beam failure detection. In response to detecting beam failure on a cell in the cell group, terminal device 120 may transmit a BFRQ to network device 110 based on the configuration. In some embodiments, the BFRQ may include TRP information associated with the beam failure detected on the cell.

[0044] In some embodiments, there may be M TRPs serving the terminal device 120, where M is a positive integer. For example, 1≦M≦4. For another example, M=2. In some embodiments, each TRP in the M TRPs is represented by or associated with at least one of a control resource set (CORESET) pool index, a CORESET group identifier (ID), a group of CORESETs, an SRS resource set, an SRS resource set ID, a TCI state, a group of TCI states, an ID of a set of reference signals (RSs) for beam failure detection, an ID of a set of RSs for new beam identification, spatial relation information, a group of spatial relation information, a set of QCL parameters, a group of RSs for beam failure detection, a group of RSs for new beam identification, etc. In the example shown in FIG. 1, M=2. In this case, the first TRP 130-1 may be represented by or associated with at least one of a first CORESET pool index (e.g., having a value of 0; for another example, a CORESET that does not have the parameter “CORESET pool index” set), a first CORESET group ID, a first group of CORESETs (e.g., a CORESET configured to have the first CORESET pool index or the first CORESET group ID; for another example, a CORESET that is not configured to have the parameter “CORESET pool index” or the parameter “CORESET group ID”), a first SRS resource set, a first SRS resource set ID, a first TCI state, a first group of TCI states, an ID of a first set of reference signals (RSs) for beam failure detection, an ID of a second set of RSs for new beam identification, first spatial relationship information, a first group of spatial relationship information, a first set of QCL parameters, a first group of RSs for beam failure detection, and a first group of RSs for new beam identification.The second TRP 130-1 may be represented by at least one of a second CORESET pool index (e.g., having a value of 1), a second CORESET group ID, a second group of CORESETs (e.g., a CORESET configured to have a second CORESET pool index or a second CORESET group ID), a second SRS resource set, a second SRS resource set ID, a second TCI state, a second group of TCI states, an ID of a third set of reference signals (RSs) for beam failure detection, an ID of a fourth set of RSs for new beam identification, second spatial relationship information, a second group of spatial relationship information, a second set of QCL parameters, a second group of RSs for beam failure detection, and a second group of RSs for new beam identification.

[0045] In the following, the terms "TRP," "CORESET pool index," "CORESET group ID," "CORESET group," "SRS resource set," "SRS resource set ID," "TCI state," "TCI state group," "ID of RS set for beam failure detection," "ID of RS set for new beam identification," "spatial relationship information," "group of spatial relationship information," "set of QCL parameters," "group of RSs for beam failure detection," and "group of RSs for new beam identification" may be used interchangeably. In the following, the terms "first TRP," "first CORESET pool index," "first CORESET group ID," "first group of CORESET," "first SRS resource set," "first SRS resource set ID," "first TCI state," "first group of TCI states," "ID of first set of RSs for beam failure detection," "ID of second set of RSs for new beam identification," "first spatial relationship information," "first group of spatial relationship information," "first set of QCL parameters," "first group of RSs for beam failure detection," and "first group of RSs for new beam identification" may be used interchangeably. In the following, the terms "second TRP," "second CORESET pool index," "second CORESET group ID," "second group of CORESET," "second SRS resource set," "second SRS resource set ID," "second TCI state," "second group of TCI state," "ID of third set of RSs for beam failure detection," "ID of fourth set of RSs for new beam identification," "second spatial relationship information," "second group of spatial relationship information," "second set of QCL parameters," "second group of RSs for beam failure detection," and "second group of RSs for new beam identification" may be used interchangeably. The terms "PUSCH" and "PUSCH MAC CE" may be used interchangeably.

[0046] In some embodiments, as described above, the network device 110 may provide a group of cells to serve the terminal device 120. Within this cell group, there may be one cell for transmitting the PUCCH and at least one secondary Scell. Hereinafter, the cell for transmitting the PUCCH may be referred to as "cell 1," and at least one Scell ​​cell may be referred to as "cell X," where X is a positive integer and 2≦X≦32. For example, cell 1 may be an Scell ​​for transmitting the PUCCH (also referred to as a "PUCCH-Scell"), a Pcell, a Pscell, or an Spcell. In some embodiments, cell 1 may be associated with two TRPs 130-1 and 130-2, or may be associated with one of the TRPs 130-1 and 130-2. In some embodiments, at least one of the cells X may be associated with two TRPs 130-1 and 130-2, or each of the cells X may be associated with one of the TRPs 130-1 and 130-2.

[0047] In some embodiments, within a group of cells, there may be a subset of cells (e.g., Y cells, where Y is an integer and 1≦Y≦X+1) configured for simultaneous beam failure recovery. In some embodiments, the subset of cells may be configured to have the same set of RSs for beam failure detection (referred to as "q0_Y") and / or the same set of RSs for new beam identification (referred to as "q1_Y"). In some embodiments, q0_Y and / or q1_Y are in at least one cell in the subset of cells.

[0048] In some embodiments, in response to detecting beam failure on at least one of the subset of cells, terminal device 120 may provide an indication (e.g., a beam failure indication) about the subset of cells to higher layers. In some embodiments, upon request from higher layers, terminal device 120 may notify higher layers that the corresponding L1-RSRP measurements are Q in,LRProvide whether there is at least one periodic CSI-RS configuration index and / or synchronization signal (SS) / physical broadcast channel block (PBCH) index from the set q1_Y that is greater than or equal to a threshold, and provide whether the periodic CSI-RS configuration index and / or SS / PBCH block index from the set, and / or Q in,LR In some embodiments, in response to detecting beam failure on at least one of the subsets of cells, terminal device 120 may transmit a BFRQ to network device 110 via a PUSCH MAC CE, where the PUSCH MAC CE includes at least one of: an index of the subset (e.g., if multiple subsets are configured in a cell group), an indication of the subset of cells, an index of a TRP associated with the subset of cells, an indication of the presence of a new beam (denoted as "q_new") identified for the subset of cells, and an RS ID for the new beam for periodic CSI-RS configuration or an SS / PBCH block provided by higher layers (if any for the subset of cells). That is, q_new is common for the subset of cells.

[0049] In some embodiments, terminal device 120 may monitor the PDCCH on all subsets of cells, in all CORESETs, or in the first group of CORESETs, or in the second group of CORESETs, using the same antenna port QCL parameter associated with the corresponding index q_new (if any). In some embodiments, the index of the subset of cells may be indicated / reported by a PUSCH (e.g., a first PUSCH) or a MAC CE. In some embodiments, monitoring may be applied 28 symbols after the last symbol of the first PDCCH reception having a DCI format that schedules a PUSCH transmission. The HARQ process number for a PUSCH transmission, or indicated in the first PDCCH, or indicated in the DCI format, may be the same as the HARQ process number of the first PUSCH. For example, the NDI field value for a PUSCH transmission, or indicated in the first PDCCH, or indicated in the DCI format may be different from the NDI field value for the first PUSCH transmission. For example, the NDI field value for a PUSCH transmission, or indicated in the first PDCCH, or indicated in the DCI format, may have a value that is toggled from the NDI field value for the first PUSCH transmission. In some embodiments, if a beam failure is detected in the first TRP, or associated with a first group of CORESET, or associated with a first group of RSs for beam failure detection, the PDCCH may be monitored in the first group of CORESET. In some embodiments, if a beam failure is detected in the second TRP, or associated with a second group of CORESET, or associated with a second group of RSs for beam failure detection, the PDCCH may be monitored in the second group of CORESET.

[0050] In some embodiments, 28 symbols after the last symbol of a PDCCH reception having a DCI format that schedules a PUSCH transmission with the same HARQ process number as the first PUSCH transmission and with a toggled NDI field value, the terminal device 120 may monitor the PDCCH on all subsets of cells indicated by the MAC CE and within all CORESETs using the same antenna port QCL parameters associated with the corresponding index q_new (if any).

[0051] In some embodiments, for example, a group of cells provided by network device 110 to serve terminal device 120 may be divided into a first subset of cells associated with a first TRP 130-1 and a second subset of cells associated with a second TRP 130-2. The first subset of cells may be configured to have a first set of RSs for beam failure detection and a second set of RSs for new beam identification. The second subset of cells may be configured to have a third set of RSs for beam failure detection and a fourth set of RSs for new beam identification. In some embodiments, in response to beam failure being detected based on the first set of RSs, terminal device 120 may transmit a first BFRQ to network device 110 that includes an indication of at least the first TRP 130-1 or the first subset of cells. For example, terminal device 120 may transmit a first BFRQ via a first PUSCH MAC CE, where the first PUSCH MAC CE includes at least one of the following: an index of the first and second subsets, an indication of the first subset of cells, an index of a first TRP associated with the first subset of cells, an indication of the presence of a new beam identified for the first subset of cells, an RS ID for the new beam for periodic CSI-RS configuration or an SS / PBCH block provided by a higher layer (if any for the first subset of cells). In some embodiments, in response to detecting beam failure based on the second set of RSs, terminal device 120 may transmit a second BFRQ to network device 110, the second BFRQ including at least a second TRP 130-2 or an indication of the second subset of cells.For example, the terminal device 120 may transmit a second BFRQ via a second PUSCH MAC CE, where the second PUSCH MAC CE includes at least one of the following: indices of the first and second subsets, an indication of the second subset of cells, an index of a second TRP associated with the second subset of cells, an indication of the existence of a new beam identified for the second subset of cells, a new beam for periodic CSI-RS configuration, or an RS ID for an SS / PBCH block provided by a higher layer (if any for the second subset of cells).

[0052] It should be appreciated that introducing a subset of cells for simultaneous beam failure recovery can reduce the delay of beam management or beam failure recovery procedures. For example, the beams may be common or similar for the subset of cells. That is, if a beam failure is detected on one cell in the subset of cells, the beams of other cells in the subset of cells may also fail. It should also be appreciated that this scheme can reduce the signaling overhead for beam failure recovery requests. For example, the indication of beam failure, whether a new beam has been identified, and / or the index of the new beam (if recognized) are common for the subset of cells. Therefore, they do not need to be reported separately for each of the subset of cells.

[0053] 3 is a diagram illustrating an example BFRQ 300 according to an embodiment of the present disclosure. As shown in FIG. 3, the fields in the BFRQ 300 are defined as follows: -SP: This field indicates beam failure detection for the SpCell of this MAC entity (as specified in clause 5.17 of TS 38.321). The SP field is set to 1 to indicate that beam failure has been detected for the SpCell only if a BFR MAC CE or a truncated BFR MAC CE is included in the MAC PDU as part of the random access procedure (as specified in 5.1.3a and 5.1.4 of TS 38.321), otherwise it is set to 0. -C i (BFR MAC CE): This field indicates beam failure detection (as described in clause 5.17) for the SCell with ServCellIndex i as described in TS 38.331 and the presence of an octet containing the AC field. i The AC field indicates that a beam failure has been detected, the evaluation of candidate beams according to the requirements specified in TS 38.133 has already been completed, and an octet containing the AC field exists for the SCell with ServCellIndex i. i The field indicates that either no beam obstruction was detected or that a beam obstruction was detected but the evaluation of candidate beams according to the requirements specified in TS 38.133 has not yet been completed and no octet containing an AC field exists for the SCell with ServCellIndex i. The octets containing the AC field are present in ascending order based on ServCellIndex. -C i (Truncated BFR MAC CE): This field indicates beam failure detection (as described in clause 5.17) for the SCell with ServCellIndex i as described in TS 38.331. C set to 1 iThe AC field indicates that a beam failure has been detected, the evaluation of candidate beams according to the requirements specified in TS 38.133 has already been completed, and an octet containing the AC field may be present for the SCell with ServCellIndex i. i The field indicates that either no beam obstruction was detected, or that a beam obstruction was detected but the evaluation of candidate beams according to the requirements specified in TS 38.133 has not yet been completed, and no octets containing AC fields are present for the SCell with ServCellIndex i. The octets containing AC fields (if present) are included in ascending order based on ServCellIndex. The number of octets containing AC fields included is maximized so as not to exceed the available grant size. Note: The number of octets containing the AC field in a truncated BFR MAC CE may be zero. -AC: This field indicates the presence of the Candidate RS ID field in the octet. If at least one SSB in the candidateBeamRSSCellList whose SS-RSRP exceeds rsrp-ThresholdBFR or at least one CSI-RS in the candidateBeamRSSCellList whose CSI-RSRP exceeds rsrp-ThresholdBFR is available, the AC field is set to 1; otherwise, it is set to 0. If the AC field is set to 1, the Candidate RS ID field is present. If the AC field is set to 0, R bits are present instead. -Candidate RS ID: This field is set to the index of the SSB in candidateBeamRSSCellList whose SS-RSRP exceeds rsrp-ThresholdBFR, or to the index of the CSI-RS in candidateBeamRSSCellList whose CSI-RSRP exceeds rsrp-ThresholdBFR. The index of the SSB or CSI-RS is the index of the entry in candidateBeamRSSCellList corresponding to that SSB or CSI-RS. Index 0 corresponds to the first entry in candidateBeamRSSCellList, index 1 corresponds to the second entry in the list, and so on. The length of this field is 6 bits. -R: Reserved bit, set to 0.

[0054] In some embodiments, in response to detecting beam failure on a cell in a cell group, the terminal device 120 may transmit a BFRQ to the network device 110 via a PUSCH MAC CE. In some embodiments, even if a cell is configured with multiple TRPs and configured to support multi-TRP beam failure recovery, the PUSCH MAC CE may include information about only one TRP. In some embodiments, the PUSCH MAC CE may include an indication of a TRP index that is common for all cells reported in the PUSCH MAC CE. For example, this indication may occupy one bit. In some embodiments, for a cell configured with multiple TRPs and configured to support multi-TRP beam failure recovery, a value of 0 may indicate that the first TRP fails if beam failure is detected on the cell, and a value of 1 may indicate that the second TRP fails if beam failure is detected on the cell. In some embodiments, for a cell configured with only one TRP, the indication in this field may be ignored or reserved. In some embodiments, for a cell configured to have only one TRP, the beam failure recovery request for the cell may be included in the PUSCH for the beam failure recovery request for the first TRP.

[0055] In some embodiments, in response to detecting a beam failure on a cell in a cell group, the terminal device 120 may transmit a BFRQ to the network device 110 via a PUSCH MAC CE. In some embodiments, even if a cell is configured with multiple TRPs and configured to support multi-TRP beam failure recovery, the PUSCH MAC CE may include information about only one TRP. In some embodiments, the PUSCH MAC CE may include an indication of a respective TRP index for each of the cells reported in the PUSCH MAC CE. For example, this indication may occupy one bit. In some embodiments, for a cell configured with multiple TRPs and configured to support multi-TRP beam failure recovery, a value of 0 may indicate that the first TRP fails if a beam failure is detected on the cell, and a value of 1 may indicate that the second TRP fails if a beam failure is detected on the cell. In some embodiments, for cells configured with only one TRP, the indication field may be reserved. In some embodiments, the indication of the TRP index and whether a new beam has been identified may be jointly or separately coded. For example, referring to FIG. 3, field "R" may be used to indicate a TRP index for cells configured to have multiple TRPs and configured to support multi-TRP beam failure recovery, or may be used as a reserved field for cells configured to have only one TRP.

[0056] In some embodiments, in response to detecting a beam failure on a cell in a cell group, the terminal device 120 may transmit a BFRQ to the network device 110 via a PUSCH MAC CE. In some embodiments, for a cell configured with multiple TRPs and configured to support multi-TRP beam failure recovery, the PUSCH MAC CE may include a first field indicating whether one or two TRPs failed for the cell, a second field indicating a TRP index, and one or more fields indicating whether a new beam has been identified for the cell and, if a new beam has been identified, the index of the new beam. In some embodiments, the indication by the second field may be different in different cases. For example, if a cell is configured with multiple TRPs and configured to support multi-TRP beam failure recovery and one TRP has failed, the second field may indicate the index of the failed TRP. If a new beam has been identified for the cell, the new beam may be associated with the TRP. For another example, if a cell is configured with multiple TRPs, configured to support multi-TRP beam failure recovery, and two TRPs fail, the second field may indicate which of the TRPs is associated with a new beam (if one is identified). If a new beam is identified for the cell, the new beam may be associated with the TRP. In some embodiments, for cells configured with only one TRP, the first field and / or the second field may be reserved.

[0057] In some embodiments, in response to detecting beam failure on a cell in a cell group, the terminal device 120 may transmit a BFRQ to the network device 110 via a PUSCH MAC CE. In some embodiments, for each cell reported in the PUSCH MAC CE, the PUSCH MAC CE may indicate at least one of whether beam failure is detected on the cell, a TRP index, whether one or two TRPs have failed, and whether a new beam has been identified for the cell. In some embodiments, at least two of whether beam failure is detected on the cell, a TRP index, whether one or two TRPs have failed, and whether a new beam has been identified for the cell may be jointly coded. FIG. 4 illustrates an example of such an embodiment. FIG. 4 illustrates an example BFRQ 410 in which each cell (e.g., C0, C1, ..., or C7) has a 3-bit field indicating information regarding beam failure detection. Table 420 illustrates possible values ​​and corresponding descriptions for the 3-bit field.

[0058] In some embodiments, in response to detecting beam failure on a cell in a cell group, the terminal device 120 may transmit a BFRQ to the network device 110 via a PUSCH MAC CE. In some embodiments, for each cell reported in the PUSCH MAC CE, the PUSCH MAC CE may indicate at least one of whether beam failure is detected on the cell, a TRP index, whether one or two TRPs have failed, and whether a new beam has been identified for the cell. In some embodiments, whether beam failure is detected on the cell may be indicated in the PUSCH MAC CE, as in conventional solutions. Additionally, the TRP index, whether one or two TRPs have failed, and whether a new beam has been identified for the cell may be coded in a joint field. FIG. 5 illustrates an example of such an embodiment. FIG. 5 illustrates an example BFRQ 510 with a 3-bit joint field where each cell indicates information regarding beam failure detection. Table 520 shows possible values ​​and corresponding descriptions for the 3-bit field. In some embodiments, if a cell is configured with two TRPs and multi-TRP beam failure recovery, the maximum number of new beam identification RSs for one TRP of the cell may be up to 32. That is, the field "Candidate RS ID" may occupy 5 bits.

[0059] In some embodiments, in response to detecting beam failure on a cell in a cell group, the terminal device 120 may transmit a BFRQ to the network device 110 via a PUSCH MAC CE. In some embodiments, for each cell reported in the PUSCH MAC CE, the PUSCH MAC CE may indicate at least one of whether beam failure is detected on the cell, a TRP index, whether one or two TRPs have failed, and whether a new beam has been identified for the cell. In some embodiments, whether beam failure is detected on the cell and whether one or two TRPs have failed may be jointly coded. FIG. 6 illustrates an example of such an embodiment. FIG. 6 illustrates an exemplary BFRQ 610 in which each cell (e.g., C0, C1, ..., or C3) has a 2-bit field indicating information regarding beam failure detection. Table 620 illustrates possible values ​​of the 2-bit field and corresponding descriptions. In some embodiments, if the value of the 2-bit field for the cell is 1, there may be one row, indicated by 630, for a cell in the BFRQ 610. If the value of the 2-bit field for a cell is 2, there may be two rows, indicated by 640, for the cell in the BFRQ 610.

[0060] In some embodiments, in response to detecting a beam failure on a cell in a cell group, terminal device 120 may transmit a BFRQ to network device 110 via a PUSCH MAC CE. In some embodiments, if a new beam is identified for a cell, the PUSCH MAC CE may indicate an RS index for the new beam, where the RS index may implicitly indicate a TRP index associated with the beam failure. In some embodiments, terminal device 120 may be configured to have two candidate RS lists, such as List_1 and List_2. The number of RSs in List_1 may be N1, where N1 is a positive integer and 1≦N1≦64. The number of RSs in List_2 may be N2, where N2 is a positive integer and 1≦N2≦64. The total number of RSs in List_1 and List_2 may be up to M, for example, M=64. In some embodiments, in the PUSCH MAC CE for BFRQ, the candidate RS ID may be set to the index of an entry in the combined list of List_1 and List_2. FIG. 7 shows an example of such an embodiment. FIG. 7 shows an example BFRQ 700 in which there is one field indicating whether one or two TRPs have failed for the cell. In some embodiments, a value of 0 in this field means that only one TRP has failed and there may be one row for reporting candidate RS IDs. In this case, the TRP index may be implicitly indicated by the candidate RS ID. For example, a value of candidate RS ID between 0 and N1-1 indicates that the first TRP has failed, while a value of candidate RS ID between N1 and N1+N2-1 indicates that the second TRP has failed. In some embodiments, a value of 1 in this field means that two TRPs have failed and there may be two rows for reporting candidate RS IDs for these two TRPs.

[0061] In some embodiments, for a cell group provided by network device 110 to serve terminal device 120, up to two PUCCH scheduling request (PUCCH-SR) resources may be configured if cell 1 is configured to have multiple TRPs (e.g., two TRPs). For example, if two PUCCH-SR resources (e.g., SR1 and SR2) are configured, SR1 may be associated with the first TRP and SR2 may be associated with the second TRP.

[0062] In some embodiments, for a cell group provided by the network device 110 to serve the terminal device 120, if cell 1 is configured to have a single TRP, then at most one PUCCH-SR resource can be configured.

[0063] In some embodiments, for a group of cells provided by network device 110 to serve terminal device 120, if cell 1 is configured to have a single TRP and at least one of cells X is configured to have multiple TRPs (e.g., two TRPs), up to two PUCCH-SR resources may be configured. For example, if two PUCCH-SR resources (e.g., SR1 and SR2) are configured, SR1 may be associated with the first TRP for cell X and SR2 may be associated with the second TRP for cell X.

[0064] 8 is a flowchart of an example method 800 according to some embodiments of the present disclosure. For example, the method 800 may be implemented in the terminal device 120 shown in FIG.

[0065] In block 810, the terminal device 120 receives a configuration from a network device (e.g., network device 110 as shown in FIG. 1), where the configuration indicates that each cell in a cell group serving the terminal device is associated with at least one of a plurality of TRPs (e.g., TRPs 130-1 and 130-2 as shown in FIG. 1) coupled to the network device 0.

[0066] In block 820, in response to detecting a beam failure on a cell in the cell group, the terminal device 120 transmits a beam failure recovery request to the network device, the beam failure recovery request including TRP information related to the beam failure detected on the cell.

[0067] In some embodiments, each of the multiple TRPs may be represented by at least one of a CORESET pool index, a CORESET group identifier, an identifier of a set of RSs for beam failure detection, an identifier of a set of RSs for new beam identification, spatial relationship information, an SRS resource set, a TCI state, and a set of QCL parameters.

[0068] In some embodiments, the plurality of TRPs may include a first TRP and a second TRP, the cell group may include a first subset of cells associated with the first TRP and a second subset of cells associated with the second TRP, the first subset of cells may be configured to have a first set of RSs for beam failure detection and a second set of RSs for new beam identification, and the second subset of cells may be configured to have a third set of RSs for beam failure detection and a fourth set of RSs for new beam identification.

[0069] In some embodiments, in response to detecting a beam failure based on the first set of RSs, terminal device 120 may transmit a first beam failure recovery request to the network device that includes an indication of at least a first TRP or a first subset of cells. In response to detecting a beam failure based on a third set of RSs, terminal device 120 may transmit a second beam failure recovery request to the network device that includes an indication of at least a second TRP 130-2 or a second subset of cells.

[0070] In some embodiments, a cell may be associated with multiple TRPs, and the TRP information may indicate one of the multiple TRPs associated with a beam obstruction detected on the cell.

[0071] In some embodiments, the TRP information may include an indication of a common TRP index for all cells indicated in the beam failure recovery request.

[0072] In some embodiments, the TRP information may include an indication of the respective TRP index for each of the cells indicated in the beam failure recovery request.

[0073] In some embodiments, a cell may be associated with multiple TRPs, and the TRP information may include at least one of: first information indicating the number of TRPs associated with a beam failure detected on the cell; second information indicating an index of one of the multiple TRPs associated with a beam failure detected on the cell; and third information indicating on which TRP of the multiple TRPs a new beam was identified.

[0074] In some embodiments, a cell may be associated with multiple TRPs, and the TRP information may include first information indicating the number of TRPs associated with beam obstructions detected on the cell, and second information indicating an RS index for a new beam identified on one of the multiple TRPs, the RS index indicating the index of the one TRP.

[0075] 9 is a flowchart of an example method 900 according to some embodiments of the present disclosure. For example, the method 900 may be implemented in the network device 110 shown in FIG.

[0076] In block 910, the network device 110 transmits a configuration to the terminal device (e.g., the terminal device 120 as shown in FIG. 1), where the configuration indicates that each cell in the cell group serving the terminal device is associated with at least one of a plurality of TRPs coupled to the network device 110 (e.g., the TRPs 130-1 and 130-2 as shown in FIG. 1).

[0077] In block 920, in response to detecting a beam failure on a cell in the cell group, the network device 110 receives a beam failure recovery request from the terminal device including TRP information related to the beam failure detected on the cell.

[0078] In some embodiments, each of the multiple TRPs may be represented by at least one of a CORESET pool index, a CORESET group identifier, an identifier of a set of RSs for beam failure detection, an identifier of a set of RSs for new beam identification, spatial relationship information, an SRS resource set, a TCI state, and a set of QCL parameters.

[0079] In some embodiments, the plurality of TRPs may include a first TRP and a second TRP, the cell group may include a first subset of cells associated with the first TRP and a second subset of cells associated with the second TRP, the first subset of cells may be configured to have a first set of RSs for beam failure detection and a second set of RSs for new beam identification, and the second subset of cells may be configured to have a third set of RSs for beam failure detection and a fourth set of RSs for new beam identification.

[0080] In some embodiments, in response to detecting a beam failure based on the first set of RSs, the network device 110 may receive a first beam failure recovery request from the terminal device that includes an indication of at least a first TRP or a first subset of cells. In response to detecting a beam failure based on a third set of RSs, the network device 110 may receive a second beam failure recovery request from the terminal device that includes an indication of at least a second TRP 130-2 or a second subset of cells.

[0081] In some embodiments, a cell may be associated with multiple TRPs, and the TRP information may indicate one of the multiple TRPs associated with a beam obstruction detected on the cell.

[0082] In some embodiments, the TRP information may include an indication of a common TRP index for all cells indicated in the beam failure recovery request.

[0083] In some embodiments, the TRP information may include an indication of the respective TRP index for each of the cells indicated in the beam failure recovery request.

[0084] In some embodiments, a cell may be associated with multiple TRPs, and the TRP information may include at least one of: first information indicating the number of TRPs associated with a beam failure detected on the cell; second information indicating an index of one of the multiple TRPs associated with a beam failure detected on the cell; and third information indicating on which TRP of the multiple TRPs a new beam was identified.

[0085] In some embodiments, a cell may be associated with multiple TRPs, and the TRP information may include first information indicating the number of TRPs associated with beam obstructions detected on the cell, and second information indicating an RS index for a new beam identified on one of the multiple TRPs, the RS index indicating the index of the one TRP.

[0086] In some embodiments, a terminal device comprises circuitry configured to receive from the network device a configuration indicating that each cell in a cell group serving the terminal device is associated with at least one of a plurality of transmission and reception points (TRPs) coupled to a network device, and in response to detecting a beam failure on a cell in the cell group, to transmit a beam failure recovery request to the network device including TRP information related to the beam failure detected on the cell.

[0087] In some embodiments, each of the plurality of TRPs may be represented by at least one of a control resource set (CORESET) pool index, a CORESET group identifier, an identifier of a set of reference signals (RS) for beam failure detection, an identifier of a set of RSs for new beam identification, spatial relationship information, a sounding reference signal (SRS) resource set, a transmission configuration indicator (TCI) state, and a set of quasi-co-location parameters.

[0088] In some embodiments, the plurality of TRPs includes a first TRP and a second TRP, the cell group includes a first subset of cells associated with the first TRP and a second subset of cells associated with the second TRP, the first subset of cells configured to have a first set of RSs for beam failure detection and a second set of RSs for new beam identification, and the second subset of cells configured to have a third set of RSs for beam failure detection and a fourth set of RSs for new beam identification.

[0089] In some embodiments, the terminal device comprises circuitry configured to: in response to a beam failure being detected based on the first set of RSs, send a first beam failure recovery request to the network device, the first beam failure recovery request including an indication of at least the first TRP or a first subset of the cells; and in response to a beam failure being detected based on the third set of RSs, send a second beam failure recovery request to the network device, the second beam failure recovery request including an indication of at least the second TRP or a second subset of the cells.

[0090] In some embodiments, a cell is associated with multiple TRPs, and the TRP information indicates one of the multiple TRPs associated with a beam obstruction detected on the cell.

[0091] In some embodiments, the TRP information includes an indication of a common TRP index for all cells indicated in the beam failure recovery request.

[0092] In some embodiments, the TRP information includes an indication of the respective TRP index for each of the cells indicated in the beam failure recovery request.

[0093] In some embodiments, the cell is associated with a plurality of TRPs, and the TRP information includes at least one of: first information indicating the number of TRPs associated with a beam failure detected on the cell; second information indicating an index of one of the plurality of TRPs associated with a beam failure detected on the cell; and third information indicating on which TRP of the plurality of TRPs a new beam was identified.

[0094] In some embodiments, a cell is associated with a plurality of TRPs, and the TRP information includes first information indicating the number of TRPs associated with beam obstructions detected on the cell, and second information indicating an RS index for a new beam identified on one of the plurality of TRPs, the RS index indicating the index of the one TRP.

[0095] In some embodiments, the network device comprises circuitry configured to transmit to the terminal device a configuration indicating that each cell in a cell group serving the terminal device is associated with at least one of a plurality of transmission and reception points (TRPs) coupled to the network device, and to receive from the terminal device, in response to detection of a beam failure on a cell in the cell group, a beam failure recovery request including TRP information related to the beam failure detected on the cell.

[0096] In some embodiments, each of the plurality of TRPs may be represented by at least one of a control resource set (CORESET) pool index, a CORESET group identifier, an identifier of a set of reference signals (RS) for beam failure detection, an identifier of a set of RSs for new beam identification, spatial relationship information, a sounding reference signal (SRS) resource set, a transmission configuration indicator (TCI) state, and a set of quasi-co-location parameters.

[0097] In some embodiments, the plurality of TRPs includes a first TRP and a second TRP, the cell group includes a first subset of cells associated with the first TRP and a second subset of cells associated with the second TRP, the first subset of cells configured to have a first set of RSs for beam failure detection and a second set of RSs for new beam identification, and the second subset of cells configured to have a third set of RSs for beam failure detection and a fourth set of RSs for new beam identification.

[0098] In some embodiments, the network device comprises circuitry configured to receive a first beam failure recovery request from the terminal device in response to beam failure being detected based on the first set of RSs, the first beam failure recovery request including an indication of at least the first TRP or a first subset of the cells, and to receive a second beam failure recovery request from the terminal device in response to beam failure being detected based on the third set of RSs, the second beam failure recovery request including an indication of at least the second TRP or a second subset of the cells.

[0099] In some embodiments, a cell is associated with multiple TRPs, and the TRP information indicates one of the multiple TRPs associated with a beam obstruction detected on the cell.

[0100] In some embodiments, the TRP information includes an indication of a common TRP index for all cells indicated in the beam failure recovery request.

[0101] In some embodiments, the TRP information includes an indication of the respective TRP index for each of the cells indicated in the beam failure recovery request.

[0102] In some embodiments, the cell is associated with a plurality of TRPs, and the TRP information includes at least one of: first information indicating the number of TRPs associated with a beam failure detected on the cell; second information indicating an index of one of the plurality of TRPs associated with a beam failure detected on the cell; and third information indicating on which TRP of the plurality of TRPs a new beam was identified.

[0103] In some embodiments, a cell is associated with a plurality of TRPs, and the TRP information includes first information indicating the number of TRPs associated with beam obstructions detected on the cell, and second information indicating an RS index for a new beam identified on one of the plurality of TRPs, the RS index indicating the index of the one TRP.

[0104] Figure 10 is a schematic block diagram of an apparatus 1000 suitable for implementing embodiments of the present disclosure. The apparatus 1000 may be considered another exemplary implementation of the network apparatus 110, the TRP 130, and / or the terminal device 120 as shown in Figure 1. Accordingly, the apparatus 1000 may be implemented in, or as at least a portion of, the network apparatus 110, the TRP 130, and / or the terminal device 120 as shown in Figure 1.

[0105] As shown, the apparatus 1000 includes a processor 1010, a memory 1020 coupled to the processor 1010, a suitable transmitter (TX) and receiver (RX) 1040 coupled to the processor 1010, and a communication interface coupled to the TX / RX 1040. The memory 1020 stores at least a portion of a program 1030. The TX / RX 1040 is used for bidirectional communication. The TX / RX 1040 has at least one antenna to facilitate communication, although the access nodes referred to herein may actually have multiple antennas. The communication interface may represent any interface required for communication with other network elements, such as an X2 interface for bidirectional communication between eNBs, an S1 interface for communication between a mobility management entity (MME) / serving gateway (S-GW) and an eNB, an Un interface for communication between an eNB and a relay node (RN), or a Uu interface for communication between an eNB and a terminal device.

[0106] The program 1030 is assumed to include program instructions that, when executed by an associated processor 1010, enable the device 1000 to operate in accordance with embodiments of the present disclosure, as described herein with reference to Figures 1-9. The embodiments herein may be implemented by computer software executable by the processor 1010 of the device 1000, by hardware, or by a combination of software and hardware. The processor 1010 may be configured to implement various embodiments of the present disclosure. Furthermore, the combination of the processor 1010 and the memory 1020 may form a processing means 1050 suitable for implementing various embodiments of the present disclosure.

[0107] The memory 1020 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology, including, by way of non-limiting example, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. While only one memory 1020 is shown in the device 1000, several physically distinct memory modules may be present within the device 1000. The processor 1010 may be of any type suitable for a local technology network and may include, by way of non-limiting example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 1000 may have multiple processors, for example, application-specific integrated circuit chips time-slaved to a clock that synchronizes the main processor.

[0108] Overall, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executable by a controller, microprocessor, or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described using block diagrams, flowcharts, or other pictorial representations, it should be understood that the blocks, devices, systems, techniques, or methods described herein can be implemented, by way of non-limiting example, in hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or any combination thereof.

[0109] 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 instructions included in program modules, that execute in a device on a target real or virtual processor to perform the processes or methods described above with reference to FIGS. 10 and 11. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or split between program modules as desired. The machine-executable instructions of the program modules may be executed in local or distributed devices. In a distributed device, the program modules may be located in both local and remote storage media.

[0110] Program code for carrying out the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, and when executed by the processor or controller, cause the program code to implement the functions / acts specified in the flowcharts and / or block diagrams. The program code may run entirely on the machine, partially on the machine, as a separate software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0111] The above-described program code may also be embodied on a machine-readable medium, which may be any tangible medium that can contain or store a program used by or associated with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the aforementioned media. More specific examples of machine-readable storage media may include an electrical connection having one or more wires, a portable computer disk, 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 optical disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0112] Although operations have been described in a particular order, it should not be understood that performing these operations in the particular order shown, or in any sequential order, or performing all of the operations described, is required to achieve desirable results. In some cases, multitasking or parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to particular embodiments. Some features that are described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination.

[0113] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the present disclosure, as defined in the appended claims, is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. means for performing beam failure detection for a cell based on two reference signal (RS) sets; and means for transmitting a medium access control (MAC) control element (CE) for beam failure recovery to a network device, wherein the MAC CE comprises: a first field indicating whether a beam failure has been detected for the cell; a second field indicating whether a beam failure is detected for one of the RS sets of the cell or whether the beam failure is detected for both of the RS sets; a third field indicating the presence of a candidate RS identifier (ID) field; a first value of the second field indicates that beam failure is detected for both of the RS sets and that there are two octets including the third field for both of the RS sets; The second value of the second field indicates that a beam failure is detected for one of the RS sets and that there is one octet including the third field for only one RS set of the cell; the second field is an octet different from the two octets and the one octet; Terminal device.

2. The MAC CE further includes a fourth field indicating an RS Set ID. The terminal device according to claim 1 .

3. The MAC CE further includes a fifth field indicating a candidate RS ID. The terminal device according to claim 1 .

4. The fifth field is also included in the one octet. The terminal device according to claim 3 .

5. The fifth field is also contained in the two octets. The terminal device according to claim 3 .

6. A maximum of two PUCCH resources for a scheduling request (SR) are configured, and the two PUCCH resources are associated with at least one of the RS sets. The terminal device according to claim 1 .

7. and means for receiving a medium access control (MAC) control element (CE) for beam fault recovery from a terminal device, wherein the MAC CE comprises: a first field indicating whether beam failure has been detected for a cell configured to have two reference signal (RS) sets for beam failure detection; a second field indicating whether a beam failure is detected for one of the RS sets of the cell or whether the beam failure is detected for both of the RS sets; a third field indicating the presence of a candidate RS identifier (ID) field; a first value of the second field indicates that beam failure is detected for both of the RS sets and that there are two octets including the third field for both of the RS sets; The second value of the second field indicates that a beam failure is detected for one of the RS sets and that there is one octet including the third field for only one RS set of the cell; the second field is an octet different from the two octets and the one octet; Network equipment.

8. The MAC CE further includes a fourth field indicating an RS Set ID. The network device according to claim 7.

9. The MAC CE further includes a fifth field indicating a candidate RS ID. The network device according to claim 7.

10. The fifth field is also included in the one octet.

10. The network device of claim 9.

11. The fifth field is also contained in the two octets.

10. The network device of claim 9.

12. A maximum of two PUCCH resources for a scheduling request (SR) are configured, and the two PUCCH resources are associated with at least one of the RS sets. The network device according to claim 7.

13. 1. A method performed by a terminal device, comprising: performing beam failure detection for the cell based on two reference signal (RS) sets; and transmitting a medium access control (MAC) control element (CE) for beam failure recovery to a network device, the MAC CE comprising: a first field indicating whether a beam failure has been detected for the cell; a second field indicating whether a beam failure is detected for one of the RS sets of the cell or whether the beam failure is detected for both of the RS sets; a third field indicating the presence of a candidate RS identifier (ID) field; a first value of the second field indicates that beam failure is detected for both of the RS sets and that there are two octets including the third field for both of the RS sets; The second value of the second field indicates that a beam failure is detected for one of the RS sets and that there is one octet including the third field for only one RS set of the cell; the second field is an octet different from the two octets and the one octet; method.

14. The MAC CE further includes a fourth field indicating an RS Set ID. The method of claim 13.

15. 1. A method performed by a network device, comprising: receiving a medium access control (MAC) control element (CE) for beam fault recovery from a terminal device, the MAC CE comprising: a first field indicating whether beam failure has been detected for a cell configured to have two reference signal (RS) sets for beam failure detection; a second field indicating whether a beam failure is detected for one of the RS sets of the cell or whether the beam failure is detected for both of the RS sets; a third field indicating the presence of a candidate RS identifier (ID) field; a first value of the second field indicates that beam failure is detected for both of the RS sets and that there are two octets including the third field for both of the RS sets; The second value of the second field indicates that a beam failure is detected for one of the RS sets and that there is one octet including the third field for only one RS set of the cell; the second field is an octet different from the two octets and the one octet; method.

Images