EP3857800A1

EP3857800A1 - Spatial relation configuration for new radio (nr) uplink transmission

Info

Publication number: EP3857800A1
Application number: EP19865168.9A
Authority: EP
Inventors: Guotong Wang; Yushu Zhang; Gang Xiong; Alexei Vladimirovich Davydov
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2018-09-28
Filing date: 2019-09-27
Publication date: 2021-08-04
Also published as: EP3857800A4; WO2020069381A1

Abstract

A device of a New Radio (NR) User Equipment (UE), a method and a machine readable medium to implement the method. The device includes a Radio Frequency (RF) interface, and processing circuitry coupled to the RF interface, the processing circuitry to: decode a Medium Access Control Control Element (MAC-CE) from a NR evolved NodeB (gNodeB); determine respective spatial relations for respective Physical Uplink Control Channel (PUCCH) resources simultaneously based on the MAC-CE; and encode PUCCHs for transmission to the gNodeB over the respective PUCCH resources based on the respective spatial relations.

Description

SPATIAL RELATION CONFIGURATION FOR NEW RADIO (NR) UPLINK TRANSMISSION

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of and priority from International Patent

Application No. PCT/CN 2018/108382 entitled "DEFAULT SPATIAL RELATION CONFIGURATION FOR NR UPLINK TRANSMISSION," filed September 28, 2018, from U.S. Provisional Patent Application No. 62/805,830 entitled "DEFAULT SPATIAL RELATION CONFIGURATION FOR NR UPLINK TRANSMISSION," filed February 14, 2019, from U.S. Provisional Patent Application No. 62/810,218 entitled " DEFAULT SPATIAL RELATION CONFIGURATION FOR NR UPLINK

TRANSMISSION," filed February 25, 2019, and from U.S. Provisional Patent Application No. 62/831,466 entitled "SPATIAL RELATION CONFIGURATION FOR NR UPLINK TRANSMISSION," filed April 9, 2019, the entire disclosures of which are incorporated herein by reference.

FIELD

[0002] Various embodiments generally may relate to the field of wireless communications, and particularly to configuring or activating a spatial relation for uplink transmissions in a cellular network.

BACKGROUND

[0003] Current Third Generation Partnership Project (3GPP) New Radio (NR) specifications do not specifically address issues related to configuring or activating a spatial relation for uplink transmissions, especially in the context of beam failure.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Fig. 1 illustrates a signaling diagram showing a sequence of signals between a New Radio (NR) evolved NodeB (gNodeB) and a NR User Equipment (UE) according to some embodiments;

[0005] Fig. 2 illustrates a signaling diagram showing signals between a UE and a gNodeB, and further showing actions on the UE side according to one embodiment;

[0006] Fig. 3 illustrates a Medium Access Control Control Element (MAC-CE) format according to one embodiment; [0007] Fig. 4 illustrates a diagram illustrating actions taken by the UE during spatial relation reconfiguration for Physical Uplink Control Channel (PUCCH) according to one embodiment;

[0008] Fig. 5 illustrates a MAC-CE format according to an alternative embodiment;

[0009] Fig. 6 illustrates a signaling diagram showing a sequence of signals gNodeB and UE according to a first embodiment;

[0010] Fig. 7 Fig. 6 illustrates a signaling diagram showing a sequence of signals between a gNodeB and a UE according to a second embodiment;

[0011] Fig. 8 illustrates a signaling diagram showing a sequence of signals between a gNodeB and a UE according to a third embodiment;

[0012] Fig. 9 shows a process according to one embodiment;

[0013] Fig. 10 illustrates an architecture of a system of a network according to some embodiments; and

[0014] Fig. 11 illustrates example interfaces of baseband circuitry according to various embodiments.

DETAILED DESCRIPTION

[0015] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well- known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrase "A or B" means (A), (B), or (A and B).

[0016] During a beam failure recovery (BFR) procedure, spatial configuration/relation for Physical uplink Control Channel (PUCCH)/Physical Uplink Shared Channel (PUSCH)/Sounding Reference Signal (SRS) can no longer be deemed valid because of the beam failure. Spatial relation may be based on a configuration of a downlink (DL) reference signal of an acquired DL beam sent by a NR evolved Node B (gNodeB) for Rx beamforming, where the DL reference signal is used by the UE to determine Tx beamforming from the acquired beam. However, if there is a beam failure with respect to the acquired reference signal, the current spatial relation to be used by the UE for Tx beamforming for PUCCH/PUSCH/SRS is no longer valid.

After sending a beam failure recovery request to the gNodeB, and then receiving from gNodeB of a beam failure recovery response and a beam reestablishment signal, the UE could perform the transmission over PUCCH/PUSCH/SRS with a new, updated spatial relation that is based on more accurate and up to date beamforming. In the space between beam failure on the one hand, and the time when an updated spatial relation is determined on the UE side and applied to PUCCH/PUSCH/SRS based on the beam reestablishment signal from the gNodeB, a default spatial relation for PUCCH/PUSCH/SRS may be applied/assumed by the UE, and the spatial relation therefore then changed in order for the UE to assist in Tx

beamforming selection for transmission over PUCCH/PUSCH/SRS until the updated spatial relation based on the beam reestablishment signal is used by the UE for Tx beamforming. For example, the default spatial relation could be based on a Channel State Information

Reference Signal (CSI-RS) or Synchronization Signal/Physical Broadcast Channel (SS/PBCH) beam from the gNodeB that the UE identifies as a candidate beam during the BFR procedure.

For the spatial relation of PUCCH/PUSCH/SRS after beam failure is detected but before an updated spatial relation is reconfigured for the UE, the UE may, for example, follow the spatial relation for Physical Random Access Channel (PRACH) transmission as the default spatial relation for PUCCH/PUSCH/SRS. The UE may for example use the PRACH to deliver the beam failure recovery request.

[0017] In the instant disclosure, embodiments are disclosed for the PUCCH/PUSCH/SRS default spatial relation/configuration after BFR.

[0018] Default spatial relation for PUCCH/PUSCH/SRS after BFR

[0019] According to one embodiment, after beam failure is detected and a new candidate beam is identified, the UE may send a beam failure recovery request to the gNodeB over PRACH. The PRACH may be transmitted over the identified new candidate beam.

[0020] After BFR, when the UE transmits over PUCCH/PUSCH/SRS, the previously configured spatial relation/configuration for PUCCH/PUSCH/SRS may not be valid any longer by virtue of the failure as noted above. Thus, a default spatial relation may, according to some embodiments, be applied in order for the UE to facilitate transmission over

PUCCH/PUSCH/SRS before an updated spatial relation is reconfigured/re-activated. [0021] Since the UE has already transmitted over PRACH with the identified candidate beam, for example to send the beam failure recovery request, the default spatial relation for a subsequent PUCCH/PUSCH/SRS may, according to one embodiment, follow the one used for the PRACH transmission.

[0022] Referring first to Fig. 1, a signaling diagram 100 is shown showing a sequence of signals between a gNodeB and UE according to one embodiment. As shown in Fig. 1, a beam 102 from the gNodeB fails at the UE, leading to a detection of a beam failure at the UE. Then, after a beam failure recovery response 106 is received from the gNodeB starting at time Tl, according to one embodiment, a default spatial relation may be configured by the UE for a PUCCH/PUSCH/SRS transmission 109. The default spatial relation configured for

PUCCH/PUSCH/SRS transmission, such as transmission 109 that starts at time Tl', may persist at UE until an updated spatial relation is reestablished for PUCCH/PUSCH/SRS by way of a beam reestablishment signal 110, as seen starting at time T2 in Fig. 1. The beam

reestablishment signal 110 which may include, by way of example only, a Radio Resource Control (RRC) signal, or a Medium Access Control Element (MAC CE) signal. The SRS may be periodic or semi-persistent or aperiodic.

[0023] The default spatial relation may, according to one embodiment, correspond to the spatial relation for the PRACH transmission 104 which is shown to start at time TO, which PRACH transmission may be used to deliver the beam failure recovery request from the UE to the gNodeB. For example, the PUCCH/PUSCH/SRS transmission 109 may, according to an embodiment, follow the spatial relation identified during a Random Access Channel RACH procedure conducted by the UE.

[0024] According to one embodiment, for any transmission between times TO and Tl (not shown in Fig. 1), e.g. after the beam failure recovery request is sent over PRACH 104 and until the gNodeB response 106 is received, the previously active spatial relation or indicated spatial relation (that is, the spatial relation with which the UE is configured prior to the beam failure detection for the beam 102) may be applied by the UE for any PUCCH/PUSCH/SRS

