Method and apparatus for transmitting sceil beam failure recovery request

Abstract

This application relates to a method and apparatus for transmitting a Scell beam failure recovery request under 3GPP 5G New Radio (NR) technology. One method includes, in response to detection of a Scell beam failure, calculating a time interval between the detection of the Scell beam failure and an available physical uplink shared channel (PUSCH) after the detection of the Scell beam failure, comparing the time interval to a time threshold, and determining whether to transmit at least one failure component carrier (CC) index associated with the detection of the Scell beam failure in the available PUSCH based on a comparison result between the time interval and the time threshold.

Description

Technical Field

[0001] Embodiments of the present invention generally relate to wireless communication technology, and more particularly to a method and apparatus for transmitting a beam fault recovery request (BFRQ) for a secondary cell (Scell). Background Technology

[0002] Enhancements to 5G New Radio (NR) multiple-input multiple-output (MIMO) have been discussed in RP-181453 of the 3rd Generation Partnership Project (3GPP). This work item aims to specify enhancements for NR MIMO identification. However, in 3GPP Release 16, details of the ScellBFRQ transmission process when the User Equipment (UE) detects at least one Scell ​​beam failure have not yet been discussed in 5G NR technology. Summary of the Invention

[0003] Some embodiments of this application provide a method. The method includes: in response to the detection of an Scell ​​beam fault, calculating a time interval between the detection of the Scell ​​beam fault and an available Physical Uplink Shared Channel (PUSCH) following the detection of the Scell ​​beam fault; comparing the time interval with a time threshold; and determining, based on the comparison result between the time interval and the time threshold, whether to transmit at least one fault component carrier (CC) index associated with the detection of the Scell ​​beam fault in the available PUSCH.

[0004] Some embodiments of this application provide an apparatus for wireless communication. The apparatus includes: a non-transitory computer-readable medium storing computer-executable instructions thereon; a receiving circuitry; a transmitting circuitry; and a processor coupled to the non-transitory computer-readable medium, the receiving circuitry, and the transmitting circuitry, wherein the computer-executable instructions cause the processor to perform the above-described method for transmitting at least one fault CC index.

[0005] Some embodiments of this application provide a method. The method includes: determining whether a Physical Uplink Control Channel (PUCCH) configured to transmit Scell ​​Beam Fault Recovery Request (BFRQ) status information overlaps with another PUCCH in the time domain; and in response to the overlap between the PUCCH configured to transmit Scell ​​BFRQ status information and the other PUCCH, transmitting the Scell ​​BFRQ status information in the other PUCCH.

[0006] Some embodiments of this application provide an apparatus for wireless communication. The apparatus includes: a non-transitory computer-readable medium storing computer-executable instructions thereon; a receiving circuitry; a transmitting circuitry; and a processor coupled to the non-transitory computer-readable medium, the receiving circuitry, and the transmitting circuitry, wherein the computer-executable instructions cause the processor to perform the aforementioned method for transmitting Scell ​​BFRQ state information. Attached Figure Description

[0007] To illustrate the advantages and features of this application, the description of this application is presented by reference to specific embodiments thereof, which are illustrated in the accompanying drawings. These drawings depict only exemplary embodiments of this application and should therefore not be construed as limiting its scope.

[0008] Figure 1 A schematic diagram illustrating an exemplary wireless communication system 100 according to some embodiments of this application;

[0009] Figure 2 A flowchart illustrating a method 200 for wireless communication according to some embodiments of this application;

[0010] Figure 3 This application describes an exemplary Scell ​​BFRQ procedure based on some embodiments of the present application;

[0011] Figure 4 This application describes an exemplary Scell ​​BFRQ procedure based on some embodiments of the present application;

[0012] Figure 5 This application describes further exemplary Scell ​​BFRQ procedures based on some embodiments of the present application;

[0013] Figure 6 This application describes additional exemplary Scell ​​BFRQ procedures according to some embodiments of the present application;

[0014] Figure 7 Another flowchart illustrating a method for wireless communication according to some embodiments of this application; and

[0015] Figure 8 A block diagram illustrating an exemplary device according to some embodiments of this application. Detailed Implementation

[0016] The detailed description of the accompanying drawings is intended to illustrate preferred embodiments of the present application and is not intended to represent the only form in which the present application may be practiced. It should be understood that the same or equivalent functionality may be achieved through different embodiments intended to be covered within the spirit and scope of the present application.

[0017] Reference will now be made in detail to some embodiments of this application, examples of which are illustrated in the accompanying drawings. To facilitate understanding, embodiments are provided under specific network architectures and new service scenarios, such as 3GPP 5G, 3GPP LTE Release 8, etc. It is understood that all embodiments of this application are applicable to similar technical problems as network architectures and new service scenarios develop; furthermore, the terminology used in this application may change without affecting the principles of this application.

[0018] Figure 1 A schematic diagram illustrating an exemplary wireless communication system 100 according to some embodiments of this application is provided.

[0019] like Figure 1 As illustrated and shown, the wireless communication system 100 includes at least one user equipment (UE) 101 and at least one base station (BS) 102. Specifically, for illustrative purposes, the wireless communication system 100 includes only one UE 101 and one BS 102. Although Figure 1 A specific number of UEs 101 and BSs 102 are depicted, but it is understood that any number of UEs 101 and BSs 102 may be included in the wireless communication system 100.

[0020] (Several) UEs 101 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (PDAs), tablet computers, smart TVs (e.g., TVs connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, and modems), Internet of Things (IoT) devices, etc. According to some embodiments of this application, (several) UEs 101 may include portable wireless communication devices, smartphones, cellular phones, flip phones, devices with a user identity module, personal computers, selective call receivers, or any other devices capable of transmitting and receiving communication signals on a wireless network. In some embodiments of this application, (several) UEs 101 include wearable devices, such as smartwatches, fitness trackers, optical head-mounted displays, etc. Furthermore, (several) UEs 101 may be referred to as user units, mobile devices, mobile stations, users, terminals, mobile terminals, wireless terminals, fixed terminals, user stations, user terminals, or devices, or described using other terms used in the art. (Some) UE101 can communicate directly with BS 102 via uplink (UL) communication signals.

[0021] In some embodiments of this application, each of the UEs 101 may be deployed with an IoT application, an eMBB application, and / or a URLLC application. It is considered that the specific types of applications deployed in the UEs 101 may be varied and are not limited.

[0022] (Several) BS 102s may be distributed across a geographical area. In some embodiments of this application, each of (several) BS 102s may also be referred to as an access point, access terminal, base station, base unit, macro cell, node B, evolved Node B (eNB), gNB, NG-RAN (Next Generation Radio Access Network) node, home node B, relay node, or device, or described using other terms used in the art. (Several) BS 102s are typically part of a radio access network, which may include one or more controllers communicatively coupled to one or more corresponding BS 102s. (Several) BS 102s may communicate directly with each other.

[0023] The wireless communication system 100 is compatible with any type of network capable of transmitting and receiving wireless communication signals. For example, the wireless communication system 100 is compatible with wireless communication networks, cellular telephone networks, time division multiple access (TDMA) based networks, code division multiple access (CDMA) based networks, orthogonal frequency division multiple access (OFDMA) based networks, LTE networks, 3GPP-based networks, 3GPP 5G networks, satellite communication networks, high-altitude platform networks, and / or other communication networks.

[0024] In some embodiments of this application, the wireless communication system 100 is compatible with 5G NR according to the 3GPP protocol, wherein (a plurality of) BS 102 use an OFDM modulation scheme to transmit data on DL and (a plurality of) UE 101 use a single-carrier frequency division multiple access (SC-FDMA) or OFDM scheme to transmit data on UL. However, more generally, the wireless communication system 100 may implement other open or proprietary communication protocols, such as WiMAX and other protocols.

[0025] In some embodiments of this application, the (several) BS 102 may use other communication protocols, such as the IEEE 802.11 wireless communication protocol family, for communication. Furthermore, in some embodiments of this application, the (several) BS 102 may communicate within licensed spectrum, while in other embodiments, the (several) BS 102 may communicate within unlicensed spectrum. This application is not intended to be limited to any particular wireless communication system architecture or protocol implementation. In still other embodiments of this application, the (several) BS 102 may use the 3GPP 5G protocol to communicate with the (several) UE 101.

[0026] In 3GPP 5G NR technology, when a UE detects one or more Scell ​​beam faults, the UE needs to transmit the BFRQ associated with the Scell ​​beam fault to the BS. As defined in 3GPP TS 38.213, the UE can be configured with a set of resources named Scell ​​for fault detection, and the UE only detects an Scell ​​beam fault when it detects that the radio link quality of all resources in the set of resources is worse than a threshold. Furthermore, as specified in NR Release 16, the UE sends an indication of the detected Scell ​​beam fault in one step, and in another step sends a fault CC index corresponding to the detected Scell ​​beam fault and an available beam index corresponding to the fault CC index in the MAC CE. Currently, in some solutions under 5G NR, the BFRQ associated with one or more Scell ​​beam faults is carried by one or more dedicated PUCCH resources in the primary cell (PCell) or primary / secondary cell (PScell). However, the issues involve how to notify the BS of at least one Scell ​​requesting Scell ​​beam fault recovery (BFR), how to multiplex Scell ​​BFRQ status information with other uplink (UL) transmissions, and when BFRQ can be transmitted on the PUSCH without resolving the Scell ​​BFRQ PUCCH. The Scell ​​BFRQ PUCCH is a PUCCH configured to transmit Scell ​​BFRQ status information associated with the detection of Scell ​​beam faults. In some embodiments of this application, the Scell ​​BFRQ PUCCH can also be expressed as a PUCCH for (several) Scell ​​beam faults.

[0027] Figure 2 A flowchart illustrating a method 200 for wireless communication according to some embodiments of this application.

[0028] In such Figure 2 In the exemplary method 200 described and illustrated, in step 201, in response to the detection of Scell ​​beam fault, the UE (such as...) Figure 1 The UE 101 described and illustrated calculates the time interval between the Scell ​​beam failure and the first available PUSCH after the Scell ​​beam failure. The first available PUSCH after the Scell ​​beam failure represents the PUSCH transmitted by the UE or scheduled by UL downlink control information (DCI) configured by higher layers and transmitted first after the Scell ​​beam failure. The first available PUSCH is not a PUSCH for retransmission because a PUSCH for retransmission can only transmit the same data as the original transmission.