transmission. Alternatively, as shown in Fig. 1, the UE may skip any PUCCH/PUSCH/SRS transmission between TO and Tl, or between TO and a time at which the gNodeB receives an acknowledgment (ACK) response from the UE for the gNodeB response 106. Alternatively, the UE may skip any additional PUCCH/PUSCH/SRS transmission between TO and a time at which the gNodeB receives PUSCH/SRS 109 from the UE, which PUSCH/SRS 109 may be dynamically scheduled by the PDCCH106 for beam failure recover (BFR).

[0025] According to another embodiment, after BFR (that is, after the PRACH 104 is sent to the gNodeB, or after the gNodeB response 106 is received at the UE, or after a time at which the gNodeB receives an acknowledgment (ACK) response from the UE for the gNodeB response 106), and before the beam reestablishment signal 110, for an aperiodic SRS transmission, the UE may continue to apply the indicated spatial relation instead of the default spatial relation to the SRS, while applying the default spatial relation to PUCCH/PUSCH transmissions, such as transmission 109. Alternatively, when applying the default spatial relation, the UE may exclude SRS for beam management altogether. In other words, the UE may not be expected to transmit SRS for beam management during BFR procedure before the beam reestablishment signal 109 is received at the UE.

[0026] After a beam failure recovery request is sent over PRACH 104 at timeTO in Fig. 1, according to an embodiment a default spatial relation may be applied by the UE for

PUCCH/PUSCH/SRS transmissions until the spatial relation is reestablished (e.g.

reconfigured/re-activated) for PUCCH/PUSCH/SRS transmissions, such as at time T2 in Fig. 1 by of beam reestablishment signal 110. The default spatial relation may be the one for PRACH transmission 104 to deliver the beam failure recovery request, although embodiments are not so limited.

[0027] Reference is now made to Fig. 2, which shows a signaling diagram 200 showing signals between a UE and a gNodeB, and further showing actions on the UE side, such as, for example, the UE and gNodeB discussed in the context of Fig. 1 above. As shown by way of example in Fig. 2, according to some embodiments, in order to ensure that both the gNodeB and the UE have the same understanding with respect to whether a beam failure recovery response from the gNodeB has been successfully received by the UE, the default spatial relation, as dictated for example by the PRACH 104 in Fig. 1, may be applied to

PUCCH/PUSCH/SRS based on whether the PDCCH that serves as the beam failure recovery response (the PDCCH for BFR response), such as PDCCH 106 of Fig. 1 or PDCCH 206 of Fig. 2) is used to schedule PDSCH transmission, PUSCH transmission (such as PUSCH transmission 109), or aperiodic SRS transmission. The diagram 200 of Fig. 2 shows in more detail an

embodiment of signals between the UE and gNodeB, and of actions taken by the UE, that may take place for example between time T1 of Fig. 1 and time Tl' of Fig. 1. According to some embodiments, the default spatial relation may be applied by the UE to a PUCCH/PUSCH/SRS transmission a number X slots after the UE reports ACK to the gNodeB if the PDCCH for BFR response is used to schedule PDSCH transmission (not shown in Fig. 1 or Fig. 2), or Y slots after the UE transmits a PUSCH if PDCCH for BFR response is used to schedule PUSCH transmission (such as PUSCH 109 of Fig. 1), or Z slots after UE transmits SRS if PDCCH for BFR response is used to schedule aperiodic SRS transmission (not shown in Fig. 1 or Fig. 2), where

X, Y and Z may be predefined or configured by higher layer signaling.

[0028] Referring still to Fig. 2, in an example, if the PDCCH for BFR response (in the searchspace BFR (SS-BFR)) is be used to schedule a PDSCH, K1 slots in the time domain may be needed for the UE to report ACK for the resulting PDSCH. In such a case, Kl+Xl slots after receipt of PDCCH 206, the UE may start to apply a default spatial relation for a

PUCCH/PUSCH/SRS transmission by resetting a Tx beam for some PUCCH resources at 208. If

PDCCH is used to schedule PUSCH, K2 may be needed to transmit PUSCH. Hence in that case,

K2+X2 slots after PDCCH 206, the UE may start to apply the default spatial relation a

PUCCH/PUSCH/SRS transmission by resetting a Tx beam for some PUCCH resources at 208. In one example K1 and K2 may be configured by higher layer signaling. According to some embodiments, X1=X2=0 slot or X1=X2=4 slots. The BFR procedure may also include a retransmission of PRACH 207 by the UE before a resetting of the Tx beam using the default spatial relation.

[0029] Signaling overhead reduction

[0030] For PUCCH, the spatial relation is typically configured per PUCCH resource. After a BFR procedure, if the default spatial relation is applied for all of the possible PUCCH resource, all of the PUCCH resources would need to be reconfigured, which could lead to a large amount of signaling overhead.

[0031] In an embodiment, if the spatial relation of the PUCCH resource is spatially Quasi Co- Located (QCLed) with PDCCH beams over which beam failure is detected (for example beams of PDCCH 102 of Fig. 1), then, the default spatial relation for this PUCCH resource may follow the spatial relation for PRACH transmission (such as PRACH transmission 104 of Fig. 1) until it is reestablished (by a beam reestablishment signal such beam reestablishment signal 110 of Fig. 1), regardless of whether the PUCCH resource is used for ACK/negative ACK (NACK), CSI reporting or a scheduling request (SR). If, however, the spatial relation of the PUCCH resource is not QCLed with the PDCCH beams over which beam failure is detected, then the UE may use the configured or indicated spatial relation for transmission over this PUCCH resource as the default spatial relation.

[0032] In an embodiment, if the default spatial relation happens to be in the spatial relation list configured by RRC signaling, then, a Medium Access Control-Control Element (MAC-CE) may be used by the gNodeB to update the spatial relation for the PUCCH resource to be the same one as the one for PRACH. The spatial relation list is configured by the gNodeB via Radio Resource Control (RRC) signaling when configuring the Physical Uplink Control Channel (PUCCH) resources. In this embodiment, the default spatial relation is the same as identified by PRACH. Thus, the gNB could know whether the default spatial relation is included in the configured spatial relation list or not. After the MAC-CE is received, the UE may apply the default spatial relation, and before the MAC-CE is received, the previously

configured/active/indicated spatial relation may continue to be applied by the UE to uplink resources.

[0033] According to another embodiment, as shown by way of example in Fig. 3, the spatial relation for all PUCCH resources may be updated to the default spatial relation with only one/a single MAC-CE from the gNodeB, with the MAC-CE updating the spatial relation to the default spatial relation after BFR. Referring to Fig. 3, a MAC-CE format 300 is shown. As suggested in Fig. 3, according to some embodiments, if the reserved bit (R bit, which is Ό' by default) in the octet of MAC-CE 300 with PUCCH Resource ID field (Oct 2) or the reserved bit in the first octet (Oct 1) is set to Ί', then it means the spatial relation contained in the MAC- CE is to be applied to all the PUCCH resources by the UE. MAC CE 300 of Fig. 3 includes three levels of octets in the frequency domain, and further provides information, among other things, on a serving cell identification (ID), a bandwidth part (BWP) ID, and a PUCCH resource ID as shown. MAC CE 300 further shows at the third octet (Oct 3) a list of spatial relations, from SO to S7, where one of the spatial relations may be set in the MAC CE to indicate that it is to be activated in the UE side.

[0034] Another option is to use MAC-CE to reset a spatial relation of the PUCCH for all PUCCH resources without limitation to a BFR scenario. For example, one reserved bit in a PUCCH spatial relation activation/re-activation MAC-CE, such as MAC-CE 300 of Fig. 3, may be used to duplicate the spatial relation configuration (e.g. the spatial relation activation/deactivation setting) from the PUCCH resource, as indicated by the PUCCH Resource ID field, to all the other configured PUCCH resources for the UE. If the bit (the 'R' bit in Oct 1 or Oct 2 as shown in Figure 3) is set to Ί', it means the spatial relation activation setting of the PUCCH resource as indicated by the PUCCH Resource ID should be duplicated by the UE to all the other PUCCH resources. In other words, if the bit (the 'R' bit in Oct 1 or Oct 2 as shown in Figure 3) is set to

Ί', then the spatial relation activation/deactivation setting indicated by the MAC-CE (e.g. indicated by Oct 3 as shown in Figure 3) applies to all the configured PUCCH resources for the

UE. If the bit (the 'R' bit in Oct 1 or Oct 2 as shown in Figure 3) is set to 'O', then the spatial relation activation/deactivation setting indicated by the MAC-CE only applies to the PUCCH resource indicated by the PUCCH Resource ID field.

[0035] According to an embodiment, as shown in particular by way of example in Fig. 4, which shows a diagram 400 illustrating actions taken by the UE during spatial relation reconfiguration for PUCCH, firstly, at 402, RRC signaling by the gNodeB may cause the UE to configure/reconfigure a spatial relation for one PUCCH resource, for example, resource A. Thereafter, at 404, a MAC-CE may be sent by the gNodeB to the UE to cause the UE to activate one spatial relation, with the PUCCH Resource ID in the MAC-CE being set to PUCCH resource A and the third octet (Oct 3) (as shown for example in Fig. 3) indicating which spatial relation, SO to S7, is activated, by setting the bit corresponding to the spatial relation SO to S7 to be activated, for example by setting the bit to Ί'. Within the MAC-CE, the reserved bit (R bit) in the first octet (Oct 1) or the second octet (Oct 2) may be set to Ί' to indicate to the UE that all the other PUCCH resources should follow the spatial relation list as configured by RRC for the PUCCH resource as indicated by the PUCCH Resource ID in the MAC-CE, e.g. resource A. The activated spatial relation should also follow the active one as indicated by the MAC-CE for PUCCH Resource A. Later if the spatial relation ought to be updated for PUCCH Resource B only, then, according to an embodiment, the gNodeB may send another MAC-CE to the UE at 406, with the reserved bits in the MAC-CE set to Ό' to indicate that the UE is to update a single PUCCH resource with a new spatial relation. In this way, the signaling overhead to (re)configure the spatial relation for PUCCH could be reduced, since it is not configured on a resource by resource basis. In an example, the naming of the reserved bit, e.g., 'R' bit in Oct 1 or Oct 2 indicating duplication of PUCCH spatial relation configuration could be changed to be bit 'D'.

[0036] Another alternative embodiment introduces a new MAC-CE format to duplicate the spatial relation for PUCCH resources. The new MAC-CE may contain at least the following fields: a BWP ID, a Serving Cell ID and a PUCCH Resource ID and possible reserved bits. The reserved bits in the new MAC-CE may be set to 'O'. The new MAC-CE is to indicate to the UE that the existing/indicated spatial relation configuration for the PUCCH resource as indicated by the PUCCH Resource ID field, may be duplicated by the UE to all the other configured

PUCCH resources for the UE. According to an embodiment, the new MAC-CE may include or even consist of the first two octets of a PUCCH spatial relation activation/deactivation MAC-

CE, such as, for example, the first two octets of the MAC-CE 300 of Fig. 3(Oct 1 and Oct 2).

The reserved bit (R bit) in the first octet (Oct 1) and the second octet (Oct 2) may still kept as reserved bits and may be always set to 'O'.

[0037] Alternatively, according to another embodiment of a MAC CE 500 as shown in Fig. 5, if a bit 'D' in the first octet (or the 'R' bit in the second octet) is set to Ί', it means the existing spatial relation activation/deactivation setting of the PUCCH resource as indicated by the PUCCH Resource ID field should be duplicated to all the configured PUCCH resources for the UE.

[0038] In scenarios involving multi-panel/multi-transmission and reception point (TRP) operation, where a TRP may include, for example, a gNodeB, an embodiment to allow an updating of the PUCCH spatial relation with a MAC-CE may be applied to a subset of the PUCCH resources. In the case of multi-panel/multi-TRP operation, different spatial relations may be applied for different UE panels or with respect to different TRPs.

[0039] In an embodiment, the spatial relation for a subset of all the configured PUCCH resources of a UE may be updated with a single MAC-CE, where the PUCCH resources are grouped into different sets. For example, in the MAC-CE, a field may be used to be indicated the PUCCH resource set(s) to which the new spatial relation is to be applied. The field may for example include a bitmap. According to one example, a PUCCH resource set may be associated with different TRPs. In such a case, according to one embodiment, where the UE is to maintain communication with two TRPs, TRP A and TRP B, the PUCCH resources may be split into two sets, set A and set B associated with TRP A and TRP B respectively. When the network then sends a MAC-CE to activate a new spatial relation for PUCCH resource set B, a field of the MAC-CE may indicate that PUCCH resource set B is to be updated with the new spatial relation, in which case the UE then updates the PUCCH spatial relation with TRP B.

[0040] In another embodiment, the spatial relation for a subset of all the configured PUCCH resources of one UE may be updated with one MAC-CE, where a PUCCH resource set could be associated with different UE antenna panels. For example, if the UE has two antenna panels, panel A and panel B, the PUCCH resources may be split into two sets, set A and set B associated with panel A and panel B respectively. When the network sends a MAC-CE to update the spatial relation with a field indicating PUCCH resource set B, then the PUCCH spatial relation with UE antenna panel B may be updated by the UE.

[0041] In another embodiment, the MAC-CE to update PUCCH spatial relation may include one or more fields to indicate the TRP(s) or UE antenna panel(s) to which the PUCCH spatial relation update is applied. The field or fields could include a bitmap.

[0042] In another embodiment, when the PUCCH resource is configured by the gNodeB, the gNodeB may explicitly configure the PUCCH resource with a group ID. Thereafter, when a MAC-CE is used to update the PUCCH spatial relation, the group ID may be included in the MAC-CE. In such a case, the spatial relation for those PUCCH resources with the same group ID may be updated simultaneously after receiving the MAC-CE. The gNodeB may determine which PUCCH resources belong to the same group based on different rules. The following shows several examples on the grouping rules: the group may be associated with a PUCCH resource set, the group may be associated with a TRPs, the group may be associated with UE antenna panels, or the group may be composed of PUCCH resources which have the same spatial relation configuration. The number of groups may be configured by the gNodeB, or it may be based on the UE's capability, and may be reported by the UE as part of its capability reporting.

[0043] Alternatively, the group ID may be configured by the gNodeB implicitly. For example, if the number of groups is 4, then the PUCCH resources within one PUCCH resource set may be divided equally into 4 parts, each part corresponding to one group. In this way, the overhead could be further reduced as the group ID is not explicitly configured.

[0044] According to an embodiment, the grouping may be based on UE operation, i.e. the UE may determine which PUCCH resources belong to the same group. For example, the PUCCH resources with the same spatial relation configuration may be determined by the UE to belong to the same group.

[0045] According to another embodiment, for single TRP operation, the spatial relation for all PUCCH resources could be changed with one MAC-CE simultaneously. Alternatively, the spatial relation configuration of one subset/group or several subsets/groups of PUCCH resources could be changed by the MAC-CE simultaneously. In the MAC-CE, the group ID and the corresponding spatial relation could be indicated. [0046] According to another embodiment for multi-TRP operation, the spatial relation configuration of one subset/group or several subsets/groups of PUCCH resources could be changed by the MAC-CE simultaneously. In the MAC-CE, the group ID and the corresponding spatial relation could be indicated.

[0047] According to another embodiment, the MAC-CE for PUCCH spatial relation

configuration may indicate whether the spatial relation applies for SSB (SS/PBCH block) based spatial relation or CSI-RS based spatial relation. For example, for a UE, some PUCCH resources may be configured with spatial relation which is SSB, and other PUCCH resources may be configured with spatial relation which is CSI-RS. In the MAC-CE, if the spatial relation in the MAC-CE is indicated to be of type SSB, then the spatial relation should be applied to those PUCCH resources which are configured with SSB based spatial relation. If the spatial relation in the MAC-CE is indicated to be of type CSI-RS, then the spatial relation may be applied to those PUCCH resources which are configured with CSI-RS based spatial relation.

[0048] In other embodiments, after BFR, the default spatial relation that is the one for PRACH transmission may be applied for each PUCCH transmission until the spatial relation is reconfigured/re-activated, for example by way of a beam reestablishment signal such as beam reestablishment signal 110 of Fig. 1. Options A and B may be applicable for such embodiments.

[0049] Option A:

[0050] After BFR (that is, after the PRACH is sent to the gNodeB to deliver the BFR request, or after the gNodeB BFR response is received at the UE, or after a time at which the gNodeB receives an acknowledgment (ACK) response from the UE for the gNodeB BFR response), the spatial relation for all the PUCCH resource may follow the default one, e.g. the one for the PRACH transmission. And the default spatial relation may be valid until the spatial relation is reconfigured/re-activated for any one PUCCH resource, such as by way of a beam

reestablishment signal. If the default spatial relation is not valid, the gNodeB is expected to guarantee that the spatial relation for one PUCCH resource is reconfigured/re-activated by the gNodeB before transmission over the resource.

[0051] Referring to Fig. 6, which is a figure similar to Fig. 1, a signaling diagram 600 is shown showing a sequence of signals between a gNodeB and UE according to one embodiment. As shown in Fig. 6, a beam 602 from the gNodeB fails at the UE, leading to a detection of a beam failure at the UE. Then, after a beam failure recovery response 606 is received from the gNodeB starting at time Tl, according to one embodiment, a default spatial relation may be configured by the UE for a PUCCH/PUSCH/SRS transmission 609. The default spatial relation configured for PUCCH/PUSCH/SRS transmission, such as transmission 609 that starts at time Tl', may persist at UE until an updated spatial relation is reestablished for PUCCH/PUSCH/SRS by way of a beam reestablishment signal 610, as seen starting at time T2 in Fig. 6. The beam reestablishment signal 610 which may include, by way of example only, a Radio Resource Control (RRC) signal, or a Medium Access Control Element (MAC CE) signal.

[0052] As seen in Fig. 6, after TO or Tl, all the PUCCH resource may follow the default spatial relation until the time instance T2. In this way, the starting time point and the ending time point to apply the default spatial relation are the same for all the PUCCH resources.

[0053] Alternatively, the default spatial relation for any specific PUCCH resource may, according to another embodiment, be valid until the spatial relation is reconfigured/re activated for this specific PUCCH resource.

[0054] Referring to Fig. 7, which is a figure similar to Fig. 1, a signaling diagram 700 is shown showing a sequence of signals between a gNodeB and UE according to one embodiment. As shown in Fig. 7, a beam 702 from the gNodeB fails at the UE, leading to a detection of a beam failure at the UE. Then, after a beam failure recovery response 706 is received from the gNodeB starting at time Tl, according to one embodiment, a default spatial relation may be configured by the UE for a PUCCH/PUSCH/SRS transmission 709. The default spatial relation configured for PUCCH/PUSCH/SRS transmission, such as transmission 709 that starts at time Tl', may persist at UE until an updated spatial relation is reestablished for PUCCH/PUSCH/SRS by way of a beam reestablishment signal 710, as seen starting at time T2 in Fig. 7. The beam reestablishment signal 710 which may include, by way of example only, a Radio Resource Control (RRC) signal, or a Medium Access Control Element (MAC CE) signal.

[0055] In particular, as shown by the example in Fig. 7, after TO or Tl, all of the PUCCH resources may follow the default spatial relation. For PUCCH resource A, after the time instance of T2, PUCCH resource A should utilize the spatial relation as reconfigured/re activated, but, for a PUCCH resource B (not shown in the figure) which does not receive reconfiguration/re-activation at T2, the PUCCH resource B should keep the default spatial relation. The default spatial relation for resource B should be kept until the

reconfiguration/re-activation for PUCCH resource B is received by the UE. In this way, the starting time point to apply the default spatial relation is the same for all of the PUCCH resources, while the ending time point for applying the default spatial relation is PUCCH resource specific.

[0056] Option B:

[0057] According to some embodiments, the default spatial relation may be applied only for the PUCCH resource(s) over which the PUCCH transmission happens. For example, after BFR, for each transmission over PUCCH, the spatial relation may follow the default one, e.g. the one for PRACH transmission regardless of whether the PUCCH resource is used for ACK/NACK, CSI reporting or SR. For the PUCCH resource over which there is no transmission yet, the previously configured spatial relation could be kept. The default spatial relation for the specific PUCCH resource over which there is a PUCCH transmission may be valid until the spatial relation is reconfigured/re-activated for this PUCCH resource, for example by way of a beam reestablishment signal.

[0058] Referring to Fig. 8, which is a figure similar to Fig. 1, a signaling diagram 800 is shown showing a sequence of signals between a gNodeB and UE according to one embodiment. As shown in Fig. 8, a beam 802 from the gNodeB fails at the UE, leading to a detection of a beam failure at the UE. Then, after a beam failure recovery response 806 is received from the gNodeB starting at time Tl, according to one embodiment, a default spatial relation may be configured by the UE for a PUCCH/PUSCH/SRS transmission 809. The default spatial relation configured for PUCCH/PUSCH/SRS transmission, such as transmission 809 that starts at time Tl', may persist at UE until an updated spatial relation is reestablished for PUCCH/PUSCH/SRS by way of a beam reestablishment signal 810, as seen starting at time T2 in Fig. 8. The beam reestablishment signal 810 which may include, by way of example only, a Radio Resource Control (RRC) signal, or a Medium Access Control Element (MAC CE) signal.

[0059] As shown by the example in Fig. 8, after TO or Tl, if there is a PUCCH transmission with resource A, it should follow the default spatial relation. And the default spatial relation should be applied for PUCCH resource A until spatial relation reconfiguration/re-activation is received for PUCCH resource A (T2). For another PUCCH resource B (not shown in the figure), which doesn't transmit PUCCH before resource A, it can keep the previously configured spatial relation. If there is a need to transmit over PUCCH resource B, then it should apply the default spatial relation until the spatial relation is reconfigured/re-activated for PUCCH resource B. In this way, the starting time point and the ending time point for applying the default spatial relation are PUCCH resource specific.

IB [0060] Alternatively, according to another embodiment, the default spatial relation for a specific PUCCH resource may be valid only before the spatial relation is reconfigured/re activated for any PUCCH resource. If the previously configured/indicated spatial relation or the default spatial relation is not applied, the gNodeB is expected to guarantee that a spatial relation for one PUCCH resource is reconfigured/re-activated before transmission over the resource.

[0061] Referring still to Fig. 8, after TO or Tl, if there is a PUCCH transmission over resource A, it should follow the default spatial relation, and the default spatial relation should be applied for PUCCH resource A until spatial relation reconfiguration/re-activation is received for PUCCH resource A (T2). For another PUCCH resource B (not shown in the figure), which does not transmit PUCCH before resource A, it may keep the previously configured spatial relation. If there is a need to transmit over PUCCH resource B, then PUCCH resource B should apply the default spatial relation as well. After the spatial relation reconfiguration/re-activation is received for PUCCH resource A (T2), the default spatial relation is not applied for PUCCH resource B. In addition, the gNodeB may guarantee that the spatial relation for resource B should also be reconfigured before the next transmission over the same. In this way, the starting time point for applying the default spatial relation are PUCCH resource specific, and the ending time point for applying the default spatial relation are the same for all the PUCCH resources.

[0062] In another embodiment, a new higher layer (RRC) signaling message may be

introduced to configure/reconfigure the spatial relation for all the existing PUCCH resources, e.g. all the PUCCH resources may share the same spatial relation(s). After BFR, the RRC message may be sent by the gNodeB to reconfigure the spatial relation for all the PUCCH resources. The signaling overhead may be reduced in this way since the spatial relation for PUCCH is not configured on a per PUCCH resource basis.

[0063] In all the embodiments where PRACH is mentioned, the PRACH for beam failure recovery request transmission may be a contention-free PRACH or a contention-based PRACH.

[0064] Referring to Fig. 9, a process 900 according to one embodiment includes at operation 902, decoding a Medium Access Control Control Element (MAC-CE) from a NR evolved NodeB (gNodeB); at operation 904, determining respective spatial relations for respective Physical Uplink Control Channel (PUCCH) resources simultaneously based on the MAC-CE; and at operation 906, encoding PUCCHs for transmission to the gNodeB over the respective PUCCH resources based on the respective spatial relations.

[0065] Fig. 10 illustrates an architecture of a system 1000 of a network according to some embodiments. The system 1000 is shown to include a user equipment (UE) 1001 and a UE 1002. The UEs 1001 and 1002 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also comprise any mobile or non-mobile computing device.

[0066] The UEs 1001 and 1002 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 1010. The UEs 1001 and 1002 utilize connections 1003 and 1004, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 1003 and 1004 are illustrated as an air interface to enable communicative coupling and may be consistent with cellular communications protocols.

[0067] In this embodiment, the UEs 1001 and 1002 may further directly exchange communication data via a ProSe interface 1005. The ProSe interface 1005 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

[0068] The UE 1002 is shown to be configured to access an access point (AP) 1006 via connection 1007. The connection 1007 may comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 1006 would comprise a wireless fidelity (WiFi^®) router. In this example, the AP 1006 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0069] The RAN 1010 may include one or more access nodes that enable the connections 1003 and 1004. These access nodes (ANs) may be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation or New Radio evolved NodeBs (gNodeB), RAN nodes, and so forth, and may comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). The RAN 1010 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 1011, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power