[0029] In some embodiments of this application, in step 201 of exemplary method 200, the UE calculates the time interval between an Scell ​​beam failure and the first available PUSCH after the Scell ​​beam failure, for example, the end time of the Scell ​​beam failure and the start time of the first available PUSCH after the Scell ​​beam failure. For example, in exemplary method 200, after detecting one or more Scell ​​beam failures, the UE calculates the time interval between the end time of the last Scell ​​beam failure and the start time of the first available PUSCH after all Scell ​​beam failures.

[0030] In step 202, the UE compares the time interval calculated in step 201 with a time threshold to determine whether the time interval is greater than, equal to or less than the time threshold.

[0031] In some embodiments of this application, the time threshold represents the shortest time between the UE detecting an Scell ​​beam fault and the PUSCH on which the Scell ​​BFRQ can be multiplexed. The time threshold is associated with the UE's processing capabilities. The time threshold can be configured by Radio Resource Control (RRC) signaling or can be predefined. In some embodiments of this application, the time threshold (e.g., as in this application) Figure 3-6 The “threshold” described and shown in the document can be named “t_threshold”.

[0032] In step 203, the UE determines, based on the comparison between the time interval and the time threshold, whether to transmit at least one fault CC index associated with the Scell ​​beam fault in the first available PUSCH.

[0033] In some embodiments of this application, Scell ​​BFRQ status information associated with one or more Scell ​​beam faults is carried by one or more dedicated PUCCH resources used for BFRQ. In some embodiments of this application, the Scell ​​BFRQ status information associated with one or more Scell ​​beam faults may also be named "BFRQ status information". According to some embodiments of this application, the Scell ​​BFRQ status information can be transmitted in a manner similar to a scheduling request (SR). According to some embodiments of this application, the Scell ​​BFRQ status information may have a higher priority than an SR.

[0034] In some embodiments of this application, the Scell ​​BFRQ status information associated with one or more Scell ​​beam faults includes a positive Scell ​​BFRQ, which indicates a request for uplink resources to transmit at least one faulty component carrier (CC) index associated with one or more Scell ​​beam faults. In some other embodiments of this application, the Scell ​​BFRQ status information associated with one or more Scell ​​beam faults includes a negative Scell ​​BFRQ, which indicates a non-request for uplink resources to transmit at least one faulty CC index.

[0035] In some embodiments of this application, the UE transmits the Scell ​​BFRQ state information by rate matching the Scell ​​BFRQ state information with the data in the PUSCH. In other embodiments of this application, the UE transmits the Scell ​​BFRQ state information by puncturing the Scell ​​BFRQ state information in the PUSCH.

[0036] In some embodiments of this application, the BFRQ associated with one Scell ​​beam fault includes one fault CC index associated with the Scell ​​beam fault. When the UE detects multiple Scell ​​beam faults, the BFRQ associated with these Scell ​​beam faults includes more than one fault CC index associated with these Scell ​​beam faults. For example, the BFRQ associated with three Scell ​​beam faults may include three fault CC indices associated with the three Scell ​​beam faults.

[0037] In some embodiments of this application, the BFRQ associated with one or more Scell ​​beam faults further includes at least one available beam index corresponding to at least one fault CC index. Therefore, the UE transmits both the at least one fault CC index and the corresponding at least one available beam index to the BS (e.g., as...). Figure 1 BS 102 as described and shown in the document.

[0038] In some embodiments of this application, in step 203 of the exemplary method 200, in response to a time interval equal to or greater than a time threshold, the UE transmits at least one faulty CC index in the first available PUSCH. In some embodiments of this application, in step 203 of the exemplary method 200, in response to a time interval less than a time threshold, the UE determines not to transmit at least one faulty CC index in the first available PUSCH.

[0039] In some embodiments of this application, in step 203 of the exemplary method 200, the UE further determines whether to transmit at least one available beam index corresponding to the fault CC index in the first available PUSCH based on a comparison between the time interval and a time threshold.

[0040] In some embodiments of this application, a BFRQ associated with an Scell ​​beam fault is carried in the Media Access Control-Control Element (MAC-CE). For example, at least one fault CC index is carried in the MAC-CE. For a further example, in addition to the at least one fault CC index, at least one available beam index corresponding to the at least one fault CC index is also carried in the MAC-CE.

[0041] In some embodiments of this application, when the UE detects that a beam has failed in at least one Scell ​​and there is a PUSCH that will be transmitted after the detection of the beam failure, if the time interval between the detection of the beam failure and the PUSCH is sufficient to perform the transmission of the Scell ​​BFRQ, then the UE may transmit the Scell ​​BFRQ in the PUSCH to indicate (a number of) fault CC indices and (a number of) corresponding available beam indices.

[0042] Figure 3 This describes an exemplary Scell ​​BFRQ procedure according to some embodiments of this application. For example... Figure 3 The exemplary Scell ​​BFRQ procedure described and demonstrated is performed by the UE (e.g., such as...). Figure 1 The UE 101 described and shown in the document is used to execute this.

[0043] Specifically, such as Figure 3 The descriptions and demonstrations herein, in the time domain (i.e., such as...) Figure 3 In the “T” described and illustrated, the UE receives the UL DCI in time slot n and transmits the PUSCH in time slot m, where the PUSCH transmitted in time slot m is scheduled by the UL DCI in time slot n. The UE will decode the UL DCI received in time slot n and prepare data for the PUSCH transmission performed in time slot m. Because the UE needs time to perform these processes, there is a time interval between the UL DCI in time slot n and the PUSCH transmission in time slot m starting from time “t2”, i.e., as shown in the diagram. Figure 3The time interval between time "t3" and time "t2" is described and shown in the diagram. If the UE detects at least one Scell ​​beam fault at time "t1", then the UE knows the fault CC index(s) and corresponding available beam index(s) associated with the at least one Scell ​​beam fault. The UE can prepare a MAC CE to report the fault CC index(s) and / or corresponding available beam index(s) to the BS (e.g., as shown in the diagram). Figure 1 (As described and shown in BS 102). The MAC CE that indicates (a number of) fault CC indices and / or (a number of) corresponding available beam indices to the BS may be named Scell ​​BFRQ MAC CE.

[0044] When the UE knows that the first available PUSCH after beam fault detection will be transmitted in time slot m, the UE can determine whether MAC CE can be transmitted in the first available PUSCH.

[0045] According to some embodiments of this application, one possible method is to determine whether there is sufficient time for the UE to transmit the Scell ​​BFRQ MAC CE in the first available PUSCH. For example, the UE can calculate the time interval between the end time of the Scell ​​beam failure and the start time of the first available PUSCH to be transmitted, i.e., the time interval between time "t1" and time "t2". The UE can determine whether the time is sufficient by comparing the time interval with a time threshold. As described above, since the UE needs both time to prepare the Scell ​​BFRQ MAC CE and time to multiplex the Scell ​​BFRQ MAC CE on the PUSCH, it needs to detect the shortest time between the Scell ​​beam failure and the multiplexing of the Scell ​​BFRQ MAC CE in the PUSCH. The time threshold can be equal to or greater than the shortest time.

[0046] Time threshold at Figure 3 The threshold is displayed in the middle. According to Figure 3 In the embodiments shown, since the UE does not need to detect the UL DCI at t1, the time threshold is no greater than the time interval between the UL DCI and the first available PUSCH, for example, as Figure 3 The time interval between "t3" and "t2" is explained and shown in the documentation. Furthermore, the Scell ​​BFRQ MAC CE can only be multiplexed on the first available PUSCH if the first available PUSCH has sufficient resource elements (REs) to carry the entire MAC CE.

[0047] In some embodiments of this application, the UE does not transmit Scell ​​BFRQ state information. When the PUSCH is not used for retransmission and has enough REs to carry the entire MAC CE, the UE can directly transmit the Scell ​​BFRQ MAC CE in the PUSCH.

[0048] When all the above conditions are met, for example, the first available PUSCH contains enough REs to carry the Scell ​​BFRQ MACCE and the time interval is not less than a threshold (e.g., "time interval >= threshold"), such as Figure 3 When required (as described and shown in the documentation), the UE will transmit the Scell ​​BFRQ MAC CE on the first available PUSCH, without transmitting the Scell ​​BFRQ status information. That is, the Scell ​​BFRQ MAC CE is transmitted on the first available PUSCH or multiplexed with other UL data, such as... Figure 3 The explanations and demonstrations are as follows.

[0049] According to such Figure 3 In the embodiments described and illustrated, where the ScellBFRQ MAC CE can be multiplexed in the first available PUSCH, the UE may not transmit the Scell ​​BFRQ PUCCH. Specifically, if the PUSCH is scheduled by the UL DCI ending at time "t3" and no new Scell ​​beam fault is detected between times "t1" and "t2", then the UE will not transmit the Scell ​​BFRQ PUCCH between times "t1" and "t2", even if there are PUCCH resources for Scell ​​BFRQ status information configured by the BS. Figure 3 The same applies to (not shown in the text).

[0050] Figure 4 This describes an exemplary Scell ​​BFRQ procedure according to some embodiments of this application. Figure 3 Similarly, such as Figure 4 The exemplary Scell ​​BFRQ procedure described and demonstrated is performed by the UE (e.g., such as...). Figure 1 The UE 101 described and shown in the document is used to execute this.

[0051] exist Figure 4 In the embodiments, the steps and operations performed by the UE are the same as those in the embodiments. Figure 3 The steps and operations are similar to those in the previous one. Figure 3 and 4 The differences between the embodiments include Figure 4 In the embodiment, the time interval between the detection of the Scell ​​beam fault and the start time of the first available PUSCH (i.e., as shown in the example) Figure 4The "time interval" described and shown in the document is less than the time threshold (i.e., as...). Figure 4 (The "threshold" described and shown in the document). In this case, the Scell ​​BFRQ MAC CE cannot be transmitted in the first available PUSCH because the minimum time requirement for multiplexing the Scell ​​BFRQ MAC CE in the PUSCH is not met. Therefore, the UE can transmit a positive Scell ​​BFRQ state in a time slot configured for the Scell ​​BFRQ PUCCH resource after time t2, or if a PUSCH exists (which satisfies the requirement for multiplexing the Scell ​​BFRQ MAC CE in the PUSCH). Figure 4 As explained and shown in the document, if the minimum time requirement for multiplexing Scell ​​BFRQ MAC CE in PUSCH in the next time slot after time slot m is met, then the UE can send Scell ​​BFRQ MACCE.