(LP) RAN node 1012.

[0070] According to some embodiments, the UEs 1001 and 1002 may be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 1011 and 1012 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals may comprise a plurality of orthogonal subcarriers.

[0071] The RAN 1010 is shown to be communicatively coupled to a core network (CN) 1020 —via an SI interface 1013. In embodiments, the CN 1020 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the SI interface 1013 is split into two parts: the Sl-U interface 1014, which carries traffic data between the RAN nodes 1011 and 1012 and the serving gateway (S-GW) 1022, and the Sl-mobility management entity (MME) interface 1015, which is a signaling interface between the RAN nodes 1011 and 1012 and MMEs 1021.

[0072] The CN 1020 includes network elements. The term "network element" may describe a physical or virtualized equipment used to provide wired or wireless communication network services. In this embodiment, the CN 1020 comprises, as network elements, the MMEs 1021, the S-GW 1022, the Packet Data Network (PDN) Gateway (P-GW) 1023, and a home subscriber server (HSS) 1024. The MMEs 1021 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).

[0073] Fig. 11 illustrates example interfaces of baseband circuitry according to various embodiments. The baseband circuitry 1100 may be included in a UE or gNodeB, for example, in UE or gNodeB of Fig. 10, and may comprise processors 1138-1142 and a memory 1144 utilized by said processors. Each of the processors 1138-1132 may include a memory interface, 1104A-1104E, respectively, to send/receive data to/from the memory 1144. Baseband circuitry 1100 may also include an audio digital signal processor (Audio DSP) 1143.