[0052] More specifically, such as Figure 4 The descriptions and demonstrations herein, if in the case of BS (e.g., such as Figure 1 If the minimum time requirement is not met when configuring Scell ​​BFRQ PUCCH in BS 102 as described and shown, then the UE will transmit Scell ​​BFRQ PUCCH during the time interval between time "t1" and "t2".

[0053] In some embodiments of this application, when uplink control information (UCI) is multiplexed on the PUSCH, the SR state is not transmitted on the PUSCH. Although the Scell ​​BFRQ state information is similar to SR, the multiplexing scheme of the Scell ​​BFRQ state information on the PUSCH may differ from that of the SR state if the Scell ​​BFRQ state information has a higher priority than SR.

[0054] As in Figure 3 and 4 As discussed in the embodiments, whether Scell ​​BFRQ MAC CE can be transmitted in the PUSCH without transmitting Scell ​​BFRQ state information depends on the time interval between the detection of Scell ​​beam fault and the PUSCH, as well as the capabilities of the PUSCH. As described above, transmitting Scell ​​BFRQ MAC CE in the PUSCH means that the time interval is not less than a time threshold and the PUSCH has enough available REs to carry the Scell ​​BFRQ MAC CE. In other words, the UE does not need to request UL resources to transmit the Scell ​​BFRQ MAC CE. In this case, if the Scell ​​BFRQ PUSCH overlaps with the PUSCH in the time domain, then the UE does not need to transmit Scell ​​BFRQ state information.

[0055] Additionally, the inability to transmit Scell ​​BFRQ MAC CE in the PUSCH means that the time interval is less than a time threshold or that the PUSCH capability does not allow for Scell ​​BFRQ MAC CE. Therefore, the UE needs to request UL resources to transmit the Scell ​​BFRQ MAC CE. In this case, if the Scell ​​BFRQ PUCCH overlaps with the PUSCH, the UE needs to transmit Scell ​​BFRQ status information.

[0056] On the BS side, the BS has no information about the existence of Scell ​​BFRQ or whether Scell ​​BFRQ MAC CE can be transmitted on the PUSCH. Therefore, if the Scell ​​BFRQ PUCCH overlaps with the PUSCH, the BS can always detect the Scell ​​BFRQ status information on the PUSCH.

[0057] The UE can transmit Scell ​​BFRQ status information on the PUSCH to report to the BS whether UL resources are needed to transmit Scell ​​BFRQ MAC CE. A positive Scell ​​BFRQ status message means that the UE needs UL resources to transmit Scell ​​BFRQ MAC CE, while a negative Scell ​​BFRQ status message means that the UE does not need UL resources to transmit Scell ​​BFRQ MAC CE.

[0058] In some embodiments of this application, when Scell ​​BFRQ MAC CE cannot be transmitted on PUSCH and PUSCH overlaps with Scell ​​BFRQ PUCCH, the UE can transmit positive Scell ​​BFRQ status information to BS on PUSCH so as to report to BS that UL resources are needed to transmit Scell ​​BFRQ MAC CE.

[0059] In some embodiments of this application, when an Scell ​​BFRQ MAC CE is transmitted in the PUSCH and the PUSCH overlaps with an Scell ​​BFRQ PUCCH, the UE may transmit negative Scell ​​BFRQ state information to the BS in the PUSCH to report that UL resources are not needed to transmit the Scell ​​BFRQ MAC CE. In some other embodiments of this application, when an Scell ​​BFRQ MAC CE is transmitted in the PUSCH and the PUSCH overlaps with an Scell ​​BFRQ PUCCH, the UE may not transmit the Scell ​​BFRQ state information to the BS, which also indicates that UL resources are not needed to transmit the Scell ​​BFRQ MAC CE.

[0060] Figure 5This describes further exemplary Scell ​​BFRQ procedures according to some embodiments of this application. Figure 3 and 4 Similarly, such as Figure 5 The exemplary Scell ​​BFRQ procedure described and demonstrated is performed by the UE (e.g., such as...). Figure 1 The UE 101 described and shown in the document is used to execute this.

[0061] exist Figure 5 In the embodiments, the steps and operations performed by the UE are the same as those in the embodiments. Figure 3 The steps and operations are similar to those in the previous one. Figure 3 and 5 The similarities between the embodiments include the UL DCI transmitted in time slot n, the PUSCH scheduled for transmission in time slot m for the UE, and the time interval between the detection of Scell ​​beam fault and the start time of the PUSCH (i.e., as shown in the original text). Figure 5 The "time interval" described and shown in the document is not less than the time threshold (i.e., such as...). Figure 5 As explained and shown in the document, the "threshold" is used, and therefore, the UE can transmit or multiplex Scell ​​BFRQ MAC CE in the PUSCH in time slot m because the shortest time requirement for multiplexing Scell ​​BFRQ MAC CE in the PUSCH in time slot m is met.

[0062] Figure 3 and 5 The differences between the embodiments include Figure 5 In the embodiment, the UL DCI transmitted in time slot n in time slot m is transmitted in the time domain (i.e., as shown in the example). Figure 5 The PUSCH scheduled in the “T” section (described and shown) is also transmitted in time slot m, along with the ScellBFRQ PUCCH. Furthermore, the ScellBFRQ PUCCH overlaps with the PUSCH in the time domain.

[0063] More specifically, in Figure 5 In this embodiment, if the UE detects an Scell ​​beam fault at time point "t1", the UE will first determine whether it can transmit the Scell ​​BFRQ MAC CE in the PUSCH. Since the time interval between the detection of the Scell ​​beam fault and the start time of the PUSCH is not less than a time threshold, the UE can transmit the Scell ​​BFRQ MAC CE in the PUSCH, such as... Figure 5 As explained and demonstrated in the document. Therefore, the UE does not require UL resources to transmit Scell ​​BFRQ MAC CE.

[0064] In such Figure 5In one example illustrated in the diagram, the UE can transmit the negative Scell ​​BFRQ status information to the BS in the PUSCH (e.g., as shown in the diagram). Figure 1 The BS 102 described and illustrated indicates that UL resources are not required to transmit the Scell ​​BFRQ MAC CE. In another instance, the UE may not transmit the Scell ​​BFRQ status information in the PUSCH, which also indicates that UL resources are not required to transmit the Scell ​​BFRQ MAC CE.

[0065] Figure 6 This describes additional exemplary Scell ​​BFRQ procedures according to some embodiments of this application. Figure 3-5 Similarly, such as Figure 6 The exemplary Scell ​​BFRQ procedure described and demonstrated is performed by the UE (e.g., such as...). Figure 1 The UE 101 described and shown in the document is used to execute this.

[0066] exist Figure 6 In the embodiments, the steps and operations performed by the UE are the same as those in the embodiments. Figure 4 The steps and operations are similar to those in the previous one. Figure 4 and 6 The similarities between the embodiments include the UL DCI transmitted in time slot n, the PUSCH scheduled for transmission in time slot m for the UE, and the time interval between the detection of Scell ​​beam fault and the start time of the PUSCH (i.e., as shown in the original text). Figure 6 The "time interval" described and shown in the document is less than the time threshold (i.e., as...). Figure 6 As explained and shown in the document, the "threshold" is not met, and therefore, the UE cannot transmit or multiplex Scell ​​BFRQ MAC CE in the PUSCH in time slot m because the minimum time requirement for multiplexing Scell ​​BFRQ MAC CE in the PUSCH in time slot m is not met.

[0067] Figure 4 and 6 The differences between the embodiments include Figure 6 In the embodiment, the UL DCI transmitted in time slot n in time slot m is transmitted in the time domain (i.e., as shown in the example). Figure 6 The PUSCH scheduled in "T" (as explained and shown) is also transmitted in time slot m, along with the ScellBFRQ PUCCH. Furthermore, the ScellBFRQ PUCCH overlaps with the PUSCH in the time domain. In this respect, Figure 6 Implementation examples and Figure 5 The implementation examples are similar.

[0068] More specifically, in Figure 6In this embodiment, if the UE detects an Scell ​​beam fault at time point "t1", the UE will first determine whether it can transmit the Scell ​​BFRQ MAC CE in the PUSCH. Since the time interval between the detection of the Scell ​​beam fault and the start time of the PUSCH is less than a time threshold, the UE cannot transmit the Scell ​​BFRQ MAC CE in the PUSCH. Figure 6 As explained and demonstrated in the document. Therefore, the UE requires UL resources to transmit the Scell ​​BFRQ MAC CE. For example, as... Figure 6 As explained and demonstrated, the UE can transmit the positive Scell ​​BFRQ status information to the BS in the PUSCH (e.g., as shown in the diagram). Figure 1 As described and shown in BS 102, this indicates the need for UL resources to transmit Scell ​​BFRQ MAC CE.

[0069] The details described in all the foregoing embodiments of this application are applicable to... Figure 3-6 Examples include (in particular, how to notify the BS of at least one Scell ​​requesting BFR, how to multiplex Scell ​​BFRQ status information together with other UL transmissions, and when Scell ​​BFRQ MAC CE can be transmitted on the PUSCH without an Scell ​​BFRQ PUCCH, as explained and described above).

[0070] For example, in such Figure 2 In the exemplary method 200 described and illustrated, the UE further determines whether the PUCCH configured to transmit Scell ​​BFRQ state information associated with the detection of Scell ​​beam fault overlaps with a first available PUSCH in the time domain. In response to the PUCCH configured to transmit Scell ​​BFRQ state information overlapping with the first available PUSCH in the time domain, the UE transmits the Scell ​​BFRQ state information in the first available PUSCH. The UE can transmit the Scell ​​BFRQ state information by rate matching the Scell ​​BFRQ state information with data in the first available PUSCH. The UE can also transmit the Scell ​​BFRQ state information by puncturing it in the first available PUSCH.

[0071] In addition, in such Figure 2In the exemplary method 200 described and illustrated, when at least one fault CC index is transmitted in the first available PUSCH, the UE may transmit a negative Scell ​​BFRQ in the first available PUSCH. Alternatively, when at least one fault CC index is not transmitted in the first available PUSCH, the UE may transmit a positive Scell ​​BFRQ in the first available PUSCH. For example, the Scell ​​BFRQ status information transmitted by the UE has a higher priority than the scheduling request (SR).

[0072] Additionally, there is a possibility that the UE is configured to transmit K PUCCHs in a time slot for the corresponding K normal SRs, excluding Scell ​​BFRQ status information. For example, the UE transmits these K PUCCHs in ascending or descending order of a set of schedulingRequestResourceId values. There is a possibility that SR transmissions in the time slot may overlap with the transmission of PUCCHs with HARQ-ACK information from the UE. There is another possibility that SR transmissions in the time slot may overlap with the transmission of PUCCHs with (some) CSI reports from the UE. When the Scell ​​BFRQ PUCCH overlaps with the same transmission of a PUCCH with HARQ-ACK information or with the transmission of a PUCCH with (some) CSI reports from the UE in the time slot, normal SRs and Scell ​​BFRQ status information, HARQ-ACK information, and / or CSIs can be multiplexed together. Figure 7 Some exemplary embodiments are described herein.

[0073] Figure 7 Another flowchart illustrating a method for wireless communication according to some embodiments of this application is provided.

[0074] In such Figure 7 In the exemplary method 700 described and illustrated, in step 701, the UE (e.g., as shown in the figure) Figure 1 The UE 101 described and illustrated determines whether the PUCCH configured to transmit Scell ​​BFRQ state information (i.e., the Scell ​​BFRQ PUCCH) overlaps with another PUCCH in the time domain. In step 702, in response to the PUCCH configured to transmit Scell ​​BFRQ state information overlapping with the other PUCCH, the UE transmits the Scell ​​BFRQ state information to the BS (e.g., as shown in the diagram) in the other PUCCH. Figure 1 BS 102 as described and shown in the document.

[0075] The details described in all the foregoing embodiments of this application are applicable to... Figure 7Examples of implementations, particularly those relating to Scell ​​BFRQ status information as explained and described above.

[0076] In some embodiments of this application, the Scell ​​BFRQ state information is similar to the SR, but the Scell ​​BFRQ state information has a higher priority than the normal SR, and the other PUCCH is used to transmit at least one of Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) and Channel State Information (CSI). Therefore, the Scell ​​BFRQ state information can be multiplexed in the PUCCH carrying HARQ-ACK and / or CSI.

[0077] For example, the Scell ​​BFRQ status information is represented by one or more bits, and the total number of these bits is calculated by the equation ceil(log2(K+2)), where K represents the total number of PUCCHs configured to carry SR that overlap with the other PUCCH mentioned above. Therefore, ceil(log2(K+2)) bits can be multiplexed in PUCCHs carrying HARQ-ACK and / or CSI, and the status K+2 indicated by the ceil(log2(K+2)) bits indicates the presence of a positive Scell ​​BFRQ. Considering that the Scell ​​BFRQ status information has a higher priority than a normal SR, if a positive Scell ​​BFRQ exists, the UE will transmit status K+2 regardless of whether a normal positive SR exists.

[0078] In such Figure 7 In the exemplary method 700 described and illustrated, the UE can determine the total number of PUCCHs configured to carry SR that overlap with the other PUCCH mentioned above.

[0079] In some embodiments of this application, the aforementioned additional PUCCH may carry a UCI with more than two bits. For example, the aforementioned additional PUCCH used for HARQ-ACK information or(s) CSI reports is format 2, format 3, or format 4 as defined in TS 38.213. Therefore, one or more bits calculated by ceil(log2(K+1)) may represent the corresponding SR in ascending order of the schedulingRequestResourceId value and may be multiplexed in the PUCCH carrying HARQ-ACK and / or CSI.