[0074] The baseband circuitry 1100 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 1112 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 1100), an application circuitry interface 1114 (e.g., an interface to send/receive data to/from an application circuitry), an RF circuitry interface 1116 (e.g., an interface to send/receive data to/from an RF circuitry), a wireless hardware connectivity interface 1118 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth^® components (e.g., Bluetooth^® Low Energy), Wi-Fi^® components, and other communication components), and a power management interface 1120 (e.g., an interface to send/receive power or control signals to/from a power management integrated circuit (PMIC).

[0075] The components of Figs. 10 and/or 11, such as the shown UEs and gNodeB's, may be used in any of the embodiments described herein.

[0076] The examples set forth herein are illustrative and not exhaustive.

[0077] Example 1 includes a device of a New Radio (NR) User Equipment (UE), the device including a Radio Frequency (RF) interface, and processing circuitry coupled to the RF interface, the processing circuitry to: detect a beam failure with respect to a beam of a downlink transmission from a New Radio evolved Node B (gNodeB); apply a default spatial relation with respect to an intermediate Physical Uplink Control Channel (PUCCH), a Physical

Uplink Shared Channel (PUSCH) or a Sounding Reference Signal (SRS) (PUCCH/PUSCH/SRS) to be transmitted to the gNodeB, the processing circuitry to apply the default spatial relation until a time at which the processing circuitry determines an updated spatial relation with respect to a subsequent PUCCH/PUSCH/SRS from the UE to the gNodeB; and encode the intermediate PUCCH/PUSCH/SRS for transmission to the gNodeB based on the default spatial relation.

[0078] Example 2 includes the subject matter of Example 1, and optionally, wherein the processing circuitry is to decode a beam reestablishment signal from the gNodeB, and to determine the updated spatial relation for the subsequent PUCCH/PUSCH/SRS based on the beam reestablishment signal.

[0079] Example 3 includes the subject matter of Example 1, and optionally, wherein the default spatial relation is based on one of a Channel State Information Reference Signal from the gNodeB to the UE, or a Synchronization Signal/Physical Broadcast Channel from the gNodeB to the UE.

[0080] Example 4 includes the subject matter of Example 1, and optionally, wherein the processing circuitry is to, based on detection of the beam failure, encode for transmission to the gNodeB a beam failure recovery request and thereafter decode a beam failure recovery response from the gNodeB, the processing circuitry to apply the default spatial relation from a time including one of a time at which the UE sends the beam failure recovery request to the gNodeB, a time after which the UE receives the beam failure recovery response from the gNodeB, or a time at which the gNodeB receives an acknowledgment (ACK) for the beam failure recovery response from the UE, and until a time at which the processing circuitry determines the updated spatial relation

[0081] Example 5 includes the subject matter of Example 4, and optionally, wherein the processing circuitry is to apply a spatial relation with which the UE is configured prior to the detection of the beam failure (indicated spatial relation) for a prior PUCCH/PUSCH/SRS to occur prior to the time including one of the time at which the UE sends the beam failure recovery request to the gNodeB, the time after which the UE receives the beam failure recovery response from the gNodeB, or the time at which the gNodeB receives an acknowledgment (ACK) for the beam failure recovery response from the UE.

[0082] Example 6 includes the subject matter of Example 5, and optionally, wherein, when the intermediate SRS includes an aperiodic SRS, the processing circuitry is to apply the default spatial relation to the intermediate PUCCH/PUSCH, and to one of apply the indicated spatial relation to the aperiodic SRS, or to refrain from encoding for transmission the aperiodic SRS until the time at which the processing circuitry determines the updated spatial relation.

[0083] Example 7 includes the subject matter of Example 4, and optionally, wherein the beam failure recovery response includes a Physical Downlink Control Channel (PDCCH), and wherein the processing circuitry is to apply the default spatial relation to the intermediate PUCCH/PUSCH/SRS at a time that is at least X slots after the gNodeB receives an ACK for the PDCCH if the PDCCH is to schedule a Physical Downlink Shared Channel (PDSCH), at least Y slots after the gNodeB receives a prior PUSCH prior to the intermediate PUCCH/PUSCH/SRS if the PDCCH is to schedule the prior PUSCH, and at least Z slots after the UE transmits a prior aperiodic SRS prior to the intermediate PUCCH/PUSCH/SRS if the PDCCH is to schedule the prior aperiodic SRS.

[0084] Example 8 includes the subject matter of Example 1, and optionally, wherein the processing circuitry is to encode for transmission to the gNodeB a Physical Random Access Channel (PRACH), the default spatial relation being based on the PRACH, and the PRACH including a beam failure recovery request based on detection of the beam failure. [0085] Example 9 includes the subject matter of Example 8, and optionally, wherein the intermediate PUCCH/PUSCH/SRS includes an intermediate PUCCH, and wherein: in response to a determination that the spatial relation of the PRACH is Quasi Co-Located (QCLed) with a spatial relation of the downlink transmission, the processing circuitry is to determine the default spatial relation to correspond to a spatial relation of the PRACH; and in response to a determination that the spatial relation of the PRACH is not QCLed with a spatial relation of the downlink transmission, the processing circuitry is to determine the default spatial relation to correspond to a spatial relation with which the UE is configured prior to the detection of the beam failure.

[0086] Example 10 includes the subject matter of Example 1, and optionally, wherein the intermediate PUCCH/PUSCH/SRS includes an intermediate PUCCH, and wherein the processing circuitry is to decode a Medium Access Control Control Element (MAC-CE) to determine the default spatial relation.

[0087] Example 11 includes the subject matter of Example 10, and optionally, wherein the intermediate PUCCH/PUSCH/SRS includes a plurality of intermediate PUCCHs, and wherein the processing circuitry is to decode the MAC-CE to determine the default spatial relation for one of all the intermediate PUCCHs or a subset of the intermediate PUCCHs, wherein the subset includes from one intermediate PUCCH up to less than all of the intermediate PUCCHs.

[0088] Example 12 includes the subject matter of Example 11, and optionally, wherein the MAC-CE includes a PUCCH Resource ID field, and wherein the processing circuitry is to decode the PUCCH Resource ID field to determine which of the intermediate PUCCHs to apply the default spatial relation to.

[0089] Example 13 includes the subject matter of Example 12, and optionally, wherein the MAC-CE further includes a spatial relation bitmap, and wherein the processing circuitry is to decode the spatial relation bitmap to determine the default spatial relation.

[0090] Example 14 includes the subject matter of Example 12, and optionally, wherein the MAC-CE further includes one of a Reserved (R) bit or a bit designated "D", the processing circuitry to decode said one of the R bit or D bit to determine whether to apply the default spatial relation to all the intermediate PUCCHs.

[0091] Example 15 includes the subject matter of Example 12, and optionally, wherein the MAC-CE includes a bandwidth part identification (BWP ID) field and a serving cell identification (Serving Cell ID) field and one or more reserved (R) bits. [0092] Example 16 includes the subject matter of Example 11, and optionally, wherein the processing circuitry is to decode the MAC-CE to determine a plurality of default spatial relations for respective subsets of the intermediate PUCCHs, respective ones of the subsets being associated with respective group IDs in the MAC-CE.

[0093] Example 17 includes the subject matter of Example 16, and optionally, wherein the processing circuitry is to determine groupings of the intermediate PUCCHs into respective subsets.

[0094] Example 18 includes the subject matter of Example 16, and optionally, wherein each of the plurality of default spatial relations correspond to one of respective Transmitting and Receiving Points (TRPs) in communication with the UE, or respective antenna panels of the UE.

[0095] Example 19 includes the subject matter of Example 10, and optionally, wherein the processing circuitry is to decode the MAC-CE to determine whether the default spatial relation is a Synchronization Signal Block/Physical Broadcast Channel (SSB/PBCH) based spatial relation, or a Channel State Information Reference Signal (CSI-RS) spatial relation.

[0096] Example 20 includes the subject matter of any one of Examples 1-19, and optionally, further including a front-end module coupled to the RF interface.

[0097] Example 21 includes the subject matter of Example 20, and optionally, further including one or more antennas coupled to the front end module to communicate with the gNodeB by way of the RF interface.

[0098] Example 22 includes a device of a New Radio (NR) evolved Node B (gNodeB), the device including a Radio Frequency (RF) interface, and processing circuitry coupled to the RF interface, the processing circuitry to: encode for transmission to a NR User Equipment (UE) a Medium Access Control Control Element (MAC-CE), the MAC-CE including information to allow the UE to apply a spatial relation to a Physical Uplink Control Channel (PUCCH) from the UE; and decode the PUCCH based on the spatial relation.

[0099] Example 23 includes the subject matter of Example 22, and optionally, wherein the PUCCH includes a plurality of intermediate PUCCHs, and wherein the processing circuitry is to encode the MAC-CE to indicate the spatial relation for one of all the intermediate PUCCHs or a subset of the intermediate PUCCHs, wherein the subset includes from one intermediate PUCCH up to less than all of the intermediate PUCCHs. [0100] Example 24 includes the subject matter of Example 23, and optionally, wherein the

MAC-CE includes a PUCCH Resource ID field, and wherein the processing circuitry is to encode the PUCCH Resource ID field to indicate which of the intermediate PUCCHs to apply the spatial relation to.

[0101] Example 25 includes the subject matter of Example 23, and optionally, wherein the MAC-CE further includes a spatial relation bitmap, and wherein the processing circuitry is to encode the spatial relation bitmap to allow the UE to determine the spatial relation.

[0102] Example 26 includes the subject matter of Example 23, and optionally, wherein the MAC-CE further includes one of a Reserved (R) bit or a bit designated "D", the processing circuitry to encode said one of the R bit or D bit to allow the UE to determine whether to apply the spatial relation to all the intermediate PUCCHs.

[0103] Example 27 includes the subject matter of Example 23, and optionally, wherein the MAC-CE includes a bandwidth part identification (BWP ID) field and a serving cell identification (Serving Cell ID) field and one or more reserved (R) bits.

[0104] Example 28 includes the subject matter of Example 22, and optionally, wherein the processing circuitry is to encode the MAC-CE to allow the UE to determine a plurality of spatial relations for respective subsets of the intermediate PUCCHs, the MAC-CE including group IDs and respective ones of the subsets being associated with respective ones of the group IDs in the MAC-CE.

[0105] Example 29 includes the subject matter of Example 28, and optionally, wherein the processing circuitry is to determine groupings of the intermediate PUCCHs into respective subsets one of explicitly or implicitly.

[0106] Example 30 includes the subject matter of Example 28, and optionally, wherein each of the plurality of spatial relations correspond to one of respective Transmitting and Receiving Points (TRPs) in communication with the UE, or respective antenna panels of the UE.

[0107] Example 31 includes the subject matter of Example 22, and optionally, wherein the processing circuitry is to encode the MAC-CE to determine whether the spatial relation is a Synchronization Signal Block/Physical Broadcast Channel (SSB/PBCH) based spatial relation, or a Channel State Information Reference Signal (CSI-RS) spatial relation.

[0108] Example 32 includes the subject matter of any one of Examples 22-31, and optionally, further including a front-end module coupled to the RF interface. [0109] Example 33 includes the subject matter of Example 32, and optionally, further including one or more antennas coupled to the front end module to communicate with the gNodeB by way of the RF interface.

[0110] Example 34 includes device of a New Radio (NR) User Equipment (UE), the device including a Radio Frequency (RF) interface, and processing circuitry coupled to the RF interface, the processing circuitry to: decode a Medium Access Control Control Element (MAC-CE) from a NR evolved NodeB (gNodeB); determine respective spatial relations for respective Physical Uplink Control Channel (PUCCH) resources simultaneously based on the MAC-CE; and encode PUCCHs for transmission to the gNodeB over the respective PUCCH resources based on the respective spatial relations.

[0111] Example 35 includes the subject matter of Example 34, and optionally, wherein the processing circuitry is to decode Radio Resource Control (RRC) signaling from the gNodeB indicating respective groups of the PUCCH resources, wherein grouping rules for the RRC signaling include grouping based on at least one of Transmitting and Receiving Points (TRPs), UE antenna panels, PUCCH resource sets, or PUCCH resources with a same spatial relation.

[0112] Example 36 includes the subject matter of Example 34, and optionally, wherein the MAC-CE includes a Group identification (ID) field indicating IDs for respective groups of the PUCCH resources, and a spatial relation field indicating spatial relations for the respective groups of PUCCH resources, wherein a group of PUCCH resources includes one PUCCH resource or multiple PUCCH resources.

[0113] Example 37 includes the subject matter of Example 37, and optionally, wherein the processing circuitry is to determine a spatial relation for one group of the PUCCH resources, or spatial relations for multiple groups of the PUCCH resources based on information in the Group ID field and in the spatial relation field, and to update the spatial relation for the one group or for the multiple groups based on the information .

[0114] Example 38 includes the subject matter of Example 34, and optionally, wherein the processing circuitry is further to: detect a beam failure with respect to a beam of a downlink transmission from the gNodeB; apply a default spatial relation with respect to an intermediate PUCCH resource, Physical Uplink Shared Channel (PUSCH) resource or Sounding Reference Signal (SRS) (PUCCH/PUSCH/SRS) resource, the processing circuitry to apply the default spatial relation based on default spatial relation information in the MAC-CE, and until a time at which the processing circuitry determines an updated spatial relation with respect to a subsequent PUCCH/PUSCH/SRS resource; and encode an intermediate

PUCCH/PUSCH/SRS in the intermediate PUCCH/PUSCH/SRS resource for transmission to the gNodeB based on the default spatial relation in the MAC-CE.

[0115] Example 39 includes the subject matter of Example 38, and optionally, wherein the processing circuitry is to decode a beam reestablishment signal from the gNodeB, and to determine the updated spatial relation for the subsequent PUCCH/PUSCH/SRS resource based on the beam reestablishment signal.

[0116] Example 40 includes the subject matter of Example 38, and optionally, wherein the processing circuitry is to, based on detection of the beam failure, encode for transmission to the gNodeB a beam failure recovery request and thereafter decode a beam failure recovery response from the gNodeB, the processing circuitry to apply the default spatial relation from a time including one of a time at which the UE sends the beam failure recovery request to the gNodeB, a time after which the UE receives the beam failure recovery response from the gNodeB, or a time at which the gNodeB receives an acknowledgment (ACK) for the beam failure recovery response from the UE, and until a time at which the processing circuitry determines the updated spatial relation

[0117] Example 41 includes the subject matter of Example 40, and optionally, wherein the beam failure recovery response includes a Physical Downlink Control Channel (PDCCH), and wherein the processing circuitry is to apply the default spatial relation to the intermediate PUCCH/PUSCH/SRS resources at a time that is at least X slots after the gNodeB receives an ACK for the PDCCH if the PDCCH is to schedule a Physical Downlink Shared Channel (PDSCH), at least Y slots after the gNodeB receives a prior PUSCH prior to the intermediate PUCCH/PUSCH/SRS if the PDCCH is to schedule the prior PUSCH, and at least Z slots after the UE transmits a prior aperiodic SRS prior to the intermediate PUCCH/PUSCH/SRS if the PDCCH is to schedule the prior aperiodic SRS.

[0118] Example 42 includes the subject matter of Example 40, and optionally, wherein the processing circuitry is to encode for transmission to the gNodeB a Physical Random Access Channel (PRACH), the default spatial relation being based on the PRACH, and the PRACH including a beam failure recovery request based on detection of the beam failure.

[0119] Example 43 includes the subject matter of any one of Examples 34-42, and optionally, wherein further including a front end module coupled to the RF interface. [0120] Example 44 includes the subject matter of Example 43, and optionally, further including one or more antennas coupled to the front end module to communicate with the gNodeB by way of the RF interface.

[0121] Example 45 includes a method to be performed at a device of a New Radio (NR) User Equipment (UE), the method including: decoding a Medium Access Control Control Element (MAC-CE) from a NR evolved NodeB (gNodeB); determining respective spatial relations for respective Physical Uplink Control Channel (PUCCH) resources simultaneously based on the MAC-CE; and encoding PUCCHs for transmission to the gNodeB over the respective PUCCH resources based on the respective spatial relations.

[0122] Example 46 includes the subject matter of Example 45, and optionally, further including decoding Radio Resource Control (RRC) signaling from the gNodeB indicating respective groups of the PUCCH resources wherein grouping rules for the RRC signaling include grouping based on at least one of Transmitting and Receiving Points (TRPs), UE antenna panels, PUCCH resource sets, or PUCCH resources with a same spatial relation.

[0123] Example 47 includes the subject matter of Example 45, and optionally, wherein the MAC-CE includes a Group identification (ID) field indicating IDs for respective groups of the PUCCH resources, and a spatial relation field indicating spatial relations for the respective groups of PUCCH resources, wherein a group of PUCCH resources includes one PUCCH resource or multiple PUCCH resources.

[0124] Example 48 includes the subject matter of Example 47, and optionally, further including determining a spatial relation for one group of the PUCCH resources, or spatial relations for multiple groups of the PUCCH resources, based on information in the Group ID field and in the spatial relation field, and updating the spatial relation for the one group or for the multiple groups based on the information .

[0125] Example 49 includes the subject matter of Example 45, and optionally, further including: detecting a beam failure with respect to a beam of a downlink transmission from the gNodeB; applying a default spatial relation with respect to an intermediate PUCCH resource, Physical Uplink Shared Channel (PUSCH) resource or Sounding Reference Signal (SRS) (PUCCH/PUSCH/SRS) resource, applying the default spatial relation based on default spatial relation information in the MAC-CE, and until a time at which the UE determines an updated spatial relation with respect to a subsequent PUCCH/PUSCH/SRS resource; and encoding an intermediate PUCCH/PUSCH/SRS in the intermediate PUCCH/PUSCH/SRS resource for transmission to the gNodeB based on the default spatial relation in the MAC-CE.

[0126] Example 50 includes the subject matter of Example 49, and optionally, further including decoding a beam reestablishment signal from the gNodeB, and determining the updated spatial relation for the subsequent PUCCH/PUSCH/SRS based on the beam reestablishment signal.

[0127] Example 51 includes the subject matter of Example 49, and optionally, further including, based on detection of the beam failure, encoding for transmission to the gNodeB a beam failure recovery request and thereafter decoding a beam failure recovery response from the gNodeB, applying the spatial relation including applying the default spatial relation from a time including one of a time at which the UE sends the beam failure recovery request to the gNodeB, a time after which the UE receives the beam failure recovery response from the gNodeB, or a time at which the gNodeB receives an acknowledgment (ACK) for the beam failure recovery response from the UE, and until a time at which the UE determines the updated spatial relation

[0128] Example 52 includes the subject matter of Example 51, and optionally, wherein the beam failure recovery response includes a Physical Downlink Control Channel (PDCCH), the method further including applying the default spatial relation to the intermediate PUCCH/PUSCH/SRS resources at a time that is at least X slots after the gNodeB receives an ACK for the PDCCH if the PDCCH is to schedule a Physical Downlink Shared Channel (PDSCH), at least Y slots after the gNodeB receives a prior PUSCH prior to the intermediate PUCCH/PUSCH/SRS if the PDCCH is to schedule the prior PUSCH, and at least Z slots after the UE transmits a prior aperiodic SRS prior to the intermediate PUCCH/PUSCH/SRS if the PDCCH is to schedule the prior aperiodic SRS.

[0129] Example 53 includes the subject matter of Example 51, and optionally, further including encoding for transmission to the gNodeB a Physical Random Access Channel (PRACH), the default spatial relation being based on the PRACH, and the PRACH including a beam failure recovery request based on detection of the beam failure.

[0130] Example 54 includes a device of a New Radio (NR) User Equipment (UE), the device including: means for decoding a Medium Access Control Control Element (MAC-CE) from a NR evolved NodeB (gNodeB); means for determining respective spatial relations for respective Physical Uplink Control Channel (PUCCH) resources simultaneously based on the MAC-CE; and means for encoding PUCCHs for transmission to the gNodeB over the respective PUCCH resources based on the respective spatial relations.

[0131] Example 55 includes the subject matter of Example 54, and optionally, further including means for decoding Radio Resource Control (RRC) signaling from the gNodeB indicating respective groups of the PUCCH resources wherein grouping rules for the RRC signaling include grouping based on at least one of Transmitting and Receiving Points (TRPs), UE antenna panels, PUCCH resource sets, or PUCCH resources with a same spatial relation.

[0132] Example 56 includes the subject matter of Example 54, and optionally, wherein the MAC-CE includes a Group identification (ID) field indicating IDs for respective groups of the PUCCH resources, and a spatial relation field indicating spatial relations for the respective groups of PUCCH resources, wherein a group of PUCCH resources includes one PUCCH resource or multiple PUCCH resources.

[0133] Example 57 includes the subject matter of Example 54, and optionally, further including means for determining a spatial relation for one group of the PUCCH resources, or spatial relations for multiple groups of the PUCCH resources, based on information in the Group ID field and in the spatial relation field, and means for updating the spatial relation for the one group or for the multiple groups based on the information .

[0134] Example 58 includes the subject matter of Example 54, and optionally, further including: means for detecting a beam failure with respect to a beam of a downlink transmission from the gNodeB; means for applying a default spatial relation with respect to an intermediate PUCCH resource, Physical Uplink Shared Channel (PUSCH) resource or Sounding Reference Signal (SRS) (PUCCH/PUSCH/SRS) resource, applying the default spatial relation based on default spatial relation information in the MAC-CE, and until a time at which the UE determines an updated spatial relation with respect to a subsequent PUCCH/PUSCH/SRS resource; and means for encoding an intermediate PUCCH/PUSCH/SRS in the intermediate PUCCH/PUSCH/SRS resource for transmission to the gNodeB based on the default spatial relation in the MAC-CE.

[0135] Example 59 includes a device of a New Radio (NR) evolved NodeB (gNodeB), the device including a Radio Frequency (RF) interface, and processing circuitry coupled to the RF interface, the processing circuitry to: encode a Medium Access Control Control Element (MAC-CE) for transmission to a NR User Equipment (UE), the MAC-CE indicating respective spatial relations for respective Physical Uplink Control Channel (PUCCH) resources to allow the UE to simultaneously update the spatial relations for the respective ones of the PUCCH resources based on the MAC-CE; and decode Physical Uplink Control Channels (PUCCHs) from the UE over the respective PUCCH resources configured based on the respective spatial relations.

[0136] Example 60 includes the subject matter of Example 59, and optionally, wherein the processing circuitry is to encode Radio Resource Control (RRC) signaling to the UE indicating respective groups of the PUCCH resources, wherein grouping rules for the RRC signaling include grouping based on at least one of Transmitting and Receiving Points (TRPs), UE antenna panels, PUCCH resource sets, or PUCCH resources with a same spatial relation.

[0137] Example 61 includes the subject matter of Example 59, and optionally, wherein the MAC-CE includes a Group identification (ID) field indicating IDs for respective groups of the PUCCH resources, and a spatial relation field indicating spatial relations for the respective groups of PUCCH resources, wherein a group of PUCCH resources includes one PUCCH resource or multiple PUCCH resources.

[0138] Example 62 includes the subject matter of Example 61, and optionally, wherein the MAC-CE is to indicate, using information in the Group ID field and in the spatial relation field, a spatial relation for one group of the PUCCH resources or spatial relations for multiple groups of the PUCCH resources.

[0139] Example 63 includes the subject matter of any one of Examples 59-61, and optionally, further including a front end module coupled to the RF interface.

[0140] Example 64 includes the subject matter of Example 63, and optionally, further including one or more antennas coupled to the front end module to communicate with the gNodeB by way of the RF interface.

[0141] Example 65 includes a machine-readable medium including code which, when executed, is to cause a machine to perform the method of any one of the Examples above.

[0142] Example 66 includes a product comprising one or more tangible computer-readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one processor to perform the method of any one of the Examples above.

[0143] Example 67 includes a machine-readable medium including code which, when executed, is to cause a machine to perform the method of any one of the Examples above. [0144] Example 68 includes a product comprising one or more tangible computer-readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one processor to perform the method of any one of the Examples above.

[0145] Example 69 includes a method to be performed at a device of a New Radio (NR) evolved Node B (gNodeB) or of a NR User Equipment (UE), the method including performing the functionalities of the processing circuitry of any one of the Examples above described in the context, respectively, of a gNodeB or a UE.

[0146] Example 70 includes an apparatus comprising means for causing a wireless communication device to perform the method of any one of the Examples above.

[0147] Example 71 includes an apparatus comprising means for causing a wireless communication device to perform the method of any one of the Examples above.

[0148] Example 72 may include a signal as described in or related to any of the examples above, or portions or parts thereof.

[0149] Example 73 may include a signal in a wireless network as shown and described herein.

[0150] Example 74 may include a method of communicating in a wireless network as shown and described herein.

[0151] Example 75 may include a system for providing wireless communication as shown and described herein.

[0152] Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed.

Claims

What is Claimed is:

1. A device of a New Radio (NR) User Equipment (UE), the device including a Radio Frequency (RF) interface, and processing circuitry coupled to the RF interface, the processing circuitry to:

decode a Medium Access Control Control Element (MAC-CE) from a NR evolved NodeB (gNodeB);

determine respective spatial relations for respective Physical Uplink Control Channel (PUCCH) resources simultaneously based on the MAC-CE; and

encode PUCCHs for transmission to the gNodeB over the respective PUCCH resources based on the respective spatial relations.

2. The device of claim 1, wherein the processing circuitry is to decode Radio Resource Control (RRC) signaling from the gNodeB indicating respective groups of the PUCCH resources, wherein grouping rules for the RRC signaling include grouping based on at least one of Transmitting and Receiving Points (TRPs), UE antenna panels, PUCCH resource sets, or PUCCH resources with a same spatial relation.

3. The device of claim 1, wherein the MAC-CE includes a Group identification (ID) field indicating IDs for respective groups of the PUCCH resources, and a spatial relation field indicating spatial relations for the respective groups of PUCCH resources, wherein a group of PUCCH resources includes one PUCCH resource or multiple PUCCH resources.

4. The device of claim 3, wherein the processing circuitry is to determine a spatial relation for one group of the PUCCH resources, or spatial relations for multiple groups of the PUCCH resources based on information in the Group ID field and in the spatial relation field, and to update the spatial relation for the one group or for the multiple groups based on the information .

5. The device of claim 1, wherein the processing circuitry is further to:

detect a beam failure with respect to a beam of a downlink transmission from the gNodeB; apply a default spatial relation with respect to an intermediate PUCCH resource,

Physical Uplink Shared Channel (PUSCH) resource or Sounding Reference Signal (SRS)

(PUCCH/PUSCH/SRS) resource, the processing circuitry to apply the default spatial relation based on default spatial relation information in the MAC-CE, and until a time at which the processing circuitry determines an updated spatial relation with respect to a subsequent

PUCCH/PUSCH/SRS resource; and

encode an intermediate PUCCH/PUSCH/SRS in the intermediate PUCCH/PUSCH/SRS resource for transmission to the gNodeB based on the default spatial relation in the MAC-CE.

6. The device of claim 5, wherein the processing circuitry is to decode a beam

reestablishment signal from the gNodeB, and to determine the updated spatial relation for the subsequent PUCCH/PUSCH/SRS resource based on the beam reestablishment signal.

7. The device of claim 5, wherein the processing circuitry is to, based on detection of the beam failure, encode for transmission to the gNodeB a beam failure recovery request and thereafter decode a beam failure recovery response from the gNodeB, the processing circuitry to apply the default spatial relation from a time including one of a time at which the UE sends the beam failure recovery request to the gNodeB, a time after which the UE receives the beam failure recovery response from the gNodeB, or a time at which the gNodeB receives an acknowledgment (ACK) for the beam failure recovery response from the UE, and until a time at which the processing circuitry determines the updated spatial relation

8. The device of claim 7, wherein the beam failure recovery response includes a Physical Downlink Control Channel (PDCCH), and wherein the processing circuitry is to apply the default spatial relation to the intermediate PUCCH/PUSCH/SRS resources at a time that is at least X slots after the gNodeB receives an ACK for the PDCCH if the PDCCH is to schedule a Physical Downlink Shared Channel (PDSCH), at least Y slots after the gNodeB receives a prior PUSCH prior to the intermediate PUCCH/PUSCH/SRS if the PDCCH is to schedule the prior PUSCH, and at least Z slots after the UE transmits a prior aperiodic SRS prior to the intermediate PUCCH/PUSCH/SRS if the PDCCH is to schedule the prior aperiodic SRS.

9. The device of claim 7, wherein the processing circuitry is to encode for transmission to the gNodeB a Physical Random Access Channel (PRACH), the default spatial relation being based on the PRACH, and the PRACH including a beam failure recovery request based on detection of the beam failure.

10. The device of any one of claims 1-9, further including a front end module coupled to the RF interface.

11. The device of claim 10, further including one or more antennas coupled to the front end module to communicate with the gNodeB by way of the RF interface.

12. A method to be performed at a device of a New Radio (NR) User Equipment (UE), the method including:

decoding a Medium Access Control Control Element (MAC-CE) from a NR evolved NodeB (gNodeB);

determining respective spatial relations for respective Physical Uplink Control Channel (PUCCH) resources simultaneously based on the MAC-CE; and

encoding PUCCHs for transmission to the gNodeB over the respective PUCCH resources based on the respective spatial relations.

IB. The method of claim 12, further including decoding Radio Resource Control (RRC) signaling from the gNodeB indicating respective groups of the PUCCH resources, wherein grouping rules for the RRC signaling include grouping based on at least one of Transmitting and Receiving Points (TRPs), UE antenna panels, PUCCH resource sets, or PUCCH resources with a same spatial relation.

14. The method of claim 12, wherein the MAC-CE includes a Group identification (ID) field indicating IDs for respective groups of the PUCCH resources, and a spatial relation field indicating spatial relations for the respective groups of PUCCH resources, wherein a group of PUCCH resources includes one PUCCH resource or multiple PUCCH resources.

15. The method of claim 14, further including determining a spatial relation for one group of the PUCCH resources, or spatial relations for multiple groups of the PUCCH resources, based on information in the Group ID field and in the spatial relation field, and updating the spatial relation for the one group or for the multiple groups based on the information .

16. The method of claim 12, further including:

detecting a beam failure with respect to a beam of a downlink transmission from the gNodeB;

applying a default spatial relation with respect to an intermediate PUCCH resource, Physical Uplink Shared Channel (PUSCH) resource or Sounding Reference Signal (SRS) (PUCCH/PUSCH/SRS) resource, applying the default spatial relation based on default spatial relation information in the MAC-CE, and until a time at which the UE determines an updated spatial relation with respect to a subsequent PUCCH/PUSCH/SRS resource; and

encoding an intermediate PUCCH/PUSCH/SRS in the intermediate PUCCH/PUSCH/SRS resource for transmission to the gNodeB based on the default spatial relation in the MAC-CE.

17. The method of claim 16, further including decoding a beam reestablishment signal from the gNodeB, and determining the updated spatial relation for the subsequent

PUCCH/PUSCH/SRS based on the beam reestablishment signal.

18. The method of claim 16, further including, based on detection of the beam failure, encoding for transmission to the gNodeB a beam failure recovery request and thereafter decoding a beam failure recovery response from the gNodeB, applying the spatial relation including applying the default spatial relation from a time including one of a time at which the UE sends the beam failure recovery request to the gNodeB, a time after which the UE receives the beam failure recovery response from the gNodeB, or a time at which the gNodeB receives an acknowledgment (ACK) for the beam failure recovery response from the UE, and until a time at which the UE determines the updated spatial relation

19. The method of claim 18, wherein the beam failure recovery response includes a Physical Downlink Control Channel (PDCCH), the method further including applying the default spatial relation to the intermediate PUCCH/PUSCH/SRS resources at a time that is at least X slots after the gNodeB receives an ACK for the PDCCH if the PDCCH is to schedule a Physical Downlink Shared Channel (PDSCH), at least Y slots after the gNodeB receives a prior PUSCH prior to the intermediate PUCCH/PUSCH/SRS if the PDCCH is to schedule the prior PUSCH, and at least Z slots after the UE transmits a prior aperiodic SRS prior to the intermediate PUCCH/PUSCH/SRS if the PDCCH is to schedule the prior aperiodic SRS.

20. The method of claim 18, further including encoding for transmission to the gNodeB a Physical Random Access Channel (PRACH), the default spatial relation being based on the PRACH, and the PRACH including a beam failure recovery request based on detection of the beam failure.

21. A device of a New Radio (NR) User Equipment (UE), the device including:

means for decoding a Medium Access Control Control Element (MAC-CE) from a NR evolved NodeB (gNodeB);

means for determining respective spatial relations for respective Physical Uplink Control Channel (PUCCH) resources simultaneously based on the MAC-CE; and

means for encoding PUCCHs for transmission to the gNodeB over the respective PUCCH resources based on the respective spatial relations.

22. The device of claim 20, further including means for decoding Radio Resource Control (RRC) signaling from the gNodeB indicating respective groups of the PUCCH resources, wherein grouping rules for the RRC signaling include grouping based on at least one of Transmitting and Receiving Points (TRPs), UE antenna panels, PUCCH resource sets, or PUCCH resources with a same spatial relation.

23. The device of claim 20, wherein the MAC-CE includes a Group identification (ID) field indicating IDs for respective groups of the PUCCH resources, and a spatial relation field indicating spatial relations for the respective groups of PUCCH resources, wherein a group of PUCCH resources includes one PUCCH resource or multiple PUCCH resources.

24. The device of claim 22, further including means for determining a spatial relation for one group of the PUCCH resources, or spatial relations for multiple groups of the PUCCH resources, based on information in the Group ID field and in the spatial relation field, and means for updating the spatial relation for the one group or for the multiple groups based on the information .

25. A product comprising one or more tangible computer-readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one processor to perform the method of any one of claims 12-20.