[0080] The details described in all the foregoing embodiments of this application (e.g., how to notify the BS of at least one Scell ​​requesting a BFR, how to multiplex Scell ​​BFRQ status information with other UL transmissions together, and when a BFRQ can be transmitted on the PUSCH without an Scell ​​BFRQ PUCCH, as explained and described above) are applicable as follows: Figure 2-6 The embodiments described and shown herein.

[0081] Figure 8 Block diagrams illustrating exemplary devices according to some embodiments of this application. References Figure 8 The device 800 includes a receiving circuit system 802, a transmitting circuit system 804, a processor 806, and a non-transitory computer-readable medium 808. The processor 806 is coupled to the non-transitory computer-readable medium 808, the receiving circuit system 802, and the transmitting circuit system 804.

[0082] After consideration, for the sake of simplicity, Figure 8 Some components are omitted. In some embodiments, the receiving circuitry system 802 and the transmitting circuitry system 804 may be integrated into a single component (e.g., a transceiver).

[0083] In some embodiments, the non-transitory computer-readable medium 808 may store thereon computer-executable instructions that cause the processor to perform operations relating to (a few) UEs as described above. For example, when executing the computer-executable instructions stored in the non-transitory computer-readable medium 808, the processor 806 executes... Figure 2 The method includes: processor 806 calculating a time interval between an Scell ​​beam failure and a first available PUSCH following an Scell ​​beam failure; and based on a comparison of the time interval with a time threshold, processor 806 determining whether to transmit at least one fault CC index associated with the Scell ​​beam failure in the first available PUSCH.

[0084] In some embodiments, the non-transitory computer-readable medium 808 may store thereon computer-executable instructions that cause the processor to perform operations relating to (a number of) BS as described above. For example, when executing the computer-executable instructions stored in the non-transitory computer-readable medium 808, the processor 806 executes... Figure 7 The method includes: processor 806 determining whether a PUCCH configured to transmit Scell ​​BFRQ state information overlaps with another PUCCH in the time domain; and in response to the overlap, processor 806 transmitting the Scell ​​BFRQ state information in the other PUCCH.

[0085] The method of this application can be implemented on a programmable processor. However, the controller, flowchart, and module can also be implemented on general-purpose or special-purpose computers, programmable microprocessors or microcontrollers and peripheral integrated circuit elements, integrated circuits, hardware electronics or logic circuits (e.g., discrete element circuits), programmable logic devices, etc. Generally, any device on which a finite state machine capable of implementing the flowchart shown in the figures resides can be used to implement the processor function of this application.

[0086] Those skilled in the art will understand that the steps of the methods described in conjunction with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of both. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. Additionally, in some aspects, the steps of the method may reside as one or any combination or set of code and / or instructions on a non-transitory computer-readable medium that may be incorporated into a computer program product.

[0087] While this disclosure has been described in conjunction with specific embodiments thereof, it will be apparent to those skilled in the art that many alternatives, modifications, and variations will be readily apparent. For example, various components of the described embodiments may be interchanged, added to, or substituted in other embodiments. Moreover, not all elements in each figure are essential to the operation of the disclosed embodiments. For example, those skilled in the art will be able to make and use the teachings of this disclosure by simply employing the elements of the independent claims. Therefore, the embodiments of this disclosure as set forth herein are intended to be illustrative rather than restrictive. Various changes may be made without departing from the spirit and scope of this disclosure.

[0088] In this document, the term "comprises" or any other variation thereof is intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but may also include other elements not expressly listed or inherent to the process, method, article, or apparatus. Elements beginning with "a / an," etc., do not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element, unless further constraints are imposed. Furthermore, the term "another" is defined as at least a second or more. As used herein, the terms "comprising," "having," etc., are defined as "including."

Claims

1. A method performed by a user equipment, the method comprising: Determine whether the first physical uplink control channel (PUCCH), configured to transmit secondary cell Scell ​​beam fault recovery request (BFRQ) status information, overlaps with the second PUCCH in the time domain; and In response to the overlap of the first PUCCH configured to transmit the Scell ​​BFRQ status information and the second PUCCH, the Scell ​​BFRQ status information is transmitted in the second PUCCH. The Scell ​​BFRQ state information is represented by one or more bits, and the total number of the one or more bits is calculated by the equation ceil(log2(K+2)), where K represents the total number of PUCCHs configured to carry SR that overlap with the second PUCCH.

2. The method of claim 1, wherein the Scell ​​BFRQ status information includes a positive Scell ​​BFRQ or a negative Scell ​​BFRQ, wherein the positive Scell ​​BFRQ indicates a request for uplink resources to transmit at least one fault component carrier (CC) index associated with the detection of the Scell ​​beam fault, and the negative Scell ​​BFRQ indicates no request for uplink resources to transmit the at least one fault CC index.

3. The method according to claim 1, wherein the Scell ​​BFRQ status information has a higher priority than the scheduling request SR.

4. The method of claim 3, wherein the second PUCCH is used to transmit at least one of Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) and Channel State Information (CSI), and the method further comprises: Determine the total number of PUCCHs configured to carry scheduling requests (SRs) that overlap with the second PUCCH.

5. The method of claim 1, wherein the second PUCCH carries uplink control information (UCI) having more than two bits.

6. A processor for wireless communication, comprising: At least one controller, coupled to at least one memory and configured such that the processor: Determine whether the first physical uplink control channel (PUCCH), configured to transmit secondary cell Scell ​​beam fault recovery request (BFRQ) status information, overlaps with the second PUCCH in the time domain; and In response to the overlap of the first PUCCH configured to transmit the Scell ​​BFRQ status information and the second PUCCH, the Scell ​​BFRQ status information is transmitted in the second PUCCH. The Scell ​​BFRQ state information is represented by one or more bits, and the total number of the one or more bits is calculated by the equation ceil(log2(K+2)), where K represents the total number of PUCCHs configured to carry SR that overlap with the second PUCCH.

7. A user equipment (UE) for wireless communication, the UE comprising: At least one memory; and At least one processor, coupled to at least one memory and configured such that the UE: Determine whether the first physical uplink control channel (PUCCH), configured to transmit secondary cell Scell ​​beam fault recovery request (BFRQ) status information, overlaps with the second PUCCH in the time domain; and In response to the overlap of the first PUCCH configured to transmit the Scell ​​BFRQ status information and the second PUCCH, the Scell ​​BFRQ status information is transmitted in the second PUCCH. The Scell ​​BFRQ state information is represented by one or more bits, and the total number of the one or more bits is calculated by the equation ceil(log2(K+2)), where K represents the total number of PUCCHs configured to carry SR that overlap with the second PUCCH.

8. The UE of claim 7, wherein the Scell ​​BFRQ status information includes a positive Scell ​​BFRQ or a negative Scell ​​BFRQ, wherein the positive Scell ​​BFRQ indicates a request for uplink resources to transmit at least one fault component carrier (CC) index associated with the detection of the Scell ​​beam fault, and the negative Scell ​​BFRQ indicates no request for uplink resources to transmit the at least one fault CC index.

9. The UE according to claim 7, wherein the Scell ​​BFRQ status information has a higher priority than the scheduling request SR.

10. The UE of claim 9, wherein the second PUCCH is used to transmit at least one of Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) and Channel State Information (CSI), and the at least one processor is further configured such that the UE: Determine the total number of PUCCHs configured to carry scheduling requests (SRs) that overlap with the second PUCCH.

11. The UE of claim 7, wherein the second PUCCH carries uplink control information (UCI) having more than two bits.

Images